Device management system and display method of device management system

Abstract

Provided is a technology for managing movable devices.　A device management system according to the present invention comprises a plurality of devices to be monitored and a monitoring server. The plurality of devices to be monitored are disposed under the monitoring server. Each device to be monitored transmits, to the monitoring server, the position information of the device to be monitored acquired from a GPS and the state information of the device to be monitored at arbitrary time intervals. The monitoring server automatically registers the position information of the device to be monitored received from the device to be monitored, and monitors the state of the device to be monitored.

Description

Equipment management system and method for displaying the equipment management system

[0001] The present invention relates to a device management system and a method for displaying a device management system.

[0002] When connecting multiple devices to a server and monitoring the status of each device using the server, each device must be registered on the server in advance. When registering a large number of devices, manually entering device information takes a lot of time and increases the likelihood of input errors. In particular, if the device's location information is entered incorrectly, the device's location cannot be accurately determined even if it malfunctions, potentially resulting in a long wait for recovery. In addition to devices with fixed locations, some devices are mobile. For example, with the increasing use of mobile unmanned aircraft, such as drones, it is necessary to constantly track the location of the devices in case of malfunction or loss.

[0003] Patent Document 1 describes that in an installation management device for sensor terminals, location information of the sensor terminals obtained by a GPS (Global Positioning System) is registered in a server.

[0004] Japanese Patent Application Laid-Open No. 2021-50993

[0005] In Patent Document 1, it is assumed that the sensor terminal will not be moved after installation, and management of a device that can be moved is not assumed. Therefore, the effect is limited to automating the registration of location information when the sensor terminal is installed.

[0006] Therefore, an object of the present invention is to provide a technique for managing a plurality of monitored devices, including mobile devices.

[0007] In order to solve the above problems, one representative device management system of the present invention comprises a plurality of monitored devices and a monitoring server, where the plurality of monitored devices are placed under the control of the monitoring server, and the monitored devices transmit location information and status information of the monitored devices obtained from GPS to the monitoring server at any time interval, and the monitoring server automatically registers the location information of the monitored devices received from the monitored devices and monitors the status of the monitored devices.

[0008] According to the present invention, it is possible to manage a plurality of monitored devices, including mobile devices.

[0009] Problems, configurations, and effects other than those described above will become apparent from the following description of the preferred embodiment of the invention.

[0010] FIG. 1 is a diagram illustrating an example of the configuration of a device management system 101 according to an embodiment of the present disclosure. FIG. 2 is a flowchart illustrating an example of a process for registering location information of a monitoring target device A during initial communication and when communication is resumed. FIG. 3 is a diagram illustrating an example of a list of monitoring target devices A displayed on a client screen. FIG. 4 is a diagram illustrating an example of a monitoring target device A displayed on a map on a client screen. FIG. 5 is a flowchart illustrating an example of a process for determining a priority of a response. FIG. 7 is a diagram illustrating an example of a large display of Tokyo on a map on a client screen. FIG. 8 is a diagram illustrating an example of a process for displaying detailed information about a warning and a proposed response on a client screen. FIG. 9A is a flowchart illustrating an example of a process for displaying detailed information about a warning and a proposed response on a client screen. FIG. 9B is a flowchart illustrating an example of a process for displaying detailed information about a warning and a proposed response on a client screen. FIG. 10 is a diagram illustrating an example of a configuration of a device management system 102 including multiple monitoring servers S. FIG. 11 is a diagram illustrating an example of a configuration of a device management system 103 including an integrated monitoring server T.

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the present invention is not limited to this embodiment. In addition, in the description of the drawings, the same parts are designated by the same reference numerals.

[0012] When there are multiple components with the same or similar functions, they may be described using the same reference numeral with different subscripts. When there is no need to distinguish between these multiple components, the subscripts may be omitted.

[0013] First, in the present disclosure, "when communication is resumed" refers to the time when the connection for communication is restored after being disconnected.

[0014] Next, the configuration of the device management system according to the embodiment of the present disclosure will be described with reference to FIG.

[0015] 1 is a diagram illustrating an example of the configuration of a device management system 101 according to an embodiment of the present disclosure. As shown in Fig. 1, the device management system 101 mainly includes a plurality of monitored devices A, a monitoring server S, a client C, a device management database (in the drawings, "database" is abbreviated as "DB") D1, an inventory management database D2, and a personnel management database D3.

[0016] The monitored device A is placed under the control of the monitoring server S, and can transmit the location information and status information of the monitored device A obtained from the GPS to the monitoring server S at any time interval. The monitoring server S can automatically register the location information of the monitored device A received from the monitored device A, and can monitor the status of the monitored device A. The client C can issue an alarm if a failure occurs in the monitored device A. The device management database D1 can register device information of the monitored device A. Furthermore, the inventory management database D2 can manage the inventory of parts required to repair the monitored device A. Furthermore, the personnel management database D3 can store work attendance information of workers.

[0017] The monitored device A and the monitoring server S, the client C and the monitoring server S, the device management database D1, the inventory management database D2, the personnel management database D3 and the monitoring server S are each connected to one another via a network N. The network N may include wired communication means or wireless communication means.

[0018] Next, with reference to FIG. 2, the registration of the location information of the monitored device A will be described.

[0019] When there are a large number of monitored devices A, manually inputting the location information of the monitored devices A takes a lot of time and is therefore very difficult. This is because the time required to register the location information of the monitored devices A depends on the number of monitored devices A. Therefore, in this embodiment, location information is obtained from the monitored devices A at the time of initial communication and when communication is resumed, and is automatically registered. Thereafter, the location information is updated at any time interval.

[0020] 2 is a flowchart showing an example of a process for registering the location information of the monitored device A at the time of initial communication and at the time of communication resumption. The monitored device A is equipped with a GPS to acquire location information.

[0021] Step 201: The monitored device A acquires location information from the GPS. The location information consists of latitude and longitude. The monitored device A transmits the latitude and longitude to the monitoring server S.

[0022] Step 202: The monitoring server S receives the latitude and longitude from the monitored device A. The monitoring server S obtains the address from the obtained latitude and longitude. To obtain the address from the latitude and longitude, a publicly available reverse geocoding API (Application Programming Interface) is used.

[0023] Step 203: The monitoring server S acquires the prefecture and city / ward / town / village from the address. Here, "ward" means a special ward of Tokyo.

[0024] Step 204: The monitoring server S registers the latitude, longitude, prefecture, and city / ward / town / village as device information.

[0025] For example, suppose that monitored device A is placed on a utility pole in Miyuki-cho, Kodaira City, Tokyo. When monitored device A is connected to monitoring server S, the address, prefecture, and city / ward / town / village where monitored device A is located are automatically registered according to the procedure shown in the flowchart of Figure 2. Specifically, the prefecture and city / ward / town / village are Tokyo and Kodaira City. The registered device information is stored in device management database D1.

[0026] By using such a device management system 101, it is not necessary to manually input the location of the monitored device A at the time of registration, and it is possible to automatically register the device by acquiring location information from the GPS installed in each monitored device A. Furthermore, even if the monitored device A is installed on a moving object such as a truck, location information can be acquired.

[0027] However, there are cases where location information cannot be acquired by GPS depending on the location of monitored device A. If location information cannot be acquired by GPS for a certain period of time during initial communication or when communication is resumed, a message "Unable to acquire" is displayed on client C, prompting the user to manually input the location of monitored device A.

[0028] Next, the client screen will be described with reference to FIGS.

[0029] FIG. 3 is a diagram showing an example of displaying a list of monitored devices A on a client screen. If a failure occurs in monitored device A, client C can issue an alarm. The list of monitored devices A can be displayed on the client screen, with the monitored device A in which a failure has occurred being displayed at the top of the list. It is also possible to use a search function to display only the monitored device A in which a failure has occurred in the list. However, it is often difficult to get an overall understanding of the location of the monitored device A in which a failure has occurred by simply displaying the list.

[0030] FIG. 4 is a diagram showing an example of displaying a monitored device A on a map on a client screen. A circle on the map indicates a monitored device A where a failure has occurred. FIG. 4 shows, for example, that at least three failures have occurred in Kodaira City. A list of monitored devices A may also be displayed on the right side of the client screen. The ratio of the map to the list on the client screen may be changed. Information about an alarm may also be displayed on the map when a cursor is placed over a circle on the map. Information about an alarm may also be displayed in the upper right corner of the client screen. For example, the time when the alarm occurred and the type of alarm may be displayed, or a search screen may be displayed by clicking a magnifying glass icon in the upper right corner of the client screen. Displaying monitored device A on the map on the client screen in this way allows a user to grasp the location of a monitored device A where a failure has occurred from a bird's-eye view.

[0031] When multiple monitored devices A simultaneously experience failures, multiple pieces of alarm information are generated, making it difficult to determine which monitored device A should receive priority and responding quickly. Therefore, alarm information may be assigned a response priority based on the type or address of the facility where the monitored device A is located and the type of alarm. The response priority may also be displayed, for example, by color. As shown in FIG. 4 , an alarm that is predicted to have a high response priority may be displayed on a map in "red," a medium response priority in "orange," and a low response priority in "yellow." Similarly, the response priority may also be displayed in a list, for example, by color. The response priority may also be displayed by a method other than color.

[0032] Furthermore, depending on the range of the map currently being displayed, the monitored device A for which an alarm has been issued may be displayed in color, or the prefecture or city, town or village in which the monitored device A for which an alarm has been issued is located may be displayed in color.

[0033] FIG. 5 is a flowchart showing an example of processing when an alarm occurs. Assuming that the address, prefecture, and city / ward / town / village of the location of each monitored device A have already been registered during initial communication between the monitored device A and the monitoring server S, the location of the monitored device A for which an alarm has occurred can be obtained from the device information and the monitored device A for which an alarm has occurred can be displayed on a map. The display method on the map on the client screen can also be changed depending on the range of the currently displayed map. For example, assume that the entire Kanto region is displayed on the map on the client screen and that the number of prefectures displayed on the map is a or more. In this state, if a failure occurs in a registered monitored device A and an alarm is generated, the location of the monitored device A for which the failure has occurred, for example, Tokyo, is displayed in color through the flow shown in FIG. 5 . Because the number of prefectures displayed on the map on the client screen is a or more, the entire Tokyo region is displayed in color, rather than the monitored device A for which the failure has occurred.

[0034] Also, suppose that Tokyo is displayed large on the map on the client screen, and the number of cities, wards, towns, and villages displayed on the map is b or more. In this state, if a failure occurs in registered monitored device A and an alarm is issued, the location of monitored device A where the failure occurred, for example, Kodaira City, is displayed in color through the flow of Figure 5. Then, since the map on the client screen displays cities, wards, towns, and villages greater than b, the entire city of Kodaira may be displayed in color, rather than monitored device A where the failure occurred.

[0035] The flowchart in Fig. 5 will be explained below step by step: Step 301: A failure occurs in a registered monitored device A, and an alarm is issued.

[0036] Step 302: The location where the alarm occurred is identified from the information of the monitored device A where the alarm occurred.

[0037] Step 303: Determine whether the number of prefectures displayed on the map on the client screen is less than a. If it is less than a, proceed to step 305. If it is a or more, proceed to step 304.

[0038] Step 304: The prefecture where the alert occurred is displayed with a color. If the priority of the response is high, it is displayed in "red," if it is medium, it is displayed in "orange," and if it is low, it is displayed in "yellow."

[0039] Step 305: Determine whether the number of cities, wards, towns, and villages displayed on the map on the client screen is less than b. If it is less than b, proceed to step 307. If it is b or more, proceed to step 306.

[0040] Step 306: The city, ward, town or village where the alert occurred is displayed in a different color: "red" if the priority of the response is high, "orange" if it is medium, and "yellow" if it is low.

[0041] Step 307: The monitored device A where an alarm has occurred is displayed in a color. If the priority of the response is high, it is displayed in "red," if it is medium, it is displayed in "orange," and if it is low, it is displayed in "yellow."

[0042] Step 308: Determine whether the number of alarms that have occurred within the same local government (prefecture, city, town, or village) is less than c. If it is less than c, end the process. If it is c or more, make the color display blink.

[0043] Next, FIG. 6 is a flowchart showing an example of a process for determining response priorities. FIG. 7 is a diagram showing an example of a large display of Tokyo on a map on a client screen. A response priority is assigned to each alarm based on factors such as the type of facility where the alarm occurred, the location where the alarm occurred, the type of alarm, and the time of the alarm, and the alarm is displayed in a different color depending on the response priority. For example, if the response priority of an alarm generated by a monitored device A located in Miyuki-cho, Kodaira City, Tokyo, is high, the entire city of Kodaira is displayed in red, as shown in FIG. 7. If alarms with different response priorities occur within the same municipality, the color corresponding to the higher response priority can be used. If the number of alarms generated within the same municipality is c or more, the municipality is highlighted. For example, the display may be flashed.

[0044] 6 will be explained below step by step: Step 401: A failure occurs in a registered monitored device A, and an alarm is issued.

[0045] Step 402: The factor N that determines the priority of the correspondence is set to 0.

[0046] Step 403: Add points to N according to the type of alarm that has occurred.

[0047] Step 404: Add a score to N according to the type of facility where the alarm occurred.

[0048] Step 405: A score corresponding to the address where the alarm occurred is added to N.

[0049] Step 406: Points are added to N according to the type of facility where the alarm occurred and the time when the alarm occurred for the address where the alarm occurred.

[0050] Step 407: Determine whether N is less than d. If it is less than d, proceed to step 410. If it is equal to or greater than d, proceed to step 408.

[0051] Step 408: The priority of the response is determined to be high.

[0052] Step 409: Display in red.

[0053] Step 410: Determine whether N is less than e. If it is less than e, proceed to step 413. If it is greater than or equal to e, proceed to step 411.

[0054] Step 411: The priority of the response is determined to be medium.

[0055] Step 412: Display in orange.

[0056] Step 413: The priority of the response is determined to be low.

[0057] Step 412: Display in yellow.

[0058] By displaying the location where an alarm has occurred in different colors according to the priority of the response, for example, it becomes possible to quickly determine the priority of the response.

[0059] Next, the display of detailed information about an alarm and a suggested response on a client screen will be described with reference to FIGS. 8 and 9. FIG.

[0060] By creating a visually easy-to-understand client screen during monitoring, it is necessary to shorten the time from the occurrence of a failure to recovery as much as possible. Therefore, when checking an active alarm on the client screen, detailed information about the alarm and a proposed response are displayed. The response proposals include the monitored target device A registered in advance, the repair method for each alarm, the necessary parts, the necessary personnel, as well as the inventory of the necessary parts and the personnel available to respond. It is also possible to display responses to similar alarms in the past.

[0061] FIG. 8 shows an example of a client screen displaying detailed information about an alarm and a proposed response. When checking an active alarm on the client screen, detailed information about the alarm and a proposed response are displayed. The monitored device A, the repair method for each alarm, the required parts, and the required personnel are registered in advance in the device management database. By attaching GPS to the containers storing each part and replacement devices, it is possible to determine "which parts and devices are in which warehouses and in what quantities." Furthermore, the inventory of parts stored in containers can be determined by weight, RFID, or other means. If the inventory is predicted to fall below a specified number when responding to a currently active alarm, a warning is issued to the administrator. While this inventory management is assumed to be performed using the inventory management database D2, it may also be performed using other databases.

[0062] As shown in Figure 8, the client screen displays personnel available to respond. The equipment management system 101 manages the attendance status and schedules of workers at each business location. Schedule and attendance management for workers can be performed in the personnel management database D3. With regard to attendance status, if workers carry employee ID cards with GPS, correct attendance information can be displayed even in the event of a sudden business trip. In addition to response proposals, the client screen may also display responses to past similar alerts.

[0063] 9 is a flowchart showing an example of a process for displaying detailed information about an alarm and a suggested response on a client screen. A connector AA in FIG. 9A is connected to a connector AA in FIG. 9B.

[0064] 9A and 9B will be described below step by step: Step 501: A failure occurs in a registered monitoring target device A, and an alarm is issued.

[0065] Step 502: Obtain alarm information A from the device management database D1. The alarm information A includes the location where the monitored device A in which the alarm occurred is located, the facility, the alarm name, the device type, and so on.

[0066] Step 503: Obtain alarm response information B from the device management database D1. The alarm response information B includes the number of workers required, the level of the workers required, the names of the parts required, the number of parts required, etc.

[0067] Step 504: Stock information C of the necessary parts included in B is obtained from the stock management database D2.

[0068] Step 505: Information D of available workers at or above the required worker level included in B is obtained from the personnel management database D3.

[0069] Step 506: Obtain past alarm information E that is the same as or similar to the currently occurring alarm from the device management database D1.

[0070] Step 507: Determine whether the number of available workers is greater than 0. If it is greater than 0, proceed to step 508. If it is 0, proceed to step 511.

[0071] Step 508: Determine whether the number of available workers is equal to or greater than the required number of workers. If it is equal to or greater than the required number of workers, proceed to step 509. If it is less than the required number of workers, proceed to step 510.

[0072] Step 509: The alarm information including A, B, C, D, and E is displayed on the client screen. For display D, the available workers are displayed in order of their work locations closest to the alarm occurrence location.

[0073] Step 510: Display the alarm information including A, B, C, D, and E on the client screen. For the display of D, display the available workers and display "Not enough available workers."

[0074] Step 511: Display the alarm information including A, B, C, D, and E on the client screen. For the display of D, display "There are not enough workers available to handle the situation."

[0075] Step 512: Determine whether (number of parts in stock) - (number of parts required) is equal to or greater than 0. If it is equal to or greater than 0, proceed to step 514. If it is less than 0, proceed to step 513.

[0076] Step 513: The stock quantity is displayed in red.

[0077] Step 514: Determine whether (number of parts in stock) + (number of parts on order) - (number of parts required) is equal to or greater than f. If equal to or greater than f, end the process. If less than f, proceed to step 515. f is a threshold for issuing a warning about a shortage of stock, and is determined for each part.

[0078] Step 515: The monitoring person and the operations manager are notified.

[0079] By displaying suggested responses to alerts that are occurring on the client screen, it is possible to smoothly carry out a series of responses from detecting a problem to recovery.

[0080] Next, the configuration of an equipment management system equipped with an integrated monitoring server will be described with reference to FIGS.

[0081] There is an upper limit in practical operation to the number of monitored devices A that can be monitored by one monitoring server S. The number of monitoring items that can be monitored by one monitoring server S is, for example, around 2,000 to 3,000, so if the number of monitoring items of the monitored device A exceeds the upper limit, it is thought that this can be handled by increasing the number of monitoring servers S.

[0082] Fig. 10 is a diagram showing an example of the configuration of a device management system 102 equipped with multiple monitoring servers S. The multiple monitoring servers S are connected to a device management database D1, an inventory management database D2, and a personnel management database D3 via a network N, but Fig. 10 omits the illustration of the device management database D1, the inventory management database D2, and the personnel management database D3.

[0083] 10 , when clients C are divided by monitoring target device A, it is necessary to use different clients C depending on the monitoring target device A to be monitored. This poses a problem, for example, in that the monitoring target device Amn cannot easily determine which client C it should check. Even when there are a huge number of monitoring items, it is necessary to provide a mechanism that makes monitoring easy.

[0084] Fig. 11 is a diagram showing an example of the configuration of a device management system 103 equipped with an integrated monitoring server T. As shown in Fig. 11, the device management system 103 mainly includes a plurality of monitored devices A, a plurality of monitoring servers S, the integrated monitoring server T, a client C, a device management database D1, an inventory management database D2, and a personnel management database D3.

[0085] The monitored device A is placed under the control of the monitoring server S, and can transmit the location information and status information of the monitored device A obtained from the GPS to the monitoring server S at any time interval. The monitoring server S is placed under the control of the integrated monitoring server T, and can transmit the location information and status information of the monitored device A received from the monitored device A to the integrated monitoring server T. The integrated monitoring server T can automatically register the location information of the monitored device A received from the monitoring server S and monitor the status of the monitored device A. The client C can issue an alarm if a failure occurs in the monitored device A. The device management database D1 can register device information of the monitored device A. The inventory management database D2 can manage the inventory of parts needed to repair the monitored device A. The personnel management database D3 can store work attendance information of workers.

[0086] The monitored device A and the monitoring server S, the monitoring server S and the integrated monitoring server T, the client C and the integrated monitoring server T, the device management database D1, the inventory management database D2, the personnel management database D3 and the integrated monitoring server T are each connected to each other via a network N.

[0087] The integrated monitoring server T comprehensively monitors the monitoring servers S. The monitoring server S periodically acquires and stores location information and status information of the monitored device A from the monitored device A. The integrated monitoring server T periodically acquires location information and status information of the monitored device A from the monitoring server S.

[0088] Information on the monitored device A is held on the monitoring server S, and data is passed on based on requests from the integrated monitoring server T. The monitoring server S notifies the integrated monitoring server T that a failure has occurred in the monitored device A. The integrated monitoring server T consolidates information on the occurrence of the failure received from multiple monitoring servers S and displays it to the client.

[0089] As a result, even if there are a huge number of monitoring items, all of the monitoring target devices A can be monitored by a single client.

[0090] Although the embodiments of the present invention have been described above, the present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the gist of the present invention.

[0091] The following are examples of the present invention, but the present invention is not limited to these examples.

[0092] (Aspect 1) A device management system comprising a plurality of monitored devices and a monitoring server, wherein the plurality of monitored devices are placed under the control of the monitoring server, the monitored devices transmit location information and status information of the monitored devices obtained from GPS to the monitoring server at any time interval, and the monitoring server automatically registers the location information of the monitored devices received from the monitored devices and monitors the status of the monitored devices.

[0093] (Aspect 2) An equipment management system according to aspect 1, further comprising an integrated monitoring server, wherein a plurality of the monitoring servers are deployed, and the plurality of monitoring servers are deployed under the integrated monitoring server, and the monitoring server transmits location information of the monitored devices and status information of the monitored devices received from the monitored devices to the integrated monitoring server.

[0094] (Aspect 3) The device management system according to aspect 1 or aspect 2, wherein the location information of the monitoring target device is automatically registered at the time of initial communication and at the time of communication resumption between the monitoring target device and the monitoring server.

[0095] (Aspect 4) The device management system according to any one of Aspects 1 to 3, further comprising a client that can connect to the monitoring server or the integrated monitoring server, and the client generates an alarm when a failure occurs in the monitored device.

[0096] (Aspect 5) The device management system according to aspect 4, wherein the client determines a priority of a response according to the registration information and alarm information of the monitored device, and displays the alarm together with the priority of the response on a map or in a list.

[0097] (Aspect 6) A device management system according to aspect 5, wherein the client displays the response priority on a per-monitored-device basis when the number of municipalities displayed on the map on the client screen is less than a first number, and displays the response priority on a per-municipal basis when the number of municipalities displayed on the map on the client screen is equal to or greater than the first number.

[0098] (Aspect 7) The device management system according to aspect 6, wherein the client highlights the priority of the response of a local government when the number of alerts generated within the same local government is equal to or greater than a second number.

[0099] (Aspect 8) An equipment management system according to any one of Aspects 5 to 7, wherein the priority of the response is determined by adding points according to factors including the type of alarm that has occurred, the type of facility where the alarm has occurred, the location where the alarm has occurred, and the time when the alarm has occurred, and is displayed in color on a map or in a list.

[0100] (Aspect 9) The device management system according to any one of Aspects 4 to 8, wherein the client displays information including details of the alert, a response proposal, and responses to past similar alerts.

[0101] (Aspect 10) An equipment management system according to any one of Aspects 4 to 9, further comprising an equipment management database and a personnel management database, and the client displays, for an active alarm, a response proposal including a required response, required parts, and available personnel, based on the registration information of the monitored device registered in the equipment management database and the attendance information of workers stored in the personnel management database.

[0102] (Aspect 11) The equipment management system according to aspect 10, further comprising an inventory management database, wherein the inventory of parts can be determined by weight or RFID, inventory is managed in the inventory management database, and when a currently occurring alarm is responded to, if it is estimated that the inventory will fall below a specified number, a warning is issued to an administrator.

[0103] (Aspect 12) The equipment management system according to aspect 10 or aspect 11, wherein when a worker has an employee ID card with a GPS, the current location of the worker can be displayed on a map on the client in real time.

[0104] (Aspect 13) A display method for an equipment management system according to aspect 5, comprising the steps of: determining whether to display the response priority on a monitored device basis or on a municipality basis, depending on the number of municipalities displayed on a map on a client screen; and determining the response priority by adding points according to items including the type of alert that has occurred, the type of facility where the alert has occurred, the location where the alert has occurred, and the time when the alert has occurred.

[0105] (Aspect 14) A display method for an equipment management system according to aspect 10, comprising: a step of displaying information according to the number of workers available and the number of workers required; and a step of displaying information according to the number of parts in stock and the number of parts required for the operation.

[0106] C: Client, T: Integrated monitoring server, S: Monitoring server, A: Monitored device, D1: Device management DB, D2: Inventory management DB, D3: Personnel management DB, N: Network

Claims

1. An equipment management system comprising a plurality of monitored devices and a monitoring server, wherein the plurality of monitored devices are placed under the control of the monitoring server, the monitored devices transmit location information of the monitored devices and status information of the monitored devices obtained from a GPS to the monitoring server at any time interval, and the monitoring server automatically registers the location information of the monitored devices received from the monitored devices and monitors the status of the monitored devices.

2. An equipment management system as described in claim 1, further comprising an integrated monitoring server, wherein a plurality of the monitoring servers are arranged under the integrated monitoring server, and the monitoring server transmits location information of the monitored devices and status information of the monitored devices received from the monitored devices to the integrated monitoring server.

3. An equipment management system according to claim 1 or 2, wherein the location information of the monitored device is automatically registered at the time of initial communication and at the time of resumption of communication between the monitored device and the monitoring server.

4. An equipment management system as claimed in claim 1 or 2, further comprising a client capable of connecting to said monitoring server or integrated monitoring server, said client generating an alarm when a fault occurs in said monitored equipment.

5. An equipment management system according to claim 4, wherein the client determines a priority of a response according to the registration information and alarm information of the monitored equipment, and displays the alarm together with the priority of the response on a map or in a list.

6. A device management system as described in claim 5, wherein the client displays the response priority on a monitored device basis when the number of municipalities displayed on the map on the client screen is less than a first number, and displays the response priority on a municipality basis when the number of municipalities displayed on the map on the client screen is equal to or greater than the first number.

7. An equipment management system according to claim 6, wherein the client highlights the priority of the response of a local government when the number of alarms generated within the same local government is equal to or greater than a second number.

8. An equipment management system as claimed in claim 5, wherein the priority of the response is determined by adding up points according to items including the type of alarm that occurred, the type of facility where the alarm occurred, the location where the alarm occurred, and the time when the alarm occurred, and is displayed by color on a map or in a list.

9. An equipment management system according to claim 4, wherein the client displays information including details of the alert, suggested responses, and responses to similar past alerts.

10. An equipment management system as claimed in claim 4, further comprising an equipment management database and a personnel management database, and wherein the client displays, in response to an occurring alarm, suggestions for response including necessary actions, required parts and available operators, based on the registration information of the monitored equipment registered in the equipment management database and the attendance information of operators stored in the personnel management database.

11. An equipment management system as claimed in claim 10, further comprising an inventory management database, wherein the number of parts in stock can be determined by weight or RFID, inventory is managed in the inventory management database, and when a currently occurring alarm is responded to, if it is estimated that the number of parts in stock will fall below a designated number, a warning is issued to an administrator.

12. An equipment management system according to claim 10, wherein when a worker has an employee ID card with a GPS, the current location of the worker can be displayed on a map on the client in real time.

13. A display method for an equipment management system as described in claim 5, comprising the steps of: determining whether the response priority should be displayed per monitored equipment unit or per municipality unit depending on the number of municipalities displayed on a map on a client screen; and determining the response priority by adding up points according to items including the type of alarm that occurred, the type of facility where the alarm occurred, the location where the alarm occurred, and the time when the alarm occurred.

14. A display method for an equipment management system as claimed in claim 10, comprising the steps of: displaying according to the number of workers available and the number of workers required; and displaying according to the number of parts in stock and the number of parts required for the response.

Images