WO2015145523A1 - Système de traitement d'erreur - Google Patents

Système de traitement d'erreur Download PDF

Info

Publication number
WO2015145523A1
WO2015145523A1 PCT/JP2014/057973 JP2014057973W WO2015145523A1 WO 2015145523 A1 WO2015145523 A1 WO 2015145523A1 JP 2014057973 W JP2014057973 W JP 2014057973W WO 2015145523 A1 WO2015145523 A1 WO 2015145523A1
Authority
WO
WIPO (PCT)
Prior art keywords
error
message
unit
storage unit
database
Prior art date
Application number
PCT/JP2014/057973
Other languages
English (en)
Japanese (ja)
Inventor
紘一郎 古川
Original Assignee
三菱電機インフォメーションシステムズ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 三菱電機インフォメーションシステムズ株式会社 filed Critical 三菱電機インフォメーションシステムズ株式会社
Priority to JP2014525220A priority Critical patent/JP5808861B1/ja
Priority to CN201480001056.7A priority patent/CN105122163B/zh
Priority to PCT/JP2014/057973 priority patent/WO2015145523A1/fr
Publication of WO2015145523A1 publication Critical patent/WO2015145523A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B23/00—Testing or monitoring of control systems or parts thereof
    • G05B23/02—Electric testing or monitoring
    • G05B23/0205—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults
    • G05B23/0259—Electric testing or monitoring by means of a monitoring system capable of detecting and responding to faults characterized by the response to fault detection
    • G05B23/0267—Fault communication, e.g. human machine interface [HMI]
    • G05B23/0272—Presentation of monitored results, e.g. selection of status reports to be displayed; Filtering information to the user

Definitions

  • the present invention relates to a technique for handling errors that occur in production facilities constituting a factory automation system (hereinafter referred to as FA system).
  • FA system factory automation system
  • a programmable logic controller (hereinafter referred to as PLC) that controls the production facility
  • a graphic operation terminal (hereinafter referred to as GOT) that is a PLC HMI (Human Machine Interface) Is provided.
  • the GOT acquires an error code indicating the error that has occurred from the PLC.
  • the GOT acquires an error message corresponding to the error code from the internal memory and displays it. The operator checks the error message displayed on the GOT, identifies the cause of the error, and takes action.
  • the FA system initially operates with a small number of production facilities, and the number of production facilities may gradually increase as demand increases.
  • the number of production facilities is small, it does not take much time to maintain error codes and error messages for each GOT.
  • the effort gradually increases. Therefore, it is desired to reduce the maintenance work of the error code and the error message due to the change of the production facility or PLC by providing a server for centrally managing the error code and the error message.
  • This invention has been made in view of the circumstances specific to the FA system described above.
  • the management of the error code and the error message can be smoothly transferred to a centralized management by a server or the like. With the goal.
  • the error handling system is: An error that performs processing related to an error that has occurred in the production facility in a factory automation system that includes a production facility, a PLC (programmable logic controller) that controls the production facility, and an interface device that is an HMI (human machine interface) of the PLC
  • a processing system comprising an error database and the interface device;
  • the error database is For each error code, an error information storage unit that stores a message indicating the content of the error is provided,
  • the interface device includes: For each error code, a message storage unit that stores a message indicating the content of the error;
  • An error code acquisition unit for acquiring an error code of an error that has occurred in the production facility;
  • a database search unit that searches the error information storage unit using the error code acquired by the error code acquisition unit as a key, and acquires a message;
  • an internal search unit that searches the message storage unit using the error code acquired by the error code acquisition unit as a key, and acquires a message
  • a display unit that displays messages acquired
  • the error information storage unit stores, for each error code, a message and handling information indicating a handling method of the error,
  • the database search unit acquires the handling information together with the message, When the display unit displays the message acquired by the database search unit, the display unit also displays the handling information.
  • the error database further includes A history storage unit that stores an error code used as a key by the database search unit as a history, And a history output unit that outputs an error code stored in the history storage unit.
  • the history output unit outputs only error codes that are not stored in the error information storage unit among error codes stored in the history storage unit.
  • the interface device further includes: A recovery time measurement unit that measures a recovery time from the occurrence of the error until the error is resolved,
  • the history storage unit stores the recovery time measured by the recovery time measurement unit together with an error code,
  • the history output unit outputs the recovery time together with the error code.
  • the interface device further includes: A message storage unit for storing the error code acquired by the error code acquisition unit and the message searched by the internal search unit in the error information storage unit when the database search unit cannot acquire the message; It is characterized by providing.
  • an error message acquired from the error database is output for the error code stored in the error database, and an interface device (for example, GOT is used for an error code not stored in the error database).
  • the error message stored in is output. Therefore, it is possible to gradually shift the management of the error message to the unified management using the error database while making use of the error message stored in the interface device. Further, when the management of the error message is shifted to the centralized management using the error database, it is not necessary to download all the error messages stored in the interface device and register them in the error database. Therefore, no large traffic is generated in the error database when shifting to the centralized management.
  • FIG. 1 is a configuration diagram of an error processing system 100 according to Embodiment 1.
  • FIG. FIG. 3 is a functional configuration diagram of a GOT 30 and an error database 40 according to the first embodiment.
  • 3 is a flowchart showing processing of the error processing system 100 according to the first embodiment.
  • FIG. The function block diagram of GOT30 and the error database 40 which concern on Embodiment 2.
  • FIG. 9 is a flowchart showing processing of the error processing system 100 according to the second embodiment.
  • FIG. 6 is a functional configuration diagram of a GOT 30 and an error database 40 according to the third embodiment.
  • 10 is a flowchart showing processing of the error processing system 100 according to the third embodiment.
  • FIG. 1 is a configuration diagram of an error processing system 100 according to the first embodiment.
  • the error processing system 100 is a system that performs processing related to an error that has occurred in the production facility 10 constituting the FA system.
  • the error processing system 100 includes a production facility 10, a PLC 20, a GOT 30 (an example of an interface device), an error database 40, and an AP server 50 (application server).
  • the production equipment 10 and the corresponding PLC 20, the PLC 20 and the corresponding GOT 30, each GOT 30 and the error database 40, and the error database 40 and the AP server 50 are connected by a network. In the network between each GOT 30 and the error database 40 and between the error database 40 and the AP server 50, traffic may be limited to a certain level or less.
  • FIG. 2 is a functional configuration diagram of the GOT 30 and the error database 40 according to the first embodiment.
  • the GOT 30 includes a message storage unit 31, an error code acquisition unit 32, a database search unit 33, an internal search unit 34, and a display unit 35.
  • the error database 40 includes an error information storage unit 41.
  • FIG. 3 is a diagram illustrating information stored in the message storage unit 31 according to the first embodiment.
  • the message storage unit 31 is a storage device that stores an error message that the GOT 30 has.
  • the message storage unit 31 stores an error message for each error code.
  • the error code is an identifier of the error that has occurred.
  • the error message is information that simply indicates the content of the error that has occurred.
  • FIG. 4 is a diagram illustrating information stored in the error information storage unit 41 according to the first embodiment.
  • the error information storage unit 41 is a storage device that stores error messages and the like.
  • the error information storage unit 41 stores an error message and handling information for each equipment ID, language, and error code.
  • the equipment ID is an identifier of the production equipment 10.
  • the language is an identifier of a description language of the error message.
  • the error code and error message are as described above.
  • the handling information is information that can be used as a reference when dealing with an error, such as how to deal with an error that has occurred.
  • FIG. 5 is a flowchart showing processing of the error processing system 100 according to the first embodiment.
  • An error occurs in the production facility 10 (S101).
  • the PLC 20 detects an error that has occurred in the production facility 10 (S102). Since the PLC 20 is a device that controls and monitors the operation of the production facility 10, it can be easily detected if an error occurs in the production facility 10.
  • the error code acquisition unit 32 of the GOT 30 acquires an error code corresponding to the error generated from the PLC 20 (S103).
  • the error code acquisition unit 32 monitors the internal memory of the PLC 20 and can detect that the PLC 20 has detected an error. Further, the error code acquisition unit 32 can acquire an error code indicating an error detected by the PLC 20 from the PLC 20.
  • the database search unit 33 uses the equipment ID of the production equipment 10 connected via the PLC 20, the language for displaying the error message, and the error code as an error database.
  • the 40 error information storage units 41 are searched (S104). Note that the language for displaying the error message is set by the user of the GOT 30 or the like.
  • the database search unit 33 acquires an error message and handling information from the record (S105). Then, the display unit 35 displays the error message and the handling information acquired by the database search unit 33 (S107).
  • the internal search unit 34 searches the message storage unit 31 using the error code as a key and acquires an error message (S106). Then, the display unit 35 displays the error message acquired by the internal search unit 34 (S107).
  • FIG. 6 is a diagram illustrating a screen example displayed by the display unit 35.
  • the display unit 35 displays various measurement values 351 relating to the production facility 10, a switch 352 for operating the production facility 10, and the like at normal times.
  • the display unit 35 displays an error message in the message display field 353 in addition to the information displayed at the normal time.
  • FIG. 7 is a diagram illustrating an example of a maintenance screen of the error information storage unit 41.
  • a list of information stored in the error information storage unit 41 is displayed on the maintenance screen.
  • the administrator selects information that needs maintenance, corrects the information, and presses an update button to update the information.
  • the administrator presses the registration button to display a new error code addition field and adds information on the new error code.
  • Network traffic between each GOT 30 and the error database 40 may be limited to a certain level or less.
  • all data is extracted from each GOT 30 and registered in the error database 40 when shifting from the state where each GOT 30 manages error code and error message data to the unified management by the error database 40. Can not do it. Therefore, it is difficult to transfer data to the error database 40 at a time.
  • the GOT 30 outputs an error message acquired from the error database 40 regarding the error code stored in the error database 40, and regarding the error code not stored in the error database 40. The error message stored in the GOT 30 is output. Therefore, in the error processing system 100 according to the first embodiment, the data can be gradually transferred to the error database 40 and can be transferred to the centralized management while continuing to operate using the data stored in the GOT 30.
  • Trainees may come to the factory from overseas. In such a case, it is necessary to temporarily switch the display language of the error message.
  • the display language can be switched for error messages registered in the error database 40. For this reason, the error processing system 100 according to the first embodiment can easily cope with the temporary switching of the display language of error messages.
  • the input / output device of the GOT 30 is usually a touch panel, and does not have a keyboard as hardware, but has only a keyboard as software. For this reason, in the GOT 30, an operation for inputting characters such as an error message has a heavy load on the worker. After the error database 40 is introduced, it is not necessary to maintain the message storage unit 31 of the GOT 30 in principle. As a result, the load on the worker is reduced.
  • the error database 40 stores handling information along with error messages.
  • the GOT 30 displays the error message acquired from the error database 40, the GOT 30 also displays countermeasure information. By displaying the handling information, it is possible to reduce the time for handling the error generated by the operator.
  • the data can be gradually transferred to the error database 40 and the centralized management can be performed, but the items (language, countermeasure information, etc.) that are not in the message storage unit in the error information storage unit By providing, error information can be further enhanced. Also, if error messages that require items (language, countermeasure information, etc.) that are not in the message storage unit 31 are preferentially registered, useful information can be provided with little effort.
  • Embodiment 2 a method for enabling efficient maintenance of error messages will be described. In the second embodiment, the description will focus on the parts different from the first embodiment.
  • the data stored in each GOT 30 may be scrutinized and registered in the error database 40 in order.
  • priority is given to production of products, and it is a fact that the operator's hand does not easily turn in the processing related to error messages. Therefore, a mechanism for preferentially registering error messages that are really required to be registered in the error database 40 in the error database 40 is required.
  • FIG. 8 is a functional configuration diagram of the GOT 30 and the error database 40 according to the second embodiment.
  • the functional configuration of the GOT 30 is the same as that of the GOT 30 according to the first embodiment shown in FIG.
  • the error database 40 includes a history storage unit 42 and a history output unit 43 in addition to the functions of the error database 40 according to Embodiment 1 shown in FIG.
  • FIG. 9 is a diagram illustrating information stored in the history storage unit 42 according to the second embodiment.
  • the history storage unit 42 is a storage device that stores information regarding errors that have occurred as a history.
  • the history storage unit 42 stores an error code, equipment ID, occurrence date / time, recovery date / time, and worker ID.
  • the error code and equipment ID are as described above.
  • the occurrence date and time is information indicating the date and time when the error occurred.
  • the recovery date and time is information indicating the date and time when the error was resolved.
  • the worker ID is an identifier of the worker who was using the GOT 30 when an error occurred.
  • FIG. 10 is a flowchart showing processing of the error processing system 100 according to the second embodiment.
  • the processing from S201 to S204 is the same as the processing from S101 to S104 shown in FIG.
  • the history storage unit 42 of the error database 40 uses the date and time when the key is received as the generation date and time, and associates the key with the equipment ID and error code, and the worker ID of the GOT 30. (S205).
  • the worker ID is registered in the GOT 30 when the GOT 30 is used, and is transmitted together with the key transmitted to the error database 40.
  • the history of all error codes searched in S204 that is, all error codes acquired in S203
  • the history of all error codes searched in S204 regardless of whether or not there is a record corresponding to the key as a result of searching in S204.
  • the processing from S206 to S208 is the same as the processing from S105 to S107 shown in FIG.
  • the operator deals with the error, and the error is resolved. Then, the operator notifies the PLC 20 that the error has been resolved by, for example, pressing a recovery button for inputting that the error of the GOT 30 has been resolved (S209). At this time, information that the recovery button has been pressed is also transmitted to the error database 40.
  • the history storage unit 42 of the error database 40 stores the date and time when the information indicating that the recovery button was pressed is received as the recovery date and time in a record in which the corresponding equipment ID, error code, occurrence date and time, etc. are stored (S210).
  • the history output unit 43 When the history output unit 43 receives an instruction from the administrator of the error processing system 100 via the AP server 50, the history output unit 43 outputs the history stored in the history storage unit 42 to the AP server 50.
  • the administrator refers to the output history and maintains the error information storage unit 41 via the AP server 50.
  • the history output unit 43 extracts an error code that is not stored in the error information storage unit 41 from the error codes included in the history, and outputs the error code together with the equipment ID stored in the same record as the error code. .
  • the administrator can know an error code indicating an error that has actually occurred among error codes not stored in the error information storage unit 41. Since an error that has actually occurred is more likely to occur than other errors, the error code that indicates the error should be maintained with priority, for example, an error that should be registered with an appropriate error message or action information. Code.
  • the history output unit 43 calculates the recovery time required for recovery from the occurrence date and time and the recovery date and outputs the recovery time together with the equipment ID and the like.
  • the long recovery time may be due to the worker not knowing how to deal with it. Therefore, an error code indicating an error with a long recovery time is an error code that should be preferentially maintained, and for example, an appropriate error message or countermeasure information should be registered.
  • the history output unit 43 may output the history in order of the recovery time.
  • the history output unit 43 may output only information whose recovery time is equal to or longer than the reference time.
  • a history of errors that have occurred can be stored, and error messages and the like can be maintained by referring to the history. For this reason, it is possible to preferentially register an error message that is really required to be registered in the error database 40 in the error database 40.
  • an error message is registered in the error database 40, a more appropriate error message is registered and handling information is also registered. Therefore, the recovery time can be shortened by referring to the error message registered in the error database 40 and dealing with the error, rather than referring to the error message registered in the GOT 30. Therefore, by preferentially registering error messages that need to be registered in the error database 40, the recovery time can be shortened and the line operating rate can be increased.
  • the history includes the worker ID of the worker who actually handled the error. Therefore, for example, when registering an error message regarding an error code or the like having a long recovery time, the administrator may register the worker ID in the handling information. Thereby, when the same error occurs later, the worker who actually coped with the error can be identified from the worker ID, so that the coping method can be obtained from the worker who actually dealt with the error.
  • the history storage unit 42 may further store “worker's coping information” indicating the content of coping performed by the worker. For example, after the recovery button is pressed in S209, the operator's countermeasure information can be selected from the menu, and the selected result is stored in the history storage unit 42 as the worker's countermeasure information. Also good. In addition, “other” can be selected in the menu, and when other is selected, the operator's countermeasure information may be separately input from the AP server 50. When maintaining error messages and the like by referring to the history, it is possible to create more appropriate error messages and handling information by referring to the handling information of the actual worker.
  • Embodiment 3 a method for automatically registering an error message will be described.
  • the description will focus on the parts different from the second embodiment.
  • traffic may be restricted in the network between each GOT 30 and the error database 40. Therefore, it is difficult to extract all error codes and error messages from each GOT 30 via the network and register them in the error database 40.
  • priority is given to the production of products, and it is a fact that the operator's hand is not easily turned in the processing related to the error message. Therefore, a mechanism for automatically registering necessary error messages in the error database 40 while satisfying the traffic restriction is required.
  • FIG. 11 is a functional configuration diagram of the GOT 30 and the error database 40 according to the third embodiment.
  • the GOT 30 includes a message storage unit 36 in addition to the functions of the GOT 30 according to the second embodiment shown in FIG.
  • the functional configuration of the error database 40 is the same as that of the error database 40 according to Embodiment 2 shown in FIG.
  • FIG. 12 is a flowchart showing processing of the error processing system 100 according to the third embodiment.
  • the processes from S301 to S307 and S309 to S311 are the same as the processes from S201 to S210 shown in FIG.
  • the message storage unit 36 stores the acquired error message in the error information storage unit 41 of the error database 40 (S308). At this time, the message storage unit 36 stores an error message in association with the error code or the like used as a key in S304.
  • the error processing system 100 when an error code and an error message of an actually generated error are not stored in the error database 40, the error code and the error message are stored in the error database. 40.
  • an error that has actually occurred is considered to be more likely to occur than other errors. For this reason, it is effective to preferentially register an error code or the like of an error that has actually occurred in the error database 40.
  • the error processing system 100 when an error actually occurs, the error code and the error message are stored in the error database 40. Therefore, it is possible to avoid the concentration of traffic at a time and to satisfy the traffic restriction.
  • FIG. 13 is a diagram illustrating an example of the hardware configuration of the GOT 30, the error database 40, and the AP server 50 described in the first and second embodiments.
  • Each device of the GOT 30, the error database 40, and the AP server 50 is a computer.
  • Each element of each device can be realized by a program.
  • an arithmetic device 901, an external storage device 902, a main storage device 903, a communication device 904, and an input / output device 905 are connected to the bus.
  • the computing device 901 is a CPU (Central Processing Unit) that executes a program.
  • the external storage device 902 is, for example, a ROM (Read Only Memory), a flash memory, a hard disk device, or the like.
  • the main storage device 903 is, for example, a RAM (Random Access Memory).
  • the communication device 904 is, for example, a communication board.
  • the input / output device 905 is, for example, a mouse, a keyboard, a display device, or the like.
  • the program is normally stored in the external storage device 902, and is loaded into the main storage device 903 and sequentially read into the arithmetic device 901 and executed.
  • the program is a program that realizes the functions described as the error code acquisition unit 32, the database search unit 33, the internal search unit 34, the display unit 35, and the history output unit 43.
  • an operating system (OS) is also stored in the external storage device 902. At least a part of the OS is loaded into the main storage device 903, and the arithmetic device 901 executes the above program while executing the OS.
  • OS operating system
  • the information described as being stored by the message storage unit 31, the error information storage unit 41, and the history storage unit 42 is stored in the main storage device 903 as a file.
  • FIG. 13 is merely an example of the hardware configuration of each device, and the hardware configuration of each device is not limited to the configuration described in FIG. 13 and may be other configurations.
  • 10 production facilities 20 PLC, 30 GOT, 31 message storage unit, 32 error code acquisition unit, 33 database search unit, 34 internal search unit, 35 display unit, 40 error database, 41 error information storage unit, 42 history storage unit, 43 History output unit, 50 AP server, 100 error handling system.

Landscapes

  • Engineering & Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • General Factory Administration (AREA)
  • Testing And Monitoring For Control Systems (AREA)
  • Programmable Controllers (AREA)

Abstract

　Le but de la présente invention est de rendre possible, lorsqu'un code d'erreur est géré individuellement dans des GOT individuels, le fait de permettre à la gestion de code d'erreur d'être décalée en douceur vers une gestion unifiée par un serveur, etc, en prenant en compte des circonstances inhérentes dans des systèmes FA. Le GOT (30), après acquisition d'un code d'erreur pour une erreur se produisant dans une installation de production, effectue une recherche dans une base de données d'erreurs (40) à l'aide du code d'erreur en tant que clé. Lorsqu'il n'est pas possible d'acquérir un message, le GOT (30) recherche dans une mémoire interne à l'aide du code d'erreur en tant que clé. Le GOT (30) affiche le message acquis.
PCT/JP2014/057973 2014-03-24 2014-03-24 Système de traitement d'erreur WO2015145523A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2014525220A JP5808861B1 (ja) 2014-03-24 2014-03-24 エラー処理システム
CN201480001056.7A CN105122163B (zh) 2014-03-24 2014-03-24 错误处理系统
PCT/JP2014/057973 WO2015145523A1 (fr) 2014-03-24 2014-03-24 Système de traitement d'erreur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2014/057973 WO2015145523A1 (fr) 2014-03-24 2014-03-24 Système de traitement d'erreur

Publications (1)

Publication Number Publication Date
WO2015145523A1 true WO2015145523A1 (fr) 2015-10-01

Family

ID=54194125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/057973 WO2015145523A1 (fr) 2014-03-24 2014-03-24 Système de traitement d'erreur

Country Status (3)

Country Link
JP (1) JP5808861B1 (fr)
CN (1) CN105122163B (fr)
WO (1) WO2015145523A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017167708A (ja) * 2016-03-15 2017-09-21 三菱電機株式会社 保全システムおよび保全方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109445406B (zh) * 2018-10-18 2021-05-18 西南交通大学 基于场景测试与事务搜索的工业控制系统安全检测方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002091913A (ja) * 2000-09-12 2002-03-29 Techno Digital:Kk 遠隔メンテナンスシステム、並びにこれに用いられるメンテナンス装置およびサポート装置
JP2004054341A (ja) * 2002-07-16 2004-02-19 Sharp Corp 生産装置管理システム、生産装置管理方法
JP2008310402A (ja) * 2007-06-12 2008-12-25 Nikon Corp 作業情報管理システム

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4082306B2 (ja) * 2003-08-08 2008-04-30 三菱ふそうトラック・バス株式会社 故障診断装置
JP4509602B2 (ja) * 2004-02-27 2010-07-21 富士重工業株式会社 オペレータ側システムおよびモードファイルの特定方法
CN101840233B (zh) * 2010-04-29 2011-09-21 深圳市共济科技有限公司 一种设备故障检测装置及设备故障检测方法
CN102508488A (zh) * 2011-11-22 2012-06-20 中联重科股份有限公司 在线故障检修系统及方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002091913A (ja) * 2000-09-12 2002-03-29 Techno Digital:Kk 遠隔メンテナンスシステム、並びにこれに用いられるメンテナンス装置およびサポート装置
JP2004054341A (ja) * 2002-07-16 2004-02-19 Sharp Corp 生産装置管理システム、生産装置管理方法
JP2008310402A (ja) * 2007-06-12 2008-12-25 Nikon Corp 作業情報管理システム

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017167708A (ja) * 2016-03-15 2017-09-21 三菱電機株式会社 保全システムおよび保全方法

Also Published As

Publication number Publication date
CN105122163A (zh) 2015-12-02
CN105122163B (zh) 2017-06-30
JPWO2015145523A1 (ja) 2017-04-13
JP5808861B1 (ja) 2015-11-10

Similar Documents

Publication Publication Date Title
US8667078B2 (en) Systems and methods of extracting, storing, and serving device definition file information
JP4820265B2 (ja) エンジニアリング装置
JP5808861B1 (ja) エラー処理システム
JP6837017B2 (ja) 作業手順提示装置及び作業手順提示方法、並びに、自動制御装置及び自動制御方法
WO2014136228A1 (fr) Dispositif de commande programmable, système de dispositif de commande programmable et procédé de création d'informations d'erreur d'exécution
JP5207310B2 (ja) プラント監視制御システム用の制御装置
JP2017010155A (ja) 施設監視装置および施設監視方法
CN108958210B (zh) 工厂监视控制系统的维护计算机及电脑可读取记录介质
KR101653925B1 (ko) 엔지니어링 장치, 엔지니어링 시스템 및 다운로드 처리 방법
JP2008287396A (ja) データ処理装置およびプログラム
JP6060123B2 (ja) 影響範囲特定装置、影響範囲特定方法、及びプログラム
US10054996B2 (en) Power system monitoring and control system having thread-dependent calculation monitoring function
JP5743826B2 (ja) 構成情報管理プログラム及び構成情報管理方法
JP6027410B2 (ja) プラント監視制御システム、およびプラント監視制御方法
US20150277858A1 (en) Performance evaluation device, method, and medium for information system
EP3046061B1 (fr) Procédé d'obtention d'au moins un paramètre de fonctionnement d'un composant de sous-station électrique
JP2011107992A (ja) ジョブスケジュール変更管理システム
JP5799005B2 (ja) 設備保全管理システム
JP5916647B2 (ja) 保守装置
JP6444287B2 (ja) Ｗｅｂプラント監視制御システムおよびＷｅｂ端末
JP2015090550A (ja) データ移行方法及び装置
JP2016076133A (ja) 初動対応支援システムおよび初動対応支援方法ならびに初動対応支援プログラム
JP2006004107A (ja) Ｃａｄ変更管理システムとその方法およびプログラム
JP2018055146A (ja) プラント保守監視システム
JP2016157376A (ja) 広域監視制御システム

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2014525220

Country of ref document: JP

Kind code of ref document: A

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

Ref document number: 14886863

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: 14886863

Country of ref document: EP

Kind code of ref document: A1