JP2021005205A - Computer system and method for generating program for controlling system - Google Patents

Abstract

To provide a computer system capable of securing design flexibility, and inexpensively and easily designing a program of a system whose specifications are frequently changed.SOLUTION: A computer system for generating a program for controlling a system can access a database which stores flow management information for managing base program structure and specification management information for managing specifications of a system executing the base program. Data of a concatenation flow in which a plurality of flows containing components are concatenated is stored in the flow management information as data representing a structure of one base program. When it receives new specifications, the computer system selects reference specifications from the specification management information, and generates a design pattern serving as a new program candidate by adjusting a component contained in a base program corresponding to the reference specifications on the basis of the flow management information.SELECTED DRAWING: Figure 1

Description

The present invention relates to a method of generating a program for controlling a system such as a manufacturing plant or an infrastructure service plant.

In a plant where various devices operate in cooperation, it is managed by a program for controlling the operation of all the devices. The techniques described in Patent Document 1 and Patent Document 2 are known as methods for generating the above-mentioned programs.

In Patent Document 1, "The program creation device includes a work block definition unit 41, a process flow editing unit 42, and a control program generation unit 43. The process flow editing unit 42 desires a plurality of work block information. In the process flow obtained by arranging them in order, the internal state information of the setting target block information following the processing target work block information is set by using the post-condition of the processing target block information. The control program generation unit 43 sets the process. A control program is generated based on a plurality of work block information for which internal state information is set by the flow editing unit 43. "

In Patent Document 2, "a macro flow is created in which a plurality of automatic blocks in which the control contents of automatic sequence control are blocked for each series of automatic operations and the operation order of each automatic block are described, and in each automatic block. A microflow template in which the contents of the minimum automatic control to be performed among the automatic controls of the machine are described in advance is created, and the electronic files 21 and 22 are stored in the storage media 4 and 6. At the time of creating the specification, the electronic file 22 of the microflow model is read from the storage medium 6, and the necessary control contents are added to complete the microflow. Then, the microflow 32 is added to the macroflow 31 prepared in advance. By associating, the automatic control specification 30 is completed. "

Japanese Unexamined Patent Publication No. 2011-238041 Japanese Unexamined Patent Publication No. 2012-48651

Patent Document 1 describes that the setting information of the subsequent block is set by using the internal state information of the block in the previous stage and the post-condition. It is necessary to prepare an algorithm for setting the setting information of the subsequent block from the information of the previous block in advance. However, in order to generate the above-mentioned algorithm, it is necessary for the developer to understand the specifications of each device and the dependency relationship and mechanism between the devices based on the device driver and control program provided by the vendor. Therefore, the cost of generating such an algorithm is very high.

In particular, when the devices are frequently replaced, it is necessary to generate an algorithm for each device replacement. Therefore, it is not realistic in terms of cost and man-hours.

In Patent Document 2, it is necessary to prepare parts for program development in advance. However, it is necessary to secure the degree of freedom in design in order to respond to various specification changes and requirements of the system. Therefore, when a program is created by combining parts prepared in advance, the degree of freedom in design is limited.

An object of the present invention is to provide a system and a method for designing a program for controlling a system whose system specifications are frequently changed at low cost and easily while ensuring a degree of freedom in design.

A typical example of the invention disclosed in the present application is as follows. That is, a computer system that generates a program for controlling a system, comprising at least one computer having a processor, a memory connected to the processor, and a network interface connected to the processor, and generating a new program. Source code management information for managing the base program used for the operation, flow management information for managing the structure of the base program, and specification management for managing the specifications of the system that executes the base program. A database for storing information is accessible, and in the flow information, data of a concatenated flow in which a plurality of flows including at least one component, which is the smallest processing unit, are concatenated represents the structure of one base program. When the processor accepts a new specification for generating the new program, it is stored as data, and based on the comparison result between the new specification and the specification stored in the specification management information. A plurality of reference specifications are selected from the specifications stored in the specification management information, and a plurality of reference specifications are included in the base program corresponding to the reference specifications based on the source code management information and the flow management information. By adjusting the components, a design pattern that is a candidate for the new program is generated.

According to the present invention, it is possible to easily design a program for controlling a system whose system specifications are frequently changed at low cost while ensuring a degree of freedom in design. Issues, configurations and effects other than those mentioned above will be clarified by the description of the following examples.

It is a figure which shows an example of the apparatus structure and the program structure of the computer system which concerns on Example 1. FIG. It is a figure which shows an example of the call and response between the control system program and the device control program which concerns on Example 1. FIG. It is a figure explaining the structure of the control system program which concerns on Example 1. FIG. It is a figure which shows an example of the structure of the component which concerns on Example 1. FIG. It is a figure which shows an example of the information managed by the data management server which concerns on Example 1. FIG. It is a figure which shows an example of the data structure of the parameter management information which concerns on Example 1. FIG. It is a figure which shows an example of the data structure of the code management information which concerns on Example 1. FIG. It is a figure which shows an example of the data structure of the specification management information which concerns on Example 1. FIG. It is a figure which shows an example of the data structure of the constraint condition management which concerns on Example 1. FIG. It is a figure which shows an example of the data structure of the flow management information which concerns on Example 1. FIG. It is a figure which shows an example of the data structure of the flow management information which concerns on Example 1. FIG. It is a figure which shows an example of the data structure of the flow management information which concerns on Example 1. FIG. It is a figure which shows an example of the structure of the connected flow defined by the flow management information which concerns on Example 1. FIG. It is a flowchart explaining the process executed by the control system program design apparatus which concerns on Example 1. FIG. It is a figure which shows an example of the screen which the control system program design apparatus which concerns on Example 1 presents. It is a figure which shows an example of the connection flow which the control system program design apparatus which concerns on Example 1 presents. It is a figure which shows an example of the connection flow which the control system program design apparatus which concerns on Example 1 presents. It is a figure which shows an example of the connection flow which the control system program design apparatus which concerns on Example 1 presents.

Hereinafter, examples of the present invention will be described with reference to the drawings. However, the present invention is not construed as being limited to the contents of the examples shown below. It is easily understood by those skilled in the art that a specific configuration thereof can be changed without departing from the idea or purpose of the present invention.

In the configurations of the invention described below, the same or similar configurations or functions are designated by the same reference numerals, and duplicate description will be omitted.

The notations such as "first", "second", and "third" in the present specification and the like are attached to identify the components, and do not necessarily limit the number or order.

The position, size, shape, range, etc. of each configuration shown in the drawings and the like may not represent the actual position, size, shape, range, etc., in order to facilitate understanding of the invention. Therefore, the present invention is not limited to the position, size, shape, range, etc. disclosed in the drawings and the like.

FIG. 1 is a diagram showing an example of a device configuration and a program configuration of the computer system according to the first embodiment.

The computer system is composed of a control system program design device 100 and a plant 10.

The control system program design device 100 is connected to the control system 10 directly or via a network. The network is, for example, WAN (Wide Area Network) and LAN (Local Area Network). The network connection method may be either wireless or wired.

In FIG. 1, the control system program design device 100 is connected to one plant 10, but may be connected to two or more plants 10.

The plant 10 includes a data management server 103, a control system server 104, a gateway 105, a storage device 106, a plurality of control devices 107, and a plurality of storage devices 108.

The data management server 103 and the control system server 104 are connected to each other via the network 110, and the gateway 105 and the plurality of control devices 107 are connected to each other via the network 111. The control system server 104 and the gateway 105 are connected to each other directly or via a network, and the control system server 104 and the storage device 106 are connected to each other directly or via a network. The control device 107 and the storage device 108 are connected to each other directly or via a network.

Data and messages are transmitted and received by socket communication between servers, between servers and devices, and between devices.

The data management server 103 includes a processor, a memory, a network interface, and a storage device (not shown), and manages various types of data. Details of the data managed by the data management server 103 will be described with reference to FIG. A network attached storage (NAS) may be provided instead of the data management server 103. If you want to reduce the price of the system by limiting the functions to data storage and sharing, NAS may be adopted.

The control device 107 controls a device such as a robot operating in the plant 10 based on the device control program 150 stored in the storage device 108. The storage device 108 stores a device control program 150 for controlling at least one device. One device control program 150 includes code that implements at least one or more control APIs.

The gateway 105 includes a processor, memory, and network interface (not shown) to control communication between the control system server 104 and the control device 107.

The control system server 104 has a processor, a memory, and a network interface (not shown), and controls the business in the plant 10, that is, the control device 107, based on the control system program 140 stored in the storage device 106. At least one control system program 140 is stored in the storage device 106. One control system program 140 contains code for executing at least one subroutine. The plant 10 may include a plurality of control system servers 104.

When the control system server 104 receives the message, the control system server 104 selects the control system program 140 to be started based on the type and content of the message, and executes the selected control system program 140. The control system server 104 transmits the execution result of the program to the data management server 103. The control system server 104 also controls the order and branching of messages, converts the data format, accesses data, and the like.

The control system program design device 100 includes a processor, a memory, and a network interface (not shown), and designs the control system program 140. A system that realizes the same functions as the control system program design device 100 may be constructed by using a plurality of computers.

The control system program design device 100 executes a program that realizes the viewer 120 and the design support module 121.

The viewer 120 displays the processing result and other information of the control system program design device 100.

The design support module 121 designs the control system program 140. Includes matching module 130 and selection module 131.

The matching module 130 generates a design pattern that is a candidate for the control system program 140 so as to match the contents of work (system specifications) in the plant. The selection module 131 selects a design pattern that matches the conditions from the design patterns generated by the matching module 130.

FIG. 2 is a diagram showing an example of a call and a response between the control system program 140 and the device control program 150 according to the first embodiment.

The control system program 140 is composed of at least one subroutine 200. The subroutine 200 is composed of at least one subtask 210. The device control program 150 is composed of at least one API 220.

The subtask 210 calls the API 220 of the device control program 150 corresponding to the device to be controlled and controls the device.

The control system program 140 shown in FIG. 2 is composed of two subroutines 200-1 and 200-2. Subroutine 200-1 is composed of subtasks 210-1 and 210-2, and subroutine 200-2 is composed of subtasks 210-3. The device control program 150-1 is composed of API A-1 (220-1) and API A-2 (220-2), and the device control program 150-2 is composed of API B-1 (220-3) and API. It is composed of B-2 (220-4), and the device control program 150-3 is composed of API C-1 (220-5) and API C-2 (220-6).

Subtask 210-1 calls API A-1 (220-2), subtask 210-2 calls API B-2 (220-2), and subtask 210-1 calls API C-1 (220-5). ) Is called.

The control system program 140 can handle the data of the structure whose component is the processing of the smallest unit. Here, the structure of the control system program 140 will be described.

FIG. 3 is a diagram illustrating the structure of the control system program 140 according to the first embodiment. FIG. 4 is a diagram showing an example of the structure of the component 300 according to the first embodiment.

The control system program 140 is composed of a plurality of components 300. The control system program 140 shown in FIG. 3 is composed of seven components 300-1, 300-2, 300-3, 300-4, 300-5, 300-6, and 300-7.

As shown in FIG. 4, the component 300 is a set of codes and parameters representing functions, APIs, etc., and represents the smallest unit of processing (work, tasks, etc.).

A set of components 300 that realize one function is treated as a flow 310. The flow 310 includes at least one component 300. One flow 310 corresponds to one transaction. Here, a transaction represents a unit of an indivisible series of processes executed in a system, and is a unit in which a plurality of interdependent processes are all completed or all canceled.

The control system program 140 shown in FIG. 3 includes three flows 310-1, 310-2, and 310-3.

The connection flow 320, which is formed by connecting a plurality of flows 310, represents the control system program 140 itself. The concatenated flow 320 corresponds to a service or the like realized by combining a plurality of functions.

FIG. 5 is a diagram showing an example of information managed by the data management server 103 according to the first embodiment.

The data management server 103 manages parameter management information 500, code management information 501, specification management information 502, constraint condition management 503, source code management information 504, and flow management information 505.

The parameter management information 500 is information for managing the parameter adjustment method. The details of the data structure of the parameter management information 500 will be described with reference to FIG.

The code management information 501 is information for managing the code adjustment method. The details of the data structure of the code management information 501 will be described with reference to FIG.

The specification management information 502 is information for managing the specifications that define the system specifications, such as the requirements for controlling the plant 10. The details of the data structure of the specification management information 502 will be described with reference to FIG.

The constraint condition management 503 is information for managing the conditions and the like satisfied by the control system program 140. The details of the data structure of the constraint condition management 503 will be described with reference to FIG.

The source code management information 504 is information for managing a code group (source code) which is an entity of the control system program 140. The source code is managed in association with the identification information of the connection flow 320.

The flow management information 505 is information for managing the structure of the control system program 140, that is, the connected flow 320. Details of the data structure of the flow management information 505 will be described with reference to FIGS. 10, 11A, and 11B.

FIG. 6 is a diagram showing an example of a data structure of the parameter management information 500 according to the first embodiment.

The parameter management information 500 stores a record composed of No601, classification ID 602, classification 603, name 604, and set value 605. There is one record for one parameter. In addition, one record may be set for one parameter adjustment method.

No. 601 is a field for storing the identification number of the parameter. The classification ID 602 is a field for storing identification information regarding the classification of parameters. Classification 603 is a field that stores the classification of parameters. The name 604 is a field for storing the name of the parameter. The setting value 605 is a field for storing the value to be set in the parameter corresponding to the record.

In this embodiment, it is assumed that the parameter adjustment result performed in the design of the control system program 140 in the past is stored in the parameter management information 500. The user may set in advance. If the number of records stored in the parameter management information 500 is small, or if the user cannot set in advance, the user executes a behavior test of the program in the test environment, and the result is stored in the parameter management information 500. All you have to do is register.

FIG. 7 is a diagram showing an example of the data structure of the code management information 501 according to the first embodiment.

The code management information 501 stores a record composed of No. 701, component ID 702, processing type 703, and setting code 704. There is one record for one code. In addition, one record may be set for one code adjustment method.

No. 701 is a field for storing the identification number of the code. The component ID 702 is a field for storing the identification information of the component including the code. The processing type 703 is a field for storing the type of processing realized by the code. The setting code 704 is a field for storing information about the set code. The setting code 704 may store the code itself, or may store information composed of conditions and codes.

In this embodiment, it is assumed that the code adjustment result performed in the design of the control system program 140 in the past is stored in the code management information 501. The user may set in advance. If the number of records stored in the code management information 501 is small, or if the user cannot set in advance, the user executes a program behavior test in the test environment and converts the result into the code management information 501. All you have to do is register.

FIG. 8 is a diagram showing an example of the data structure of the specification management information 502 according to the first embodiment.

The specification management information 502 stores a record composed of No801, connection flow ID802, item ID803, item classification 804, name 805, set value 806, and unit 807. There is a record for one specification. Also, one record contains as many rows as there are items.

No. 801 is a field for storing the identification number of the specification. The concatenation flow ID 802 is a field for storing the identification information of the concatenation flow 320 having the best score corresponding to the specification. Item ID 803 is a field for storing item identification information. Item classification 804 is a field for storing the item classification. The name 805 is a field for storing the name of the item. The setting value 806 is a field for storing definition information of the value to be set for the item. The unit 807 is a field for storing the unit of the value corresponding to the set value 806.

FIG. 9 is a diagram showing an example of the data structure of the constraint condition management 503 according to the first embodiment.

The constraint condition management 503 stores a record composed of No. 901, condition classification 902, item name 903, priority 904, and content 905. There is one record for one constraint.

No. 901 is a field for storing the identification number of the constraint condition. The condition classification 902 is a field for storing the classification of the constraint condition. The item name 903 is a field for storing the name of the object (item) of the constraint. The priority 904 is a field for storing the priority of the constraint condition. The content 905 is a field for storing the specific content of the constraint condition.

In this embodiment, three types of constraints, a "single constraint" constraint, a "crossing constraint" constraint, and a "system constraint" constraint, are set in the constraint management 503.

The constraint condition of "single constraint" is a constraint condition relating to the apparatus operating in the plant 10. The constraint condition of "single constraint" is generated based on the specifications and operating conditions of the device.

The constraint condition of the "crossing constraint" is a constraint condition relating to the exchange between a plurality of devices operating in the plant 10. The constraint condition of "crossing constraint" is generated based on the dependency between devices and the difference in interface specifications.

The constraint condition of "system constraint" is a constraint condition related to the plant 10. The constraint condition of "system constraint" is generated based on a user request from a viewpoint different from the operation of the device, such as a stoppage due to a holiday of the company operating the plant 10, an update of the plant 10, and a test operation.

Priority is set for the same type of constraint. By applying the constraint condition based on the priority, the strength of narrowing down the number of design patterns of the program can be adjusted, and a more preferable program can be output.

It should be noted that the content and number of constraints can be adjusted according to the content of operations in the manufacturing industry and the plant 10 such as infrastructure services such as electric power, gas, and water supply.

10, 11A and 11B are diagrams showing an example of the data structure of the flow management information 505 according to the first embodiment. FIG. 12 is a diagram showing an example of the structure of the connected flow 320 defined by the flow management information 505 according to the first embodiment.

The flow management information 505 includes the concatenated flow structure information 1000 and the flow / component structure information 1100.

The concatenated flow structure information 1000 stores a record composed of a concatenated flow ID 1001, a start component ID 1002, an end component ID 1003, and a concatenated flow function 1004. There is one record for one concatenated flow 320.

The concatenation flow ID 1001 is a field for storing the identification information of the concatenation flow 320. The start component ID 1002 is a field that stores the identification information of the component 300 that is the starting point of the connection flow 320. The end component ID 1003 is a field that stores the identification information of the component 300 that is the end point of the connection flow 320. The concatenated flow function 1004 is a field for storing information about the function realized by the concatenated flow 320.

The flow / component structure information 1100 stores a record composed of a flow ID 1101, a component ID 1102, a front component ID 1103, a rear component ID 1104, a transition condition 1105, and a flow function 1106. There is one record for one flow 310. In addition, one record contains as many rows as the number of components 300 constituting the flow 310.

The flow ID 1101 is a field for storing the identification information of the flow 310. The component ID 1102 is a field that stores identification information of the component 300 that constitutes the flow 310.

The front component ID 1103 is a field for storing the identification information of the component 300 connected before the component 300 corresponding to the component ID 1102. The rear component ID 1104 is a field for storing the identification information of the component 300 connected after the component 300 corresponding to the component ID 1102.

The transition condition 1105 is a group of fields that stores information about the transition between the components 300, and includes an ID 1111, a related ID 1112, and a condition 1113.

ID 1111 is a field for storing the identification information of the transition source component 300, that is, the component 300 corresponding to the component ID 1102. The related ID 1112 is a field for storing the identification information of the transition destination component 300, that is, the component 300 corresponding to the post-component ID 1104. The condition 1113 is a field for storing information regarding the condition and processing of the transition between the components 300.

The flow function 1106 is a field for storing information about the function realized by the flow 310.

The connection flow 320 having the connection flow ID 1001 of "001C" has a structure as shown in FIG. The numbers in the solid box represent the identification information of the component 300, and the numbers in the dotted box represent the identification information of the flow 310.

Next, the process executed by the control system program design device 100 will be described.

The control system program design device 100 uses the previously designed control system program 140 as a design asset to design a new control system program 140. In the present invention, it is assumed that the program development is carried out with the change of a part or all of the system specifications, and it is assumed that any of the following conditions is satisfied.

(1) The system specifications can be satisfied by adjusting the parameters of the target component 300 of the existing program or adjusting the parameters of the target component 300 and the component 300 having a dependency relationship with the target component 300.

(2) The system specifications can be satisfied by adjusting the parameters and codes of the target component 300.

(3) The system specifications can be satisfied by adjusting the parameters and codes of the target component 300 and adjusting the parameters and codes of the component 300 having a dependency relationship with the target component 300.

Here, the adjustment of the parameter includes a change of a numerical value or a character string assigned to an arbitrary variable (parameter). In addition, code adjustment is not only a simple change such as a change from addition processing to subtraction processing or a change from multiplication processing to division processing, but also complicated calculation processing, data conversion processing, and transmission of commands for controlling the device. Includes complicated processing changes such as processing.

For a reconciliation of the code, engineers, read the changes in the system specification, considered if the best case that understand what may be adjusted to any code in advance, to adjust the pre-user code is case, control The system program design device 100 adjusts only the parameters. On the other hand, there are some worst cases where engineers don't understand which code to adjust. In this case, algorithms such as machine learning and artificial intelligence that realize advanced parameter and code adjustment may be introduced into the control system program design device 100. The control system program design device 100 searches for an optimum value, an optimum solution, or an optimum code, and designs a program that satisfies the system specifications.

In the following description, parameter adjustment and code adjustment will be referred to as component 300 adjustment.

In addition to the automatic processing, the adjustment of the component 300 includes processing performed in cooperation with the user by using the least squares method, likelihood estimation, pattern matching, machine learning, artificial intelligence, and the like.

FIG. 13 is a flowchart illustrating a process executed by the control system program design device 100 according to the first embodiment. FIG. 14 is a diagram showing an example of a screen presented by the control system program design device 100 according to the first embodiment. 15A, 15B, and 15C are diagrams showing an example of a connection flow presented by the control system program design device 100 according to the first embodiment.

When the design support module 121 of the control system program design device 100 receives the generation request of the control system program 140 including the new specifications, the design support module 121 starts the process described below.

The design support module 121 compares the new specifications with the specifications stored in the specification management information 502, and selects the specifications to be used based on the comparison result (step S101). For example, the following processing can be considered.

The design support module 121 compares the settings of each item in the specifications, calculates the similarity of the settings of each item, and calculates the average value or the total value of the similarity of all the items as the evaluation value. The design support module 121 selects the specification having the highest evaluation value. The design support module 121 refers to the flow management information 505 based on the connection flow ID 802 of the record corresponding to the selected specification, and acquires the information of the connection flow 320 corresponding to the selected specification. The design support module 121 sets the acquired connection flow 320 as a base program (base connection flow 320).

The above-mentioned specification selection method is an example and is not limited to this. For example, the specifications may be selected based on the type of specifications, the type of user, and the like.

The design support module 121 executes the component matching process (step S102). Specifically, the following processing is executed.

(S102-1) The matching module 130 selects the target component 300. It is assumed that the target component 300 is selected so as to follow the flow of the connection flow 320. The target component 300 is also described as the first layer component 300.

(S102-2) The matching module 130 adjusts the first layer component 300 so as to satisfy the device specifications or operating conditions defined in the new specifications with reference to the parameter management information 500 and the code management information 501. To do. In the adjustment of the component 300, at least one of the parameter and code changes is adjusted. At this time, the matching module 130 evaluates how close the value output from the first layer component 300 is to the output target value.

Here, the matching module 130 calculates the output similarity defined by the equation (1) as an evaluation value. The output target value shall be included in the new specifications.

(S102-3) The matching module 130 identifies the component 300 connected to the first layer component 300, and executes the same processing as in (S102-3) for the component 300. The identified component 300 is referred to as a second layer component 300. It should be noted that not only the second layer component 300 but also the first layer component may be adjusted.

(S102-4) The matching module 130 identifies the component 300 connected to the second layer component 300, and executes the same processing as in (S102-3) for the component 300. The identified component 300 is referred to as a third layer component 300. In addition to the third layer component, adjustments may be made to the first layer component 300 and the second layer component 300.

(S102-5) In the matching module 130, whether or not the statistical value (for example, average value or total value) of the output similarity of the first layer component 300, the second layer component 300, and the third layer component 300 is larger than the threshold value. Is determined. When the statistical value of the output similarity is larger than the threshold value, the matching module 130 registers the connection flow 320 generated by (S102-2) to (S102-4) in the list as a candidate design pattern.

(S102-6) In the matching module 130, when the number of candidate design patterns registered in the list exceeds the threshold value, or the number of times of loop processing from (S102-2) to (S102-5) is executed is the threshold value. When the above is obtained, the process proceeds to (S102-7).

(S102-7) The matching module 130 determines whether or not the processing is completed for all the components 300. If it is determined that the processing has not been completed for all the components 300, the matching module 130 returns to (S102-1). When it is determined that the processing is completed for all the components 300, the matching module 130 ends the processing in step S102.

As a result of adjusting one component 300, an event such as an inconsistent interface to another component 300 or the behavior of the dependent component 300 may not satisfy the system specifications may occur. Therefore, the matching module 130 adjusts the component 300 hierarchically.

Further, by adjusting the hierarchical component 300, it is possible to divert as much design assets as possible and reduce the man-hours required for the adjustment. In addition, by diverting as many design assets as possible that are guaranteed to conform to the system specifications, it is possible to design a program that is likely to conform to the system specifications, that is, has high reliability.

The number of layers of the component 300 to be evaluated can be arbitrarily set. The above is the description of the process of step S102.

Next, the selection module 131 of the design support module 121 narrows down the design pattern based on the constraint condition of the “single constraint” (step S103). Specifically, the selection module 131 determines whether or not the constraint condition of the "single constraint" is satisfied for each component 300 included in the design pattern.

Next, the design support module 121 executes the flow matching process (step S104). Specifically, the following processing is executed.

(S104-1) The matching module 130 selects a design pattern.

(S104-2) The matching module 130 selects the target flow 310 from the design patterns. The target flow 310 shall be selected so as to follow the flow of the connected flow 320.

(S104-3) The matching module 130 calculates the output similarity of the components included in the target flow 310, and further calculates statistical values such as the sum, mean, variance, and standard deviation of each output similarity. This is a value for evaluating the output of the flow 310. Further, the matching module 130 calculates the structural similarity of the flow 310 defined by the equation (2). The flow similarity index is given by the equation (3), and the component similarity index is given by the equation (4). Structural similarity is used as an index for designing a program similar to the base program.

(S104-4) When each of the output similarity statistical value and the structural similarity index is larger than the threshold value, the matching module 130 registers the connection flow 320 as a candidate design pattern in the list. If at least one of the output similarity statistics and the structural similarity index is below the threshold, the matching module 130 adjusts the component 300 included in the flow 310. For example, the matching module 130 adjusts the components 300 in ascending order of output similarity. The matching module 130 executes the process (S104-3) for the flow 310 including the adjusted component 300.

When the number of executions of the process of (S104-3) is larger than the threshold value, the matching module 130 proceeds to (S104-5).

(S104-5) The matching module 130 determines whether or not the processing is completed for all the flows 310 included in the selected design pattern. When it is determined that the processing is not completed for all the flows 310 included in the selected design pattern, the matching module 130 returns to (S104-2).

(S104-6) When it is determined that the processing is completed for all the flows 310 included in the selected design pattern, the matching module 130 determines whether or not the processing is completed for all the design patterns. When it is determined that the processing is not completed for all the design patterns, the matching module 130 returns to (S104-1). When it is determined that the processing is completed for all the design patterns, the matching module 130 ends the processing in step S104.

The matching module 130 does not have to use the structural similarity. The above is the description of the process of step S104.

Next, the selection module 131 of the design support module 121 narrows down the design pattern based on the constraint condition of the “crossing constraint” (step S105). Specifically, the selection module 131 determines whether or not the constraint condition of the "crossing constraint" is satisfied for each flow 310 included in the design pattern.

Next, the design support module 121 executes the connection flow matching process (step S106). Specifically, the following processing is executed.

(S106-1) The matching module 130 selects a design pattern.

(S106-2) The matching module 130 calculates the output similarity of the components 300 included in each flow 310, and also calculates the structural similarity of each flow 310. The matching module 130 calculates the output similarity statistical value and the structural similarity statistical value of the component.

(S106-3) When each of the output similarity statistical value and the structural similarity statistical value is larger than the threshold value, the matching module 130 registers the connection flow 320 as a candidate design pattern in the list. If at least one of the output similarity statistics and the structure similarity index statistics is less than or equal to the threshold, the matching module 130 adjusts at least one of the components 300. For example, the matching module 130 adjusts the components 300 in ascending order of output similarity. The matching module 130 executes the process (S106-2) for the connection flow 320 including the adjusted component 300.

When the number of executions of the process of (S106-3) is larger than the threshold value, the matching module 130 proceeds to (S106-4).

(S106-4) The matching module 130 determines whether or not the processing is completed for all the design patterns. When it is determined that the processing is not completed for all the design patterns, the matching module 130 returns to (S106-1). When it is determined that the processing is completed for all the design patterns, the matching module 130 ends the processing in step S106.

The matching module 130 does not have to use the structural similarity. The above is the description of the process of step S106.

Next, the selection module 131 of the design support module 121 narrows down the design pattern based on the constraint condition of the “system constraint” (step S107). Specifically, the selection module 131 determines whether or not the constraint condition of the "system constraint" is satisfied for the connection flow 320 corresponding to the design pattern.

Next, the design support module 121 registers information about the design pattern in the data management server 103 (step S108).

Information about the adjusted parameters is registered in the parameter management information 500, information about the adjusted code is registered in the code management information 501, new specifications are registered in the specification management information 502, and the source code corresponding to the design pattern is registered. Is registered in the source code management information 504, and the connection flow 320 corresponding to the design pattern is stored in the flow management information 505.

Next, the viewer 120 presents information about the design pattern (step S109), and then ends the process. The viewer 120 displays, for example, the screen 1400 as shown in FIG.

The screen 1400 includes a design pattern selection field 1401, a base program display button 1402, a design pattern display button 1403, and a detailed information field 1404.

The design pattern selection column 1401 is a column for selecting a design pattern to be evaluated or browsed. In FIG. 14, a design pattern that can be selected in a pull-down format is presented.

The base program display button 1402 is a button for displaying the base program used when generating the design pattern. When the user operates the base program display button 1402, the viewer 120 presents, for example, a connection flow 320 corresponding to the base program as shown in FIG. 15A. The connected flow 320 includes flows 310-1 and 310-2. The U-shaped component 300 indicates a branch, and the component 300 including the DB character string indicates a database.

The design pattern display button 1403 is a button for displaying the design pattern selected in the design pattern selection field 1401. When the user operates the design pattern display button 1403, the viewer 120 presents, for example, a connection flow 320 corresponding to the design pattern as shown in FIG. 15B or FIG. 15C.

When a new parameter is added due to a change in the system specifications, it is necessary to create a new component 300 including the new parameter. Further, in order to add the new component 300, it is necessary to add the dependency component 300 that functions as an interface that acts as an intermediary for the component 300 of the base program.

In the concatenation flow 320 shown in FIG. 15B, the black box represents the new component 300 containing the new parameters and the shaded box represents the dependency component 300. Also, the dot box represents the component 300 whose parameters have been adjusted with the addition of the dependency component 300.

In the connected flow 320 shown in FIG. 15C, the component 300 of the flow 310-1 is adjusted. Specifically, it includes a component 300 whose parameters are adjusted according to a change in system specifications, and two dependency components 300 whose parameters are adjusted according to the adjustment of the component 300.

The detailed information column 1404 is a column for displaying the structure of the selected design pattern, indexes such as output similarity and structural similarity, and changes from the base program.

The viewer 120 may present a list of design patterns sorted based on output similarity statistics, structural similarity statistics, and the like. At this time, the viewer 120 may present only the upper design pattern.

The viewer 120 may present the source code, parameters, codes, and the like as information such as numerical values, texts, graphs, and figures.

After the matching process is executed, the design pattern is narrowed down based on the constraint conditions because the larger the number of sample data, the better the matching accuracy and the calculation convergence.

Further, assuming a change or replacement of the device, the matching process is executed bottom-up in the order of the component 300, the flow 310, and the connected flow 320 so that the device can be operated reliably in the new system.

After each matching process is executed, the design pattern may be narrowed down based on the constraint conditions. However, the constraints are applied in the order of "single constraint", "crossing constraint", and "system constraint".

When the control system program 140 is newly generated without using the past control system program 140, the control system program design device 100 executes the following processing.

The design support module 121 generates the component 300 based on the specifications, the parameter management information 500, and the code management information 501, connects the components 300 to generate the flow 310, and further connects and connects the flow 310. Generate flow 320. The design support module 121 selects the connection flow 320 that satisfies the constraint condition.

As described above, the control system program design device 100 can easily design a program for controlling a system whose system specifications are frequently changed by diverting the previously designed control system program 140. Further, since the control system program design device 100 can design the control system program 140 by adjusting the component 300 based on the parameter management information 500 and the code management information 501, the cost required for designing the program can be reduced.

The present invention is not limited to the above-mentioned examples, and includes various modifications. Further, for example, the above-described embodiment describes the configuration in detail in order to explain the present invention in an easy-to-understand manner, and is not necessarily limited to the one including all the described configurations. Further, it is possible to add, delete, or replace a part of the configuration of each embodiment with other configurations.

Further, each of the above configurations, functions, processing units, processing means and the like may be realized by hardware by designing a part or all of them by, for example, an integrated circuit. The present invention can also be realized by a program code of software that realizes the functions of the examples. In this case, a storage medium in which the program code is recorded is provided to the computer, and the processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium realizes the functions of the above-described embodiment, and the program code itself and the storage medium storing the program code itself constitute the present invention. Examples of the storage medium for supplying such a program code include a flexible disk, a CD-ROM, a DVD-ROM, a hard disk, an SSD (Solid State Drive), an optical disk, a magneto-optical disk, a CD-R, and a magnetic tape. Non-volatile memory cards, ROMs, etc. are used.

Further, the program code that realizes the functions described in the present embodiment can be implemented in a wide range of programs or script languages such as assembler, C / C ++, perl, Shell, PHP, Python, and Java (registered trademark).

Further, by distributing the program code of the software that realizes the functions of the examples via the network, it is stored in a storage means such as a hard disk or memory of a computer or a storage medium such as a CD-RW or a CD-R. , The processor provided in the computer may read and execute the program code stored in the storage means or the storage medium.

In the above-described embodiment, the control lines and information lines show what is considered necessary for explanation, and do not necessarily indicate all the control lines and information lines in the product. All configurations may be interconnected.

10 Control system (plant)
100 Control system program design device 103 Data management server 104 Control system server 105 Gateway 106 Storage device 107 Control device 108 Storage device 110, 111 Network 120 Viewer 121 Design support module 130 Matching module 131 Selection module 140 Control system program 150 Device control program 200 Subtask 210 Subtask 220 API
300 Component 310 Flow 320 Concatenated flow 500 Parameter management information 501 Code management information 502 Specification management information 503 Constraint management 504 Source code management information 505 Flow management information

Claims (8)

A computer system that generates programs to control the system.
It comprises at least one computer having a processor, a memory connected to the processor, and a network interface connected to the processor.
To manage source code control information for managing the base program used to generate a new program, flow management information for managing the structure of the base program, and specifications of the system that executes the base program. You can access the database that stores the specification management information of
In the flow management information, data of a concatenated flow in which a plurality of flows including at least one component which is the smallest processing unit are concatenated is stored as data representing the structure of one base program.
The processor
When a new specification for generating the new program is accepted, it is stored in the specification management information based on the comparison result between the new specification and the specification stored in the specification management information. Select the reference specification from the specifications and select
Based on the source code management information and the flow management information, a design pattern that is a candidate for the new program is generated by adjusting a plurality of the components included in the base program corresponding to the reference specifications.
A computer system characterized by outputting the design pattern. The computer system according to claim 1.
The component consists of at least one code and at least one parameter.
The database stores code management information for managing the code change method and parameter management information for managing the parameter change method.
The processor modifies the at least one code and the at least one parameter of the component included in the base program corresponding to the reference specification based on the code management information and the parameter management information. A computer system characterized by adjusting. The computer system according to claim 2.
Multiple devices are operating in the system
The database manages a first constraint that defines a constraint on the device, a second constraint that defines a constraint on interaction between the plurality of devices, and a third constraint that defines a constraint on the system. Stores constraint condition management information
The processor
A plurality of first design patterns are generated by adjusting each of the plurality of components included in the base program so that the difference between the output of the component and the target output becomes small.
The first design pattern satisfying the first constraint condition is selected from the plurality of first design patterns.
A plurality of second designs by adjusting the at least one component included in the plurality of flows included in the selected first design pattern so that the difference between the output of the flow and the target output becomes small. Generate a pattern and
The second design pattern satisfying the second constraint condition is selected from the plurality of second design patterns.
A plurality of third design patterns are generated by adjusting each of the plurality of components included in the selected second design pattern so that the difference between the output of the connection flow and the target output becomes small.
The third design pattern satisfying the third constraint condition is selected from the plurality of third design patterns.
A computer system characterized by outputting the selected third design pattern. The computer system according to claim 3.
The processor
The at least one component included in the plurality of flows included in the first design pattern has a small difference between the output of the flow and the target output, and the structure of the flow before the change and the flow after the change. Adjusted to be similar to the structure of
Each of the plurality of components included in the third design pattern has a small difference between the output of the connection flow and the target output, and has a structure of the connection flow before the change and a structure of the connection flow after the change. A computer system characterized by adjusting so that they are similar. A method of generating a program to control a computer system, which is executed by a computer system.
The computer system
Includes a processor, memory connected to the processor, and at least one computer having a network interface connected to the processor.
To manage source code control information for managing the base program used to generate a new program, flow management information for managing the structure of the base program, and specifications of the system that executes the base program. You can access the database that stores the specification management information of
In the flow management information, data of a concatenated flow in which a plurality of flows including at least one component which is the smallest processing unit are concatenated is stored as data representing the structure of one base program.
The method of generating the program is
When the processor accepts a new specification for generating the new program, the specification management information is based on a comparison result between the new specification and the specification stored in the specification management information. The first step to select a reference specification from the specifications stored in
Based on the source code control information and the flow management information, the processor adjusts a plurality of the components included in the base program corresponding to the reference specifications to obtain a design pattern that is a candidate for the new program. The second step to generate and
A method of generating a program, wherein the processor includes a third step of outputting the design pattern. The method for generating a program according to claim 5.
The component consists of at least one code and at least one parameter.
The database stores code management information for managing the code change method and parameter management information for managing the parameter change method.
In the second step, the processor uses the code management information and the parameter management information to obtain the at least one code and the at least one parameter of the components included in the base program corresponding to the reference specifications. A method of generating a program, comprising the step of adjusting the component by modifying it. The method for generating a program according to claim 6.
Multiple devices are operating in the system
The database manages a first constraint that defines a constraint on the device, a second constraint that defines a constraint on interaction between the plurality of devices, and a third constraint that defines a constraint on the system. Stores constraint condition management information
The second step is
A fourth, in which the processor adjusts each of the plurality of components included in the base program so that the difference between the output of the component and the target output becomes small, thereby generating a plurality of first design patterns. Steps and
A fifth step in which the processor selects the first design pattern satisfying the first constraint condition from the plurality of first design patterns.
The processor adjusts the at least one component included in the plurality of flows included in the selected first design pattern so that the difference between the output of the flow and the target output becomes small. The sixth step of generating the second design pattern of
A seventh step in which the processor selects the second design pattern satisfying the second constraint condition from the plurality of second design patterns.
The processor adjusts each of the plurality of components included in the selected second design pattern so that the difference between the output of the connection flow and the target output becomes small, so that the plurality of third design patterns Eighth step to generate
A ninth step in which the processor selects the third design pattern satisfying the third constraint condition from the plurality of third design patterns.
A method of generating a program, wherein the processor comprises a tenth step of outputting the selected third design pattern. The method for generating a program according to claim 7.
In the sixth step, the processor changes the at least one component included in the plurality of flows included in the first design pattern so that the difference between the output of the flow and the target output is small and before the change. Including the step of adjusting the structure of the flow and the structure of the modified flow so as to be similar to each other.
In the eighth step, the processor makes each of the plurality of components included in the third design pattern have a small difference between the output of the connection flow and the target output, and the connection flow before the change. A method of generating a program, which comprises a step of adjusting the structure and the structure of the connected flow after the change so as to be similar.

Images