A scheduling-based intelligent workbench system and method based on dynamic role switching and scene component pool

Abstract

This invention discloses a scheduling intelligent workbench system and method based on dynamic role switching and a scene component pool. The system includes: a role dynamic adaptation module, a scene component pool module, a multimodal data update module, an intelligent service module, and a multi-terminal synchronization module. The method includes: loading scene views according to roles; selecting components from the component pool and dynamically laying them out based on a virtual grid; subscribing to external system change events and executing corresponding update modes; and using timestamp arbitration to retain the latest operations during concurrent operations on multiple terminals. This invention can dynamically adapt the interface according to roles, and through a modular component pool and three data update modes, effectively improve the efficiency of multi-role collaborative command and data consistency, achieving scalability and seamless cross-terminal collaboration of the scheduling workbench.

Description

Technical Field

[0001] This invention relates to power dispatching information technology, specifically to a dispatching digital intelligent workbench system and method based on dynamic role switching and scenario component pool. Background Technology

[0002] With the deepening of the construction of new power systems, provincial power dispatching systems are gradually evolving from independent monitoring of single services to multi-role collaborative command. Early dispatching systems primarily achieved single-point monitoring and remote operation of substations. After 2010, provincial power grids began integrating multiple professional systems such as dispatching, automation, and operation and maintenance to build centralized dispatching platforms, achieving panoramic monitoring of transmission and transformation equipment. In recent years, several provinces, including Zhejiang, have piloted digital intelligent workbenches, supporting drag-and-drop customization of scenarios through component-based interfaces, marking the entry of dispatching systems into a stage of configurable interfaces.

[0003] However, existing technologies still have the following bottlenecks: 1) Insufficient dynamic interface adaptation: Traditional systems use fixed layout templates and cannot dynamically reconstruct the interface according to role responsibilities. For example, leaders in the power grid dispatch center need a macro-decision view, while the dispatch console needs an alarm list and operation ticket panel. Existing technology lacks an automatic role-scenario matching engine, which forces system users to manually switch between multiple systems.

[0004] 2) Low efficiency in real-time data collaboration: When multiple roles operate concurrently, data updates rely on a polling mechanism. When a dispatcher modifies a maintenance order, other users' interfaces cannot be synchronized in real time and must be manually refreshed. The lack of a unified multimodal data-driven framework causes delays in business collaboration.

[0005] 3) Limitations in Function Expansion and Multi-Platform Interoperability: New business components require customized development, making it impossible to achieve lightweight integration of third-party functions. Furthermore, the heterogeneous data channels used by mobile and desktop terminals necessitate manual relaying of cross-terminal tasks, reducing the collaborative efficiency of emergency power grid fault handling. Summary of the Invention

[0006] Purpose of the invention: The purpose of this invention is to provide a scheduling digital workbench system and method based on dynamic role switching and scene component pool, which is used to realize collaborative command, real-time data linkage and dynamic interface reconstruction of multiple roles (central leader, dispatch console, automated duty console, etc.) in provincial power grids, and solve the problem of business segmentation between mobile terminal and desktop terminal in the prior art.

[0007] Technical solution: The intelligent scheduling workbench system based on dynamic role switching and scene component pool described in this invention includes: The role dynamic adaptation module is used to obtain the role identifier when the user logs in, and automatically load the matching preset scene view according to the role identifier. The preset scene view contains the layout configuration of several business components. The scene component pool module is used to store and manage multiple business components. It allows users to select business components from the scene component pool and add them to the current scene view. It also supports registering third-party business components through standard interfaces. The multimodal data update module is used to implement three update modes: manual data refresh, differential push, and message notification, and handles concurrent operation conflicts based on a timestamp arbitration strategy. The intelligent service module provides functions such as voice interaction, automatic log generation, and fault contingency plan recommendation. The multi-terminal synchronization module is used to synchronize business data between desktop and mobile terminals via a message bus and to perform timestamp arbitration in case of conflicts.

[0008] Preferably, the role dynamic adaptation module enables intelligent loading of multi-role interfaces: it automatically matches preset scenarios based on user identity; the central leadership view integrates a panoramic view of the supply area, load forecast curves, and risk heat maps; the dispatch console view has a built-in timeline engine, displays the shift's fault / maintenance task flow at hourly granularity, and embeds intelligent compliance verification rules for dispatch operation tickets; the automated duty view accurately locates faulty components through a three-level topology map of the computer room-cabinet-equipment, and provides real-time feedback on alarm processing status in conjunction with dynamic legends.

[0009] Preferably, the scene component pool module provides an extensible component ecosystem: background components support full-screen display of power grid GIS maps or power supply area holographic connection maps, meeting the needs of overlaying geographic information and power grid topology; the floating component library includes general workbench components such as weather carousel, to-do task list, and real-time alarm panel, supporting 3D drag and drop and responsive layout; the open component registration interface allows developers to submit metadata (name / category / access address) and automatically add it to the library, realizing lightweight access to external third-party functions.

[0010] Preferably, the multimodal data update module overcomes the limitations of traditional system data collaboration by employing a unique three-pronged mechanism of manual refresh, differential push, and message notification. During concurrent operations by multiple users, a millisecond-level timestamp arbitration strategy is used, and overwritten operations generate warning markers for manual verification. As one implementation scheme, the multimodal data update module includes: a manual refresh mode that triggers a full-page component reload in response to user operations; a differential push mode that uses RabbitMQ to transmit JSON-Patch format differential packets to achieve automatic updates of local components; and a message notification mode that pushes change notifications to the user's message center, executing the update after user confirmation. The timestamp arbitration strategy uses millisecond-level timestamp comparison, retains the latest operation record, generates conflict markers for overwritten operations, and provides manual verification. The multimodal data update module is also configured to: enable local caching in case of network anomalies, manage cached data using an LRU algorithm, and perform incremental synchronization through a differential comparison engine after network recovery.

[0011] Preferably, the intelligent service module integrates artificial intelligence technology: the voice interaction engine supports system user voiceprint verification; the LSTM network-based automatic log generation system builds a dynamic template library by analyzing historical operation patterns and outputs standardized log drafts for the system backend; and the fault contingency plan recommendation function relies on big data from the control cloud monitoring to automatically generate the optimal handling plan.

[0012] Preferably, the multi-terminal synchronization module achieves strong cross-platform consistency: desktop and mobile terminals synchronize data via a distributed message bus, automatically triggering a timestamp arbitration mechanism in case of conflicts; core business processes such as maintenance orders and operation tickets support seamless collaboration between the two terminals, with tests showing a low rate of manual intervention. As one implementation scheme, the multi-terminal synchronization module adopts an event-driven model, serializing business objects into JSON transmission packets, which are then distributed via the message bus and deserialized and rendered by the receiving end; the message bus is a distributed message bus with a three-level priority queue: fault alarm queue latency <100ms, scheduling instruction queue latency <500ms, and regular notification queue latency <2s; the entire message chain has a tracking ID and ACK receipt mechanism, and integrates real-time sensitive word filtering and content compliance review.

[0013] Beneficial Effects: Compared with existing technologies, this invention has the following significant advantages: It pioneers a mechanism for integrating pre-set templates with user-defined scenarios, achieving adaptive adjustment of component layout through a virtual grid algorithm, thus solving the problem of rigid interface layout in traditional systems; it breaks through by integrating three data update modes to meet the high-concurrency real-time collaborative business needs of provincial power grids; a standardized registration interface supports rapid access for third-party components, building a sustainable and evolving scheduling application ecosystem; and a timestamp-based conflict arbitration algorithm ensures cross-terminal data consistency. Attached Figure Description

[0014] Figure 1This refers to the core layout and component grid of the character view in this embodiment of the invention.

[0015] Figure 2 This refers to the component refresh / minimize / close operation logic in this embodiment of the invention.

[0016] Figure 3 This is the general workbench announcement / notification / to-do module in this embodiment of the invention.

[0017] Figure 4 This is the component registration parameter configuration interface in an embodiment of the present invention.

[0018] Figure 5 This is an interface for scene customization and component addition in the embodiments of the present invention.

[0019] Figure 6 Scene filtering settings (region / time) are provided in this embodiment of the invention. Detailed Implementation

[0020] The technical solution of the present invention will be further described below with reference to the accompanying drawings and embodiments.

[0021] Example 1: System Architecture Deployment and Dynamic Generation of Role Views like Figure 1 As shown, the system deploys a power control cloud platform, which realizes dynamic generation of role views through a three-layer architecture: the data synchronization layer builds a three-level data channel based on Kafka (fault alarm / dispatch instruction / routine notification); the role adaptation layer pre-sets four types of JSON format templates (central leader / dispatch console / automated duty / general view); the component rendering layer integrates a WebGL engine, and finally lays out components according to a 24×24 virtual grid.

[0022] When a user logs in, the LDAP protocol matches role identifiers and automatically loads the dispatch center leadership view: a panoramic view of the supply area situation, load forecast curves, and risk heatmaps. Components are dynamically arranged in a grid. Scenario customization can be achieved through... Figure 6 The filter interface shown can be configured with region / time conditions.

[0023] Example 2: Multimodal Data Update and Conflict Resolution Mechanism The system is built with a hierarchical data update architecture to support three linkage modes: manual refresh via... Figure 2 The refresh button in the shown component triggers a full page reload; differential push notifications transmit JSON-Patch differential packets via RabbitMQ; message alerts are sent to the user's message center via push notifications, such as... Figure 3 The notification area of ​​the Zhongtong workbench.

[0024] When multiple users perform concurrent operations, the conflict detection module compares the operation sequence using millisecond-level timestamps, executes the "last operation first" arbitration strategy, and retains the latest timestamp operation record. Overwritten operations generate conflict markers for manual review. In case of network anomalies, local caching is enabled, using the LRU algorithm to manage cached data. After network recovery, incremental synchronization is performed through a difference comparison engine to ensure system operation data consistency.

[0025] Example 3: Component Lifecycle Management and Intelligent Recommendation The intelligent component management system enables end-to-end management of components, from registration to recommendation. 1) Registration Phase: Developers submit metadata (component name, function category, access address, default size) through a standardized interface. The system assigns a unique ID and performs a security review, such as... Figure 4 The component registration interface shown; 2) Deployment phase: Verify component interface specifications through a compatibility testing framework and automatically generate description documents to be stored in the knowledge base; 3) Recommendation Stage: Based on user roles and operation history, a collaborative filtering model is built to dynamically recommend components to specific scenarios, such as... Figure 5 The component addition process is shown in the scene customization interface. When a component is invoked, the responsive layout engine calculates the position parameters in real time and generates a layout description file containing size and hierarchy, supporting cross-scene reuse.

[0026] Example 4: Voice Interaction and Intelligent Log Generation The voice interaction module implements natural language control through an end-to-end processing flow: a microphone array acquires a 48kHz audio stream, a speech recognition engine converts it into text, and a power grid-specific semantic model parses the operation intent. Before execution, dual security verification is performed: voiceprint feature matching and operation permission verification. The execution result is then broadcast via a TTS engine.

[0027] The intelligent log generation module adopts a fusion of event-driven and deep learning technologies: LSTM network analyzes the semantic patterns of historical logs to build a dynamic template library. When a real-time operation event is triggered, the fuzzy matching algorithm associates the best template, automatically fills in the parameters to generate a standardized log draft, and supports manual correction through a visual interface. Finally, the generated structured log is synchronized to the knowledge base.

[0028] Example 5: Project Collaborative Management and Multi-device Synchronization The project management module integrates a Gantt chart engine and an intelligent scheduling algorithm: after inputting the task set, resource constraints, and dependencies, the constraint programming algorithm calculates the critical path and resource load. When the schedule deviation is greater than 15%, a yellow / red warning signal is triggered. The operation interface is as follows: Figure 6 The filter settings are shown below. The multi-party collaborative space supports document version control and online annotation, and the template engine automatically extracts project data to generate weekly project management reports.

[0029] Cross-terminal synchronization adopts an event-driven model: maintenance orders drafted on the desktop are serialized into JSON transmission packets and distributed to the mobile terminal for deserialization and rendering via a message bus. When there is a conflict between the two terminals, an arbitration strategy is executed based on timestamp comparison. The overridden operation generates a red warning icon to ensure strong consistency across multiple terminals.

[0030] Example 6: High-Reliability Message Bus Architecture The real-time message bus adopts a distributed deployment and optimizes the transmission path through an intelligent routing algorithm: a three-level priority queue is established, and the link with the lowest latency is dynamically selected, where the fault alarm queue has a latency of <100ms; the scheduling instruction queue has a latency of <500ms; and the regular notification queue has a latency of <2s.

[0031] The entire message chain is tracked by IDs recording transmission status, and an ACK receipt mechanism ensures reliable delivery. The security module integrates a real-time sensitive word filtering engine and content compliance review, with message processing latency of <200ms shown in tests with tens of thousands of concurrent users.

[0032] In summary, this system achieves digital transformation of scheduling through three innovative workflows: 1. Role-based scenario construction process: The system obtains the role identifier when logging into the system based on the LDAP protocol and automatically loads the corresponding preset scenario; users drag and drop new business components from the component pool, and the layout engine dynamically adjusts the position according to the 24×24 virtual grid; the saved scenario configuration can be synchronized to other role users with one click through the sharing mechanism to realize the rapid reuse of one-to-many multi-user collaborative scenarios.

[0033] 2. Real-time data linkage process: The data-driven engine actively subscribes to system change events such as OMS and D5000. When multiple concurrent operations are detected, the conflict detection module immediately compares the operation timestamps. According to the user's preset mode, the data update strategy is selected and the local components are automatically updated in the differential push mode. In the message reminder mode, the change notification is pushed to the message center and the update is performed only after the system user account confirms it.

[0034] 3. Intelligent Operation and Maintenance Closed-Loop Process: Taking the automated duty scenario as an example: After the equipment alarm is triggered, the system accurately locates the faulty component through the three-level topology map, automatically notifies the responsible person and updates the handling status to the dynamic legend; the handling process generates structured logs in sync, which are then optimized by the LSTM neural network and stored in the system knowledge base, forming a closed loop of equipment fault handling experience.

Claims

1. A scheduling-based intelligent workbench system based on dynamic role switching and scene component pool, characterized in that, include: The role dynamic adaptation module is used to obtain the role identifier when the user logs in, and automatically load the matching preset scene view according to the role identifier. The preset scene view contains the layout configuration of several business components. The scene component pool module is used to store and manage multiple business components. It allows users to select business components from the scene component pool and add them to the current scene view. It also supports registering third-party business components through standard interfaces. The multimodal data update module is used to implement three update modes: manual data refresh, differential push, and message notification, and handles concurrent operation conflicts based on a timestamp arbitration strategy. The intelligent service module provides functions such as voice interaction, automatic log generation, and fault contingency plan recommendation. The multi-terminal synchronization module is used to synchronize business data between desktop and mobile terminals via a message bus and to perform timestamp arbitration in case of conflicts.

2. The system according to claim 1, characterized in that, The role dynamic adaptation module obtains the role identifier based on the LDAP protocol; The pre-set scene views include: a central leadership view, which integrates a panoramic view of the supply area, load forecast curves, and risk heat maps; a dispatch console view, which has a built-in time axis engine, displays the on-duty fault / maintenance task flow at the hourly level, and embeds intelligent compliance verification rules for dispatch operation tickets; and an automated duty view, which accurately locates faulty components through a three-level topology map of the computer room-cabinet-equipment, and provides real-time feedback on alarm processing status in conjunction with dynamic legends.

3. The system according to claim 1, characterized in that, The role dynamic adaptation module also includes a layout engine, which uses a preset virtual grid to dynamically adjust the position of business components; the virtual grid is an M×N grid unit, where M and N are both integers greater than 1; after the scene configuration is saved, it can be synchronized to other role users with one click through the sharing mechanism.

4. The system according to claim 1, characterized in that, The scene component pool module includes: a background component that supports full-screen display of a power grid GIS map or a power supply area holographic connection map; a floating component library that includes a weather carousel, a list of tasks to be done, and a real-time alarm panel; and an open component registration interface for receiving metadata submitted by developers. The metadata includes the component name, function category, access address, and default size, and is automatically added to the library after security review.

5. The system according to claim 1, characterized in that, In the multimodal data update module: the manual refresh mode responds to user operations and triggers a full-page reload of the component; the differential push mode transmits differential packet data through the message middleware to achieve automatic updates of local components; the message reminder mode pushes change notifications to the user message center, and executes the update after user confirmation; the timestamp arbitration strategy is a millisecond-level timestamp comparison, retains the latest operation record, generates conflict markers for overwritten operations, and provides manual review.

6. The system according to claim 1, characterized in that, The multimodal data update module is also configured to: enable local caching when the network is abnormal, manage cached data using a cache management algorithm, and perform incremental synchronization through a difference comparison engine after the network is restored.

7. The system according to claim 1, characterized in that, The intelligent service module includes: a voice interaction engine that supports voiceprint verification and natural language control, wherein voiceprint verification includes voiceprint feature matching and operation permission verification; an automatic log generation unit that analyzes historical operation patterns based on LSTM network and automatically generates standardized log drafts by associating templates through fuzzy matching algorithm; and a fault contingency plan recommendation function that automatically generates handling plans based on big data monitoring of the control cloud.

8. The system according to claim 1, characterized in that, The multi-terminal synchronization module adopts an event-driven model, serializing business objects into transmission packets, which are then distributed by the message bus and deserialized and rendered by the receiving end. The message bus is a distributed message bus with hierarchical priority queues, and different priority queues correspond to different transmission delay requirements. The entire message link is equipped with tracking identification and delivery confirmation mechanisms, and integrates content security review functions.

9. A scheduling method based on dynamic role switching and scene component pool, characterized in that, Includes the following steps: Step 1: Based on the user's role identifier when logging in, automatically load the matching preset scene view, which contains the layout configuration of several business components; Step 2: In response to the user's operation of selecting a business component from the scene component pool, add the selected business component to the current scene view and dynamically adjust the layout according to the virtual grid; Step 3: Subscribe to change events of external business systems. When a data update is detected, perform the update according to the preset data update mode, which includes manual refresh, differential push, and message notification. Step 4: Utilize the intelligent service module to perform voice interaction, automatic log generation, or fault contingency plan recommendations; Step 5: When conflicts arise from concurrent operations on multiple terminals, arbitration is performed based on the operation timestamp, the latest operation is retained, and a warning mark is generated for the overwritten operation.

10. The method according to claim 9, characterized in that, It also includes step six: receiving metadata from third-party components through an open component registration interface, performing security reviews, and storing it in the scenario component pool; and dynamically recommending suitable business components to users based on user roles and operation history using a collaborative filtering model. Furthermore, the saved scene configuration can be shared to other user roles with a single click.

Images