JPH09146808A - Management device for constant value for control - Google Patents

Abstract

PROBLEM TO BE SOLVED: To prevent occurrence of an abnormal operation due to a change error at the time of changing a constant by providing an external interface part, and when the registration instruction or change instruction of the constant and the definition data of the constant are inputted from the outside, invalidating the registration request or change request when an input form is abnormal and performing output as guidance output and the executed result of a function to the outside. SOLUTION: When the registration instruction or change instruction of the constant and the definition data of the constant are inputted from the outside, the external interface part 4 decodes the inputted definition data corresponding to an input rule and then, when the input form of the definition data stipulated by the conditional data is normal, delivers the definition data to an access control part 3 as the new registration data of the constant or the change data of the constant. On the other hand, when the input form is abnormal, the registration request or the change request is invalidated and the output as the guidance output and the executed result of the function is performed to the outside.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a control constant value management apparatus suitable for application to a control system such as a process control system that requires a large number of control constants.

[0002]

2. Description of the Related Art In a process control system, various physical control values such as equipment physical constants, science constants, modeling constants, resource definition constants, calculation constants and set values are managed in a table in a storage device in the control device. . Conventionally, maintenance and management of these constant values for control have been performed by a human memory or a ledger.

[0003]

However, in general, the number of these control constants is several hundred items of data x
Since it is a large number of thousands of records or more, the work required for its initial setting and maintenance is not easy, and in particular, work mistakes such as omission of constants due to constant changes during addition / correction work and deletion of constants due to erroneous operation are possible. It happened. further,
Because I ran the system without noticing the work mistake,
The system may stop or operate abnormally due to an error in setting constants. That is, for example, when a constant A is changed, another constant B correlated with the constant A should also be changed, but if the work of changing the constant B is missed, the process control system using those constants operates abnormally. It may cause an accident such as.

The present invention has been made in view of the above-mentioned problems, and an object of the present invention is to prevent an abnormal operation from occurring due to a mistake in changing a constant in a process control system of this type. The object is to provide a control constant value management device capable of controlling.

[0005]

The invention according to claim 1 of the present application is a constant functioning as a file for storing a data group corresponding to one or more definition items constituting a constant value for control. A numerical value storage unit, a key management unit that functions as a file for storing a data group corresponding to one or more definition items that form the key information for managing the control constant value, and the constant value storage The constant value stored in the section is registered via the key management section,
Man-machine interface function between an access control unit that executes access control when changing, deleting, or referencing, and an output device that outputs the data stored in the constant value storage unit, stored in the constant value storage unit Input / output function with an external storage device that stores data for storing or stored data, or an external interface unit that executes a function interface function that links with an external program. The range of constant values such as the upper and lower limit values of the definition data that make up the control constant value and the condition data indicating the possible values are stored.The external interface unit externally issues a constant registration instruction or change instruction and a constant When the definition data and is input, after the input definition data is decoded according to the input rule, the definition specified by the condition data If the input format of chromatography data is normal,
While passing the definition data to the access control unit as constant new registration data or constant change data,
If the input format is abnormal, the registration request or change request is invalidated, and the guidance output or the function execution result is output to the outside.

The invention according to claim 2 of this application is a constant value storage unit which functions as a file for storing a data group corresponding to one or more definition items constituting a control constant value, and A key management unit that functions as a file for storing a data group corresponding to one or more definition items that constitute key information for managing a constant value for control, and the constant value storage unit. An access control unit that performs access control when registering, changing, deleting, or referencing a constant value via the key management unit, and an output device that outputs the data stored in the constant value storage unit And man-machine interface function, data to be stored in the constant value storage unit or an input / output function with an external storage device that stores the stored data, or an external program and link And an external interface unit that executes a function interface function, and the constant value storage unit stores class data indicating a target higher constant when the constant depends on another constant, When the definition data passed from the external interface unit as constant change data or constant deletion data has a class designation defined by the class data, the access control unit has registered the constant of the target class. Is checked, and if it is not registered, the fact is notified to the external interface.

The invention according to claim 3 of this application is a constant value storage unit that functions as a file for storing a data group corresponding to one or more definition items that make up a control constant value; A key management unit that functions as a file for storing a data group corresponding to one or more definition items that constitute key information for managing a constant value for control, and the constant value storage unit. An access control unit that performs access control when registering, changing, deleting, or referencing a constant value via the key management unit, and an output device that outputs the data stored in the constant value storage unit And man-machine interface function, data to be stored in the constant value storage unit or an input / output function with an external storage device that stores the stored data, or an external program and link And an external interface unit that executes a function interface function for storing a key value that is representative of each constituent unit with a plurality of control constants associated with each other as one constituent unit. The access control unit registers, changes, deletes constants,
Alternatively, when the key value attached to the definition data passed from the external interface unit as reference data is registered in the key management unit, for a plurality of constant values specified by the key value, The feature is that the constants are registered, changed, deleted, or referred to in a batch.

The invention according to claim 4 of this application is a constant value storage unit which functions as a file for storing a data group corresponding to one or more definition items constituting a control constant value; A key management unit that functions as a file for storing a data group corresponding to one or more definition items that constitute key information for managing a constant value for control, and the constant value storage unit. An access control unit that executes access control when registering, changing, deleting, or referencing a constant value via the key management unit, and a source code of a constant registered in the constant storage unit. Man-machine interface function between a source code generation unit that generates according to a programming language and an output device that outputs the data stored in the constant value storage unit, the constant value storage Input or output function and external storage device for storing data or the stored data to be stored in,
Alternatively, the external interface unit executes a function interface function linked with an external program, and the external interface unit specifies a language to be used and a target constant to the source code generation unit when a constant source code generation request is generated. Then, the source code generation unit requests the access control unit to refer to the specified constant, extracts the structure of the constant and the constant value, and determines the symbol name, type declaration, and definition according to the language used. A source code declaring a numerical value is generated and notified to the external interface section.

The invention according to claim 5 of this application is a constant value storage unit which functions as a file for storing a data group corresponding to one or more definition items constituting a control constant value, and A key management unit that functions as a file for storing a data group corresponding to one or more definition items that constitute key information for managing a constant value for control, and the constant value storage unit. When a constant value is registered, changed, or deleted through the key management unit, an access control unit that performs access control when registering, changing, deleting, or referring to the constant value is performed. Man-machine interface function between the version management unit that records time and date of operation, operation reason, constant value before change, etc. in time series and the output device that outputs the data stored in the constant value storage unit An external interface unit for executing an input / output function with an external storage device for storing data to be stored in the constant value storage unit or the stored data, or an external interface unit for executing a function interface function linked with an external program, When the constant change history reference instruction and the reference constant key value are input from the outside, the interface passes the input reference constant key value to the version management unit as constant change history reference data, and performs the version management. The unit is characterized in that the change history information for the input constant key value is read and the change history information and the result thereof are notified to the external interface.

The invention according to claim 6 of this application is a constant value storage unit that functions as a file for storing a data group corresponding to one or more definition items that make up a control constant value; A key management unit that functions as a file for storing a data group corresponding to one or more definition items that constitute key information for managing a constant value for control, and the constant value storage unit. When a constant value is registered, changed, or deleted through the key management unit, an access control unit that performs access control when registering, changing, deleting, or referring to the constant value is performed. Man-machine interface function between the version management unit that records time and date of operation, operation reason, constant value before change, etc. in time series and the output device that outputs the data stored in the constant value storage unit An external interface unit for executing an input / output function with an external storage device for storing data to be stored in the constant value storage unit or the stored data, or an external interface unit for executing a function interface function linked with an external program, When the constant restoration instruction, the restoration constant key value, and the modification date and time are input from the outside, the interface unit passes the input restoration constant key value to the version management unit as constant restoration data, and performs the version management. Section reads the change history information for the entered constant key value, specifies the constant value before the change of the change history information, notifies the access control section of the change of the constant, and at the same time, the result Is notified to the external interface unit.

The invention according to claim 7 of this application functions as a file for compressing and storing and decompressing and reading a data group corresponding to one or two or more definition items constituting a constant value for control. A constant value compression storage unit, a key management unit functioning as a file for storing a data group corresponding to one or more definition items forming key information for managing the control constant value, and A constant value stored in the constant value storage unit is registered, changed, deleted, or accessed through the key management unit, and an access control unit that executes access control, and constant registration, change, or Stored in the constant value storage unit and a version management unit for time-sequentially compressing and recording and decompressing and reading the date and time when the deletion operation is performed, the operation reason, and the constant value before change Done Man-machine interface function with an output device that outputs existing data, an input / output function with an external storage device that stores the data to be stored in the constant value storage unit or the stored data, or a function that links with an external program And an external interface unit that executes an interface function.

[0012]

DETAILED DESCRIPTION OF THE INVENTION Some embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

FIG. 1 is a block diagram showing the configuration of the first embodiment of the present invention. In the figure, the constant value storage unit 1
Is a file that stores constant values. The constant value storage unit 1 stores data structure / type, size, constant name, key value, constant value, unit, upper and lower limit values, and the like.

The key management unit 2 is a file that stores key information for managing constant values. This key management unit 2
The key structure / type, size, key name, key value, information classification (class), and the like are stored in.

The access control unit 3 executes access control when registering, referring to, updating, and deleting the constant value stored in the constant value storage unit 1 via the key management unit 2.

The external interface 4 has a CRT 5, a man-machine interface function with the printer 6, a floppy disk 7, an input / output function with an external storage medium such as a magnetic tape or an optical disk (not shown), and an external program 8.
It executes the function interface function linked with.

In the first embodiment, in the management of constants, the functions of registering, changing, deleting and referring to constants are provided. Hereinafter, the operation for realizing each function will be described in detail with reference to FIGS.

<Registration Function of Constant Value> A constant is a data group composed of one or a plurality of items. The following items are defined when a constant is registered. (A) Data type: This includes numeric values, bit patterns,
There are character strings, etc., and the size is variable according to the type. (B) Structure definition showing the arrangement of data that constitutes a constant: This includes the symbol name of the data. (C) a key value representing a constant (primary key), a plurality of key values (subkeys) for searching a constant, a structure and type of the key value,
Character string data indicating each key name (d) Constant value: When the constant is composed of a plurality of data, the value for each data is included. (E) Conditional data indicating a range of constant values such as upper and lower limit values of numerical values and possible values: This also includes units. (F) Plural class data indicating information division of constants: Here, the class indicates a target upper (parent) constant when the constant depends on another constant. An example of class definition is shown in FIG. In the example shown in FIG. 2, the setting value f1 defines the function e1 as an upper class, and the function e1 is the equipment a.
1 is defined as an upper class.

The flowcharts of FIGS. 3 and 4 are as follows.
The processing of the external interface 4 for realizing the constant value registration function and the processing of the access control unit 3 are shown.

First, as shown in FIG. 3, the external interface 4 uses a man-machine interface function, an input / output function with a storage medium, and a function interface function to externally generate a constant new registration instruction and a constant definition data group. Input (step 301). What definition data each input data means is defined by the field specifications of the screen,
The input rule is determined by the grammar of the command language and the parameter specifications of the function.

Next, the external interface 4 decodes the input definition data according to the input rule (step 302), and then inputs the definition data in the input format (data structure / type,
If the size, the range of constant values, etc.) are normal (YES in step 303), the data is transferred to the access control unit 3 as constant new registration data (step 304). If the input format is abnormal (NO in step 303), the registration request is invalidated (step 306), and output as guidance output or function execution result to the outside (step 307).

Next, as shown in FIG. 4, the access control unit 3 extracts the primary key value from the input definition data (step 321), and confirms that the same key value is not registered in the key management unit 2. Check (step 32)
2). If the key value is not registered (NO in step 322),
The definition data group is registered in the constant value storage unit 1 (step 32
5) The key management information such as the key value is registered in the key management unit 2 (step 326). Further, when the class is designated (YES in step 327), it is checked whether or not the constant of the target class has been registered (step 328). If it is not registered (NO in step 328), the effect is indicated by the external interface 4
(Step 329). If the registration is completed normally (YES in step 330), the fact is notified to the external interface 4 (step 331). On the contrary,
If the same key value has already been registered (YES in step 322), the access control unit 3 invalidates the constant registration request (step 323) and notifies the external interface 4 of an error (step 324).

Next, the external interface 4 outputs the registration result notified from the access control unit 3 to the outside as guidance output or function execution result (step 305).

<Constant Change Function> The flowcharts of FIGS. 5 and 6 show the processing of the external interface 4 and the processing of the access control unit 3 for realizing the constant value change function, respectively. As shown in FIG. 5, first, the external interface 4 inputs a constant change instruction and a constant change data group from the outside by a man-machine interface function, a storage medium input / output function, and a function interface function (step 401). An input rule is determined by the definition of the definition data for each input data according to the screen field specifications, the command language grammar and the function parameter specifications. Next, the external interface 4 decodes the input change data according to the input rule (step 402), and if the input format of the change data (data structure / type, size, range of constant value, etc.) is normal (step 402). 403YES), and transfers this as constant change data to the access control unit 3 (step 4).
04). If the input format is abnormal (NO in step 403),
The registration request is invalidated (step 405) and output as guidance output or function execution result to the outside (step 4).
06).

Next, as shown in FIG. 6, the access control unit 3 extracts the primary key value from the input definition data (step 421), and confirms that the same key value is registered in the key management unit 2. Check (Step 42)
2). If the key value is registered (YES in step 422)
), And shifts to registration data change processing (step 42).
3).

As shown in FIG. 7, when the registration data change processing is started, the registration data is read from the constant value storage unit 1 and replaced with the change data (step 510), and the changed constant data is converted into a constant value. It is re-registered in the storage unit 1 (step 511). However, if there is an instruction to change the primary key value (YES in step 501), the change request is invalidated (step 502), and an error is notified to the external interface 4 (step 503). If the key management information other than the primary key value is changed (YES in step 504), the key management information is read from the key management unit 2 and replaced with the changed data (step 505), and the changed key management information is key-managed. Register in section 2 (step 506). Further, when the class is designated (YES in step 507), it is checked whether the constant of the target class has been registered (step 508). If it is not registered (NO in step 508), the fact is notified to the external interface 4 (step 509). When the change is completed normally, the fact is notified to the external interface 4 (step 512). On the other hand, returning to FIG. 6, if the change target key value is not registered (step 422 NO), the access control unit 3 invalidates the constant change request (step 426) and notifies the external interface 4 of an error ( Step 427).

Next, the access control unit 3 searches for a constant that defines the changed constant (denoted as A) as a parent class (step 424). If there is a constant (B) defined as the parent class (step 4)
24YES), and notifies all applicable constant names (B) to the external interface 4 (step 425). further,
It is searched whether there is a constant that defines the constant (B) as a parent class (step 424). If there is a constant (C) defined as the parent class (step 424YE)
S), and notifies all applicable constant names (C) to the external interface 4 (step 425). This will be repeated until there are no more constants of interest (step 4).
24 NO).

Next, the external interface 4 outputs the change result notified from the access control section 3 to the outside as guidance output or function execution result (step 40).
7). Further, if there are child constants (B, C ...) That define the changed constant (A) as a parent class, an inquiry is made as to whether or not the child constant needs to be changed (step 408).

<Constant Delete Function> The flowcharts of FIGS. 8 and 9 show the process of the external interface 4 and the process of the access control unit 3 which realize the constant value delete function, respectively.

As shown in FIG. 8, first, the external interface 4 inputs a constant deletion instruction and a deletion constant key value from the outside by a man-machine interface function, a storage medium input / output function, and a function interface function. (Step 601). The external interface 4 passes the input key value of the deletion constant to the access control unit 3 as deletion data of the constant (step 603).

Next, as shown in FIG. 9, the access control unit 3 takes out the main key value of the input constant (step 621) and checks that the same key value is registered in the key management unit 2. (Step 622). If the key value is registered (YES in step 622), the registered data in the constant value storage unit 1 and the key management unit 2 is deleted (step 623). If the deletion is completed normally, the fact is notified to the external interface 4 (step 624). On the other hand, if the key value to be deleted is not registered (NO in step 622), the access control unit 3 invalidates the constant deletion request (step 627) and notifies the external interface 4 of an error (step 628).

Next, the access control unit 3 searches for a constant that defines the deleted constant (denoted as A) as a parent class (step 625). If there is a constant (B) defined as the parent class (step 6)
25YES), and notifies all applicable constant names (B) to the external interface 4 (step 626). further,
It is searched whether or not there is a constant defining the constant (B) as a parent class (step 625). If there is a constant (C) defined as the parent class (step 625YE)
S), and notifies all applicable constant names (C) to the external interface 4 (step 626). This is repeated until there is no target constant (NO in step 625).

Next, the external interface 4 outputs the deletion result notified from the access control unit 3 to the outside as guidance output or function execution result (step 60).
3). Furthermore, when there is a child constant (BC ...) Defining the deleted constant (A) as a parent class,
An inquiry is made as to whether or not the child constant needs to be deleted or changed (step 604).

<Constant Reference Function> The flowcharts in FIGS. 10 and 11 show the processing of the external interface 4 and the processing of the access control unit 3 which realize the constant value reference function, respectively.

As shown in FIG. 10, first, the external interface 4 has a man-machine interface function, an input / output function with a storage medium, and a function interface function.
A constant reference instruction and a reference constant key value are input from the outside (step 701). The external interface 4 transfers the input key value of the reference constant to the access control unit 3 as constant reference data (step 702).

Next, as shown in FIG. 11, the access control unit 3 takes out the key value of the input constant (step 721) and checks that the same key value is registered in the key management unit 2. (Step 722). If the key value is registered (YES in step 722), the registration data in the constant value storage unit 1 and the key management unit 2 is read (step 723), and the registration data and the result are notified to the external interface 4 (step 724). On the other hand, if the reference target key value is not registered (NO in step 722), the access control unit 3 invalidates the constant reference request (step 727) and notifies the external interface 4 of an error (step 728).

Next, the access control unit 3 searches for a constant that defines the referenced constant (denoted as A) as a parent class (step 725). If there is a constant (B) defined as the parent class (step 7)
25YES), and notifies all applicable constant names (B) to the external interface 4 (step 726). further,
It is searched for a constant that defines the constant (B) as a parent class (step 725). If there is a constant (C) defined as the parent class (step 725YE)
S), and notifies all applicable constant names (C) to the external interface 4 (step 726). This will be repeated until there are no more constants of interest (step 7).
25 NO).

Next, the external interface 4 outputs the reference result notified from the access control section 3 to the outside as guidance output or function execution result (step 70).
3). For the relationship information of the class, a display format of the relationship status such as a table format or a tree structure format can be set and referenced. Further, when there are child constants (B, C, ...) Which define the referenced constant (A) as a parent class, an inquiry is made as to whether or not the child constant needs to be referenced (step 704).

According to the first embodiment, the following effects can be expected. (1) It is possible to set the range of constant values when registering or changing constants, and it is possible to prevent input errors when changing constants. (2) When a constant is changed, it has a function to check the necessity of changing other constants that set the relationship with the constant by specifying the class, and when it is necessary to maintain consistency between constants It is possible to prevent change mistakes. (3) When a constant is deleted, it has a function to check the necessity of changing other constants that set the relationship with the constant by specifying the class, and it is necessary to maintain consistency between constants. It is possible to prevent deletion mistakes. (4) A large number of constants can be divided and registered gradually in a hierarchical or stepwise manner by defining the structure of constants and specifying the class. Further, it becomes possible to display and change the constants in divided units, which facilitates maintenance and management of the constants.

Next, a modification of the above-described first embodiment will be described with reference to FIG. The feature of this modification is that
A source code generator 9 is newly provided in the configuration of the first embodiment shown in FIG. 1 to enable generation of constant source code. Source code is C language or FORTRAN
It is used as an INCLUDE declaration in a programming language such as a language.

As shown in FIG. 12, the device shown in this modification has a constant value storage unit 1, a key management unit 2, an access control unit 3, an external interface 4 and a new unit, which have the same contents as in FIG. And a source code generator 9 provided in the. The source code generation unit 9 generates a source code of a registered constant according to a target programming language.

Next, the operation of this modification will be described. In this modified example as well, as in the embodiment of FIG. 1, functions for registering, changing, deleting, and referring to constants are provided in constant management.

When a constant source code generation request is generated, the external interface 4 notifies the source code generation section 9 of the source code generation by designating the language to be used and the target constant. The source code generation unit 9 requests the access control unit 3 to refer to the specified constant and extracts the structure of the constant and the constant value. Then, the source code in which the symbol name, the type declaration, and the constant value are declared according to the language used is generated and notified to the external interface 4. The external interface 4 outputs the notified source code to an external storage device such as a floppy disk, a display device, a printer, or the like.

According to this modification, the following effects can be expected. There are two methods for referring to the constant. The first point is a method that is dynamically referred to during use.
The second point is a method in which the source code is generated in advance by an INCLUDE declaration statement or the like and is referred to during the language processing of the program. The first method is suitable for a constant reference method in which the value does not need to be changed even if the constant is changed and the value is easily changed. The second method requires language processing of the program again when the constant is changed, but since the constant value can be referred to at high speed, it is suitable for referring to a constant whose frequency of change is low. In this way, by providing a plurality of constant reference means, the applicable range of the present device can be expanded.

Next, FIG. 13 shows the configuration of the second embodiment of the present invention. In the figure, the same components as those of the first embodiment shown in FIG. 1 are designated by the same reference numerals and the description thereof will be omitted.

In FIG. 13, the version management unit 10
Is for recording the date and time when a constant is registered, changed or deleted, the operation reason, the constant value before the change, and the like.

Next, the operation of the second embodiment will be described with reference to FIG.
~ It demonstrates with reference to the flowchart of FIG. In the second embodiment, in addition to the constant registration, change, deletion and reference functions of the first embodiment, a change history reference function and a constant value restoration function are newly provided.

<Registration Function of Constant> A constant is a data group composed of one or a plurality of items. The following items are defined when a constant is registered. (A) Data type: This includes numeric values, bit patterns,
There are character strings, etc., and the size is variable according to the type. (B) Structure definition showing the arrangement of data that constitutes a constant: This includes the symbol name of the data. (C) a key value representing a constant (primary key), a plurality of key values (subkeys) for searching a constant, a structure and type of the key value,
Character string data indicating each key name (d) Constant value: When the constant is composed of a plurality of data, the value for each data is included. (E) Conditional data indicating a range of constant values such as upper and lower limit values of numerical values and possible values: This also includes units. (F) Plural class data indicating information division of constants: Here, the class indicates a target upper (parent) constant when the constant depends on another constant. An example of class definition is shown in FIG. In the example shown in FIG. 2, the setting value f1 defines the function e1 as an upper class, and the function e1 is the equipment a.
1 is defined as an upper class.

The flowcharts of FIGS. 14, 15 and 16 show the processing of the external interface 4 for realizing the constant value registration function, the processing of the access control section 3 and the processing of the version management section 10, respectively.

As shown in FIG. 14, first, the external interface 4 has a man-machine interface function, an input / output function with a storage medium, and a function interface function.
A new constant registration instruction and a constant definition data group are input from the outside (step 1001). The definition of input data is determined by the field specifications of the screen, the grammar of the command language, the parameter specifications of the functions, and the like.

Next, the external interface 4 decodes the input definition data in accordance with the input rule (step 1002) and then inputs the definition data in the input format (data structure.
If the type, size, constant value range, etc.) are normal (YES in step 1003), the data is transferred to the access control unit 3 as constant new registration data (step 1004). If the input format is abnormal (NO in step 1003), the registration request is invalidated (step 1005) and output as guidance output or function execution result to the outside (step 100).
6).

Next, as shown in FIG. 15, the access control unit 3 extracts the primary key value from the input definition data (step 1021), and confirms that the same key value is not registered in the key management unit 2. Check (Step 1
022). If the key value is not registered (step 1022)
No), the definition data group is registered in the constant value storage unit 1 (step 1023), and the key management information such as the key value is registered in the key management unit 2 (step 1024). Further, if the class is designated (step 1025 YES), it is checked whether the constant of the target class has been registered (step 102).
6). If not registered (step 1026 NO), the fact is notified to the external interface 4 (step 102).
7). When the registration is completed normally, the fact is notified to the external interface 4 (step 1029). On the other hand, if the same key value has already been registered (YES in step 1022), the access control unit 3 invalidates the constant registration request (step 1031) and notifies the external interface 4 of an error (step 1032).

Next, the access control unit 3 notifies the version management unit 10 to record the change history information such as the operation date and time, the operation reason, the key value of the target constant, and the registration reason (step 1030).

Then, as shown in FIG. 16, the version management unit 10 records the notified operation date / time, operation reason, key value of the target constant, and registration reason in time series in a storage device such as a magnetic disk ( Step 1041).

Next, the external interface 4 outputs the registration result notified from the access control unit 3 to the outside as guidance output or function execution result (step 1007).

<Constant Change Function> The flowcharts of FIGS. 17, 18 and 19 show the processing of the external interface 4, the access control section 3, and the version management section 10 for realizing the constant value change function. Are shown respectively.

As shown in FIG. 17, first, the external interface 4 has a man-machine interface function, an input / output function with a storage medium, and a function interface function.
A constant change instruction and a constant change data group are input from the outside (step 1101). An input rule is determined by the definition of the definition data for each input data according to the screen field specifications, the command language grammar and the function parameter specifications. Next, the external interface 4 decodes the input change data according to the input rule (step 1102), and if the change data input format (data structure / type, size, constant value range, etc.) is normal (step 1102). 1103 YES), and this is transferred to the access control unit 3 as constant change data (step 1104). If the input format is abnormal (NO in step 1103), the registration request is invalidated (step 110).
5) The guidance output or the function execution result is output to the outside (step 1106).

Next, as shown in FIG. 18, the access control unit 3 extracts the primary key value from the input definition data (step 1121), and confirms that the same key value is registered in the key management unit 2. Check (Step 11)
22). If the key value is registered (step 1122)
YES), shift to registration data change processing (step 1)
123).

As shown in FIG. 20, in this registration data changing process, the registration data is read from the constant value storage unit 1 and replaced with the change data (step 1210), and the changed constant data is stored in the constant value storage unit 1. Re-register (step 1211). However, if there is an instruction to change the primary key value (YES in step 1201), the change request is invalidated (step 1202), and an error is notified to the external interface 4 (step 1203). When the key management information other than the primary key value is changed (YES in step 1204), the key management information is read from the key management unit 2 and replaced with the changed data (step 1205), and the changed key management information is key-managed. Register in copy 2 (step 1206). Furthermore, when the class is designated (step 1207 YES)
), It is checked whether the constant of the target class has been registered (step 1208). If not registered (step 1208N
O), and notifies it to the external interface 4 (step 1209). If the change is completed normally, the fact is notified to the external interface 4 (step 121).
2). On the other hand, returning to FIG. 18, the access control unit 3 determines that the change target key value is not registered (step 112).
2NO), the constant change request is invalidated (step 112).
7) The error is notified to the external interface 4 (step 1128).

Next, the access control unit 3 notifies the version management unit 10 to record change history information such as the operation date and time, the operation reason, the key value of the target constant, and the constant value before the change (step 1124). ).

As shown in FIG. 19, the version management unit 10 records the operation date and time, the operation reason, the key value of the target constant, and the constant value before the change, which have been notified, in a storage device such as a magnetic disk in time series. (Step 1141).

Next, the access control unit 3 searches for a constant that defines the changed constant (denoted as A) as a parent class (step 1125). If there is a constant (B) defined as the parent class (YES in step 1125), all the corresponding constant names (B) are notified to the external interface 4 (step 1126). Further, it is searched whether there is a constant that defines the constant (B) as a parent class (step 1125). If a constant (denoted as C) defined as a parent class exists (step 1125 YES), all the corresponding constant names (C) are notified to the external interface 4 (step 1126). This is repeated until there is no target constant (step 1125 NO).

Next, the external interface 4 outputs the change result notified from the access control section 3 to the outside as guidance output or function execution result (step 11).
07). Further, when there are child constants (B, C ...) Which define the changed constant (A) as a parent class, an inquiry is made as to whether or not the child constant needs to be changed (step 1108).

<Constant Deletion Function> The flowcharts of FIGS. 21, 22, and 23 show the processing of the external interface 4, the processing of the access control unit 3, and the processing of the version management unit 10 that realize the constant value deletion function. Are shown respectively.

As shown in FIG. 21, first, the external interface 4 has a man-machine interface function, an input / output function with a storage medium, and a function interface function.
An instruction to delete a constant and a key value of the constant to be deleted are input from the outside (step 1301). Then the external interface 4
Passes the key value of the input deletion constant to the access control unit 3 as deletion data of the constant (step 130).
2).

Next, as shown in FIG. 22, the access control unit 3 retrieves the input primary key value of the constant (step 1321) and checks that the same key value is registered in the key management unit 2. Yes (step 132)
2). If the key value is registered (step 1322YE
S), the registration data of the constant value storage unit 1 and the key management unit 2 are deleted (step 1323). If the deletion is completed normally, the fact is notified to the external interface 4 (step 1324). On the other hand, if the deletion target key value is not registered (NO in step 1322), the access control unit 3
The constant deletion request is invalidated (step 1328) and an error is notified to the external interface 4 (step 132).
9).

Next, the access control unit 3 notifies the version management unit 6 to record the change history information such as the operation date and time, the operation reason, the key value of the target constant, the constant value before deletion (step 1325). ).

As shown in FIG. 23, the version management unit 6 records the notified operation date and time, the operation reason, the key value of the target constant, and the constant value before deletion in time series in a storage device such as a magnetic disk. (Step 1341).

Next, the access control unit 3 searches for a constant that defines the deleted constant (denoted as A) as a parent class (step 1326). If there is a constant (B) defined as the parent class (step 1326 YES), all the corresponding constant names (B) are notified to the external interface 4 (step 1327). Further, it searches for a constant that defines the constant (B) as a parent class (step 1326). If a constant (denoted as C) defined as a parent class exists (step 1326 YES), all the corresponding constant names (C) are notified to the external interface 4 (step 1327). This is repeated until there is no target constant (step 1326 NO).

Next, the external interface 4 outputs the deletion result notified from the access control unit 3 to the outside as guidance output or function execution result (step 13).
03). Furthermore, when there is a child constant (BC ...) That defines the deleted constant (A) as a parent class, an inquiry is made as to whether or not the child constant needs to be deleted or changed (step 1).
304).

<Constant Reference Function> FIGS. 24 and 25
The respective flowcharts 1 to 3 show the processing of the external interface 4 for realizing the constant value reference function and the processing of the access control unit 3, respectively.

As shown in FIG. 24, first, the external interface 4 has a man-machine interface function, an input / output function with a storage medium, and a function interface function.
A constant reference instruction and a reference constant key value are input from the outside (step 1401). The external interface 4 passes the key value of the input reference constant to the access control unit 3 as constant reference data (step 1402).

Next, as shown in FIG. 25, the access control unit 3 takes out the key value of the input constant (step 1421) and checks that the same key value is registered in the key management unit 2. (Step 1422). Here, if the key value is registered (step 1422YE
S), the registration data in the constant value storage unit 1 and the key management unit 2 are read (step 1423), and the registration data and the result are notified to the external interface 4 (step 142).
4). On the other hand, if the reference target key value is not registered (step 1422 NO), the access control unit 3 invalidates the constant reference request (step 1427) and notifies the external interface 4 of an error (step 1428).

Next, the access control unit 3 searches for a constant that defines the referenced constant (denoted as A) as a parent class (step 1425). If there is a constant (B) defined as the parent class (step 1425 YES), all the corresponding constant names (B) are notified to the external interface 4 (step 1426). Further, it is searched for a constant that defines the constant (B) as a parent class (step 1425). If a constant (denoted as C) defined as a parent class exists (step 1425 YES), all the corresponding constant names (C) are notified to the external interface 4 (step 1426). This is repeated until there is no target constant (step 1425 NO).

Then, the external interface 4 outputs the reference result notified from the access control unit 3 to the outside as guidance output or function execution result (step 14).
03). For the relationship information of the class, a display format of the relationship status such as a table format or a tree structure format can be set and referenced. Furthermore, if there are child constants (B, C, ...) That define the referenced constant (A) as a parent class, an inquiry is made as to whether or not the child constant needs to be referenced (step 1404).

<Constant change history reference function> FIGS. 26 and 2
7 and each flowchart of FIG. 27 show the processing of the external interface 4, which realizes the constant value change history reference function, the processing of the access control unit 3, and the processing of the version management unit 10, respectively.

As shown in FIG. 26, first, the external interface 4 has a man-machine interface function, an input / output function with a storage medium, and a function interface function.
A constant change history reference instruction and a reference constant key value are input from the outside (step 1501). Next, the external interface 4 passes the input key value of the reference constant to the version management unit 10 as constant change history reference data (step 1502).

Next, as shown in FIG. 28, the version management unit 10 reads out the change history information for the key value of the input constant (step 1541) and outputs the change history information and the result thereof to the external interface 4. (Step 1542).

As shown in FIG. 27, if the change history information of the reference target key value is not registered (YES in step 1521), the access control unit 3 invalidates the constant reference request (step 1522) and causes the external interface 4 to access the external interface 4. An error is notified (step 1523).

Next, the external interface 4 externally outputs the reference result notified from the version management unit 10 as guidance output or function execution result (step 1503).

<Constant Value Restoring Function> In the flowcharts of FIGS. 29, 30, and 31, the processing of the external interface 4 for realizing the constant value restoring function and the access control unit 3 are performed.
And the process of the version management unit 10 are shown.

As shown in FIG. 29, the external interface 4 uses a man-machine interface function, an input / output function with a storage medium, and a function interface function to restore a constant constant value from outside and a constant key value. The change date and time is input (step 1601). The external interface 4 transfers the input key value of the reference constant to the version management unit 10 as constant restoration data (step 1).
602).

Next, as shown in FIG. 31, the version management unit 10 reads out the change history information for the input constant key value (step 1642), and obtains the constant value before the change of the change history information. By designating, the access control unit 3 is notified of the constant change, and at the same time, the result is notified to the external interface 4 (step 1643). If the change history information of the reference target key value is not registered (NO in step 1641), the version management unit 10 invalidates the constant restoration request (step 1644) and notifies the external interface 4 of an error (step 1645).

Then, as shown in FIG. 30, the access control unit 3 extracts the primary key value from the input change data (step 1621) and confirms that the same key value is registered in the key management unit 2. Check (step 16)
22). If the key value is registered (step 1622)
YES), the registered data is read from the constant value storage unit 1 and replaced with the changed data (step 1623), and the changed constant data is re-registered in the constant value storage unit 1 (step 162).
4).

If the key management information other than the key value is changed (YES in step 1625), the key management information is read from the key management unit 2 and replaced with the changed data (step 1626), and the changed key management information is replaced with the changed key management information. It is registered in the key management unit 2 (step 1627). Furthermore, if the class is designated (YES in step 1628), it is checked whether or not the constant of the target class has been registered (step 1629). If it is not registered (NO in step 1629), the fact is notified to the external interface 4 (step 1630). When the change is completed normally, the fact is notified to the external interface 4 (step 1631).

On the other hand, if the key value to be changed is not registered (NO in step 1622), the access control unit 3 executes the same processing as the processing at the time of new registration shown in steps 1023 to 1030 of FIG. Yes (Step 1
635). That is, the definition data group is registered in the constant value storage unit 1 (step 1023), and the key management information such as the key value is registered in the key management unit 2 (step 1024). Furthermore, if a class is specified (step 1025 YES)
), It is checked whether the constant of the target class has been registered (step 1026). If not registered (step 1026N
O), and notifies it to the external interface 4 (step 1027). If the registration is completed normally, the fact is notified to the external interface 4 (step 102).
9). Then, the access control unit 3 asks the version management unit 10 about the operation date and time, the operation reason, the key value of the target constant,
It is notified to record the change history information such as the registration reason (step 1030).

After notifying the external interface 4 that the change has been normally completed in step 1631, the access control unit 3 informs the version management unit 10 of the operation date and time,
Notification is made to record change history information such as the operation reason, the key value of the target constant, and the constant value before the change (step 163).
2). In response to this, the version management unit 10 records the notified operation date and time, the operation reason, the key value of the target constant, and the constant value before the change in time series in the storage device such as the magnetic disk (step 1646).

Next, the access control unit 3 searches for a constant that defines the changed constant (A) as a parent class (step 1633). If there is a constant (defined as B) defined as the parent class (YES in step 1633), all the corresponding constant names (B) are notified to the external interface 4 (step 1634). Further, it searches for a constant that defines the constant (B) as a parent class (step 1633). If there is a constant (denoted as C) defined as the parent class (YES in step 1633), all the corresponding constant names (C) are notified to the external interface 4 (step 1634). This is repeated until there is no target constant (step 1633 NO).

Next, the external interface 4 outputs the change result notified from the version management unit 10 and the access control unit 3 to the outside as a guidance output or a function execution result (step 1603). Furthermore, child constants (B, C, ...) that define the modified constant (A) as a parent class.
..) exists, an inquiry is made as to whether or not the child constant needs to be changed (step 1604).

According to the second embodiment as described above, the following effects can be expected.

The management of the change history is extremely important for the maintenance and management of the constants, and it is valuable investigation data when an abnormality or problem occurs in the system. For example, when a system control error occurs, this is often because the constant value being used is not set correctly. A possible cause of this is a setting error when changing the constant. Therefore, smooth maintenance and management of constants can be performed by storing a change history of constants that is currently set and providing a mechanism that can be referred to at any time.

When a constant is deleted or changed by mistake,
By providing the function of restoring the constant value before the deletion or the change, it is possible to quickly perform the recovery process in the case of an erroneous operation. As a result, it is possible to reduce system abnormalities and downtime, and improve the operating rate of the system.

Next, a modification of the above-described second embodiment will be described with reference to FIG. The feature of this modification is that
A data compression / decompression function is newly added to the configuration of the second embodiment shown in FIG. 12 so that the constant storage area can be reduced.

As shown in FIG. 32, the apparatus shown in this modification has a key management unit 2, an access control unit 3, an external interface 4 and a constant value newly provided, which have the same contents as in FIG. It is composed of a compression storage unit 11 and a version compression management unit 12. The constant value compression storage unit 11 and the version compression management unit 12 are provided with data compression and decompression functions. The constant value compression storage unit 11 and the version compression management unit 12 compress and write data when writing, and decompress the read compressed data when reading.

Next, the operation of this modification will be described. Also in this modified example, as in the embodiment of FIG.
In the management of constants, register, change, delete, reference constants,
A function for referring to the change history and restoring constants is provided.

The constant value compression / storing unit 11 has a function of compressing data when storing a constant value and writing the data in a storage device such as a magnetic disk, and expanding the compressed data when reading a constant value. Similarly, the version compression management unit 12
It has a function of compressing data when storing the change history information and writing it in a storage device such as a magnetic disk, and expanding the compressed data when reading the change history information.

According to the modification of the second embodiment as described above, the following effects can be expected.

When storing constants, a large amount of storage area is required as the number of constants to be managed increases. Further, when the change history information is saved, the save area further increases according to the change amount. Therefore, by compressing the data and reducing the size of the storage area, a storage device such as a magnetic disk can be used efficiently, and change history information can be stored for a long period of time. , The maintenance and management functions of constants can be enhanced.

[0099]

As described in detail above, according to the present invention, in this type of process control system, it is possible to prevent an abnormal operation from occurring due to a mistake in changing a constant.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a first embodiment of a control constant value management device according to the present invention.

FIG. 2 is a system diagram for explaining an example of class definition.

FIG. 3 is a flowchart showing processing of an external interface that realizes a constant value registration function in the first embodiment.

FIG. 4 is a flowchart showing processing of an access control unit that realizes a constant value registration function in the first embodiment.

FIG. 5 is a flowchart showing a process of an external interface that realizes a constant value changing function in the first embodiment.

FIG. 6 is a flowchart showing processing of an access control unit that realizes a constant value changing function in the first embodiment.

FIG. 7 is a flowchart showing details of registration data change processing used to realize a constant value change function.

FIG. 8 is a flowchart showing a process of an external interface that realizes a constant value deletion function according to the first embodiment.

FIG. 9 is a flowchart illustrating processing of an access control unit that realizes a constant value deletion function according to the first embodiment.

FIG. 10 is a flowchart showing processing of an external interface that realizes a constant value reference function in the first embodiment.

FIG. 11 is a flowchart showing processing of an access control unit that realizes a constant value reference function in the first embodiment.

FIG. 12 is a block diagram showing a configuration of a modified example of the first embodiment.

FIG. 13 is a block diagram showing a configuration of a second exemplary embodiment of a control constant value management device according to the present invention.

FIG. 14 is a flowchart showing processing of an external interface that realizes a constant value registration function in the second embodiment.

FIG. 15 is a flowchart showing processing of an access control unit that realizes a constant value registration function in the second embodiment.

FIG. 16 is a flowchart showing processing of a version management unit that realizes a constant value registration function according to the second embodiment.

FIG. 17 is a flowchart showing a processing operation of an external interface which realizes a constant value changing function in the second embodiment.

FIG. 18 is a flowchart showing processing of an access control unit that realizes a constant value changing function in the second embodiment.

FIG. 19 is a flowchart showing a process of a version management unit that realizes a constant value changing function in the second embodiment.

FIG. 20 is a flowchart showing details of registration data change processing used for realizing a constant value change function.

FIG. 21 is a flowchart showing a process of an external interface that realizes a constant value deleting function according to the second embodiment.

FIG. 22 is a flowchart showing a process of an access control unit that realizes a constant value deleting function according to the second embodiment.

FIG. 23 is a flowchart showing a process of a version management unit that realizes a constant value deleting function according to the second embodiment.

FIG. 24 is a flowchart showing processing of an external interface that realizes a constant value reference function in the second embodiment.

FIG. 25 is a flowchart showing processing of an access control unit that realizes a constant value reference function in the second embodiment.

FIG. 26 is a flowchart showing a process of an external interface that realizes a constant value change history reference function in the second embodiment.

FIG. 27 is a flowchart showing a process of an access control unit that realizes a constant value change history reference function in the second embodiment.

FIG. 28 is a flowchart showing a process of a version management unit that realizes a constant value change history reference function according to the second embodiment.

FIG. 29 is a flowchart showing a process of an external interface that realizes a constant value restoration function according to the second embodiment.

FIG. 30 is a flowchart showing a process of an access control unit that realizes a constant value restoration function according to the second embodiment.

FIG. 31 is a flowchart showing a process of a version management unit that realizes a constant value restoration function according to the second embodiment.

FIG. 32 is a block diagram showing a configuration of a modified example of the second embodiment.

[Explanation of symbols]

 1 constant value storage unit 2 key management unit 3 access control unit 4 external interface 5 CRT 6 printer 7 floppy disk drive 8 external program 9 source code generation unit 10 version management unit 11 constant value compression storage unit 12 version compression management unit

Claims (7)

[Claims] 1. A constant value storage unit which functions as a file for storing a data group corresponding to one or more definition items constituting a control constant value, and a key for managing the control constant value. A key management unit that functions as a file for storing a data group corresponding to one or more definition items forming information, and a constant value stored in the constant value storage unit via the key management unit. , A man-machine interface function between an access control unit that executes access control when registering, changing, deleting, or referencing, and an output device that outputs the data stored in the constant value storage unit, the constant value Implements an input / output function with data to be stored in the storage unit or an external storage device that stores the stored data, or a function interface function that links with an external program. The constant value storage unit stores condition data indicating a range of constant values such as upper and lower limit values of definition data constituting the control constant value and possible values, The external interface unit, when a constant registration instruction or change instruction and constant definition data are input from the outside, deciphers the input definition data according to an input rule, and then defines the definition data defined by the condition data. If the input format is normal, the definition data is passed to the access control unit as constant new registration data or constant change data, while if the input format is abnormal, the registration request or change request is invalidated, A control constant value management device characterized by externally outputting guidance and the result of function execution. 2. A constant value storage unit functioning as a file for storing a data group corresponding to one or more definition items constituting a control constant value, and a key for managing the control constant value. A key management unit that functions as a file for storing a data group corresponding to one or more definition items forming information, and a constant value stored in the constant value storage unit via the key management unit. , A man-machine interface function between an access control unit that executes access control when registering, changing, deleting, or referencing, and an output device that outputs the data stored in the constant value storage unit, the constant value Implements an input / output function with data to be stored in the storage unit or an external storage device that stores the stored data, or a function interface function that links with an external program. The constant value storage unit stores class data indicating a target higher constant when the constant depends on another constant, and the access control unit , If the definition data passed from the external interface unit as constant change data or constant deletion data has a class specification defined by the class data, check whether the constant of the target class has been registered, If not registered, a notification to that effect is sent to the external interface, and a control constant value management device is characterized. 3. A constant value storage unit which functions as a file for storing a data group corresponding to one or more definition items constituting a control constant value, and a key for managing the control constant value. A key management unit that functions as a file for storing a data group corresponding to one or more definition items forming information, and a constant value stored in the constant value storage unit via the key management unit. , A man-machine interface function between an access control unit that executes access control when registering, changing, deleting, or referencing, and an output device that outputs the data stored in the constant value storage unit, the constant value Implements an input / output function with data to be stored in the storage unit or an external storage device that stores the stored data, or a function interface function that links with an external program. The key management unit stores a key value that is representative for each structural unit with a plurality of control constants associated with each other as one structural unit, and the access control unit If a key value attached to the definition data passed from the external interface unit as reference data is registered, changed, deleted, or reference data is registered in the key management unit, it is defined by the key value. A control constant value management device characterized by performing constant registration, change, deletion, or reference operation on a plurality of constant values collectively. 4. A constant value storage unit functioning as a file for storing a data group corresponding to one or more definition items constituting a control constant value, and a key for managing the control constant value. A key management unit that functions as a file for storing a data group corresponding to one or more definition items forming information, and a constant value stored in the constant value storage unit via the key management unit. An access control unit that executes access control when registering, changing, deleting, or referencing, and a source code generation that generates a source code of a constant registered in the constant storage unit according to a target programming language. Section and a man-machine interface function between the constant value storage section and an output device for outputting the data stored in the constant value storage section, data or a case for storing in the constant value storage section. And an external interface unit that executes a function interface function that links with an external program. The external interface unit generates a constant source code generation request. At this time, the source code generation unit is notified of the source code generation by designating the used language and the target constant, and the source code generation unit requests the access control unit to refer to the specified constant and the constant structure and constant value Take out,
A control constant value management device characterized by generating a source code in which a symbol name, a type declaration, and a constant value are declared according to the language used and notifying the external interface unit. 5. A constant value storage unit functioning as a file for storing a data group corresponding to one or more definition items constituting a control constant value, and a key for managing the control constant value. A key management unit that functions as a file for storing a data group corresponding to one or more definition items forming information, and a constant value stored in the constant value storage unit via the key management unit. Access control unit that executes access control when registering, changing, deleting, or referencing, and the date and time when the operation of registering, changing, or deleting a constant, the reason for the operation, and the constant before the change. A man-machine interface function between a version management unit that records numerical values and the like in time series and an output device that outputs the data stored in the constant value storage unit. And an external interface unit that executes an input / output function with an external storage device that stores the stored data or a function interface function that links with an external program, and the external interface is a constant change history from the outside. When the reference instruction and the key value of the reference constant are input, the key value of the input reference constant is passed to the version management unit as constant change history reference data, and the version management unit receives the key of the input constant. A control constant value management device characterized by reading change history information for a value and notifying the change history information and the result thereof to the external interface. 6. A constant value storage unit which functions as a file for storing a data group corresponding to one or more definition items constituting a control constant value, and a key for managing the control constant value. A key management unit that functions as a file for storing a data group corresponding to one or more definition items forming information, and a constant value stored in the constant value storage unit via the key management unit. Access control unit that executes access control when registering, changing, deleting, or referencing, and the date and time when the operation of registering, changing, or deleting a constant, the reason for the operation, and the constant before the change. A man-machine interface function between a version management unit that records numerical values and the like in time series and an output device that outputs the data stored in the constant value storage unit. And an external interface unit that performs an input / output function with an external storage device that stores the stored data or a function interface function that links with an external program, and the external interface unit restores constants from the outside. When the instruction, the key value of the restoration constant and the modification date and time are input, the input key value of the restoration constant is passed to the version management unit as restoration data of the constant, and the version management unit receives the key of the input constant. Read the change history information for the value, specify the constant value before the change history information is changed, notify the access control unit of the change of the constant, and at the same time notify the external interface unit of the result. A constant value control device for control, characterized by. 7. A constant value compression storage unit that functions as a file for compressing and storing and expanding and reading a data group corresponding to one or more definition items constituting a control constant value, said control A key management unit that functions as a file for storing a data group corresponding to one or more definition items that make up the key information for managing the constant value for storage, and a constant stored in the constant value storage unit. An access control unit that executes access control when registering, changing, deleting, or referencing a numerical value via the key management unit, and when a constant registration, changing, or deleting operation is performed. A version management unit for time-sequentially compressing and recording the date and time, operation reason, constant value before change, etc. and reading out, and an output device for outputting the data stored in the constant value storage unit External machine that executes the man-machine interface function, the input / output function with the external storage device that stores the data to be stored in the constant value storage unit or the stored data, or the function interface function that links with the external program. A constant value control device for control, characterized in that