WO2020138176A1 - Monitoring system, monitoring method, and monitoring program - Google Patents

Monitoring system, monitoring method, and monitoring program Download PDF

Info

Publication number
WO2020138176A1
WO2020138176A1 PCT/JP2019/050841 JP2019050841W WO2020138176A1 WO 2020138176 A1 WO2020138176 A1 WO 2020138176A1 JP 2019050841 W JP2019050841 W JP 2019050841W WO 2020138176 A1 WO2020138176 A1 WO 2020138176A1
Authority
WO
WIPO (PCT)
Prior art keywords
failure
information
remote management
management system
unit
Prior art date
Application number
PCT/JP2019/050841
Other languages
French (fr)
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
Priority claimed from JP2018246644A external-priority patent/JP2022044845A/en
Priority claimed from JP2018246646A external-priority patent/JP2022044846A/en
Priority claimed from JP2018246635A external-priority patent/JP2022044844A/en
Application filed by 京セラドキュメントソリューションズ株式会社 filed Critical 京セラドキュメントソリューションズ株式会社
Priority to CN201980086125.1A priority Critical patent/CN113260984A/en
Priority to US17/417,475 priority patent/US11635923B2/en
Publication of WO2020138176A1 publication Critical patent/WO2020138176A1/en

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201Dedicated interfaces to print systems
    • G06F3/1278Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
    • G06F3/1285Remote printer device, e.g. being remote from client or server
    • G06F3/1287Remote printer device, e.g. being remote from client or server via internet
    • BPERFORMING OPERATIONS; TRANSPORTING
    • B41PRINTING; LINING MACHINES; TYPEWRITERS; STAMPS
    • B41JTYPEWRITERS; SELECTIVE PRINTING MECHANISMS, i.e. MECHANISMS PRINTING OTHERWISE THAN FROM A FORME; CORRECTION OF TYPOGRAPHICAL ERRORS
    • B41J29/00Details of, or accessories for, typewriters or selective printing mechanisms not otherwise provided for
    • B41J29/38Drives, motors, controls or automatic cut-off devices for the entire printing mechanism
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F13/00Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201Dedicated interfaces to print systems
    • G06F3/1202Dedicated interfaces to print systems specifically adapted to achieve a particular effect
    • G06F3/121Facilitating exception or error detection and recovery, e.g. fault, media or consumables depleted
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201Dedicated interfaces to print systems
    • G06F3/1223Dedicated interfaces to print systems specifically adapted to use a particular technique
    • G06F3/1229Printer resources management or printer maintenance, e.g. device status, power levels
    • G06F3/1234Errors handling and recovery, e.g. reprinting
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F3/00Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
    • G06F3/12Digital output to print unit, e.g. line printer, chain printer
    • G06F3/1201Dedicated interfaces to print systems
    • G06F3/1278Dedicated interfaces to print systems specifically adapted to adopt a particular infrastructure
    • G06F3/1285Remote printer device, e.g. being remote from client or server

Definitions

  • the present invention relates to a monitoring system, a monitoring method, and a monitoring program for a remote management system that remotely manages an image forming apparatus.
  • Patent Document 1 Japanese Patent Laid-Open No. 8-30152
  • Patent Document 2 Japanese Patent No. 6303875
  • Patent Document 3 Japanese Patent No. 6331778
  • Patent Document 4 Japanese Patent No. 2017-27124
  • an object of the present invention is to provide a monitoring system, a monitoring method, and a monitoring program capable of improving the stability of remote management of an image forming apparatus by the remote management system.
  • a monitoring system includes an information acquisition unit that acquires information from a remote management system that remotely manages an image forming apparatus, an information analysis unit that analyzes the information acquired by the information acquisition unit, and an analysis performed by the information analysis unit. And a result notifying unit for notifying the result of, the information analyzing unit detects a failure of the remote management system based on the information acquired by the information acquiring unit, and the result notifying unit is the information analyzing unit.
  • the remote management system is notified of a fault detected by the remote management system.
  • the monitoring system of the present invention notifies a failure of the remote management system when a failure occurs in the remote management system, so that appropriate measures can be taken for the remote management system. Therefore, the monitoring system of the present invention can improve the stability of remote management of the image forming apparatus by the remote management system.
  • the information acquisition unit may acquire information from at least one of the image forming apparatus and the ICT base on which the remote management system operates.
  • the monitoring system of the present invention performs remote management based on not only the information acquired from the remote management system but also the information acquired from at least one of the image forming apparatus and the ICT base on which the remote management system operates. Since the system failure is detected, the accuracy of detecting the failure of the remote management system can be improved.
  • the information analysis unit is a time series, the importance of the failure indicated by the information, the degree of similarity between the failure indicated by the information and a failure that occurred in the past, and the component from which the information is acquired.
  • the information may be sorted and analyzed according to at least one criterion as to whether or not a failure occurs simultaneously in different components.
  • the monitoring system of the present invention the time series, the importance of the failure indicated by the information, the degree of similarity of the failure indicated by the information with the failure that occurred in the past, and the component from which the information was acquired Since the information is sorted and analyzed according to at least one criterion as to whether or not a failure has occurred in different components at the same time, it is noticeable by human monitoring based on a huge amount of information acquired from a remote management system or the like. Difficult, remote management system failures can be detected.
  • the result notification unit is a notification destination set in association with this condition. May be notified of this failure.
  • the monitoring system of the present invention notifies the failure to the notification destination set in association with this condition when the detected failure satisfies the preset condition, so that it is appropriate according to the failure. It is possible to notify a human being of a disorder.
  • a monitoring method of the present invention using a computer and a storage unit includes an information acquisition step of acquiring information from a remote management system that remotely manages an image forming apparatus, and an information analysis step of analyzing the information acquired in the information acquisition step. And a result notifying step of notifying the result of the analysis in the information analyzing step, wherein the information analyzing step includes a step of detecting a failure of the remote management system based on the information acquired in the information acquiring step.
  • the result notifying step has a step of notifying a failure of the remote management system detected in the information analyzing step.
  • the monitoring method of the present invention notifies a failure of the remote management system when a failure occurs in the remote management system, so that appropriate measures can be taken for the remote management system. Therefore, the monitoring method of the present invention can improve the stability of remote management of the image forming apparatus by the remote management system.
  • a monitoring program includes an information acquisition unit that acquires information from a remote management system that remotely manages an image forming apparatus, an information analysis unit that analyzes the information acquired by the information acquisition unit, and an analysis performed by the information analysis unit.
  • the computer that executes the monitoring program of the present invention notifies the failure of the remote management system when a failure occurs in the remote management system, so that appropriate measures can be taken for the remote management system. it can. Therefore, the computer that executes the monitoring program of the present invention can improve the stability of remote management of the image forming apparatus by the remote management system.
  • the monitoring system, monitoring method, and monitoring program of the present invention can improve the stability of remote management of the image forming apparatus by the remote management system.
  • FIG. 1 is a block diagram of a system according to an embodiment of the present invention. It is a block diagram of the remote management system shown in FIG.
  • FIG. 2 is a block diagram of the monitoring system shown in FIG. 1 when configured with one computer.
  • 4 is a flowchart of the operation of the monitoring system shown in FIG. 3 when notifying the occurrence of a failure.
  • It is a block diagram of the 1st modification of the monitoring system shown in FIG. 1 at the time of comprising one computer.
  • It is a figure which shows an example of the cloud failure table shown in FIG.
  • FIG. shows an example of the temporary management table shown in FIG.
  • FIG. shows an example of the failure history table shown in FIG.
  • FIG. shows an example of the notification destination determination table shown in FIG.
  • 6 is a flowchart of the operation of the monitoring system shown in FIG. 5 when updating the cloud failure table. 6 is a flowchart of the operation of the monitoring system shown in FIG. 5 when notifying the occurrence of a failure. It is a block diagram of the 2nd modification of the monitoring system shown in FIG. 1 at the time of comprising one computer. 13 is a flowchart of the operation of the monitoring system shown in FIG. 12 when notifying the occurrence of a failure.
  • FIG. 14 is a flowchart continued from the flowchart shown in FIG. 13.
  • 15 is a flowchart of a modified example of the operation shown in FIGS. 13 and 14.
  • FIG. 1 is a block diagram of a system 10 according to this embodiment.
  • the system 10 includes a network 20 such as a LAN (Local Area Network) for customers of a company that manages image forming apparatuses (hereinafter referred to as “management company”).
  • the system 10 may include, in addition to the network 20, at least one network having the same configuration as the network 20.
  • the network 20 includes a firewall 21 that controls communication between the inside of the network 20 and the outside of the network 20, and an image forming apparatus 22.
  • the network 20 can include at least one image forming apparatus having the same configuration as the image forming apparatus 22.
  • the image forming apparatus in the network 20 is composed of, for example, an MFP (Multifunction Peripheral), a printer-dedicated machine, and the like, and is used by a customer of a management company.
  • the system 10 includes a remote management system 30 that remotely manages each image forming apparatus in the system 10.
  • the remote management system 30 is used by a management company.
  • the remote management system 30 may be composed of one computer or a plurality of computers.
  • the remote management system 30 will be described as operating on a public cloud cloud platform as an ICT (Information and Communication Technology) base.
  • the capacity of the server forming the remote management system 30 is increased as the number of image forming apparatuses connected to the remote management system 30 increases. , Flexibly expanded. Further, in the cloud platform on which the remote management system 30 operates, a part of the system may go down at a timing when the remote management system 30 does not understand due to system failure or maintenance of the cloud platform. Therefore, the remote management system 30 needs to take appropriate measures when a failure occurs in a component of the remote management system 30 for stable operation of the remote management system 30 itself. 30 own components need to be monitored.
  • the system 10 includes a cloud provider server 40 which is an endpoint provided by a provider of a cloud platform on which the remote management system 30 operates.
  • the system 10 includes a monitoring system 50 that monitors the remote management system 30.
  • the monitoring system 50 is used by a management company.
  • the monitoring system 50 may be composed of one computer or plural computers.
  • Each network in the system 10, the remote management system 30, the cloud provider server 40, and the monitoring system 50 can communicate with each other via the Internet 11.
  • FIG. 2 is a block diagram of the remote management system 30.
  • the remote management system 30 includes a command server 31 that issues control commands to the image forming apparatus.
  • the remote management system 30 can include at least one command server having the same configuration as the command server 31.
  • the command server can issue a control command that exceeds the firewall to the image forming apparatus.
  • one command server can be simultaneously connected to 4000 image forming apparatuses.
  • the remote management system 30 processes information necessary for management of the image forming apparatus transmitted from the image forming apparatus connected through the firewall, and connects to the command server appropriate for the image forming apparatus.
  • the device management server 32 for instructing to establish is, for example, a command server having the smallest number of image forming apparatuses to which the connection is established.
  • the remote management system 30 can include at least one device management server having the same configuration as the device management server 32. For example, one device management server can execute processing for 2000 image forming apparatuses per minute.
  • the remote management system 30 includes a load balancer 33 that distributes the load by allocating the information necessary for managing the image forming apparatus transmitted from the image forming apparatus connected through the firewall to an appropriate device management server. ing.
  • the remote management system 30 manages operations for performing various remote operations of the image forming apparatus, such as acquisition of various information from the image forming apparatus, updating of control software of the image forming apparatus, various settings of the image forming apparatus. It has a user management server 34 that receives information from users such as service persons of a trader. The command server maintains the image forming apparatus by transmitting the operation accepted by the user management server 34 to the image forming apparatus as a control command.
  • the remote management system 30 includes a database 35 and a cache server 36 that store various information collected from the image forming apparatus by the command server, such as a print counter of the image forming apparatus and information about authentication of the image forming apparatus.
  • FIG. 3 is a block diagram of the monitoring system 50 when it is configured by one computer.
  • the monitoring system 50 shown in FIG. 3 is an operation unit 51 that is an operation device such as a keyboard and a mouse to which various operations are input, and a display device such as an LCD (Liquid Crystal Display) that displays various information.
  • the display unit 52 a communication unit 53 that is a communication device that communicates with an external device directly via a network such as a LAN or the Internet, or directly by wire or wirelessly without a network, and stores various kinds of information.
  • a storage unit 54 that is a non-volatile storage device such as a semiconductor memory or an HDD (Hard Disk Drive), and a control unit 55 that controls the entire monitoring system 50 are provided.
  • the storage unit 54 stores a monitoring program 54a for monitoring the remote management system 30 (see FIG. 2).
  • the monitoring program 54a may be installed in the monitoring system 50 at the manufacturing stage of the monitoring system 50, or may be installed in an external device such as a CD (Compact Disk), a DVD (Digital Versatile Disk), or a USB (Universal Serial Bus) memory. It may be additionally installed in the monitoring system 50 from a storage medium, or may be additionally installed in the monitoring system 50 from a network.
  • the storage unit 54 stores a processing table 54b indicating processing according to a failure.
  • the control unit 55 can update the processing table 54b according to an instruction via the operation unit 51 or the communication unit 53.
  • the storage unit 54 can store a notification destination determination table 54c for determining the notification destination of the failure occurrence.
  • the notification destination determination table 54c is information associating the condition for notification of failure occurrence with the notification destination of failure occurrence.
  • the control unit 55 can update the notification destination determination table 54c according to an instruction via the operation unit 51 or the communication unit 53.
  • the control unit 55 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Memory) that is used as a work area of the CPU of the control unit 55. Access Memory).
  • the CPU of the control unit 55 executes the program stored in the storage unit 54 or the ROM of the control unit 55.
  • the control unit 55 executes the monitoring program 54a to acquire information from the components of the system 10, an information analysis unit 57 that analyzes the information acquired by the information acquisition unit 56, and an information analysis.
  • a result notification unit 58 that notifies the result of the analysis by the unit 57 is realized.
  • the information acquisition unit 56 includes an information acquisition adapter 56a that is a module for acquiring information from the components of the system 10.
  • the components of the system 10 include the image forming apparatus in the system 10, the components of the remote management system 30, and the cloud provider server 40.
  • the components of the remote management system 30 include a command server, a device management server, a user management server 34, a database 35, and a cache server 36.
  • the information acquisition unit 56 can include at least one information acquisition adapter having the same configuration as the information acquisition adapter 56a in addition to the information acquisition adapter 56a.
  • the information acquired from the image forming apparatus by the information acquisition adapter is, for example, information on whether the image forming apparatus is stopped or information on an error that has occurred in the image forming apparatus.
  • the information acquired from the constituent element of the remote management system 30 by the information acquisition adapter is, for example, information on whether this constituent element is stopped or information on an error that has occurred in this constituent element.
  • the information acquired from the cloud provider server 40 by the information acquisition adapter is, for example, information related to maintenance of the cloud platform on which the remote management system 30 operates, and information on whether or not this cloud platform is operating normally.
  • At least one of the components of the system 10, such as the image forming apparatus, the command server, the device management server, the user management server 34, the database 35, the cache server 36, and the cloud provider server 40 in the system 10, is connected to the monitoring system 50.
  • An agent for outputting information may be installed. The agent can output to the monitoring system 50 information for debugging the installed components and information on more detailed operation status of the installed components.
  • the information acquisition unit 56 includes an information acquisition processing unit 56b that acquires information by the information acquisition adapter. Since the information acquisition function of the information acquisition unit 56 is constructed by the information acquisition adapter, the information acquisition function can be flexibly expanded in accordance with the expansion of the function of the remote management system 30. Therefore, the monitoring system 50 can minimize the changes accompanying the functional expansion of the remote management system 30.
  • the information analysis unit 57 is acquired by the information acquisition unit 56, and a logic generation unit 57a that generates the information distribution logic acquired by the information acquisition unit 56 by a known learning algorithm such as machine learning, neurocomputing, and deep learning.
  • the information distribution unit 57b that distributes the generated information according to the logic generated by the logic generation unit 57a.
  • Examples of the information distribution logic generated by the logic generation unit 57a include, for example, a time-series information distribution logic, a failure information importance distribution logic, and a degree of similarity with a failure that occurred in the past.
  • the importance of the failure may be determined according to a specific rule, for example, based on at least one of the location of the failure and the frequency of occurrence of the failure.
  • the information analysis unit 57 includes a failure detection unit 57c that detects a failure of the remote management system 30 based on the information distributed by the information distribution unit 57b. For example, the information analysis unit 57 establishes communication between the image forming apparatus and the remote management system 30 based on the information acquired from the image forming apparatus in the system 10 and the information acquired from the components of the remote management system 30. Whether or not it can be detected. Further, the information analysis unit 57 performs the remote operation of the image forming apparatus correctly by the remote management system 30 based on the information acquired from the image forming apparatus in the system 10 and the information acquired from the components of the remote management system 30. It is possible to detect whether or not it has been broken. In addition, the information analysis unit 57 can detect whether the cloud platform on which the remote management system 30 operates is operating normally, based on the information acquired from the cloud provider server 40.
  • the information analysis unit 57 includes a process determination unit 57d that determines the process associated with the failure detected by the failure detection unit 57c in the processing table 54b.
  • the processing determined by the processing determination unit 57d includes, for example, restart of the remote management system 30, scale out of the cloud platform on which the remote management system 30 operates, data maintenance of the database 35, capacity increase of the database 35, remote There is disconnection of a server in which a problem occurs in the management system 30.
  • the result notification unit 58 When the failure analyzed by the information analysis section 57 satisfies the condition set in the notification destination determination table 54c, the result notification unit 58 notifies the notification destination set in the notification destination determination table 54c according to the failure.
  • a message transmission adapter 58a which is a module for transmitting a message indicating this failure, is provided.
  • the result notification unit 58 may send a message indicating the occurrence of a failure of which importance is lower than a specific importance to only a technician who can perform appropriate measures for the remote management system 30.
  • a message indicating that a failure having a higher importance than a specific importance has occurred is sent to the remote management system 30 not only by the technician who can execute appropriate measures but also by the management of the image forming apparatus. It may be sent to a wider range of stakeholders, such as existing distributors.
  • the result notification unit 58 is a command transmission adapter 58b that is a module for transmitting the processing command determined by the processing determination unit 57d to one of the remote management system 30 and the cloud provider server 40 that is suitable for this command. Is equipped with.
  • the result notification unit 58 includes a notification processing unit 58c that controls the message transmission adapter 58a and the command transmission adapter 58b.
  • the result notifying unit 58 has a notification function built by modules such as the message sending adapter 58a and the command sending adapter 58b, so that the notification function can be flexibly expanded according to the function expansion of the remote management system 30. be able to. Therefore, the monitoring system 50 can minimize the changes accompanying the functional expansion of the remote management system 30.
  • FIG. 4 is a flowchart of the operation of the monitoring system 50 when notifying the occurrence of a failure.
  • the control unit 55 of the monitoring system 50 executes the operation shown in FIG. 4 at a specific timing such as a regular timing such as every second.
  • the information acquisition processing unit 56b attempts to collect information from the components of the system 10 (S101).
  • the information distribution unit 57b distributes the information acquired in S101 by the logic generated by the logic generation unit 57a (S102).
  • the failure detection unit 57c attempts to detect a failure of the remote management system 30 based on the information distributed in S102 (S103). For example, when the load on the command server increases by a certain degree or more, the failure detection unit 57c determines that the number of image forming apparatuses connected to the command server decreases by a certain degree or more. It may be detected as a failure. In addition, when the load on the database 35 increases by a certain degree or more, the failure detecting unit 57c detects the failure of the data acquisition from the database 35 as a failure of the database 35 when the failure occurs by more than a certain degree. Is also good. The failure detection unit 57c predicts the occurrence of a failure of the remote management system 30 based on the information distributed in S102 by a known learning algorithm such as machine learning, neurocomputing, deep learning, etc. It is also possible to detect it before it occurs.
  • a known learning algorithm such as machine learning, neurocomputing, deep learning, etc. It is also possible to detect it before it occurs.
  • the failure detection unit 57c determines whether a failure of the remote management system 30 has been detected in S103 (S104).
  • the processing determination unit 57d determines the processing associated with the failure detected in S103 in the processing table 54b (S105).
  • the notification processing unit 58c determines whether the failure detected in S103 satisfies the condition set in the notification destination determination table 54c (S106).
  • the notification processing unit 58c determines in S106 that the failure detected in S103 does not satisfy the condition set in the notification destination determination table 54c, the operation illustrated in FIG. 4 ends.
  • the message transmission adapter 58a determines in S106 that the failure detected in S103 satisfies the condition set in the notification destination determination table 54c, the message transmission adapter 58a sets the failure in the notification destination determination table 54c according to the failure. A message indicating this failure is transmitted to the notified notification destination (S107).
  • the command transmission adapter 58b transmits the processing command determined in S105 to one of the remote management system 30 and the cloud provider server 40 that is suitable for this command (S108), and the operation shown in FIG. To finish.
  • the monitoring system 50 has transmitted the processing command determined in S105 in S108, the monitoring system 50 does not execute the processing in S108 and sends a message including the contents of the processing determined in S105. You may transmit in S107.
  • the monitoring system 50 when the remote management system 30 has a failure (YES in S104), the monitoring system 50 notifies the remote management system 30 of the failure (S107). Appropriate action can be taken. Therefore, the monitoring system 50 can improve the stability of remote management of the image forming apparatus by the remote management system 30.
  • the monitoring system 50 uses the information acquired from the remote management system 30 as well as the information acquired from at least one of the image forming apparatus and the cloud platform on which the remote management system 30 operates to detect a failure of the remote management system 30. Is detected (S101 to S103), it is possible to improve the accuracy of detecting a failure of the remote management system 30.
  • the monitoring system 50 uses the time series, the importance of the failure indicated by the information, the similarity between the failure indicated by the information and the failure that occurred in the past, and the failure at the same time as the constituent element different from the constituent element from which the information is acquired. Since information is sorted and analyzed according to at least one criterion as to whether or not the occurrence has occurred (S102 to S103), it is noticeable by human monitoring based on the huge amount of information acquired from the remote management system 30 or the like. It is possible to detect a difficult failure of the remote management system 30.
  • the monitoring system 50 When the detected failure satisfies the preset condition (YES in S106), the monitoring system 50 notifies the notification destination set in association with this condition of this failure (S107). You can notify the appropriate person of the failure.
  • the monitoring system 50 is realized by a computer different from the remote management system 30 in this embodiment. However, at least some of the computers that implement the remote management system 30 and at least some of the computers that implement the monitoring system 50 may be the same.
  • the monitoring system 50 of the present modified example is capable of storing a further table in addition to the table stored in the storage unit 54 in the above-described embodiment, and the information acquisition unit 56 uses the stored table.
  • the information analysis unit 57 and notification by the result notification unit 58 uses the stored table.
  • the storage unit 54 can store a cloud failure table 54c indicating a failure that has occurred in the cloud platform on which the remote management system 30 operates.
  • FIG. 6 is a diagram showing an example of the cloud failure table 54c.
  • the cloud failure table 54c shown in FIG. 6 is created based on failure information collected from the cloud platform on which the remote management system 30 operates.
  • the cloud failure table 54c illustrated in FIG. 6 includes the original text of the failure content collected from the cloud platform on which the remote management system 30 operates, the failure location, the failure area, the failure code indicating the failure, and the failure code. The start date and time and the end date and time of the failure are shown for each failure.
  • the storage unit 54 can store a temporary management table 54d for temporarily managing a failure that has occurred in the remote management system 30.
  • FIG. 7 is a diagram showing an example of the temporary management table 54d.
  • the original text of the content of the failure collected from the remote management system 30 the location of the failure, the area where the failure occurred, the importance of the failure, and the cause of the failure are displayed in the remote management system 30.
  • the location of the failure factor, the failure detection date and time, and the degree of similarity with other failures that occurred in the past are shown.
  • the temporary management table 54d shown in FIG. 5 the importance of the failure, the location of the factor, and the similarity of which the detection date and time is “2018/1522 15:00” are omitted.
  • the storage unit 54 can store a failure history table 54e indicating a history of failures that have occurred in the remote management system 30.
  • FIG. 8 is a diagram showing an example of the failure history table 54e.
  • the failure history table 54e shown in FIG. 8 includes the original text of the failure content collected from the remote management system 30, the location of the failure, the area where the failure occurred, the importance of the failure, the location of the failure factor, and the failure. The detection date and time and the similarity with other failures that occurred in the past are shown for each failure.
  • the storage unit 54 can store a notification destination determination table 54f for determining the notification destination of the failure occurrence.
  • FIG. 9 is a diagram showing an example of the notification destination determination table 54f.
  • the notification destination determination table 54f shown in FIG. 9 is a combination of the location of the failure, the area where the failure occurs, the importance of the failure, the location of the cause of the failure, and the similarity with other failures that occurred in the past.
  • the notification destination of failure occurrence and the content of notification of failure occurrence are shown for each condition of notification of failure occurrence.
  • a range may be set as the importance of the failure, such as 50 or more and less than 60.
  • a range may be set for the similarity as well as the importance.
  • the location of the cause of failure may be set by distinguishing whether it is inside or outside the remote management system 30, or inside or outside the remote management system 30.
  • the location, the occurrence area, the importance, and the similarity are "Service A”, “US”, “50 or more and less than 60", and "60” in the notification condition. “Location” is set so that it may be inside or outside the remote management system 30.
  • the control unit 55 shown in FIG. 5 can update the notification destination determination table 54f in accordance with an instruction via the operation unit 51 or the communication unit 53.
  • the result notification unit 58 of the present modified example responds to the failure by the notification destination determination table 54f.
  • a message sending adapter 58a which is a module for sending a message indicating this failure, is provided at the notification destination set to.
  • the result notification unit 58 may send a message indicating the occurrence of a failure of which importance is lower than a specific importance to only a technician who can perform appropriate measures for the remote management system 30.
  • a message indicating that a failure having a higher importance than a specific importance has occurred is sent to the remote management system 30 not only by the technician who can execute appropriate measures but also by the management of the image forming apparatus. It may be sent to a wider range of stakeholders, such as existing distributors.
  • FIG. 10 is a flowchart of the operation of the monitoring system 50 when updating the cloud failure table 54c.
  • control unit 55 of the monitoring system 50 executes the operation shown in FIG. 10 at a specific timing, such as a regular timing such as every second.
  • the information acquisition unit 56 attempts to collect, from the cloud provider server 40, information on a failure that has occurred in the cloud platform on which the remote management system 30 operates (S111).
  • the failure detection unit 57c determines whether or not failure information has been collected in S111 (S112).
  • the failure detection unit 57c determines in S112 that the failure information has been collected, the failure detection unit 57c adds the failure information collected in S111 to the cloud failure table 54c (S113).
  • the fault detection unit 57c terminates the operation shown in FIG. 10 when it determines in S112 that fault information has not been collected or when the process of S113 ends.
  • FIG. 11 is a flowchart of the operation of the monitoring system 50 when notifying the occurrence of a failure.
  • the control unit 55 of the monitoring system 50 executes the operation shown in FIG. 11 at a specific timing, such as a regular timing such as every second.
  • the information acquisition processing unit 56b attempts to collect information from the image forming apparatus in the system 10 and the constituent elements of the remote management system 30 (S121).
  • the failure detection unit 57c determines whether or not the information indicating the failure of the remote management system 30 has been collected in S121 (S122).
  • the failure detection unit 57c determines in S122 that the information indicating the failure of the remote management system 30 has been collected, the failure detection unit 57c adds the failure information determined in S122 to the temporary management table 54d (S123).
  • the failure added to the temporary management table 54d in S123 is important just after the end of the processing in S123, such as the failure whose detection date and time is "2018/03/22 15:00" shown in FIG.
  • the degree, the location of the factor, and the degree of similarity are not yet remembered.
  • the failure detection unit 57c determines another failure that occurred in the past based on the failure information added to the temporary management table 54d in S123 and the past failure information shown in the failure history table 54e.
  • the similarity of the fault added to the temporary management table 54d in S123 is determined according to a specific determination method (S124).
  • the determination method in S124 may be, for example, a method using a known learning process algorithm such as known statistical processing or machine learning, neuro-computing, deep learning, or the like.
  • the failure detection unit 57c adds the similarity determined in S124 to the failure information added to the temporary management table 54d in S123 (S125).
  • the failure detection unit 57c determines the importance of the failure added to the temporary management table 54d in S123 according to a specific determination method (S126).
  • the determination method in S126 may be, for example, a method of determining according to a specific rule, based on at least one of the location of the failure and the frequency of occurrence of the failure.
  • the failure detection unit 57c adds the degree of importance determined in S126 to the failure information added to the temporary management table 54d in S123 (S127).
  • the failure detection unit 57c corresponds to the failure added to the temporary management table 54d in S123 based on the failure information added to the temporary management table 54d in S123 and the failure information shown in the cloud failure table 54c. It is determined whether the failure is related to the failure shown in the cloud failure table 54c, that is, the failure of the cloud platform on which the remote management system 30 operates (S128). That is, when the failure location, occurrence area, and detection date and time of the failure added to the temporary management table 54d in S123 are included in the information of any failure shown in the cloud failure table 54c, the failure detection unit 57c performs temporary management in S123. It is determined in S128 that the failure added to the table 54d is related to the failure shown in the cloud failure table 54c.
  • the failure detection unit 57c determines that the location, the occurrence area, and the detection date and time shown in FIG. 7 are “Service A”, “US”, and “2018/1522 15:00”, respectively.
  • the original text, the area of occurrence, the start date and time and the end date and time are "Service A has failed.”, "US”, “2018/1522 14:00” and “2018/1522 16:00", respectively. Determined to be related to a disorder.
  • the failure detection unit 57c determines that a specific time has elapsed after the processing of S127. After that, the process of S128 may be executed.
  • the failure detection unit 57c determines in S128 that the failure corresponding to the failure added to the temporary management table 54d in S123 is related to the failure of the cloud platform on which the remote management system 30 operates, the failure cause is the remote management system 30.
  • the fact that it is external is stored as the location of the cause of failure added to the temporary management table 54d in S123 (S129).
  • the failure detection unit 57c determines in S128 that the failure corresponding to the failure added to the temporary management table 54d in S123 is not related to the failure of the cloud platform on which the remote management system 30 operates, the cause of the failure is the remote management system 30. Is stored as the location of the failure factor added to the temporary management table 54d in S123 (S130).
  • the failure detection unit 57c moves the failure added to the temporary management table 54d in S123 to the failure history table 54e (S131). That is, the failure detection unit 57c reflects all the current information of the failure added to the temporary management table 54d in S123 on the failure history table 54e, and all the failure information added to the temporary management table 54d in S123 at the current time. Information is deleted from the temporary management table 54d. ..
  • the notification processing unit 58c determines the failure moved to the failure history table 54e in S131 based on the failure information moved to the failure history table 54e in S131 and the notification destination determination table 54f.
  • the notification destination of the failure occurrence and the notification content of the failure occurrence set in the notification destination determination table 54f are determined (S132). That is, the notification processing unit 58c indicates the location of the failure, the area where the failure occurred, the importance of the failure, the location of the cause of the failure, and other failures that occurred in the past, which are indicated in the notification destination determination table 54f.
  • the notification processing unit 58c may notify only a technician who can execute appropriate measures to the remote management system 30 regarding a failure whose importance level is lower than a specific importance level.
  • the notification processing unit 58c After the processing of S132, the notification processing unit 58c notifies the notification destination determined in S132 with the notification content determined in S132 (S133).
  • the notification processing unit 58c may include various kinds of information in the failure history table 54e regarding the failure moved to the failure history table 54e in S131 in the notification content notified in S133.
  • the notification processing unit 58c moves to the failure history table 54e in S131 whether the location of the cause of the failure moved to the failure history table 54e in S131 is outside the remote management system 30. The determination is made based on the location of the factor of the failure (S134).
  • the notification processing unit 58c determines in S134 that the location of the cause of the failure moved to the failure history table 54e in S131 is outside the remote management system 30, it notifies the provider of the cloud platform on which the remote management system 30 operates. Then, a support request for notifying the content of the failure is issued (S135).
  • the notification processing unit 58c determines in S134 that the location of the failure factor moved to the failure history table 54e in S131 is not outside the remote management system 30 or when the processing of S135 ends, the operation shown in FIG. finish.
  • the monitoring system 50 of the present modification when a failure occurs in the remote management system 30 (YES in S122), the failure of the remote management system 30 is appropriately determined according to the importance of this failure. Since the notification is sent to the appropriate notification destination (S132 to S133), appropriate measures can be taken for the remote management system 30. Therefore, the monitoring system 50 can improve the stability of remote management of the image forming apparatus by the remote management system 30.
  • the monitoring system 50 detects a failure of the remote management system 30 based not only on the information acquired from the remote management system 30 but also on the information acquired from the image forming apparatus (S121 to S122). The accuracy of detecting a failure of the remote management system 30 can be improved.
  • the monitoring system 50 detects the failure of the remote management system 30 based not only on the information acquired from the remote management system 30 but also on the information acquired from the cloud platform on which the remote management system 30 operates (S121 to S122). Therefore, the accuracy of detecting a failure of the remote management system 30 can be improved.
  • the monitoring system 50 sends a support request for notifying the content of the failure to the provider of the cloud platform. Since it is issued to the remote management system 30 (S135), the possibility that appropriate measures will be taken for the cloud platform on which the remote management system 30 operates increases, and as a result, the stability of remote management of the image forming apparatus by the remote management system 30 is improved. Can be improved.
  • the monitoring system 50 When the location of the cause of failure of the remote management system 30 is outside the remote management system 30 (YES in S134), the monitoring system 50 notifies the provider of the cloud platform on which the remote management system 30 operates of the failure. Since the support request for notifying the contents is issued (S135), it is possible to prompt the cloud platform provider to promptly recover from the failure of the cloud platform. However, the monitoring system 50 may end the operation illustrated in FIG. 11 without executing the processes of S134 and S135 after the process of S133.
  • the conditions for notification of the occurrence of a failure in the notification destination determination table 54f include the location of the failure, the area where the failure occurs, the importance of the failure, the location of the cause of the failure, and the location of the past occurrence. It includes the degree of similarity with other obstacles that have occurred.
  • the conditions of notification of occurrence of a failure include at least the location of the failure, the area where the failure occurs, the importance of the failure, the location of the cause of the failure, and the similarity with other failures that occurred in the past. One may not be included.
  • the monitoring system 50 is realized by a computer different from the remote management system 30.
  • the computers that implement the remote management system 30 and at least some of the computers that implement the monitoring system 50 may be the same.
  • the monitoring system 50 of the present modification makes it possible to further store a failure treatment table in the storage unit 54 of the first modification, and uses the table stored in the storage unit to store information on the information collected by the information acquisition unit 56.
  • the analysis by the analysis unit 57 and the notification by the result notification unit 58 are performed, and a predetermined action is automatically executed to the remote management system according to the analysis result.
  • the same components as those of the above-described embodiment and the first modification are designated by the same reference numerals, and the description thereof will be omitted here.
  • the storage unit 54 is capable of storing a failure treatment table 54g that indicates a failure action for each failure.
  • the control unit 55 can update the failure treatment table 54g according to an instruction via the operation unit 51 or the communication unit 53.
  • 13 and 14 are flowcharts of the operation of the monitoring system 50 in the case of notifying the occurrence of a failure in this modification. Since the operation of the monitoring system 50 when updating the cloud failure table 54c is the same as that of the first modification, its description is omitted in this modification.
  • the control unit 55 of the monitoring system 50 executes the operation shown in FIGS. 13 and 14 at a specific timing, such as a regular timing such as every second.
  • Steps S121 to S131 are the same as those of the first modified example, and therefore the description thereof is omitted here.
  • the notification processing unit 58c determines the failure moved to the failure history table 54e in S131 based on the failure information moved to the failure history table 54e in S131 and the notification destination determination table 54f.
  • the notification destination of the failure occurrence set in the notification destination determination table 54f is determined (S132). That is, the notification processing unit 58c selects the failure in S131 from the combinations of the failure location, the failure occurrence area, the failure importance, and the failure factor location shown in the notification destination determination table 54f.
  • the notification processing unit 58c may notify only a technician who can execute appropriate measures to the remote management system 30 regarding a failure whose importance level is lower than a specific importance level.
  • a failure whose degree is higher than a certain degree of importance not only a technician who can perform appropriate measures for the remote management system 30 but also a wider range of interests such as a sales company that manages the image forming apparatus.
  • the person concerned may be the notification destination.
  • the notification processing unit 58c determines whether or not the similarity of the failure moved to the failure history table 54e in S131 with other failures that occurred in the past is equal to or higher than the first similarity. Yes (S136).
  • the failure determined in S133 that the similarity to the failure moved to the failure history table 54e in S131 is equal to or higher than the first similarity. Is displayed in the failure treatment table 54g (S137).
  • the notification processing unit 58c determines in S137 that the failure determined in S136 that the similarity to the failure moved to the failure history table 54e in S131 is equal to or higher than the first similarity is indicated in the failure treatment table 54g. Then, in the remote management system 30, the fault management table 30g associates the fault determined in S136 with the fault that has been moved to the fault history table 54e in S131 and has a similarity not lower than the first similarity. On the other hand, it is automatically executed (S138).
  • the notification processing unit 58c includes, in the notification content scheduled to be notified to the notification destination determined in S132, the fact that the appropriate action has been performed (S1369).
  • the notification processing unit 58c determines in S136 that the similarity is not equal to or higher than the first similarity, the similarity of the failure moved to the failure history table 54e in S131 to the other failure that occurred in the past is the second similarity. It is determined whether it is less than (S140).
  • the second similarity may be equal to or lower than the first similarity.
  • the notification processing unit 58c determines in S140 that the degree of similarity is less than the second similarity, the notification processing unit 58c includes, in the notification content scheduled to be notified to the notification destination determined in S132, a serious failure that has not been experienced in the past. (S141).
  • the notification processing unit 58c determines in S137 that the failure determined in S136 that the similarity to the failure moved to the failure history table 54e in S131 is equal to or higher than the first similarity is not indicated in the failure treatment table 54g. Then, the process of S139 is performed, it is determined in S140 that the degree of similarity is not less than the second similarity, or when the process of S141 is performed, the notification destination determined in S132 is notified to the notification destination indicating that a failure has occurred. Notify (S142).
  • the notification processing unit 58c may include various information in the failure history table 54e regarding the failure moved to the failure history table 54e in S131 in the notification content notified in S142.
  • the notification processing unit 58c when the processing of S139 has been executed, the notification processing unit 58c includes, in the notification content of which the notification is performed in S142, that the appropriate treatment has been executed. In addition, when the processing of S141 has been executed, the notification processing unit 58c includes in the notification content of which the notification in S142 is a serious failure that has not been experienced in the past.
  • the notification processing unit 58c moves to the failure history table 54e in S131 whether the location of the cause of the failure moved to the failure history table 54e in S131 is outside the remote management system 30. The determination is made based on the location of the factor of the failure (S143).
  • the notification processing unit 58c determines in S143 that the location of the cause of the failure moved to the failure history table 54e in S131 is outside the remote management system 30, the notification processing unit 58c informs the provider of the cloud platform on which the remote management system 30 operates. Then, a support request for notifying the content of the failure is issued (S144).
  • the notification processing unit 58c determines in S143 that the location of the cause of the failure moved to the failure history table 54e in S131 is not outside the remote management system 30, or when the processing in S144 ends, the notification processing section 58c is displayed as shown in FIGS. The operation shown is ended.
  • the monitoring system 50 regards the failure of the remote management system 30 as a degree of similarity between this failure and a failure that occurred in the past. Since notification is made with the notification content according to (S136 to S142), appropriate measures can be taken for the remote management system 30. Therefore, the monitoring system 50 can improve the stability of remote management of the image forming apparatus by the remote management system 30.
  • the monitoring system 50 responds to the failure that occurred in the past and is similar to the failure of the remote management system 30. Since the attached procedure is executed (S138), an appropriate procedure can be taken for the remote management system 30.
  • the monitoring system 50 Since the monitoring system 50 notifies the remote management system 30 of a fault having a low degree of similarity to a fault that has occurred in the past (YES in S140), it notifies that the fault is a serious one (S141 to S142). Appropriate measures can be promptly taken for serious disabilities that have never been experienced before.
  • the monitoring system 50 determines the degree of similarity between the failure of the remote management system 30 and the failure that occurred in the past by using a specific learning algorithm (S124), so that convenience can be improved.
  • the monitoring system 50 detects a failure of the remote management system 30 based on not only the information acquired from the remote management system 30 but also the information acquired from the image forming apparatus and the cloud platform on which the remote management system 30 operates ( Since S121 to S122), the accuracy of detecting a failure of the remote management system 30 can be improved.
  • the monitoring system 50 may execute the operation shown in FIG. 15 instead of the operation shown in FIG.
  • the operation shown in FIG. 15 is to execute the processing of S151 instead of the processing of S138 and the processing of S139 in the operation shown in FIG. That is, in the operation illustrated in FIG. 15, the notification processing unit 58c determines in step S133 that the similarity to the failure moved to the failure history table 54e in step S131 is equal to or higher than the first similarity. If it is determined in S134 that the failure is indicated in step S134, the failure determined in S136 that the similarity to the failure moved to the failure history table 54e in S131 is equal to or higher than the first similarity is associated in the failure treatment table 54g. The specified action is included in the notification content scheduled to be notified to the notification destination determined in S132 (S151), and the process of S142 is executed.
  • the monitoring system 50 responds to the failure that occurred in the past and is similar to the failure of the remote management system 30.
  • appropriate action can be taken to the remote management system 30.
  • the conditions for notification of failure occurrence in the notification destination determination table 54f include the location of the failure, the area where the failure occurred, the importance of the failure, and the location of the cause of the failure.
  • the condition of the notification of the occurrence of the failure may not include at least one of the location of the failure, the area where the failure occurs, the importance of the failure, and the location of the cause of the failure.
  • the monitoring system 50 determines the notification destination of the notification in S142 in S132. However, the monitoring system 50 may always use the operation manager of the remote management system 30 as the notification destination of the notification in S142.
  • the monitoring system 50 is realized by a computer different from the remote management system 30.
  • the computers that implement the remote management system 30 and at least some of the computers that implement the monitoring system 50 may be the same.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Quality & Reliability (AREA)
  • Debugging And Monitoring (AREA)
  • Computer And Data Communications (AREA)

Abstract

Provided are a monitoring system, a monitoring method, and a monitoring program with which it is possible to improve the stability of remote management of an image forming device employing a remote management system. This monitoring system is characterized in that: information is acquired from a remote management system for remote management of an image forming device; a failure of the remote management system is detected by analyzing the acquired information; and a notification of the detected failure of the remote management system is issued.

Description

監視システム、監視方法および監視プログラムMonitoring system, monitoring method, and monitoring program
 本発明は、画像形成装置を遠隔管理する遠隔管理システムの監視システム、監視方法および監視プログラムに関する。 The present invention relates to a monitoring system, a monitoring method, and a monitoring program for a remote management system that remotely manages an image forming apparatus.
 従来、画像形成装置の障害を検出する遠隔管理システムが知られている(例えば、特許文献1-4参照。)。 Conventionally, a remote management system that detects a failure of an image forming apparatus is known (for example, refer to Patent Documents 1-4).
  特許文献1:特開平8-30152号公報
  特許文献2:特許第6303875号公報
  特許文献3:特許第6331778号公報
  特許文献4:特開2017-27124号公報
Patent Document 1: Japanese Patent Laid-Open No. 8-30152 Patent Document 2: Japanese Patent No. 6303875 Japanese Patent Document 3: Japanese Patent No. 6331778 Japanese Patent Document 4: Japanese Patent No. 2017-27124
 しかしながら、従来の技術においては、遠隔管理システムの障害を検出することができないので、遠隔管理システムに障害が発生した場合に、遠隔管理システムによって画像形成装置を遠隔管理することができないという問題がある。 However, in the conventional technique, a failure of the remote management system cannot be detected. Therefore, when a failure occurs in the remote management system, the remote management system cannot remotely manage the image forming apparatus. ..
 そこで、本発明は、遠隔管理システムによる画像形成装置の遠隔管理の安定性を向上することができる監視システム、監視方法および監視プログラムを提供することを目的とする。 Therefore, an object of the present invention is to provide a monitoring system, a monitoring method, and a monitoring program capable of improving the stability of remote management of an image forming apparatus by the remote management system.
 本発明の監視システムは、画像形成装置を遠隔管理する遠隔管理システムから情報を取得する情報取得部と、前記情報取得部によって取得された情報を分析する情報分析部と、前記情報分析部による分析の結果を通知する結果通知部とを備え、前記情報分析部は、前記情報取得部によって取得された情報に基づいて前記遠隔管理システムの障害を検出し、前記結果通知部は、前記情報分析部によって検出された、前記遠隔管理システムの障害を通知することを特徴とする。 A monitoring system according to the present invention includes an information acquisition unit that acquires information from a remote management system that remotely manages an image forming apparatus, an information analysis unit that analyzes the information acquired by the information acquisition unit, and an analysis performed by the information analysis unit. And a result notifying unit for notifying the result of, the information analyzing unit detects a failure of the remote management system based on the information acquired by the information acquiring unit, and the result notifying unit is the information analyzing unit. The remote management system is notified of a fault detected by the remote management system.
 この構成により、本発明の監視システムは、遠隔管理システムに障害が発生した場合に、遠隔管理システムの障害を通知するので、遠隔管理システムに対して適切な処置が講じられることができる。したがって、本発明の監視システムは、遠隔管理システムによる画像形成装置の遠隔管理の安定性を向上することができる。 With this configuration, the monitoring system of the present invention notifies a failure of the remote management system when a failure occurs in the remote management system, so that appropriate measures can be taken for the remote management system. Therefore, the monitoring system of the present invention can improve the stability of remote management of the image forming apparatus by the remote management system.
 本発明の監視システムにおいて、前記情報取得部は、前記画像形成装置と、前記遠隔管理システムが動作するICT基盤との少なくとも1つからも情報を取得しても良い。 In the monitoring system of the present invention, the information acquisition unit may acquire information from at least one of the image forming apparatus and the ICT base on which the remote management system operates.
 この構成により、本発明の監視システムは、遠隔管理システムから取得した情報だけでなく、画像形成装置と、遠隔管理システムが動作するICT基盤との少なくとも1つから取得した情報にも基づいて遠隔管理システムの障害を検出するので、遠隔管理システムの障害の検出の精度を向上することができる。 With this configuration, the monitoring system of the present invention performs remote management based on not only the information acquired from the remote management system but also the information acquired from at least one of the image forming apparatus and the ICT base on which the remote management system operates. Since the system failure is detected, the accuracy of detecting the failure of the remote management system can be improved.
 本発明の監視システムにおいて、前記情報分析部は、時系列と、情報が示す障害の重要度と、情報が示す障害の、過去に発生した障害との類似度と、情報が取得された構成要素とは異なる構成要素で同時に障害が発生しているか否かとの少なくとも1つの基準によって情報を振り分けて分析しても良い。 In the monitoring system of the present invention, the information analysis unit is a time series, the importance of the failure indicated by the information, the degree of similarity between the failure indicated by the information and a failure that occurred in the past, and the component from which the information is acquired. The information may be sorted and analyzed according to at least one criterion as to whether or not a failure occurs simultaneously in different components.
 この構成により、本発明の監視システムは、時系列と、情報が示す障害の重要度と、情報が示す障害の、過去に発生した障害との類似度と、情報が取得された構成要素とは異なる構成要素で同時に障害が発生しているか否かとの少なくとも1つの基準によって情報を振り分けて分析するので、遠隔管理システムなどから取得した膨大な数量の情報に基づいて、人間による監視では気付くのが困難な、遠隔管理システムの障害を検出することができる。 With this configuration, the monitoring system of the present invention, the time series, the importance of the failure indicated by the information, the degree of similarity of the failure indicated by the information with the failure that occurred in the past, and the component from which the information was acquired Since the information is sorted and analyzed according to at least one criterion as to whether or not a failure has occurred in different components at the same time, it is noticeable by human monitoring based on a huge amount of information acquired from a remote management system or the like. Difficult, remote management system failures can be detected.
 本発明の監視システムにおいて、前記結果通知部は、前記情報分析部によって分析された、前記遠隔管理システムの障害が予め設定された条件を満たす場合に、この条件に対応付けて設定された通知先に、この障害を通知しても良い。 In the monitoring system of the present invention, when the failure of the remote management system analyzed by the information analysis unit satisfies a preset condition, the result notification unit is a notification destination set in association with this condition. May be notified of this failure.
 この構成により、本発明の監視システムは、検出した障害が予め設定された条件を満たす場合に、この条件に対応付けて設定された通知先に、この障害を通知するので、障害に応じた適切な人間に障害を通知することができる。 With this configuration, the monitoring system of the present invention notifies the failure to the notification destination set in association with this condition when the detected failure satisfies the preset condition, so that it is appropriate according to the failure. It is possible to notify a human being of a disorder.
 コンピューターと記憶部とを用いる本発明の監視方法は、画像形成装置を遠隔管理する遠隔管理システムから情報を取得する情報取得工程と、前記情報取得工程で取得された情報を分析する情報分析工程と、前記情報分析工程での分析の結果を通知する結果通知工程とを含み、前記情報分析工程は、前記情報取得工程で取得された情報に基づいて前記遠隔管理システムの障害を検出する工程を有し、前記結果通知工程は、前記情報分析工程で検出された、前記遠隔管理システムの障害を通知する工程を有することを特徴とする。 A monitoring method of the present invention using a computer and a storage unit includes an information acquisition step of acquiring information from a remote management system that remotely manages an image forming apparatus, and an information analysis step of analyzing the information acquired in the information acquisition step. And a result notifying step of notifying the result of the analysis in the information analyzing step, wherein the information analyzing step includes a step of detecting a failure of the remote management system based on the information acquired in the information acquiring step. However, the result notifying step has a step of notifying a failure of the remote management system detected in the information analyzing step.
 この構成により、本発明の監視方法は、遠隔管理システムに障害が発生した場合に、遠隔管理システムの障害を通知するので、遠隔管理システムに対して適切な処置が講じられることができる。したがって、本発明の監視方法は、遠隔管理システムによる画像形成装置の遠隔管理の安定性を向上することができる。 With this configuration, the monitoring method of the present invention notifies a failure of the remote management system when a failure occurs in the remote management system, so that appropriate measures can be taken for the remote management system. Therefore, the monitoring method of the present invention can improve the stability of remote management of the image forming apparatus by the remote management system.
 本発明の監視プログラムは、画像形成装置を遠隔管理する遠隔管理システムから情報を取得する情報取得部と、前記情報取得部によって取得された情報を分析する情報分析部と、前記情報分析部による分析の結果を通知する結果通知部とをコンピューターに実現させ、前記情報分析部は、前記情報取得部によって取得された情報に基づいて前記遠隔管理システムの障害を検出し、前記結果通知部は、前記情報分析部によって検出された、前記遠隔管理システムの障害を通知することを特徴とする。 A monitoring program according to the present invention includes an information acquisition unit that acquires information from a remote management system that remotely manages an image forming apparatus, an information analysis unit that analyzes the information acquired by the information acquisition unit, and an analysis performed by the information analysis unit. A result notifying unit for notifying the result of the computer, the information analyzing unit detects a failure of the remote management system based on the information acquired by the information acquiring unit, and the result notifying unit, It is characterized in that a failure of the remote management system detected by the information analysis unit is notified.
 この構成により、本発明の監視プログラムを実行するコンピューターは、遠隔管理システムに障害が発生した場合に、遠隔管理システムの障害を通知するので、遠隔管理システムに対して適切な処置が講じられることができる。したがって、本発明の監視プログラムを実行するコンピューターは、遠隔管理システムによる画像形成装置の遠隔管理の安定性を向上することができる。 With this configuration, the computer that executes the monitoring program of the present invention notifies the failure of the remote management system when a failure occurs in the remote management system, so that appropriate measures can be taken for the remote management system. it can. Therefore, the computer that executes the monitoring program of the present invention can improve the stability of remote management of the image forming apparatus by the remote management system.
 本発明の監視システム、監視方法および監視プログラムは、遠隔管理システムによる画像形成装置の遠隔管理の安定性を向上することができる。 The monitoring system, monitoring method, and monitoring program of the present invention can improve the stability of remote management of the image forming apparatus by the remote management system.
本発明の一実施の形態に係るシステムのブロック図である。1 is a block diagram of a system according to an embodiment of the present invention. 図1に示す遠隔管理システムのブロック図である。It is a block diagram of the remote management system shown in FIG. 1台のコンピューターによって構成される場合の図1に示す監視システムのブロック図である。FIG. 2 is a block diagram of the monitoring system shown in FIG. 1 when configured with one computer. 障害の発生を通知する場合の図3に示す監視システムの動作のフローチャートである。4 is a flowchart of the operation of the monitoring system shown in FIG. 3 when notifying the occurrence of a failure. 1台のコンピューターによって構成される場合の図1に示す監視システムの第1の変形例のブロック図である。It is a block diagram of the 1st modification of the monitoring system shown in FIG. 1 at the time of comprising one computer. 図5に示すクラウド障害テーブルの一例を示す図である。It is a figure which shows an example of the cloud failure table shown in FIG. 図5に示す一時管理テーブルの一例を示す図である。It is a figure which shows an example of the temporary management table shown in FIG. 図5に示す障害履歴テーブルの一例を示す図である。It is a figure which shows an example of the failure history table shown in FIG. 図5に示す通知先決定用テーブルの一例を示す図である。It is a figure which shows an example of the notification destination determination table shown in FIG. クラウド障害テーブルを更新する場合の図5に示す監視システムの動作のフローチャートである。6 is a flowchart of the operation of the monitoring system shown in FIG. 5 when updating the cloud failure table. 障害の発生を通知する場合の図5に示す監視システムの動作のフローチャートである。6 is a flowchart of the operation of the monitoring system shown in FIG. 5 when notifying the occurrence of a failure. 1台のコンピューターによって構成される場合の図1に示す監視システムの第2の変形例のブロック図である。It is a block diagram of the 2nd modification of the monitoring system shown in FIG. 1 at the time of comprising one computer. 障害の発生を通知する場合の図12に示す監視システムの動作のフローチャートである。13 is a flowchart of the operation of the monitoring system shown in FIG. 12 when notifying the occurrence of a failure. 図13に示すフローチャートの続きのフローチャートである。FIG. 14 is a flowchart continued from the flowchart shown in FIG. 13. 図13および図14に示す動作の変形例のフローチャートである。15 is a flowchart of a modified example of the operation shown in FIGS. 13 and 14.
 以下、本発明の実施の形態について、図面を用いて説明する。 Embodiments of the present invention will be described below with reference to the drawings.
 まず、本発明の一実施の形態に係るシステムの構成について説明する。 First, the configuration of the system according to the embodiment of the present invention will be described.
 図1は、本実施の形態に係るシステム10のブロック図である。 FIG. 1 is a block diagram of a system 10 according to this embodiment.
 図1に示すように、システム10は、画像形成装置を管理する業者(以下「管理業者」という。)の客のLAN(Local Area Network)などのネットワーク20を備えている。システム10は、ネットワーク20以外にも、ネットワーク20と同様の構成のネットワークを少なくとも1つ備えることが可能である。 As shown in FIG. 1, the system 10 includes a network 20 such as a LAN (Local Area Network) for customers of a company that manages image forming apparatuses (hereinafter referred to as “management company”). The system 10 may include, in addition to the network 20, at least one network having the same configuration as the network 20.
 ネットワーク20は、ネットワーク20の内部と、ネットワーク20の外部との間の通信を制御するファイアウォール21と、画像形成装置22とを備えている。ネットワーク20は、画像形成装置22以外にも、画像形成装置22と同様の構成の画像形成装置を少なくとも1つ備えることが可能である。ネットワーク20における画像形成装置は、例えば、MFP(Multifunction Peripheral)、プリンター専用機などによって構成されており、管理業者の客によって使用される。 The network 20 includes a firewall 21 that controls communication between the inside of the network 20 and the outside of the network 20, and an image forming apparatus 22. In addition to the image forming apparatus 22, the network 20 can include at least one image forming apparatus having the same configuration as the image forming apparatus 22. The image forming apparatus in the network 20 is composed of, for example, an MFP (Multifunction Peripheral), a printer-dedicated machine, and the like, and is used by a customer of a management company.
 システム10は、システム10における各画像形成装置を遠隔管理する遠隔管理システム30を備えている。遠隔管理システム30は、管理業者によって使用される。遠隔管理システム30は、1台のコンピューターによって構成されても良いし、複数台のコンピューターによって構成されても良い。以下において、遠隔管理システム30は、ICT(Information and Communication Technology)基盤としてのパブリッククラウドのクラウドプラットフォーム上で動作するものとして説明する。 The system 10 includes a remote management system 30 that remotely manages each image forming apparatus in the system 10. The remote management system 30 is used by a management company. The remote management system 30 may be composed of one computer or a plurality of computers. In the following, the remote management system 30 will be described as operating on a public cloud cloud platform as an ICT (Information and Communication Technology) base.
 遠隔管理システム30にはインターネットを介して多数の画像形成装置が接続可能であるので、遠隔管理システム30を構成するサーバーの能力は、遠隔管理システム30に接続される画像形成装置の増加に伴って、機動的に拡大される。また、遠隔管理システム30が動作するクラウドプラットフォームは、このクラウドプラットフォームのシステム障害やメンテナンスのために、遠隔管理システム30が把握していないタイミングで、システムの一部がダウンする場合がある。したがって、遠隔管理システム30は、遠隔管理システム30自身の安定的な稼働のために、遠隔管理システム30自身の構成要素に障害が発生した場合に適切な処置を受ける必要があるので、遠隔管理システム30自身の構成要素が監視される必要がある。 Since a large number of image forming apparatuses can be connected to the remote management system 30 via the Internet, the capacity of the server forming the remote management system 30 is increased as the number of image forming apparatuses connected to the remote management system 30 increases. , Flexibly expanded. Further, in the cloud platform on which the remote management system 30 operates, a part of the system may go down at a timing when the remote management system 30 does not understand due to system failure or maintenance of the cloud platform. Therefore, the remote management system 30 needs to take appropriate measures when a failure occurs in a component of the remote management system 30 for stable operation of the remote management system 30 itself. 30 own components need to be monitored.
 システム10は、遠隔管理システム30が動作するクラウドプラットフォームの提供者が提供する端点であるクラウドプロバイダーサーバー40を備えている。 The system 10 includes a cloud provider server 40 which is an endpoint provided by a provider of a cloud platform on which the remote management system 30 operates.
 システム10は、遠隔管理システム30を監視する監視システム50を備えている。監視システム50は、管理業者によって使用される。監視システム50は、1台のコンピューターによって構成されても良いし、複数台のコンピューターによって構成されても良い。 The system 10 includes a monitoring system 50 that monitors the remote management system 30. The monitoring system 50 is used by a management company. The monitoring system 50 may be composed of one computer or plural computers.
 システム10における各ネットワークと、遠隔管理システム30と、クラウドプロバイダーサーバー40と、監視システム50とは、インターネット11を介して互いに通信可能である。 Each network in the system 10, the remote management system 30, the cloud provider server 40, and the monitoring system 50 can communicate with each other via the Internet 11.
 図2は、遠隔管理システム30のブロック図である。 FIG. 2 is a block diagram of the remote management system 30.
 図2に示すように、遠隔管理システム30は、画像形成装置に対する制御コマンドを発行するコマンドサーバー31を備えている。遠隔管理システム30は、コマンドサーバー31以外にも、コマンドサーバー31と同様の構成のコマンドサーバーを少なくとも1つ備えることが可能である。コマンドサーバーは、画像形成装置との接続が確立された場合に、この画像形成装置に対してファイアウォールを超えた制御コマンドの発行が可能になる。1つのコマンドサーバーは、例えば4000台の画像形成装置と同時に接続することが可能である。 As shown in FIG. 2, the remote management system 30 includes a command server 31 that issues control commands to the image forming apparatus. In addition to the command server 31, the remote management system 30 can include at least one command server having the same configuration as the command server 31. When the connection with the image forming apparatus is established, the command server can issue a control command that exceeds the firewall to the image forming apparatus. For example, one command server can be simultaneously connected to 4000 image forming apparatuses.
 遠隔管理システム30は、ファイアウォールを超えて接続してきた画像形成装置から送信されてきた、この画像形成装置の管理に必要な情報を処理し、この画像形成装置に対して適切なコマンドサーバーとの接続を確立するように指示するデバイス管理サーバー32を備えている。ここで、適切なコマンドサーバーとは、例えば、接続が確立されている画像形成装置の台数が最も少ないコマンドサーバーである。遠隔管理システム30は、デバイス管理サーバー32以外にも、デバイス管理サーバー32と同様の構成のデバイス管理サーバーを少なくとも1つ備えることが可能である。1つのデバイス管理サーバーは、例えば1分間当たり2000台の画像形成装置に対する処理を実行可能である。 The remote management system 30 processes information necessary for management of the image forming apparatus transmitted from the image forming apparatus connected through the firewall, and connects to the command server appropriate for the image forming apparatus. The device management server 32 for instructing to establish Here, the appropriate command server is, for example, a command server having the smallest number of image forming apparatuses to which the connection is established. In addition to the device management server 32, the remote management system 30 can include at least one device management server having the same configuration as the device management server 32. For example, one device management server can execute processing for 2000 image forming apparatuses per minute.
 遠隔管理システム30は、ファイアウォールを超えて接続してきた画像形成装置から送信されてきた、この画像形成装置の管理に必要な情報を適切なデバイス管理サーバーに割り振ることによって負荷を分散させるロードバランサー33を備えている。 The remote management system 30 includes a load balancer 33 that distributes the load by allocating the information necessary for managing the image forming apparatus transmitted from the image forming apparatus connected through the firewall to an appropriate device management server. ing.
 遠隔管理システム30は、画像形成装置からの各種の情報の取得、画像形成装置の制御ソフトウェアの更新、画像形成装置の各種の設定など、画像形成装置の各種の遠隔操作を行うための操作を管理業者のサービスパーソンなどの利用者から受け付けるユーザー管理サーバー34を備えている。コマンドサーバーは、ユーザー管理サーバー34によって受け付けられた操作を制御コマンドとして画像形成装置に伝達することによって、この画像形成装置をメンテナンスする。 The remote management system 30 manages operations for performing various remote operations of the image forming apparatus, such as acquisition of various information from the image forming apparatus, updating of control software of the image forming apparatus, various settings of the image forming apparatus. It has a user management server 34 that receives information from users such as service persons of a trader. The command server maintains the image forming apparatus by transmitting the operation accepted by the user management server 34 to the image forming apparatus as a control command.
 遠隔管理システム30は、画像形成装置の印刷カウンターや画像形成装置の認証に関する情報など、コマンドサーバーによって画像形成装置から収集された各種の情報を記憶するデータベース35およびキャッシュサーバー36を備えている。 The remote management system 30 includes a database 35 and a cache server 36 that store various information collected from the image forming apparatus by the command server, such as a print counter of the image forming apparatus and information about authentication of the image forming apparatus.
 図3は、1台のコンピューターによって構成される場合の監視システム50のブロック図である。 FIG. 3 is a block diagram of the monitoring system 50 when it is configured by one computer.
 図3に示す監視システム50は、種々の操作が入力される例えばキーボード、マウスなどの操作デバイスである操作部51と、種々の情報を表示する例えばLCD(Liquid Crystal Display)などの表示デバイスである表示部52と、LAN、インターネットなどのネットワーク経由で、または、ネットワークを介さずに有線または無線によって直接に、外部の装置と通信を行う通信デバイスである通信部53と、各種の情報を記憶する例えば半導体メモリー、HDD(Hard Disk Drive)などの不揮発性の記憶デバイスである記憶部54と、監視システム50全体を制御する制御部55とを備えている。 The monitoring system 50 shown in FIG. 3 is an operation unit 51 that is an operation device such as a keyboard and a mouse to which various operations are input, and a display device such as an LCD (Liquid Crystal Display) that displays various information. The display unit 52, a communication unit 53 that is a communication device that communicates with an external device directly via a network such as a LAN or the Internet, or directly by wire or wirelessly without a network, and stores various kinds of information. For example, a storage unit 54 that is a non-volatile storage device such as a semiconductor memory or an HDD (Hard Disk Drive), and a control unit 55 that controls the entire monitoring system 50 are provided.
 記憶部54は、遠隔管理システム30(図2参照。)を監視するための監視プログラム54aを記憶している。監視プログラム54aは、例えば、監視システム50の製造段階で監視システム50にインストールされていても良いし、CD(Compact Disk)、DVD(Digital Versatile Disk)、USB(Universal Serial Bus)メモリーなどの外部の記憶媒体から監視システム50に追加でインストールされても良いし、ネットワーク上から監視システム50に追加でインストールされても良い。 The storage unit 54 stores a monitoring program 54a for monitoring the remote management system 30 (see FIG. 2). The monitoring program 54a may be installed in the monitoring system 50 at the manufacturing stage of the monitoring system 50, or may be installed in an external device such as a CD (Compact Disk), a DVD (Digital Versatile Disk), or a USB (Universal Serial Bus) memory. It may be additionally installed in the monitoring system 50 from a storage medium, or may be additionally installed in the monitoring system 50 from a network.
 記憶部54は、障害に応じた処理を示す処理テーブル54bを記憶している。制御部55は、操作部51または通信部53を介した指示に応じて処理テーブル54bを更新することが可能である。 The storage unit 54 stores a processing table 54b indicating processing according to a failure. The control unit 55 can update the processing table 54b according to an instruction via the operation unit 51 or the communication unit 53.
 記憶部54は、障害の発生の通知先を決定するための通知先決定用テーブル54cを記憶可能である。通知先決定用テーブル54cは、障害の発生の通知の条件と、障害の発生の通知先とを関連付けた情報である。制御部55は、操作部51または通信部53を介した指示に応じて通知先決定用テーブル54cを更新することが可能である。 The storage unit 54 can store a notification destination determination table 54c for determining the notification destination of the failure occurrence. The notification destination determination table 54c is information associating the condition for notification of failure occurrence with the notification destination of failure occurrence. The control unit 55 can update the notification destination determination table 54c according to an instruction via the operation unit 51 or the communication unit 53.
 制御部55は、例えば、CPU(Central Processing Unit)と、プログラムおよび各種のデータを記憶しているROM(Read Only Memory)と、制御部55のCPUの作業領域として用いられるメモリーとしてのRAM(Random Access Memory)とを備えている。制御部55のCPUは、記憶部54または制御部55のROMに記憶されているプログラムを実行する。 The control unit 55 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Memory) that is used as a work area of the CPU of the control unit 55. Access Memory). The CPU of the control unit 55 executes the program stored in the storage unit 54 or the ROM of the control unit 55.
 制御部55は、監視プログラム54aを実行することによって、システム10の構成要素から情報を取得する情報取得部56と、情報取得部56によって取得された情報を分析する情報分析部57と、情報分析部57による分析の結果を通知する結果通知部58とを実現する。 The control unit 55 executes the monitoring program 54a to acquire information from the components of the system 10, an information analysis unit 57 that analyzes the information acquired by the information acquisition unit 56, and an information analysis. A result notification unit 58 that notifies the result of the analysis by the unit 57 is realized.
 情報取得部56は、システム10の構成要素から情報を取得するためのモジュールである情報取得アダプター56aを備えている。ここで、システム10の構成要素には、システム10における画像形成装置と、遠隔管理システム30の構成要素と、クラウドプロバイダーサーバー40とが含まれている。また、遠隔管理システム30の構成要素には、コマンドサーバーと、デバイス管理サーバーと、ユーザー管理サーバー34と、データベース35と、キャッシュサーバー36とが含まれている。情報取得部56は、情報取得アダプター56a以外にも、情報取得アダプター56aと同様の構成の情報取得アダプターを少なくとも1つ備えることが可能である。情報取得アダプターによって画像形成装置から取得される情報は、例えば、画像形成装置が停止しているか否かの情報や、画像形成装置に発生したエラーの情報である。情報取得アダプターによって遠隔管理システム30の構成要素から取得される情報は、例えば、この構成要素が停止しているか否かの情報や、この構成要素に発生したエラーの情報である。情報取得アダプターによってクラウドプロバイダーサーバー40から取得される情報は、例えば、遠隔管理システム30が動作するクラウドプラットフォームのメンテナンスに関わる情報など、このクラウドプラットフォームが正常に稼働しているか否かの情報である。 The information acquisition unit 56 includes an information acquisition adapter 56a that is a module for acquiring information from the components of the system 10. Here, the components of the system 10 include the image forming apparatus in the system 10, the components of the remote management system 30, and the cloud provider server 40. The components of the remote management system 30 include a command server, a device management server, a user management server 34, a database 35, and a cache server 36. The information acquisition unit 56 can include at least one information acquisition adapter having the same configuration as the information acquisition adapter 56a in addition to the information acquisition adapter 56a. The information acquired from the image forming apparatus by the information acquisition adapter is, for example, information on whether the image forming apparatus is stopped or information on an error that has occurred in the image forming apparatus. The information acquired from the constituent element of the remote management system 30 by the information acquisition adapter is, for example, information on whether this constituent element is stopped or information on an error that has occurred in this constituent element. The information acquired from the cloud provider server 40 by the information acquisition adapter is, for example, information related to maintenance of the cloud platform on which the remote management system 30 operates, and information on whether or not this cloud platform is operating normally.
 なお、システム10における画像形成装置、コマンドサーバー、デバイス管理サーバー、ユーザー管理サーバー34、データベース35、キャッシュサーバー36、クラウドプロバイダーサーバー40など、システム10の構成要素の少なくとも1つには、監視システム50に情報を出力するためのエージェントがインストールされても良い。エージェントは、インストールされている構成要素のデバッグ用の情報や、インストールされている構成要素の、より細かい動作状況に関する情報を監視システム50に出力することができる。 At least one of the components of the system 10, such as the image forming apparatus, the command server, the device management server, the user management server 34, the database 35, the cache server 36, and the cloud provider server 40 in the system 10, is connected to the monitoring system 50. An agent for outputting information may be installed. The agent can output to the monitoring system 50 information for debugging the installed components and information on more detailed operation status of the installed components.
 情報取得部56は、情報取得アダプターによって情報を取得する情報取得処理部56bを備えている。なお、情報取得部56は、情報の取得の機能が情報取得アダプターによって構築されているので、遠隔管理システム30の機能拡張に合わせて、情報の取得の機能を柔軟に拡張することができる。したがって、監視システム50は、遠隔管理システム30の機能拡張に伴う変更を最小にすることができる。 The information acquisition unit 56 includes an information acquisition processing unit 56b that acquires information by the information acquisition adapter. Since the information acquisition function of the information acquisition unit 56 is constructed by the information acquisition adapter, the information acquisition function can be flexibly expanded in accordance with the expansion of the function of the remote management system 30. Therefore, the monitoring system 50 can minimize the changes accompanying the functional expansion of the remote management system 30.
 情報分析部57は、情報取得部56によって取得された情報の振り分けのロジックを機械学習、ニューロコンピューティング、ディープラーニングなどの既知の学習アルゴリズムによって生成するロジック生成部57aと、情報取得部56によって取得された情報を、ロジック生成部57aによって生成されたロジックによって振り分ける情報振り分け部57bとを備えている。ロジック生成部57aによって生成される、情報の振り分けのロジックとしては、例えば、時系列による情報の振り分けのロジックと、障害の重要度による情報の振り分けのロジックと、過去に発生した障害との類似度による情報の振り分けのロジックと、他の構成要素で同時に障害が発生しているか否かによる情報の振り分けのロジックとが存在する。なお、障害の重要度は、例えば、障害の発生箇所と、障害の発生頻度との少なくとも1つに基づいて、特定の規則に従って判定されても良い。 The information analysis unit 57 is acquired by the information acquisition unit 56, and a logic generation unit 57a that generates the information distribution logic acquired by the information acquisition unit 56 by a known learning algorithm such as machine learning, neurocomputing, and deep learning. The information distribution unit 57b that distributes the generated information according to the logic generated by the logic generation unit 57a. Examples of the information distribution logic generated by the logic generation unit 57a include, for example, a time-series information distribution logic, a failure information importance distribution logic, and a degree of similarity with a failure that occurred in the past. There is a logic for distributing information according to the above, and a logic for distributing information depending on whether or not a failure has occurred in other components at the same time. The importance of the failure may be determined according to a specific rule, for example, based on at least one of the location of the failure and the frequency of occurrence of the failure.
 情報分析部57は、情報振り分け部57bによって振り分けられた情報に基づいて遠隔管理システム30の障害を検出する障害検出部57cを備えている。例えば、情報分析部57は、システム10における画像形成装置から取得した情報と、遠隔管理システム30の構成要素から取得した情報とに基づいて、画像形成装置と、遠隔管理システム30との通信が確立しているか否かを検出することができる。また、情報分析部57は、システム10における画像形成装置から取得した情報と、遠隔管理システム30の構成要素から取得した情報とに基づいて、遠隔管理システム30によって画像形成装置の遠隔操作が正しく行われているか否かを検出することができる。また、情報分析部57は、クラウドプロバイダーサーバー40から取得した情報に基づいて、遠隔管理システム30が動作するクラウドプラットフォームが正常に稼働しているか否かを検出することができる。 The information analysis unit 57 includes a failure detection unit 57c that detects a failure of the remote management system 30 based on the information distributed by the information distribution unit 57b. For example, the information analysis unit 57 establishes communication between the image forming apparatus and the remote management system 30 based on the information acquired from the image forming apparatus in the system 10 and the information acquired from the components of the remote management system 30. Whether or not it can be detected. Further, the information analysis unit 57 performs the remote operation of the image forming apparatus correctly by the remote management system 30 based on the information acquired from the image forming apparatus in the system 10 and the information acquired from the components of the remote management system 30. It is possible to detect whether or not it has been broken. In addition, the information analysis unit 57 can detect whether the cloud platform on which the remote management system 30 operates is operating normally, based on the information acquired from the cloud provider server 40.
 情報分析部57は、障害検出部57cによって検出された障害に処理テーブル54bにおいて対応付けられている処理を決定する処理決定部57dを備えている。処理決定部57dによって決定される処理としては、例えば、遠隔管理システム30の再起動、遠隔管理システム30が動作するクラウドプラットフォームのスケールアウト、データベース35のデータのメンテナンス、データベース35の容量の増強、遠隔管理システム30において不具合が発生しているサーバーの切り離しなどが存在する。 The information analysis unit 57 includes a process determination unit 57d that determines the process associated with the failure detected by the failure detection unit 57c in the processing table 54b. The processing determined by the processing determination unit 57d includes, for example, restart of the remote management system 30, scale out of the cloud platform on which the remote management system 30 operates, data maintenance of the database 35, capacity increase of the database 35, remote There is disconnection of a server in which a problem occurs in the management system 30.
 結果通知部58は、情報分析部57によって分析された障害が通知先決定用テーブル54cに設定されている条件を満たす場合に、この障害に応じて通知先決定用テーブル54cに設定されている通知先に、この障害を示すメッセージを送信するためのモジュールであるメッセージ送信アダプター58aを備えている。例えば、結果通知部58は、重要度が特定の重要度より低い障害の発生を示すメッセージを、遠隔管理システム30に対して適切な処置を実行することが可能な技術者のみに送信しても良いし、重要度が特定の重要度より高い障害の発生を示すメッセージを、遠隔管理システム30に対して適切な処置を実行することが可能な技術者だけでなく、画像形成装置を管理している販社など、より広範囲の利害関係者に送信しても良い。 When the failure analyzed by the information analysis section 57 satisfies the condition set in the notification destination determination table 54c, the result notification unit 58 notifies the notification destination set in the notification destination determination table 54c according to the failure. First, a message transmission adapter 58a, which is a module for transmitting a message indicating this failure, is provided. For example, the result notification unit 58 may send a message indicating the occurrence of a failure of which importance is lower than a specific importance to only a technician who can perform appropriate measures for the remote management system 30. A message indicating that a failure having a higher importance than a specific importance has occurred is sent to the remote management system 30 not only by the technician who can execute appropriate measures but also by the management of the image forming apparatus. It may be sent to a wider range of stakeholders, such as existing distributors.
 結果通知部58は、処理決定部57dによって決定された処理用のコマンドを、遠隔管理システム30およびクラウドプロバイダーサーバー40のうち、このコマンドに適した方に送信するためのモジュールであるコマンド送信アダプター58bを備えている。 The result notification unit 58 is a command transmission adapter 58b that is a module for transmitting the processing command determined by the processing determination unit 57d to one of the remote management system 30 and the cloud provider server 40 that is suitable for this command. Is equipped with.
 結果通知部58は、メッセージ送信アダプター58aおよびコマンド送信アダプター58bを制御する通知処理部58cを備えている。なお、結果通知部58は、通知の機能がメッセージ送信アダプター58aおよびコマンド送信アダプター58bなどのモジュールによって構築されているので、遠隔管理システム30の機能拡張に合わせて、通知の機能を柔軟に拡張することができる。したがって、監視システム50は、遠隔管理システム30の機能拡張に伴う変更を最小にすることができる。 The result notification unit 58 includes a notification processing unit 58c that controls the message transmission adapter 58a and the command transmission adapter 58b. The result notifying unit 58 has a notification function built by modules such as the message sending adapter 58a and the command sending adapter 58b, so that the notification function can be flexibly expanded according to the function expansion of the remote management system 30. be able to. Therefore, the monitoring system 50 can minimize the changes accompanying the functional expansion of the remote management system 30.
 次に、障害の発生を通知する場合の監視システム50の動作について説明する。 Next, the operation of the monitoring system 50 when notifying the occurrence of a failure will be described.
 図4は、障害の発生を通知する場合の監視システム50の動作のフローチャートである。 FIG. 4 is a flowchart of the operation of the monitoring system 50 when notifying the occurrence of a failure.
 監視システム50の制御部55は、例えば1秒毎などの定期的なタイミングなど、特定のタイミングで図4に示す動作を実行する。 The control unit 55 of the monitoring system 50 executes the operation shown in FIG. 4 at a specific timing such as a regular timing such as every second.
 図4に示すように、情報取得処理部56bは、システム10の構成要素から情報を収集することを試みる(S101)。 As shown in FIG. 4, the information acquisition processing unit 56b attempts to collect information from the components of the system 10 (S101).
 次いで、情報振り分け部57bは、S101において取得された情報を、ロジック生成部57aによって生成されたロジックによって振り分ける(S102)。 Next, the information distribution unit 57b distributes the information acquired in S101 by the logic generated by the logic generation unit 57a (S102).
 次いで、障害検出部57cは、S102において振り分けられた情報に基づいて遠隔管理システム30の障害の検出を試みる(S103)。例えば、障害検出部57cは、コマンドサーバーの負荷が特定の程度以上、上がった場合に、このコマンドサーバーに接続している画像形成装置の台数が特定の程度以上、下がったとき、このコマンドサーバーの障害として検出しても良い。また、障害検出部57cは、データベース35の負荷が特定の程度以上、上がった場合に、データベース35からのデータの取得の失敗が特定の程度以上、発生したとき、データベース35の障害として検出しても良い。なお、障害検出部57cは、S102において振り分けられた情報に基づいて遠隔管理システム30の障害の発生を機械学習、ニューロコンピューティング、ディープラーニングなどの既知の学習アルゴリズムによって予測することによって、この障害を発生前に検出することも可能である。 Next, the failure detection unit 57c attempts to detect a failure of the remote management system 30 based on the information distributed in S102 (S103). For example, when the load on the command server increases by a certain degree or more, the failure detection unit 57c determines that the number of image forming apparatuses connected to the command server decreases by a certain degree or more. It may be detected as a failure. In addition, when the load on the database 35 increases by a certain degree or more, the failure detecting unit 57c detects the failure of the data acquisition from the database 35 as a failure of the database 35 when the failure occurs by more than a certain degree. Is also good. The failure detection unit 57c predicts the occurrence of a failure of the remote management system 30 based on the information distributed in S102 by a known learning algorithm such as machine learning, neurocomputing, deep learning, etc. It is also possible to detect it before it occurs.
 障害検出部57cは、S103の処理の後、遠隔管理システム30の障害がS103において検出されたか否かを判断する(S104)。 After the processing of S103, the failure detection unit 57c determines whether a failure of the remote management system 30 has been detected in S103 (S104).
 障害検出部57cは、遠隔管理システム30の障害が検出されなかったとS104において判断すると、図4に示す動作を終了する。 When the failure detection unit 57c determines in S104 that no failure of the remote management system 30 has been detected, the operation illustrated in FIG. 4 ends.
 処理決定部57dは、遠隔管理システム30の障害が検出されたとS104において判断されると、S103において検出された障害に処理テーブル54bにおいて対応付けられている処理を決定する(S105)。 When it is determined in S104 that a failure of the remote management system 30 has been detected, the processing determination unit 57d determines the processing associated with the failure detected in S103 in the processing table 54b (S105).
 次いで、通知処理部58cは、S103において検出された障害が通知先決定用テーブル54cに設定されている条件を満たすか否かを判断する(S106)。 Next, the notification processing unit 58c determines whether the failure detected in S103 satisfies the condition set in the notification destination determination table 54c (S106).
 通知処理部58cは、S103において検出された障害が通知先決定用テーブル54cに設定されている条件を満たさないとS106において判断すると、図4に示す動作を終了する。 If the notification processing unit 58c determines in S106 that the failure detected in S103 does not satisfy the condition set in the notification destination determination table 54c, the operation illustrated in FIG. 4 ends.
 メッセージ送信アダプター58aは、S103において検出された障害が通知先決定用テーブル54cに設定されている条件を満たすとS106において判断されると、この障害に応じて通知先決定用テーブル54cに設定されている通知先に、この障害を示すメッセージを送信する(S107)。 When the message transmission adapter 58a determines in S106 that the failure detected in S103 satisfies the condition set in the notification destination determination table 54c, the message transmission adapter 58a sets the failure in the notification destination determination table 54c according to the failure. A message indicating this failure is transmitted to the notified notification destination (S107).
 次いで、コマンド送信アダプター58bは、S105において決定された処理用のコマンドを、遠隔管理システム30およびクラウドプロバイダーサーバー40のうち、このコマンドに適した方に送信して(S108)、図4に示す動作を終了する。 Next, the command transmission adapter 58b transmits the processing command determined in S105 to one of the remote management system 30 and the cloud provider server 40 that is suitable for this command (S108), and the operation shown in FIG. To finish.
 なお、監視システム50は、以上において、S105において決定された処理用のコマンドをS108において送信しているが、S108の処理を実行せずに、S105において決定された処理の内容を含めたメッセージをS107において送信しても良い。 Although the monitoring system 50 has transmitted the processing command determined in S105 in S108, the monitoring system 50 does not execute the processing in S108 and sends a message including the contents of the processing determined in S105. You may transmit in S107.
 以上に説明したように、監視システム50は、遠隔管理システム30に障害が発生した場合(S104でYES)に、遠隔管理システム30の障害を通知する(S107)ので、遠隔管理システム30に対して適切な処置が講じられることができる。したがって、監視システム50は、遠隔管理システム30による画像形成装置の遠隔管理の安定性を向上することができる。 As described above, when the remote management system 30 has a failure (YES in S104), the monitoring system 50 notifies the remote management system 30 of the failure (S107). Appropriate action can be taken. Therefore, the monitoring system 50 can improve the stability of remote management of the image forming apparatus by the remote management system 30.
 監視システム50は、遠隔管理システム30から取得した情報だけでなく、画像形成装置と、遠隔管理システム30が動作するクラウドプラットフォームとの少なくとも1つから取得した情報にも基づいて遠隔管理システム30の障害を検出する(S101~S103)ので、遠隔管理システム30の障害の検出の精度を向上することができる。 The monitoring system 50 uses the information acquired from the remote management system 30 as well as the information acquired from at least one of the image forming apparatus and the cloud platform on which the remote management system 30 operates to detect a failure of the remote management system 30. Is detected (S101 to S103), it is possible to improve the accuracy of detecting a failure of the remote management system 30.
 監視システム50は、時系列と、情報が示す障害の重要度と、情報が示す障害の、過去に発生した障害との類似度と、情報が取得された構成要素とは異なる構成要素で同時に障害が発生しているか否かとの少なくとも1つの基準によって情報を振り分けて分析する(S102~S103)ので、遠隔管理システム30などから取得した膨大な数量の情報に基づいて、人間による監視では気付くのが困難な、遠隔管理システム30の障害を検出することができる。 The monitoring system 50 uses the time series, the importance of the failure indicated by the information, the similarity between the failure indicated by the information and the failure that occurred in the past, and the failure at the same time as the constituent element different from the constituent element from which the information is acquired. Since information is sorted and analyzed according to at least one criterion as to whether or not the occurrence has occurred (S102 to S103), it is noticeable by human monitoring based on the huge amount of information acquired from the remote management system 30 or the like. It is possible to detect a difficult failure of the remote management system 30.
 監視システム50は、検出した障害が予め設定された条件を満たす場合(S106でYES)に、この条件に対応付けて設定された通知先に、この障害を通知する(S107)ので、障害に応じた適切な人間に障害を通知することができる。 When the detected failure satisfies the preset condition (YES in S106), the monitoring system 50 notifies the notification destination set in association with this condition of this failure (S107). You can notify the appropriate person of the failure.
 監視システム50は、本実施の形態において、遠隔管理システム30とは別のコンピューターによって実現されている。しかしながら、遠隔管理システム30を実現する少なくとも一部のコンピューターと、監視システム50を実現する少なくとも一部のコンピューターとが同一でも良い。 The monitoring system 50 is realized by a computer different from the remote management system 30 in this embodiment. However, at least some of the computers that implement the remote management system 30 and at least some of the computers that implement the monitoring system 50 may be the same.
 次に、上記実施の形態の第1の変形例を図5から図11を参照して説明する。 Next, a first modification of the above embodiment will be described with reference to FIGS. 5 to 11.
 本変形例の監視システム50は、図5に示すように、記憶部54が前記実施の形態で記憶するテーブル以外にさらなるテーブルを記憶可能となされ、記憶されたテーブルを用いて情報取得部56が収集した情報に対し情報分析部57による分析および結果通知部58による通知を行うことで上記実施の形態と同様の技術的効果を達成する監視システムを実現する。なお、本変形例の説明において、上記実施の形態と同じ構成要素には同じ参照符号を付し、ここでの説明は省略する。 As shown in FIG. 5, the monitoring system 50 of the present modified example is capable of storing a further table in addition to the table stored in the storage unit 54 in the above-described embodiment, and the information acquisition unit 56 uses the stored table. By performing analysis by the information analysis unit 57 and notification by the result notification unit 58 on the collected information, it is possible to realize a monitoring system that achieves the same technical effect as the above-described embodiment. In the description of this modification, the same components as those in the above-mentioned embodiment are designated by the same reference numerals, and the description thereof will be omitted.
 図5に示すように、記憶部54は遠隔管理システム30が動作するクラウドプラットフォームに発生した障害を示すクラウド障害テーブル54cを記憶可能である。 As shown in FIG. 5, the storage unit 54 can store a cloud failure table 54c indicating a failure that has occurred in the cloud platform on which the remote management system 30 operates.
 図6は、クラウド障害テーブル54cの一例を示す図である。 FIG. 6 is a diagram showing an example of the cloud failure table 54c.
 図6に示すクラウド障害テーブル54cは、遠隔管理システム30が動作するクラウドプラットフォームから収集された障害の情報に基づいて生成されるものである。図6に示すクラウド障害テーブル54cは、遠隔管理システム30が動作するクラウドプラットフォームから収集された障害の内容の原文と、障害の箇所と、障害の発生地域と、障害を示す障害コードと、障害の開始日時と、障害の終了日時とを障害毎に示すものである。 The cloud failure table 54c shown in FIG. 6 is created based on failure information collected from the cloud platform on which the remote management system 30 operates. The cloud failure table 54c illustrated in FIG. 6 includes the original text of the failure content collected from the cloud platform on which the remote management system 30 operates, the failure location, the failure area, the failure code indicating the failure, and the failure code. The start date and time and the end date and time of the failure are shown for each failure.
 図5に示すように、記憶部54は、遠隔管理システム30に発生した障害を一時的に管理するための一時管理テーブル54dを記憶可能である。 As shown in FIG. 5, the storage unit 54 can store a temporary management table 54d for temporarily managing a failure that has occurred in the remote management system 30.
 図7は、一時管理テーブル54dの一例を示す図である。 FIG. 7 is a diagram showing an example of the temporary management table 54d.
 図7に示す一時管理テーブル54dは、遠隔管理システム30から収集された障害の内容の原文と、障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因が遠隔管理システム30の内部および外部のいずれによるものかを示す、障害の要因の箇所と、障害の検出日時と、過去に発生した他の障害との類似度とを障害毎に示すものである。なお、図5に示す一時管理テーブル54dにおいては、検出日時が「2018/09/22 15:00」である障害の重要度、要因の箇所および類似度が省略して描かれている。 In the temporary management table 54d shown in FIG. 7, the original text of the content of the failure collected from the remote management system 30, the location of the failure, the area where the failure occurred, the importance of the failure, and the cause of the failure are displayed in the remote management system 30. For each failure, the location of the failure factor, the failure detection date and time, and the degree of similarity with other failures that occurred in the past are shown. In the temporary management table 54d shown in FIG. 5, the importance of the failure, the location of the factor, and the similarity of which the detection date and time is “2018/09/22 15:00” are omitted.
 図5に示すように、記憶部54は、遠隔管理システム30に発生した障害の履歴を示す障害履歴テーブル54eを記憶可能である。 As shown in FIG. 5, the storage unit 54 can store a failure history table 54e indicating a history of failures that have occurred in the remote management system 30.
 図8は、障害履歴テーブル54eの一例を示す図である。 FIG. 8 is a diagram showing an example of the failure history table 54e.
 図8に示す障害履歴テーブル54eは、遠隔管理システム30から収集された障害の内容の原文と、障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因の箇所と、障害の検出日時と、過去に発生した他の障害との類似度とを障害毎に示すものである。 The failure history table 54e shown in FIG. 8 includes the original text of the failure content collected from the remote management system 30, the location of the failure, the area where the failure occurred, the importance of the failure, the location of the failure factor, and the failure. The detection date and time and the similarity with other failures that occurred in the past are shown for each failure.
 図5に示すように、記憶部54は、障害の発生の通知先を決定するための通知先決定用テーブル54fを記憶可能である。 As shown in FIG. 5, the storage unit 54 can store a notification destination determination table 54f for determining the notification destination of the failure occurrence.
 図9は、通知先決定用テーブル54fの一例を示す図である。 FIG. 9 is a diagram showing an example of the notification destination determination table 54f.
 図9に示す通知先決定用テーブル54fは、障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因の箇所と、過去に発生した他の障害との類似度との組み合わせからなる、障害の発生の通知の条件毎に、障害の発生の通知先と、障害の発生の通知内容とを示すものである。ここで、通知先決定用テーブル54fにおいて、障害の重要度は、例えば50以上60未満というように、範囲が設定されても良い。通知先決定用テーブル54fにおいて、類似度も、重要度と同様に範囲が設定されても良い。また、通知先決定用テーブル54fにおいて、障害の要因の箇所は、遠隔管理システム30の内部および外部のいずれによるものかを区別して設定されても良いし、遠隔管理システム30の内部および外部のいずれでも良いように設定されても良い。図9に示す通知先決定用テーブル54fにおいて、箇所、発生地域、重要度および類似度がそれぞれ「ServiceA」、「US」、「50以上60未満」および「60」である通知の条件の「要因の箇所」は、遠隔管理システム30の内部および外部のいずれでも良いように設定されている。 The notification destination determination table 54f shown in FIG. 9 is a combination of the location of the failure, the area where the failure occurs, the importance of the failure, the location of the cause of the failure, and the similarity with other failures that occurred in the past. The notification destination of failure occurrence and the content of notification of failure occurrence are shown for each condition of notification of failure occurrence. Here, in the notification destination determination table 54f, a range may be set as the importance of the failure, such as 50 or more and less than 60. In the notification destination determination table 54f, a range may be set for the similarity as well as the importance. Further, in the notification destination determination table 54f, the location of the cause of failure may be set by distinguishing whether it is inside or outside the remote management system 30, or inside or outside the remote management system 30. However, it may be set to be good. In the notification destination determination table 54f illustrated in FIG. 9, the location, the occurrence area, the importance, and the similarity are "Service A", "US", "50 or more and less than 60", and "60" in the notification condition. “Location” is set so that it may be inside or outside the remote management system 30.
 図5に示す制御部55は、操作部51または通信部53を介した指示に応じて通知先決定用テーブル54fを更新することが可能である。 The control unit 55 shown in FIG. 5 can update the notification destination determination table 54f in accordance with an instruction via the operation unit 51 or the communication unit 53.
 なお、本変形例の結果通知部58は、情報分析部57によって分析された障害が通知先決定用テーブル54fに設定されている条件を満たす場合に、この障害に応じて通知先決定用テーブル54fに設定されている通知先に、この障害を示すメッセージを送信するためのモジュールであるメッセージ送信アダプター58aを備えている。例えば、結果通知部58は、重要度が特定の重要度より低い障害の発生を示すメッセージを、遠隔管理システム30に対して適切な処置を実行することが可能な技術者のみに送信しても良いし、重要度が特定の重要度より高い障害の発生を示すメッセージを、遠隔管理システム30に対して適切な処置を実行することが可能な技術者だけでなく、画像形成装置を管理している販社など、より広範囲の利害関係者に送信しても良い。 In addition, when the failure analyzed by the information analysis unit 57 satisfies the condition set in the notification destination determination table 54f, the result notification unit 58 of the present modified example responds to the failure by the notification destination determination table 54f. A message sending adapter 58a, which is a module for sending a message indicating this failure, is provided at the notification destination set to. For example, the result notification unit 58 may send a message indicating the occurrence of a failure of which importance is lower than a specific importance to only a technician who can perform appropriate measures for the remote management system 30. A message indicating that a failure having a higher importance than a specific importance has occurred is sent to the remote management system 30 not only by the technician who can execute appropriate measures but also by the management of the image forming apparatus. It may be sent to a wider range of stakeholders, such as existing distributors.
 次に、クラウド障害テーブル54cを更新する場合の監視システム50の動作について説明する。 Next, the operation of the monitoring system 50 when updating the cloud failure table 54c will be described.
 図10は、クラウド障害テーブル54cを更新する場合の監視システム50の動作のフローチャートである。 FIG. 10 is a flowchart of the operation of the monitoring system 50 when updating the cloud failure table 54c.
 本変形例においても、監視システム50の制御部55は、例えば1秒毎などの定期的なタイミングなど、特定のタイミングで図10に示す動作を実行する。 Also in this modification, the control unit 55 of the monitoring system 50 executes the operation shown in FIG. 10 at a specific timing, such as a regular timing such as every second.
 図10に示すように、情報取得部56は、遠隔管理システム30が動作するクラウドプラットフォームに発生した障害の情報をクラウドプロバイダーサーバー40から収集することを試みる(S111)。 As shown in FIG. 10, the information acquisition unit 56 attempts to collect, from the cloud provider server 40, information on a failure that has occurred in the cloud platform on which the remote management system 30 operates (S111).
 次いで、障害検出部57cは、S111において障害の情報が収集されたか否かを判断する(S112)。 Next, the failure detection unit 57c determines whether or not failure information has been collected in S111 (S112).
 障害検出部57cは、障害の情報が収集されたとS112において判断すると、S111において収集された、障害の情報をクラウド障害テーブル54cに追加する(S113)。 When the failure detection unit 57c determines in S112 that the failure information has been collected, the failure detection unit 57c adds the failure information collected in S111 to the cloud failure table 54c (S113).
 障害検出部57cは、障害の情報が収集されなかったとS112において判断するか、S113の処理が終了すると、図10に示す動作を終了する。 The fault detection unit 57c terminates the operation shown in FIG. 10 when it determines in S112 that fault information has not been collected or when the process of S113 ends.
 次に、本変形例における障害の発生を通知する場合の監視システム50の動作について説明する。 Next, the operation of the monitoring system 50 in the case of notifying the occurrence of a failure in this modification will be described.
 図11は、障害の発生を通知する場合の監視システム50の動作のフローチャートである。 FIG. 11 is a flowchart of the operation of the monitoring system 50 when notifying the occurrence of a failure.
 監視システム50の制御部55は、例えば1秒毎などの定期的なタイミングなど、特定のタイミングで図11に示す動作を実行する。 The control unit 55 of the monitoring system 50 executes the operation shown in FIG. 11 at a specific timing, such as a regular timing such as every second.
 図11に示すように、情報取得処理部56bは、システム10における画像形成装置と、遠隔管理システム30の構成要素とから情報を収集することを試みる(S121)。 As shown in FIG. 11, the information acquisition processing unit 56b attempts to collect information from the image forming apparatus in the system 10 and the constituent elements of the remote management system 30 (S121).
 次いで、障害検出部57cは、遠隔管理システム30の障害を示す情報がS121において収集されたか否かを判断する(S122)。 Next, the failure detection unit 57c determines whether or not the information indicating the failure of the remote management system 30 has been collected in S121 (S122).
 障害検出部57cは、遠隔管理システム30の障害を示す情報が収集されなかったとS122において判断すると、図11に示す動作を終了する。 When the failure detection unit 57c determines in S122 that information indicating a failure of the remote management system 30 has not been collected, the operation illustrated in FIG. 11 ends.
 障害検出部57cは、遠隔管理システム30の障害を示す情報が収集されたとS122において判断すると、収集されたとS122において判断した、障害の情報を、一時管理テーブル54dに追加する(S123)。ここで、S123において一時管理テーブル54dに追加された障害は、S123の処理の終了直後には、図7に示す検出日時が「2018/09/22 15:00」である障害のように、重要度、要因の箇所および類似度が未だ記憶されていない。 When the failure detection unit 57c determines in S122 that the information indicating the failure of the remote management system 30 has been collected, the failure detection unit 57c adds the failure information determined in S122 to the temporary management table 54d (S123). Here, the failure added to the temporary management table 54d in S123 is important just after the end of the processing in S123, such as the failure whose detection date and time is "2018/09/22 15:00" shown in FIG. The degree, the location of the factor, and the degree of similarity are not yet remembered.
 障害検出部57cは、S123の処理の後、S123において一時管理テーブル54dに追加した障害の情報と、障害履歴テーブル54eに示される過去の障害の情報とに基づいて、過去に発生した他の障害に対する、S123において一時管理テーブル54dに追加した障害の類似度を特定の判定方法に従って判定する(S124)。S124における判定方法は、例えば、既知の統計処理や、機械学習、ニューロコンピューティング、ディープラーニングなどの既知の学習アルゴリズムを利用した方法でも良い。 After the processing of S123, the failure detection unit 57c determines another failure that occurred in the past based on the failure information added to the temporary management table 54d in S123 and the past failure information shown in the failure history table 54e. On the other hand, the similarity of the fault added to the temporary management table 54d in S123 is determined according to a specific determination method (S124). The determination method in S124 may be, for example, a method using a known learning process algorithm such as known statistical processing or machine learning, neuro-computing, deep learning, or the like.
 障害検出部57cは、S124の処理の後、S124において判定した類似度を、S123において一時管理テーブル54dに追加した障害の情報に追加する(S125)。 After the processing of S124, the failure detection unit 57c adds the similarity determined in S124 to the failure information added to the temporary management table 54d in S123 (S125).
 次いで、障害検出部57cは、S123において一時管理テーブル54dに追加した障害の重要度を特定の判定方法に従って判定する(S126)。S126における判定方法は、例えば、障害の発生箇所と、障害の発生頻度との少なくとも1つに基づいて、特定の規則に従って判定する方法でも良い。 Next, the failure detection unit 57c determines the importance of the failure added to the temporary management table 54d in S123 according to a specific determination method (S126). The determination method in S126 may be, for example, a method of determining according to a specific rule, based on at least one of the location of the failure and the frequency of occurrence of the failure.
 障害検出部57cは、S126の処理の後、S126において判定した重要度を、S123において一時管理テーブル54dに追加した障害の情報に追加する(S127)。 After the processing of S126, the failure detection unit 57c adds the degree of importance determined in S126 to the failure information added to the temporary management table 54d in S123 (S127).
 次いで、障害検出部57cは、S123において一時管理テーブル54dに追加した障害の情報と、クラウド障害テーブル54cに示される障害の情報とに基づいて、S123において一時管理テーブル54dに追加した障害に該当する障害が、クラウド障害テーブル54cに示されている障害、すなわち、遠隔管理システム30が動作するクラウドプラットフォームの障害に関係するか否かを判断する(S128)。すなわち、障害検出部57cは、S123において一時管理テーブル54dに追加した障害の箇所、発生地域および検出日時が、クラウド障害テーブル54cに示されるいずれかの障害の情報に含まれる場合、S123において一時管理テーブル54dに追加した障害が、クラウド障害テーブル54cに示されている障害に関係するとS128において判断する。例えば、障害検出部57cは、図7に示す箇所、発生地域および検出日時がそれぞれ「ServiceA」、「US」および「2018/09/22 15:00」である障害が、図6に示す内容の原文、発生地域、開始日時および終了日時がそれぞれ「サービスAで障害が発生しました。」、「US」、「2018/09/22 14:00」および「2018/09/22 16:00」である障害に関係すると判断する。 Next, the failure detection unit 57c corresponds to the failure added to the temporary management table 54d in S123 based on the failure information added to the temporary management table 54d in S123 and the failure information shown in the cloud failure table 54c. It is determined whether the failure is related to the failure shown in the cloud failure table 54c, that is, the failure of the cloud platform on which the remote management system 30 operates (S128). That is, when the failure location, occurrence area, and detection date and time of the failure added to the temporary management table 54d in S123 are included in the information of any failure shown in the cloud failure table 54c, the failure detection unit 57c performs temporary management in S123. It is determined in S128 that the failure added to the table 54d is related to the failure shown in the cloud failure table 54c. For example, the failure detection unit 57c determines that the location, the occurrence area, and the detection date and time shown in FIG. 7 are “Service A”, “US”, and “2018/09/22 15:00”, respectively. The original text, the area of occurrence, the start date and time and the end date and time are "Service A has failed.", "US", "2018/09/22 14:00" and "2018/09/22 16:00", respectively. Determined to be related to a disorder.
 なお、遠隔管理システム30が動作するクラウドプラットフォームの障害がクラウド障害テーブル54cに反映されるまでに時間を要する場合があるので、障害検出部57cは、S127の処理の後、特定の時間が経過してから、S128の処理を実行しても良い。 Since it may take time for the failure of the cloud platform on which the remote management system 30 operates to be reflected in the cloud failure table 54c, the failure detection unit 57c determines that a specific time has elapsed after the processing of S127. After that, the process of S128 may be executed.
 障害検出部57cは、S123において一時管理テーブル54dに追加した障害に該当する障害が、遠隔管理システム30が動作するクラウドプラットフォームの障害に関係するとS128において判断すると、障害の要因が遠隔管理システム30の外部によるものであることを、S123において一時管理テーブル54dに追加した障害の要因の箇所として記憶する(S129)。 When the failure detection unit 57c determines in S128 that the failure corresponding to the failure added to the temporary management table 54d in S123 is related to the failure of the cloud platform on which the remote management system 30 operates, the failure cause is the remote management system 30. The fact that it is external is stored as the location of the cause of failure added to the temporary management table 54d in S123 (S129).
 障害検出部57cは、S123において一時管理テーブル54dに追加した障害に該当する障害が、遠隔管理システム30が動作するクラウドプラットフォームの障害に関係しないとS128において判断すると、障害の要因が遠隔管理システム30の内部によるものであることを、S123において一時管理テーブル54dに追加した障害の要因の箇所として記憶する(S130)。 When the failure detection unit 57c determines in S128 that the failure corresponding to the failure added to the temporary management table 54d in S123 is not related to the failure of the cloud platform on which the remote management system 30 operates, the cause of the failure is the remote management system 30. Is stored as the location of the failure factor added to the temporary management table 54d in S123 (S130).
 障害検出部57cは、S129またはS130の処理の後、S123において一時管理テーブル54dに追加した障害を障害履歴テーブル54eに移動する(S131)。すなわち、障害検出部57cは、S123において一時管理テーブル54dに追加した障害の現時点での全ての情報を障害履歴テーブル54eに反映するとともに、S123において一時管理テーブル54dに追加した障害の現時点での全ての情報を一時管理テーブル54dから削除する。  After the processing of S129 or S130, the failure detection unit 57c moves the failure added to the temporary management table 54d in S123 to the failure history table 54e (S131). That is, the failure detection unit 57c reflects all the current information of the failure added to the temporary management table 54d in S123 on the failure history table 54e, and all the failure information added to the temporary management table 54d in S123 at the current time. Information is deleted from the temporary management table 54d. ‥
 通知処理部58cは、S131の処理の後、S131において障害履歴テーブル54eに移動された障害の情報と、通知先決定用テーブル54fとに基づいて、S131において障害履歴テーブル54eに移動された障害に対して通知先決定用テーブル54fにおいて設定されている、障害の発生の通知先と、障害の発生の通知内容とを決定する(S132)。すなわち、通知処理部58cは、通知先決定用テーブル54fに示される、障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因の箇所と、過去に発生した他の障害との類似度との組み合わせの中から、S131において障害履歴テーブル54eに移動された障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因の箇所と、過去に発生した他の障害との類似度とに対応する組み合わせを特定し、特定した組み合わせに対して通知先決定用テーブル54fに示される、障害の発生の通知先と、障害の発生の通知内容とを決定する。例えば、通知処理部58cは、重要度が特定の重要度より低い障害に関しては、遠隔管理システム30に対して適切な処置を実行することが可能な技術者のみを通知先としても良いし、重要度が特定の重要度より高い障害に関しては、遠隔管理システム30に対して適切な処置を実行することが可能な技術者だけでなく、画像形成装置を管理している販社など、より広範囲の利害関係者を通知先としても良い。 After the processing of S131, the notification processing unit 58c determines the failure moved to the failure history table 54e in S131 based on the failure information moved to the failure history table 54e in S131 and the notification destination determination table 54f. On the other hand, the notification destination of the failure occurrence and the notification content of the failure occurrence set in the notification destination determination table 54f are determined (S132). That is, the notification processing unit 58c indicates the location of the failure, the area where the failure occurred, the importance of the failure, the location of the cause of the failure, and other failures that occurred in the past, which are indicated in the notification destination determination table 54f. From the combination with the similarity degree of No., the location of the failure moved to the failure history table 54e in S131, the area where the failure occurred, the importance of the failure, the location of the cause of the failure, and other past occurrences. The combination corresponding to the similarity with the failure is specified, and the notification destination of the failure occurrence and the notification content of the failure occurrence shown in the notification destination determination table 54f are determined for the specified combination. For example, the notification processing unit 58c may notify only a technician who can execute appropriate measures to the remote management system 30 regarding a failure whose importance level is lower than a specific importance level. With respect to a failure whose degree is higher than a certain degree of importance, not only a technician who can perform appropriate measures for the remote management system 30 but also a wider range of interests such as a sales company that manages the image forming apparatus. The person concerned may be the notification destination.
 通知処理部58cは、S132の処理の後、S132において決定した通知先に、S132において決定した通知内容で通知する(S133)。ここで、通知処理部58cは、S131において障害履歴テーブル54eに移動された障害に関する、障害履歴テーブル54eにおける各種の情報を、S133において通知する通知内容に含めても良い。 After the processing of S132, the notification processing unit 58c notifies the notification destination determined in S132 with the notification content determined in S132 (S133). Here, the notification processing unit 58c may include various kinds of information in the failure history table 54e regarding the failure moved to the failure history table 54e in S131 in the notification content notified in S133.
 通知処理部58cは、S133の処理の後、S131において障害履歴テーブル54eに移動された障害の要因の箇所が遠隔管理システム30の外部であるか否かを、S131において障害履歴テーブル54eに移動された障害の要因の箇所に基づいて判断する(S134)。 After the processing of S133, the notification processing unit 58c moves to the failure history table 54e in S131 whether the location of the cause of the failure moved to the failure history table 54e in S131 is outside the remote management system 30. The determination is made based on the location of the factor of the failure (S134).
 通知処理部58cは、S131において障害履歴テーブル54eに移動された障害の要因の箇所が遠隔管理システム30の外部であるとS134において判断すると、遠隔管理システム30が動作するクラウドプラットフォームの提供者に対して、障害の内容を通知するためのサポート要求を発行する(S135)。 When the notification processing unit 58c determines in S134 that the location of the cause of the failure moved to the failure history table 54e in S131 is outside the remote management system 30, it notifies the provider of the cloud platform on which the remote management system 30 operates. Then, a support request for notifying the content of the failure is issued (S135).
 通知処理部58cは、S131において障害履歴テーブル54eに移動された障害の要因の箇所が遠隔管理システム30の外部ではないとS134において判断するか、S135の処理が終了すると、図11に示す動作を終了する。 The notification processing unit 58c determines in S134 that the location of the failure factor moved to the failure history table 54e in S131 is not outside the remote management system 30 or when the processing of S135 ends, the operation shown in FIG. finish.
 以上に説明したように、本変形例の監視システム50は、遠隔管理システム30に障害が発生した場合(S122でYES)に、遠隔管理システム30の障害を、この障害の重要度に応じた適切な通知先に通知する(S132~S133)ので、遠隔管理システム30に対して適切な処置が講じられることができる。したがって、監視システム50は、遠隔管理システム30による画像形成装置の遠隔管理の安定性を向上することができる。 As described above, in the monitoring system 50 of the present modification, when a failure occurs in the remote management system 30 (YES in S122), the failure of the remote management system 30 is appropriately determined according to the importance of this failure. Since the notification is sent to the appropriate notification destination (S132 to S133), appropriate measures can be taken for the remote management system 30. Therefore, the monitoring system 50 can improve the stability of remote management of the image forming apparatus by the remote management system 30.
 本変形例においても、監視システム50は、遠隔管理システム30から取得した情報だけでなく、画像形成装置から取得した情報にも基づいて遠隔管理システム30の障害を検出する(S121~S122)ので、遠隔管理システム30の障害の検出の精度を向上することができる。 Also in this modification, the monitoring system 50 detects a failure of the remote management system 30 based not only on the information acquired from the remote management system 30 but also on the information acquired from the image forming apparatus (S121 to S122). The accuracy of detecting a failure of the remote management system 30 can be improved.
 また、監視システム50は、遠隔管理システム30から取得した情報だけでなく、遠隔管理システム30が動作するクラウドプラットフォームから取得した情報にも基づいて遠隔管理システム30の障害を検出する(S121~S122)ので、遠隔管理システム30の障害の検出の精度を向上することができる。 Further, the monitoring system 50 detects the failure of the remote management system 30 based not only on the information acquired from the remote management system 30 but also on the information acquired from the cloud platform on which the remote management system 30 operates (S121 to S122). Therefore, the accuracy of detecting a failure of the remote management system 30 can be improved.
 さらに、監視システム50は、遠隔管理システム30の障害の要因がクラウドプラットフォームの障害によるものである場合(S134でYES)に、この障害の内容を通知するためのサポート要求をクラウドプラットフォームの提供者に対して発行する(S135)ので、遠隔管理システム30が動作するクラウドプラットフォームに対して適切な処置が講じられる可能性が向上し、その結果、遠隔管理システム30による画像形成装置の遠隔管理の安定性を向上することができる。 Furthermore, when the cause of the failure of the remote management system 30 is due to the failure of the cloud platform (YES in S134), the monitoring system 50 sends a support request for notifying the content of the failure to the provider of the cloud platform. Since it is issued to the remote management system 30 (S135), the possibility that appropriate measures will be taken for the cloud platform on which the remote management system 30 operates increases, and as a result, the stability of remote management of the image forming apparatus by the remote management system 30 is improved. Can be improved.
 監視システム50は、遠隔管理システム30の障害の要因の箇所が遠隔管理システム30の外部である場合(S134でYES)に、遠隔管理システム30が動作するクラウドプラットフォームの提供者に対して、障害の内容を通知するためのサポート要求を発行する(S135)ので、クラウドプラットフォームの提供者に対して、クラウドプラットフォームの障害の迅速な復旧を促すことができる。しかしながら、監視システム50は、S133の処理の後、S134およびS135の処理を実行せずに図11に示す動作を終了しても良い。 When the location of the cause of failure of the remote management system 30 is outside the remote management system 30 (YES in S134), the monitoring system 50 notifies the provider of the cloud platform on which the remote management system 30 operates of the failure. Since the support request for notifying the contents is issued (S135), it is possible to prompt the cloud platform provider to promptly recover from the failure of the cloud platform. However, the monitoring system 50 may end the operation illustrated in FIG. 11 without executing the processes of S134 and S135 after the process of S133.
 通知先決定用テーブル54fにおける障害の発生の通知の条件には、本実施の形態において、障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因の箇所と、過去に発生した他の障害との類似度とが含まれる。しかしながら、障害の発生の通知の条件には、障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因の箇所と、過去に発生した他の障害との類似度との少なくとも1つが含まれなくても良い。 In the present embodiment, the conditions for notification of the occurrence of a failure in the notification destination determination table 54f include the location of the failure, the area where the failure occurs, the importance of the failure, the location of the cause of the failure, and the location of the past occurrence. It includes the degree of similarity with other obstacles that have occurred. However, the conditions of notification of occurrence of a failure include at least the location of the failure, the area where the failure occurs, the importance of the failure, the location of the cause of the failure, and the similarity with other failures that occurred in the past. One may not be included.
 本変形例においても監視システム50は、遠隔管理システム30とは別のコンピューターによって実現されている。しかしながら、遠隔管理システム30を実現する少なくとも一部のコンピューターと、監視システム50を実現する少なくとも一部のコンピューターとが同一でも良い。 Also in this modification, the monitoring system 50 is realized by a computer different from the remote management system 30. However, at least some of the computers that implement the remote management system 30 and at least some of the computers that implement the monitoring system 50 may be the same.
 次に、上記実施の形態の第2の変形例を図12から図15を参照して説明する。 Next, a second modification of the above embodiment will be described with reference to FIGS. 12 to 15.
 本変形例の監視システム50は、第1の変形例の記憶部54にさらに障害処置テーブルを記憶可能とし、前記記憶部に記憶されたテーブルを用いて情報取得部56が収集した情報に対し情報分析部57による分析および結果通知部58による通知を行うとともに、分析結果に従って自動で所定の処置を遠隔管理システムに対して実行する。本変形例によっても、上記実施の形態と同様の技術的効果を達成する監視システムを実現することが可能である。なお、本変形例の説明においても、上記実施の形態および第1の変形例と同じ構成要素には同じ参照符号を付し、ここでの説明は省略する。 The monitoring system 50 of the present modification makes it possible to further store a failure treatment table in the storage unit 54 of the first modification, and uses the table stored in the storage unit to store information on the information collected by the information acquisition unit 56. The analysis by the analysis unit 57 and the notification by the result notification unit 58 are performed, and a predetermined action is automatically executed to the remote management system according to the analysis result. Also according to this modification, it is possible to realize a monitoring system that achieves the same technical effects as the above-described embodiment. Also in the description of the present modification, the same components as those of the above-described embodiment and the first modification are designated by the same reference numerals, and the description thereof will be omitted here.
 記憶部54は、障害に対する処置を障害毎に示す障害処置テーブル54gを記憶可能である。制御部55は、操作部51または通信部53を介した指示に応じて障害処置テーブル54gを更新することが可能である。 The storage unit 54 is capable of storing a failure treatment table 54g that indicates a failure action for each failure. The control unit 55 can update the failure treatment table 54g according to an instruction via the operation unit 51 or the communication unit 53.
 図13および図14は、本変形例における障害の発生を通知する場合の監視システム50の動作のフローチャートである。なお、クラウド障害テーブル54cを更新する場合の監視システム50の動作は前記第1の変形例と同様であるので本変形例ではその説明を省略する。 13 and 14 are flowcharts of the operation of the monitoring system 50 in the case of notifying the occurrence of a failure in this modification. Since the operation of the monitoring system 50 when updating the cloud failure table 54c is the same as that of the first modification, its description is omitted in this modification.
 監視システム50の制御部55は、例えば1秒毎などの定期的なタイミングなど、特定のタイミングで図13および図14に示す動作を実行する。 The control unit 55 of the monitoring system 50 executes the operation shown in FIGS. 13 and 14 at a specific timing, such as a regular timing such as every second.
 ステップS121からステップS131は第1の変形例と同様で同様であるのでここでの説明は省略する。 Steps S121 to S131 are the same as those of the first modified example, and therefore the description thereof is omitted here.
 通知処理部58cは、S131の処理の後、S131において障害履歴テーブル54eに移動された障害の情報と、通知先決定用テーブル54fとに基づいて、S131において障害履歴テーブル54eに移動された障害に対して通知先決定用テーブル54fにおいて設定されている、障害の発生の通知先を決定する(S132)。すなわち、通知処理部58cは、通知先決定用テーブル54fに示される、障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因の箇所との組み合わせの中から、S131において障害履歴テーブル54eに移動された障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因の箇所とに対応する組み合わせを特定し、特定した組み合わせに対して通知先決定用テーブル54fに示される、障害の発生の通知先を決定する。例えば、通知処理部58cは、重要度が特定の重要度より低い障害に関しては、遠隔管理システム30に対して適切な処置を実行することが可能な技術者のみを通知先としても良いし、重要度が特定の重要度より高い障害に関しては、遠隔管理システム30に対して適切な処置を実行することが可能な技術者だけでなく、画像形成装置を管理している販社など、より広範囲の利害関係者を通知先としても良い。 After the processing of S131, the notification processing unit 58c determines the failure moved to the failure history table 54e in S131 based on the failure information moved to the failure history table 54e in S131 and the notification destination determination table 54f. On the other hand, the notification destination of the failure occurrence set in the notification destination determination table 54f is determined (S132). That is, the notification processing unit 58c selects the failure in S131 from the combinations of the failure location, the failure occurrence area, the failure importance, and the failure factor location shown in the notification destination determination table 54f. The combination corresponding to the location of the failure, the area where the failure has occurred, the importance of the failure, and the location of the cause of the failure, which have been moved to the history table 54e, is identified, and the notification destination determination table 54f is specified for the identified combination. Determine the notification destination of the failure occurrence shown in. For example, the notification processing unit 58c may notify only a technician who can execute appropriate measures to the remote management system 30 regarding a failure whose importance level is lower than a specific importance level. With respect to a failure whose degree is higher than a certain degree of importance, not only a technician who can perform appropriate measures for the remote management system 30 but also a wider range of interests such as a sales company that manages the image forming apparatus. The person concerned may be the notification destination.
 通知処理部58cは、S132の処理の後、S131において障害履歴テーブル54eに移動された障害の、過去に発生した他の障害との類似度が第1の類似度以上であるか否かを判断する(S136)。 After the processing of S132, the notification processing unit 58c determines whether or not the similarity of the failure moved to the failure history table 54e in S131 with other failures that occurred in the past is equal to or higher than the first similarity. Yes (S136).
 通知処理部58cは、第1の類似度以上であるとS133において判断すると、S131において障害履歴テーブル54eに移動された障害との類似度が第1の類似度以上であるとS133において判断した障害が障害処置テーブル54gに示されているか否かを判断する(S137)。 When the notification processing unit 58c determines in S133 that the similarity is equal to or higher than the first similarity, the failure determined in S133 that the similarity to the failure moved to the failure history table 54e in S131 is equal to or higher than the first similarity. Is displayed in the failure treatment table 54g (S137).
 通知処理部58cは、S131において障害履歴テーブル54eに移動された障害との類似度が第1の類似度以上であるとS136において判断した障害が障害処置テーブル54gに示されているとS137において判断すると、S131において障害履歴テーブル54eに移動された障害との類似度が第1の類似度以上であるとS136において判断した障害に障害処置テーブル54gにおいて対応付けられている処置を遠隔管理システム30に対して自動で実行する(S138)。 The notification processing unit 58c determines in S137 that the failure determined in S136 that the similarity to the failure moved to the failure history table 54e in S131 is equal to or higher than the first similarity is indicated in the failure treatment table 54g. Then, in the remote management system 30, the fault management table 30g associates the fault determined in S136 with the fault that has been moved to the fault history table 54e in S131 and has a similarity not lower than the first similarity. On the other hand, it is automatically executed (S138).
 次いで、通知処理部58cは、適切な処置を実行した旨を、S132において決定した通知先に通知する予定の通知内容に含める(S1369)。 Next, the notification processing unit 58c includes, in the notification content scheduled to be notified to the notification destination determined in S132, the fact that the appropriate action has been performed (S1369).
 通知処理部58cは、第1の類似度以上ではないとS136において判断すると、S131において障害履歴テーブル54eに移動された障害の、過去に発生した他の障害との類似度が第2の類似度未満であるか否かを判断する(S140)。ここで、第2の類似度は、第1の類似度以下であれば良い。 If the notification processing unit 58c determines in S136 that the similarity is not equal to or higher than the first similarity, the similarity of the failure moved to the failure history table 54e in S131 to the other failure that occurred in the past is the second similarity. It is determined whether it is less than (S140). Here, the second similarity may be equal to or lower than the first similarity.
 通知処理部58cは、第2の類似度未満であるとS140において判断すると、過去に経験したことがない重大な障害である旨を、S132において決定した通知先に通知する予定の通知内容に含める(S141)。 When the notification processing unit 58c determines in S140 that the degree of similarity is less than the second similarity, the notification processing unit 58c includes, in the notification content scheduled to be notified to the notification destination determined in S132, a serious failure that has not been experienced in the past. (S141).
 通知処理部58cは、S131において障害履歴テーブル54eに移動された障害との類似度が第1の類似度以上であるとS136において判断した障害が障害処置テーブル54gに示されていないとS137において判断するか、S139の処理を実行するか、第2の類似度未満ではないとS140において判断するか、またはS141の処理を実行すると、障害が発生した旨の通知内容でS132において決定した通知先に通知する(S142)。ここで、通知処理部58cは、S131において障害履歴テーブル54eに移動された障害に関する、障害履歴テーブル54eにおける各種の情報を、S142において通知する通知内容に含めても良い。なお、通知処理部58cは、S139の処理を実行済みである場合には、適切な処置を実行した旨をS142において通知する通知内容に含めている。また、通知処理部58cは、S141の処理を実行済みである場合には、過去に経験したことがない重大な障害である旨をS142において通知する通知内容に含めている。 The notification processing unit 58c determines in S137 that the failure determined in S136 that the similarity to the failure moved to the failure history table 54e in S131 is equal to or higher than the first similarity is not indicated in the failure treatment table 54g. Then, the process of S139 is performed, it is determined in S140 that the degree of similarity is not less than the second similarity, or when the process of S141 is performed, the notification destination determined in S132 is notified to the notification destination indicating that a failure has occurred. Notify (S142). Here, the notification processing unit 58c may include various information in the failure history table 54e regarding the failure moved to the failure history table 54e in S131 in the notification content notified in S142. In addition, when the processing of S139 has been executed, the notification processing unit 58c includes, in the notification content of which the notification is performed in S142, that the appropriate treatment has been executed. In addition, when the processing of S141 has been executed, the notification processing unit 58c includes in the notification content of which the notification in S142 is a serious failure that has not been experienced in the past.
 通知処理部58cは、S142の処理の後、S131において障害履歴テーブル54eに移動された障害の要因の箇所が遠隔管理システム30の外部であるか否かを、S131において障害履歴テーブル54eに移動された障害の要因の箇所に基づいて判断する(S143)。 After the processing of S142, the notification processing unit 58c moves to the failure history table 54e in S131 whether the location of the cause of the failure moved to the failure history table 54e in S131 is outside the remote management system 30. The determination is made based on the location of the factor of the failure (S143).
 通知処理部58cは、S131において障害履歴テーブル54eに移動された障害の要因の箇所が遠隔管理システム30の外部であるとS143において判断すると、遠隔管理システム30が動作するクラウドプラットフォームの提供者に対して、障害の内容を通知するためのサポート要求を発行する(S144)。 If the notification processing unit 58c determines in S143 that the location of the cause of the failure moved to the failure history table 54e in S131 is outside the remote management system 30, the notification processing unit 58c informs the provider of the cloud platform on which the remote management system 30 operates. Then, a support request for notifying the content of the failure is issued (S144).
 通知処理部58cは、S131において障害履歴テーブル54eに移動された障害の要因の箇所が遠隔管理システム30の外部ではないとS143において判断するか、S144の処理が終了すると、図13および図14に示す動作を終了する。 The notification processing unit 58c determines in S143 that the location of the cause of the failure moved to the failure history table 54e in S131 is not outside the remote management system 30, or when the processing in S144 ends, the notification processing section 58c is displayed as shown in FIGS. The operation shown is ended.
 以上に説明したように、監視システム50は、遠隔管理システム30に障害が発生した場合(S122でYES)に、遠隔管理システム30の障害を、この障害の、過去に発生した障害との類似度に応じた通知内容で通知する(S136~S142)ので、遠隔管理システム30に対して適切な処置が講じられることができる。したがって、監視システム50は、遠隔管理システム30による画像形成装置の遠隔管理の安定性を向上することができる。 As described above, when a failure has occurred in the remote management system 30 (YES in S122), the monitoring system 50 regards the failure of the remote management system 30 as a degree of similarity between this failure and a failure that occurred in the past. Since notification is made with the notification content according to (S136 to S142), appropriate measures can be taken for the remote management system 30. Therefore, the monitoring system 50 can improve the stability of remote management of the image forming apparatus by the remote management system 30.
 監視システム50は、過去に発生した障害との類似度が高い障害が遠隔管理システム30に発生した場合(S136でYES)に、遠隔管理システム30の障害と類似する、過去に発生した障害に対応付けられている処置を実行する(S138)ので、遠隔管理システム30に対して適切な処置を講じることができる。 When the remote management system 30 has a failure having a high degree of similarity to the failure that occurred in the past (YES in S136), the monitoring system 50 responds to the failure that occurred in the past and is similar to the failure of the remote management system 30. Since the attached procedure is executed (S138), an appropriate procedure can be taken for the remote management system 30.
 監視システム50は、過去に発生した障害との類似度が低い障害が遠隔管理システム30に発生した場合(S140でYES)に、重大な障害である旨を通知する(S141~S142)ので、過去に経験したことがない重大な障害に対して適切な処置が速やかに講じられることができる。 Since the monitoring system 50 notifies the remote management system 30 of a fault having a low degree of similarity to a fault that has occurred in the past (YES in S140), it notifies that the fault is a serious one (S141 to S142). Appropriate measures can be promptly taken for serious disabilities that have never been experienced before.
 監視システム50は、遠隔管理システム30の障害の、過去に発生した障害との類似度を、特定の学習アルゴリズムを利用して判定する(S124)ので、利便性を向上することができる。 The monitoring system 50 determines the degree of similarity between the failure of the remote management system 30 and the failure that occurred in the past by using a specific learning algorithm (S124), so that convenience can be improved.
 監視システム50は、遠隔管理システム30から取得した情報だけでなく、画像形成装置と、遠隔管理システム30が動作するクラウドプラットフォームとから取得した情報にも基づいて遠隔管理システム30の障害を検出する(S121~S122)ので、遠隔管理システム30の障害の検出の精度を向上することができる。 The monitoring system 50 detects a failure of the remote management system 30 based on not only the information acquired from the remote management system 30 but also the information acquired from the image forming apparatus and the cloud platform on which the remote management system 30 operates ( Since S121 to S122), the accuracy of detecting a failure of the remote management system 30 can be improved.
 なお、監視システム50は、図14に示す動作に代えて、図15に示す動作を実行しても良い。図15に示す動作は、図14に示す動作において、S138の処理およびS139の処理に代えて、S151の処理を実行するものである。すなわち、図15に示す動作において、通知処理部58cは、S131において障害履歴テーブル54eに移動された障害との類似度が第1の類似度以上であるとS133において判断した障害が障害処置テーブル54gに示されているとS134において判断すると、S131において障害履歴テーブル54eに移動された障害との類似度が第1の類似度以上であるとS136において判断した障害に障害処置テーブル54gにおいて対応付けられている処置を、S132において決定した通知先に通知する予定の通知内容に含めて(S151)、S142の処理を実行する。 Note that the monitoring system 50 may execute the operation shown in FIG. 15 instead of the operation shown in FIG. The operation shown in FIG. 15 is to execute the processing of S151 instead of the processing of S138 and the processing of S139 in the operation shown in FIG. That is, in the operation illustrated in FIG. 15, the notification processing unit 58c determines in step S133 that the similarity to the failure moved to the failure history table 54e in step S131 is equal to or higher than the first similarity. If it is determined in S134 that the failure is indicated in step S134, the failure determined in S136 that the similarity to the failure moved to the failure history table 54e in S131 is equal to or higher than the first similarity is associated in the failure treatment table 54g. The specified action is included in the notification content scheduled to be notified to the notification destination determined in S132 (S151), and the process of S142 is executed.
 監視システム50は、過去に発生した障害との類似度が高い障害が遠隔管理システム30に発生した場合(S136でYES)に、遠隔管理システム30の障害と類似する、過去に発生した障害に対応付けられている処置を通知する(S151およびS142)とき、遠隔管理システム30に対して適切な処置が講じられることができる。 When the remote management system 30 has a failure having a high degree of similarity to the failure that occurred in the past (YES in S136), the monitoring system 50 responds to the failure that occurred in the past and is similar to the failure of the remote management system 30. When notifying the attached action (S151 and S142), appropriate action can be taken to the remote management system 30.
 通知先決定用テーブル54fにおける障害の発生の通知の条件には、本実施の形態において、障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因の箇所とが含まれる。しかしながら、障害の発生の通知の条件には、障害の箇所と、障害の発生地域と、障害の重要度と、障害の要因の箇所との少なくとも1つが含まれなくても良い。 In the present embodiment, the conditions for notification of failure occurrence in the notification destination determination table 54f include the location of the failure, the area where the failure occurred, the importance of the failure, and the location of the cause of the failure. However, the condition of the notification of the occurrence of the failure may not include at least one of the location of the failure, the area where the failure occurs, the importance of the failure, and the location of the cause of the failure.
 監視システム50は、本実施の形態において、S142における通知の通知先をS132で決定する。しかしながら、監視システム50は、遠隔管理システム30の運用管理者を常にS142における通知の通知先としても良い。 In the present embodiment, the monitoring system 50 determines the notification destination of the notification in S142 in S132. However, the monitoring system 50 may always use the operation manager of the remote management system 30 as the notification destination of the notification in S142.
 本変形例においても、監視システム50は遠隔管理システム30とは別のコンピューターによって実現されている。しかしながら、遠隔管理システム30を実現する少なくとも一部のコンピューターと、監視システム50を実現する少なくとも一部のコンピューターとが同一でも良い。 Also in this modification, the monitoring system 50 is realized by a computer different from the remote management system 30. However, at least some of the computers that implement the remote management system 30 and at least some of the computers that implement the monitoring system 50 may be the same.
 22 画像形成装置
 30 遠隔管理システム
 31 コマンドサーバー
 32 デバイス管理サーバー
 34 ユーザー管理サーバー
 35 データベース
 36 キャッシュサーバー
 40 クラウドプロバイダーサーバー
 50 監視システム(コンピューター)
 54a 監視プログラム
 56 情報取得部
 57 情報分析部
 58 結果通知部
22 image forming apparatus 30 remote management system 31 command server 32 device management server 34 user management server 35 database 36 cache server 40 cloud provider server 50 monitoring system (computer)
54a Monitoring program 56 Information acquisition unit 57 Information analysis unit 58 Result notification unit

Claims (15)

  1.  画像形成装置を遠隔管理する遠隔管理システムから情報を取得する情報取得部と、
     前記情報取得部によって取得された情報を分析する情報分析部と、
     前記情報分析部による分析の結果を通知する結果通知部と
     を備え、
     前記情報分析部は、前記情報取得部によって取得された情報に基づいて前記遠隔管理システムの障害を検出し、
     前記結果通知部は、前記情報分析部によって検出された、前記遠隔管理システムの障害を通知する、
    ことを特徴とする監視システム。
    An information acquisition unit that acquires information from a remote management system that remotely manages the image forming apparatus;
    An information analysis unit that analyzes the information acquired by the information acquisition unit;
    And a result notifying section for notifying the result of the analysis by the information analyzing section,
    The information analysis unit detects a failure of the remote management system based on the information acquired by the information acquisition unit,
    The result notifying unit notifies a failure of the remote management system detected by the information analysis unit,
    A monitoring system characterized by that.
  2.  前記情報取得部は、
      前記画像形成装置と、
      前記遠隔管理システムが動作するICT基盤と
     の少なくとも1つからも情報を取得することを特徴とする請求項1に記載の監視システム。
    The information acquisition unit,
    The image forming apparatus;
    The monitoring system according to claim 1, wherein the information is also acquired from at least one of an ICT base on which the remote management system operates.
  3.  前記情報分析部は、
      時系列と、
      情報が示す障害の重要度と、
      情報が示す障害の、過去に発生した障害との類似度と、
      情報が取得された構成要素とは異なる構成要素で同時に障害が発生しているか否かと
     の少なくとも1つの基準によって情報を振り分けて分析することを特徴とする請求項1または請求項2に記載の監視システム。
    The information analysis unit,
    Time series,
    The severity of the failure indicated by the information,
    The similarity of the failure indicated by the information to the failure that occurred in the past,
    The information according to claim 1 or 2, wherein the information is sorted and analyzed according to at least one criterion of whether or not a failure occurs simultaneously in a component different from the component from which the information was acquired. system.
  4.  前記情報分析部は、検出した前記障害に対応付けられた処理を決定することを特徴とする請求項1から請求項3のいずれかに記載の監視システム。 The monitoring system according to any one of claims 1 to 3, wherein the information analysis unit determines a process associated with the detected failure.
  5.  前記結果通知部は、前記情報分析部によって分析された、前記遠隔管理システムの障害が予め設定された条件を満たす場合に、この条件に対応付けて設定された通知先に、前記障害を通知することを特徴とする請求項1から請求項4のいずれかに記載の監視システム。 When the failure of the remote management system analyzed by the information analysis section satisfies a preset condition, the result notification section notifies the failure to the notification destination set in association with this condition. The monitoring system according to any one of claims 1 to 4, wherein:
  6.  前記結果通知部は、前記障害を示すメッセージと前記処理のコマンドを送信することを特徴とする請求項5に記載の監視システム。 The monitoring system according to claim 5, wherein the result notification unit transmits a message indicating the failure and a command for the processing.
  7.  前記情報分析部は、検出した前記障害の重要度を判定し、
     前記結果通知部は、前記情報分析部によって検出された前記障害を前記重要度に対応付けて設定された通知先に通知することを特徴とする請求項6に記載の監視システム。
    The information analysis unit determines the importance of the detected failure,
    7. The monitoring system according to claim 6, wherein the result notifying unit notifies the notification destination set in association with the degree of importance of the failure detected by the information analysis unit.
  8.  前記情報取得部は、前記遠隔管理システムが動作するICT基盤から情報を取得し、
     前記情報分析部は、前記ICT基盤から取得した前記情報から前記ITC基盤の障害の情報を収集し、前記遠隔管理システムの前記障害と前記ITC基盤の前記障害とに基づいて、前記遠隔管理システムの前記障害の要因が前記ICT基盤の前記障害によるものであるか否かを判断し、
     前記結果通知部は、前記遠隔管理システムの障害の前記要因が前記ICT基盤の障害によるものであると前記情報分析部によって判断された場合に、前記遠隔管理システムの前記障害の内容を通知するためのサポート要求を前記ICT基盤の提供者に対して発行することを特徴とする請求項2に記載の監視システム。
    The information acquisition unit acquires information from an ICT platform on which the remote management system operates,
    The information analysis unit collects information on a failure of the ITC base from the information acquired from the ICT base, and based on the failure of the remote management system and the failure of the ITC base, the information management unit of the remote management system. Determining whether the cause of the failure is due to the failure of the ICT base,
    The result notification unit notifies the content of the failure of the remote management system when the information analysis unit determines that the factor of the failure of the remote management system is due to the failure of the ICT base. 3. The monitoring system according to claim 2, wherein a support request for the ICT-based provider is issued to the ICT-based provider.
  9.  前記情報分析部は、検出した前記遠隔管理システムの前記障害の、過去に発生した前記遠隔管理システムの障害との類似度を判定し、
     前記結果通知部は、前記情報分析部によって判定された類似度に応じた通知内容で、検出された前記遠隔管理システムの前記障害を通知することを特徴とする請求項3に記載の監視システム。
    The information analysis unit determines the degree of similarity between the detected failure of the remote management system and the failure of the remote management system that occurred in the past,
    The monitoring system according to claim 3, wherein the result notifying unit notifies the detected failure of the remote management system with a notification content according to the similarity determined by the information analysis unit.
  10.  前記結果通知部は、判定された前記類似度が第1の類似度以上である場合、検出された前記遠隔管理システムの前記障害との類似度が前記第1の類似度以上である、過去に発生した障害に対応付けられている処置を前記遠隔管理システムに対して実行することを特徴とする請求項9に記載の監視システム。 When the determined similarity is equal to or higher than a first similarity, the result notification unit determines that the detected similarity to the failure of the remote management system is equal to or higher than the first similarity. The monitoring system according to claim 9, wherein a treatment associated with the occurred fault is executed on the remote management system.
  11.  前記結果通知部は、前記処置を前記遠隔管理システムに実行した場合、実行した前記処置を通知内容に含めることを特徴とする請求項10に記載の監視システム。 11. The monitoring system according to claim 10, wherein the result notifying unit includes the executed action in the notification content when the action is executed by the remote management system.
  12.  前記結果通知部は、前記情報分析部によって判定された前記類似度が第2の類似度未満である場合、重大な障害である旨を通知内容に含めることを特徴とする請求項9に記載の監視システム。 10. The result notification unit according to claim 9, wherein when the similarity determined by the information analysis unit is less than a second similarity, the result notification unit includes in the notification content a serious failure. Monitoring system.
  13.  前記情報分析部は、特定の学習アルゴリズムを利用して類似度を判定することを特徴とする請求項9から請求項13までのいずれかに記載の監視システム。 The monitoring system according to any one of claims 9 to 13, wherein the information analysis unit determines the degree of similarity using a specific learning algorithm.
  14.  コンピューターと記憶部を用いる監視方法であり、
     画像形成装置を遠隔管理する遠隔管理システムから情報を取得する情報取得工程と、
     前記情報取得工程で取得された情報を分析する情報分析工程と、
     前記情報分析工程での分析の結果を通知する結果通知工程とを含み、
     前記情報分析工程は、前記情報取得工程で取得された情報に基づいて前記遠隔管理システムの障害を検出する工程を有し、前記結果通知工程は、前記情報分析工程で検出された、前記遠隔管理システムの障害を通知する工程を有する、
    ことを特徴とする監視方法。
    It is a monitoring method that uses a computer and a storage unit,
    An information acquisition step of acquiring information from a remote management system that remotely manages the image forming apparatus;
    An information analysis step of analyzing the information acquired in the information acquisition step,
    And a result notifying step of notifying the result of the analysis in the information analyzing step,
    The information analysis step includes a step of detecting a failure of the remote management system based on the information acquired in the information acquisition step, and the result notification step includes the remote management detected in the information analysis step. Has a process of notifying a system failure,
    A monitoring method characterized by the above.
  15.  画像形成装置を遠隔管理する遠隔管理システムから情報を取得する情報取得部と、
     前記情報取得部によって取得された情報を分析する情報分析部と、
     前記情報分析部による分析の結果を通知する結果通知部と
     をコンピューターに実現させ、
     前記情報分析部は、前記情報取得部によって取得された情報に基づいて前記遠隔管理システムの障害を検出し、
     前記結果通知部は、前記情報分析部によって検出された、前記遠隔管理システムの障害を通知する、
    ことを特徴とする監視プログラム。
    An information acquisition unit that acquires information from a remote management system that remotely manages the image forming apparatus;
    An information analysis unit that analyzes the information acquired by the information acquisition unit;
    And a result notifying unit for notifying the result of the analysis by the information analyzing unit,
    The information analysis unit detects a failure of the remote management system based on the information acquired by the information acquisition unit,
    The result notifying unit notifies a failure of the remote management system detected by the information analysis unit,
    A monitoring program characterized by that.
PCT/JP2019/050841 2018-12-28 2019-12-25 Monitoring system, monitoring method, and monitoring program WO2020138176A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201980086125.1A CN113260984A (en) 2018-12-28 2019-12-25 Monitoring system, monitoring method, and monitoring program
US17/417,475 US11635923B2 (en) 2018-12-28 2019-12-25 Monitoring system, monitoring method, and monitoring program

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
JP2018246644A JP2022044845A (en) 2018-12-28 2018-12-28 Monitoring system and monitoring program
JP2018246646A JP2022044846A (en) 2018-12-28 2018-12-28 Monitoring system and monitoring program
JP2018-246646 2018-12-28
JP2018246635A JP2022044844A (en) 2018-12-28 2018-12-28 Monitoring system and monitoring program
JP2018-246635 2018-12-28
JP2018-246644 2018-12-28

Publications (1)

Publication Number Publication Date
WO2020138176A1 true WO2020138176A1 (en) 2020-07-02

Family

ID=71127140

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2019/050841 WO2020138176A1 (en) 2018-12-28 2019-12-25 Monitoring system, monitoring method, and monitoring program

Country Status (3)

Country Link
US (1) US11635923B2 (en)
CN (1) CN113260984A (en)
WO (1) WO2020138176A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114884930B (en) * 2022-04-22 2023-05-09 广东悦伍纪网络技术有限公司 Method and system for monitoring and processing basic deployment service faults of cloud mobile phone

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH07162420A (en) * 1993-12-03 1995-06-23 Mitsubishi Electric Corp Network monitor system
JP2006099249A (en) * 2004-09-28 2006-04-13 Fujitsu Ltd Fault management device and fault management method
JP2012088855A (en) * 2010-10-18 2012-05-10 Nec Computertechno Ltd Event occurrence notification apparatus, event occurrence notification method, event occurrence notification program
JP2013073389A (en) * 2011-09-27 2013-04-22 Nec Corp Fault analysis device, fault analysis method and program
JP2013250915A (en) * 2012-06-04 2013-12-12 Canon Inc Service providing device, information process device, image formation device, control method of printing system and computer program
WO2016121728A1 (en) * 2015-01-27 2016-08-04 日本電気株式会社 Network function virtualization management and orchestration device, system, management method, and program
JP2018136656A (en) * 2017-02-21 2018-08-30 株式会社野村総合研究所 Troubleshooting supporting system

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPS5536419A (en) 1978-09-08 1980-03-14 Yamasa Shoyu Co Ltd 2-substituted adenosine derivative and its preparation
JPS5614260A (en) 1979-07-16 1981-02-12 Canon Inc Developing device
JPH0830152A (en) 1994-07-14 1996-02-02 Fuji Xerox Co Ltd Remote trouble shooting system
JP2011002906A (en) * 2009-06-16 2011-01-06 Fujitsu Ltd Monitoring program, monitoring device, and monitoring method
US8453027B2 (en) * 2009-09-17 2013-05-28 Microsoft Corporation Similarity detection for error reports
JP6331778B2 (en) 2014-07-01 2018-05-30 富士ゼロックス株式会社 Information management control device, information management control program
JP6303875B2 (en) 2014-07-01 2018-04-04 富士ゼロックス株式会社 Information management control device, information management control program
JP6500663B2 (en) 2015-07-16 2019-04-17 株式会社リコー INFORMATION PROCESSING SYSTEM, INFORMATION PROCESSING APPARATUS, PROGRAM, AND METHOD FOR EMBEDDING FAULT PREDICTION LOGIC
US20190054700A1 (en) * 2017-08-15 2019-02-21 Cincinnati Incorporated Machine learning for additive manufacturing
JP6973067B2 (en) * 2017-12-28 2021-11-24 富士通株式会社 Data processing programs, data processing methods, and data processing equipment
US10996906B2 (en) * 2018-02-21 2021-05-04 Canon Kabushiki Kaisha Image processing apparatus that is connectable with information processing apparatus providing service to image processing apparatus, control method therefor, and storage medium storing control program therefor
JP7046648B2 (en) * 2018-02-27 2022-04-04 キヤノン株式会社 Print processing system, method, and program

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH07162420A (en) * 1993-12-03 1995-06-23 Mitsubishi Electric Corp Network monitor system
JP2006099249A (en) * 2004-09-28 2006-04-13 Fujitsu Ltd Fault management device and fault management method
JP2012088855A (en) * 2010-10-18 2012-05-10 Nec Computertechno Ltd Event occurrence notification apparatus, event occurrence notification method, event occurrence notification program
JP2013073389A (en) * 2011-09-27 2013-04-22 Nec Corp Fault analysis device, fault analysis method and program
JP2013250915A (en) * 2012-06-04 2013-12-12 Canon Inc Service providing device, information process device, image formation device, control method of printing system and computer program
WO2016121728A1 (en) * 2015-01-27 2016-08-04 日本電気株式会社 Network function virtualization management and orchestration device, system, management method, and program
JP2018136656A (en) * 2017-02-21 2018-08-30 株式会社野村総合研究所 Troubleshooting supporting system

Also Published As

Publication number Publication date
CN113260984A (en) 2021-08-13
US20220066704A1 (en) 2022-03-03
US11635923B2 (en) 2023-04-25

Similar Documents

Publication Publication Date Title
US7421371B2 (en) Automated performance analysis and failure remediation
JP6306499B2 (en) Fault information providing server and fault information providing method
JP2011100283A (en) Management device, equipment management method, equipment management program, recording medium, and equipment management system
JP2008191878A (en) Remote diagnostic-failure responding system, remote diagnostic-failure responding device, remote diagnostic-failure response instruction device, remote diagnostic-falure responding method, and remote diagnostic-failure responding program
JPWO2015037603A1 (en) Remote monitoring system, remote monitoring method, and program
US11068217B2 (en) Image forming apparatus and control method
US8032789B2 (en) Apparatus maintenance system and method
WO2020138176A1 (en) Monitoring system, monitoring method, and monitoring program
JP2003271422A (en) Preventive maintenance decision processing method, preventive maintenance decision processing program and maintenance managing method
JP4102592B2 (en) Failure information notification system with an aggregation function and a program for causing a machine to function as a failure information notification means with an aggregation function
JP2008035444A (en) Apparatus management device and remote apparatus diagnosis management system
US9531611B2 (en) Device management system and method
JP2014002660A (en) Maintenance component production management device and maintenance component production management method
JP2022044844A (en) Monitoring system and monitoring program
JP2022044845A (en) Monitoring system and monitoring program
US20200387428A1 (en) Information processing system
JP6222759B2 (en) Failure notification device, failure notification method and program
US20160218945A1 (en) Monitoring apparatus, system, control method for monitoring apparatus, control method for system, and program
JP2022044846A (en) Monitoring system and monitoring program
US10986014B2 (en) Monitoring system and non-transitory computer-readable recording medium storing monitoring program
JP7457282B2 (en) Data linkage system and configuration change system
US20240179098A1 (en) System and method of controlling system
JP7163687B2 (en) Information processing device, information processing system and information processing program
JP2020107156A (en) Monitoring system, monitoring program, and system
JP7167749B2 (en) Information processing device, information processing system, and information processing program

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19902635

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19902635

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP