JP5180809B2 - Information control system and method for creating control software - Google Patents

Description

  The present invention relates to an information control system and control software creation method that can clearly define and execute conditions that define the state of a device to be controlled.

  There is a waterfall model as a program development model of an information control system. The waterfall model divides the entire project into several processes, clearly defines the deliverables in each process (documents such as specifications and design documents), and performs post-process work based on the deliverables. Go sequentially. The waterfall model is a document-driven development process aimed at applying the principle of “definition by specification”.

  For example, in an information control system such as a power system, a train operation management system, and a water and sewage management system, a “system specification” is created between the orderer and the contractor at the time of ordering the system. This system specification is a document for defining the state of equipment (equipment) constituting the system. In addition, the system specification is an important interface document among the orderer, the contractor, the designer, and the producer (coding). Therefore, in the system specification, various explanations regarding the state of the device are written in sentences such as Japanese.

Further, a reserved word file in which syntax rules and execution rules for each reserved word are associated is defined, and a processing method of an execution program is disclosed using a script using a reserved word in the business process definition file (for example, , See Patent Document 1).
JP 2005-149339 A

  However, in the technique of Patent Document 1, the business process definition is described by a simple script, but there remains a problem of creating a script for the contents of the system specifications of the business process.

  There are cases where the description of the system specification is basically ambiguous or missing. For example, Japanese may be interpreted multiple times in one sentence. Further, for example, in the system specification, it is often described as “Zoom when not in the state of XX” by a Japanese sentence.

  A designer or producer cannot produce a control program unless the conditions under which the “XX state” is not satisfied are clear. Therefore, it is preferable that the system specification document describes a condition that does not hold. However, in the system specification, only the explanation when the “XX state” is established is described in Japanese, and the explanation when the “XX state” is not established is not described. Many. Therefore, even in this respect, the description of the system specification may be ambiguous.

  In addition, the conditions that define the state of the device are often unclear as to whether the conditions are satisfied or not, and it is necessary to be skillful to write all the conditions in Japanese without omission. For example, in the system specification, it is often written as “YY when in the state of XX” by a Japanese sentence. When the “XX state” is satisfied only by one condition, the condition is uniquely determined. Therefore, this sentence is clear. However, when “the state of XX” is satisfied by a plurality of conditions, there is a problem that the conditions for establishing and not satisfying the conditions are often unclear.

  As described above, conventionally used system specifications may have vague descriptions or omissions. Moreover, even if the system specifications that have been used in the past are described in an ambiguous manner, they are misunderstood as if all explanations are clearly understood by the reader only by the description. There was a case.

  Therefore, there has been a problem that the system specification that has been used in the past may induce an ambiguous understanding to the reader. In addition, for example, when the orderer and the contractor confirm the specifications or analyze the requirements, there is a problem that it is difficult to determine the omission of the specification or the validity of the description.

  In addition, for example, when a designer and a producer create a control program, there is a problem that it is difficult to check whether the conditions for each specification are satisfied or not. Furthermore, there has been a problem that equipment (equipment) may not be able to operate properly with the specifications described in the conventionally used system specifications.

  An object of the present invention is to provide an information control system and a method for creating control software that can clearly define and execute conditions that define the state of a device to be controlled. To do.

  In order to achieve the above object, the information control system introduces the idea of an object that is a target constituting the control target system and an actor that monitors the state of the object and commands a change of state to the object.

The management server (for example, the SI management server 100) that manages the control software of the system to be controlled, sets the object name of the object, the monitoring item of the object, and the setting value of the monitoring item for each actor that is a control element that monitors and controls the object. and a storage unit for storing the actor definition information that associates monitoring condition setting value (e.g., the storage unit 20) and, client terminal (for example, development PC 100A) When accepting the actor creation request from the actor definition of the actor Information is displayed on the display section of the client terminal in the form of a table with the monitoring items of the object as rows or columns and the setting values and monitoring conditions as columns or rows , and when registering the actor definition information related to the actor, Object name, monitoring item of object, setting value of monitoring item, and monitoring of setting value The term used in the condition is described in the form of a definition word, and when an actor registration request is received from a client terminal, a model creation unit (stores actor definition information related to the actor displayed on the display unit in the storage unit ( For example, it has a model creation unit 130) .

  According to the present invention, it is possible to clearly define and execute a condition that defines the state of a device to be controlled.

  Hereinafter, an embodiment of the present invention (hereinafter referred to as “the present embodiment”) will be described in detail with reference to the drawings. In addition, in each figure, about the same component or the same component, the same code | symbol is attached | subjected and those overlapping description is abbreviate | omitted.

  The information control system according to the present embodiment is not a method in which a program developer decodes a specification and creates a program based on a conventional ambiguous system specification. That is, instead of creating and executing a program based on a system specification, a programless development method based on a system definition is adopted. Therefore, it is important to model the controlled system.

  To model the system to be controlled, the "operator's work" and the "judgment criteria and operation procedure" used in the work are modeled, and the operation (control) such as "equipment value" and "operation plan". It is necessary to do what is necessary for performing. These are hereinafter referred to as “actors” and “objects”, respectively. Details will be described later.

  FIG. 1 is a block diagram showing the configuration of the information control system according to the present embodiment. The information control system S is a PC that monitors the control status of the SI management server 100 (management server), the development PC 100A (client terminal) that is a developer PC (Personal Computer), the real machine server 400, and the control target system 200. A monitoring PC 400 </ b> A and an operation plan PC 400 </ b> B that is a PC for an operation planner (control planner) of the control target system 200 are included. Each server and each PC are connected via a network 300. SI is an abbreviation for System Integrator.

  The SI management server 100 includes a processing unit 10 that performs information control processing, a storage unit 20 that stores data when performing information control processing, an input unit 31 that inputs data, an output unit 32 that outputs data, and a network The communication unit 33 is configured to communicate with the development PC 100 </ b> A, the real machine server 400, and the like via the 300.

  The storage unit 20 includes a RAM (Random Access Memory), a HDD (Hard disk drive) device, and the like. The processing unit 10 is realized by executing a program on the RAM or HDD by one or more CPUs (Central Processing Units). The input unit 31 is a device for inputting an instruction to a computer such as a keyboard and a mouse, and inputs an instruction for starting a program. The output unit 32 is a display or the like, and displays an execution status or an execution result of the processing by the SI management server 100. The communication unit 33 exchanges various data and commands with the real machine server 400 via the network 300. The control target system 200 includes, for example, an electric power system, a train operation management system, and a water and sewage management system.

  The processing unit 10 uses a model creation unit 130 that creates a control model of the control target system, a model validation unit 140 that validates the model created by the model creation unit 130, and a model confirmed by the model validation unit 140 using test data. An operation verification unit 150 that performs operation verification, and an execution module distribution unit 160 that distributes the execution module verified by the operation verification unit 150 to the real machine server 400.

  The model creation unit 130 of the processing unit 10 includes an actor setting unit 131, an object setting unit 132, an actor control setting unit 133, an object control setting unit 134, and a dictionary setting unit 135.

  The storage unit 20 includes an actor DB 21 for storing actor information (actor definition information, actor definition table), an object DB 22 for storing object information (object definition information, object definition table), and terms used for actors and objects. A dictionary DB 23 in which the definition of the actor and the object is set, a template DB 24 for storing a template (definition table) for setting actors and objects, a verification result in the model verification unit 140, test data in the case of verification in the operation verification unit 150, A verification unit DB 25 that stores verification results is stored. The actor definition table will be described later with reference to FIGS. The object definition table will be described later with reference to FIGS.

  The real machine server 400 has a processing unit (not shown) of the control target system 200 monitor the state change of the object of the control target system, and a control command to the object based on the control command of the monitoring function unit 410 A control function unit 420 that performs operation management, and an operation management function unit 430 that performs operation management of the control target system 200.

  The monitoring function unit 410 has a function of monitoring an object to be controlled based on the actor definition table and the object definition table distributed from the SI management server 100.

  The contents of the actor and the object, and the actor setting unit 131, the object setting unit 132, the actor control setting unit 133, and the object control setting unit 134 will be described with reference to FIG.

  FIG. 2 is an explanatory diagram showing the relationship between actors and objects. In this embodiment, an accident monitoring of an electric station of a power system will be described as an example. An electric station is a power plant, a substation, or the like. An object is necessary for business (control). In the case of an electric station, an object includes an electric station, a bus bar constituting the electric station, a relay, a circuit breaker, and the like. Also, the drawing pattern of the monitoring screen and the alarm for monitoring can be said to be objects. An actor refers to an operator's business or control function, and includes an instruction operation function, a screen monitoring function, and a response function when a state changes. In FIG. 2, as the actor, for example, there are a drawing pattern operation instruction, an electric station state correspondence, a bus state correspondence, a relay state correspondence, a breaker state correspondence, and the like. That is, a function required as a control target system is defined as an actor, and data used by the actor is defined as an object.

  Returning to FIG. 1, the actor setting unit 131 stores the defined actor definition table in the actor DB 21 that is set based on the definition table of actors in the template DB 24. Similarly, the object setting unit 132 is set based on the object definition table in the template DB 24 and stores the defined object definition table in the object DB 22.

  The actor control setting unit 133 is a part for setting the operation of the entire actor, sets a plurality of actors as an actor group for each function of the control target system 200, and sets an execution order of the actors, an object data capturing timing, and the like. . The actor control setting unit 13 sets a plurality of actor groups.

  The object control setting unit 134 is a part for setting the operation of the entire object, sets a plurality of objects as an object group for each function of the control target system, and controls the reflection of data between the same objects across the CPUs. Set. The object control setting unit 134 sets a plurality of object groups.

  The set actor group and object group are executed in the information control system S in accordance with rules defined for the actor control and the object control, respectively.

The information control system S is controlled by actors and objects, and features and specific methods will be described below.
(1) Separation of model logic and implementation cooperation ・ A range in which specifications are defined based on a model and an operating part that requires cooperation with surroundings are separated.
-The interface between model logic and implementation linkage is realized only via data. In other words, procedures related to implementation cooperation are hidden by objects.

(2) Ensuring the independence of functions and the unit that operates when running is the unit of the actor, and is one unit for mounting. Note that “running out” means that it can be executed independently in that unit and “operates when a condition is met”.
・ Actors operate when the conditions they should operate are met.
• Actors do not implement synchronous execution with other actors during actor execution. That is, the logic is not such that an execution request is made to another actor and a response from the requested actor is waited for.
・ Execution is performed by verifying whether or not all actors can be executed periodically and sequentially executing the actors that can be executed.

(3) There is no data or status for the next time in the unit where logic and data can be separated and run. For things that run well, and values and states that need to be continued to run, another implementation that manages the values and states is performed.
(4) Ensuring independence of data units.
・ Data is defined by object. For this reason, the object linked with the outside updates the data of the other party based on the actor or the data update from the outside.
-Data updates for linking with the outside of the object are fetched before the actor execution cycle and reflected after execution. A function group for realizing this data update is defined in the object.

Defines the behavior model of actors and objects that satisfy the above characteristics. That is,
(1) The actual data is reflected in the object data before execution based on the actor control. Executes a function group that is specified for an object and that is executed when it is referenced.
(2) The actors are activated sequentially according to the execution order of the actors specified by the actor control. In particular,
(2-1) The actor determines whether the condition to be executed by the actor is satisfied.
(2-2) An actor that satisfies the conditions is executed based on the described specifications. Specifically, necessary data is referenced from the object, and data is set in the object according to a predetermined rule.
(2-3) When the execution of all actors is completed, the value of the object whose value has been changed is reflected in the actual data. Executes a function group that is specified in the object and that is executed when it is updated.

Next, specific actor definition tables and object definition tables will be described.
3 to 6 are actor definition tables, and FIGS. 7 and 8 are object definition tables. In this embodiment, an actor and an object that define an accident monitoring function of an electric station will be described.

  FIG. 3 is a block diagram showing the accident monitoring function of the actor definition table. The actor definition table includes a name part, a control part, and an execution part. The name part is composed of a name for identifying an actor, and has an actor type, an actor name 1, and an actor name 2. The control unit is a part that defines a monitoring item (object name) for the action of the actor and a start condition that is a condition for enabling the condition described in the execution unit.

  The execution unit (actor execution unit) includes a result including a monitoring item and a set value, and a condition for obtaining the result. The condition represents the operator's know-how reflected in the system to be controlled and the constraint conditions for operation (control). The execution unit defines conditional expressions in tabular form for a plurality of monitoring items. Specifically, if the [operation state] of [current] in [electricity station] satisfies the condition of [accident occurrence] by the processing unit 10, the [drawing pattern] of the monitoring item is instructed to [blink]. Means that. In cases other than the above (if [Operational State] in [Electric Power Station] does not satisfy the condition of [Accident Occurrence]), the [Drawing Pattern] monitoring item is commanded to [Blink Stop]. Means that. Furthermore, in the example shown in FIG. 3, if the [operation state] of [current] of [electricity station] satisfies the condition of [accident occurrence], the [drawing pattern] of the monitoring item is instructed to [blink] [Alarm] is commanded to [Output], and [Man Machine Button] is commanded to [Flicker].

  In the tabular execution unit, each term enclosed by “[” and “]” represents a definition word on the information control system S. Hereinafter, each term surrounded by “[” and “]” is referred to as a “definition word”. This definition word is used as a definition word having a common meaning in other actors. This definition word is used to associate each actor.

  Also, as shown in FIG. 3, since the information control system S needs to consider a time element, a definition word such as [current] is used in the conditional expression. Since the time element is defined by other actors, the description is omitted.

  FIG. 4 is a configuration diagram showing an electric station state of the actor definition table. The actor definition table shown in FIG. 4 is the same as FIG. 3 and the description thereof is omitted, but the definition of OR conditions of a plurality of conditions is shown. Specifically, the monitoring item (object name) [Electric power station] is set to [Accident occurrence] in [Operation state] if a predetermined operation condition is satisfied. Predetermined operating conditions are those that [operating state] of [this time] for [belonging to electric station] and [bus] is [occurrence of accident], or [this] for [this time] for [belonging to electric station] and [railway] [Operating status] is [Accident occurred] condition, [Attached to electrical station] [Transformer] [Current] [Operating status] is [Accident occurred] condition, or [Attached to electrical station] [Power generation] This is a case where [Operating state] of [Current] of [Aircraft] satisfies the condition of [Accident occurrence]. Each [monitoring target] (for example, [belongs to an electric station] [bus]] is associated with the object definition table (equipment structure object) shown in FIG.

  FIG. 5 is a configuration diagram showing a bus accident state and a bus operating state of the actor definition table. The actor definition tables shown in FIGS. 5A and 5B are the same as those in FIG. 3 and will not be described. However, the conditions of the execution unit are AND conditions of a plurality of conditions. Specifically, as shown in FIG. 5A, the monitoring item (object name) [Bus] is a condition that [Accident monitoring status] of [Current] of [Bus] is [Monitoring], and If [Breaker State] of [Bus] satisfies the condition of [Trip], [Operating State] is set as [Accident Occurrence]. Similarly, [bus], which is the monitoring item (object name) shown in FIG. 5A, is a condition where [relay state] of [previous] of [bus] is [trip] and [current] of [bus] If [Relay status] of [] satisfies the condition of [Trip], [Accident monitoring status] is set to [Monitoring].

  Specifically, as shown in FIG. 5B, the monitoring item (object name) [bus] is [belongs to] and [relay] [previous] [state] is [connection]. [Relay status] is set to [Trip] if [Status] of [Current] of [Belonging] [Relay] is [Shutdown].

  FIG. 6 is a configuration diagram showing a relay state and a circuit breaker state of the actor definition table. The definition table shown in FIGS. 6A and 6B is a definition table that associates a signal bit (control signal) of an object that is one of the controlled systems with a “set value” of “monitor item”. It is. Specifically, as shown in FIG. 6A, [Relay], which is a monitoring item (object name), is set to [Connected] for [State] when the condition is “0” and “1”. Under the above conditions, [Status] is set to [Block]. Similarly, as shown in FIG. 6B, [breaker], which is the monitoring item (object name), is set to [connected] when [condition] is “0” and “1”. When the condition is met, [Status] is set to [Block]. The monitoring function unit 410 receives the control signal from the control target system 200 via the communication unit 33.

  FIG. 7 is a configuration diagram showing an electric station of the object definition table. The object definition table includes an object definition table showing the equipment state shown in FIG. 7A and an object definition table showing the equipment structure shown in FIG. 7B. The object definition table has a common part for defining the attributes of the object and a data item part managed by the object.

  The common part includes an object name that identifies an object, a higher class that designates the class (group) of the object, and a class designation that designates whether or not the object is handled as a class. A class means an identifier of a group when grouped as a plurality of object groups.

  The data item section includes a data item name that is a name for identifying the data, a data format that specifies the data format of the data to be stored, a structure format of the meaning of the array when there are multiple data, and a value that can be taken by the data (status Value) that specifies a value), an initial value, and the like.

  Specifically, as shown in FIG. 7 (a), [drawing pattern], [operation state], etc. are specified in the data item part of the equipment state of the electric station, as shown in FIG. 7 (b). The data item part of the electrical facility equipment structure includes [belongs to electrical station] [bus], [belongs to electrical station] [track], [belongs to electrical station] [transformer], [belongs to electrical station] [Generator] is specified.

  FIG. 8 is a configuration diagram showing a bus of the object definition table. As in FIG. 7, the object definition table includes an object definition table indicating the equipment state shown in FIG. 8A and an object definition table showing the equipment structure shown in FIG. 8B. Specifically, as shown in FIG. 8 (a), [bus state], [accident monitoring state], [relay state], and [breaker state] are specified in the data item part of the equipment state of the bus. As shown in FIG. 8B, [belonging to the bus] [relay] and [belonging to the bus] [breaker] are specified in the data item portion of the equipment structure of the bus.

Next, the processing flow will be described.
FIG. 9 is a flowchart showing processing for distributing an execution module from the SI management server to the real machine server. This will be described with reference to FIG. When the developer calls the model creation screen 50 (see FIGS. 10 and 11) on the development PC 100A, and the model creation unit 130 accepts the registration request, the definition of the entered actor, dictionary, and object is converted to the actor DB 21, It registers in object DB22 and dictionary DB23 (step S11).

  FIG. 10 is an explanatory diagram showing an example of an actor definition screen. The model creation screen 50a (50) includes a menu unit 51, a setting unit 52 for setting a definition table, a cancel button 53 for canceling an input input to the setting unit 52, a read button 54 for reading an already registered definition table, A registration button 55 for registering the registration content input to the setting unit 52 is provided. In the setting unit 52 shown in FIG. 10, the actor definition table is displayed in a table format with object monitoring items as rows or columns and setting values and monitoring conditions as columns or rows. FIG. 10 shows a state in the middle of setting the actor definition table. Specifically, it is a state in which up to [drawing pattern] of the monitoring item is input.

  The menu 51 includes a “model creation unit” for setting an actor definition table and an object definition table, a “model verification” for verifying a set (created) definition table, and an “operation verification” for verifying the operation of the set model. ”, A“ distribution unit ”that distributes execution modules to the real machine server 400, and a“ help ”menu that explains operation functions in model creation and the like. In the “model creation unit”, there are menus of “actor”, “object”, “actor control”, “object control”, “dictionary”, and a setting screen is displayed by clicking with a mouse or the like. Specifically, when the “actor” menu is clicked, the actor setting unit 131 reads the template of the actor definition table from the template DB 24 and displays it on the setting unit 52.

  Further, the “model verification” menu has a more detailed menu. Specifically, there are menus such as “execution”, “relation table display (bird's eye view)”, “relation table display (tree display)”, “inconsistency display”, and “inconsistency non-display”.

  Also, when reading an already registered actor definition table, the developer inputs the actor type, actor name 1, and monitoring item (object name) into the actor definition table template table displayed in the setting section 52, and then loads it. When the button 54 is clicked with a mouse or the like, the actor setting unit 131 searches the actor DB 21 using the actor type, actor name 1, and monitoring item (object name) as keys and displays them on the setting unit 52.

  FIG. 11 is an explanatory diagram illustrating an example of an object definition screen. Similar to FIG. 10, the model creation screen 50b (50) includes a menu unit 51, a setting unit 52 for setting a definition table, a cancel button 53 for canceling input input to the setting unit 52, and a definition table already registered. Read button 54 and a registration button 55 for registering the registration contents input to the setting unit 52. The setting unit 52 in FIG. 11 shows a state in the middle of setting the object definition table, and more specifically, a state in which [drawing pattern] of the monitoring item is input.

  When “object” is clicked with a mouse or the like in the “model creation section” of the menu section 51, a setting screen is displayed. The object setting unit 132 reads the template of the object definition table from the template DB 24 and displays it on the setting unit 52. In addition, when reading an already registered object definition table, when the developer inputs an object name and at least one data item name in the template table of the object definition table displayed in the setting unit 52, the object setting unit 132 The object DB 22 is searched using the object name and data item name as keys and displayed on the setting unit 52. When the object setting unit 132 searches a plurality of corresponding object definition tables, a definition table selection screen (not shown) different from the model creation screen 50 is displayed, and the developer may be instructed to select. .

  Returning to FIG. 9, after step S <b> 11, when “execution” in “model verification” in the menu section 51 of the model creation screen 50 is clicked with a mouse or the like, the model verification section 140 performs the model verification processing shown in FIG. 12. Thus, the model created by the model creation unit 130 is verified (step S12).

  FIG. 12 is a flowchart showing model verification processing. When the model verification unit 140 receives the actor type and the actor name from the setting unit 52 (step S41), the model verification unit 140 repeats steps S42 to S46 for the monitoring item (object name), the monitoring item, and the setting value. In step S43, a definition word group (term group) of conditions is extracted (step S43), and an actor that matches the extracted definition word group (term group) is extracted (step S44). Further, the model verification unit 140 extracts an object (step S45) that matches the extracted definition word group (term group). In addition, the definition word group (term group) of conditions is, for example, [electricity station] [operating state] [accident occurrence] shown in FIG.

  Then, the model verification unit 140 creates a related table (related information) (see FIGS. 13 and 14) (step S47), stores it in the verification unit DB 25, and displays the related table on the screen. In the related table, a part having a defect such as a loop (mismatch) is detected (step S48), and notification is made by changing the connection color of the display screen.

  As for the actors extracted in step S43, the extraction of actors and objects that match the condition definition word group may be repeated as in steps S41 to S46.

  Returning to FIG. 9, the developer determines whether or not there is a definition error (step S13). If there is a definition error (No in step S13), the developer returns to step S11. When there is no definition error (step S13, Yes), when “registration” in “model verification” of the menu unit 51 is clicked with a mouse or the like, the model verification unit 140 sends an actor to the verification unit DB 25 of the SI management server 14. Dictionary and object definitions are registered (step S14), and a document, source, and execution module are generated (step S15).

  When the developer clicks “execution” in “operation verification” in the menu section 51 with a mouse or the like, the operation verification section 150 performs operation verification on the model confirmed by the model verification section 140 using test data (step). S16). The operation verification unit 150 displays the operation verification result on an operation verification screen (not shown). The developer determines whether there is a defect (step S17). If there is a problem (No at Step S17), the process returns to Step S11. When there is no defect (step S17, Yes), when the developer clicks “execute” in the “distribution unit” of the menu unit 51 with a mouse or the like, the execution module distribution unit 160 is stored in the verification unit DB 25. The verified execution module is distributed to the real machine server 40 via the communication unit 33 (step S18), and the series of processes is terminated.

  FIG. 13 is a bird's-eye view (bird's-eye view) showing the association table. FIG. 13 shows a plurality of actor definition tables as bird's-eye views (bird's-eye views) from FIGS. 13 (a) to 13 (e). 13 (a) shows the accident monitoring function (see FIG. 3), FIG. 13 (b) shows the electric station state (see FIG. 4), and FIGS. 13 (c) and 13 (d) show the bus A state (refer FIG. 5, a bus-bar accident state, a bus-bar operation state) is shown, and 13 (e) shows a relay state (see FIG. 6). In FIG. 13, only the definition words related to a plurality of actors are described, and other descriptions may be omitted. Moreover, the relationship of a definition word is linked | related by the broken line or the continuous line.

  The definition word group of [electricity station] [operation state] [accident occurrence] shown in FIG. 13A is associated with FIG. 13B, and [bus] [operation state] shown in FIG. 13B. The definition word group of “accident occurrence” is associated with FIG. Further, [bus], [accident monitoring state], and [under monitoring] in FIG. 13C are associated in FIG. 13C.

  Similarly, [bus] [relay state] [trip] shown in FIG. 13 (c) is associated with FIG. 13 (d), and [relay] [state] [connection] shown in FIG. 13 (d) or , [Relay] [state] [blocking] are associated with FIG.

  At this time, the model verification unit 140, for example, [bus] [relay state] [trip] shown in FIG. 13C has [bus] [relay state] shown in FIG. ] Is determined as inconsistent association.

  FIG. 14 is a tree diagram showing an association table. FIG. 14 illustrates a case where a tree format is used as another method for displaying the related table. FIG. 14A shows the relationship among a plurality of actor definition tables. Specifically, [electricity station] (FIG. 3), which is the object name of the monitoring item, is associated with [electricity station] (FIG. 4), and [electricity station] (FIG. 4) is [bus] (FIG. 5). (A)), [track], [transformer], [generator], and [bus] (FIG. 5 (a)) are associated with [bus] (FIG. 5 (b)). Yes. Furthermore, [Bus] (FIG. 5 (b)) is associated with [Relay] (FIG. 6 (a)) and [Circuit breaker] (FIG. 6 (b)).

  FIG. 14B shows the relationship between the object name and the object definition table. Specifically, [electricity station], which is the object name of the monitoring item, is composed of a plurality of object definition tables (FIGS. 7A and 7B). [Bus] is composed of a plurality of object definition tables (FIGS. 8A and 8B).

  FIG. 15 is a flowchart showing processing of the monitoring function. The monitoring function unit 410 of the real machine server 400 monitors the state of the actor. As shown in FIG. 2, even if a plurality of actors are registered as an actor group, each actor is basically independent and is a process of “operating when a condition is met”. FIG. 15 shows actor processing.

  The monitoring function unit 410 monitors the actor (step S1). The actor monitoring is to monitor whether or not the condition item of the actor has changed. If the state does not change (step S2, No), the process returns to step S1 to continue monitoring the actor. When the state has changed (step S2, Yes), it is determined whether or not the conditions for the actor are satisfied (step S3). If the actor condition is not satisfied (step S3, No), the process returns to step S1 to continue monitoring the actor. If the actor condition is satisfied (step S3, Yes), the set value of the monitoring item of the target object is set (step S4). Thereafter, the process returns to step S1 and continues.

  In the present embodiment, an example of the power system has been described for the actor definition table and the object definition table, but the present invention is not limited to this. Any control target system that can be defined as an actor and an object can be used for other information control systems such as a train operation management system and a water and sewage management system.

  According to the present embodiment, information that can be clearly defined and executed in the condition confirmation and requirement analysis between the orderer and the contractor without using an ambiguous document and that defines the condition of the device to be controlled. A control system S can be provided.

  According to the present embodiment, by dividing into an actor definition table, an object definition table, and a dictionary definition table, rows and columns can be suppressed without increasing each definition table. Further, in the case of a function change or the like, it can be dealt with by changing individual actor definition tables, object definition tables, and dictionary definition tables. Further, when one actor is executed, the relationship between the actors, the objects, and the dictionary can be easily grasped by displaying them in a tree diagram or a bird's-eye view (bird's-eye view), for example. Furthermore, the definition of an incomplete actor, object, or dictionary can be extracted by detecting inconsistency in model verification.

According to this embodiment, it also has the following effects.
(1) Since an actor that can be executed independently is adopted, it is possible to quickly respond to a function change or partial correction of an object.
(2) Even if the configuration of the device of the controlled system changes, the degree of influence is small.
(3) The impact on future equipment increases and function increases is small.
(4) Unaffected by differences in hardware, OS (Operation System), and middleware.
(5) The test environment system can be easily linked to the communication unit.
(6) A partial test of the actor group can be easily performed.
(7) The response and reliability of the actor group can be verified and controlled.

It is a block diagram which shows the structure of the information control system which concerns on this embodiment. It is explanatory drawing which shows the relationship between an actor and an object. It is a block diagram which shows the accident monitoring function of an actor definition table. It is a block diagram which shows the electric station state of an actor definition table | surface. It is a block diagram which shows the bus-bar accident state and bus-bar operation state of an actor definition table. It is a block diagram which shows the relay state and circuit breaker state of an actor definition table. It is a block diagram which shows the electric station of an object definition table. It is a block diagram which shows the bus-line of an object definition table. It is a flowchart which shows the process of registration of distribution of an execution module from an SI management server to a real machine server. It is explanatory drawing which shows the example definition screen of an actor. It is explanatory drawing which shows the example of an object definition screen. It is a flowchart which shows the process of model verification. It is a bird's-eye view (bird's-eye view) showing a related table. It is a tree figure which shows a related table. It is a flowchart which shows the process of a monitoring function.

Explanation of symbols

10 processing unit 20 storage unit 21 actor DB
22 Object DB
23 Dictionary DB
24 Template DB
25 Verification unit DB
31 Input unit 32 Output unit 33 Communication unit 100 SI management server (management server)
100A development PC (client terminal)
DESCRIPTION OF SYMBOLS 130 Model creation part 131 Actor setting part 132 Object setting part 133 Actor control setting part 134 Object control setting part 135 Dictionary setting part 140 Model verification part 150 Operation | movement verification part 160 Execution module distribution part 200 Control target system 300 Network 400 Real machine server 410 Monitoring Function part 420 Control function part 430 Operation management function part S Information control system

Claims (6)

And a management server for managing control software of the control systems, information control comprising an object as an object constituting the controlled object system, and actors for monitoring the state of the object performing the control command to the object A system,
The management server
Storage for storing actor definition information that associates an object name of the object, a monitoring item of the object, a setting value of the monitoring item, and a monitoring condition of the setting value for each actor that is a control element that monitors and controls the object And
When receiving the creation request of the actor from a client terminal, the actor definition information according to the actor, a row or column of the monitored item of the object, in tabular form the set value and the monitoring condition as a column or row, the client Term displayed on the display unit of the terminal and used for the object name of the object, the monitoring item of the object, the setting value of the monitoring item, and the monitoring condition of the setting value when registering the actor definition information related to the actor but with those described in the definition language format, it accepts the registration request of the actor from the client terminal, modeling storing before term memory unit actors definition information relating to the actor that is displayed on the display unit information control system characterized by having a part. Before Symbol management server, further,
When receiving the model validation request from the previous SL client terminal, before Symbol monitoring conditions, and the term group to extract a plurality of terms, and extract the actors that matches before Symbol term group, Ru sequentially associate before Symbol extracted actor The information control system according to claim 1, further comprising a model verification unit that creates related information and stores the related information in the storage unit . The information control system according to claim 2, wherein the model verification unit displays the related information on the display unit of the client terminal as an overhead view or a tree diagram. And a management server for managing the control software of control systems, information comprising an object as an object constituting the controlled object system, and actors for monitoring the state of the object performing the control command to the object a control software on how to create a control system,
The management server has a storage unit and a model creation unit,
In the storage unit, for each actor is a control element for monitoring and controlling the pre-Symbol object, the object name of the object, monitored item of the object, the set value of the monitored item, and associating a monitoring condition of the set value Actor definition information is stored,
When the model creation unit receives the actor creation request from the client terminal, the model creation unit displays the actor definition information related to the actor as the row or column of the monitoring item of the object, and the setting value and the monitoring condition as a column or row. Displayed on the display unit of the client terminal in the format, and when registering the actor definition information related to the actor, the object name of the object, the monitoring item of the object, the setting value of the monitoring item, and the setting value of the setting value Terms used for monitoring conditions are described in the form of definition words, and when the registration request for the actor is received from the client terminal , the actor definition information related to the actor displayed on the display unit is stored in the storage unit. A method of creating control software characterized by storing. The management server further comprises a model verifying unit,
Before SL model verification unit,
When receiving the model verification request from the client terminal, associated before Symbol monitoring conditions, and the term group to extract a plurality of terms, and extract the actors that matches before Symbol term group, Ru sequentially associate before Symbol extracted actor Information is created and memorize | stored in the said memory | storage part . The creation method of the control software of Claim 4 characterized by the above-mentioned. The method of creating control software according to claim 5 , wherein the model verification unit displays the related information on the display unit of the client terminal as an overhead view or a tree diagram.

Images