GB/T 32575-2026Power plant engineering data handover (English PDF)

7.3 Information Granularity

7.3.1 The granularity of the transferred data should be determined according to the requirements of operation and maintenance.

7.3.2 The granularity of information in the system classification data list and the equipment and product classification data table should conform to the requirements of Appendices D to J. The project can be customized or expanded upon. When customizing or expanding, the granularity requirements for application information at each stage and the digital design process should be analyzed and evaluated. The need to exchange the generated data.

7.4 Data Level This document defines four data levels.

1.Data required by laws, regulations, mandatory standards, or provisions.

2.Necessary data. Data that affects the integrity and safety of the power plant.

3.Optional Data. Data that can be transferred based on the differentiated needs of the project. This type of data may be available at the start of operation. Data that was previously (or at the start of operation) frozen may cause discrepancies between the data and the actual data when used during operation and maintenance. The risks are inconsistent and amplified over time by subsequent activities throughout the power plant's life cycle.

4.Temporary data. This refers to data that is used for specific tasks and has no long-term value, possessing temporary characteristics.

7.5 Data Format

7.5.1 Data Format Classification Data formats can be classified as follows:

a) Open structure format. Data organized according to a predefined open structure format, which has a high degree of information sharing. Sexuality can prevent information from being locked into specific application software.

b) Specific native format. Data created by specific application software, which typically does not have a clearly defined or publicly available structural format. This type of data information They are usually locked to specific application software.

c) Uneditable format. Formats such as images or portable documents whose content is difficult to edit or modify directly.

7.5.2 Data Format Selection Principles

7.5.2.1 The data format should be determined based on the following factors.

a) Purpose of the data;

c) Information granularity;

d) Appropriate data format standards;

e) The need for data updates;

f) The cost and potential difficulties of data transformation;

g) The ability of each participating party to submit data in the prescribed format;

h) The need for information interoperability;

i) The frequency of data usage and updates;

j) Data retention period.

7.5.2.2 Data transfer should preferably use a publicly available structured format. If no suitable publicly available structured format is available, a specific native format or an unmodifiable format may be used. Change the format. When using a specific native format, you should continuously track changes to that format and update the format when the application software that generates the data releases a new version. Data should be updated regularly, and format conversion should be performed when a specific native format is at risk of becoming obsolete.

7.6 Handover Method The project may choose one of the following methods or agree on other methods for data transfer.

a) The owner/operator already has a power plant information system, and all participating parties shall transfer data to that system;

b) The owner/operator may implement an agreed information system with the contractor handling the project data transfer, and transfer the system along with the data. To the owner/operator;

7.9 Quality Management

7.9.1 All participating parties shall agree on a data transfer quality management plan, establishing quality management objectives, management system, and management responsibilities, and standardizing data transfer procedures. According to the handover management process.

7.9.2 The data handover quality management plan should be part of the overall project quality plan. The data handover quality management plan should include the following. List of contents.

a) The data items to be transferred and the relationships between them;

b) Data transfer methods and verification methods;

c) Data import time, data update time;

d) Quality requirements for imported data and procedures to ensure data quality;

e) The process for handling erroneous data;

f) Records of the data's source, responsible party, and intended use;

g) Processes for identifying and resolving data inconsistencies;

h) Data encoding rules, etc.

7.9.3 The data should be evaluated according to the quality requirements in Table 2. Table

2 Quality Requirements Quality Requirements The degree to which normative data conforms to data standards The integrity of the handover requires a certain degree of completeness of the available information in the data. The accuracy of the transferred data in terms of its closeness to the actual situation. Consistency refers to the degree of consistency between data from different sources in terms of names, values, relationships, etc. The timeliness of updating timeliness data when needed The extent to which accessibility data can be accessed compliantly and conveniently.

8.1 Data Transfer Implementation Management

8.1.1 The owner/operator shall, in the early stages of the project, organize the development of a data handover strategy, determine data handover requirements, formulate a data handover plan, and implement it. Implementation plan.

8.1.2 All parties involved in the transfer shall establish a transfer organization and define their responsibilities for the transfer data.

8.1.3 An information environment, including hardware and software, that meets the requirements for data transfer should be established in a timely manner.

8.1.4 Before starting the data handover, a trial handover can be conducted to check the data source, data quality, and the feasibility of the data handover plan.

8.1.5 The transferred data should be verified and confirmed to meet quality requirements, including timely handling of any issues encountered during the data transfer process according to the established workflow. Check for deviations (such as ambiguous definitions, missing parsing rules, non-standard coding, etc.) and examine the implementation results of the handover plan.

8.1.6 Data quality checks and data transfers should be carried out by different personnel.

8.1.7 All handover processes should be controlled throughout the entire process to ensure traceability.

8.1.8 All participating parties shall promptly evaluate and summarize the data handover process.

8.2 Establishment of a database of power plant facility information Owners/operators should establish a database of power plant facility information according to the following principles.

a) Power plant facility object data should be managed using unique, searchable codes, which should comply with the requirements of GB/T 50549-2020;

b) It is advisable to establish and maintain the data model between power plant facilities and engineering data based on publicly available data model standards, such as GB/T 18975.2. relation;

c) It can integrate data with relevant management information systems for power plant operation and maintenance.

9.1 Data Transfer Contents for Various Power Generation Projects

9.1.1 The transfer data list for power generation projects shall be determined according to the system classification specified in GB/T 50549-2020, and in accordance with GB/T 50549- The data sheets defined in the 2020 equipment and product classifications were used for the transfer of engineering data.

9.1.2 For engineering data generated using other power plant identification systems, connections can be established with the system, equipment, and product classifications in this document. The mapping uses the data list and data table in this file for data transfer.

9.1.3 The system classification transfer data list and equipment and product classification data table for various power generation projects to be transferred shall conform to Appendix D to Appendix J. The corresponding requirements are shown in Table

3.The data source/purpose, data level, data format, and transfer time are listed in the system classification and transfer data list. See

9.3 for the data status reference code.

9.2 General Rules for Handover Content

9.2.1 Data Table The data table should include information such as the values of the attributes of the power plant facilities and the units of measurement, and the units of measurement should be consistent.

9.2.2 Drawings and Documents

9.2.2.1 Paper drawings and documents should be scanned into electronic format.

9.2.2.2 Drawings and documents shall be numbered uniquely, and their numbers and names shall not contain special characters.

9.2.2.3 Electronic documents shall meet the following requirements.

a) Electronic documents should not contain password protection that would impair readability;

b) The electronic document itself, its index, and attachments should be a single file package.

9.2.2.4 A document directory structure should be established for the handover of drawings and documents.

9.2.2.5 Drawings and documents should preferably use a uniform electronic file format.

9.2.3 Model

9.2.3.1 The information in the two-dimensional and three-dimensional models should be consistent with the information in the data sheets, drawings and documents.

9.2.3.2 The three-dimensional model should accurately represent the key dimensions and attribute information of the power plant facilities.

9.2.3.3 Three-dimensional models should be lightweighted by means of parametric processing, merging primitives, and compressing textures.

9.2.4 Relationship

9.2.4.1 Each power plant facility shall have a unique identification code, which shall be linked to its respective system, equipment, product, and related data sheets, drawings, and documents. Establish corresponding relationships between components, models, etc.

9.2.4.2 When the transferred data changes, its associations should be updated synchronously.

9.3 Data Transfer Reference Code

9.3.1 Data Source/Data Purpose The codes for data source/data purpose are shown in Table 4.

9.3.5 Data Status See Table 8 for data status codes.