WO2018181705A1 - プラント監視システム、プラント運転支援システム、プラント監視方法、及びプログラム - Google Patents

プラント監視システム、プラント運転支援システム、プラント監視方法、及びプログラム Download PDF

Info

Publication number
WO2018181705A1
WO2018181705A1 PCT/JP2018/013226 JP2018013226W WO2018181705A1 WO 2018181705 A1 WO2018181705 A1 WO 2018181705A1 JP 2018013226 W JP2018013226 W JP 2018013226W WO 2018181705 A1 WO2018181705 A1 WO 2018181705A1
Authority
WO
WIPO (PCT)
Prior art keywords
program
plant
execution
unit
execution request
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/JP2018/013226
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
健司 ▲高▼尾
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitsubishi Heavy Industries Ltd
Original Assignee
Mitsubishi Heavy Industries Ltd
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 Mitsubishi Heavy Industries Ltd filed Critical Mitsubishi Heavy Industries Ltd
Priority to US16/494,456 priority Critical patent/US11262732B2/en
Publication of WO2018181705A1 publication Critical patent/WO2018181705A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/4183—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by data acquisition, e.g. workpiece identification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • 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
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/042—Programme control other than numerical control, i.e. in sequence controllers or logic controllers using digital processors
    • G05B19/0428—Safety, monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
    • H04L9/0643—Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
    • H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
    • H04L9/0819—Key transport or distribution, i.e. key establishment techniques where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s)
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the present invention relates to a plant monitoring system, a plant operation support system, a plant monitoring method, and a program.
  • supply a plant equipment supplier
  • user a plant equipment user
  • various countermeasures are taken. Will be taken. Even when trouble or the like does not occur, when information is newly acquired, various information may be shared between the supplier and the user.
  • Patent Document 1 discloses a technique for automatically executing a program.
  • the present invention has been made in view of the above problems, and an object of the present invention is to provide a plant monitoring system or the like that monitors a plant using a program that is guaranteed not to be tampered with.
  • the plant monitoring system of the present invention is a plant monitoring system for monitoring a plant, and a program for transmitting at least a part of a plant state monitoring information group to a predetermined information processing device is distributed and recorded in advance in a plurality of recording devices.
  • the distributed recording unit the determination unit that sequentially acquires the state monitoring information, the determination unit that determines whether the acquired state monitoring information satisfies a predetermined program execution condition, and the program execution condition is satisfied
  • An execution request output unit that outputs the execution request of the program corresponding to the program execution condition to the distributed recording unit, and the distributed recording unit is configured to output the execution request when the execution request is output.
  • the program execution processing unit reads and executes the program specified by the execution request.
  • the plant operation support system of the present invention is a plant operation support system for supporting operation of a plant, and a distributed record in which a program for outputting operation support information related to a plant is distributed and recorded in a plurality of recording devices in advance. And an execution request output unit that outputs the execution request to the distributed recording unit when an execution request for the program is received, wherein the distributed recording unit is designated by the execution request.
  • an agreement determination processing unit that determines whether a predetermined agreement condition defined with a provider of the program is satisfied, and when the agreement condition is satisfied, When the program is executed according to the execution request and a program execution processing unit that executes the designated program, the program is And having a an execution history recording unit for the execution history information distributed recording indicating that the rows.
  • the program execution processing unit executes each of the plurality of distributedly recorded programs, compares the operation values obtained by the execution of each program, and the comparison result It is determined whether to output the calculation value according to the above.
  • the distributed recording unit includes an approval unit that outputs an approval result of the received execution request to each of the distributed recording units, and the agreement determination unit includes the approval unit. It is characterized in that it is determined whether or not a predetermined agreement condition is satisfied based on the approval result output by.
  • the plant operation support system of the present invention is characterized in that currency substitution information that increases or decreases with the execution of the program is recorded in the distributed recording unit.
  • the predetermined agreement condition includes a condition whether or not predetermined information is shared at a time after a predetermined period from when the execution request is made. It is characterized by.
  • the program recorded in the distributed recording unit is encrypted, and when the agreement condition is satisfied, each distributed recording from the provider of the program is performed.
  • an encryption key output unit for outputting a key for decryption.
  • the plant monitoring method of the present invention includes a distributed recording step for previously distributing and recording a program for transmitting at least a part of a state monitoring information group of a plant to a predetermined information processing apparatus in a plurality of recording devices, and the state monitoring information Are sequentially acquired, and a determination step for determining whether or not the acquired state monitoring information satisfies a predetermined program execution condition, and when the program execution condition is satisfied, the program execution condition corresponds to the program execution condition.
  • the program of the present invention records a program for transmitting at least a part of a plant state monitoring information group to a predetermined information processing device in a plurality of recording devices in advance in a distributed manner by a computer of a plant monitoring system that monitors the plant.
  • a distributed recording unit a determination unit that sequentially acquires the state monitoring information, a determination unit that determines whether the acquired state monitoring information satisfies a predetermined program execution condition, and a case where the program execution condition is satisfied
  • the execution request output means for outputting the execution request of the program corresponding to the program execution condition to the distributed recording unit, and the program specified in the execution request when the execution request is output. It functions as a program execution processing means for reading and executing.
  • a plant can be monitored using a program that is guaranteed not to be tampered with.
  • FIG. 1 is a diagram showing a plant monitoring system according to a first embodiment of the present invention.
  • FIG. 2 is a diagram illustrating a part of the plant monitoring system according to the first embodiment of this invention.
  • FIG. 3 is a diagram showing a part of the plant monitoring system according to the first embodiment of the present invention.
  • FIG. 4 is a flowchart of the plant monitoring method according to the first embodiment of the present invention.
  • FIG. 5 is a flowchart of the plant monitoring method according to the first embodiment of the present invention.
  • FIG. 6 is a diagram showing a plant operation support system according to the second embodiment of the present invention.
  • FIG. 7 is a diagram showing a part of the plant operation support system according to the second embodiment of the present invention.
  • FIG. 1 is a diagram showing a plant monitoring system according to a first embodiment of the present invention.
  • FIG. 2 is a diagram illustrating a part of the plant monitoring system according to the first embodiment of this invention.
  • FIG. 3 is a diagram showing a part
  • FIG. 8 is a flowchart of the plant operation support method according to the second embodiment of the present invention.
  • FIG. 9 is a flowchart of the plant operation support method according to the second embodiment of the present invention.
  • FIG. 10 is a diagram showing a plant operation support system according to the third embodiment of the present invention.
  • FIG. 11 is a diagram showing a part of the plant operation support system according to the third embodiment of the present invention.
  • FIG. 12 is a flowchart of the plant operation support method according to the third embodiment of the present invention.
  • the plant monitoring system 1 of this embodiment includes a distributed recording unit 3, a determination unit 4, an execution request output unit 5, and an information processing device 6 provided in the arithmetic device 2. ing.
  • the distributed recording unit 3 is provided in each of the plurality of arithmetic devices 2, and one storage system is configured with each of the plurality of distributed recording units 3 as a node.
  • the distributed recording unit 3 is recorded in each of the plant provider's computing device 2a and the plant user's computing device 2b.
  • the computing device 2 includes an input device that receives input from a user (not shown) and a display device that displays various information.
  • the arithmetic device 2 is an example of a recording device.
  • the distributed recording unit 3 includes a database 7, a program execution processing unit 8, an approval unit 9, an agreement determination unit 10, and a recording request unit 11.
  • FIG. 3 shows a state in which five blocks are connected in a chain shape.
  • the state monitoring information includes, for example, sensor observation values such as pipe temperature, pressure, and valve opening.
  • Each block does not have to be a block that contains only meaningful information. For example, an execution result executed by a certain program and another program may be stored in the same block.
  • each block also includes the hash value of the block registered in the database 7 immediately before.
  • a hash value is a non-regular value obtained from the original data by a certain calculation procedure. The same hash value is always obtained from the same data, but a different hash value is always obtained from different data. There is a characteristic.
  • the program execution processing unit 8 is a functional unit that reads and executes the program specified by the execution request output by the execution request output unit 5. Since the execution request output unit 5 specifies a specific program by the program ID and issues an execution request, the program execution processing unit 8 uses the program ID to specify the address of the block on the database 7 in which the program is recorded. A value is acquired, and a program is read from the database 7 and executed based on the address value. Details will be described later.
  • the approval unit 9 determines whether or not the execution request output by the execution request output unit 5 or the recording request output by the recording request unit 11 satisfies a desired requirement, and the approval result is assigned to each distributed recording unit.
  • 3 is a functional unit that outputs the data. This desired condition may be changed depending on the content of the execution request, or may be a condition that an input by the user is accepted.
  • the agreement determination unit 10 is a functional unit that determines whether a predetermined agreement condition set in advance is satisfied.
  • the agreement condition for example, whether or not the number of approval results to be approved output from the approval unit 9 has reached a predetermined ratio of the total number of the computing devices 2, more specifically, two-thirds or more. It is also possible to make a condition such as whether or not the number is reached.
  • the recording request unit 11 is a functional unit that outputs a recording request with the content of recording specific information in the database 7 to each distributed recording unit 3.
  • the determination unit 4 includes a sensor that sequentially acquires state monitoring information, and is a functional unit that determines whether the acquired state monitoring information satisfies a predetermined program execution condition.
  • This program execution condition is a condition determined in advance by agreement between the plant provider and the plant user.
  • the execution request output unit 5 is a functional unit that outputs a program execution request to each distributed recording unit 3 when the program execution condition is satisfied.
  • the determination unit 4 and the execution request output unit 5 are provided on the user side of the plant, they are not necessarily limited to such an aspect.
  • the information processing device 6 is a device that receives state monitoring information transmitted to the plant provider side by a program executed by the program execution processing unit 8.
  • the information processing device 6 and the calculation device 2 are described separately.
  • the calculation device 2a on the plant provider side may also serve as the information processing device 6.
  • Step S1 First, as shown in FIG. 4, in the plant monitoring method of the present embodiment, a program and a program execution condition corresponding to the program are agreed in advance between the plant provider and the plant user, and the program is created.
  • the program referred to here has a content of transmitting a plant state monitoring information group to the information processing device 6 on the plant provider side.
  • the program is such that the pipe temperature is transmitted to the plant provider.
  • a condition that the pipe temperature is equal to or higher than a predetermined temperature is agreed in advance as a program execution condition.
  • Step S2 Next, by the operation of the program provider, the recording request unit 11 outputs a recording request for recording the program to each distributed recording unit 3.
  • Step S3 After waiting for an input from the operator of the arithmetic device 2, the approval unit 9 indicates the approval result as to whether or not the recording request output by the recording request unit 11 satisfies a desired requirement for each distributed recording unit 3. Output to.
  • Step S4 it is determined whether or not the number of outputs indicating that the agreement determination unit approves the recording request output from each approval unit 9 in step S3 has reached two-thirds or more of all the arithmetic devices 2. judge. Note that the ratio of two-thirds is merely an example, and other ratios may be used. For example, a majority approval may be used. If it does not reach more than two thirds, the program is not stored in the database and the process ends.
  • Step S5 As a result of the determination in step S4, when the number reaches two-thirds or more of all the arithmetic devices 2, the program is recorded as a block in the database 7 of each distributed recording unit 3. In addition to this program, this block includes at least the hash value of the immediately preceding block, and may include various other information.
  • the address value of the block in which the program is registered (value indicating the position on the database 7) is also acquired. Then, an address value is separately stored in the database 7 in association with a program ID for identifying the program.
  • the program when the program is stored in the database 7 or when the program is updated, the consent of two-thirds or more of all the arithmetic devices 2 is required.
  • the computing device 2 is a plant provider and a plant user, each holding half of the number, requesting consent of more than two-thirds, either registering the program alone , You will not be able to update.
  • the numerical value of 2/3 is an example, Comprising: It can change into a desired value suitably. Thereby, both the plant provider and the user of the plant can prevent the automatic execution program that is not recognized by itself from being saved.
  • the database 7 stores two types of programs: an old program before update and a new program after update. Therefore, at the stage of program execution, the program is identified and executed based on the address value of the block where the new program after update is saved, not the address value of the block where the old program before update is saved. Will be.
  • Step S11 a method for monitoring the program execution stage will be described.
  • the determination unit 4 determines whether or not a predetermined program execution condition is satisfied. This determination is performed based on the value of the temperature sensor provided in the determination unit 4, for example. In addition, it is preferable that this determination is performed automatically by constantly monitoring with a sensor provided in the determination unit 4 so that no human intervention is required. If the program execution conditions are not met, repeat this step.
  • Step S12 Next, as a result of the determination in step S ⁇ b> 11, when the program execution condition is satisfied, the execution request output unit 5 outputs a program execution request to each distributed recording unit 3.
  • the program execution request output unit 5 specifies a program ID and specifies the program to make a program execution request.
  • the approval unit 9 determines whether to approve the program execution request output from the execution request output unit 5 and outputs an approval result. In this case, it is preferable that no human intervention is required, and it is conceivable that the determination condition is, for example, whether or not a program execution request is issued from the execution request output unit 5.
  • Step S14 Next, whether the number of outputs indicating that the agreement determination unit 10 approves the execution request of the program output from each approval unit 9 in step S13 has reached the number of two-thirds or more of all the computing devices 2 Determine whether or not.
  • the numerical value of 2/3 is an example, Comprising: It can change into a desired value suitably. If it has not reached more than two-thirds, the program is not executed and the process ends.
  • Step S15 As a result of the determination in step S14, when the number of all the arithmetic devices 2 is more than two-thirds, the program execution processing unit 8 is designated by the program execution request output by the execution request output unit 5. Read and execute the program. Specifically, since the program ID and the address value are recorded in the database 7 in association with each program stored in the database 7, the program execution processing unit 8 outputs the program request by the execution request output unit 5. The address value of the program is acquired based on the program ID. Then, the program execution processing unit 8 identifies a block in which the program is recorded based on the address value, reads the program, and executes it.
  • Step S16 the state monitoring information is transmitted to the information processing apparatus 6 by the program executed by the program execution processing unit 8.
  • the pipe temperature is transmitted to the information processing device 6.
  • each program execution processing unit 8 outputs the execution result of the program to the other distributed recording unit 2.
  • each program execution processing unit 8 determines whether or not the execution results received in step S17 are all equal.
  • Step S19 As a result of the determination in step S18, if there is a different execution result among the execution results received from the other distributed recording units 2, the program execution processing unit 8 indicates that there is an execution error for each distributed type. Output to the recording unit 2. In this case, as long as even one different execution result exists, execution of the program in the program execution processing units 8 of all the distributed recording units 2 is stopped and terminated. In place of step S18 and this step, if there is an execution result that matches at a predetermined ratio or more among the execution results received in step S17, the execution result is trusted and the next step S20 is performed. You may control to advance to. Examples of the predetermined ratio include two-thirds.
  • Step S20 If all the execution results are equal as a result of the determination in step S18, the recording request unit 11 outputs a recording request to each distributed recording unit 2 so that the execution result is recorded in the database 7.
  • the approval unit 9 outputs an approval result as to whether or not the recording request output by the recording request unit 11 satisfies a desired requirement to each distributed recording unit 3.
  • a desired requirement for example, it can be considered to be a formal requirement such as confirming whether or not it is a recording request from the recording request unit 11.
  • Step S22 Next, whether or not the number of outputs indicating that the agreement determination unit 10 approves the recording request output from each approval unit 9 in step S ⁇ b> 21 has reached the number of two-thirds or more of all the computing devices 2. Determine. If it does not reach more than two-thirds, the execution result is not stored in the database 7 and the process ends.
  • the numerical value of 2/3 is an example, Comprising: It can change into a desired value suitably.
  • Step S23 As a result of the determination in step S22, when the number reaches two-thirds or more of all the arithmetic devices 2, the execution result is recorded as a block in the database 7 of each distributed recording unit 3, and the process ends.
  • the determination unit 4 determines whether or not a predetermined program execution condition is satisfied, and then executes the program smoothly without human judgment until the program is executed. Can do. As a result, when trouble occurs in the past, it is possible to omit the time required for discussions between the plant provider and the plant user and not only to reduce costs but also to troubleshoot promptly. This can be eliminated, and the system down time of the plant can be shortened.
  • the plant operation system of the present embodiment is different from the distributed monitoring unit 23, the execution request output unit 24, the communication monitoring unit 25, and the encryption provided in the arithmetic unit 22.
  • the key notification unit 26 is configured.
  • the distributed recording unit 23 includes a database 27, a program execution processing unit 28, an approval unit 29, an agreement determination unit 30, and an execution history processing unit 31. Since the approval unit 29 and the agreement determination unit 30 are the same as those in the first embodiment, description thereof is omitted.
  • the database 27 stores data for each block, and the blocks are connected in a chain. Various types of information can be recorded in the block of this embodiment, but at least for data, the data itself is not stored, but the hash value of the data is stored.
  • the database 27 of the present embodiment also stores a program for outputting operation support information related to the plant.
  • Examples of the driving support information include information related to power demand prediction, driving analysis, failure diagnosis, and the like.
  • the program for outputting the operation support information related to the plant includes a full service program that can output operation support information that is sufficiently useful for the user and a limited service program that can output only limited operation support information. Yes.
  • Examples of the full service program include a program that outputs a failure diagnosis result, and examples of the limited service program include a program that simply outputs an average value of data, a variance value, and the like.
  • the program stored in the database 27 is encrypted by the program provider.
  • the execution request output unit 24 includes an input unit 32 that receives input from an operator who is a plant user.
  • the execution request output unit 32 is a functional unit that outputs an execution request to the distributed recording unit 23 when an execution request for executing a program for outputting operation support information related to a plant from an operator is received. But there is.
  • the communication monitoring unit 25 is a functional unit that monitors whether the distributed recording unit 23 provided in each arithmetic device 22 can communicate with other distributed recording units 23.
  • Step S31 a plant operation support method using the plant operation support system 21 of the present embodiment will be described.
  • the user of the plant operates the input unit 32 to request the execution request output unit to execute a desired program.
  • the execution request output unit 24 outputs the execution request to the distributed recording unit 23.
  • Step S32 Next, it is determined whether or not the program requested by the execution request output unit 24 in step S1 is a full service program.
  • Step S33 If it is determined in step S32 that the program is not a full service program but a limited service program, the program execution processing unit 28 executes the program in accordance with the execution request made in step S31 and ends the process.
  • Step S34 If the result of determination in step S32 is a full service program, it is next determined by the communication monitoring unit 25 whether or not the plant provider and the plant user are in a communicable state. If the communication is possible, the process proceeds to step S35. If the communication is impossible, the process is terminated and the full service program is not executed.
  • Step S35 the agreement determination processing unit 30 determines whether or not a predetermined agreement condition is satisfied for executing the program.
  • This predetermined agreement condition is a condition determined in advance between the plant provider and the plant user. For example, a condition such as whether or not the plant provider has approved, a condition such as whether or not a fee has been paid, and a condition such as whether or not owned plant information is provided can be considered.
  • the plant provider In order to determine whether or not the plant provider has approved, for example, it may be determined based on the number of outputs of the approval result by the approval unit 29 for the execution request output by the execution request output unit 24. If the number of computing devices 22a on the plant provider side and the number of computing devices 22b on the user side of the plant are the same, the approval result by the approval unit 29 reaches more than two-thirds of all the computing devices 22. In other words, at least if someone on the plant provider side does not approve, the predetermined agreement condition is not satisfied.
  • a method of recording and processing virtual currency (currency alternative information) in the database 27 can be considered.
  • the user of the plant purchases the virtual currency by actually paying a fee to the plant provider (step S41). Then, in order to record the virtual currency in the database 27, the approval of the plant provider is required, and the approval of the plant provider is obtained and registered in the database 27 (step S42). Then, as a predetermined agreement condition for the execution request of the program, it is determined on the condition that the user of the plant holds the virtual currency in the database 27 (step S43). Then, when actually executing the program, the virtual currency recorded automatically is decreased (step S44). By doing in this way, it can be discriminate
  • the owned plant information it may be determined whether or not the data is stored in the database 27. Specifically, it is conceivable to determine whether or not the data has been saved at a time after a certain period before the execution request is made by the execution request output unit 24.
  • Step S36 As a result of step S35, when predetermined agreement conditions are satisfied, the encryption key notification unit 26 notifies each distributed recording unit 23 of the encryption key. In addition, as a result of step S35, when the predetermined agreement condition is not satisfied, the process is terminated.
  • Step S37 when receiving the notification of the encryption key, the program execution processing unit 28 executes the full service program according to the execution request.
  • Step S38 the execution history processing unit 31 records execution history information indicating that the program has been executed in the database 27 and ends the processing.
  • execution history information for example, a hash value of an execution result of executing a program can be cited.
  • execution history information is recorded in the database 27 of the distributed recording unit 23, so that the plant provider ensures that the plant user has executed the program. It is possible to know automatically, and management costs can be reduced.
  • the communication monitoring unit 25 monitors the communication state between the plant user and the plant provider, it is possible to prevent the full service program from being executed without the permission of the plant provider.
  • the limited service program can be executed even when the communication state is interrupted due to circumstances on the plant provider side, dissatisfaction with the plant user can be reduced.
  • the program recorded in the database 27 is encrypted, and the encryption key is notified only when a predetermined agreement condition is reached for the execution of the program, so that the contents of the program can be managed as secret.
  • the execution result is separately recorded in the database, and a hash value is obtained for the execution result periodically recorded in the database, and this value and the hash value stored in the database 27 are obtained. If there is a defect, you may be notified.
  • the present embodiment is characterized mainly in that it is automatically determined whether or not the plant operation status and the maintenance status by the plant user are appropriate.
  • the plant operation system 41 of the present embodiment is provided on the user side of the plant, the distributed recording unit 43 provided in the computing device 42, the hash value comparison unit 44, the database 45 provided on the plant providing side.
  • a database 46 and a hash value information output unit 47 are provided.
  • the distributed recording unit 43 includes a database 48 and a hash value information recording unit 49. Various kinds of information are recorded in the database 48. In this embodiment, hash values of plant operation information and maintenance information are mainly recorded.
  • the hash value information recording unit 49 is a functional unit that stores the hash value received from the hash value information output unit 47 in the database 48.
  • the database 45 and the database 46 are configured to have the same contents by synchronizing them periodically.
  • the database 45 and the database 46 store plant operation information and maintenance information itself.
  • the operation information is information relating to plant operating conditions and the like
  • the maintenance information is information relating to maintenance frequency and method.
  • the hash value comparison unit 44 calculates the hash value of the operation information and maintenance information stored in the database 45 and the database 46, compares the hash value with the hash value stored in the database 48, and the comparison results in a mismatch And a function unit for outputting an alert signal.
  • the hash value information output unit 47 is a functional unit that outputs the hash values of operation information and maintenance information to the distributed recording unit 43.
  • Step S41 the plant operation method of this embodiment is demonstrated.
  • this embodiment first, as shown in FIG. 12, each time a user of the plant operates the plant and every time the plant is maintained, these pieces of information are acquired, and the operation information and maintenance information of the plant are stored in the database 46. Record.
  • Step S42 the hash value information output unit 47 calculates the hash value of the operation information and maintenance information, and outputs this hash value to the distributed recording unit 43.
  • Step S43 the hash value information recording unit 49 records the hash value received in step S42 in the database 48 of the distributed recording unit 43.
  • Step S44 Next, the database 46 and the database 45 are synchronized so that the contents of the database 45 and the database 46 are the same.
  • Step S45 the hash value comparison unit 44 calculates a hash value of the operation information and maintenance information recorded in the database 45 and the database 46, and compares this value with the hash value stored in the database 48.
  • Step S46 As a result of step S45, if the two match, the process ends. If they do not match, the hash value comparison unit 44 outputs alert information indicating that there is a mismatch to the distributed recording unit 43, and ends the process.
  • operation information and maintenance information are recorded in the database 48 as hash values, so that these information can be prevented from being tampered with.
  • the plant provider side can immediately determine whether there is a problem in operation or maintenance, and the plant provider side determines acceptance of the complaint. Time can be shortened.
  • Each process in the plant monitoring system 1 and the plant operation support systems 21 and 41 is stored in a computer-readable recording medium in the form of a program, and the computer reads and executes the program.
  • the computer-readable recording medium means a magnetic disk, a magneto-optical disk, a CD-ROM, a DVD-ROM, a semiconductor memory, or the like.
  • the computer program may be distributed to the computer via a communication line, and the computer that has received the distribution may execute the program.
  • the program may be for realizing a part of the functions described above. Furthermore, what can implement
  • the present invention is applicable to all plant monitoring systems and all plant operation support systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • General Engineering & Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Power Engineering (AREA)
  • Testing And Monitoring For Control Systems (AREA)
PCT/JP2018/013226 2017-03-31 2018-03-29 プラント監視システム、プラント運転支援システム、プラント監視方法、及びプログラム Ceased WO2018181705A1 (ja)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/494,456 US11262732B2 (en) 2017-03-31 2018-03-29 Plant monitoring system, plant operation assistance system, plant monitoring method, and program

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2017071157A JP6846973B2 (ja) 2017-03-31 2017-03-31 プラント監視システム、プラント運転支援システム、プラント監視方法、及びプログラム
JP2017-071157 2017-03-31

Publications (1)

Publication Number Publication Date
WO2018181705A1 true WO2018181705A1 (ja) 2018-10-04

Family

ID=63676093

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2018/013226 Ceased WO2018181705A1 (ja) 2017-03-31 2018-03-29 プラント監視システム、プラント運転支援システム、プラント監視方法、及びプログラム

Country Status (3)

Country Link
US (1) US11262732B2 (enExample)
JP (1) JP6846973B2 (enExample)
WO (1) WO2018181705A1 (enExample)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3543940A1 (de) 2018-03-23 2019-09-25 Siemens Aktiengesellschaft Computerimplementiertes verfahren zum bereitstellen von daten, insbesondere für eine konformitätsverfolgung
US11405180B2 (en) * 2019-01-15 2022-08-02 Fisher-Rosemount Systems, Inc. Blockchain-based automation architecture cybersecurity
US11960473B2 (en) * 2019-01-15 2024-04-16 Fisher-Rosemount Systems, Inc. Distributed ledgers in process control systems
US10962965B2 (en) 2019-01-15 2021-03-30 Fisher-Rosemount Systems, Inc. Maintaining quality control, regulatory, and parameter measurement data using distributed ledgers in process control systems

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH1098778A (ja) * 1996-07-30 1998-04-14 Mitsubishi Electric Corp ビル管理装置
JPH10161707A (ja) * 1996-11-29 1998-06-19 Sukiyan Technol:Kk Ｆａシステムの制御方法
JPH11231932A (ja) * 1998-02-17 1999-08-27 Toshiba Corp 入出力管理装置
JP2002202811A (ja) * 2000-12-28 2002-07-19 Yamatake Building Systems Co Ltd 設備データモニタリング方法及び装置
JP2003337853A (ja) * 2002-05-22 2003-11-28 Daikin Ind Ltd 設備機器管理システム、設備機器運用装置およびシステム管理装置
JP2004021658A (ja) * 2002-06-18 2004-01-22 Nec Corp プログラム自動実行システム
JP2007241513A (ja) * 2006-03-07 2007-09-20 Japan Lucida Co Ltd 機器監視装置
JP2008176403A (ja) * 2007-01-16 2008-07-31 Toshiba Corp 遠隔監視・診断システム

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000029849A (ja) * 1998-07-15 2000-01-28 Hitachi Ltd 分散制御システム、及び分散制御システムにおけるフィルタリング方法
US6822945B2 (en) * 2000-11-08 2004-11-23 Genesys Telecommunications Laboratories, Inc. Method and apparatus for anticipating and planning communication-center resources based on evaluation of events waiting in a communication center master queue
TW573266B (en) * 2002-01-11 2004-01-21 Univ Nat Cheng Kung Universal service management system
US7899877B2 (en) * 2005-05-17 2011-03-01 Dell Products L.P. Method for dynamically managing multicast sessions for software downloads and related systems
US8332807B2 (en) * 2007-08-10 2012-12-11 International Business Machines Corporation Waste determinants identification and elimination process model within a software factory operating environment
JP2013011200A (ja) 2011-06-28 2013-01-17 Mitsubishi Heavy Ind Ltd 運転監視システム、運転監視方法、及びプログラム
JP5998577B2 (ja) 2012-03-29 2016-09-28 日本電気株式会社 クラスタ監視装置、クラスタ監視方法、及びプログラム
DE102015114215A1 (de) * 2015-08-27 2017-03-02 Rwe Ag Versorgungssystem und verfahren zum betreiben eines versorgungssystems

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH1098778A (ja) * 1996-07-30 1998-04-14 Mitsubishi Electric Corp ビル管理装置
JPH10161707A (ja) * 1996-11-29 1998-06-19 Sukiyan Technol:Kk Ｆａシステムの制御方法
JPH11231932A (ja) * 1998-02-17 1999-08-27 Toshiba Corp 入出力管理装置
JP2002202811A (ja) * 2000-12-28 2002-07-19 Yamatake Building Systems Co Ltd 設備データモニタリング方法及び装置
JP2003337853A (ja) * 2002-05-22 2003-11-28 Daikin Ind Ltd 設備機器管理システム、設備機器運用装置およびシステム管理装置
JP2004021658A (ja) * 2002-06-18 2004-01-22 Nec Corp プログラム自動実行システム
JP2007241513A (ja) * 2006-03-07 2007-09-20 Japan Lucida Co Ltd 機器監視装置
JP2008176403A (ja) * 2007-01-16 2008-07-31 Toshiba Corp 遠隔監視・診断システム

Also Published As

Publication number Publication date
US11262732B2 (en) 2022-03-01
JP6846973B2 (ja) 2021-03-24
JP2018173794A (ja) 2018-11-08
US20200192335A1 (en) 2020-06-18

Similar Documents

Publication Publication Date Title
US8566949B2 (en) Software component, software component management method, and software component management system
US10523526B2 (en) System and method for managing services and licenses using a blockchain network
WO2018181705A1 (ja) プラント監視システム、プラント運転支援システム、プラント監視方法、及びプログラム
US20210243201A1 (en) Blockchain-based verification framework
US11868338B2 (en) Tracking and fault determination in complex service environment
US20190036935A1 (en) Automated certification based on role
US20100174812A1 (en) Secure remote maintenance and support system, method, network entity and computer program product
CN113065727A (zh) 基于区块链的测量设备管理方法及装置
US10341303B2 (en) Automating the creation and maintenance of policy compliant environments
JP7278299B2 (ja) データ管理サーバ、データ利用サーバ、データ流通システム、データ管理方法及びプログラム
WO2020055413A1 (en) Blockchain for audit
JP2021118444A (ja) 情報処理装置、情報処理方法及びプログラム
US20220210164A1 (en) Apparatus and method for managing remote attestation
US20250112787A1 (en) Public Key Infrastructure (PKI) Monitoring Systems and Methods
CN117134955B (zh) 一种计算机网络信息安全监护方法、装置及计算设备
JP7135893B2 (ja) 車両情報管理システム
CN111143788A (zh) 许可证处理方法、电子设备、存储介质及计算机程序产品
US12105808B2 (en) Automated trust center for real-time security and compliance monitoring
WO2021166607A1 (ja) 信頼性評価システム、信頼性評価方法
US20210365341A1 (en) Ledger-based device health data sharing
JP2015018477A (ja) 電子計量システム及び電子計量器のプログラム改竄処理方法
TWI831072B (zh) 開源軟體風險評鑑與智能監控系統及方法
US12464024B2 (en) SaaS security configurations distribution and management
CN119853922A (zh) 一种接口校验的方法、装置、计算机设备和存储介质
US20220294636A1 (en) Detecting Manipulated Clients in a Control System

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

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

Country of ref document: EP

Kind code of ref document: A1