JP5198159B2 - Client terminal management system - Google Patents

Description

  The present invention relates to a management system for a client terminal that integrates and manages the status of a plurality of devices (assets) such as personal computers and household electrical appliances owned by a company.

  Organizations such as companies use information devices such as personal computers and home appliances (hereinafter referred to as assets) such as air conditioners in their buildings, and the usage status of these devices is managed. Normally, such asset management is performed manually by users and managers of the asset, but it has also been proposed to perform the management in an integrated manner using a management system.

  As an example, the monitoring center monitors failures in the monitored hardware system. If there is a failure in the hardware system, the monitoring center analyzes the failure and decides how to recover it, and the worker repairs it. A technique for working is proposed (for example, see Patent Document 1).

  In this technology described in Patent Document 1, the CPU, memory, HD, LAN, expansion board, UPS, etc. in the hardware system to be monitored are the hardware to be monitored, and this is the hardware system to be monitored. The fault monitoring computer in FIG. 1 constantly monitors and when a fault of hardware to be monitored (failure such as HD fault or temperature abnormality) is detected, fault data and a fault detection signal are sent to the monitoring center. In the monitoring center, the monitoring center computer obtains the report, creates a report, and notifies the hardware administrator computer in the hardware system to be monitored of the failure. At the same time, in the management center, the responsible maintenance base computer 4 analyzes the failure based on the report from the monitoring center computer, determines the recovery method, and causes the worker to perform the recovery operation. When the monitored hardware recovers, the fault monitoring computer detects this and notifies the management center, and the monitoring center computer of the monitoring center uses the hardware manager in the monitored hardware system. Notify the computer.

  As another example, a user office and a management center are connected via a network. By applying for asset management at the user office, an information device that registers and manages this asset at the management center can be used. An asset management system has been proposed (see, for example, Patent Document 2).

In the asset management system described in Patent Document 2, the asset information and asset information (such as the manager responsible and the device purchase date) of the information device for which management is applied at the user application terminal of the user office are input to obtain the asset information. When applying for new registration or change, the management center registers or changes this as an asset management table. At the same time, the management center checks the operating status of the information equipment in the user office that has been registered or changed, and if it is in the operating status, the operating start date is not in the operating status. In this case, register the information “stopped” in the asset management table as the operational status confirmation information, and register the asset management table in the corresponding information device in the user office that applied for it. . In this way, the asset number and asset information of each information device can be confirmed from the asset management table regardless of whether the information device is operating or stopped, and even if the information device does not have a display device. .
JP 2001-325165 A JP 2005-148974 A

  By the way, according to the technique described in Patent Document 1, when a failure or abnormality occurs in a monitoring target, this is detected and notified to the management center, and the management center analyzes the notification content to determine a recovery method, The management center handles only the monitoring target that has been notified of a failure or abnormality, and constantly monitors the status of each asset in the organization such as a company. Then it is not a thing.

  In the technique described in Patent Document 2, the management center registers and changes the applied asset information, and registers the operation start date of the asset for which registration or change has been applied. Is.

  As described above, the techniques described in the cited documents 1 and 2 do not always monitor the status of each monitoring target. In particular, the technique described in Patent Document 1 manages when a failure or abnormality occurs. Since the center operates in order to cope with this, there is a problem that a failure or an abnormality is likely to occur or an asset in which these may occur cannot be confirmed.

  The purpose of the present invention is to solve such problems, constantly monitor each asset in the organization such as a company, and to confirm the assets that are likely or likely to fail or abnormally. It is an object of the present invention to provide a client terminal management system that can cope with the above.

  To achieve the above object, the present invention comprises a plurality of client terminals, an event management server connected to the client terminals via a communication line, and a display terminal for displaying event management information of the event management server. A client terminal management system, in which an event management server defines a control unit, an event database for storing event information related to an event that occurred in each client terminal, and information on the importance of the event, and is stored in the event database. An event group table for selecting event information of an important event from the event information, an event group table for setting a combination of related event information selected by the important event table as an event group, and an event group Event group data to be stored And a local information database that stores, as local information, information relating to the physical arrangement relationship of a plurality of client terminals and the hierarchical structure on the network, and the control unit includes the event information stored in the event database. For event information determined to be important with reference to the important event table, the event group table is referenced to determine whether or not to register as an event group, and the event information to be registered is combined with each other Event group, register the event group as event management information in the event group database, accept display request of event management information from the display terminal, read the event group from the event group database, read from the local information database Event information with local information Management information is transmitted to the display terminal, and the display terminal receives the event management information transmitted from the event management server. Based on the received event management information on the display screen, the display area and event group of the client terminal are displayed. Based on the physical arrangement of the client terminals based on local information and the hierarchical structure on the network, images of the client terminals are arranged and displayed in the display area of the client terminals, and the number of event groups per day By displaying the time-dependent change in the number of occurrences of the event group in the display area of the event group.

  Further, the present invention provides a support information table for setting conditions for obtaining support information and a form of support information for each event group, and for creating support information from the event group. A support information database for storing support information, the control unit refers to a support information table for the event group stored in the event group database, determines the presence or absence of corresponding support information, The support information to be registered is registered in the support information database, the display request of the event management information from the display terminal is received, and the support information stored in the support information database is sent together with the event group and the local information to the event management information. To the display terminal, the display terminal is the client terminal in the display area of the client terminal Characterized in that the one corresponding to the display form of the image in the support information.

  Further, according to the present invention, an image of the client terminal in the display area of the client terminal on the display terminal is arranged and displayed in an arrangement relationship according to the local information in a space by a vertical axis and a horizontal axis. And the horizontal axis are displayed so that the parameters can be changed, and the arrangement relationship of the images of the client terminal can be changed in accordance with the change of the parameters.

  Further, according to the present invention, a date designating unit is displayed in the event group display area of the display screen of the display terminal, and the support information for the event group on the date designated by the designating unit is displayed in the client terminal display area. The display form of the image of the corresponding client terminal is set according to the above.

Further, the present invention includes a monitoring server connected to the plurality of client terminals via the communication line , and the monitoring server monitors the presence / absence of the event information from each of the client terminals and does not generate an event. Event information indicating that no event has occurred is transmitted to the event management server with respect to the client terminal that has stopped transmitting event information.

  According to the present invention, an event management server acquires event information from each client terminal (assets) in an organization such as a company and constantly monitors them, creates an event group from such event information, and a failure or abnormality is likely to occur. Or, for client terminals where this may occur, it can be displayed at any time on the display terminal, so it is possible to confirm the status of the client terminal reliably and respond immediately to abnormalities It becomes.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.
FIG. 1 is a system configuration diagram showing an embodiment of a client terminal management system according to the present invention. 1, 1A to 1C are assets, 2 is an event management server, 3 is a monitoring server, 4 is a display terminal, and 5 is a display terminal. A network 6 is a system administrator.

In the figure, an asset 1 (here, assets A to C) as a plurality of client terminals, an event management server 2, a monitoring server 3, and a display terminal 4 are connected to each other via a network 5, and the client It forms a terminal management system. The asset 1 is an asset of an organization such as a personal computer provided and used in the same organization such as one company, and here, as the asset 1, three assets 1A to 1C are used. However, the present invention is not limited to this, and any plurality of assets 1 may be used and connected to the network 5. Further, although the asset 1 is a personal computer here, it may be another information device, or may be another device such as a home appliance.

  The event management server 2 acquires event information by monitoring events (situations) such as start (power ON) or stop (power OFF), abnormality occurrence, repair, etc. of each asset 1, especially in the case of an abnormality, Create support information for this. The support information of each asset 1A-1C is provided to the display terminal 4, and this is displayed as an event screen. With this event screen, the system administrator 6 can confirm events in the assets 1A to 1C.

  The monitoring server 3 acquires the event information by monitoring the status of each of the assets 1A to 1C. When there is no response from any of the assets 1 for a certain period of time, the monitoring server 3 replaces the asset 1 with the event information. It is sent to the event management server 2.

  FIG. 2 is a block diagram showing a specific example of the event management server 2 in FIG. 1, wherein 10 is a communication unit, 11 is a CPU (central processing unit), 12 is a DB (database) unit, 13 is an event DB, 14 Is an event group DB, 15 is a support information DB, 16 is a local information DB, and 17 is a property DB.

  In the figure, the event management server 2 includes a CPU 11, a communication unit 10 that communicates with the asset 1, the monitoring server 3, and the display terminal 4 via the network 5 under the control of the CPU 11, and various information. And a DB unit 12 for storage.

  The DB unit 12 stores an event DB 13 that stores event information from the asset 1, an event group DB 14 that stores an event group that is stored in the event DB 13 and summarizes important events, and stores the event group DB 14. Support information DB 15 for storing support information created from a set of events and asset information related to the corresponding asset, an office map, a company organization chart, a network diagram of a client terminal management system as shown in FIG. It includes a local information DB 16 that stores information related to assets as local information, and a property DB 17 that stores information related to the assets A to C as property information.

  FIG. 3 is a diagram showing the flow of information processing in the DB unit 12 shown in FIG. 2, wherein 18a is an important event table, 18b is an event group table, and 19 is a support information table. The same reference numerals are assigned to the components, and duplicate descriptions are omitted.

In Figure 1, as described above, the event information from the event information and the monitoring server 3 from each asset 1A~1C are sequentially transferred to the event management server 2. In the event management server 2, in FIG. 3, event information from each of the assets 1 </ b> A to 1 </ b> C and the monitoring server 3 is received by the communication unit 10 in the order of transmission, and under the control of the CPU 11, Stored in the event DB 13.

  FIG. 4 is a diagram showing a specific example of the event DB 13, in which 13a is an event number, 13b is a reception date, 13c is an asset name, and 13d is an event type.

  In the figure, event information in the event DB 13 includes an event number 13a assigned to an event in the order of acquisition by the event management server 2, the reception date and time of the event information, and the name (asset name) 13c of the asset that transmitted the event information. And an event type 13d.

  Here, as shown in FIG. 1, No. 1 2, No, 3,. Event information is received in the order of 64, N0.65 and stored in the event DB 13. Among such event information, for example, the event number 13a is No. The event information 1 is event information from the asset 1A received at 8:30 on Monday, April 14, 2008, and the event type 13d is “ON”. The event information whose event type is “ON” represents an event in which the power is turned on (ON). The event number 13a is No. Event information 6 is event information from the asset 1A received at 17:00 on April 14, 2008 (Monday), and its event type 13d is “OFF”. The event information whose event type is “OFF” represents an event in which the power is shut off (OFF). From this, the asset 1A was turned on and operated at 8:30 on April 14, 2008 (Monday), and was turned off at 17:00.

  The event number 13a is No. 4 is event information from the asset 1A received at 16:30 on Monday, April 14, 2008, the event type 13d is “HDD abnormality”, and the event number 13a is No. Event information 5 is event information from the asset 1A received at 16:50 on Monday, April 14, 2008, and its event type 13d is “HDD automatic restoration”. For this reason, in the asset 1A, the HDD became an abnormal state at 16:50 on Monday, April 14, 2008. 4 is transmitted from this asset 1A, and the HDD is automatically repaired at 16:50 on the same day. Event information 5 is transmitted from this asset 1A. Such an event on Asset 1A also occurred on Monday, April 21, 2008. 39, no. 40 event information is transmitted from this asset 1A, and it occurs on April 28, 2008 (Monday). 61, no. 62 event information is transmitted from the asset 1A.

  Further, in this asset 1A, abnormal heat generation occurred in the CPU at 12:00, 12:02, and 12:03 on April 15, 2008 (Tuesday). 12, no. 13, no. 14 event information is transmitted from this asset 1A.

  Furthermore, in Asset 1B, a power supply abnormality occurred at 18:10 on Friday, April 18, 2008. 34 event information is transmitted from this asset 1B, but thereafter, the asset 1B is not turned on and is not operating. If this state continues for 10 days, an event “OFF 10 days” occurs in this asset 1B, and the monitoring server 3 monitoring each asset 1 has no event information from the asset 1B for 10 days. Event information of this event “OFF 10 days” is transmitted at 18:15 on Monday, April 28, 2008. Thereby, in the event DB 13, as shown in FIG. It is stored as 64 event information. For the assets 1A and 1C in which no power supply abnormality has occurred, events of power ON and power OFF have occurred on the day when they operate, and event information is sent from the assets 1A and 1C to the event management server 2 each time. (For example, event information No. 37 and No. 41 for asset 1A, and event information No. 38 and No. 42 for asset 1C).

  Returning to FIG. 3, (a) an event group is created from the event information stored in the event DB 13 using the important event table 18 a and the event group table 18 b, and stored in the event group DB 14.

  FIG. 5 shows a specific example of the important event table 18a.

  In the figure, an important event table 18a is used for selecting event information of an important event among event information stored in the event DB 13. Here, the event names are "ON", "OFF", The events of “HDD abnormality”, “HDD automatic repair”, “network abnormality”, “CPU 100% operation”, “CPU abnormal heat generation”, “power supply abnormality”, and “OFF 10 days” are set as important events. “CPU 100% operation” represents the degree of load on the CPU, and means operation at 100% of the processing capacity of the CPU. Even if it is instantaneous, a large load is applied to the CPU, so it is set as an important event.

  FIG. 6 shows a specific example of the event group table 18b.

  In the figure, an event group table 18b is an event group formed by combining related important events among the important events set in the important event table 18a shown in FIG.

  According to this event group table 18b, the event group “ON” is set for the important event “ON” in which only the power is turned on. After the power is turned on, the power is turned off with respect to the power on. In this case, the event group “normal start / end” is set by combining the important events “ON” and “OFF”. Therefore, after the power is turned on (at this time, event information of the event type “ON” is transmitted from the asset 1), the asset group “ON” is set when the asset 1 is still in operation without being turned off. After that, when the power is turned off (event information of event type “OFF” is transmitted from asset 1 at this time), the event group is changed from “ON” to “normal start / end” Is done. The acquisition date / time of the event group at this time is the acquisition date / time of the event information of the event type “OFF” whose operation has been completed after the power is turned off.

  If the important event “HDD failure” is not repaired, the event group “HDD failure” is set. However, if this is automatically repaired, the important events “HDD failure”, “automatic” The event group “HDD auto-repair completed” is set by combining “repair”. Therefore, when an HDD abnormality occurs (at this time, event information of the event type “HDD abnormality” is transmitted from the asset 1), the event group “HDD abnormality” is set while automatic repair is not performed. After that, when the HDD is automatically repaired (at this time, the event information of the event type “HDD automatic repair” is transmitted from the asset 1), the event group is changed from “HDD abnormal” to “HDD automatic repair completed”. The The acquisition date / time of the event group at this time is the acquisition date / time of the event information of the repaired event type “HDD automatic repair”.

  For the important event “network error”, the event group “network error” is set. This event occurs in the network 5 (FIG. 1), and the event information is supplied from the monitoring server 3 that also monitors the network 5.

  For the important event “CPU 100% operation”, an event group is not set unless an event of CPU 100% operation is performed for the same asset 1 a predetermined number of times (multiple times). When the information is received at the event management server 2 a plurality of times), the event group “CPU load is large” is set. The acquisition date and time of the event group at this time is the acquisition date and time of the event information of the event type “CPU 100% operation” of the CPU 100% operation OFF that was performed a plurality of times.

  For the important event “CPU abnormal heat generation”, when this heat generation occurs (at this time, event information of the event type “CPU abnormal heat generation” is transmitted from the asset 1), the event group will not be terminated unless the heat generation ends. “CPU abnormal heat generation” is set, but when the heat generation ends naturally and cools down (at this time, event information of event type “CPU cooldown” is transmitted from asset 1), the event group is “CPU abnormal heat generation” is changed to “CPU abnormal heat generation repaired”. The acquisition date and time of the event group at this time is the acquisition date and time of the cooldown event information.

  For the important event “power failure” (when a power failure occurs, event information of the event type “power failure” is transmitted from the asset 1), the event group “CPU abnormal heat generation” is set.

  For the important event “OFF 10 days” (when the power-off state continues for 10 days, event information of the event type “OFF 10 days” is transmitted from the asset 1), the event group “OFF 10 days” is set.

  7 is a diagram showing a specific example of the event group DB 14 created from the event information of the event DB 13 shown in FIG. 4 using the important event table 18a shown in FIG. 5 and the event group table 18b shown in FIG. 14a is an event group number, 14b is an acquisition date, 14c is an asset name, and 14d is an event group type.

  In the figure, the event group information in the event group DB 14 includes the event group number 14a assigned in the order of creation of the event group from the event information in the event DB 13, the acquisition date and time of the event group in the event DB 13, and the corresponding asset 1 It consists of a name (asset name) 14c and an event group type 14d.

  In the event group DB 14, for example, the event group number 14a is No. 1 is an event number No. 1 in the event DB 13 shown in FIG. Event information “Event No. 4” and event number No. The event group type is “HDD automatic repair completed” according to the event group table 18 b shown in FIG. 6. This No. The acquisition date and time of the event group 1 is the event number No. The acquisition date and time of the event type “HDD automatic restoration” of 5 is 16:50 on Monday, April 14, 2008, and the asset name is the name of the asset 1A.

  In addition, the event group number 14a is No. 2 is an event number No. 2 for the asset 1A in the event DB 13 shown in FIG. 1 event type “ON” event information and event number no. The event group type is “normal start / end” according to the event group table 18b shown in FIG. This No. The acquisition date and time of the event group 2 is the event number No. The acquisition date and time of event type “OFF” of No. 6 is 14:00 on April 14, 2008 (Monday), and the asset name is the name of asset 1A. Similarly, no. 3, No. 4 is an event number No. 4 for the asset 1B in the event DB 13 in FIG. 2 event type “ON” event information and event number no. 7 from the event type “OFF” event information, the event number No. 3 event type “ON” event information and event number no. No. 8 event type “OFF” and event information “No.” The acquisition date and time of the event group 3 is the event number No. No. 7 event type “OFF” acquisition date and time, Monday, April 14, 2008, 17:20. The acquisition date and time of the event group No. 4 is the event number no. The acquisition date and time of event type “OFF” of 8 is 18:20 on Monday, April 14, 2008.

  In addition, the event group number 14a is No. 5, no. 6, no. 7 is an event number No. 7 for the asset 1A in the event DB 13 shown in FIG. 12, no. 13, no. The event group type is created from the event information of the 14 event types “CPU abnormal heat generation”, and the event group type is one in which each abnormal heat generation has cooled down. The event group table 18b shown in FIG. , “CPU abnormal heat generation repaired”. These No. 5-No. The acquisition date and time of the event group No. 7 is the event number No. 5-No. The acquisition date and time of April 7, 2008, Tuesday, April 15, 12:00, 02 minutes, 03 minutes, and the asset name is the name of asset 1A.

  In addition, the event group number 14a is No. The event group No. 18 has an event number No. 1 for the asset 1B in the event DB 13 shown in FIG. The event group type is “power failure” according to the event group table 18b shown in FIG. 6 because it is created from the event information of the event type “power failure” 34 and has not been repaired. This No. The acquisition date and time of the event group No. 18 is the event number no. It is 18:10 on Friday, April 18, 2008, the acquisition date of 34, and the asset name is the name of asset 1B.

  In addition, the event group number 14a by not repairing the power supply is No. The event group No. 34 has an event number No. for the asset 1B in the event DB 13 shown in FIG. The event group type is created from event information of 64 event types “OFF 10 days”, and the event group type is “OFF 10 days” according to the event group table 18b shown in FIG. This No. The acquisition date and time of the event group No. 34 is the event number no. 64 acquisition date and time, Monday, April 28, 2008, 18:15, and the asset name is the name of asset 1B.

  For event groups other than the above, the event group number 14a is No. Similarly to the event group 2 event group, the event group type formed from the event type “ON” event and the event type “OFF” event is the “normal start / end” event group.

  Here, when the next power ON event information is transmitted from the asset 1A at 8:40 on April 29, 2008, in the event DB 13 shown in FIG. 66, event information having an asset name 13c of “A” and an event type 13d of “ON” is added. At the same time, in the event group DB 14 shown in FIG. 7, the asset name 14c is “A” and the event group type 14d is The event group of “ON” is the event group number No. 36, when event information indicating that the asset 1A is turned off at 17:30 on the same day is transmitted to the event DB 13 shown in FIG. 67 is added as event information No. 67, and in the event group DB 14 shown in FIG. The event group No. 66 has an event number No. whose event group type is “normal start / end”. It will be updated to 66 event groups. As described above, when new event information is transmitted from the asset 1, the event group in the event group DB 14 may be updated.

  Returning to FIG. 3, the event group created as described above is stored in the event group DB 14 or the event group is updated. Next, (b) the event group stored in the event group DB 14 Thus, the support information is created using the support information table 19, and new support information is registered in the support information DB 15 or the stored support information is updated.

  FIG. 8 is a diagram showing a specific example of the support information table 19, where 19a is an event group, 19b is a condition, 19c is support information, and 19c is a support display pattern and level.

  In the figure, a support information table 19 is used to create support information from an event group, and for each event group type shown in FIG. It consists of an event group type 19a, a condition 19b, a support information type 19c, and a display mode (support display pattern and level) 19d on the support information display terminal 4 (FIG. 1). Yes.

  For example, when the event group type 19a is “normal start / end”, if this is performed more than 1800 times as the condition 19b, “system check required” is set as the support information 19c, and the support display pattern The level 19d is “system operating status: yellow level”, but if it is performed 3000 times or more in total, “replacement target device” is set as the support information 19c (that is, it is recognized as a device requiring replacement). The support display pattern and the level 19d are “system operating status: red level”.

  When the level of the display pattern is “yellow level”, it indicates that the asset 1 is in an operating state but has been fully used, and when it is “red level” This indicates that it is time to replace the device.

  When the event group type 19a is “HDD auto-repair completed”, if the HDD abnormality and the auto-repair occur three times or more within one month as the condition 19b, “HDD attention target” is set as the support information 19c. The support display pattern and level 19d become “failure possibility: yellow level”, but if it occurs 5 times or more within one month, “HDD warning target” is set as support information 19c, and the support display pattern The level 19d becomes “failure possibility: red level”.

  It should be noted that the level of the display pattern in this case indicates that a failure is more likely to occur when the level is “red level” than “yellow level”.

  When the event group type 19a is “CPU abnormal heat repair completed”, if the CPU abnormal heat generation and its repair occur three times or more within one hour as the condition 19b, “CPU monitoring target” is set as the support information 19c. The support display pattern and the level 19d are set to “system operation status: yellow level”, but if it occurs 60 times or more within one hour, “system extension required” is set as the support information 19c, and the support display is displayed. The pattern and level 19d are “failure possibility: red level”.

  The level of the display pattern in this case also indicates that the failure is more likely to occur when the level is “red level” than “yellow level”.

  When the event group type 19a is “power failure”, when the condition 19b occurs once, “attention target” is set as the support information 19c, and the support display pattern and the level 19d are “probability of failure: If it occurs five times, “exchange target” is set as the support information 19c, and the support display pattern and level 19d become “failure possibility: red level”.

  The level of the display pattern in this case also indicates that the failure is more likely to occur when the level is “red level” than “yellow level”.

  Although the support information 19c is set in conformity with the above condition 19b and the support display pattern and the level 19d are set and displayed, the event group type 19a for which no action is taken is “warning”. In the case of “not supported”, “warning” is set as the support information 19c for all of the conditions 19b, and the support display pattern and the level 19d are “caution information: red level”.

  When the event group type 19a is “OFF 10 days”, for example, when the total number of events is 18 or more, “unused” is set as the support information 19c, and the support display pattern and level 19d are “system”. “Operating status: yellow level”, but when the total is 36, “unused” is set as the support information 19c, but the support display pattern and level 19d are “system operating status: red level”.

  FIG. 9 is a diagram showing a specific example of the support information DB 15 created from the event group stored in the event group DB 14 in FIG. 3 by using the support information table 19 shown in FIG. 15b is an acquisition date, 15c is an asset name, 15d is a support display pattern, and 15e is a level.

  In the event group DB 14 shown in FIG. 7, on Tuesday, April 5, 2008, for the asset 1A, three event group numbers “No. 5-No. 7 exists within one hour, the condition 19b of “three times within one hour” for the event group type “CPU abnormal heat repair completed” in the support information table 19 shown in FIG. Thus, based on the support information table 19, the support information number No. 1 shown in FIG. 1 support information (acquisition date 15b = Tuesday, April 5, 2008 12:03, asset name 15c = asset 1A, support display pattern 15d = system operating status, level 15e = yellow) Stored in DB15.

  As described above, the event group number No. of the event group DB 14 shown in FIG. 5-No. According to No. 7, on Tuesday, April 5, 2008, in the asset 1A, “CPU abnormal heat repair completed” occurred three times, but no response has been made to this. 9 corresponds to the condition 19b of “all” with respect to the event group type “warning not supported” in the support information table 19 shown in FIG. 8, and based on the support information table 19, the support shown in FIG. Information No. 2 support information (acquisition date and time 15b = April 5, 2008 (Tue) 12:03, asset name 15c = asset 1A, support display pattern 15d = careful information, level 15e = red) Stored in DB15.

  As described above, the event group number No. of the event group DB 14 shown in FIG. 18, the first “power failure” has occurred in the asset 1B on Friday, April 18, 2008. This is because the event group type “in the support information table 19 shown in FIG. This corresponds to the condition 19b of “once occurrence” for “power failure”. Accordingly, based on the support information table 19, the support information number No. 1 shown in FIG. 3 support information (acquisition date and time 15b = Friday 18 April 2008 18:10, asset name 15c = asset 1B, support display pattern 15d = system operating status, level 15e = yellow) Stored in DB15. In this case as well, since no countermeasure is taken against the power supply abnormality, it corresponds to the condition 19b of “all” for the event group type “warning not supported” in the support information table 19 shown in FIG. As shown in FIG. 4 support information (acquisition date and time 15b = Friday 18 April 2008 18:10, asset name 15c = asset 1B, support display pattern 15d = careful information, level 15e = red) Stored in DB15.

  As described above, the event group number No. of the event group DB 14 shown in FIG. 1 and no. 21, “HDD automatic repair” occurred in the asset 1A on April 14, 2008 (Monday) and April 21, 2008 (Monday). This is the support information table shown in FIG. Assuming that the condition 19b of “at least three times within one month” for the event group type “HDD auto-repaired” at 19 is met, this is shown in FIG. 9 based on the support information table 19. Support information No. 5 support information (acquisition date and time 15b = Monday, April 21, 2008 17:30, asset name 15c = asset 1A, support display pattern 15d = probability of failure, level 15e = yellow) Stored in DB15.

  As described above, the event group number No. of the event group DB 14 shown in FIG. 1, No. 1 21 and no. 32, “Automatic HDD restoration” occurred in Asset 1A on April 14, 2008 (Monday), April 21, 2008 (Monday), and April 28, 2008 (Monday). If this corresponds to the condition 19b of “three or more times within one month” for the event group type “HDD automatic repair completed” in the support information table 19 shown in FIG. Based on the support information number No. shown in FIG. 6 support information (acquisition date 15b = Monday, April 28, 2008 17:10, asset name 15c = asset 1A, support display pattern 15d = probability of failure, level 15e = yellow) Stored in DB15.

  Here, as described above, when the event group is updated in the event group DB 14 shown in FIG. 7 and new support information is created, the new support information is added to the support information DB 15.

  Returning to FIG. 3, (c) When the support information newly stored in the support information DB 15 is stored or the stored support information is updated as described above, the support information DB 15 is then updated. Based on the above, new support information is registered or updated in the property DB 17.

FIG. 10 is a diagram showing a specific example of the property DB 17 in FIG. 3, in which 17a is an asset name, 17b is system information, and 17c is support information.

  In the figure, property information (attribute information) is set for each asset 1 in the property DB 17. The property information includes a name 17a of the asset 1, system information 17b indicating the attribute of the asset 1, and support information 17c related to the asset 1.

  The system information 17b includes a device name (type of device such as a personal computer), model name, physical location (affiliated department or installation location), IP address, user, OS version, management period, power supply status, CPU operating rate, network usage rate. It consists of such.

  The support information 17c is support information corresponding to the asset 1 stored in the support information DB 15. For example, in the property information of the asset 1A, three pieces of support information “system operation status: yellow level”, “failure possibility: yellow level”, and “caution information: red level” are supported by the support information DB 15 shown in FIG. In the property information of the asset 1B, two pieces of support information “system operating status: yellow level” and “caution information: red level” are set by the support information DB 15 shown in FIG. .

FIG. 11 is a diagram showing a specific example of the local information DB 16 in FIG. 3, in which 16a is a local information name and 16b is a content.

  In the figure, local information is information relating to the location of the asset 1, and such information is stored in the local information DB 16. The local information DB 16 includes a local information name 16a indicating its type and a content 16b indicating its specific contents.

As the local information, here, an office map 16a ₁ for representing the physical installation location of each asset 1 as a map, a company organization chart 16a ₂ for representing the department where each asset 1 is installed, There is a network unit 16a ₃ for indicating the relevance on the network. When the location of each asset 1 is shown based on the system information 17b in the property DB 17 shown in FIG. 10, the asset 1A is arranged on the first floor of the main building in the office map 16a ₁ and the business organization chart 16a ₂ Arranged in part. Further, the asset 1B is arranged on the second floor of the main building in the office map 16a _{1 and} is arranged in the second sales department in the company organization chart 16a ₂ . Further, the asset 1C is arranged on the second floor of the main building in the office map 16a _{1 and} is arranged in the planning department in the company organization chart 16a ₂ .

  Such local information is input by a terminal operation by an operator or input by an image reading device or the like.

  FIG. 12 is a flowchart showing an event processing operation of the event management server 2 in FIG.

  In the figure, when the event management server 2 starts event monitoring (step S100), it waits until an event occurs in the asset 1 and event information can be acquired ("No" in step S101). When an event occurs in the asset 1 and event information is acquired (“Yes” in step S101), this is stored in the event DB 13 (FIGS. 2 and 3) as shown in FIG. Is determined to be an important event on the basis of the important event table 18a (FIG. 5) (“Yes” in step S102), and further to be an event group based on the event group table 18b (FIG. 6). If determined (“Yes” in step S103), an event group is created and registered in the event group DB 14 (step S105: FIG. 7). In addition, event information that is not determined to be at least an important event or not determined to be an event group remains stored in the event DB 13 (step S104), and waits until the next event information is acquired (step S100). , S101).

  It is determined whether or not the event group registered in the event group DB 14 meets the conditions in the support information table 19 (FIG. 8). If not matched (“No” in step S106), the next event information 9 is registered (step S100, S101), but the matching information is registered in the support information DB 15 as support information as shown in FIG. 9 (step S107). Then, this support information is registered in the property DB 17 in association with the corresponding asset 1 (step S108). And it waits until the next event information is acquired (step S100, S101).

  FIG. 13 is a flowchart showing the information provision processing operation to the display terminal 4 of the event management server 2 in FIG.

  In this figure, when the display operation by the system administrator 6 from the display terminal 4 in FIG. 1 is accepted (step S300), the event management server 2 reads all the property information from the property DB 17 and all the information from the local information DB 16 The local information is read, all event groups are read from the event group DB 14, and all of these are transmitted to the display terminal 4 (step S301). Thereby, on the display terminal 4, the screen using these information is displayed (step S302).

  In such a screen display state, the CPU 11 (FIG. 2) of the event management server 2 monitors property information, local information, and an event group. If there is a change (increase or change) in the event group (“Yes” in step S305). "), The changed event group is transmitted to the display terminal 4 (step S306). In the display terminal 4, the event group acquired from the event management server 2 is changed. When an event group requiring change is used on the screen displayed at this time, the change is performed on the screen. .

  When the property information is changed (increased or changed) due to the change of the event group (“Yes” in step S303), the event management server 2 transmits the changed property information to the display terminal 4 (step S303). S306). In the display terminal 4, the property information acquired from the event management server 2 is changed. When property information that needs to be changed is used on the screen displayed at this time, the change is performed on the screen. .

  Further, when there is a change in local information (such as increase / decrease of asset 1 or change in arrangement), the event management server 2 transmits the changed local information to the display terminal 4 (step S306). The display terminal 4 performs processing for changing the local information acquired from the event management server 2, and when the local information that needs to be changed is used on the screen displayed at this time, the change is performed on the screen. .

  If there is no change in any of the event group, property information, and local information, the process flow of step S302 → step S303 → step S304 → step S305 → step S302 is repeated, and the process waits until the information is changed. . In step 302, the screen is switched by the operation of the display terminal 4 by the system administrator 6.

  Note that some of the screens displayed on the display terminal 4 also display event information, as will be described later. When such a screen is displayed, the display terminal 4 displays the event DB (see FIG. 2, necessary event information is acquired from FIG.

  Next, a specific example of the integrated asset management screen (hereinafter referred to as an event screen) displayed on the display terminal 4 in FIG. 1 based on the processing shown in FIG. 13 will be described.

  FIG. 14 is a diagram showing a specific example of a standard screen of event screens. TA is a “chart display” tab, TB is a “physical location display” tab, TC is an “internal organization chart display” tab, and TD is "Network diagram display" tab, 1a to 1c, 2a, 3a, 4a are icons (images), 20 is a chart screen, 21 is an asset display area, 21X is an X-axis item display area, 21Y is a Y-axis item display area, 22X Is an X-axis menu selection unit, 22Y is a Y-axis menu selection unit, 23X and 23Y are pull-down buttons, 24 is an event detail display area, 24a is a date, 24b to 24e are event detail information, 25 is a daily event group display area, 25a is a calendar, 25b is an event group mark, 25c is a day designation frame, 25d is an event group type display selection section, 25e is a pull-down button, and 26 is Supported by information type selection area, 26a is a pull-down button, 26b assistance mark, 27 balloon, 28 is a power supply OFF mark.

  When the system administrator 6 performs a power ON operation on the display terminal 4 in FIG. 1, a chart screen 20 which is a standard screen among the event screens shown in FIG. 14 is displayed.

  In this chart screen 20, an asset display area 21 that displays the arrangement of assets 1 as a client terminal, an event detail display area 24 on the right side, and a daily event group display area 25 on the lower side of the asset display area 21, respectively. The support information type display selection area 26 is set at the upper right of the daily event group display area 25, and the "chart display" tab TA, "physical location display" tab TB, and "internal organization chart display" tab A TC and a “network diagram display” tab TD are provided, and when any of these tabs is selected, a screen corresponding to the selected tab is displayed. Here, the chart screen 20 as the standard screen is a screen in a state where the “chart display” tab TA is selected, and a chart (graph) relating to assets is displayed in the asset display area 21. When one of the “physical location display” tab TB, the “internal organization chart display” tab TC, and the “network diagram display” tab TD is selected, information corresponding to the selected tab is displayed in the asset display area 21. .

In this chart screen 20, the asset display area 21 captures and displays the local information “network diagram” 16 a ₃ stored in the local information DB 16 shown in FIG. 11 in the coordinate space represented by the X and Y axes. Is done. Here, for the assets 1A to 1C, the display terminal 4, the event management server 2 and the monitoring server 3, the icons 1a to 1c, 4a, 2a and 3a representing those images are X axis items for the X axis. The Y-axis is arranged and displayed at a position corresponding to each item in the display area 21X and at a position corresponding to each item in the Y-axis item display area 21Y. The item type in the X-axis item display area 21X can be selected by the X-axis menu selection unit 22X, and the item type in the Y-axis item display area 21Y can be selected by the Y-axis menu selection unit 22Y.

  Here, assuming that the type (menu) “department” is selected in the X-axis menu selection unit 22X, in the X-axis item display area 21X, “sales part”, “sales part 2”, “planning part”. , “General Affairs Department” items corresponding to this menu are arranged in that order along the X axis, and the icon 1a of the asset 1A is an X axis item based on the property information in the property DB 17 shown in FIG. The icon 1b of the asset 1B is displayed in the position of the item "Sales 2" on the X-axis, the icon 1c of the asset 1C is displayed in the position of the item "Planning Department" on the X-axis. Although not shown so far, if the display terminal 4 belongs to the General Affairs Department, the icon 4a of the display terminal 4 is displayed at the position of the item “General Affairs Department” on the X axis.

  If the type (menu) “system diagram” is selected in the Y-axis menu selection unit 22Y, the system hierarchy is displayed in the Y-axis item display area 21Y. An icon is displayed on the upper side in the direction. Here, since the assets 1A to 1C and the assets of the display terminal 4 are in the same level in the lower level of the event management server 2, the icons 1a to 1c and 4a of these assets 1A to 1C and the display terminal 4 are used. Are arranged at the same hierarchical position with respect to the Y axis, and the icon 2a of the event management server 2 having a higher hierarchy is displayed above these icons 1a to 1c, 4a. Since the monitoring server 3 monitors the assets 1A to 1C, the icon 3a is displayed on the upper side of the icons 1a to 1c and 4a with the hierarchy higher than these.

  Each icon also displays the attributes of the corresponding asset 1A to 1C, the display terminal 4, and the servers 2 and 3, such as the name, so that the device can be directly identified from the icon.

  The X-axis menu selection section 22X is provided with a pull-down button 23X. When the pull-down button 23X is touched, a chart X-axis pull-down menu 30 shown in FIG. 15A is displayed. "," Department "," Purchase Year "," Trouble Frequency "," CPU Spec ", and" Memory Size "are set. Then, by selecting one of them, the selected menu item is displayed in the X-axis item display area 21X, and the arrangement of the icons 1a to 1c and 4a in the X-axis direction is set accordingly. become.

  Similarly, the Y-axis menu selection unit 22Y is also provided with a pull-down button 23Y. When the pull-down button 23Y is touched, a chart Y-axis pull-down menu 31 shown in FIG. 15B is displayed. Menu items such as “system diagram”, “department”, “purchase year”, “trouble frequency”, “CPU spec”, and “memory size” are set. Then, by selecting one of them, the selected menu item is displayed in the Y-axis item display area 21Y, and the arrangement of the icons 1a to 1c and 4a in the Y-axis direction is set accordingly. become.

  In the daily event group display area 25, a calendar 25a in which daily dates are arranged in the horizontal direction is displayed. On the day when the event group exists, the event group exists below the corresponding day of the calendar 25a. An event group mark 25b indicating this is displayed. When there are a plurality of event groups on the same day, the event group marks 25a for each are arranged and displayed in the vertical direction. For example, since there are six event groups on April 15, according to FIG. 7, six event group marks 25b are displayed, and on April 22, there are two event groups. Two event group marks 25b are displayed. Further, since there are no event groups on April 19th and 20th, the event mark 25b is not displayed.

  Any one of the dates displayed on the calendar 25a is designated by the date designation frame 25c, and the details of the event corresponding to the event mark 25b of the date designated by the designation frame 25c are displayed from this designated date. The event is displayed in the event detail display area 24 with the balloon 27. Here, it is assumed that April 28 is designated in the daily event group display area 25, and this date 24 a is displayed in the event detail display area 24 and the date in the daily event group display area 25 is displayed. Event groups in the event group DB 14 shown in FIG. 7 corresponding to the four event group marks 25b on April 28 designated by the designation frame 25c are displayed as event detailed information 24b, 24c, 24d, 24e. .

  One of the event detailed information, that is, the event detailed information 24b is an event group of the event type group “HDD automatic repair completed” of the asset 1A at 17:10 on April 28, 2008. : 10 HDD auto-repair completed "is displayed, and the event number in the event DB 13 shown in FIG. 61 and No. 62 events are fetched and displayed as “16:50 HDD error” and “17:10 HDD auto-repair”, respectively.

  Therefore, in the daily event group display area 25, if any date on which the event group mark 25b exists in the calendar 25a is specified by operating the date specification frame 25c, a balloon 27 from the specified date is displayed. The event details are displayed in the event details display area 24, whereby event details information for each event group mark 25b existing on the specified date is displayed in the event details display area 24.

  The daily event group display area 25 is provided with an event group type selection unit 25d, which displays the type of the selected event group. Here, the type of the selected event is “display all”, and in this case, the event group mark 25b displayed for each corresponding day in the daily event group display area 25 relates to the event group of all types. It is what is displayed. Therefore, in this case, on April 28, 2008, there is an event group with the event types “HDD automatic repair completed” and “normal start / end” for the asset 1A as shown in FIG. In the daily event group display area 25, the event group mark 25b of these event groups is set on April 28, 2008, and in the event detailed information area 24, the event types are “HDD automatic repair completed” and “normal” Detailed event information 24b and 24c for each event group “start / end” is displayed.

  Note that the other two event group marks 25b on April 28, 2008, the event group of the asset 1B whose event group type is “OFF 10 days” and the event group type “normal start” are clear from FIG. -For the event group of the asset 1C of "End".

  The event group type selection unit 25d is provided with a pull-down button 25e. When the pull-down button 25e is touched, an event group display pull-down menu 32 shown in FIG. 15C is displayed. “Display”, “Display for each asset”, “ON”, “Normal start / end”, “HDD failure”, “HDD auto-repair completed”, “Network error”, “CPU load high”, “CPU abnormal heat generation”, The event group type menus such as “CPU abnormal heat repair completed”, “Power supply abnormality”, “OFF 10 days”, “Warning not supported” are set, and by selecting one of these, the selected type is selected. Is displayed on the event group type selection unit 25d, and the event group type arranged on each day of the calendar 25a is changed accordingly, and the event corresponding to this is changed. So that the door group mark 25b is set.

  Although not shown in the pull-down menu 32, when the type “display for each asset” is selected, a pull-down menu for selecting an asset is displayed. When a predetermined asset is selected, this selection is made. “ON”, “normal start / end”, “HDD failure”, “HDD auto-repair completed”, “network error”, “CPU load high”, “CPU abnormal heat generation”, “CPU abnormal heat recovery” A pull-down menu for selecting one or all of “completed”, “power failure”, “OFF 10 days”, and “no warning” is displayed.

  Accordingly, in the pull-down menu 32, it is selected to display all types for all assets 1, or “ON”, “normal start / end”, “HDD failure”, “HDD automatic repair completed”, “ Any one of “Network error”, “CPU load high”, “CPU abnormal heat generation”, “CPU abnormal heat generation repair completed”, “Power supply abnormality”, “OFF 10 days”, “Warning not supported” can be selected. At the same time, the selected asset 1 is also selected to display all types, or “ON”, “normal start / end”, “HDD failure”, “HDD auto-repair completed”, “network error” , “High CPU load”, “CPU abnormal heat generation”, “CPU abnormal heat generation repaired”, “Power supply abnormality”, “OFF 10 days”, “Warning not supported” can be selected.

  The support information type display selection area 26 is used to select support information stored in the support information DB 15 shown in FIG. 9, and is selected from among the assets 1 whose icons are displayed in the asset display area 21. The fact that the selected support information is related to the asset 1 corresponding to the supported support information is displayed. Here, support information “probability of failure” is selected in the support information type display selection area 26, and a double ring-shaped support mark 26b is displayed.

  Asset 1 corresponding to the support information selected in the support information type display selection area 26 among the assets 1 displayed in the asset display area 21 on the date specified by the date specification frame 25c in the daily event group display area 25. Is present, the support mark 26b displayed in the support information type display selection area 26 is attached to the asset 1. Here, the support information selected in the support information type display selection area 26 is “probability of failure”, and support information of this “probability of failure” on April 28, 2008 specified by this date specification frame 25c. Since the asset 1 related to is the asset 1A according to the support information DB 15 shown in FIG. 9, the support mark 26b is attached to the icon 1a of the asset 1A displayed in the asset display area 21. The fact that the support mark 26b is attached is hereinafter referred to as an alert (warning) display.

  The support information type display selection area 26 is provided with a pull-down button 26a. When the pull-down button 26a is touched, a support display pull-down menu 33 shown in FIG. 15D is displayed. The support information pattern 19 in the support information table 19 shown in FIG. 8 and the support information DB shown in FIG. 9 such as “No”, “Possibility of failure”, “Caution required information”, “System operation status” are set. By selecting one of them, the selected support information is displayed in the support information type display selection area 26. In response to this, the icon of the corresponding asset 1 is attached with a support mark 26b and displayed as an alert. It will be.

  Note that the support information selected in the support information type display selection area 26 is set in an event group at risk of failure based on the support information table as shown in FIG. A yellow level is set for the event group determined to be at risk of failure according to the information table, together with the support display pattern, and a red level is set when this risk level is higher. In FIG. 14, the support mark 26 b is added to the asset 1, which means that this asset 1 is supported in the support information type (that is, the support pattern 19 d in FIG. 8) displayed in the support information type display selection area 26. This means that the information is set, and therefore the level of the support information (yellow or red level in FIG. 8) is set for the asset 1.

  Therefore, like the asset 1A in FIG. 14, the asset 1 that is added with the support mark 26b and displayed as an alert is colored with an icon (yellow or red) according to the level set in the support information. indicate. This makes it possible to more clearly identify the asset 1 that is at risk of failure.

  Note that the asset 1 that is not used on the date specified by the date specification frame 25c and is not turned on is displayed as being in a power-off state. Here, since the asset 1B is in that state, a power OFF mark 28 with a cross is attached to the icon 1b. The addition of the power OFF mark 28 in this way is hereinafter referred to as a power OFF display.

  FIG. 16 is a diagram showing a chart screen when the menu “trouble frequency” in the pull-down menu 30 (FIG. 15A) is changed by operating the X-axis menu selection unit 22X of the chart screen 20 shown in FIG. Reference numeral 20a denotes a chart screen, and parts corresponding to those in FIG.

  When the X-axis menu selection unit 22X of the chart screen 20 shown in FIG. 14 is operated to pull down the pull-down menu 30 (FIG. 15A) and the menu “trouble frequency” is selected, the chart screen 20a shown in FIG. Become.

  In the chart screen 20a, the selected menu “trouble frequency” is displayed in the X-axis menu selection unit 22X, and an item (numerical value) indicating the trouble frequency from 0% to 100% is displayed in the X-axis item display area 21X. Is displayed. Accordingly, since the contents (item types) of the Y-axis item display area 21Y are not changed, the icons 1a to 1c, 4a, 2a, and 3a of the assets 1A to 1C, the display terminal 4, and the servers 2 and 3 are The position in the X-axis direction is changed according to the trouble frequency and displayed at a position according to the trouble frequency.

  FIG. 17 is a diagram showing a chart screen when the menu “purchase year” in the pull-down menu 31 (FIG. 15B) is changed by operating the Y-axis menu selection unit 22Y of the chart screen 20a shown in FIG. Reference numeral 20b denotes a chart screen, and parts corresponding to those in FIG.

  When the Y-axis menu selection unit 22Y of the chart screen 20a shown in FIG. 16 is operated to pull down the pull-down menu 31 (FIG. 15B) and the menu “Purchase Year” is selected, the chart screen 20b shown in FIG. Become.

  In this chart screen 20b, the selected menu “Purchase Year” is displayed in the Y-axis menu selection unit 22Y, and at the same time, an item (for example, a year from 2000 to 2008) is displayed in the Y-axis item display area 21Y. Numeric value) is displayed. Accordingly, the contents (item type) of the X-axis item display area 21X are not changed and remain “trouble frequency”, so that the icons 1a to 1c of the assets 1A to 1C, the display terminal 4, and the servers 2 and 3 are displayed. , 4a, 2a, and 3a are displayed in positions corresponding to the purchase year, with the position in the Y-axis direction being changed according to the purchase year.

  In this manner, on the chart screen 20, the asset 1 and the display terminal 4, by appropriately selecting the menu of the X axis and the Y axis by operating the X axis menu selection unit 22X and the Y axis menu selection unit 22Y. The relationship between the servers 2 and 3 can be displayed in a form corresponding to the selected menu, the asset 1 can be managed in a form suitable for the system administrator 6, and each asset 1 for each day can be managed. It is also possible to manage all types of events, manage events of a specified type, and manage events for each asset by operating the event type selection unit 25d.

  When a “physical location display” tab TB is selected on the chart screen 20, a physical location display screen is displayed on the display terminal 4.

  FIG. 18 is a diagram showing a specific example of the physical location display screen. Reference numeral 40A denotes a physical location display screen. Parts corresponding to those in the previous drawings are denoted by the same reference numerals, and redundant description is omitted.

In the figure, in the physical location display screen 40A, the local information “office map” 16a ₁ read from the local information DB 16 is displayed in the asset display area 21, and the icons 1a to 1c of the assets 1A to 1C are displayed in the property DB 17 (FIG. Based on the property information of each asset 1 shown in FIG. 10 stored in 2), it is displayed at the corresponding installation position in the “office map” 16a ₁ .

  Similarly, for the display terminal 4, the event management server 2, and the monitoring server 3, the icons 4a, 2a, and 3a are displayed at the corresponding installation positions based on the property information in the property DB 17.

  The rest of the configuration is the same as the chart screen 20 shown in FIG.

  On this physical location display screen 40A, the actual installation location of each asset 1 can be confirmed. Based on this confirmation, the event of each asset is managed in the same manner as in the chart screen 20. Can do.

  When the “company organization chart display” tab TC is selected on the chart screen 20 shown in FIGS. 14, 16, and 17 or the physical location display screen 40 A shown in FIG. 18, the company organization chart display screen is displayed on the display terminal 4. .

  FIG. 19 is a diagram showing a specific example of a company organization chart display screen. 40B is a company organization chart display screen. Parts corresponding to the previous drawings are given the same reference numerals and redundant description is omitted.

In the figure, in the company organization chart display screen 40B, the local information “company organization chart” 16a ₂ read from the local information DB 16 is displayed in the asset display area 21, and the icons 1a to 1c of the respective assets 1A to 1C are displayed in the property DB 17. Based on the property information of each asset 1 shown in FIG. 10 stored in (FIG. 2), it is displayed in the corresponding department in the “company organization chart” 16a ₂ .

  Similarly, for the display terminal 4, the event management server 2, and the monitoring server 3, the icons 4a, 2a, and 3a are displayed in the department to which these belong, based on the property information in the property DB 17.

  The rest of the configuration is the same as the chart screen 20 shown in FIG.

  In this company organization chart display screen 40B, the department to which each asset 1 actually belongs can be confirmed. Based on this confirmation, the event of each asset is managed in the same manner as in the chart screen 20. can do.

  When the “network diagram display” tab TD is selected on the chart screen 20 shown in FIG. 14, FIG. 16, FIG. 17, the physical location display screen 40A shown in FIG. 18, or the company organization chart display screen 40B shown in FIG. A screen is displayed on the display terminal 4.

  FIG. 20 is a diagram showing a specific example of the network diagram display screen. Reference numeral 40C denotes the network diagram display screen, and portions corresponding to the previous drawings are denoted by the same reference numerals, and redundant description is omitted.

In the figure, on the network diagram display screen 40C, the local information “network diagram” 16a ₃ read from the local information DB 16 shown in FIG. 11 is displayed in the asset display area 21, and the icons 1a of the assets 1A to 1C are displayed in this network diagram. ~ 1c is displayed.

  The icons 4a, 2a, and 3a are also displayed for the display terminal 4, the event management server 2, and the monitoring server 3.

  The rest of the configuration is the same as the chart screen 20 shown in FIG.

  In this network diagram display screen 40C, the relationship between each asset 1, the display terminal 4, and the servers 2 and 3 can be confirmed. Based on this confirmation, the event of each asset is displayed on the chart screen 20. It can be managed as in the case.

  In the chart screen 20 shown in FIG. 14, details of the event of the asset 1 (in this case, the asset 1 </ b> A) displayed with the support mark 26 b attached to the icon and turned off and colored in yellow or red are displayed in the event group type. By operating the selection unit 25d to display the pull-down menu 32 (15 (c)) and designating the asset 1A from the pull-down menu 32, it can be easily and reliably acquired. . This is the same for the chart screen 20a shown in FIG. 16 and the chart screen 20b shown in FIG. 17, but the following description will be made using the chart screen shown in FIG.

  In the chart screen 20 shown in FIG. 14, when the event group type selection unit 25d is operated to display the pull-down menu 32 (FIG. 15C) and the type “display for each asset” is selected, the asset is not shown. 1 is displayed, and when an asset 1A is selected from the selection menu, a chart screen 20c shown in FIG. Here, in FIG. 21, reference numeral 50 denotes a selection display mark, and parts corresponding to those in FIG.

  In this chart screen 20c, “display of asset 1A” is displayed as the type of the selected event group in the event group type selection unit 25d, and displayed together with the calendar 25a in the daily event group display area 25. All the event group marks 25b to be performed are related to the asset 1A. Therefore, the event detail information displayed in the event detail display area 24 on the date specified in the date specification frame 25c (in this case, April 28, 2008) is only the event detail information 24b and 24c related to the asset 1A. Become.

  At this time, since only the asset 1A is selected, a selection display mark 50 including, for example, square brackets at the four corners shown in the figure is displayed on the icon 1a of the asset 1A. This makes it possible to clearly confirm that the current day event group display area 25 is used only for the event group related to the asset 1A.

  By the way, looking at the daily event group display area 25 on the chart screen 20c, except April 15, every week, April 14, April 21, April 28, and every Monday. There are two event group marks 25c and peaks in the number thereof. To confirm this peak, the date designation frame 25c in the daily event group display area 25 is moved to the position of the previous peak. Then, a chart screen 20d shown in FIG. 22 is displayed. However, in FIG. 22, 51 is a designation display mark, 52 is a progress information display field, 53 is a related information display field, and parts corresponding to those in FIG.

  In this figure, on this chart screen 20d, the date designation frame 25c is in a designated state of April 21 with two event group marks 25b, and any one of these event group marks 25b is a support information type display selection section. If the event group corresponds to the type of support information “probability of failure” displayed in 26, a designation display mark 51 surrounding the event group mark 25c of the event group is displayed. The designation display mark 51 indicates that the event group corresponding to the event group mark 25c designated by this is an event group corresponding to the type of support information displayed on the support information type display selection unit 26. is there.

  At this time as well, a balloon 27 is displayed in the event detail display area 24 from the designated April 21st, and the April 21 event group mark 25c designated by the designation display mark 51 in the event detail display area 24. Detailed event information 24b and 24c for is displayed. Further, if the event detail information 24b of one “17:30 HDD auto-repaired” relates to the event group corresponding to the type of support information displayed on the support information type display selection unit 26, it is acquired from the event management server 2. An event group corresponding to the type of support information displayed on the support information type display selection unit 26 is extracted from the event group, and is displayed as related information in the related item column 53. Here, among the event information transmitted from the asset 1, in particular, in the case of event information related to an abnormality such as “HDD abnormality” of the asset 1, progress information until an abnormality occurs in the event information related to this abnormality Is included from the corresponding event information stored in the event DB 13 (FIG. 2) of the event management server 2 until it becomes “HDD abnormality” at 17:20. Displayed in the column 52 as progress information.

  The system administrator 6 (FIG. 1) determines that the event “HDD auto-repaired” corresponds to the type of support information displayed on the support information type display selection unit 26 from the information of the progress information 52 and the related item 53. Based on this, for example, by hearing with the user of this asset 1A, for example, a hard disk backup is performed weekly on the asset 1A, and a hard disk is used for that load. Error occurred, but the user can know that the error was not noticed by setting automatic termination after work, and this can be dealt with by adding memory, etc. It becomes possible.

  The progress information column 52 and the related information column 53 are respectively provided with scroll bars 52a and 53a. When long information is displayed, the progress information and the related information are scrolled by operating these. Can be displayed as a whole.

  In this way, even if the user of the asset 1 is not aware of the failure, the system administrator can recognize that the failure is likely to occur, thereby dealing with the situation before the failure occurs and the user cannot use it. It becomes possible.

  In the chart screen 20 shown in FIG. 14, when the system administrator 6 notices that the asset 1B has not been turned on recently and checks the usage status of the asset 1B, it operates the event group type selection unit 25d. When the pull-down menu 32 (FIG. 15C) is displayed, the type “display for each asset” is selected, and the asset 1B and the type “normal start / end” are selected, the chart screen 20e shown in FIG. Is displayed on the display terminal 4. Here, in FIG. 23, 24f is the detailed event information, and the same reference numerals are given to the portions corresponding to the previous drawings, and redundant description is omitted.

  In this chart screen 20e, “normal start / end” is displayed as the type of the selected event group in the event group type selection unit 25d, and at the same time, a selection instruction mark 50 is displayed on the icon 1b of the asset 1B. Thereby, it is indicated that the event group mark 25b displayed in the daily event group display area 25 relates to the event group of the event group type “normal start / end” in the asset 1B.

  If the support mark 26b is attached to an asset 1 other than the asset 1B (in this case, the asset 1A) and the power is turned off, and this is an obstacle, the support information display selection area 26 is operated to display the support mark 26b. The support information type “not displayed” shown in FIG. 15 (d) may be specified (in this case, “not displayed” is displayed in the support information type display selection unit 26), and is displayed on the asset 1A. The support mark 26b is deleted and the power OFF display is released.

  In the daily event group display area 25, the event group mark 25b of the event group whose type for each day of the asset 1B is “normal start / end” is displayed. Event mark 25b of the event group "" is not displayed, and no event group mark 25b is displayed on the last date designated by the date designation frame 25c as a default, that is, on April 28. Therefore, in the event detail display area 24 represented by the balloon 27, only the event group information 24f of the date 24a and “none” is displayed.

  Therefore, when the date designation frame 25c is moved and this date is designated in accordance with April 18 when the event group mark 25b is finally displayed, a chart screen 20f shown in FIG. 24 is displayed on the display terminal 4. In FIG. 24, 24g and 24h are event group detailed information, and the same reference numerals are given to the portions corresponding to the previous drawings, and redundant description is omitted.

  In this chart screen 20f, the date designation frame 25c is in a state of designating April 18 with two event group marks 25b, and any one of these event group marks 25b is displayed on the support information type display selection unit 26. If the event group corresponds to the type of support information “normal start / end”, a designation display mark 51 surrounding the event group mark 25c of the event group is displayed. The designation display mark 51 indicates that the event group corresponding to the event group mark 25c designated by this is an event group corresponding to the type of support information displayed on the support information type display selection unit 26. is there.

  Also at this time, a balloon 27 is displayed in the event details display area 24 from April 18 that is designated, and the event group mark 25c of April 18 designated by the designation display mark 51 in the event details display area 24. Detailed event information 24g and 24h for is displayed. Further, the event detailed information 24g of one of “18:10 power failure” relates to the event group corresponding to the type of support information displayed on the support information type display selection unit 26, and the event acquired from the event management server 2 An event group corresponding to the type of support information displayed in the support information type display selection unit 26 is extracted from the group, and this is displayed as related information in the related item column 53, but here there is no such related information. , The message “No corresponding data” is displayed. Here, among the event information transmitted from the asset 1, in particular, in the case of event information related to an abnormality such as “power supply abnormality” of the asset 1, progress information until an abnormality occurs in the event information related to this abnormality Is acquired from the corresponding event information stored in the event DB 13 (FIG. 2) of the event management server 2 until it becomes “power failure” at 18:10, and this is acquired as the progress information. For example, it is displayed in the column 52 as progress information “18:10 Power supply abnormality warning occurred”.

  The system administrator 6 (FIG. 1) sets the asset “abnormal start / end” corresponding to the type of support information displayed on the support information type display selection unit 26 from the information of the progress information 52 and the related item 53. The event of 1B can be confirmed, and based on this, for example, it is possible to directly confirm the state of the asset 1B and take measures such as replacing the power supply unit.

  In this way, even if the user of the asset 2 has left a failure of the power supply, the system administrator can recognize it, and thus it is possible to take measures such as replacing the power supply unit. Become.

  In the chart screen 20 shown in FIG. 14, since the support mark 26b is set to the icon 1a of the asset 1A and the power is turned off, the system administrator 6 checks the details of the event group type selection unit 25d. To display the pull-down menu 32 (FIG. 15C) and select the type “warning not supported”, the chart screen 20g shown in FIG. Here, in FIG. 25, 24i is the detailed event information, and the same reference numerals are given to the portions corresponding to the previous drawings, and the overlapping description is omitted.

  In this chart screen 20g, “alarm unsupported” is displayed as the type of the selected event group in the event group type selection unit 25d, and at the same time, all the assets 1 are displayed in the daily event group display area 25. The event group mark 25b related to the event group of the event group type “Warning not supported” is displayed. Here, three event group marks 25b are displayed on April 15 and one event group mark 25b is displayed on April 18. Accordingly, there is no event group mark 25b on April 28, and the event group detailed information 24i of the message “none” is displayed in the event detail display area 24 by the balloon 27 from April 28 set as a default. Is displayed.

  Accordingly, when the date designation frame 25c is moved and this date is designated in accordance with April 15 on which the three event group marks 25b are displayed, the chart screen 20h shown in FIG. The In FIG. 26, 24j to 24l are event group detailed information, 54 is a display by time, and the same reference numerals are given to the portions corresponding to the previous drawings, and redundant description is omitted.

  In this chart screen 20h, the date designation frame 25c is in a state of designating April 15 with three event group marks 25b, and any one of these event group marks 25b is displayed on the support information type display selection unit 26. In the event group corresponding to the type of support information “warning unsupported”, a designation display mark 51 surrounding the event group mark 25c of the event group is displayed. In addition, since April 15 is before April 18 when the power failure occurs in the asset 1B, the unused mark 28 is not attached to the asset 1B, and the power OFF display is not performed.

  At this time as well, a balloon 27 is displayed in the event detail display area 24 from the designated April 15th, and the three events on April 15 designated by the designation display mark 51 in the event detail display area 24 are displayed. Detailed event information 24j, 24k, 24l for the group mark 25c is displayed.

  In the event group of the type “warning not supported” for the event group mark 25b indicated by the designation display mark 51, the number of the asset 1A in FIG. 5-No. In each event detailed information 24j, 24k, 24l, “12:00 CPU abnormal heat generation repaired”, “12:03 CPU abnormal heat generation repair completed”, “12:02 CPU abnormal heat generation repaired” "Completed" is displayed, along with progress information of "Abnormal heat generation" and "Cool down".

  Further, since these event detailed information 24j, 24k, and 24l are related to an event of the same type “repair of abnormal heat generation”, in the first event detailed information 24j, progress information 52, related information 53, and hourly display 54 are displayed. Displayed as detailed information. This hourly display 54 shows a change in the heat generation status of the CPU of the asset 1A on April 15, and reads information on the time change of the CPU temperature of the asset 1A recorded as system information in the property DB 17. Is displayed. Although not shown in FIG. 10, the property DB 17 can store the time change of the CPU temperature for each asset as system information.

  When the system administrator 6 operates the display terminal 4 (FIG. 1) on the chart screen 20h and designates the event group mark 25c designated by the designation display mark 51 in the date designation frame 25c, the chart shown in FIG. A screen 20 i is displayed on the display screen 4. In FIG. 27, 55 is a check mark required, 56 is a cursor, 57 is a dialog box, and 58 is a frame-like cursor, and portions corresponding to the previous drawings are given the same reference numerals and redundant description is omitted.

  In the figure, in the daily event group display area 25 of the chart screen 20i, when the event group mark 25b designated by the designation display mark 51 in the date designation frame 25c is designated by the cursor 56, the menus "check", " A “Agreed ○” dialog box 57 is displayed, and one of these menus can be selected with a frame cursor 58.

  Therefore, if the menu “check in” is selected in the dialog box 57, the event group of the type displayed in the event group type selection unit 25d of the asset 1 displayed in the asset display area 21 is related. A check mark 55 is added to the asset 1 to be managed, in this case, the asset 1A. The asset 1 of the icon to which the check mark 55 is required has an event group type that does not support warnings, but if this check mark 55 is added, there is no event group that does not support warnings, This check mark 55 is added.

  Note that when the menu “corresponding ○” is selected in the dialog box 57, it means that the warning has been handled, and the selection display mark attached to the icon 1a of the corresponding asset 1, in this case, the asset 1A. 50 is erased. Therefore, for the asset 1 corresponding to the warning, the selection display mark 50 can be erased and the icon can be displayed in a corresponding state by selecting the menu “corresponding ○” in the dialog box 57.

  In the above embodiment, the monitoring server 3 is used in FIG. 1. However, the event management server 2 has the above function of monitoring the status of each asset 1 of the monitoring server 3 so that the monitoring server 3 Can be omitted.

1 is a system configuration diagram showing an embodiment of an integrated asset management system according to the present invention. It is a block diagram which shows one specific example of the event management server in FIG. It is a figure which shows the flow of the process of the information in the DB part shown in FIG. It is a figure which shows one specific example of event DB in FIG. It is a figure which shows one specific example of the important event table in FIG. It is a figure which shows one specific example of the event group table in FIG. FIG. 7 is a diagram showing a specific example of an event group DB created from event information of the event DB shown in FIG. 4 using the important event table shown in FIG. 5 and the event group table shown in FIG. 6. It is a figure which shows one specific example of the assistance information table in FIG. It is a figure which shows one specific example of assistance information DB produced using the assistance information table shown in FIG. 8 from the event group stored in event group DB in FIG. It is a figure which shows one specific example of property DB in FIG. It is a figure which shows one specific example of local information DB in FIG. It is a flowchart which shows the event processing operation | movement of the event management server in FIG. It is a flowchart which shows the information provision process operation | movement to the display terminal of the event management server in FIG. It is a figure which shows one specific example of the standard screen among the event screens displayed with the display terminal in FIG. It is a figure which shows one specific example of the pull-down menu used with the standard screen in FIG. It is a figure which shows the chart screen when operating the X-axis menu selection part of the chart screen shown in FIG. 14, and changing to the menu "trouble frequency" in a pull-down menu (FIG. 15 (a)). It is a figure which shows the chart screen when operating the Y-axis menu selection part of the chart screen shown in FIG. 14, and changing into the menu "purchase year" in a pull-down menu (FIG. 15 (a)). It is a figure which shows one specific example of the physical location display screen among the event screens displayed on the display terminal in FIG. It is a figure which shows one specific example of the company organization chart display screen among the event screens displayed on the display terminal in FIG. It is a figure which shows one specific example of the network diagram display screen among the event screens displayed on the display terminal in FIG. FIG. 15 is a diagram showing a chart screen when the event type selection unit in the chart screen shown in FIG. 14 sets the type to “undisplayed asset 1A”. It is a figure which shows a char and a screen when another date is designated by the date designation frame on the chart screen shown in FIG. FIG. 15 is a diagram showing a chart screen when the type is “normal start / end of asset 1B” in the event type selection section on the chart screen shown in FIG. 14. FIG. 24 is a diagram showing a chart screen when another date is designated in the date designation frame on the chart screen shown in FIG. 23. FIG. 15 is a diagram showing a chart screen when the event type selection unit on the chart screen shown in FIG. FIG. 26 is a diagram showing a chart screen when another date is designated in the date designation frame on the chart screen shown in FIG. 25. FIG. 27 is a diagram showing a chart screen when an event group mark within a date designation frame is designated on the chart screen shown in FIG. 26.

Explanation of symbols

1, 1A-1C Assets 1a-1c, 2a, 3a, 4a Icon 2 Event management server 3 Monitoring server 4 Display terminal 5 Network 6 System administrator 10 Communication unit 11 CPU
12 DB section 13 Event DB
13a Event number 13b Date and time of reception 13c Asset name 13d Event type 14 Event group DB
14a Event group number 14b Acquisition date 14c Asset name 14d Event group type 15 Support information DB
15a Support information number 15b Acquisition date and time 15c Asset name 15d Support display pattern 15e Level 16 Local information DB
16a Local information name 16a ₁ Office map (local information)
16a ₂ Company organization chart (local information)
16a ₃ network diagram (local information)
16b Content 17 Property DB
17a Asset name 17b System information 17c Support information 18a Important event table 18b Event group table 19 Support information table 19a Event group 19b Condition 19c Support information 19c Support display pattern and level 20, 20a-20i Chart screen 21 Asset display area 21X X-axis item Display area 21Y Y-axis item display area 22X X-axis menu selection area 22Y Y-axis menu selection area 23X, 23Y pull-down button 24 Event details display area 24a Date 24b-24l Event details information 25 Daily event group display area 25a Calendar 25b Event group Mark 25c Day designation frame 25d Event group type display selection part 25e Pull-down button 26 Support information type selection area 26a Pull-down button 26b Support mark 27 blowing Output 28 Power OFF mark 30-33 Pull-down menu 40A Physical location display screen 40B Company organization chart display screen 40C Network diagram display screen 50 Selection display mark 51 Designated display mark 52 Progress information 53 Related information 54 Hourly display 52a, 53a, 54a Scroll Bar 55 Check mark required 56 Cursor 57 Dialog box 58 Frame cursor TA “Chart display” tab TB “Physical location display” tab TC “Company organization chart display” tab TD “Network diagram display” tab

Claims (5)

In a client terminal management system comprising a plurality of client terminals, an event management server connected to the client terminals via a communication line, and a display terminal for displaying event management information of the event management server,
The event management server
A control unit;
An event database that stores event information related to events that have occurred in each of the client terminals;
An important event table for defining information on the importance of an event and selecting the event information of an important event from the event information stored in the event database;
An event group table for making the combination of the relevant event information selected by the important event table an event group;
An event group database for storing the event group;
A local information database that stores, as local information, information related to the physical arrangement relationship of the plurality of client terminals and the hierarchical structure on the network;
The control unit
Of the event information stored in the event database, whether the event information determined to be important with reference to the important event table should be registered as an event group with reference to the event group table. Determining and registering the event information to be registered together as an event group, registering the event group as event management information in the event group database,
Accepting a display request for event management information from the display terminal, reading the event group from the event group database, and sending it to the display terminal as event management information together with the local information read from the local information database,
The display terminal
Receiving the event management information transmitted from the event management server;
Based on the received event management information, a display area for the client terminal and a display area for the event group are provided on the display screen. Based on the physical arrangement of the client terminal based on the local information and the hierarchical structure on the network The client terminal images are arranged and displayed in the display area of the client terminal, and the change in the number of event groups over time is displayed in the display area of the event group by displaying the number of event groups for each day. System for managing client terminals. In claim 1,
The event management server
For each event group type, a condition for obtaining support information and a form of support information are set, and a support information table for creating support information from the event group,
A support information database for storing the support information;
The controller is
For the event group stored in the event group database, refer to the support information table to determine the presence or absence of corresponding support information, register the corresponding support information in the support information database,
Accepting the display request for event management information from the display terminal, the support information stored in the support information database, together with the event group and the local information,
As event management information, send to the display terminal,
The display system according to claim 1, wherein the display form of the image of the client terminal in the display area of the client terminal corresponds to the support information. In claim 1 or 2,
The image of the client terminal in the display area of the client terminal on the display terminal is arranged and displayed in an arrangement relationship according to the local information in a space by a vertical axis and a horizontal axis,
A client terminal management system, wherein parameters are displayed on the vertical axis and the horizontal axis in a changeable manner, and the image layout of the client terminal can be changed in accordance with the change of the parameters. Oite to claim 2,
In the display area of the event group on the display screen of the display terminal,
The date designation method is displayed.
In the display area of the client terminal, the display form of the image of the corresponding client terminal is set according to the support information for the event group on the date specified by the specifying means. system. In any one of Claims 1-4,
A monitoring server connected to the plurality of client terminals via the communication line ;
The monitoring server monitors the presence or absence of the event information from each of the client terminals,
An event non-occurrence event information is transmitted to the event management server with respect to the client terminal that no longer generates an event and no longer transmits event information.

Images