WO2024116287A1 - Dispositif de surveillance de défaillance et procédé de surveillance de défaillance - Google Patents

Dispositif de surveillance de défaillance et procédé de surveillance de défaillance Download PDF

Info

Publication number
WO2024116287A1
WO2024116287A1 PCT/JP2022/044021 JP2022044021W WO2024116287A1 WO 2024116287 A1 WO2024116287 A1 WO 2024116287A1 JP 2022044021 W JP2022044021 W JP 2022044021W WO 2024116287 A1 WO2024116287 A1 WO 2024116287A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
information
building
unit
equipment
Prior art date
Application number
PCT/JP2022/044021
Other languages
English (en)
Japanese (ja)
Inventor
泰 丸岡
英郎 青木
長範 細川
Original Assignee
株式会社日立ビルシステム
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立ビルシステム filed Critical 株式会社日立ビルシステム
Priority to PCT/JP2022/044021 priority Critical patent/WO2024116287A1/fr
Publication of WO2024116287A1 publication Critical patent/WO2024116287A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring

Definitions

  • the present invention relates to a fault monitoring system and a fault monitoring method.
  • building facility equipment which is the equipment installed in buildings, has become more sophisticated and multifunctional, and often works in conjunction with other devices. Therefore, it is important to monitor whether building facility equipment is working properly, and to notify the department responsible for the building facility equipment when a malfunction occurs.
  • surveillance footage captured by surveillance cameras installed in a building is sent to a surveillance center via network devices and stored on a surveillance server installed in the surveillance center, where surveillance processing is carried out based on the surveillance footage.
  • the surveillance server detects a suspicious person or other object from the surveillance footage, it notifies a terminal such as that of the building manager.
  • surveillance cameras are used as an example, but various building equipment such as elevators, air conditioning equipment, and entrance/exit management systems installed in the building are also designed to operate in conjunction with various other devices in a similar manner.
  • a malfunction occurs in any of the building equipment, the services provided by that building equipment will no longer be available.
  • the monitoring server which means monitoring is no longer possible, in a situation where monitoring is based on footage captured by a surveillance camera.
  • a maintenance worker from the management company of the relevant service upon receiving a notification of the malfunction, a maintenance worker from the management company of the relevant service will visit the building, find out which equipment is malfunctioning, and carry out repairs or replacement of the faulty equipment, thereby restoring monitoring processing.
  • the causes of equipment abnormalities are diverse, ranging from something as simple as the power plug being pulled out and the power not turning on, to more advanced recovery procedures such as an abnormality in the application program implemented in the equipment or a memory abnormality.
  • Patent Document 1 describes a monitoring technology that refers to a business configuration information table to infer the business in which a failure has occurred, and extracts the configuration devices and resources that make up the business in which the failure has occurred.
  • Patent Document 1 when a fault occurs in a device constituting a system, it is conventionally known to detect or estimate the fault. When considering actual recovery work, specialized maintenance personnel will need to carry out the work for application program anomalies, memory anomalies, etc. On the other hand, relatively simple anomalies such as a power plug being unplugged can be dealt with by someone in the building once the cause is identified, without the need for specialized maintenance personnel to be dispatched.
  • information about malfunctions in building facilities is only known at specific locations, such as the maintenance service company. Therefore, when an abnormality occurs in building facilities, the maintenance staff of the maintenance service company must carry out the work regardless of the nature of the malfunction, which places a heavy burden on the maintenance staff and takes a long time from the occurrence of the malfunction to recovery.
  • the present application includes multiple means for solving the above-mentioned problems.
  • a fault monitoring system that monitors faults in building equipment connected to multiple services provided in a building, comprising a database unit that stores service definition information that defines the building equipment connected to the multiple services, a fault reception unit that receives fault information of the building equipment equipment in which a fault has occurred, a fault management unit that, when the fault reception unit receives the fault information, refers to the database unit to identify the multiple services affected by the fault in the building equipment, and a notification processing unit that outputs the multiple services affected by the fault in the building equipment identified by the fault management unit.
  • appropriate notifications can be sent for each piece of building equipment based on the services that are affected by the failure of that equipment, making it possible to take appropriate action for each piece of building equipment in which a failure occurs.
  • FIG. 1 is a block diagram showing an example of the configuration of a fault monitoring system according to an embodiment of the present invention
  • 1 is a block diagram showing an example of the configuration of building equipment connected to a fault monitoring system according to an embodiment of the present invention.
  • 5 is a flowchart showing an example of a notification operation by the fault monitoring system according to an embodiment of the present invention.
  • 10 is a flowchart illustrating an example of an authority setting process performed by the fault monitoring system according to an embodiment of the present invention.
  • FIG. 11 is a diagram showing an example of user information according to an embodiment of the present invention.
  • FIG. 11 is a diagram showing an example of access authority according to an embodiment of the present invention.
  • FIG. 13 is a diagram showing an example of a constituent parts map according to an embodiment of the present invention.
  • FIG. 13 is a diagram illustrating an example of alert authority according to an embodiment of the present invention.
  • FIG. 13 is a diagram showing an example of an alert user definition according to an embodiment of the present invention.
  • FIG. 11 is a diagram showing an example (example 1) of an alert notification screen according to an embodiment of the present invention.
  • FIG. 13 is a diagram showing an example (example 2) of an alert notification screen according to an embodiment of the present invention.
  • FIG. 13 is a diagram showing an example of a relation screen according to an embodiment of the present invention.
  • 11A and 11B are diagrams illustrating an example of an alert detection period and a notification method according to an embodiment of the present invention.
  • FIG. 14 is a diagram showing an example of alert authority in the case of the example of FIG. 13.
  • FIG. 14 is a diagram showing an example of alert authority in the case of the example of FIG. 13.
  • FIG. 1 is a diagram showing the overall configuration of a fault monitoring system according to this embodiment.
  • the fault monitoring system according to this embodiment monitors faults in building equipment devices 101, 102 installed in a building. These building equipment devices 101, 102 are operated as facilities within the building. Here, the building equipment devices 101, 102 are collectively referred to as on-premise equipment 100.
  • the off-premises facilities 200 are servers or the like installed outside the building, and are connected to the building facility devices 101, 102, etc. via a network (not shown).
  • the building equipment devices 101 and 102 of the on-premise facility 100 are monitored by terminal monitoring units 103 and 104 installed in the equipment devices, respectively.
  • the terminal monitoring unit 103 monitors the container of the building equipment device 101.
  • the terminal monitoring unit 104 monitors the device of the building equipment device 102.
  • fault information such as anomalies is transmitted to a fault receiving unit 12 provided in the fault monitoring system of this embodiment.
  • the failure reception unit 12 When the failure reception unit 12 receives failure information, it performs a failure reception process of transmitting the failure information to the failure management unit 13.
  • the failure reception unit 12 can receive not only failure information but also information indicating normal operation from the on-premise equipment 100 and the off-premise equipment 200.
  • the fault monitoring system of this embodiment also includes a different system data input unit 11.
  • the different system data input unit 11 receives fault information from the different systems 300 and information indicating that the different systems are operating normally. The information received by the different system data input unit 11 is also transmitted to the fault management unit 13.
  • the failure management unit 13 When the failure management unit 13 receives the notified failure information, the failure management unit 13 performs a failure management process of instructing the database management unit 15 to read from the database unit 14 the registered information on the facility device in which the failure has occurred.
  • the database unit 14 information such as component parts, alert authorities, and component parts of facility devices is registered in advance as a database. That is, the database management unit 15 performs a service definition information storage process that stores definition information of services realized by the fault monitoring system in a database. Specific examples of the configuration of the database in which the service definition information and the like are stored will be described in Figure 5 and subsequent figures. In the drawings, the database is abbreviated as "DB.”
  • the database management unit 15 can communicate with the management server 16.
  • the management server 16 can add or update information held in the database unit 14 through operations by the user terminal 400. That is, when the database management unit 15 receives an input for adding or updating service definition information stored in the database unit 14, the database management unit 15 can reflect the received addition or update in the service definition information held by the database unit 14. However, this addition or update of the service definition information is performed only when the accessed user terminal 400 has authority for the building equipment to which the user is trying to add or update the service definition information.
  • the database management unit 15 also receives equipment information on building equipment, and adds or updates the equipment information on the building equipment stored in the database unit 14 .
  • the database management unit 15 reads information such as the alert authority from the database unit 14 based on an instruction from the fault management unit 13 and sends it to the notification control unit 17 .
  • the notification control unit 17 determines to whom to notify based on the fault information acquired from the fault management unit 13 and information such as the alert authority read from the database unit 14. Then, based on the result of the determination, the notification control unit 17 instructs the notification processing unit 500 on the method of notifying the fault.
  • the notification processing unit 500 includes a processing unit for notifying the user terminal by a plurality of methods, that is, the notification processing unit 500 includes a mail control unit 501, an SMS control unit 502, a cooperation API control unit 503, and the like.
  • the mail control unit 501 notifies the user terminal 400 by email.
  • the SMS control unit 502 notifies the user terminal 400 using the Short Message Service function of the mobile phone.
  • the link API control unit 503 has an application programming interface function for sending a notification to the user terminal 400 by using a specific application program.
  • the notification processing unit 500 may include other notification function processing units.
  • FIG. 2 shows the configuration of building facility equipment.
  • one group of building facility equipment is made up of an external device 110, a terminal 120, and a cloud device 130.
  • Another group of building facility equipment is made up of two cloud devices 140 and 150 .
  • Yet another group of building equipment consists of external equipment 160 .
  • the external device 110 is composed of two devices 111 and 112 and a network (NW) device 113.
  • the network device 113 communicates with a terminal 120.
  • Each of the devices 111, 112, and 113 has a function of monitoring the device itself.
  • the terminal 120 is an information processing terminal configured as a computer, and includes an information processing unit 121, a terminal monitoring unit 122, and a network device 123.
  • the information processing unit 121 includes a service execution unit 121a, a resource unit 121b, an OS (Operating System) and middleware 121c, and a performance unit 121d.
  • the terminal monitoring unit 122 includes an SSD (Solid State Drive) life prediction unit 122a, a terminal life prediction unit 122b, and a temperature measurement unit 122c.
  • the network device 123 communicates with the external device 110 and the cloud device 130 .
  • Cloud devices 130, 140, 150 also respectively include service execution units 131, 141, 151, resource units 132, 142, 152, OS and middleware 133, 143, 153, and performance units 134, 144, 154. Although not shown in FIG. 2, cloud devices 130, 140, 150 also include a monitoring unit similar to terminal monitoring unit 122.
  • External device 160 is composed of two devices 161 and 162 and a network device 163. Each of devices 161, 162, and 163 has a function for monitoring the device itself.
  • each of the devices 110 to 160 shown in FIG. 2 is monitored, and when a fault occurs, the fault reception unit 12 of the fault monitoring system of this embodiment receives fault information.
  • FIG. 3 is a flowchart showing the flow of a fault notification process performed by the fault monitoring system according to this embodiment.
  • fault information is notified from any of the devices (eg, the devices 110 to 160 shown in FIG. 2), and the fault information is received by the fault receiving unit 12 (step S11).
  • the fault information received by the fault receiving unit 12 is sent to the fault management unit 13.
  • the database management unit 15 acquires device information indicating the occurrence of a fault from the fault information registered in the database unit 14 (step S12).
  • the failure management unit 13 identifies the details of the failure based on the failed device and the details of the failure indicated by the failure information and the information acquired from the database unit 14 (step S13).
  • the fault management unit 13 creates notification information to be notified to the user terminal based on the acquired notification information (step S14).
  • the fault management unit 13 requests the database management unit 15 to register the occurrence of the fault in the corresponding device in the database unit 14 (step S15).
  • the notification control unit 17 creates a notification request (step S16).
  • the notification control unit 17 determines whether the notification destination of this notification request satisfies the notification authority etc. specified in the information obtained from the database unit 14 (step S17). If the notification authority etc. is not satisfied in step S17 (NO in step S17), the notification control unit 17 waits until a notification request that satisfies the notification authority etc. arrives.
  • step S17 if the notification authority etc. is met (YES in step S17), a request is made to the notification processing unit 500 to notify the user terminal of the notification information.
  • Access permission setting process 4 is a flow chart showing the flow of the access authority setting process performed by the fault monitoring system of this embodiment.
  • the access authority setting is performed by, for example, the user terminal 400 shown in FIG.
  • the user terminal 400 accesses the management server 16, and performs a login authentication process by operating the user terminal 400 (step S21).
  • the management server 16 identifies the user who has accessed the system (step S22), and determines the authority the user has based on the type of user, etc. (step S23).
  • the management server 16 refers to the information registered in the database unit 14 to identify the user's authority.
  • the management server 16 identifies which building equipment devices the user has the authority to access based on the user's authority identified in step S23 (step S24).
  • the management server 16 acquires the setting information of the building equipment devices to which the user has the access authority (step S25).
  • the management server 16 performs a web service provision process to provide the user terminal 400 with information on the building equipment devices to which the user has the access authority (step S26).
  • the management server 16 provides information about the building equipment to the user terminal 400.
  • the notification processing unit 500 shown in FIG. 1 may provide information about the building equipment, such as faults, to the user terminal 400.
  • FIG. 5 shows an example of user information held in the database unit 14.
  • the user information has the user's name, authority, and remarks.
  • the remarks information registers the user's type, etc.
  • a user with the name "aaaa” has authority of type k1
  • the system provider is registered as the type.
  • the types include sales, partner company, customer, etc.
  • the names "aaaa” and "bbbb" shown in FIG. 5 are actually entered as user names (names, company names, etc.).
  • FIG. 6 shows an example of information on access rights held in the database unit 14.
  • the information on the access authority indicates the type and the configuration or parts that can be accessed with that type of authority.
  • the type of access authority corresponds to the authority of the user information shown in FIG.
  • external device C, external device D, terminal C, cloud C, cloud D, and cloud D are shown as configurations that can be accessed with access authority k1.
  • the part is displayed. For example, when the access authority is k3, the network of the external device C and the network of the external device D are displayed as accessible parts.
  • FIG. 7 shows a component parts map of each piece of equipment stored in the database unit 14.
  • the configuration parts map has a configuration column showing the equipment devices and a parts column showing the parts that the configuration has.
  • each of the devices 110 to 160 shown in Fig. 2 corresponds to a configuration
  • each individual processing unit (such as device 111) in the devices 110 to 160 corresponds to a part.
  • external device C includes device E, device F, and a network device.
  • the parts here include parts realized by software, such as the service execution unit 121a, resource unit 121b, OS and middleware 121c, performance unit 121d, SSD life prediction unit 122a, terminal life prediction unit 122b, and temperature measurement unit 122c shown in FIG. 2.
  • FIG. 8 shows the alert authority held in the database unit 14.
  • the alert authority indicates a configuration and part, the type of alert that the part issues when a fault occurs, and the type of authority to receive notification of the alert.
  • device E which is a part of external device C, may issue alerts for power supply abnormality, communication abnormality, and radio wave abnormality.
  • these three alerts power supply abnormality, communication abnormality, and radio wave abnormality
  • a user with authorities k1 and k2 is notified of the three alerts of device E.
  • FIG. 8 which authority applies to each alert issued by a configuration and part is shown.
  • FIG. 9 shows the alert user definitions held in the database unit 14.
  • the alert user definition indicates a user, a configuration, a part, an alert, a definition cycle, and a definition notification. For example, it is indicated that for user "dddd”, periodic notification of a radio wave abnormality in device F of external device C is not necessary, and notification will be made by short message service (SMS). It is also indicated that user "dddd” will notify external device C of a communication abnormality in device F only once each time the abnormality occurs, and that the notification will be made using a specific application.
  • SMS short message service
  • FIG. 10 shows an example of how authority k1 is displayed on a user terminal.
  • a failure has occurred in external device C, and the display area 510 of the user terminal displays the configuration of external device C (external device 110) and the devices related to external device C (terminal 120, cloud device 130, cloud device 140, cloud device 150, external device 160). All of the devices displayed in these display areas 510 have authority k1, and devices that do not have authority k1 are not displayed.
  • a display area 520 of the user terminal displays a list of the configuration, parts, alerts, and detection intervals of the building equipment.
  • the display area 530 of the user terminal displays the alert period 531, an alert message 532, an alert notification destination 533, and alert contents 534.
  • the alert contents 534 indicate the contents of the fault, such as a radio wave abnormality or a power supply abnormality.
  • FIG. 11 shows an example of how authority k3 is displayed on a user terminal.
  • an example of display on the user terminal of authority k3 when a fault occurs in the network section of external device C (device 110) or the network section of external device D (device 160) is shown.
  • the user terminal with authority k3 has authority only for the network part of external device C and the network part of external device D. Therefore, only the network part of external device C (device 110) and the network part of external device D (device 160) are displayed in display area 510 of the user terminal. Note that the other components of external device C and external device D are also displayed in display area 510, but are displayed in a different manner from the network part (for example, in a light color) to indicate that notifications and operations cannot be performed. Also, a device can be selected with cursor display 591.
  • the display area 520 of the user terminal only the alerts of the network part of the external device C and the network part of the external device D having the authority k3 are displayed.
  • an alert occurs in the network part of the external device C having the authority k3 and the network part of the external device D, details of the alert are also displayed in the display area 530 of the user terminal.
  • FIG. 12 shows an example of a list of relations displayed on a user terminal.
  • the relation here refers to a function that allows information such as faults to be displayed to a user who has authority for a service for each service type.
  • the fault monitoring system of this embodiment is composed of many devices and parts. Therefore, the larger the service provided, the more devices and parts will be used, and they may also be reused. For this reason, in this embodiment, relations are used to perform monitoring by defining monitoring groups that are freely associated not only with devices and parts, but also with devices, parts, and alerts.
  • the relation screen shown in FIG. 12 comprises a relation list display area 610, a relation details display area 620, a configuration-parts-alert list display area 630, an alert type display area 640, and a relation details display area 650.
  • the user can select each display item by operating the cursor display 691.
  • the relation list display area 610 displays the relation name (video service, communication error, etc.), the registration date and time, and the name of the user who registered.
  • the configuration of the selected relation is displayed graphically in the relation detail display area 620. For example, when a video service is selected, the devices 110, 120, 130, 140, 150, and 160 related to the video service and the transmission systems of these devices 110 to 160 are displayed.
  • the configuration-parts-alert list display area 630 displays a list of configurations, parts, and alerts for each relation name.
  • the type of alert indicated by each part is displayed in the alert type display area 640.
  • the alert type display area 640 has a selection field 641 that allows any type of alert, and when this selection field 641 is selected, all alerts of the corresponding part are displayed in the alert type display area 640.
  • a button 642 for adding an alert type is provided, allowing an alert type to be added.
  • the relation detail display area 650 includes a relation name 651 , an alert cycle 652 , an alert message 653 , an alert notification destination 654 , alert contents 655 , and a setting button 656 .
  • FIG. 13 shows an example of an alert registered in the database unit 14 for displaying a relation.
  • the alert information for displaying the relation includes the configuration, parts, alerts, default detection interval, and default notification method.
  • FIG. 14 shows an example of alert rights registered in the database unit 14 for displaying relations.
  • the alert permission information for displaying the relationship shows the configuration, parts, alerts, and permissions.
  • FIG. 15 shows an example of an alert user definition registered in the database unit 14 for displaying a relation.
  • the alert user definition indicates the user name, configuration, parts, alert, definition cycle, and definition notification.
  • the definition cycle indicates whether to perform periodic notification or to perform notification only once at the time of alert.
  • the definition notification indicates the notification method. In this way, it is possible to set a notification method for a specific alert from a building facility device for each user.
  • FIG. 16 shows an example of relation management registered in the database unit 14 for displaying relations.
  • the relation management information indicates the relation name, the registration date and time, the registered user name, the definition cycle, and the definition notification.
  • the relation management information indicates each of the relations shown in the list of FIG.
  • FIG. 17 shows an example of a relation configuration registered in the database unit 14 for displaying relations.
  • the relation configuration includes a relation name, a configuration, parts, and an alert.
  • the video service shown in Fig. 17 only the configuration and parts of the video service are shown, and the alert is left blank.
  • the fault monitoring system of the embodiment described above it is possible to give an appropriate notification for each building equipment device based on the services affected by the fault of that equipment.
  • the fault monitoring system of the embodiment outputs multiple services affected by the fault of the building equipment device identified based on the received fault information, and notifies the corresponding user. Therefore, it is possible to take appropriate measures for each building equipment device in which a fault has occurred. For example, as shown in FIG. 6, different authorities are set for each type of user shown in FIG. 5, and when a fault occurs in the building equipment corresponding to that authority, each user is notified of the fault and is also notified of the services that are affected by the fault in the building equipment, allowing them to take appropriate action.
  • a user with authority k1 has authority to access alerts for almost all building equipment and is notified of all faults, whereas users with authority k3 and authority k4 are notified of only some alerts for some equipment. Therefore, it will be possible to send alerts when a fault occurs or during regular monitoring, depending on the type of person, such as the person in charge of the service company that provides maintenance services related to building facilities, the building's customers, etc. For example, in the event of a serious equipment fault, an alert will be sent to the service company, and in the event of a relatively minor fault such as a power abnormality, an alert will be sent to both the service company's person in charge and the building's customers, allowing the building customers to deal with the fault.
  • the affected service is output in association with the building equipment that caused the problem, so that only authorized users are notified of the affected service, as well as the building equipment that caused the problem, allowing them to take appropriate action.
  • an alert is sent to each maintenance service company for each piece of building equipment that they are responsible for, so each maintenance service company does not receive unnecessary alerts.
  • alerts will only be sent to the relevant personnel of the maintenance service companies for each system.
  • the database management unit accepts input for additions or updates to the service definition information stored in the database unit, and the accepted additions or updates are reflected in the service definition information held by the database unit, thereby always maintaining optimal service definition information.
  • the database unit stores the equipment information and usage rights of the building equipment, and when service definition information is added or updated, the usage rights of the building equipment included in the service definition information are added or updated after being confirmed by referring to a specified management server, so that only authorized users can add or update service definition information.
  • the database management unit accepts equipment information for building equipment and adds or updates the equipment information for the building equipment stored in the database unit, so that the addition or update of equipment information for building equipment can also be done appropriately based on authority.
  • the fault monitoring system of this example is configured using an information processing device such as a computer
  • the program that realizes the fault monitoring system may be stored in non-volatile storage or memory within the computer, or it may be stored on a recording medium such as an external memory, an IC card, an SD card, or an optical disk and transferred.
  • SSD life prediction unit 122b...life prediction unit, 122c...temperature measurement unit, 123...network device, 130...cloud device, 131...service execution unit, 132...resource unit, 133...middleware, 134...performance unit, 140, 150...cloud device, 160, 161...device, 163...network device, 200...off-premises equipment, 201...system, 300...other system, 400...user terminal, 500...notification processing unit, 501...email control unit, 502...SMS control unit, 503...linked API control unit

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Alarm Systems (AREA)

Abstract

L'invention concerne un système de surveillance de défaillance qui surveille une défaillance d'un équipement de bâtiment connecté à une pluralité de services fournis au niveau d'un bâtiment. Le système de surveillance de défaillance comprend une unité de base de données qui stocke des informations de définition de service pour définir un équipement de bâtiment connecté à une pluralité de services, une unité de réception de défaillance qui reçoit des informations de défaillance concernant un équipement de bâtiment en défaillance, une unité de gestion de défaillance qui identifie, lorsque l'unité de réception de défaillance a reçu les informations de défaillance, une pluralité de services affectés par la défaillance de l'équipement de bâtiment en se référant à l'unité de base de données et une unité de notification qui délivre la pluralité de services affectés par la défaillance de l'équipement de bâtiment, les services étant identifiés par l'unité de gestion de défaillance.
PCT/JP2022/044021 2022-11-29 2022-11-29 Dispositif de surveillance de défaillance et procédé de surveillance de défaillance WO2024116287A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/044021 WO2024116287A1 (fr) 2022-11-29 2022-11-29 Dispositif de surveillance de défaillance et procédé de surveillance de défaillance

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2022/044021 WO2024116287A1 (fr) 2022-11-29 2022-11-29 Dispositif de surveillance de défaillance et procédé de surveillance de défaillance

Publications (1)

Publication Number Publication Date
WO2024116287A1 true WO2024116287A1 (fr) 2024-06-06

Family

ID=91323383

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2022/044021 WO2024116287A1 (fr) 2022-11-29 2022-11-29 Dispositif de surveillance de défaillance et procédé de surveillance de défaillance

Country Status (1)

Country Link
WO (1) WO2024116287A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000194627A (ja) * 1998-12-25 2000-07-14 Ntt Data Corp ネットワ―クシステムの運用方法、運用状況監視装置及び情報通信装置
JP2008275317A (ja) * 2008-08-07 2008-11-13 Mitsubishi Electric Corp 冷熱機器管理システム、および冷熱機器の遠隔保守監視システム
JP2009252161A (ja) * 2008-04-10 2009-10-29 Hitachi Electronics Service Co Ltd 情報処理装置管理システム及び情報処理装置管理サーバ及び情報処理装置管理サービス提供方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000194627A (ja) * 1998-12-25 2000-07-14 Ntt Data Corp ネットワ―クシステムの運用方法、運用状況監視装置及び情報通信装置
JP2009252161A (ja) * 2008-04-10 2009-10-29 Hitachi Electronics Service Co Ltd 情報処理装置管理システム及び情報処理装置管理サーバ及び情報処理装置管理サービス提供方法
JP2008275317A (ja) * 2008-08-07 2008-11-13 Mitsubishi Electric Corp 冷熱機器管理システム、および冷熱機器の遠隔保守監視システム

Similar Documents

Publication Publication Date Title
US11627051B2 (en) Determining asset associations for data center customers
CA2980767C (fr) Procede et appareil pour gerer des dispositifs distants et acceder a des informations de dispositifs distants
US9557807B2 (en) Using augmented reality to create an interface for datacenter and systems management
JP6396887B2 (ja) モバイルデバイスサポートサービスを提供するためのシステム、方法、装置、および非一時的コンピュータ可読記憶媒体
US9049105B1 (en) Systems and methods for tracking and managing event records associated with network incidents
JP6095140B2 (ja) 遠隔監視システム、遠隔監視方法、及びプログラム
US11475758B2 (en) Monitoring control panels of a fire control system
KR102155014B1 (ko) 무인 단말기 유지 보수 장치 및 방법
JP2006199469A (ja) エレベータの点検報告システム及びその制御方法
US7552057B2 (en) Method and apparatus for using process exceptions to provide instant notifications for distributed processes
WO2024116287A1 (fr) Dispositif de surveillance de défaillance et procédé de surveillance de défaillance
US20200068192A1 (en) Video management system for video devices in a building system
JP2004013411A (ja) リモートメンテナンス装置
JP2006072784A (ja) 統合監視システム
US8424002B2 (en) Method, system and program of outputting information
EP3949279B1 (fr) Gestion de problèmes d'alarme pour un environnement de gestion de bâtiment
JP6569247B2 (ja) 障害検証装置及び障害検証方法、検証対象装置、無線通信システム、コンピュータ・プログラム
JP2012059305A (ja) アプリケーション稼働監視システム及び顧客アプリケーション稼働監視サービス提供システム
US20160307168A1 (en) System and Method for Managing Products, Product Services, and Stakeholders over an Internet
CN114074868B (zh) 大厦设备的运转状态显示装置、以及大厦设备的运转状态显示方法
JP2023043369A (ja) 映像モニタリング装置、映像モニタリングシステム、及び映像モニタリング方法
JP2020021138A (ja) 施設管理システム、下位コントローラ、および、下位コントローラにおける通信診断方法
JP2004153417A (ja) 集合住宅用インターホンシステム
Doffing Don't Just Kick the Tires, Look Under the Hood.
JP2003140925A (ja) タスク監視システム及び方法