Abstract:
A system management apparatus and method adapted for use in a network system that comprises a plurality of devices such as computers connected via a network, whereby it is possible to automatically manage device information unique to each of the devices in association with users of the devices and subordinate organizations that possess the devices. The system and method additionally allow for automatically creating a database for managing device information of each device that constitutes a network system, thereby reducing system administrator&#39;s efforts required for system management operations. Moreover, in accordance with the system management apparatus and method of this invention, it is possible to interlock a database for managing device information of each device that constitutes a network system with another database for managing information of subordinate organizations having the devices and users of the devices such that a change in the users and the subordinate organizations is automatically reflected in the device information of each device, thereby facilitating maintenance and management of the device information.

Description:
FIELD OF THE INVENTION  
         [0001]    This invention relates to a system management apparatus and a method for use in a network system, which may be provided in a business organization, for managing serial numbers and users of respective devices (e.g., computers or the like) in the system on a user basis and/or a subordinate organization basis.  
         BACKGROUND OF THE INVENTION  
         [0002]    A network system, comprising a plurality of computers connected via a network, has been used in the art to perform data processing, data transfers and the like. In general, system management operations in such a system have been performed by associating information unique to devices (constituents of the system) with users and subordinate organizations that possess the devices respectively.  
           [0003]    For example, Japanese Patent Publications, identified in Japanese as Tokkai sho 63-114337, Tokkai hei 4-79446, Tokko hei 1-16066 and Tokko hei 7-44541 (References  1  to  4 ), disclose electronic mail schemes and data transfer schemes, each exploiting such a network system. However, these References merely disclose methods for associating destinations and routes of mails (data) with subordinate organizations of users and names thereof. In another words, none of the References discloses a method of automatically managing information of devices in association with users and subordinate organizations.  
           [0004]    In view of the aforementioned problems of the prior art, it is an object of this invention to provide a system management apparatus and a method for use in a network system, comprising a plurality of devices such as computers connected via a network, which are capable of automatically managing device information unique to each of the devices in association with subordinate organizations possessing the devices and users thereof.  
           [0005]    It is an object of the invention to automatically manage device data unique to each of the devices that constitutes a network system in association with users of devices and subordinate organizations that possess the devices.  
           [0006]    It is another object of this invention to provide a system management apparatus and a method, for automatically creating a database for managing device information relating to each of the devices (constituents of a network system), thereby to reduce system administrator&#39;s efforts required for system management operations.  
           [0007]    It is yet another object of this invention to provide a system management apparatus and a method, which cause a database for managing device information relatung to each of the devices (constituents of a network system) to be interlocked or collaborated with another database for managing information of subordinate organizations possessing the devices and users thereof, whereby a change in a user and/or a subordinate organization is automatically reflected in the device information of each device in a way to facilitate maintenance and management of the device information.  
         SUMMARY OF THE INVENTION  
         [0008]    In order to accomplish said objects of this invention, there is provided a first system management apparatus, for use in a system including one or more managed devices for managing a device data item of each of said managed devices, which comprises an information database for storing one or more information data items, each having a keyword data item; a device database for storing one or more device data items, each being unique to each of said managed devices, and for storing each of said keyword data items in association with each of said device data items; and data change/management means, being responsive to a change in a given one of said information data items, for changing a given one of said device data items, stored in said device database in association with said keyword data item of said given one of said information data items, consistent with said change in said given one of said information data items, thereby managing said device data items of said managed devices.  
           [0009]    Further in accordance with another aspect of this invention, there is provided a second system management apparatus for use in a system including one or more managed devices, wherein said managed devices and said second system management apparatus communicate with each other via a network, each of said managed devices having a unique device data item and a keyword data item assigned thereto, and each of said managed devices being responsive to a scanning operation via said network for returning said assigned device data item and keyword data item. Said second system management apparatus is adapted for managing a device data item of each of said managed devices, and it comprises an information database for storing one or more information data items, each having said keyword data item; a device database for storing said device data items of said managed devices respectively, and for storing said keyword data items in association with said device data items respectively; device change detecting means for scanning each of said managed devices, said device change detecting means, being responsive to said device data item and said keyword data item returned from each of said managed devices, for detecting a device change that includes a change in a given one of said managed devices and/or a change in a given one of said device data items; and, first device database updating means for updating said device data item and said keyword data item, stored in said device database and assigned to a given one of said managed devices, consistent with said detected device change.  
           [0010]    Preferably, said information data item and said device data partly overlap each other, and said first or second system management apparatus further comprises second device database updating means for updating the overlapped portion of said device data item, stored in said device database and assigned to a given one of said managed devices, consistent with said information data item which is stored in said information database and which has said keyword data item associated with said device data item to be updated. Preferably, said information data item represents an information item of a user of said managed device, said keyword data item represents a user of said managed device, and said device A data item includes at least a portion of an information item of a user of said managed device.  
           [0011]    In an exemplary environment where a plurality of computers having peripheral devices such as printers (managed devices) are connected via a network for communicating with each other via the network, each of said first and second system management apparatuses automatically updates and manages contents of a database (device database), which stores and manages device data items uniquely assigned to the managed devices, such as manufacturer&#39;s serial numbers (serial numbers), identification numbers of users (employee numbers), organizational numbers (organizational codes) of users&#39; subordinate organizations and the like, in association with contents of another database (information database), which stores and manages identification numbers of users and information items relating to users&#39; subordinate organizations.  
           [0012]    In a typical case where changes of users (i.e., personnel changes occur due to renewal of subordinate organizations and such changes give rise to changes in the information database, said data change/management means of said first system management apparatus uses employee numbers or the like of data items relating to the changed users as keywords (keyword data items), which are commonly stored in the device database and the information database respectively, retrieves device data items of computers that were used by the users who left their subordinate organizations from those data items stored in the device database, and then changes such device data items of computers found as a result of the retrieval so as to make such device data items consistent with contents of the changed information database. Thus, said data change/management means replaces the employee numbers or the like of device data items of computers that were used by the users who left their subordinate organizations with other employee numbers or the like of other users who are newly added due to the personnel changes, thereby preventing any disagreement or inconsistency between contents of the device database and the information database.  
           [0013]    Further, in said second system management apparatus of this invention, a device data item is assigned to each of the computers (managed devices) respectively, and each of the computers has functions for transmitting the assigned device data item to said second system management apparatus via said network in response to a request therefrom. Said first device database updating means issues a request to each of the computers via the network for transmitting a device data item at a specified time (e.g., at the time of starting system operations, after starting the system operation, at periodical intervals, or in response to a system administrator&#39;s action), detects addition/removal of a computer to/from the network system or any setup change for computers, and then changes contents of the device database consistent with the detected changes. Thus, said first device database updating means periodically adds a device data item of a newly added computer into the device database, erases a device data item of a removed computer, or changes device data items stored in the device database consistent with a device data item obtained from a computer subject to a setup change for causing the device data items to be consistent with those device data items actually set up for computers in the network system.  
           [0014]    Further, in accordance with another aspect of this invention, there is provided a first system management method for use in a system including one or more managed devices for managing a device data item of each of said managed devices, which comprises the steps of: storing one or more information data items, each having a keyword data item; storing one or more device data items, each being unique to each of said managed devices, and storing each of said keyword data items in association with each of said device data items; and responsive to a change in a given one of said information data items, changing a given one of said device data items stored in said device database in association with said keyword data item of said given one of information data items, with said change in said given one of information data items, thereby managing said device data items of said managed devices.  
           [0015]    Further, in accordance with another aspect of this invention, there is provided a second system management method for use in a system including one or more managed devices and a system management apparatus for managing a device data item of each of said managed devices, wherein said managed devices and said system management apparatus communicate each other via a network, each of said managed devices has a unique device data item and a keyword data item assigned thereto, each of said managed devices being responsive to a scanning operation via said network for returning said assigned device data item and keyword data item. Said second system management method comprises the steps of: storing one or more information data items, each having said keyword data item; storing said device data items of said managed devices respectively, and storing said keyword data items in association with said device data items respectively; scanning each of said managed devices and, responsive to said device data item and said keyword data item returned from each of said managed devices, detecting a device change that includes a change in a given one of said managed devices and/or a change in a given one of said device data items; and updating said device data item and said keyword data item stored in said device database and assigned to a given one of said managed devices, consistent with said detected device change.  
           [0016]    Further in accordance with another aspect of this invention, there is provided a first machine readable storage medium for storing a program adapted for use in a system including one or more managed devices and a system management apparatus for managing a device data item of each of said managed devices. Said program is executable by a computer for causing said system management apparatus to carry out machine-effected steps of: storing one or more information data items, each having a keyword data item; storing one or more device data items, each being unique to each of said managed devices, and storing each of said keyword data items in association with each of said device data items; and responsive to a change in a given one of said information data items, changing a given one of said device data items, which is stored in said device database in association with said keyword item of said given one of information data items, consistent with said change in said given one of information data items, thereby managing said device data items of said managed devices.  
           [0017]    Further, in accordance with another aspect of this invention, there is provided a second machine readable storage medium for storing a program adapted for use in a system including one or more managed devices and a system management apparatus for managing a device data item of each of said managed devices, wherein said managed devices and said system management apparatus communicate with each other via a network, each of said managed devices having a unique device data item and a keyword data item assigned thereto, and each of said managed devices being responsive to a scanning operation via said network for returning said assigned device data item and keyword data item. Said program is executable by a computer for causing said system management apparatus to carry out machine-effected steps of: storing one or more information data items, each having said keyword data item; storing said device data items of said managed devices respectively, and storing said keyword data items in association with said device data items respectively; scanning each of said managed devices and, responsive to said device data item and said keyword data item returned from each of said managed devices, detecting a device change that includes a change in a given one of said managed devices and/or a change in a given one of said device data items; and updating said device data item and said keyword data item, which are stored in said device database and are assigned to a given one of said managed devices, consistent with said detected device change. 
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0018]    The invention will now be described in greater detail with reference to the appended drawings wherein:  
         [0019]    [0019]FIG. 1 is a diagram showing a network system wherein a system management method of this invention may be applied;  
         [0020]    [0020]FIG. 2 is a flow chart showing a setup process of device data in a managed program shown in FIG. 1;  
         [0021]    [0021]FIG. 3 is a flow chart schematically showing a process of a system management program shown in FIG. 1;  
         [0022]    [0022]FIG. 4 is a diagram exemplifying a summary of a system scanning process shown in FIG. 3;  
         [0023]    [0023]FIG. 5 is a flow chart showing a system scanning process shown in FIGS. 3 and 4;  
         [0024]    [0024]FIG. 6 is a diagram showing a summary of a first database synchronization process shown in FIG. 3;  
         [0025]    [0025]FIG. 7 is a flow chart showing a first database synchronization process shown in FIGS. 3 and 6;  
         [0026]    [0026]FIG. 8 is a diagram exemplifying a summary of a second database synchronization process shown in FIG. 3; and  
         [0027]    [0027]FIG. 9 is a flow chart showing a system display process shown in FIG. 3. 
     
    
     DESCRIPTION OF THE PREFERRED EMBODIMENT  
       [0028]    [0028]FIG. 1 shows a network system  1 , wherein a network management method of this invention may be applied. As shown in FIG. 1, the network system  1  comprises k management apparatuses  2  (FIG. 1 exemplifies a case of k= 1 ), managed devices  3 - 1  to  3 -m (FIG. 1 exemplifies a case of m= 7 ), and a communication network  10 , such as a data communication network, an ISDN network or a LAN network, which is capable of supporting data communication (without distinction of protocols). Hereinbelow, when an arbitrary one of the managed devices  3 - 1  to  3 -m is referred to, it will be simply called “managed device  3 ” in singular or plural form, as the case may be.  
         [0029]    The network system  1 , with these constituents, transmits data between the management apparatus  2  and the managed devices  3 , processes the same, and automatically changes device data (which is unique to each of the managed devices  3 ) consistent with any addition/removal of the managed devices  3  and/or any setup change for the managed devices  3 , as well as any change of personnel information such as a reshuffling of users of the managed devices  3  and the like.  
         [0030]    &lt;Management Apparatus  2 &gt; 
         [0031]    The management apparatus  2  comprises, for example, a display device  200  such as a CRT display or the like, an input/output device  20  having an input device including a keyboard  204  and a mouse  206  for accepting a user&#39;s action, a computer  22  having data communication functions and executing a system management program  220 , a system management database (DB)  24  and a database (DB)  26  for personnel-organization information. Note that, in the management apparatus  2 , the system management database  24  and the personnel-organization database  26  may be implemented by using hardware other than the computer  22 , or they may be implemented as software that uses resources of the computer  22 .  
         [0032]    &lt;System Management Program  220 &gt; 
         [0033]    The system management program  220  implements system management functions of the management apparatus  2  as described below. For each of the subordinate organizations (e.g., divisions/sections in a business organization) that use the network system  1 , the system management program  220  stores names and identifiers (employee numbers) of employees (users) who belong to this subordinate organization in the personnel-organization database  26  in association with an identifier (organizational number) of this subordinate organization for management purpose (Function A). Hereinbelow, such data stored into the personnel-organization database  26  and managed therein will be collectively called “personnel information data”.  
         [0034]    Further, in response to acceptance of a system administrator&#39;s action entered via the keyboard  204  or the like, the system management program  220  retrieves the system management database  24  by using employee numbers (keywords) included in the personnel information data stored in the personnel-organization database  26 , issues a request to a given one of the managed device  3  that is being used by a designated user for transmitting device data, receives the device data returned from such managed device  3  in response to the request, and displays the received device data on the display device  200  (Function B: system display function).  
         [0035]    Further, at the time of starting operations of the management apparatus  2 , for example, the system management program  220  issues requests to each of the managed devices  3  via the communication network  10  for transmitting device data, receives the device data returned from each of the managed devices  3  in response to the requests, and stores the received device data into the system management database  24  for management therein. Note here that the device data so returned includes additional data (e.g., employee numbers of users who use the managed devices  3 , organizational numbers of subordinate organizations that possess the managed devices  3 , contact points of the users and the like) that may be changed in accord with personnel changes, as well as data unique to each of the managed devices  3  (e.g., manufacturer&#39;s serial numbers, device names, network addresses, memory amounts, configurations of hard disks and the like).  
         [0036]    Further, after starting operations of the network system  1 , at periodical intervals, or in response to a system administrator&#39;s action entered via the keyboard  204  or the like, for example, the system management program  220  issues requests to each of the managed devices  3  via the communication network  10  for transmitting the latest device data, receives the device data returned from each of the managed devices  3  in response to the requests, detects any addition/removal of the managed devices  3 , or any setup change of device data for the managed devices  3 , and updates device data in the system management database  24  in line with the actual system configurations and device data in the network system  1  (Function C: system scanning function).  
         [0037]    Further, the system management program  220  retrieves personnel information data stored in the personnel-organization database  26  by using keywords (employee numbers or the like that are commonly stored in the system management database  24  and the personnel-organization database  26 ) of the device data returned from the managed devices  3 , transmits the additional data of the personnel information data that is obtained as a result of the retrieval to the managed devices  3 , and updates the device data assigned to the managed devices  3  (Function D: system information update function).  
         [0038]    Further, should there be changes in members (users) of subordinate organizations due to personnel changes and give rise to changes in the contents of the personnel information data stored in the personnel-organization database  26 , the system management program  220  uses employee numbers or the like as keywords, changes/updates the device data in the system management database  24  associated with the changed points of personnel information data in line with the personnel information data, thereby avoiding any discrepancy or inconsistency between the contents of the device data in the system management database  24  and the contents of the personnel information data in the personnel-organization database  26  (Function E: database synchronization function).  
         [0039]    Further, the system management program  220  accepts device data set up by a system administrator via the keyboard  204  or the like, and transmits the device data to a given one of the managed devices  3  via the communication network  10 , thereby causing the device data of this managed device  3  to be updated (Function F).  
         [0040]    &lt;Managed Devices  3 &gt; 
         [0041]    Similar to the management apparatus  2 , each of the managed devices  3  comprises, for example, a display device  200 , an input/output device  30  having an input component, a computer  32  having data communication functions and capable of executing a managed program  320 , and a hard disk drive  34  for storing device data entered from the input/output device  30 . While FIG. 1 illustrates constituents of the managed device  3 - 1  alone, it should be understood that each of the other managed devices  3 - 2  to  3 -m has the same constituents as well.  
         [0042]    &lt;Managed Program  320 &gt; 
         [0043]    As described below, the managed program  320  has functions required for accepting management by the management apparatus  2 . The managed program  320  accepts a user&#39;s setup action for device data entered via the keyboard  204  or the like, and stores the device data in a non-volatile storage device such as the hard disk drive  34  (Function a). Further, the managed program  320  reads device data from the hard disk drive  34  in response to a request transmitted from the management apparatus  2  via the communication network  10 , and transmits the read device data to the management apparatus  2  via the communication network  10  (Function b). Further, the managed program  320  receives new device data from the management apparatus  2  via the communication network  10 , and replaces old device data stored in the hard disk drive  34  with the new device data to update a setup of device data (Function c).  
         [0044]    &lt;Operations of Network System  1 &gt; 
         [0045]    Hereinbelow, operations of the network system  1  adapted for implementing primary ones of the aforementioned system management functions will be described.  
         [0046]    &lt;Setup of Device Data for Managed devices  3 &gt; 
         [0047]    First, with reference to FIG. 2, a setup process of device data for the managed devices  3  (corresponding to said Function a) will be described. FIG. 2 is a flow chart showing a setup process of device data by the managed program  320  shown in FIG. 1. As shown in FIG. 2, at step  120  (S 120 ), the managed program  320  accepts device data entered by a user via the keyboard  204 . At step  122  (S 122 ), the managed program  320  stores the accepted device data into the hard disk drive  34 .  
         [0048]    &lt;Summary of Process of System Management Program  220 &gt; 
         [0049]    Next, with reference to FIG. 3, a summary of process of the system management program  220  of the management apparatus  2  will be described. FIG. 3 is a flow chart schematically showing a process (main program) of the system management program  220  shown in FIG. 1. As shown in FIG. 3, at step  100  (S 100 ), the system management program  220  accepts a system administrator&#39;s action entered via the keyboard  204  or the like. At step  102  (S 102 ), the system management program  220  analyzes the entered command, and determines if the entered command is a predetermined command (a system scanning command or a system information update command) that corresponds to either of Functions C, D (the system scanning function or the system information update function). If the entered command is a system scanning command or a system information update command, the system management program  220  proceeds to S 200 . Otherwise it continues to perform a command analysis process of S 110 . Note that details of the system scanning process (S 200 ) will be described below with reference to FIGS. 4 and 5.  
         [0050]    At step  110  (S 110 ), the system management program  220  determines if the entered command is a database synchronization command that corresponds to Function E. If the entered command is a database synchronization command, the system management program  220  proceeds to a database synchronization process at step S 300 . Otherwise, the system management program  220  determines that the entered command is a system display command that corresponds to Function B (system display function), and proceeds to the system display process at step S 400 . Note that details of the database synchronization process (S 300 ) will be described below with reference to FIGS.  4  to  8 , whereas details of the system display process (S 400 ) will be described below with reference to FIG. 9. At each of the steps  104 ,  112 ,  114  (S 104 , S 112 , S 114 ), the system management program  220  displays executed results of S 200 , S 300 , S 400  on the display device  200 .  
         [0051]    &lt;System Scanning Process and System Information Update Process&gt; 
         [0052]    Now, with reference to FIGS. 4 and 5, the system scanning process (Function C) and the system information update process (Function D), shown in FIG. 3 as S 200 , will be described. FIG. 4 is a diagram exemplifying a summary of the system scanning process shown in FIG. 3. FIG. 5 is a flow chart showing the system scanning process shown in FIGS. 3 and 4. In the system scanning process, the system management program  220  of the management apparatus  2  communicates with the managed programs  320  of the managed devices  3  and, as briefed at legend ( 1 ) in FIG. 4, collects device data of each of the managed devices  3 , including device numbers (serial numbers) of computers PCOO 1  to PC 0 O 3 , as well as device numbers of peripheral devices (printers) PRT 001 , PRT 002 , arranges the collected device data by using employee numbers (EOOO 1  to E 0004 ) as keywords, thereby to automatically generate data to be stored in the system management database (SM-DB)  24 .  
         [0053]    Further, as briefed at legend ( 2 ) in FIG. 4, the system management program  220  interlocks the system management database (SM-DB)  24  with the personnel-organization database (PO-DB)  26  to manage device data and, as briefed at legend ( 3 ) in FIG. 4, classifies users&#39; employee numbers of personnel information data stored in the personnel-organization database  26  for each of the subordinate organizations, thereby to display device data of each of the managed devices  3  in association with the classified user&#39;s employee number or the user&#39;s name (process of S 104  shown in FIG. 3).  
         [0054]    Now details of the system scanning process will be described. First, procedures (S 202  to S 218 ) executable on the management apparatus  2  in the system scanning process will be described. As shown in FIG. 5, at step  202  (S 202 ), the system management program  220  broadcasts a system scanning command to each of the managed devices  3  via the communication network  10  to request transmission of device data assigned to each of the managed devices  3 . Upon receipt of the system scanning command, respective managed programs  320  (in each of the managed devices  3 ) return a system scanning response, including device data stored in the hard disk drive  34 , to the management apparatus  2 . At step  204  (S 204 ), the system management program  220  receives the system scanning response returned from each of the managed devices  3  via the communication network  10 .  
         [0055]    At step  206  (S 206 ), the system management program  220  retrieves/interrogates the system management database (SM-DB)  24 , by using the keyword (e.g., employee number) included in the device data of the system scanning response returned from each of the managed devices  3 . At step  208  (S 208 ), the system management program  220  determines, based on the interrogated result of the system management database  24  at S 206 , if each of the managed devices  3  that has returned the system scanning response is registered in the system management database  24  and, if so, it proceeds to S 210 . Otherwise, it branches to S 212 .  
         [0056]    At step  210  (S 210 ), the system management program  220  adds records (device data) of non-registered managed devices  3  to the system management database  24 . At step  212  (S 212 ), the system management program  220  retrieves/interrogates the personnel-organization database (PO-DB)  26 , by using a keyword (employee number) included in the device data of a received system scanning response, and acquires personnel information data of a user including this keyword.  
         [0057]    At step  214  (S 214 ), the system management program  220  transmits a system information update command to a designated one of the managed devices  3  for updating additional data included in device data that has been assigned to this managed devices  3 . Note in this respect that, among the data included in the acquired personnel information data, said system information update command includes additional data (employee number of the user, organizational number of the subordinate organization that possesses this managed devices  3 , contact point of the user, and the like) in the device data. At step  216  (S 216 ), the system management program  220  updates device data in the system management database  24  such that the content of device data received from this managed device  3  and additional data in the personnel information data obtained as a result of the retrieval/interrogation to the personnel-organization database  26  matches with content of associated device data in the system management database  24 . Thereafter, the system management program  220  displays the processed results on the display device  200  (S 112  in FIG. 3). At step  218  (S 218 ), the system management program  220  determines if another system scanning response has been received from any of the remaining managed devices  3  and, if so, it proceeds to S 204 . Otherwise, it terminates the process.  
         [0058]    Now, procedures (S 220  to S 226 ) executable on a given one of the managed devices  3  will be described. At step  220  (S 220 ), the managed program  320  of this managed devices  3  determines if a system scanning command or a system information update command has been received from the management apparatus  2  via the communication network  10  and, if so, proceeds to S 222 . At step  222  (S 222 ), the managed program  320  determines if the received command is a system scanning command and, if so, it proceeds to S 224 . Otherwise, it determines that the received command is a system information update command and branches to S 226 .  
         [0059]    At step  224  (S 224 ), the managed program  320  acquires device data stored in the hard disk drive  34 , transmits a system scanning response including the acquired device data to the management apparatus  2  via the communication network  10 , and proceeds to S 220  (Function b). At step  226  (S 226 ), the managed program  320  updates device data stored in the hard disk drive  34  in line with additional data included in the system information update command received from the management apparatus  2  (Function c).  
         [0060]    &lt;First Database Synchronization Process (Function E)&gt; 
         [0061]    Hereinbelow, with reference to FIGS. 6 and 7, a first database synchronization process (S 300  in FIG. 3; Function E), which is adapted for use in a case where personnel information data in the personnel-organization database  26  has been changed due to a personnel change, will be described in detail. FIG. 6 is a diagram showing a summary of the first database synchronization function shown in FIG. 3. FIG. 7 is a flow chart showing the first database synchronization function shown in FIGS. 3 and 6.  
         [0062]    If, before execution of the first database synchronization process, there occurs a change in a subordinate organization that uses the network system  1 , this organizational change will be reflected in the personnel-organization database  26  as changes personnel information data stored therein. It is assumed here for the purpose of explaining a specific example as shown in FIG. 6 that “Hanako Yamakawa”, a user of an employee number E 0002 , leaves a subordinate organization represented by organizational number  110  due to a personnel change and, thus, personnel information data in the personnel-organization database  26  is changed. It is further assumed that to a computer of a device number PCO 01 , which has been used by “Hanako Yamakawa” before the personnel change, an employee number E 0001  of “Taro Suzuki” is provided as new device data after the personnel change. In this case, as briefed at legend ( 1 ) in FIG. 6, the system management program  220  detects the personnel change in response to a change action for the personnel-organization database (PO-DB)  26 , or in response to the occurrence of any difference in the personnel information data stored in the personnel-organization database  26  before and after the change action.  
         [0063]    Next, as briefed at legend ( 2 ) in FIG. 6, the system management program  220  retrieves the system management database (SM-DB)  24 , acquires device data including device number PC 0 O 2  of the computer that has been used by “Hanako Yamakawa”, and further acquires the latest device data from the computer of device number PC 0 O 2  via the communication network  10  in an online manner. If the acquired device data do not match each other, the system management program  220  confirms a user&#39;s change (more particularly, the fact that the computer of the device number PC 0 O 2  has been transferred from “Hanako Yamakawa” to “Taro Suzuki”).  
         [0064]    Next, as briefed at legend ( 3 ) in FIG. 6, the system management program  220  changes the device data for the computer having the device number PC 0 O 2  as stored in the system management database  24  to be consistent with the personnel information data of “Taro Suzuki” as stored in the personnel-organization database  26 , and it automatically updates the contents of the system management database  24 .  
         [0065]    Now, with reference to FIG. 7, the first database synchronization process will be described in detail. First, procedures (S 302  to S 322 ) executable on the management apparatus  2  in the first database synchronization process will be described. At step  302  (S 302 ), the system management program  220  detects any change of personnel information data in the personnel-organization database (PO-DB)  26 , and retrieves/interrogates a user (unprocessed user) who is not yet subject to the process (database synchronization process) for changing device data stored in the system management database  24  in line with the changed personnel information data.  
         [0066]    At step  304  (S 304 ), the system management program  220  determines if there is an unprocessed user and, if negative, it terminates the process. Otherwise, it proceeds to S 306 . At step  306  (S 306 ), the system management program  220  uses, for example , an employee number included in personnel information data of an unprocessed user as a keyword to retrieve/interrogate any device data that includes the same employee number as the keyword and is stored in the system management database (SM-DB)  24 . In other words, it is determined if there is any device data of a given one of the managed devices  3  that is registered in the system management database  24  as a device of an unprocessed user.  
         [0067]    At step  308  (S 308 ), the system management program  220  uses an address of the managed device  3 , that is included in the device data obtained as a result of the interrogation of the system management database  24  at S 306 , to transmit a system scanning command, as shown in FIG. 5, to the managed devices  3  of the unprocessed user via the communication network  10 . Upon receipt of the system scanning command, the managed device  3  of the unprocessed user returns a system scanning response, as shown in FIG. 5. At step  310  (S 310 ), the system management program  220  receives the system scanning response from the managed device  3  via the communication network  10 . At step  312  (S 312 ), the system management program  220  uses a keyword (employee number) included in the received system scanning response to retrieve/interrogate the personnel-organization database  26 , thereby to acquire personnel information data including this keyword.  
         [0068]    At step  314  (S 314 ), the system management program  220  transmits a system information update command, as shown in FIG. 5, to the managed devices  3  of the unprocessed user. Note in this respect that, among the data included in the acquired personnel information data, said system information update command includes additional data (employee number of this user, organizational number of subordinate organization that possesses this managed devices  3 , contact point of this user, and the like) in the device data. At step  316  (S 316 ), the system management program  220  updates device data stored in the system management database  24 , such that the content of device data received from this managed device  3  of the unprocessed user and additional data in the personnel information data obtained from the personnel-organization database  26  as a result of the retrieval/interrogation match with content of corresponding device data stored in the system management database  24 .  
         [0069]    At step  318  (S 318 ), the system management program  220  determines if there is another managed device  3  of the same unprocessed user and, if so, it proceeds to S 308 . Otherwise, it proceeds to S 320 . At step  320  (S 320 ), the system management program  220  sets up those managed devices  3  of the unprocessed user, which are subject to the database synchronization process at S 306  to S 318 , to indicate that they have been processed. Incidentally, if personnel information data stored in the personnel-organization database  26  is rendered to contain a field for indicating whether or not the database synchronization process with respect to corresponding device data stored in the system management database  24  is finished, such that data indicating an unprocessed state is written into this field until the database synchronization process is finished after any change in personnel information data due to a personnel change, and another data indicating a processed state is written into this field after the database synchronization process is finished, it will be useful in knowing an unprocessed/processed state of the database synchronization process, thereby enabling reliable execution of the database synchronization process.  
         [0070]    At step  322  (S 322 ), the system management program  220  determines if the database synchronization process has been executed for device data of the managed devices  3  of all unprocessed users. If so, the process is terminated. Otherwise, it proceeds to S 306 . The system management program  220  displays results of the first database synchronization process on the display device  200 .  
         [0071]    Next, procedures (S 330  to S 336 ) executable on a given one of the managed devices  3  in the first database synchronization process will be described. At step  330  (S 330 ), the managed program  320  of this managed device  3  determines if a system scanning command or a system information update command is received from the management apparatus  2  via the communication network  10  and, if so, it proceeds to S 332 . At step  332  (S 332 ), the managed program  320  determines if the received command is a system scanning command and, if so, it proceeds to S 334 . Otherwise, it determines that the received command is a system information update command and proceeds to S 336 .  
         [0072]    At step  334  (S 334 ), the managed program  320  acquires device data stored in the hard disk drive  34 , adds the device data to a system scanning response, transmits it to the management apparatus  2  via the communication network  10 , and proceeds to S 330  (Function b). Alternatively, at step  336  (S 336 ), the managed program  320  updates device data stored in the hard disk drive  34  consistent with the additional data included in the system information update command received from the management apparatus  2  (Function c). As described, even when the management apparatus  2  executes the database synchronization process, processing of the managed device  3  is the same as the cases where the system scanning process and the system information update process are executed.  
         [0073]    &lt;Second Database Synchronization Process (Function E)&gt; 
         [0074]    Hereinbelow, with reference to FIG. 8, a second database synchronization process (S 300  in FIG. 3; Function E), which is adapted for use in a case where a given one of the managed devices  3  is newly added to the network system  1 , will be described. FIG. 8 is a diagram exemplifying a summary of the second database synchronization process shown in FIG. 3. It is assumed here for the purpose of explaining a specific example as shown in FIG. 8 that, before execution of the second database synchronization process, a computer of device number PC 0 O 4  has been added to the network system  1  as a new managed device  3 . It is further assumed that additional information (employee number and the like) of “Saburo Yamada”, whose employee number is E 0005 , is set up to this added managed device  3 .  
         [0075]    In this case, as briefed at legend ( 1 ) in FIG. 8, the system management program  220  detects, by means of the system scanning function, a given managed device  3  that is newly added to the network system  1  and that is not registered in the system management database (SM-DB)  24 . The system management program acquires device data from this detected managed device  3 . Next, as briefed at legend ( 2 ) in FIG. 8, the system management program  220  creates a record of this new managed device  3  based on the acquired device data, and retrieves/interrogates the personnel-organization database (PO-DB)  26  by using an employee number included in the acquired device data as a keyword.  
         [0076]    Next, as briefed at legend ( 3 ) in FIG. 8, the system management program  220  acquires personnel information data of “Saburo Yamada” from the personnel-organization database  26 , generates device data of this new managed device  3  in line with the acquired personnel information data, and stores the newly generated record in the system management database  24 , thereby updating the contents of the system management database  24 .  
         [0077]    Now, with reference to FIG. 7 again, differences between the first database synchronization process and the second database synchronization process will be described. First, procedures executable on the management apparatus  2  in the second database synchronization process will be described.  
         [0078]    In the second database synchronization process, the system management program  220  does not execute procedures of S 302  to S 306  shown in FIG. 7. Instead, at step  308  (S 308 ), the system management program  220  broadcasts a system scanning command to each of the managed devices  3  via the communication network  10 . At step  310  (S 310 ), the system management program  220  receives a system scanning response from each of the managed devices  3  via the communication network  10 . At step  312  (S 312 ), the system management program  220  compares device data included in a system scanning response received from each of the managed devices  3  with device data stored in the system management database  24 , in order to detect a managed device  3  that is newly added to the network system  1 .  
         [0079]    In the second database synchronization process, the system management program  220  does not execute the processes of S 314  and S 316 . At step  318  (S 318 ), the system management program  220  determines if there is another managed devices  3  that is newly added to the network system  1  and, if negative, terminates the process. On the other hand, if there is a new managed device  3 , it proceeds to S 320 .  
         [0080]    At step  320  (S 320 ), the system management program  220  creates a record of this new managed device  3  in the system management database  24 , retrieves the personnel-organization database  26  by using an employee number, which is included in the device data of this new managed device  3  received at S 310  as a keyword, creates device data consistent with the personnel information data of a user of this new managed device  3  obtained as a result of the retrieval, stores the created device data into the record in the system management database  24 , thereby updating the contents of the system management database  24 . At step  322  (S 322 ), the system management program  220  determines if the second database synchronization process has been executed for device data of all of the managed devices  3  that are newly added to the network system  1 . If so, the process is terminated. Otherwise, it returns to S 320 .  
         [0081]    As described above, by modifying the first database synchronization process shown in FIG. 7 , it is possible to implement the second database synchronization process. Further, even in the second database synchronization process, there is no modification for the procedures (S 330  to S 336 ) executable on each of the managed devices  3 . Moreover, if the second database synchronization process (which is adapted for use in a case where a new managed device  3  is added to the network system  1 ) is so modified as to detect a removed managed device  3  based on device data obtained from each of the managed devices  3 , to delete device data of this removed managed device  3  from the system management database  24 , and to delete data relating to this removed managed device  3  from personnel information data stored in the personnel-organization database  26 , it will be possible to apply the second database synchronization process to a case where a managed device  3  is removed from the network system.  
         [0082]    &lt;System Display Function (Function B)&gt; 
         [0083]    Hereinbelow, with reference to FIG. 9, the system display function (Function B) shown in S 400  in FIG. 3 will be described. In the case of executing the system display function as shown in FIG. 9, the system management program  220  executes the database synchronization process (S 300  in FIG. 3, FIGS.  6  to  8 ). At step  402  (S 402 ), the system management program  220  retrieves the personnel-organization database (PO-DB)  26 , and acquires information of existing subordinate organizations. At step  404  (S 404 ), the system management program  220  selects either one of the acquired subordinate organizations, and acquires personnel information data of users belonging to the selected subordinate organization.  
         [0084]    At step  406  (S 406 ), the system management program  220  retrieves the system management database (SM-DB)  24  by using an employee number included in the acquired personnel information data as a keyword, and acquires device data of all of the managed devices  3  that are used by one of the users who belongs to this subordinate organization. At step  408  (S 408 ), the system management program  220  determines if the device data of managed devices  3  used by all users who belongs to this subordinate organization have been acquired and, if so, it proceeds to S 410 . Otherwise, it returns to S 406 .  
         [0085]    At step  410  (S 410 ), the system management program  220  determines if device data of managed devices  3  used by users who belong to all subordinate organizations have been acquired and, if so, it proceeds to S 412 . Otherwise, it returns to S 404 . At step  412  (S 412 ), the system management program  220  arranges employee numbers, names and the like included in the acquired personnel information data in association with each of the subordinate organizations, associates keywords such as employee numbers or the like included in the personnel information data so arranged with device data of the managed devices  3  that include the same keywords, and displays them in the form of tables for each of the subordinate organizations/individuals (S 114  in FIG. 3).  
         [0086]    As described above, in accordance with the system management method of this invention, it is always possible to automatically maintain consistency between contents of the system management database  24  and contents of the personnel-organization database  26 , even where a managed device  3  is newly added to the network system  1  or any of the managed devices  3  constituting the network system  1  is changed. Further, in accordance with the system management method of this invention, it is possible to manage device data for each of the managed devices  3  in the network system  1  in association with subordinate organizations that possess the managed devices  3  and users, whereby efforts of a system administrator may be significantly reduced and yet occurrence of working errors may be prevented.  
         [0087]    It should be noted here that the configuration of the network system  1  shown in FIG. 1 is exemplary and it may be readily modified by those skilled in the art in terms of number of each constituent and types thereof. By the same token, the processing algorithm executable on each constituent of the network system  1  is exemplary and may be replaced by another algorithm provided that each accomplish substantially the same functions and performance.  
         [0088]    The invention has been described with reference to several specific embodiments. One having skill in the relevant art will recognize that modifications may be made without departing from the spirit and scope of the invention as set forth in the appended claims.