A data processing and storage method for building an equipment monitoring page

Abstract

The application discloses a kind of data processing storage methods for building equipment monitoring page, it is related to equipment monitoring technical field, obtains page component configuration before page component publishing and running, and it is judged whether component target purpose is matched with binding field, calculation rule and historical data range, so that only for the page component of running state display is saved page display data, the page component of involving pressure abnormality alarm, maintenance work order generation and abnormality trace is saved corresponding alarm basis data, order basis data and trace basis data, simultaneously, page component that does not satisfy purpose condition is excluded from the corresponding purpose, reduce the false alarm, false generation order and trace data missing problem caused by binding field incomplete, calculation rule missing or historical data range deficiency, and make operation and maintenance personnel can see the field value at that time, trigger time and historical data range.

Description

Technical Field

[0001] This invention relates to the field of equipment monitoring technology, specifically to a data processing and storage method for building an equipment monitoring page. Background Technology

[0002] With the increasing digital access of industrial equipment, energy equipment, building equipment, and production equipment, equipment monitoring pages have gradually evolved from simply displaying real-time values ​​to becoming data access points that support functions such as viewing operational status, identifying anomalies, processing work orders, assisting with shutdowns, and tracing historical data. How the data bound to components is processed and saved during the page construction process directly affects the reliability and traceability of subsequent monitoring results.

[0003] Currently, when building device monitoring pages, the focus is usually only on whether page components are bound to fields, whether fields can return data, and whether the page can be displayed correctly. However, there is a lack of unified verification of the data source, sampling period, calculation formula, threshold rules, unit rules, permission rules, and historical data range that the same component should meet under different uses such as display, alarm, work order, shutdown, or tracing. As a result, some components may be able to display data, but may not meet the conditions for being used as the basis for alarms, work orders, or shutdowns. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention provides a data processing and storage method for building a device monitoring page, thus solving the problems mentioned in the background section.

[0005] This invention is achieved through the following technical solution: a data processing and storage method for building a device monitoring page, comprising the following steps: S1. Obtain the page component configuration of the page components in the device monitoring page. The page component configuration includes component identifier, component target purpose, binding fields, calculation rules and historical data range. S2. Determine the component data requirements based on the component's target purpose. The component's target purpose is one of display purpose, alarm purpose, work order purpose, or traceability purpose. The component data requirements are used to indicate the conditions that the binding fields, the calculation rules, and the historical data range need to meet when the page component achieves the component's target purpose. S3. Determine the list of associated fields based on the binding fields, the calculation rules, and the historical data range, and determine whether the list of associated fields meets the component data requirements to obtain a component usage verification record. The component usage verification record includes records that meet the requirements or records that do not meet the requirements. S4. Determine the list of usable uses for the page component based on the component use verification record. When the component use verification record includes the satisfied record, add the component's target use to the list of usable uses. When the component use verification record includes the unsatisfied record, exclude the use corresponding to the unsatisfied record in the display use, alarm use, work order use, and traceability use from the list of usable uses. S5. Determine the data storage level and data storage content of the page component according to the list of usable uses, and store the page display data, alarm basis data, work order basis data or traceability basis data corresponding to the page component according to the data storage level and the data storage content.

[0006] Preferably, step S1 includes: S11. In the editing interface of the device monitoring page, receive one of the creation operation and selection operation of the page component, and generate the component identifier according to the saving order of the page components in the device monitoring page; S12. Read the purpose option, field option, calculation setting and historical query setting corresponding to the page component, determine the purpose option as the target purpose of the component, determine the field option as the bound field, determine the calculation setting as the calculation rule, and determine the historical query setting as the historical data range; S13. Write the component identifier, the component target purpose, the binding field, the calculation rule, and the historical data range into the same configuration record, and determine the configuration record as the page component configuration.

[0007] Preferably, step S2 includes: S21. When the target purpose of the component is the display purpose, the field identifier and real-time data table name corresponding to the bound field in the field table, and the write field name corresponding to the page component in the page data table are determined as the component data requirements. S22. When the target purpose of the component is the alarm purpose, the field identifier and the real-time data table name corresponding to the binding field in the field table, the calculation input field in the calculation rule, and the write field name corresponding to the page component in the alarm data table are determined as the component data requirements. S23. When the target purpose of the component is the work order purpose, the field identifier and the real-time data table name corresponding to the binding field in the field table, the calculation input field in the calculation rule, and the write field name corresponding to the page component in the work order data table are determined as the component data requirements. When the target purpose of the component is the traceability purpose, the field identifier corresponding to the binding field in the field table, the real-time data table name and the historical data table name, the calculation input field in the calculation rule, and the write field name corresponding to the page component in the traceability data table are determined as the component data requirements.

[0008] Preferably, in step S3, determining the list of associated fields includes: S31. Write the bound field into the associated field list; S32. When the calculation rule contains the calculation input field, parse the calculation rule, extract the calculation input field from the calculation rule, and write the calculation input field into the associated field list; S33. When the historical data range is not empty, the bound field and the calculation input field that need to be queried within the historical data range are written into the associated field list, and duplicate fields in the associated field list are retained only once.

[0009] Preferably, in step S3, generating the component usage verification record includes: S34. Determine the field table requirements, calculated field requirements, and historical data requirements based on the component data requirements. The field table requirements include the field identifier and the real-time data table name corresponding to the field in the associated field list. The calculated field requirements are generated when the component data requirements include the calculated input field. The calculated field requirements include that all the calculated input fields in the calculation rules exist in the associated field list. The historical data requirement is generated when the component data requirement includes the historical data table name, and the historical data requirement includes the existence of a historical record number that falls within the historical data range in the data table corresponding to the historical data table name; S35. Read the fields in the associated field list one by one, and query the field identifier and the real-time data table name corresponding to the fields in the associated field list in the field table; When the calculation field requirement has been generated, the calculation input field in the calculation rule is compared with the list of associated fields. When the historical data requirement has been generated, the historical record number that falls within the historical data range is queried in the data table corresponding to the historical data table name. S36. When all of the generated field table requirements, calculated field requirements, and historical data requirements are matched, a satisfactory record is generated. When at least one of the generated field table requirements, calculated field requirements, and historical data requirements is not matched, a non-satisfied record is generated, and one of the satisfactory record and the non-satisfied record is written into the component usage verification record.

[0010] Preferably, in step S36, generating the non-satisfied item record includes: S361. When the field table requirement is not matched, the field names in the associated field list that are not matched in the field table and the data table names that are not matched in the field table are written into the non-satisfied item record; S362. When the calculated field requirement is not matched, the calculated input field that is not matched in the associated field list is written into the unsatisfied item record; S363. When the historical data requirement is not matched, the field name of the historical record number that was not found and the corresponding historical data range are written into the unmet item record.

[0011] Preferably, step S4 includes: S41. The display purpose, alarm purpose, work order purpose and traceability purpose are respectively used as the purpose to be judged, and the component data requirements corresponding to each purpose to be judged are determined respectively; S42. Compare the list of associated fields with the component data requirements corresponding to each of the uses to be judged to obtain a use judgment record corresponding to each of the uses to be judged. The use judgment record is one of the satisfied record and the unsatisfied record. S43. Write the usage to be judged corresponding to the satisfied record into the list of usable uses, and exclude the usage to be judged corresponding to the unsatisfied record from the list of usable uses.

[0012] Preferably, in step S5, determining the data retention level includes: S51. Read the list of usable uses in the order of the traceability purpose, the work order purpose, the alarm purpose, and the display purpose; S52. When there is at least one use in the list of usable uses, the use that is first read in the list of usable uses is determined as the use for saving; when there is no use in the list of usable uses, the data saving level is determined as the non-saving level. S53. When the purpose of saving is the purpose of display, the data saving level is determined as the display saving level; When the purpose of saving is for alarm purposes, the data saving level is determined as the alarm saving level; when the purpose of saving is for work order purposes, the data saving level is determined as the work order saving level. When the purpose of the data storage is for traceability, the data storage level is determined to be the traceability storage level.

[0013] Preferably, in step S5, determining the data storage content includes: S54. When the data storage level is the display storage level, the page display data is determined as the data storage content. The page display data includes the field values ​​and corresponding display times displayed by the page component on the device monitoring page. S55. When the data storage level is the alarm storage level, the page display data and the alarm basis data are determined as the data storage content; When the data storage level is the work order storage level, the page display data, the alarm basis data, and the work order basis data are determined as the data storage content; The alarm basis data includes the field value that triggered the alarm and the alarm trigger time; the work order basis data includes the field value used when generating the work order and the work order generation time. S56. When the data storage level is the traceability storage level, the page display data, the alarm basis data, the work order basis data, and the traceability basis data are determined as the data storage content. The traceability basis data includes historical field values ​​used for traceability queries, the corresponding historical time range, and the component usage verification record. When the data storage level is the non-storage level, the data storage content is determined as an empty content list.

[0014] Preferably, in step S5, storing the data corresponding to the page component according to the data storage level and the data storage content includes: S57. When the data storage content is not the empty content list, determine the corresponding target data table list from the page data table, the alarm data table, the work order data table and the traceability data table according to the data storage content; S58. Write the data corresponding to the page components into the data tables in the target data table list, and record the component identifier, the purpose of saving, the data saving level and the component purpose verification record in the written data. S59. The records written into the target data table list are determined as the saved records of the page component. When the data saved content is the empty content list, the saved record is not generated.

[0015] This invention provides a data processing and storage method for building a device monitoring page, which has the following beneficial effects: (1) Before the page components are published and run, it is determined whether the target purpose of the component matches the bound fields, calculation rules and historical data range. This allows page components used only for displaying the running status to save the page display data, and page components involved in pressure abnormal alarms, maintenance work order generation and abnormal traceability to save the corresponding alarm basis data, work order basis data and traceability basis data. This reduces the problems of false alarms, false work orders and missing traceability data caused by incomplete bound fields, missing calculation rules or insufficient historical data range. It also enables maintenance personnel to clearly see the field values, trigger time and historical data range when viewing the exhaust pressure abnormality record.

[0016] (2) By organizing the binding fields, calculation rules and historical data range into a list of associated fields, and checking the field table, calculation input fields and historical record number item by item to see if they meet the component data requirements, a record of meeting or not meeting the requirements is formed. This allows the system to clearly know the specific reasons why a page component cannot be used for a certain purpose. For example, when the exhaust pressure component lacks a historical record number, it will not be used directly for traceability purposes. Instead, the corresponding field name, historical data range and the reason for not finding the historical record number will be written into the component purpose verification record, which will facilitate the subsequent location of missing configuration or missing data.

[0017] (3) By filtering the list of usable uses based on the component usage verification records, and determining the data storage level and data storage content in the order of traceability use, work order use, alarm use and display use, the exhaust pressure component can save the page display data, alarm basis data, work order basis data and traceability basis data when it meets the traceability use, and only save the page display data when it only meets the display use. This avoids page components that do not meet the data conditions from being used for pressure abnormality alarms, maintenance work order generation or abnormal traceability, and ensures that the content written into the page data table, alarm data table, work order data table and traceability data table is consistent with the actual usable use of the page component. Attached Figure Description

[0018] Figure 1 A schematic diagram of a data processing and storage method for building a device monitoring page; Figure 2 A diagram illustrating the process of configuring and validating the purpose of page components; Figure 3 This diagram illustrates the data preservation levels and data writing process. Detailed Implementation

[0019] The technical solutions of the present invention will now be clearly and completely described with reference to the accompanying drawings in the embodiments of the present invention.

[0020] Example 1

[0021] In a specific application scenario, a production workshop has been connected to an air compressor, an air tank, a refrigerated dryer, and a pipeline pressure sensor; Maintenance personnel need to set up an equipment monitoring page without changing the on-site equipment and data acquisition hardware; The equipment monitoring page includes page components for displaying exhaust pressure, exhaust temperature, operating status, and fault information. Some page components are used only for displaying the running status, some page components are used for pressure abnormality alarms, some page components are used to generate maintenance work orders, and some page components are used for subsequent querying of historical data before and after the abnormality occurred. Because different page components have different uses, their bound fields, calculation rules, and historical data ranges need to meet different data conditions. Therefore, before a page component is published and run, the bound fields, calculation rules, and historical data range need to be validated according to the target purpose of the page component, and the actual use, data storage level, and data storage content of the page component should be determined based on the validation results.

[0022] This invention provides a data processing and storage method for building a device monitoring page. Please refer to [link / reference]. Figure 1 This includes the following steps: S1. Obtain the page component configuration of the page components in the device monitoring page. The page component configuration includes component identifier, component target purpose, binding fields, calculation rules and historical data range. S2. Determine the component data requirements based on the component's target purpose. The component's target purpose is one of display purpose, alarm purpose, work order purpose, or traceability purpose. The component data requirements are used to indicate the conditions that the binding fields, the calculation rules, and the historical data range need to meet when the page component achieves the component's target purpose. S3. Determine the list of associated fields based on the binding fields, the calculation rules, and the historical data range, and determine whether the list of associated fields meets the component data requirements to obtain a component usage verification record. The component usage verification record includes records that meet the requirements or records that do not meet the requirements. S4. Determine the list of usable uses for the page component based on the component use verification record. When the component use verification record includes the satisfied record, add the component's target use to the list of usable uses. When the component use verification record includes the unsatisfied record, exclude the use corresponding to the unsatisfied record in the display use, alarm use, work order use, and traceability use from the list of usable uses. S5. Determine the data storage level and data storage content of the page component according to the list of usable uses, and store the page display data, alarm basis data, work order basis data or traceability basis data corresponding to the page component according to the data storage level and the data storage content.

[0023] In this embodiment, by using the above method, before the page component is published and run, it can be determined whether the target purpose of the component matches the bound fields, calculation rules, and historical data range. This allows page components used only for displaying the running status to save the page display data, while page components involved in pressure anomaly alarms, maintenance work order generation, and anomaly tracing save the corresponding alarm basis data, work order basis data, and tracing basis data. This reduces the problems of false alarms, false work order generation, and missing tracing data caused by incomplete bound fields, missing calculation rules, or insufficient historical data range. It also enables maintenance personnel to clearly see the field values, trigger times, and historical data ranges when viewing the exhaust pressure anomaly records.

[0024] Example 2

[0025] Please see Figure 2 Specifically, step S1 includes: S11. In the editing interface of the device monitoring page, receive one of the creation operation and selection operation of the page component, and generate the component identifier according to the saving order of the page components in the device monitoring page; Specifically: In the air compressor station equipment monitoring page set in Example 1, the equipment monitoring page has a unique page number. The creation operation of the page component is the operation of the maintenance personnel to drag the exhaust pressure component, exhaust temperature component, operating status component or fault information component from the component library. The selection operation of the page component is the operation of the maintenance personnel to click the exhaust pressure component, exhaust temperature component, operating status component or fault information component that has been saved in the equipment monitoring page. During data processing, the existing component record corresponding to the page number is queried in the page component table. When the creation operation is received, the maximum save order in the existing component record is incremented by one to become the save order of the current page component. When the selection operation is received, the save order of the selected page component already saved in the page component table is read. The component identifier is formed by concatenating the page number, the connection character, and the saving order in sequence. The connection character is pre-saved by the configuration table and is used to separate the page number and the saving order. The generated component identifier is written into the component identifier column of the page component table, and the written field value is used as a fixed identifier for subsequent queries of the same page component.

[0026] S12. Read the purpose option, field option, calculation setting and historical query setting corresponding to the page component, determine the purpose option as the target purpose of the component, determine the field option as the bound field, determine the calculation setting as the calculation rule, and determine the historical query setting as the historical data range; Specifically: In the component attribute area of ​​the page component, the purpose option is generated by the purpose drop-down box. The selectable values ​​of the purpose drop-down box are pre-stored by a dictionary table. The selectable values ​​of the purpose drop-down box only include display purpose, alarm purpose, work order purpose and traceability purpose. The field value selected by the operation and maintenance personnel in the purpose drop-down box is written into the target purpose of the component. During data processing, field options are generated from device field drop-down boxes. The data in the device field drop-down boxes comes from a field table, which includes at least a device number column, a field name column, a field identifier column, a real-time data table name column, and a historical data table name column. The field name column is filtered from the field table according to the current device number, and the field name selected by the maintenance personnel in the device field drop-down box is written into the bound field. During data processing, the calculation settings are generated by the calculation condition input area, which includes a calculation input field input box, a comparison method drop-down box, and a comparison benchmark value input box. The selectable values ​​of the comparison method drop-down box are pre-stored in a dictionary table, and the selectable values ​​of the comparison method drop-down box only include greater than, less than, equal to, not equal to, greater than or equal to, and less than or equal to. The value entered in the comparison benchmark value input box is selected from the minimum allowed value column and the maximum allowed value column in the field table. When the entered value is less than the value corresponding to the minimum allowed value column or greater than the value corresponding to the maximum allowed value column, the entered value is not written into the calculation rule, and a prompt is displayed on the page to enter it again. During data processing, the historical query settings are generated by the historical query time input area, which includes a start time input box and an end time input box. The time values ​​of the start time input box and the end time input box are written into the historical data range. When the time value of the start time input box is later than the time value of the end time input box, it is not written into the historical data range, and a prompt is displayed on the page to fill it in again. Therefore, the selected value in the purpose drop-down box is determined as the target purpose of the component, the selected field name in the device field drop-down box is determined as the binding field, the calculation input field, the comparison method and the comparison benchmark value are combined to form the calculation rule, and the start time and the end time are combined to form the historical data range.

[0027] S13. Write the component identifier, the component target purpose, the binding field, the calculation rule, and the historical data range into the same configuration record, and determine the configuration record as the page component configuration; Specifically: Add a new record to the page component configuration table. The page component configuration table includes a component identifier column, a component target purpose column, a binding field column, a calculation rule column, a historical data range column, and a record generation time column. Write the component identifier into the component identifier column, write the component target purpose column into the component target purpose column, write the binding field into the binding field column, write the calculation input field, comparison method, and comparison benchmark value in the calculation rule into the calculation rule column, write the start time and end time in the historical data range column into the historical data range column, and write the current time into the record generation time column. Before writing to the page component configuration table, the page component configuration table is queried according to the component identifier. If no record containing the component identifier is found, a new record is added. If a record containing the component identifier is found, the component target purpose column, binding field column, calculation rule column, historical data range column and record generation time column in the record are overwritten. The written record is identified as the page component configuration, and the component identifier, the component target purpose, the binding field, the calculation rule, and the historical data range in the page component configuration are used as data inputs for subsequent steps.

[0028] Step S2 includes: S21. When the target purpose of the component is the display purpose, the field identifier and real-time data table name corresponding to the bound field in the field table, and the write field name corresponding to the page component in the page data table are determined as the component data requirements. Specifically: When the target purpose of the component is the display purpose, the bound field is used as the query condition to query records in the field name column of the field table whose character values ​​are the same as those of the bound field character by character. The character-by-character same means that the number of characters, the order of characters and the character code of each character in the field name column are the same as those of the bound field. During data processing, when a record with a character value that is identical to the bound field is found in the field table, the field identifier column and the real-time data table name column in the record are read. When no record with a character value that is identical to the bound field is found in the field table, the field is not registered in the component data requirement table. Using the component identifier as the query condition, search for records in the component identifier column of the page data table whose character values ​​are identical to the component identifier character by character. When a record is found in the page data table, read the write field name column in that record. When no record is found in the page data table, write the missing content of the page data write position in the component data requirement table. When the field identifier column, the real-time data table name column, and the write field name column are read, the field values ​​of the field identifier column, the real-time data table name column, and the write field name column are written to the same row of the component data requirement table, and this row of the record is identified as the component data requirement corresponding to the display purpose.

[0029] S22. When the target purpose of the component is the alarm purpose, the field identifier and the real-time data table name corresponding to the binding field in the field table, the calculation input field in the calculation rule, and the write field name corresponding to the page component in the alarm data table are determined as the component data requirements. Specifically: when the target purpose of the component is the alarm purpose, the bound field is used as the query condition to query records in the field name column of the field table whose character values ​​are the same as those in the bound field character by character, and the field identifier column and real-time data table name column of the queried records are read. During data processing, the calculation rules are parsed. The calculation rules include the calculation input field, comparison method, and comparison benchmark value. It is determined whether the calculation input field is empty. When the calculation input field is empty, the missing content of the calculation input field is written into the component data requirement table. When the calculation input field is not empty, records whose character values ​​are identical to those of the calculation input field are queried in the field name column of the field table. Using the component identifier as the query condition, the alarm data table queries records whose character values ​​are identical to the component identifier character by character in the component identifier column. The alarm data table includes at least a component identifier column, a write field name column, an alarm trigger time column, and a trigger field value column. When a record is found in the alarm data table, the write field name column, alarm trigger time column, and trigger field value column in the record are read. When no record is found in the alarm data table, the missing alarm data write position content is written to the component data requirement table. When the field identifier column, real-time data table name column, calculation input field, comparison method, comparison benchmark value, write field name column, alarm trigger time column, and trigger field value column are read, the above contents are written to the same row of the component data requirement table, and the row of the record is identified as the component data requirement corresponding to the alarm purpose.

[0030] S23. When the target purpose of the component is the work order purpose, the field identifier and the real-time data table name corresponding to the binding field in the field table, the calculation input field in the calculation rule, and the write field name corresponding to the page component in the work order data table are determined as the component data requirements. Specifically: when the target purpose of the component is the purpose of the work order, the binding field is used as the query condition to query records in the field name column of the field table whose character values ​​are the same as those in the binding field character by character, and the field identifier column and real-time data table name column of the queried records are read. During data processing, the calculation input field, comparison method, and comparison benchmark value in the calculation rules are parsed. If the calculation input field is empty, the missing content of the calculation input field is written into the component data requirement table. If the calculation input field is not empty, records whose character values ​​are identical to those of the calculation input field are queried in the field name column of the field table. Using the component identifier as the query condition, the system queries the component identifier column of the work order data table for records whose character values ​​are identical to the component identifier character by character. The work order data table includes at least a component identifier column, a write field name column, a work order generation time column, and a work order trigger field value column. When a record is found in the work order data table, the write field name column, work order generation time column, and work order trigger field value column of that record are read. When no record is found in the work order data table, the system writes the missing content of the work order data write position into the component data requirement table. When the field identifier column, real-time data table name column, calculation input field, comparison method, comparison benchmark value, write field name column, work order generation time column, and work order trigger field value column are read, the above contents are written into the same row of the component data requirement table, and the row of the record is identified as the component data requirement corresponding to the purpose of the work order.

[0031] When the target purpose of the component is the traceability purpose, the field identifier, the real-time data table name and the historical data table name corresponding to the binding field in the field table, the calculation input field in the calculation rule, and the write field name corresponding to the page component in the traceability data table are determined as the component data requirements; Specifically: when the target purpose of the component is the traceability purpose, the binding field is used as the query condition to query records in the field name column of the field table whose character values ​​are the same as those in the binding field character by character, and the field identifier column, real-time data table name column and historical data table name column in the queried records are read. During data processing, the start time and end time of the historical data range are read, and the field value in the historical data table name column is used as the data table name. Records whose record time is not earlier than the start time and not later than the end time are queried in the data table. The historical record number column of the queried records is read. When the historical record number column is not found, the missing historical record content is written into the component data requirement table. The calculation input field, comparison method, and comparison benchmark value in the calculation rule are parsed. If the calculation input field is empty, the binding field is written as the calculation input field into the component data requirement table. If the calculation input field is not empty, records whose character values ​​are the same as those of the calculation input field are queried in the field name column of the field table. Using the component identifier as the query condition, the system queries the component identifier column of the traceability data table for records whose character values ​​are identical to the component identifier character by character. The traceability data table includes at least a component identifier column, a write field name column, a historical time range column, and a historical field value column. When a record is found in the traceability data table, the write field name column, historical time range column, and historical field value column of that record are read. When no record is found in the traceability data table, the system writes the missing traceability data write position content into the component data requirement table. When the field identifier column, real-time data table name column, historical data table name column, historical record number column, calculation input field, write field name column, historical time range column, and historical field value column are read, the above contents are written into the same row of the component data requirement table, and the row of the record is identified as the component data requirement corresponding to the traceability purpose.

[0032] In this embodiment, the creation, selection, purpose, field, calculation, and historical query settings of page components in the editing interface are converted into a single page component configuration. Furthermore, corresponding component data requirements are formed based on the component's target purpose. This ensures that the display purpose, alarm purpose, work order purpose, and traceability purpose correspond to specific fields and write locations in the field table, page data table, alarm data table, work order data table, or traceability data table, respectively. This avoids page components only completing the appearance configuration but lacking subsequent data sources and storage locations, facilitating unified configuration, verification, and subsequent storage of different page components such as exhaust pressure and exhaust temperature components in the air compressor station page.

[0033] Example 3

[0034] Please see Figure 2 Specifically: In step S3, determining the list of associated fields includes: S31. Write the bound field into the associated field list; Specifically: In the air compressor station equipment monitoring page set in Example 1, the bound field column in the page component configuration table is read. If the field value of the bound field column is the exhaust pressure field, the exhaust pressure field is written into the field name column of the associated field list. During data processing, the associated field list includes at least a component identifier column, a field name column, a field source column, and a write order column. The component identifier in the page component configuration table is written to the component identifier column of the associated field list, the bound field is written to the field name column of the associated field list, the field source column is written to the directly bound field, and the write order column is written to 1. It should be noted that the field names in the associated field list are written character by character. This means that the written field names and the bound fields are identical in terms of the number of characters, the order of characters, and the character encoding of each character. After writing, the associated field list is read using the component identifier and the field name as query conditions. If a corresponding record is found, that record is written as the result of the bound field.

[0035] S32. When the calculation rule contains the calculation input field, parse the calculation rule, extract the calculation input field from the calculation rule, and write the calculation input field into the associated field list; Specifically: Read the calculation rule column in the page component configuration table. The calculation rule column includes the calculation input field, comparison method and comparison benchmark value. First, determine whether the calculation input field is empty. If the calculation input field is empty, do not write the calculation input field to the associated field list. If the calculation input field is not empty, write the calculation input field to the field name column of the associated field list. During data processing, the input field for calculation can be one field name or multiple field names. When the input field for calculation is multiple field names, the multiple field names are split according to the field separator in the calculation rule column. The field separator is stored in the configuration table. The split field names are obtained one by one, and each field name is written into the associated field list. It should be noted that when writing each calculated input field, the component identifier is written to the component identifier column of the associated field list, the field source column is written to the calculated input field, and the writing order column is written to the order in which the calculated input field is arranged in the calculation rule column. After writing is completed, the associated field list is read using the component identifier and field name as query conditions. If the corresponding record is found, the record is written as the calculated input field in the result.

[0036] S33. When the historical data range is not empty, the bound field that needs to be queried within the historical data range is written into the associated field list. When the calculation input field is not empty, the calculation input field that needs to be queried within the historical data range is written into the associated field list. Duplicate fields in the associated field list are retained only once. Specifically: Read the historical data range column in the page component configuration table. The historical data range column includes the start time and the end time. When both the start time and the end time exist, it is determined that the historical data range is not empty. During data processing, the bound fields are written to the associated field list, and the calculation input fields in the calculation rules are read. When the calculation input field is not empty, the calculation input field is written to the associated field list, and the field source column of the above-mentioned written record is written to the historical query field. It should be noted that when processing duplicate fields in the associated field list, the component identifier and field name are used as the duplicate judgment conditions. When the component identifier and field name of two records are identical character by character, the record with the smaller writing order is retained, the record with the larger writing order is deleted, and the retained record is determined as the valid record in the associated field list.

[0037] In step S3, generating the component usage verification record includes: S34. Determine the field table requirements, calculated field requirements, and historical data requirements based on the component data requirements. The field table requirements include the field identifier and the real-time data table name corresponding to the field in the associated field list. The calculated field requirements are generated when the component data requirements include the calculated input field. The calculated field requirements include that all the calculated input fields in the calculation rules exist in the associated field list. Specifically: Read the component data requirements corresponding to the current component identifier in the component data requirement table. If the component data requirements contain field identifiers and real-time data table names, then generate field table requirements. The validation object of the field table requirements is the field table. The validation content of the field table requirements is that there is a field name record in the field table that is identical to the field name in the associated field list character by character, and the field identifier column and the real-time data table name column in the record are not empty values. During data processing, if the component data requirements include calculated input fields, then calculated field requirements are generated. The verification object of the calculated field requirements is the list of associated fields, and the verification content of the calculated field requirements is that each calculated input field in the calculation rule can be found in the field name column of the list of associated fields with the same field name record character by character. It should be noted that when the component data requirements do not include calculated input fields, calculated field requirements are not generated, and the calculated field requirements will not be matched when the component usage validation record is generated subsequently.

[0038] The historical data requirement is generated when the component data requirement includes the historical data table name, and the historical data requirement includes the existence of a historical record number that falls within the historical data range in the data table corresponding to the historical data table name; Specifically: When the component data requirement includes the name of a historical data table, a historical data requirement is generated. The verification object of the historical data requirement is the data table corresponding to the historical data table name. The verification content of the historical data requirement is that there is a historical record number in the data table whose record time is no earlier than the start time and no later than the end time in the historical data range. During data processing, if the component data requirements do not include the name of the historical data table, then no historical data requirements will be generated, and the historical data requirements will not be matched when the component usage verification record is generated subsequently. It should be noted that whether the recorded time falls within the historical data range is determined by a closed interval method. The closed interval method means that if the recorded time is equal to the start time, it is included in the historical data range, and if the recorded time is equal to the end time, it is also included in the historical data range.

[0039] S35. Read the fields in the associated field list one by one, and query the field identifier and the real-time data table name corresponding to the fields in the associated field list in the field table; Specifically: Read the field names one by one in the order they were written in the list of related fields, and use the read field names as the query conditions to query records with identical characters in the field name column of the field table; During data processing, if a record with the same field name character by character is found in the field table, the field identifier column and the real-time data table name column of the record are read, and the field name, field identifier, and real-time data table name are written into the field validation content column of the component purpose validation record. If no record with the same field name is found in the field table, or if the field identifier column of the found record is empty, or if the real-time data table name column of the found record is empty, then the field name will be written into the non-compliance column of the component purpose validation record.

[0040] When the calculation field requirement has been generated, the calculation input field in the calculation rule is compared with the list of associated fields. When the historical data requirement has been generated, the historical record number that falls within the historical data range is queried from the data table corresponding to the historical data table name. Specifically: When the calculated field requirements have been generated, read each calculated input field in the calculation rule, and use each calculated input field as a query condition to query records that are identical character by character in the field name column of the associated field list; During data processing, if each calculated input field has a record with the same field name character by character in the associated field list, the required verification status of the calculated field is written as matched. If no calculated input field has a record with the same field name character by character in the associated field list, the calculated input field is written as the unsatisfied item column of the component purpose verification record, and the required verification status of the calculated field is written as unmatched. When historical data requirements have been generated, the historical data table name is read, and the corresponding data table is read using the historical data table name as the data table name. Then, the start and end times in the historical data range are used as query conditions to query the historical record numbers in the data table whose record times fall within the historical data range. If at least one historical record number is found, the verification status of the historical data requirement is written as "matched". If no historical record number is found, the historical data range and the historical data table name are written to the "unsatisfied" column of the component purpose verification record, and the verification status of the historical data requirement is written as "unmatched".

[0041] S36. When all of the generated field table requirements, calculated field requirements, and historical data requirements are matched, a satisfactory record is generated. When at least one of the generated field table requirements, calculated field requirements, and historical data requirements is not matched, a non-satisfied record is generated, and one of the satisfactory record and the non-satisfied record is written into the component usage verification record. Specifically: When generating component usage verification records, set verification status columns for field table requirements, calculated field requirements, and historical data requirements respectively. The values ​​of the verification status columns only include matched, unmatched, and not generated. During data processing, when the validation status of the requirements generated in the field table requirements, calculated field requirements, and historical data requirements are all matched, a satisfactory record is generated and written to the record type column of the component purpose validation record. During data processing, if the validation status of any of the generated requirements from the field table requirements, calculated field requirements, and historical data requirements is "not matched", a non-compliant item record is generated and written to the record type column of the component purpose validation record. At the same time, the name of the non-matching requirement and the non-matching content are written to the non-compliant item column of the component purpose validation record.

[0042] In step S36, generating the non-satisfied item record includes: S361. When the field table requirement is not matched, the field names in the associated field list that are not matched in the field table and the data table names that are not matched in the field table are written into the non-satisfied item record; Specifically: When the validation status required by the field table is unmatched, read the unmatched field name. The unmatched field name is the field name for which no record with the same character was found in the field name column of the field table, or the field name for which a record with the same character was found but the field identifier column is empty, or the field name for which a record with the same character was found but the real-time data table name column is empty. During data processing, unmatched field names are written to the field name column of the record that does not meet the requirements, the field table is written to the data source column of the record that does not meet the requirements, and field names that do not exist, field identifiers that are null, or real-time data table names that are null are written to the reason column of the record that does not meet the requirements. It should be noted that when the real-time data table name column is empty, the real-time data table name will be written to the data table name column of the record that does not meet the requirements. When the field name does not exist in the field table, the data table name column will be written with an empty value.

[0043] S362. When the calculated field requirement is not matched, the calculated input field that is not matched in the associated field list is written into the unsatisfied item record; Specifically: When the required validation status of the calculated field is unmatched, read the unmatched calculated input field. The unmatched calculated input field is the field name that exists in the calculation rule but no record with the same character can be found in the field name column of the associated field list. During data processing, unmatched calculation input fields are written to the field name column of the record that does not meet the requirements, calculation rules are written to the data source column of the record that does not meet the requirements, and the reason why the calculation input fields are not written to the list of associated fields is written to the reason column of the record that does not meet the requirements. It should be noted that if there are multiple calculation input fields in the calculation rule, records of non-compliance items will be generated one by one, and each record of non-compliance item will only be written to one unmatched calculation input field.

[0044] S363. When the historical data requirement is not matched, the field name of the historical record number that was not found and the corresponding historical data range are written into the unsatisfied item record. Specifically: When the verification status of historical data is not matched, read the historical data table name and historical data range, and query the historical record number whose record time falls within the historical data range in the data table corresponding to the historical data table name; During data processing, if the historical record number is not found, write the field name that needs to be queried into the field name column of the record that does not meet the requirements, write the historical data table name into the data source column of the record that does not meet the requirements, write the historical data range into the time range column of the record that does not meet the requirements, and write the reason why the historical record number was not found into the reason column of the record that does not meet the requirements. It should be noted that if the field names for the historical query include both bound fields and calculated input fields, then separate records of non-satisfied items will be generated for each bound field and each calculated input field, and only one field name will be written for each non-satisfied item record.

[0045] In this embodiment, the binding fields, calculation rules, and historical data ranges are organized into a list of associated fields. Each field table, calculation input field, and historical record number is checked to see if they meet the component data requirements. This forms a record of whether the requirements are met or not, allowing the system to clearly know the specific reason why a page component cannot be used for a certain purpose. For example, if the exhaust pressure component lacks a historical record number, it will not be used directly for traceability purposes. Instead, the corresponding field name, historical data range, and reason for not finding the historical record number are written into the component purpose verification record, which facilitates the subsequent location of missing configurations or missing data.

[0046] Example 4

[0047] Please see Figure 3 Specifically, step S4 includes: S41. The display purpose, alarm purpose, work order purpose and traceability purpose are respectively used as the purpose to be judged, and the component data requirements corresponding to each purpose to be judged are determined respectively; Specifically: In the air compressor station equipment monitoring page set in Example 1, the display purpose, alarm purpose, work order purpose and traceability purpose are read from the purpose dictionary table. The purpose dictionary table includes at least a purpose name column and a purpose activation status column. Only the purpose name that is enabled in the purpose activation status column is read. During the data processing, the read display purpose, alarm purpose, work order purpose and traceability purpose are written into the purpose to be judged table one by one. The purpose to be judged table includes at least a component identifier column, a purpose to be judged column and a processing order column. It should be noted that the processing order column is generated according to the order in which the display purpose, alarm purpose, work order purpose, and traceability purpose are written. The processing order column is only used to process the purpose to be judged item by item, and is not used to determine the data retention level. For each application to be determined, the component data requirements corresponding to that application are regenerated according to the processing method of steps S21 to S23 in Embodiment 2, and the application to be determined, the field identifier corresponding to that application, the real-time data table name, the historical data table name, the calculation input field, and the write field name are written into the same row of the component data requirements table.

[0048] S42. Compare the list of associated fields with the component data requirements corresponding to each of the uses to be judged to obtain a use judgment record corresponding to each of the uses to be judged. The use judgment record is one of the satisfied record and the unsatisfied record. Specifically: Read the uses to be judged one by one according to the processing order column in the use to be judged table, and read the component data requirements corresponding to the use to be judged; During the data processing, following the processing method of steps S35 to S36 in Example 3, the field names in the associated field list are compared item by item with the field identifiers, real-time data table names, historical data table names, calculation input fields, and write field names in the component data requirements. It should be noted that the field names are compared using a character-by-character matching method. Character-by-character matching means that the number of characters, the order of characters, and the character encoding of each character in the two field names being compared are all the same. Generate a usage judgment record for each usage to be judged. The usage judgment record shall include at least a component identifier column, a usage to be judged column, a record type column, and a non-satisfied item column. When all items in the component data requirements corresponding to the purpose to be judged are matched, the record type column is written to the matching record, and the non-matching item column is written to null. When there are unmatched items in the component data requirements corresponding to the purpose to be judged, the record type column is written to the unsatisfied item record, and the unmatched field name, data table name, calculation input field or historical data range is written to the unsatisfied item column.

[0049] S43. Write the usage to be judged corresponding to the satisfied record into the usable usage list, and exclude the usage to be judged corresponding to the unsatisfied record from the usable usage list; Specifically: Read the record type column of each record one by one to determine its purpose; During data processing, when the record type column is a satisfactory record, the purpose to be judged in the same purpose judgment record is written into the purpose name column of the usable purpose list; When the record type column is a non-compliant record, the pending compliant use in the same compliant use judgment record is not written into the usable use list, and the pending compliant use and the contents of the non-compliant use column are written into the compliant use exclusion record table; It should be noted that the list of usable uses should include at least a component identifier column and a use name column, and the use exclusion record table should include at least a component identifier column, an excluded use column, and an exclusion reason column. Therefore, the list of usable uses retains only the uses that have been satisfied, while the list of excluded uses stores the uses of records that have been unsatisfied and the unsatisfied content.

[0050] In step S5, determining the data preservation level includes: S51. Read the list of usable uses in the order of the traceability purpose, the work order purpose, the alarm purpose, and the display purpose; Specifically: The purpose and reading order are pre-stored in a save level dictionary table, which includes at least a purpose name column, a reading order column, and a save level name column; In this embodiment, the reading order for traceability purposes is the first order, the reading order for work orders is the second order, the reading order for alarm purposes is the third order, and the reading order for display purposes is the fourth order. It should be noted that the above reading order indicates that the data retention level is determined by prioritizing the use of more complete content to be saved; for traceability purposes, page display data, alarm basis data, work order basis data, and traceability basis data need to be saved; for work order purposes, page display data, alarm basis data, and work order basis data need to be saved; for alarm purposes, page display data and alarm basis data need to be saved; and for display purposes, page display data needs to be saved. Search the usage name column in the list of available uses in the order of reading, from the first to the fourth.

[0051] S52. When there is at least one use in the list of usable uses, the use that is first read in the list of usable uses is determined as the use for saving; when there is no use in the list of usable uses, the data saving level is determined as the non-saving level. Specifically: In the list of available uses, search the use name column in the following order: traceability use, work order use, alarm use, and display use; During data processing, if the traceability purpose is found in the list of usable purposes, the traceability purpose will be written into the storage basis purpose. If the traceability purpose is not found but the work order purpose is found, then the work order purpose will be written into the storage basis purpose. If neither the traceability purpose nor the work order purpose can be found, but the alarm purpose can be found, then the alarm purpose will be written to the storage basis purpose. If the traceability purpose, work order purpose, and alarm purpose are not found, but the display purpose is found, then the display purpose will be written to the storage basis purpose. If the display purpose, alarm purpose, work order purpose, and traceability purpose are not found in the list of available purposes, then the data retention level will be set to "not retain" and the retention basis purpose will be set to null.

[0052] S53. When the purpose of saving is the purpose of display, the data saving level is determined as the display saving level; Specifically: Read the storage basis for purpose. When the storage basis for purpose is display purpose, query the storage level dictionary table for records where the purpose name column is display purpose, and write the storage level name column of that record into the data storage level. In this embodiment, the display storage level name column corresponding to the purpose is set to display storage level; the display storage level is written to the data storage level column.

[0053] When the purpose of saving is the alarm purpose, the data saving level is determined as the alarm saving level; Specifically: Read the storage basis purpose. When the storage basis purpose is alarm purpose, query the storage level dictionary table for records where the purpose name column is alarm purpose, and write the storage level name column of the record into the data storage level. In this embodiment, the alarm storage level name column corresponding to the alarm purpose is the alarm storage level, and the alarm storage level is written into the data storage level column.

[0054] When the purpose of saving is the purpose of the work order, the data saving level is determined as the work order saving level; Specifically: Read the storage basis purpose. When the storage basis purpose is work order purpose, query the storage level dictionary table for records whose purpose name column is work order purpose, and write the storage level name column of the record into the data storage level. In this embodiment, the work order's purpose corresponds to the work order's storage level name column, which is then written into the data storage level column.

[0055] When the purpose of the data storage is for traceability, the data storage level is determined to be the traceability storage level. Specifically: Read the storage basis purpose. When the storage basis purpose is retrospective purpose, query the storage level dictionary table for records where the purpose name column is retrospective purpose, and write the storage level name column of the record into the data storage level. In this embodiment, the storage level name column corresponding to the traceability purpose is the traceability storage level, and the traceability storage level is written into the data storage level column.

[0056] In step S5, determining the data storage content includes: S54. When the data storage level is the display storage level, the page display data is determined as the data storage content. The page display data includes the field values ​​and corresponding display times displayed by the page component on the device monitoring page. Specifically: When the data retention level is set to the display retention level, the component identifier and bound fields are read from the page component configuration table, and the field values ​​of the bound fields at the current collection time are read from the data table corresponding to the real-time data table name. During data processing, the field value and the current time are written into the page display data, with the current time serving as the display time; It should be noted that the data displayed on the page should include at least the component identifier column, field name column, field value column, and display time column; Write the data displayed on the page into the data content column of the data storage table, and write the data type column into the data displayed on the page.

[0057] S55. When the data storage level is the alarm storage level, the page display data and the alarm basis data are determined as the data storage content; Specifically: When the data retention level is alarm retention level, first generate the page display data according to step S54, and then read the calculation input field, comparison method and comparison benchmark value in the calculation rule; During data processing, the field values ​​of the input fields are read from the data table corresponding to the real-time data table name, and the field values ​​are compared with the comparison benchmark value according to the comparison method. It should be noted that when the comparison method is greater than, alarm data is generated if the field value is greater than the comparison benchmark value; when the comparison method is less than, alarm data is generated if the field value is less than the comparison benchmark value; when the comparison method is equal to, alarm data is generated if the field value is equal to the comparison benchmark value; when the comparison method is not equal to, alarm data is generated if the field value is not equal to the comparison benchmark value; when the comparison method is greater than or equal to, alarm data is generated if the field value is greater than or equal to the comparison benchmark value; and when the comparison method is less than or equal to, alarm data is generated if the field value is less than or equal to the comparison benchmark value. The alarm data should include at least the component identifier column, the trigger field name column, the trigger field value column, the comparison method column, the comparison base value column, and the alarm trigger time column. Write the page display data and alarm basis data into the data content column of the data storage table, and write the data type column into the page display data and alarm basis data respectively.

[0058] When the data storage level is the work order storage level, the page display data, the alarm basis data, and the work order basis data are determined as the data storage content; Specifically: When the data retention level is the work order retention level, first generate the page display data according to step S54, and then generate the alarm basis data according to the processing method under the alarm retention level; During data processing, the component identifier column of the work order data table is read. When there is a record in the work order data table that is identical to the component identifier character by character, the field value used when generating the work order and the current time are written into the work order basis data. It should be noted that the data used for a work order should include at least the following columns: component identifier, work order trigger field name, work order trigger field value, and work order generation time. Write the page display data, alarm basis data, and work order basis data into the data content column of the data storage table, and write the data type column into the page display data, alarm basis data, and work order basis data, respectively.

[0059] The alarm basis data includes the field value that triggered the alarm and the alarm trigger time; the work order basis data includes the field value used when generating the work order and the work order generation time. Specifically: the field value that triggers the alarm is the current field value of the input field in the data table corresponding to the real-time data table name, and the alarm trigger time is the current time when the alarm is generated based on the data. The field values ​​used when generating the work order are the field values ​​of the calculated input fields read when generating the work order, and the work order generation time is the current time when the data used to generate the work order is used. It should be noted that both the alarm trigger time and the work order generation time are generated by the server time, which is provided uniformly by the device monitoring platform.

[0060] S56. When the data storage level is the traceability storage level, the page display data, the alarm basis data, the work order basis data, and the traceability basis data are determined as the data storage content. The traceability basis data includes historical field values ​​used for traceability query, the corresponding historical time range, and the component usage verification record. When the data storage level is the non-storage level, the data storage content is determined as an empty content list. Specifically: When the data retention level is traceability retention level, first generate the page display data, alarm basis data, and work order basis data according to the processing methods under the display retention level, alarm retention level, and work order retention level; During data processing, the start and end times of the historical data range are read, and the historical field values ​​with a record time no earlier than the start time and no later than the end time are queried in the data table corresponding to the historical data table name. It should be noted that the traceability data should include at least the component identifier column, the historical field name column, the historical field value column, the historical time range column, and the component usage verification record column. Write the page display data, alarm basis data, work order basis data, and traceability basis data into the data content column of the data storage table, and write the data type column into the page display data, alarm basis data, work order basis data, and traceability basis data respectively; When the data retention level is set to no retention, the data table corresponding to the real-time data table name is not read, nor is the data table corresponding to the historical data table name. Instead, the data content columns in the data retention content table are written to an empty content list.

[0061] In step S5, storing the data corresponding to the page component according to the data storage level and the data storage content includes: S57. When the data storage content is not the empty content list, determine the corresponding target data table list from the page data table, the alarm data table, the work order data table and the traceability data table according to the data storage content; Specifically: Read data row by row and save the data type column in the content table; During data processing, when the data type column is the page display data, the page data table is written into the target data table list; When the data type column is alarm basis data, the alarm data table is written into the target data table list; When the data type column is the work order basis data, the work order data table is written into the target data table list; When the data type column is traceability basis data, the traceability data table is written to the target data table list; It should be noted that the target data table list should include at least a component identifier column, a data type column, and a target table name column. If the same target table name has already been written into the target data table list, it will not be written again.

[0062] S58. Write the data corresponding to the page components into the data tables in the target data table list, and record the component identifier, the purpose of saving, the data saving level and the component purpose verification record in the written data. Specifically: Read the target table names from the target data table list one by one; During data processing, when the target table name is page data table, the page display data is written to the page data table; When the target table name is alarm data table, write the alarm basis data into the alarm data table; When the target table name is Work Order Data Table, write the work order data into the Work Order Data Table. When the target table is named Traceability Data Table, the traceability basis data will be written to the Traceability Data Table. It should be noted that each time the data table corresponding to the target table name is written, the component identifier, the purpose of saving, the data storage level, and the component purpose verification record are also written. After the writing is completed, the latest record number in the data table corresponding to the target table name is read and written to the save record table.

[0063] S59. The records written into the target data table list are determined as the saved records of the page component. When the data saved content is the empty content list, the saved record is not generated. Specifically: The record table records the results of each write to the target data table list. The record table should include at least the component identifier column, the target table name column, the record number column, the purpose of saving column, the data retention level column, and the write time column. During the data processing, the latest record number obtained in step S58 is written into the record number column of the saved record table, the target table name is written into the target table name column, and the current time is written into the time column. When the data storage content is an empty content list, no data is written to the page data table, alarm data table, work order data table, and traceability data table, nor are any records written to the saved record table.

[0064] In this embodiment, a list of usable uses is filtered out based on the component usage verification record. The data storage level and data storage content are determined in the order of traceability use, work order use, alarm use, and display use. This ensures that when the exhaust pressure component meets the traceability use requirement, it simultaneously stores page display data, alarm basis data, work order basis data, and traceability basis data. When it only meets the display use requirement, it only stores page display data. This avoids page components that do not meet the data conditions from being used for pressure abnormality alarms, maintenance work order generation, or abnormality traceability. It also ensures that the content written to the page data table, alarm data table, work order data table, and traceability data table is consistent with the actual usable use of the page component.

[0065] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A data processing and storage method for building a device monitoring page, characterized in that: Includes the following steps: S1. Obtain the page component configuration of the page components in the device monitoring page. The page component configuration includes component identifier, component target purpose, binding fields, calculation rules and historical data range. S2. Determine the component data requirements based on the component's target purpose. The component's target purpose is one of display purpose, alarm purpose, work order purpose, or traceability purpose. The component data requirements are used to indicate the conditions that the binding fields, the calculation rules, and the historical data range need to meet when the page component achieves the component's target purpose. Step S2 includes: S21. When the target purpose of the component is the display purpose, the field identifier and real-time data table name corresponding to the bound field in the field table, and the write field name corresponding to the page component in the page data table are determined as the component data requirements. S22. When the target purpose of the component is the alarm purpose, the field identifier and the real-time data table name corresponding to the binding field in the field table, the calculation input field in the calculation rule, and the write field name corresponding to the page component in the alarm data table are determined as the component data requirements. S23. When the target purpose of the component is the work order purpose, the field identifier and the real-time data table name corresponding to the binding field in the field table, the calculation input field in the calculation rule, and the write field name corresponding to the page component in the work order data table are determined as the component data requirements. When the target purpose of the component is the traceability purpose, the field identifier, the real-time data table name and the historical data table name corresponding to the binding field in the field table, the calculation input field in the calculation rule, and the write field name corresponding to the page component in the traceability data table are determined as the component data requirements; S3. Determine the list of associated fields based on the binding fields, the calculation rules, and the historical data range, and determine whether the list of associated fields meets the component data requirements to obtain a component usage verification record. The component usage verification record includes records that meet the requirements or records that do not meet the requirements. S4. Determine the list of usable uses for the page component based on the component use verification record. When the component use verification record includes the satisfied record, add the component's target use to the list of usable uses. When the component use verification record includes the unsatisfied record, exclude the use corresponding to the unsatisfied record in the display use, alarm use, work order use, and traceability use from the list of usable uses. Step S4 includes: S41. The display purpose, alarm purpose, work order purpose and traceability purpose are respectively used as the purpose to be judged, and the component data requirements corresponding to each purpose to be judged are determined respectively; S42. Compare the list of associated fields with the component data requirements corresponding to each of the uses to be judged to obtain a use judgment record corresponding to each of the uses to be judged. The use judgment record is one of the satisfied record and the unsatisfied record. S43. Write the usage to be judged corresponding to the satisfied record into the usable usage list, and exclude the usage to be judged corresponding to the unsatisfied record from the usable usage list; S5. Determine the data storage level and data storage content of the page component according to the list of usable uses, and store the page display data, alarm basis data, work order basis data or traceability basis data corresponding to the page component according to the data storage level and the data storage content.

2. The data processing and storage method for building a device monitoring page according to claim 1, characterized in that: Step S1 includes: S11. In the editing interface of the device monitoring page, receive one of the creation operation and selection operation of the page component, and generate the component identifier according to the saving order of the page components in the device monitoring page; S12. Read the purpose option, field option, calculation setting and historical query setting corresponding to the page component, determine the purpose option as the target purpose of the component, determine the field option as the bound field, determine the calculation setting as the calculation rule, and determine the historical query setting as the historical data range; S13. Write the component identifier, the component target purpose, the binding field, the calculation rule, and the historical data range into the same configuration record, and determine the configuration record as the page component configuration.

3. The data processing and storage method for building a device monitoring page according to claim 1, characterized in that: In step S3, determining the list of associated fields includes: S31. Write the bound field into the associated field list; S32. When the calculation rule contains the calculation input field, parse the calculation rule, extract the calculation input field from the calculation rule, and write the calculation input field into the associated field list; S33. When the historical data range is not empty, the bound field and the calculation input field that need to be queried within the historical data range are written into the associated field list, and duplicate fields in the associated field list are retained only once.

4. The data processing and storage method for building a device monitoring page according to claim 3, characterized in that: In step S3, generating the component usage verification record includes: S34. Determine the field table requirements, calculated field requirements, and historical data requirements based on the component data requirements. The field table requirements include the field identifier and the real-time data table name corresponding to the field in the associated field list. The calculated field requirements are generated when the component data requirements include the calculated input field. The calculated field requirements include that all the calculated input fields in the calculation rules exist in the associated field list. The historical data requirement is generated when the component data requirement includes the historical data table name, and the historical data requirement includes the existence of a historical record number that falls within the historical data range in the data table corresponding to the historical data table name; S35. Read the fields in the associated field list one by one, and query the field identifier and the real-time data table name corresponding to the fields in the associated field list in the field table; When the calculation field requirement has been generated, the calculation input field in the calculation rule is compared with the list of associated fields. When the historical data requirement has been generated, the historical record number that falls within the historical data range is queried in the data table corresponding to the historical data table name. S36. When all of the generated field table requirements, calculated field requirements, and historical data requirements are matched, a satisfactory record is generated. When at least one of the generated field table requirements, calculated field requirements, and historical data requirements is not matched, a non-satisfied record is generated, and one of the satisfactory record and the non-satisfied record is written into the component usage verification record.

5. The data processing and storage method for building a device monitoring page according to claim 4, characterized in that: In step S36, generating the non-satisfied item record includes: S361. When the field table requirement is not matched, the field names in the associated field list that are not matched in the field table and the data table names that are not matched in the field table are written into the non-satisfied item record; S362. When the calculated field requirement is not matched, the calculated input field that is not matched in the associated field list is written into the unsatisfied item record; S363. When the historical data requirement is not matched, the field name of the historical record number that was not found and the corresponding historical data range are written into the unmet item record.

6. The data processing and storage method for building a device monitoring page according to claim 1, characterized in that: In step S5, determining the data preservation level includes: S51. Read the list of usable uses in the order of the traceability purpose, the work order purpose, the alarm purpose, and the display purpose; S52. When there is at least one use in the list of usable uses, the use that is first read in the list of usable uses is determined as the use for saving; when there is no use in the list of usable uses, the data saving level is determined as the non-saving level. S53. When the purpose of saving is the purpose of display, the data saving level is determined as the display saving level; When the purpose of saving is for alarm purposes, the data saving level is determined as the alarm saving level; when the purpose of saving is for work order purposes, the data saving level is determined as the work order saving level. When the purpose of the data storage is for traceability, the data storage level is determined to be the traceability storage level.

7. The data processing and storage method for building a device monitoring page according to claim 6, characterized in that: In step S5, determining the data storage content includes: S54. When the data storage level is the display storage level, the page display data is determined as the data storage content. The page display data includes the field values ​​and corresponding display times displayed by the page component on the device monitoring page. S55. When the data storage level is the alarm storage level, the page display data and the alarm basis data are determined as the data storage content; When the data storage level is the work order storage level, the page display data, the alarm basis data, and the work order basis data are determined as the data storage content; The alarm basis data includes the field value that triggered the alarm and the alarm trigger time; the work order basis data includes the field value used when generating the work order and the work order generation time. S56. When the data storage level is the traceability storage level, the page display data, the alarm basis data, the work order basis data, and the traceability basis data are determined as the data storage content. The traceability basis data includes historical field values ​​used for traceability queries, the corresponding historical time range, and the component usage verification record. When the data storage level is the non-storage level, the data storage content is determined as an empty content list.

8. The data processing and storage method for building a device monitoring page according to claim 7, characterized in that: In step S5, storing the data corresponding to the page component according to the data storage level and the data storage content includes: S57. When the data storage content is not the empty content list, determine the corresponding target data table list from the page data table, the alarm data table, the work order data table and the traceability data table according to the data storage content; S58. Write the data corresponding to the page components into the data tables in the target data table list, and record the component identifier, the purpose of saving, the data saving level and the component purpose verification record in the written data. S59. The records written into the target data table list are determined as the saved records of the page component. When the data saved content is the empty content list, the saved record is not generated.

Images