JP5458040B2 - HI software data creation apparatus and HI software data creation method - Google Patents

Description

  The present invention relates to a data creation device for HI software and a data creation method for HI software, in which definition data is collected, in human interface (HI) software of a digital protection device.

  The digital type protection device that protects the power system receives the amount of electricity such as current and voltage of the power system and the operating status of the equipment and devices (switch on / off, device use / non-use, etc.) as an input relay. A calculation or logic process is used to determine whether or not an accident has occurred in the power system, or to determine trip command output time coordination, and based on the determination result, a trip command is output to the circuit breaker.

  In addition, in order to notify a human system (for example, a monitor) of a trip by the protection device, the operation information of the protection device is output to another device such as a monitoring control device. In addition, a continuous monitoring function and an automatic inspection function are provided in the protective device itself to monitor whether there is an abnormality in the protective device, and in order to notify the human system when an abnormality is detected. The abnormality information of the protection device is output to another device such as a monitoring control device.

  In addition, the digital protection device is equipped with the HI function, and it is possible to input and confirm the set values and set values necessary for the above-mentioned functions, display the contents of relay operation and trip output, and use the constant monitoring function and automatic inspection function. Anomaly detection contents are displayed through the HI screen. The human system performs various input operations and display confirmation on this HI screen.

  This HI screen is realized by a software program (hereinafter referred to as software), and the settable value to be input, the range of values that can be input, the steps, the characters of each item to be displayed, etc. Is pre-defined as data.

  On the other hand, the function of the digital protection device is illustrated as an expanded connection diagram. Specifically, the function is illustrated by a sheet that explains the function by text or a diagram, or a sheet that is expressed by a logic diagram. This development connection diagram is drawn by CAD (Computer Aided Design) software (hereinafter referred to as CAD software), and also shows the HI function in addition to the function of the power system protection itself.

  The data of the HI software of the digital type protective device is created as a source code, for example, manually by a programmer based on the developed connection diagram. Also, for some setting values, one setting value may be used as input for logic processing at multiple locations. In such a case, notation on multiple logic diagram sheets (setting value names, etc.) From the above, the human determines that the set values are the same set value, and creates the data on the source code as one set value data (see, for example, Patent Document 1).

JP 2009-219245 A

  As described above, in conventional HI software data creation work, programmers manually create HI software data as source code based on the development connection diagram. However, once input to the CAD software as the development connection diagram. Since the same data is manually input again as the source code of the data for the HI software, the input to the CAD software and the work man-hours overlap. In addition, there is a possibility that incorrect data is input during manual input of HI software data, and a mismatch occurs between the drawing and the HI software data.

  Furthermore, as described above, for the setting values that are input to a plurality of logic diagrams, man-hours are required for a human to determine whether or not they are the same setting value. May occur.

  In addition, even in the development connection diagram input by CAD software, there is a possibility that a human error such as erroneously inputting data having the same contents with respect to data that should not be duplicated may occur.

  An object of the present invention is to create data for HI software from data input to CAD software as a development connection diagram, and to create HI software data reliably and easily. It is to provide a data creation method.

  The present invention is an invention for solving the above-described problems, and the HI software data creation device extracts definition data relating to the HI function from CAD data of the developed connection diagram, and creates a data table of the HI software. It is what I did. Also, in this process, for the setting values that are input to multiple logic diagrams, it is determined by the signal name that they are the same setting value, and if they are the same setting value, it is output to the data table as one setting value It is what you do.

  In addition, in the process of creating the data for HI software, it is easy to detect errors in illustration in the developed connection diagram by checking the duplication of input data to CAD software and displaying the error of the duplicated part. To do.

  According to the present invention, HI software data can be created from data input to CAD software as a development connection diagram, and the creation of HI software data can be made reliably and easily.

It is a figure which shows the data creation procedure for HI software. It is a figure which shows the example of the set value of an expansion | deployment connection diagram. It is a figure which shows the example of the operation setting of an expansion | deployment connection diagram. It is a figure which shows the example of the forced control of an expansion | deployment connection diagram, and an operation display. It is a figure which shows the example of the test setting of an expansion | deployment connection diagram, and abnormality display (1). It is a figure which shows the example of the test setting of an expansion | deployment connection diagram, and abnormality display (2). It is a figure which shows the example of the test setting of an expansion | deployment connection diagram, and abnormality display (3). It is a figure which shows the example of the data table for 1st HI software when there is no incorrect input in CAD data. It is a figure which shows the example of the data table for 1st HI software in case CAD data has an incorrect input. It is a figure which shows the example of a duplication data list. It is a figure which shows the example of the 2nd data table for HI software. It is a figure which shows the structure of the data preparation apparatus for HI software.

Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a diagram showing a procedure for creating data for HI software. FIG. 12 is a diagram showing the configuration of the HI software data creation device.

  A configuration example of the apparatus will be described with reference to FIG. A data table creation program 20 for HI software (hereinafter referred to as program 20) developed from the mass storage device 15 such as a hard disk to the memory 16 is processed by the CPU 11, and data is extracted from the CAD data 102 on the memory 16.

  First HI software data table 104 (first HI software data information) (see FIGS. 8 and 9), which is a HI software data table (provisional) extracted or edited by the program 20, HI software data The second HI software data table 107 (second HI software data information) (see FIG. 11) and the duplicate data list 106 (see FIG. 10), which are tables (books), are arranged on the memory 16. The HI software data table (provisional) is a provisional data table including data duplication, as will be described in detail later. The HI software data table (main) is a data duplication check (S105, see FIG. 1). ) Data table after processing.

  The first HI software data table 104, the second HI software data table 107, and the duplicate data list 106 are displayed on the screen by the display unit 13 which is a display, and the contents can be confirmed by the user. The same content can also be output to paper by the output unit 14 which is a printer. Based on the duplicate data list 106, the user can edit the CAD data 102 from the input unit 12.

The program 20 includes a data extraction unit 21 and a data duplication inspection unit 22.
The data extraction unit 21 performs the processing of HI software data extraction S103 (see FIG. 1). Specifically, the data extraction unit 21 extracts definition data related to the HI function from the CAD data 102 of the developed connection diagram, and generates the first HI software data table 104 (first HI software data information). Stored in the memory 16 (storage unit).

  The data duplication checking unit 22 performs the data duplication check S105 (see FIG. 1). Specifically, the data duplication inspection unit 22 uses the generated first HI software data information to set the signal names corresponding to the setting values with respect to the setting values that are input to the plurality of development connection diagrams. To determine whether or not the setting values are the same, generate a duplicate data list 106 of the setting values with overlapping signal names, and aggregate the setting values with overlapping signal names as one setting value. HI software data table 107 (second HI software data information) is generated and stored in the memory 16.

Hereinafter, each procedure of the HI software data creation procedure shown in FIG. 1 will be described.
[Development connection diagram input S101]
The development connection diagram input S101 is performed manually by using CAD software, and CAD data 102 which is a development connection diagram is created. FIG. 2 to FIG. 6 show examples of development connection diagram sheets.

  FIG. 2 is a diagram illustrating an example of the set value list 202 described on the sheet 201. In the set value list 202, a set element name 203, a minimum value 204 and a maximum value 205 that can be set, a step 206, a unit 207, and a signal name 208 are described. Among the settling element names 203, 44SX1 and 44SX2 represent reactance type short-circuit distance relays, and 44S represents a short-circuit distance relay.

  3 to 6 show examples of sheets 301, 401, 501, and 601 represented by logic diagrams. Among these, FIG. 3 is an example of a logic diagram related to an operation setting 302 that is one of the HI functions described in the sheet 301. This figure shows a notation example in which the HI function type 303, operation setting element name 304, possible setting value 305, and signal name 306 are described in the symbol of the operation setting 302.

  FIG. 4 is an example of a logic diagram related to the forced control 402 and the operation display 412 among the HI functions described in the sheet 401. For the sake of explanation, FIG. 4 shows an example in which the forced control 402 and the operation display 412 are written in the same logic, but they are not necessarily written in the same logic. In FIG. 4, the HI function type 403, the forced control element name 404, and the signal name 405 are included in the symbol of the forced control 402, and the HI function type 413, the operation display element name 414, and the signal name 415 are included in the symbol of the operation display 412. Shows a notation example in which is written.

  FIG. 5 is a logic diagram related to the test setting 502 and the abnormality display 512 among the HI functions described in the sheet 501. As in FIG. 4, the test setting 502 and the abnormality display 512 are not necessarily described in the same logic. In FIG. 5, the symbol of the test setting 502 includes the HI function type 503, the test setting element name 504, the signal name 505, and the symbol of the abnormality display 512 includes the HI function type 513, the failure detection item 514, and the failure estimation part 515. , A notation example in which a signal name 516 is described.

  FIG. 6 is an example of logic related to the test setting 602 and the abnormality display 612 among the HI functions described in the sheet 601. As in FIG. 4, the test setting 602 and the abnormality display 612 are not necessarily described in the same logic. In FIG. 6, HI function type 603, test setting element name 604, and signal name 605 are included in the symbol of test setting 602, and HI function type 613, failure detection item 614, and failure estimation part 615 are included in the symbol of abnormality display 612. , A notation example in which a signal name 616 is described.

  The data described in each of the sheets in FIGS. 2 to 6 is input manually by CAD software.

[HI Software Data Extraction S103]
The data extraction unit 21 extracts HI software data from the CAD data 102 of the developed connection diagram. Here, the data to be extracted will be described with reference to FIGS. 2 to 6. In FIG. 2, the settling element name 203, the minimum value 204, the maximum value 205, the step 206, the unit 207, and the signal name 208 of each settling value are extracted. To do. In FIG. 3, the operation setting element name 304, possible setting value 305, and signal name 306 of the operation setting 302 are extracted. In FIG. 4, the forced control element name 404 and the signal name 405 of the forced control 402 and the operation display element name 414 and the signal name 415 of the operation display 412 are extracted.

  In FIG. 5, the test setting element name 504 and the signal name 505 of the test setting 502 are extracted, and the failure detection item 514, the failure estimated part 515, and the signal name 516 of the abnormality display 512 are extracted. In FIG. 6, the test setting element name 604 and the signal name 605 of the test setting 602, and the failure detection item 614, the failure estimation part 615, and the signal name 616 of the abnormality display 612 are extracted.

  With respect to selection of extraction targets, all data described in the set value list 202 is extracted in FIG. 2, and HI function types 303, 403, 413, 503, 513, 603, and 613 are described in FIGS. Extract symbols.

  The data extraction unit 21 (see FIG. 12) outputs the extracted data as a first HI software data table 104 which is a HI software data table (temporary). FIG. 8 shows an example of the first HI software data table 104. Here, in relation to the explanation of the data duplication check S105 in the next procedure, the data is extracted as the first HI software data table 104 including the logic of FIG. 6 similar to FIG. In FIG. 5 and FIG. 6, test settings 502 and 602 which are the same signal are input to the logic diagrams of the respective drawings.

  As a method of creating the first HI software data table 104, first, when extracting data from the CAD data 102, the extracted data from the set value list 202 (see FIG. 2) is “set value”. Is added to each extracted data as an attribute indicating a data category (hereinafter referred to as a category attribute).

  For the extracted data from the logic diagram, the HI function types 303, 403, 413, 503, 513, 603, 613 are added to the respective extracted data as segmentation attributes. After extracting all data to be extracted from the CAD data 102, the extracted data is organized using the category attributes as key information, and the extracted data is output to the first HI software data table 104 for each category attribute.

  As a configuration in the first HI software data table 104, for example, in the example of FIG. 8, the bracket attribute “[]” indicates the partition attribute, and the extracted data is arranged after the next row of each partition attribute. In the extracted data, each attribute is arranged in a comma delimiter, and a comment representing the meaning of each attribute is arranged on the next line of the division attribute so that the meaning of each attribute can be understood. Since each attribute of the data extracted for each category attribute is determined, the comment line has contents determined for each category attribute. The extracted data is arranged in the sheet order on the CAD data 102.

[Data duplication check S105]
Using the first HI software data table 104, the duplication of HI software data extracted from the expanded connection diagram is checked. In the digital protection device, as for the input signal to the logic diagram, the same signal may be input to a plurality of logics. On the other hand, regarding the output signal from the logic diagram, the same signal cannot be output from a plurality of logics.

  Here, in the HI data described in the logic diagrams of FIGS. 3 to 6, the input signals to the logic diagram are the operation setting 302, the forced control 402, and the test settings 502 and 602, which correspond to the output signals from the logic diagram. Those are an operation display 412 and abnormality displays 512 and 612.

  Therefore, the extracted data may overlap with respect to the operation setting 302, the forced control 402, and the test settings 502 and 602 that are input signals, and the extracted data with respect to the operation display 412 and the abnormality displays 512 and 612 that are output signals. There will be no overlap. Also, there can be no overlap with respect to the settling value.

  Here, FIG. 7 is shown as an example in which one place in the operation display of FIG. 4 is erroneously input. FIG. 7 shows an example in which the operation name of the signal name 3044S1TPB is erroneously input as 44S1 stage A phase trip where the name of the operation display element should be 44S1 stage B phase trip, and the signal name 3044S1TPA and action display element name overlap.

  7 is used instead of FIG. 4, and the data extraction unit 21 (see FIG. 12) uses the first HI software data table 901 extracted from FIG. 2, FIG. 3, FIG. 7, FIG. Shown in Here, since the test settings 502 and 602 in FIG. 5 and FIG. 6 are the same signal, they are output in an overlapping state as indicated by 902 in FIG. Further, since the operation display in FIG. 7 is also duplicated due to an erroneous input, it is output in a duplicated state as indicated by 903 in FIG.

  When the data duplication checking unit 22 (see FIG. 12) performs the data duplication check S105 on the first HI software data table 901, the duplication data list 106 is output as a check result. An example is shown in FIG. The judgment of whether or not there are duplicates is considered to be duplicated if the signal names are the same, or if the signal element names (setting element name, operation setting element name, etc.) are the same. Only duplicate data is displayed on this list. Since the test setting is an input signal and there is a possibility of duplication, it is output with a warning [W] as shown at 1002 in FIG. Since this is an output signal and there is no possibility of duplication, it is an example of being output with error handling [E] as shown in 1003 in FIG.

  At the same time, as a result of the data duplication check S105, a second HI software data table 107 which is a HI software data table (main) is output. An example is shown in FIG. The second HI software data table 107 is actually used by the HI software, and is displayed on the HI screen with the contents defined in this table.

  The second HI software data table 107 is created when the data duplication checking unit 22 (see FIG. 12) edits the first HI software data table 901. As editing contents, overlapping input signals are interpreted as intentionally overlapping, and the overlapping signals are automatically aggregated into one signal as indicated by 1102 in FIG. Since the same signal is displayed as one item on the actual HI screen, the automatic aggregation in this way can reduce the work man-hours and prevent work errors as compared with the manual editing. Even if there is an overlap with respect to the output signal, the output signal is output as it is as shown in 1103 of FIG.

  As shown in FIG. 1, in this case, a human recognizes an erroneous input from the duplicate data list 106, that is, determines whether or not there is a data error (S108), and if there is an error (S108, yes), Returning to the developed connection diagram input S101 in S101, the CAD data is corrected by re-inputting to obtain the correct second HI software data table 107. If there is no error (S108, none), the HI software data creation process is terminated.

  Here, the second HI software data table 107 (see FIG. 11) from the first HI software data table 104 (see FIG. 8) or the first HI software data table 901 (see FIG. 9) is used. In the example, the sheet number is deleted when the sheet number is obtained. However, the sheet number may be left without being deleted.

  According to the above procedure, the HI software data can be created by using the CAD data of the developed connection diagram without manual input by a human, and the number of steps for creating the HI software data is reduced and the quality is improved. In addition, it is possible to easily detect a duplication error in a portion related to the HI function of the developed connection diagram.

  According to the present embodiment, it is possible to create HI software data using CAD data of the developed connection diagram, and the number of steps for creating the HI software data is reduced and the quality is improved. In addition, it is possible to easily detect a duplication error in a portion related to the HI function of the developed connection diagram.

10 HI software data creation device 11 CPU
DESCRIPTION OF SYMBOLS 12 Input part 13 Display part 14 Output part 15 Mass storage part 16 Memory 20 Program 21 Data extraction part 22 Data duplication test | inspection part 102 CAD data 104,901 First HI software data table (HI software data table (temporary) , Data information for the first HI software)
106 Duplicate data list 107 Second HI software data table (HI software data table (main), second HI software data information)

Claims (5)

This is a data creation device for HI software that extracts definition data for human interface software (hereinafter referred to as HI software) from CAD data in a development connection diagram for a digital type protective device and creates data information that summarizes the definition data. And
A data extraction unit that extracts definition data related to the HI function from the CAD data of the developed connection diagram, generates first HI software data information, and stores the data information in the storage unit;
Based on the generated data information for the first HI software, it is determined whether or not the setting values are the same by the signal name with respect to a plurality of setting values that are input to the expanded connection diagram, and overlap A duplication data list of setting values, and a data duplication checking unit that aggregates the duplicated setting values as one setting value to generate second HI software data information and stores the data information in the storage unit. A data creation apparatus for HI software characterized by the above. The HI software data creation device according to claim 1, wherein the data duplication checking unit determines whether the setting value is the same including the element name in the determination. The data duplication inspection unit determines whether or not the setting values are the same by the signal name with respect to the setting values output from the plurality of developed connection diagrams, and generates a duplicate data list of the duplicate setting values. The HI software data creation device according to claim 1. The data duplication checking unit adds a warning symbol to the duplicated input set value and an error symbol to the duplicated output set value in the duplicate data list. The data creation device for HI software described in 1. Data for the HI software of the data creation device that extracts the definition data for human interface software (hereinafter referred to as HI software) from the CAD data of the development connection diagram for the digital type protective device and creates data information in which the definition data is collected. A creation method,
The data creation device includes:
Data relating to the HI function is extracted from the CAD data of the developed connection diagram, and the first HI software data information is generated and stored in the storage unit,
Based on the generated data information for the first HI software, it is determined whether or not the setting values are the same by the signal name with respect to a plurality of setting values that are input to the expanded connection diagram, and overlap A duplication data list of setting values is generated, and the duplication setting values are aggregated as one setting value to generate second HI software data information and stored in the storage unit. Data creation method.

Images