Platform construction method for digital twin system of transformer substation

Abstract

The invention relates to a platform construction method for a digital twin system of a transformer substation. The method comprises the following steps: S1, defining system requirements; s2, determining a key driving factor; s3, the expandability and the flexibility are emphasized; s4, hardware platform compatibility; and S5, a digital system and platform mechanism. All users can conveniently use the platform constructed by the invention, can enter the digital twin system of the transformer substation only by logging in one platform, and can add new functions or integrate with other systems according to needs; the platform provides a solid foundation for business innovation, supports rapid iteration and trial and error, and promotes research and development of new products and new services.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of substation digital twin system management, and particularly relates to a substation digital twin system platform construction method. BACKGROUND

[0002] At present, digital twin systems are mostly single-station types, and cannot be effectively integrated. Platform construction of multiple system integration has become a major trend in the technical field. This integration not only involves the fusion of software systems, but also includes the comprehensive integration of hardware devices, data resources, and business processes. By constructing a unified platform, seamless connection and efficient collaboration between different systems can be achieved, thereby greatly improving the convenience of use. SUMMARY

[0003] The purpose of the present application is to overcome the shortcomings of the prior art and provide a substation digital twin system platform construction method. The digital twin systems of each substation are organically integrated to form a unified, efficient, and collaborative platform. This process involves in-depth analysis, accurate positioning, and skillful integration of each system to ensure that each system can maximize its performance on the platform while maintaining overall coordination and stability.

[0004] The technical problem of the present application is solved by the following technical solution: A substation digital twin system platform construction method, the steps of the method are: S1, define system requirements: comprehensively analyze system requirements, including functional requirements and non-functional requirements, and clearly define requirements and business requirements as the key to ensuring the design of suitable technical architecture; S2, determine the key driving factors: based on the requirement analysis, identify the key driving factors that affect the architecture design, such as performance requirements, reliability requirements, security requirements, scalability, and cost constraints. These factors need to be considered in the design process to ensure that the architecture meets business and technical requirements; S3, pay attention to scalability and flexibility: choose tools with high scalability and flexibility; S4, hardware platform compatibility: ensure that the selected IDE or tool supports the architecture of the target hardware platform, understand and select development tools compatible with specific hardware architectures; S5, digital system and platform mechanism: build an efficient "point-line-surface-body" three-dimensional platform architecture mode, connect different substations through digital systems, achieve efficient collaboration, promote the value realization of each organization and individual on the platform, and form extensive network effects.

[0005] The advantages and beneficial effects of the present application are: 1. Ease of use and accessibility: All users can easily use the platform functions, and only need to log in to one platform to enter the digital twin system of the substation.

[0006] 2. Extensibility and flexibility: The platform has high scalability and flexibility. As the project develops, new functions can be added or integrated with other systems as needed.

[0007] 3. Promote business innovation: The platform provides a solid foundation for business innovation. It supports rapid iteration and trial and error, promoting the development of new products and services. Through the open platform API, third-party developers can participate and jointly promote the innovation and transformation of business models. BRIEF DESCRIPTION OF DRAWINGS

[0008] Figure 1 System platform schematic diagram for the method of the present application. DETAILED DESCRIPTION

[0009] The present application will be further described in detail through specific embodiments, the following embodiments are only descriptive and not limiting, and cannot limit the protection scope of the present application.

[0010] A digital twin system platform construction method for a substation, the innovation lies in: through the landing of the four-layer architecture of "hardware layer - interface layer - service layer - application layer", combined with modular development and collaborative testing, the platform construction of the digital twin system of the substation is realized, the steps of the method are: (I) Server hyper-converged deployment 1. Hardware selection and configuration Server specification determination: According to the number of substation access (calculated according to the daily data volume of 50GB-100GB of single-station digital twin system), select 2U rack server, configure high-performance processor, and ensure that the server cluster can support the real-time data processing needs of 10-20 substations.

[0011] Hyper-converged cluster construction: Adopt cluster deployment mode, nodes are interconnected through high-speed network cards, based on the hyper-converged architecture of Wangchao, realize storage resource pooling and elastic allocation of computing resources, and configure dual hot standby mechanism, when a single node fails, the business can be automatically switched to other nodes within 30 seconds, guaranteeing system availability ≥99.99%.

[0012] Hardware compatibility verification: For the target hardware platform, verify the communication protocol adaptability of the server and the edge device through the hardware compatibility test tool, ensure that the data collected on the edge side can be uploaded to the hyper-converged cluster through the Modbus TCP / OPC UA protocol. Stable.

[0013] 2. Infrastructure virtualization configuration Virtual machine division: based on business needs, dedicated virtual machines are divided, including "data collection virtual machine", "model calculation virtual machine", "application service virtual machine" and other virtual machines isolated through VLAN to avoid resource preemption.

[0014] (II) Information exchange interface development 1. Interface protocol selection and design Edge side interface: supports 10ms level data sampling frequency, the interface adopts "request-response" mode, sets up timeout reconnection mechanism (retry interval 500ms, maximum retry number 3), ensures data collection success rate ≥99.9%.

[0015] Cross-system integration interface: to realize data intercommunication with power dispatching system and equipment operation and maintenance management system, RESTful API interface is developed, JSON format is adopted to encapsulate data, interface fields include "device ID, collection time, data type, value, check code" and other core information, and HTTPS encryption transmission (TLS 1.3 protocol is adopted) is supported to prevent data leakage.

[0016] Third-party development interface: open platform API interface, SDK development toolkit (supports Java, Python language) is provided, including interface call examples, parameter description and error code documents, interface access adopts OAuth 2.0 authorization mechanism, third-party developers need to apply AppKey and AppSecret, and realize interface access control through token (Token).

[0017] (III) Back-end service building 1. Service architecture design Microservice splitting: based on domain-driven design, back-end services are split into "data collection service", "model management service", "user permission service", "alarm pushing service" and other microservices, each service is independently deployed and independently scaled, service registration and discovery are realized through framework (Nacos is adopted), and configuration center management is realized (unified configuration of database connection, interface parameters, etc.).

[0018] Data processing flow: After the data collection service receives the edge device data, it first performs data cleaning, and then pushes the valid data to the model management service through the Kafka message queue; the model management service calls the digital twin modeling engine, combines the device three-dimensional model with real-time data, and generates a dynamic twin; the user permission service is responsible for verifying user login information and assigning function permissions according to user roles (such as administrators, maintenance personnel, and visitors); the alarm push service monitors whether the data exceeds the threshold (such as CPU usage ≥ 90% triggering an alarm), and notifies relevant personnel through SMS and APP push methods, with an alarm response time ≤ 1 minute.

[0019] 2. Database design and deployment Database selection: Adopt a hybrid architecture of "relational database + time series database", MySQL database (master-slave replication deployment) stores structured data (such as user information, device basic information, interface configuration), ensuring data consistency; InfluxDB time series database stores massive time series data (such as device real-time monitoring data, historical trend data), supporting high write performance (single node write rate ≥ 100,000 / s) and fast query (near 1 hour data query response time ≤ 1 second).

[0020] (Four) Front-end interface construction 1. Interface architecture design Technology selection: Develop the front-end interface using the Vue 3 framework combined with the Element Plus component library, use ECharts for data visualization (such as CPU usage line chart, device status pie chart), use Three.js to load the substation three-dimensional model, support model rotation, scaling, roaming, and other interactive operations, and the interface is adapted to PC. Page module division: The front-end interface is divided into "home page map module", "device monitoring module", "twin model module", "alarm center module", and "system management module" five modules: Home page map module: Based on the Gaode Map API, it shows the geographical location of the connected substations (marker color distinguishes the running state: green for normal, yellow for warning, and red for fault), and the mouse-over marker displays the substation name, device quantity, and other basic information; (Five) Component modular development 1. Modularization splitting principles Function cohesion: encapsulate the reusable functions as independent components, such as "data dashboard component" (reusable to device monitoring module, twin model module), "alarm card component" (reusable to home page, alarm center module), "paging component" (unify the data paging style of each module), the internal component contains independent logic processing and style definition, external through props receives parameters, through emit triggers events, realizes the decoupling of component.

[0021] 2. Component testing and integration Unit testing: use Jest tool to test the component, verify whether the component props transmission is correct, whether the event triggering is normal, whether the style meets the design specification (such as color, font, spacing), and the test coverage rate is ≥80%.

[0022] Integration testing: after integrating the component into the front-end page, test the interaction logic between components (such as when the "paging component" switches the page number, whether the "data list component" updates the data synchronously), and verify the compatibility of the component in different browsers (Chrome, Firefox, Edge), to ensure that there is no difference in interface display and function.

[0023] (Six) System integration and online Full-process testing: simulate the actual business scenario, from edge device data acquisition → interface transmission → back-end service processing → front-end interface display full-process verification, such as connecting 1 RTU device in the substation site, testing whether the device data is displayed in real time in the front-end map module and twin model module, and whether the data error is ≤1%.

[0024] Abnormal scenario testing: simulate edge device disconnection (pull out the network cable), server node failure (turn off 1 hyper-converged node), interface request timeout (set network delay 1000ms) and other abnormal scenarios, verify whether the system triggers the preset fault tolerance mechanism (such as displaying "offline" state in front-end when the device is disconnected, automatically switching the business when the server fails, automatically retrying after the interface timeout).

[0025] User acceptance testing (UAT): invite substation operation and maintenance personnel, dispatch personnel to participate in testing, collect user feedback on interface operation, function integrity, data accuracy, optimize the system according to the feedback (such as adjusting alarm threshold, increasing device filtering conditions), until the user confirms that the business requirements are met.

[0026] Although the embodiments of the present application and the drawings are disclosed for the purpose of illustration, those skilled in the art can understand that various substitutions, changes and modifications are possible without departing from the spirit and scope of the present application and the appended claims, therefore, the scope of the present application is not limited to the disclosed content of the embodiments and drawings.

Claims

1. A method for platform-based construction of a substation digital twin system, characterized in that: The steps of the method are as follows: S1. Define system requirements: Conduct a comprehensive analysis of system requirements, including functional and non-functional requirements. Clearly defining requirements and business needs is key to ensuring the design of a suitable technical architecture. S2. Identify key drivers: Based on the requirements analysis, identify key drivers that affect the architecture design, such as performance requirements, reliability requirements, security requirements, scalability and cost constraints. These factors need to be considered during the design process to ensure that the architecture meets business and technical needs. S3. Emphasize scalability and flexibility: Choose tools that are highly scalable and flexible; S4. Hardware Platform Compatibility: Ensure that the selected IDE or tool supports the architecture of the target hardware platform, and understand and select development tools that are compatible with specific hardware architectures. S5. Digital Systems and Platform Mechanisms: Construct an efficient "point-line-surface-volume" three-dimensional platform architecture model, connect different substations through digital systems, achieve efficient collaboration, promote the realization of value for each organization and individual on the platform, and form a broad network effect.

Images