TWI806783B - Method of editing report for scada system - Google Patents

Abstract

A report editing method for a supervisory control and data acquisition (SCADA) system is disclosed and includes following steps: when a window interface is triggered to open, determining whether a binding label exists in a register of a variable library of the SCADA system; when the binding label exists, reading report data corresponding to the binding label from an edited-data file to import the report data to the window interface; when the binding label does not exist, obtaining multiple items of report information through the window interface to create and store new report data in the edited-data file; and writing a new binding label corresponding to the new report data to the variable library to bind the window interface with the new report data.

Description

Report Editing Method Used in SCADA System

The invention relates to a SCADA system, in particular to a report editing method used by the SCADA system.

Data acquisition and monitoring (Supervisory Control and Data Acquisition, SCADA) system is a system with program monitoring and data collection capabilities, generally used in various environments, production lines, systems or devices, allowing managers to monitor, collect and report Provide the required information.

The current SCADA system only has the function of exporting the historical data in the database to generate a report in a fixed format, and cannot allow users to arbitrarily set export conditions (at most, allow users to set time parameters). For example, even though a production line can be used to produce multiple products, the current SCADA system can only generate comprehensive reports for multiple products according to the report type selected by the user (such as daily report, weekly report, etc.). That is to say, the content of the report can only correspond to the total output of the production line, but cannot be distinguished by product.

In addition, in the current SCADA system, the user cannot copy and modify the data of the edited report through the window interface, nor can it add or delete report fields in real time.

Furthermore, if the user wants to perform conditional query on the historical data in the database, it is usually necessary to add a structured query language (Structured Query Language, hereinafter referred to as SQL) conditional expression in the script program of the SCADA system, so as to use the SQL program to Perform conditional query on historical data in the database. However, if the manager or engineer of the client does not have the ability to write SQL, it is impossible to add SQL conditional expressions through the above method. Moreover, there are multiple objects (such as buttons, drop-down menus, etc.) on the window interface of the SCADA system, and the SQL programs added through the above method will be scattered in the script programs of different objects. In this way, the difficulty of program maintenance is increased in practice.

The main purpose of the present invention is to provide a report editing method of a SCADA system, which can allow the window interface to automatically import the bound edited report, and allow the user to edit the edited report again.

In order to achieve the above-mentioned purpose, the report editing method of the present invention includes the following steps: a) when opening a window interface, determine whether a binding tag exists in a temporary register of a variable dictionary; b) when the binding tag exists, Query an edit file according to the binding tag to read a report data corresponding to the binding tag, and import the report data to the window interface; c) When the binding tag does not exist, through the window interface Obtain a plurality of report elements to create and save a new report data to the edit file, wherein the plurality of report elements include a report name, a report type, a data table and a plurality of parameter fields; and d) write the new A new binding tag corresponding to the report data is added to the variable dictionary to bind the window interface and the new report.

Compared with the related technology, the technical effect of the present invention is that the SCADA system can automatically import the bound edited report into each editing area in the window interface during the preloading stage, so that the user can directly export the report Data or edit the edited report again.

1: SCADA system

2: Windows script program

20: Windows interface

21: Report component editing area

211: Report name field

212: Report type menu

213: Historical report menu

214: Data sheet menu

215~218: button

22: Field editing area

221: Field menu

222:Edit field preview

223~228: button

23: Time editing area

24: Filter editing area

25: Bound report display area

26: Report display area

3: Report module

4: Database

41: Edit File

411: Report data

412: New report data

42: Machine file

5: variable dictionary

S31~S36, S81~S87, S91~S98, S101~S112: editing steps

FIG. 1 is an embodiment of a system architecture diagram of the present invention.

FIG. 2 is an embodiment of a schematic diagram of a window interface of the present invention.

Fig. 3 is an embodiment of the editing flowchart of the present invention.

FIG. 4 is an embodiment of a schematic diagram of a binding query in the present invention.

FIG. 5 is an embodiment of a schematic diagram of an edited file in the present invention.

FIG. 6 is an embodiment of a report field diagram of the present invention.

FIG. 7 is an embodiment of a schematic diagram of report addition in the present invention.

FIG. 8 is an embodiment of the system operation flowchart of the present invention.

FIG. 9 is an embodiment of the operation flow of the system in FIG. 8 in the preloading stage of the present invention.

FIG. 10 is an embodiment of the operation flow of the system in FIG. 8 in the editing stage of the present invention.

A preferred embodiment of the present invention will be described in detail below in conjunction with the drawings.

The present invention discloses a report editing method (hereinafter referred to as the editing method) of a Supervisory Control and Data Acquisition (SCADA) system.

Please refer to FIG. 1 , which is an embodiment of a structure diagram of a SCADA system 1 of the present invention. As shown in Figure 1, for software framework, SCADA system 1 of the present invention comprises window script program 2, a plurality of Report module 3 and database 4. The window script program 2 includes a plurality of function modules in the editing areas 21-24 for receiving character input and menu operations from the user. Multiple report modules 3 correspond to multiple editing areas 21-24, and are used to access the database 4 according to the input characters and menus received by the multiple editing areas 21-24. The window script program 2 also includes functional modules of the display areas 25 and 26 , the display area 25 is used to display the bound report name, and the display area 26 is used to display the machine original data returned from the database 4 .

Regarding the hardware structure (not shown in the figure), the SCADA system 1 includes at least one personal computer and a data center. The personal computer includes a processor, a memory, a user input interface and a display. The window script program 2 and multiple report modules 3 can be compiled into program codes and stored in the memory. The processor is coupled to the memory, the user input interface and the display, and is used to receive character input and menu operations through the user input interface, and execute the window script program 2 and multiple report modules 3 according to the user input to generate processing result. The display is used for presenting multiple editing areas 21-24 and related pictures of the display areas 25, 26, and presenting the processing results generated by the processor executing the window script program 2 on the pictures. The data center can be a cloud hard disk or a cloud server to realize the database 4; in one embodiment, the built-in memory of the personal computer can be used to realize the database 4.

The database 4 includes editing files 41 and machine files 42 . In one embodiment, the editing file 41 is used to record and store the report data of the edited report, and the machine file 42 is used to record and store the raw data (raw data) of the SCADA system 1, such as multiple machines on the production line statistics, historical data, etc.

Please refer to FIG. 2 , which is an embodiment of a schematic diagram of a window interface 20 of the present invention. As shown in Figure 2, when the window script program 2 is executed, the window interface 20 can be opened, and the window interface 20 displays a plurality of editors. Editing areas 21~24, users can input characters or operate menus through editing areas 21~24 to edit various reports.

Specifically, the editing areas 21-24 are used to input the received characters or menu content into the corresponding function module, function or subroutine in the window script program 2, so as to call the report module 3 to access the database 4, and then Get the corresponding data from database 4. In one embodiment, the window script program 2 can be executed in multiple window interfaces 20 , allowing users to edit and export multiple reports on the multiple window interfaces 20 .

It is worth noting that the report module 3 is established based on SQL. Through SQL functions or commands, the report module 3 can query the database 4 according to the conditions set by the user to obtain the required data. Through the establishment of the report module 3, the user does not need to have SQL coding ability, and can directly use the editing areas 21-24 on the window script program 2 to perform conditional query on the database 4 of the SCADA system 1. In this way, it is beneficial for the user to edit the format, columns and content of the report. Moreover, when the system administrator or developer needs to maintain the SQL program, it is only necessary to update the report module 3, and there is no need to search for the program codes in each editing area 21-24 in the window script program 2. In this way, the convenience of program maintenance is effectively improved.

As shown in FIG. 2 , the window interface 20 displays a report component editing area 21 , field editing area 22 , time editing area 23 , filter editing area 24 , bound report display area 25 and report display area 26 . In the embodiment of FIG. 2 , the multiple editing areas 21-24 include input fields and drop-down menus, but not limited thereto.

The report component editing area 21 is used to receive character input and menu operations, including a report name field 211 , a report type menu 212 , a historical report menu 213 and a data table menu 214 . The report name field 211 is an input field for allowing the user to input a report name. The report type menu 212, the historical report menu 213 and the data table menu 214 are drop-down menus, but not limited thereto. Report Type Menu 212 is used to allow the user to select the desired report type, for example, daily report, weekly report, monthly report, time interval report, utilization rate report, through-through rate report, yield rate report, capacity utilization rate report, etc. The historical report menu 213 is used for allowing the user to select a previously generated and stored historical report. The data table menu 214 is used to allow the user to select the required report type or the data table corresponding to the historical report. The data sheet corresponds to a specific product category (such as a thermostat or a motor screw, etc.) in the environment where the SCADA system 1 is located (such as a factory), so different data sheets will include different numbers and types of parameter columns, and each parameter column Bits respectively record parameters such as product density, product thickness, product width, energy consumption, productivity and line speed, but not limited thereto.

The report component editing area 21 also includes a plurality of buttons 215 , 216 , 217 , 218 . The button 215 is used to trigger the window script program 2 to bind the report according to the setting of the report name column 211, the report type menu 212, the historical report menu 213 and the data table menu 214, so that the bound report display area 25 displays the bound report The name. Button 216 is used to unbind the report. The button 217 is used to clear the setting of the report name column 211, the report type menu 212, the historical report menu 213 and the data table menu 214, and clear a report data 411 in the editing file 41 (drawn in FIG. 5 ). The button 218 is used to save all current input data in the window interface 20 to the editing file 41 .

The column editing area 22 is used for receiving menu operations, including a column menu 221 and an edit column preview 222 . The field menu 221 provides multiple parameters or items for the user to select, and the parameters or items selected by the user are added to the edit field preview 222, thereby editing and previewing multiple parameter fields of a report.

The column editing area 22 also includes a plurality of buttons 223 - 228 . The button 223 is used to import all the parameters or items included in the field menu 221 into the edit field preview 222 . The button 224 is used to empty all the parameters or items displayed in the edit field preview 222 . Button 225 is used to preview from the edit field View 222 deletes the parameter or item selected in column menu 221. The button 226 is used to move forward the parameter or item selected in the field menu 221 from the edit field preview 222 to adjust the order of the items. The button 227 is used to trigger the window script program 2 to query the corresponding report data from the database 4 according to the settings of the report element editing area 21, column editing area 22, time editing area 23, and filter editing area 24, and display the query results on Report display area 26 . The button 228 is used to trigger the window script program 2 to export the report.

The time editing area 23 is used to set a filter time, and the filter time is a specific time or a period of time, so as to filter the time range of the exported report.

The filter editing area 24 is used to set filter conditions (such as multiple combinations greater than, equal to or less than a specific value) for one or more parameters or items selected in the field menu 221, thereby filtering the value range of the exported report.

The report display area 26 is used for displaying the setting of the editing field preview 222 and the query result of the report module 3 . Specifically, the window script program 2 queries the corresponding report data from the database 4 through the report module 3 according to the settings of the report element editing area 21, field editing area 22, time editing area 23, and filter editing area 24, and sends The query result is displayed in the report display area 26 (as shown in the lower part of FIG. 2 ).

However, the above is only a specific implementation example of the present invention. In other embodiments, the user can perform any combination of the following operations according to the requirements, including setting the fields of the report, directly exporting the historical report, setting the filter condition, setting Time parameters, editing historical reports and creating new reports.

One of the technical features of the present invention is that after the user finishes editing a report through the report element editing area 21, field editing area 22, time editing area 23 and filter editing area 24, the report data and bindings of the edited report can be stored. Set the label to the edit file 41 and bind the window interface 20 with the binding label. When the user executes the window script program 2 again, the SCADA system 1 can query and edit the file 41 according to the existing binding tags to obtain corresponding report data, and automatically import the binding tags Mark the corresponding multiple report components to the multiple editing areas 21-24 of the window interface 20. In this way, users do not need to start editing a new report from a blank report. Moreover, through the multiple editing areas 21-24 on the window interface 20, the user can re-edit the edited report, so as to realize a more flexible use situation of the report.

Please refer to FIG. 3 , which is an embodiment of the editing flowchart of the present invention. The editing flow shown in FIG. 3 can be applied to the SCADA system 1 shown in FIG. 1 and realized through the window script program 2 shown in FIG. 1 and the window interface 20 shown in FIG. 2 .

As shown in FIG. 3 , the window script program 2 of the SCADA system 1 judges whether there is a binding tag in the register of the variable dictionary (step S31 ). That is, the window script program 2 judges whether the variable dictionary is empty (Null) or there is an invalid character string (such as ###). If the variable dictionary is empty or there is an invalid string, it means that there is no binding tag; if there is a valid string in the variable dictionary, it means that there is a binding tag.

In one embodiment, the binding tag is recorded in the variable dictionary as a string. If there is a binding tag in the variable dictionary, it means that the database 4 stores a bound report. If there is no binding tag in the variable dictionary, it means that the database 4 does not store the bound report.

If there is no binding tag in the variable dictionary, the user needs to create a new report data from a blank report. When there is no binding tag, the window script program 2 receives the user's operation through the window interface 20, and obtains a plurality of report elements input or set by the user (step S32), so as to create a new report from the blank report. After the user input and setting are completed, the window script program 2 stores a plurality of report elements as a new report data to the edit file 41 (step S33). And, the window script program 2 writes a new binding tag corresponding to the new report data into the variable dictionary (step S34 ), so as to bind the window interface 20 and the new report data. The report data and the new report data respectively include a plurality of report elements, and the plurality of report elements include a report name, a report type, a data table and a plurality of parameter fields.

If it is determined in step S31 that there is a binding tag, the window script program 2 queries the editing file 41 of the SCADA system 1 according to the binding tag to read the report data corresponding to the binding tag (step S35 ). Moreover, the window script program 2 automatically imports multiple report elements of the report data to the multiple editing areas 21-24 of the window interface 20 (step S36). This way, users do not need to create a new report from a blank report.

In one embodiment, the binding tag is a report name of the report data. When the user finishes editing a report and presses the binding button 215, the window script program 2 writes the name of the current report into the register of the variable dictionary to complete the binding action.

Please refer to FIG. 4 , which is an embodiment of a schematic diagram of a bound query in the present invention. In the embodiment of FIG. 4 , a report name (test_week_report is taken as an example in FIG. 4 ) is recorded in the temporary register of the variable dictionary 5 of the SCADA system 1 . In the preloading stage, the window script program 2 will first query and edit the file 41 according to the report name (ie, the binding label), so as to read the multiple report elements corresponding to the report name, and import the multiple report elements into the window interface 20. For example, the report name field 211 imports the report name test_week_report, the report type menu 212 imports the weekly report, the historical report menu 213 imports test_week_report, the data table menu 214 imports DIV_test1021, and the edit field preview 222 imports Items such as product density (product_D), product thickness (product_T), product width (product_W), energy consumption (elect_show), production capacity (Production) and line speed (Line_Speed). The filtering editing area 24 imports the conditions of "product density is equal to 1000 (product_D=1000)" and "product thickness is greater than or equal to 100 (product_T>=100)". This way, users do not need to create a new report from a blank report.

Please refer to FIG. 5 , which is an embodiment of the schematic diagram of the editing file 41 of the present invention. As shown in FIG. 5 , the editing file 41 includes a plurality of data rows (rows), each of which records a report data 411 respectively. Report data 411 includes time stamp, report name, edit field, report type, Data fields such as data tables and filter conditions. Those skilled in the art can add or delete data fields included in the report data 411 according to actual needs, but not limited to the above.

Conceptually, a plurality of report elements in a report data 411 can be regarded as a plurality of bound label groups, and there is a binding relationship between them. The window script program 2 can query the relevant label group (ie, report elements such as time stamp, edit field, report type, data table and filter condition) in the edit file 41 through the bound label (ie, report name), and then Import all tags in a report data 411 into the corresponding function, so that the window interface 20 can display the corresponding import result.

Specifically, the Windows script program 2 judges that the bound label test_week_report exists in the register of the variable dictionary 5 of the SCADA system 1 (step S31 of FIG. 3 ). Then in the preloading stage, the window script program 2 queries the editing file 41 according to the binding tag test_week_report to read the bound report data 411 (step S35 in FIG. 3 ). Moreover, the window script program 2 automatically imports the multiple report elements of the report data 411 into the multiple editing areas 21-24 of the window interface 20 (step S36 in FIG. 3 ). For example, import the report name into the historical report menu 213, import the report type into the report type menu 212, import the data table into the data table menu 214, import multiple parameter fields into the field menu 221 and edit field preview 222 , import at least one filter condition into the filter edit area 24 , and import the filter time into the time edit area 23 .

Please refer to FIG. 6 , which is an embodiment of the report field diagram of the present invention. Referring to FIG. 5 , the window script program 2 automatically imports multiple items in the edit field of the report data 411 to the field edit area 22 in the window interface 20 . For example, import items such as product density (product_D), product thickness (product_T), product width (product_W), energy consumption (elect_show), production capacity (Production), and line speed (Line_Speed) into the drop-down menu of the field menu 221 and edit field preview 222 . Thus, the user Without inputting any information, a bound edited report can be automatically obtained after the window interface 20 is opened.

Please refer to FIG. 7 , which is an embodiment of a schematic diagram of report addition in the present invention. As shown in Figure 7, after editing the new report (for example, modify the report name to TEST_time interval report, and add the filter condition product_D=1000), the user can press the button 218 to save the field, thereby saving the window All the input data in the interface 20 are sent to the editing file 41 as a new report data 412 (the new report data 412 includes the filter condition product_D=1000). When the user presses the button 215 to bind the report, the window script program 2 writes a new binding tag (such as TEST_time interval report) to the register of the variable dictionary 5 to complete the binding.

After the binding is completed, the window script program 2 displays the new binding label (for example, the report name of the new report) on the bound report display area 25 to notify that the binding is completed. When the user executes the window script program 2 next time, the window script program 2 will import the new report data 412 corresponding to the new binding tag.

Please refer to FIG. 8 , which is an embodiment of the system operation flowchart of the present invention. The process shown in FIG. 8 is applied to the SCADA system 1 , the window script program 2 and the window interface 20 shown in FIGS. 1 and 2 . The system operation process of the present invention includes a preloading stage and an editing stage.

In the preloading phase, the window script program 2 will first verify the user's authority (step S81). In one embodiment, the window script program 2 will open the editing areas 21-24 to provide report editing, storage and binding functions when it is judged that the user has editing authority (such as a factory manager or an electrical control engineer). If the window script program 2 judges that the user does not have the editing authority (such as a general operator), it only provides the report query and export functions, that is to say, the user who does not have the editing authority cannot modify the report format, content and field to edit.

Next, the window script program 2 judges whether there is a bound report (step S82). Specifically, the Windows script program 2 accesses the register of the variable dictionary 5 to determine whether there is a binding tag in the variable dictionary 5 . If there is a binding tag in the variable dictionary 5, then the window script program 2 obtains the report data corresponding to the binding tag from the editing file 41 according to the steps shown in FIG. 3 , and automatically imports a plurality of report elements in the report data. to the corresponding multiple editing areas 21-24 to be displayed on the window interface 20. If it is judged in step S82 that there is no bound report, then the window interface 20 displays blank editing areas 21, 23, ~24, wherein the window script program 2 reads from the machine file 42 according to the data table selected by the data table menu 214. Get multiple parameter fields corresponding to the data table, so as to import multiple parameter fields to the field menu 221 .

In the editing stage, the window script program 2 receives the user's operation through the report type menu 212 to select the required report type (step S83), and receives the user's operation through the historical report menu 213 to query from the edited file 41 multiple historical reports under the selected report category, and select one of the multiple historical reports (step S84). In one embodiment, the window script program 2 can automatically fill the report name of the historical report into the report name field 211 after importing the bound report data. In another embodiment, if the window script program 2 determines that there is no bound report, the user needs to input the report name into the report name field 211 .

After step S84, the window script program 2 imports the data table corresponding to the selected historical report into the data table menu 214 for selection by the user.

After the user completes the selection of the data table, the window script program 2 queries the multiple parameter fields included in the selected data table in the machine file 42 , and imports the multiple parameter fields to the field menu 221 . In this way, the window script program 2 can receive the user's operation through the field menu 221 to add, remove or shift the parameter field and simultaneously display it on the edit field preview 222 (step s85 ).

The window script program 2 can also receive user operations through the filter editing area 24 to set filter conditions for each parameter field. Wherein, the filter condition is used when the window script program 2 queries the machine file 42, and is used to limit the value range of the data. In one embodiment, the filter editing area 24 records the filter conditions as a series of SQL programs. In this embodiment, the filter editing area 24 can query the machine file 42 through the corresponding report module 3 using the filter conditions of the SQL program.

After step S85, the user can trigger the save column button 218 on the window interface 20 to save the current state of the window interface 20 as a new edited report, and store a new report data correspondingly to the edited file 41 (step S86) .

In addition, since the user has edited the report through steps S83 to S85 (that is, new report data 412 has been generated), the user can trigger the binding report button 215 on the window interface 20 to allow the window script program 2 to write Import the new binding tag corresponding to the new report data 412 into the temporary register of the variable dictionary 5, so as to bind the new report data 412 (step S87).

Please refer to FIG. 9 , which is an embodiment of the system operation process in FIG. 8 in the preloading stage of the present invention. The flow shown in Figure 9 is applied to the SCADA system 1 and the Windows script program 2 shown in Figures 1 and 2, and includes the following steps:

Step S91: Determine whether it is an operator? If yes, go to step S92; if not, go to step S94.

Step S92: Import the name of the report.

Step S93: Import the data table. Finish.

Step S94: Determine whether there is a binding tag? If yes, go to step S95; if not, end.

Step S95: Import the name of the report.

Step S96: importing report types.

Step S97: Import the data table.

Step S98: importing the field data of the report. Finish.

In step S91, the window script program 2 judges whether the currently logged-in user is an operator to verify the user's authority (that is, step S81 of FIG. 8 ). If it is judged that the currently logged-in user is an operator, the window script program 2 automatically imports any or specified historical reports from the edited file 41 in steps S92 and S93, and imports the report names and data tables of the historical reports to the window interface 20, and end the preloading phase. If it is determined that the currently logged-in user is not an operator, the window script program 2 determines in step S94 that there is a binding tag (that is, step S82 of FIG. 8 ). If it is judged that there is a binding label, the window script program 2 automatically imports the field data (ie, a plurality of parameter fields) of the report name, report type, data sheet and bound report in the window interface 20 in steps S95 to S98, And end the preload phase. If it is determined that there is no binding tag, the window script program 2 ends the preloading phase. In short, steps S91 to S93 of FIG. 9 are detailed steps of step S81 of FIG. 8 , and steps S91 to S94 are detailed steps of step S82 of FIG. 8 .

Please refer to FIG. 10 , which is an embodiment of the system operation flow in FIG. 8 in the editing stage of the present invention. The process shown in FIG. 10 is applied to the SCADA system 1, the window script program 2 and the window interface 20 shown in FIGS. 1 and 2, and includes the following steps:

Step S101: Select a report type.

Step S102: Determine whether there is a historical report? If yes, go to step S60; if not, go to step S56.

Step S103: Edit the name of the report.

Step S104: Select a data table. Go to step S68.

Step S105: Select a historical report.

Step S106: Import the name of the report.

Step S107: Import the data table.

Step S108: Import field data.

Step S109: Edit field data.

Step S110: Set filter conditions.

Step S111: Store the new report data.

Step S112: Binding new report data. Finish.

In step S101, the window script program 2 selects a report type according to user input. In step S102, the window script program 2 inquires whether there is a historical report in the edited file 41 according to the selected report type. If there are multiple historical reports, the window script program 2 automatically imports the report name, data table and field data (ie, multiple parameter fields) according to the selected historical reports in steps S105, S106, S107, and S108. If there is no historical report, the window script program 2 receives the user to edit the report name and select the data table through the window interface 20 in steps S103 and S104; in addition, the window script program 2 reads the edit column corresponding to the data table from the machine file 42 to import multiple parameter fields to the field menu 221.

In steps S109 and S110 , the window script program 2 receives the field data edited by the user and the filtering conditions set by the user through the window interface 20 . In steps S111 and S112, the window script program 2 stores the new report data and binds the new report data. For the detailed operations in FIG. 8 , FIG. 9 , and FIG. 10 , please refer to the relevant descriptions in FIG. 1 to FIG. 7 , and details are not repeated here.

To sum up, in the present invention, a plurality of items in a report data can be regarded as a plurality of bound label groups, and there is a binding relationship between them. The window script program 2 can query the relevant tag group (that is, time stamp, edit field, report type, data table and filter condition) in the database 4 through the bound tag (that is, the report name), and then a report All tags in the data are imported into the corresponding function, so that the window interface 20 can display the corresponding import results. When the user executes the window script program 2 next time and opens the same window interface 20, the window script program 2 can automatically import the bound edited report according to the aforementioned technical means. Moreover, the user can edit the edited report again (such as adjusting parameter fields and setting filter conditions, etc.), not limited to exporting report data with fixed fields and contents.

The above descriptions are only preferred specific examples of the present invention, and are not intended to limit the patent scope of the present invention. Therefore, all equivalent changes made by using the content of the present invention are all included in the scope of the present invention. bright.

S31~S36: Editing steps

Claims (15)

A report editing method for a SCADA system, comprising: a) judging by a window script program of the SCADA system whether there is a binding label in a temporary register of a variable dictionary of the SCADA system, wherein the binding label indicates A bound report is stored in a database; b) when the binding tag exists, the window script program queries an editing file of the SCADA system according to the binding tag to read the binding tag corresponding The report data of the bound report; c) When the binding tag does not exist, obtain multiple report elements through a window interface to create a new report, and save the multiple report elements as a new report data to the edit file and d) write a new binding tag corresponding to the new report data into the variable dictionary by the window script program, so as to bind the window interface and the new report. The report editing method of the SCADA system as described in claim item 1, wherein the report data and the new report data include the plurality of report elements respectively, and the plurality of report elements include a report name, a report type, a data table and multiple The step b) includes: b1) importing the plurality of report elements of the report data into the plurality of editing areas of the window interface. The report editing method of the SCADA system as described in claim item 2, wherein the binding tag is the name of the report. The report editing method of the SCADA system as described in claim item 2, wherein the multiple editing areas include: a report element editing area, including: a report name column, used to receive the report name; a report type menu, used to receive to select the report type; A historical report menu, used to receive operations to select a historical report; and a data table menu, used to receive operations to select the data table; a field editing area, including: a field menu, used to receive operations to select The plurality of parameter fields; and an edit field preview for previewing the plurality of parameter fields; a bound report display area for displaying the binding label or the new binding label. The report editing method of the SCADA system as described in claim 4, wherein the report name field is an input field; the report type menu, the historical report menu, the data table menu and the field menu are drop-down menus. The report editing method of the SCADA system as described in claim 4, wherein the SCADA system includes: a machine file for storing raw data; and a plurality of report modules based on SQL, one of the plurality of editing areas When one or the other is triggered, call one of the corresponding reporting modules to access the editing file and the machine file. The report editing method of the SCADA system as described in claim item 4, wherein the step b1) includes: b2) importing the report name to the historical report menu; b3) importing the report type to the report type menu; b4) importing import the data table into the data table menu; and b5) import the plurality of parameter fields into the field menu and the edit field preview. The report editing method of the SCADA system as described in claim item 7, wherein the plurality of report elements also include a filtering time; The multiple editing areas also include a time editing area for receiving operations to set the filter time, the filter time is a specific time or a period of time; and the step b1) also includes: b7) importing the filter time to the time editing area. The report editing method of the SCADA system as described in claim item 8, wherein the plurality of report elements also include at least one filter condition; the plurality of editing areas also include a filter editing area for receiving operations to set the at least one filter condition ; and the step b1) also includes: b6) importing the at least one filter condition into the filter editing area. The report editing method of the SCADA system as described in request item 9, wherein the method also includes: e1) according to the report name, the report type, the data table, the plurality of parameter fields and the filtering time, query a machine file and display an export report; or e2) query the machine file and display the report according to the report name, the report type, the data table, the plurality of parameter fields, the filter time and the at least one filter condition report. The report editing method of the SCADA system as described in claim 4, wherein in a preloading stage of the SCADA system, before the step a), the method also includes: a1) verifying a user's editing authority; a2) When the user has no editing authority, read and import the report name and the data sheet of the historical report to the window interface; a3) When the user has editing authority, execute step a) and step b );and a4) When the binding tag does not exist in the step c), end the preloading phase. The report editing method of the SCADA system as described in claim 11, wherein in an editing stage of the SCADA system, the method includes: e1) receiving an operation through the report type menu to select the report type; e2) according to the report type , query the historical report corresponding to the report type from the editing file; e3) When there is no historical report corresponding to the report type, including: receiving the report name through the report name field; receiving operations through the data table menu to select the data table; and query the multiple parameter fields corresponding to the data table from the editing file to import into the field menu; and e4) when there is the historical report corresponding to the report type, through the The historical report menu receives the historical report and performs the step b1). The report editing method of the SCADA system as described in claim item 12, wherein after the step e3) and the step e4), the method further includes: e5) selecting the plurality of parameter fields through the field menu receiving operation; e6 ) receiving an operation through a filter editing area to set at least one filter condition; e7) storing the received report name, the report type, the data table, the plurality of parameter fields and the at least one filter condition to the edit file, to add the new report data; and e8) writing the new binding tag corresponding to the new report data into the variable dictionary, so as to bind the window interface and the new report data. The report editing method of the SCADA system as described in claim item 4, wherein the column editing area also includes: an import all button, used to import all the multiple parameter fields included in the field menu into the edit field preview; a clear all button, used to preview the multiple parameter fields displayed in the edit field a delete field button, used to delete one of the plurality of parameter fields selected by the field menu from the edit field preview; and a forward shift button, used to preview the edit field from the edit field One of the plurality of parameter fields selected in the field menu is shifted forward to adjust the order of the plurality of parameter fields. The report editing method of the SCADA system as described in claim item 1, wherein the binding tag is recorded in the temporary register of the variable dictionary in the form of a string, if the variable dictionary is empty or there is an invalid string, then There is no binding tag; if there is a valid string in the variable dictionary, the binding tag exists.

Images