Method and system for promoting collaborative management of power grid projects

Abstract

The embodiment of the invention provides a method and a system for promoting collaborative management of power grid projects. The method comprises the following steps: acquiring data transmitted by each department; integrating and cleaning the various data to obtain shared data which is provided with at least one of the following labels: project early-stage data, project middle-stage data and project later-stage data; and displaying the shared data in a classified manner based on the labels so that the multiple departments can read the shared data in real time. According to the invention, the problems of business data walls and low information transmission efficiency in the prior art are solved.

Description

Technical Field

[0001] The embodiments of the present invention relate to the technical field of digital power grids, and in particular, to a method and system for promoting collaborative management of power grid projects. Background Art

[0002] With the progress of society and the development of science and technology, digital power grid has become an important development direction for the power industry. Based on information technology, digital power grid transforms the traditional power system into an intelligent and automated system, achieving high efficiency and reliability in power supply, distribution and management. The development of this technology enables the power industry to better adapt to the growing power demand and complex power network.

[0003] Currently, digital power grids have been successfully applied in many places. Through the combination of data acquisition, communication networks and intelligent devices, digital power grids have achieved real-time monitoring and control of power grid status and operation information. This enables power companies and operators to manage and maintain power systems more efficiently and improve power supply quality and reliability. Digital power grids also have powerful fault detection and diagnosis capabilities, which can detect and repair power grid faults in a timely manner, reducing power outage time and impact range.

[0004] However, although the application of digital power grid has achieved certain results, there are still some problems in daily operations. One of the important problems is the existence of business data walls. Each department reports the situation of its own department within the business wall, resulting in fragmentation and isolation of project data. For example, Department 1 reports the implementation of Project A plan, Department 2 reports the construction progress report of Project A, Department 3 reports the financial expenditure report of Project A, and Department 4 reports the material procurement of Project A. This decentralized data reporting method leads to information isolation, requiring relevant personnel to assist in the transmission of information back and forth, which consumes a lot of time and energy.

[0005] Moreover, since information needs to be repeatedly transmitted between different departments, there is a problem of low efficiency in information transmission. Each department needs to wait for other departments to report information before proceeding to the next step, which not only prolongs the project cycle, but also increases the risk of information transmission and the possibility of errors.

[0006] Based on the above problems, it is necessary to propose a new technology to solve the problems of business data wall and inefficient information transmission, so as to further improve the operational efficiency and management level of digital power grid. Summary of the invention

[0007] The embodiments of the present invention provide a method and system for promoting collaborative management of power grid projects, so as to at least solve the problems of business data wall and low efficiency of information transmission existing in the related art.

[0008] According to one embodiment of the present invention, a method for promoting collaborative management of power grid projects is provided, comprising: Obtain data transmitted by various departments; Integrate and clean the multiple data to obtain shared data, wherein the shared data is provided with at least one of the following labels: early project data, mid-project data, and late project data; The shared data is displayed based on the tags and classified so that the multiple departments can read it in real time.

[0009] According to another embodiment of the present invention, a system for promoting collaborative management of power grid projects is provided, comprising: Data acquisition module, used to obtain data transmitted by various departments; A data processing module, used for integrating and cleaning the multiple data to obtain shared data, wherein the shared data is provided with at least one of the following labels: early project data, mid-project data, and late project data; The data classification display module is used to display the shared data based on the label classification so that the multiple departments can read it in real time.

[0010] According to yet another embodiment of the present invention, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any one of the above method embodiments when run.

[0011] According to yet another embodiment of the present invention, there is provided an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0012] Through the present invention, firstly, the data transmitted by each department is integrated and cleaned, eliminating the existence of business data walls. In this way, the data between different departments are no longer scattered and isolated, but are unified and integrated into shared data. This unified data format can be better acquired and recognized by other departments, thereby facilitating the transmission and sharing of information.

[0013] Secondly, after generating shared data, the present invention displays the data based on label classification. Through this classification display method, different departments can browse the data related to their work in real time without waiting for reports from other departments. In this way, the efficiency of information transmission is greatly improved, and each department can obtain the required information more timely, so as to carry out the next step of work.

[0014] In summary, the present invention solves the problems of business data wall and inefficient information transmission by integrating, cleaning and displaying data by label classification. This is of great significance to the improvement of the operational efficiency and management level of the digital power grid, and can promote the collaborative work among various departments to achieve more efficient and reliable power supply and management. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a flow chart of a method for promoting collaborative management of power grid projects according to an embodiment of the present invention; Figure 2 is a flow chart of a method for acquiring data transmitted by various departments according to an embodiment of the present invention; Figure 3 is a flowchart of a method for providing a data transmission interface so that an account transmits data through the data transmission interface according to an embodiment of the present invention; Figure 4 is a flowchart of a method for authorizing a first account to transmit data to a second account when the first account cannot transmit data, so that the second account transmits data through a first data transmission interface, according to an embodiment of the present invention; Figure 5 is a flowchart of a method for displaying shared data based on tag classification so that multiple departments can read it in real time according to an embodiment of the present invention; Figure 6 4 is a schematic diagram of the structure of a system for promoting collaborative management of power grid projects according to an embodiment of the present invention. DETAILED DESCRIPTION

[0016] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings and in combination with the embodiments.

[0017] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0018] In this embodiment, a method for promoting collaborative management of power grid projects is provided. Figure 1 is a flow chart of a method for promoting collaborative management of power grid projects according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps: Step S101, obtaining data transmitted by each department; In an exemplary embodiment, the following method may be used: Design a digital management platform for power grid projects.

[0019] Create accounts for different departments on the platform and grant corresponding permissions to upload data.

[0020] Design and provide data upload interfaces or tools to facilitate various departments to upload data to the platform.

[0021] Departments upload relevant data to the platform in the specified format and specifications as needed. This can be real-time data, historical data, operation and maintenance records, etc.

[0022] Step S102, integrating and cleaning the various data to obtain shared data, wherein the shared data is provided with at least one of the following labels: early project data, mid-project data, and late project data; In an exemplary embodiment, the following method may be used: Design data integration and cleansing functions on the platform to integrate the data uploaded by various departments.

[0023] Determine standards and specifications for data integration to ensure that data from different data sources can be matched and associated.

[0024] Perform data cleaning, such as removing duplicate data, processing missing values, correcting formats, etc., to ensure data accuracy and consistency.

[0025] The integrated and cleaned data is stored in the form of shared data in preparation for subsequent data display and reading.

[0026] Set labels for each data in the shared data, such as pre-project data, mid-project data, and post-project data, so as to classify and retrieve the data.

[0027] Step S103, displaying the shared data based on the tag classification so that multiple departments can read it in real time.

[0028] In an exemplary embodiment, the following method may be used: Design and implement data display interfaces or dashboards to centrally display shared data.

[0029] Set corresponding data display modules and functions according to the needs and permissions of different departments.

[0030] It provides functions such as data search, filtering and sorting to facilitate users to find and obtain specific data.

[0031] You can design visualizations such as charts, graphs, and reports to visualize data and make it easier to understand and analyze.

[0032] Provide permission management function to ensure that different departments can only access data within their authority, thus ensuring data security and privacy.

[0033] Through step S101 to step S103, first, the data transmitted by each department is integrated and cleaned, eliminating the existence of business data walls. In this way, the data between different departments are no longer scattered and isolated, but are unified and integrated into shared data. This unified data format can be better acquired and recognized by other departments, thereby facilitating the transmission and sharing of information.

[0034] Secondly, after generating shared data, the present invention displays the data based on label classification. Through this classification display method, different departments can browse the data related to their work in real time without waiting for reports from other departments. In this way, the efficiency of information transmission is greatly improved, and each department can obtain the required information more timely, so as to carry out the next step of work.

[0035] In summary, the present invention solves the problems of business data wall and inefficient information transmission by integrating, cleaning and displaying data by label classification. This is of great significance to the improvement of the operational efficiency and management level of the digital power grid, and can promote the collaborative work among various departments to achieve more efficient and reliable power supply and management.

[0036] In one implementation, obtaining data transmitted by various departments includes: Step S201, create accounts for different departments and grant corresponding data transmission permissions; In an exemplary embodiment, the following method may be used: User account management: Create user accounts in the platform, each account corresponds to a department or functional module. Account creation and management can be completed by the system administrator or platform administrator. When creating an account, you need to specify relevant information about the account, such as account name, department name, contact information, etc.

[0037] Permission management: Set corresponding permissions for uploading data according to the needs and responsibilities of each department. Permissions can be subdivided into levels such as read, modify, and delete. Platform administrators can assign corresponding permissions to each account based on actual conditions to ensure data security and compliance.

[0038] Account authentication and authorization: When a user logs in to the platform, identity authentication is required to ensure the legitimacy of the account. Authentication methods may include username and password, email verification, mobile phone verification code, etc. After authentication, the platform will authorize the corresponding data upload permission for the account according to the account's permission settings.

[0039] Step S202: providing a data transmission interface so that the account can transmit data through the data transmission interface.

[0040] In one embodiment, a data transmission interface is provided to enable an account to transmit data through the data transmission interface, including: When the account is the first account, the data transmission interface is set to the first data transmission interface, so that the first account transmits data through the first data transmission interface.

[0041] In an exemplary embodiment, the following method may be used: Design data upload interface: Design a suitable data upload interface according to the platform requirements and technical architecture. The interface can adopt standard API protocols, such as RESTful API or GraphQL, or you can define your own interface specifications according to specific circumstances.

[0042] Interface permission control: Implement permission verification in the data upload interface to ensure that only accounts with permission to upload data can call the interface. Verification can be performed through the account's identity authentication information, such as the username and password, token verification, etc. mentioned above.

[0043] Data format normalization: Set the data format and specifications of the data upload interface to ensure that the uploaded data meets the data structure requirements of the platform. For example, the data format can be defined as JSON or XML, and the required fields and data types can be specified to help the platform correctly parse and process the uploaded data.

[0044] Data upload process: Provide a data upload interface or tool so that users can easily select the data file to be uploaded or input data, and transmit data through the data upload interface. You can consider supporting different upload methods such as batch upload and real-time upload to meet the needs of different users.

[0045] Data upload status feedback: After the data upload is completed, the upload status and results are returned to the user to confirm whether the upload is successful. The corresponding status code, message or upload log can be returned through the interface for feedback.

[0046] In one embodiment, a data transmission interface is provided to enable an account to transmit data through the data transmission interface, including: Step S301, when the account is a second account, setting the data transmission interface to the second data transmission interface, so that the second account transmits data through the second data transmission interface; In an exemplary implementation, the specific setting method is the same as the setting of the first account and the first data transmission interface, and will not be repeated here.

[0047] Step S302, when the first account cannot transmit data, the data transmission authority of the first account is authorized to be delegated to the second account, so that the second account transmits data through the first data transmission interface and / or the second data transmission interface.

[0048] In an exemplary embodiment, the following method may be used: Authorization agent function: Add the authorization agent function in the account management system, allowing the first account to authorize other second accounts to upload data. In this way, the first account can grant the data upload permission to the second account when it cannot upload data itself.

[0049] Identity verification and permission verification: When the second account uses the data upload interface of the first account to upload data, it must first be authenticated to ensure that its identity is authorized by the first account. This can be achieved by verifying the second account's identity authentication information, authorization credentials or tokens, etc.

[0050] Data upload parameter settings: Provide appropriate interface parameters or configuration items to allow the second account to specify the source account of the uploaded data, that is, the first account, when uploading data on behalf of the second account. In this way, even if the second account is used to upload data, the platform can still identify the source account of the data.

[0051] Record upload logs and audit: During the data upload process, the system should record relevant log information, including upload time, upload account, upload data, etc., for data tracing and auditing. This ensures that the data uploaded by the first account and the second account agent can be monitored and tracked.

[0052] In the above manner, the second account can upload data through the data upload interface of the first account without logging into the first account.

[0053] In one embodiment, when the first account cannot transmit data, authorizing the first account's data transmission authority to be delegated to the second account so that the second account transmits data through the first data transmission interface includes: Step S401, obtaining the attendance sheet of the EHR system; In an exemplary embodiment, the following method may be used: Determine the connection method: First, determine the method of connecting to the EHR system. The possible connection methods include API interface, data interface or file transfer. Choose the appropriate connection method according to the specific situation of the EHR system.

[0054] Establish connection with EHR system: After determining the connection method, develop or configure the corresponding connection tools or modules to establish connection with EHR system. This may involve operations such as authentication and authorization to ensure the legitimacy and security of access rights.

[0055] Extract attendance sheet data: After the connection is established, the attendance sheet data is obtained by accessing the interface or data interface of the EHR system. This involves sending a request to the EHR system and obtaining the attendance sheet data according to the corresponding data structure and parameters. Programming languages ​​and tools can be used to process and parse the returned data.

[0056] Data cleaning and integration: After obtaining the attendance sheet data, data cleaning and integration operations are performed to make it suitable for the data display and analysis needs of the digital management platform. This includes operations such as data format conversion, field mapping, and data merging to ensure data accuracy and consistency.

[0057] Data storage and indexing: The cleaned and integrated attendance sheet data can be stored in the database or data warehouse of the digital management platform, and corresponding indexes can be established to facilitate quick retrieval and query of data. This ensures the efficient use of attendance sheet data in the digital management platform.

[0058] Data display and analysis: Finally, the attendance sheet data is displayed and analyzed in the digital management platform. Data visualization tools and reporting functions can be used to visualize and analyze attendance data. In this way, users can view and analyze various indicators and data related to attendance through the digital management platform.

[0059] Step S402, identifying the leave request form based on the attendance form; In an exemplary embodiment, the following method may be used: Feature analysis of leave requests: First, analyze the existing leave request data to understand the characteristics and patterns of each leave request. For example, you can check the title, content, date, leave type and other information of the leave request to determine the features that may be used for automatic recognition.

[0060] Feature extraction: Based on the analysis results, extract and encode the features of each leave request. Natural language processing techniques such as text preprocessing, bag-of-words model, word embedding, etc. can be used to convert the leave request into a numerical or vector representation.

[0061] Build a model: Use machine learning or deep learning technology to build a model and train the features with the corresponding leave types. The models that can be used include decision trees, random forests, support vector machines, neural networks, etc. You can use existing labeled data sets for model training so that the model can learn and predict new leave types.

[0062] Model evaluation and tuning: Evaluate the performance of the model through cross-validation or reserved data sets, and perform model tuning. You can adjust the model's hyperparameters, try different feature combinations, or adjust the model structure to improve the model's accuracy and generalization ability.

[0063] Apply the model: Apply the trained model to new leave request data to predict the type. Based on the prediction results of the model, the leave request can be marked as the corresponding leave type, such as sick leave, annual leave, personal leave, etc.

[0064] Step S403, automatically identifying the second account designated by the first account of the leave-seeker based on the leave request form; In an exemplary embodiment, the following method may be used: Extract leave request information: Extract the account information of the person who requested leave and the person who is replacing the person based on the data structure and format of the leave request. This may involve analyzing the title, content, date and other fields of the leave request to determine the location and rules of the account information.

[0065] Data cleaning and organization: Clean and organize the extracted account information to ensure the consistency and accuracy of the format. For example, remove redundant characters, handle uppercase and lowercase letters, align account information, etc.

[0066] Matching substitutes: Use appropriate technology and algorithms to match the substitute’s account information with the account information of the person on leave. Fuzzy matching, string matching, similarity calculation and other methods can be used to compare the account information of the person on leave and the substitute to determine the degree of match and the best match.

[0067] Designate a substitute account: Based on the matching results, designate the substitute's account information as the second account of the person on leave. This can include adding the substitute's account information to the leave request or recording it in the relevant data structure for subsequent use and reference.

[0068] Step S404: authorizing the data transmission authority of the first account to be delegated to the second account, so that the second account transmits data through the first data transmission interface.

[0069] In an exemplary embodiment, the following method may be used: Determine permission requirements: Determine the specific permissions and requirements that the first account needs to transfer data. This can include permissions to read, write, modify, or delete data.

[0070] Configure proxy authorization: In the data transfer interface of the first account, configure the proxy authorization mechanism to allow the second account to use the permissions of the first account for data transfer. This can be achieved through mechanisms such as access control lists (ACLs) or role-based permission management (RBAC).

[0071] Generate a proxy token: Generate a proxy token or token combination for the second account to verify its identity and authority when using the data transfer interface of the first account. The proxy token can contain the necessary authentication information and authorization information so that the second account can establish a valid connection and perform data transfer.

[0072] Authentication and authorization: In the data transfer interface of the first account, the received request is authenticated and authorized. This can be done by verifying the token, checking the access control list, or querying the role permissions to ensure that the second account has the corresponding authorization permissions.

[0073] Data transfer: After verification and authorization, the second account can use the data transfer interface of the first account to transfer data, including reading, writing, modifying or deleting data. These operations will be performed with the permissions of the first account to ensure the validity and legitimacy of the data transfer.

[0074] In one embodiment, when the first account cannot transmit data, authorizing the first account's data transmission authority to be delegated to the second account so that the second account transmits data through the first data transmission interface includes: The interface parameters of the first data transmission interface are configured so that when the second account transmits data through the first data transmission interface, the source account of the data transmission and the transmitted data are recorded.

[0075] In an exemplary implementation, if the first account cannot transmit data (for example, the staff member corresponding to the first account needs to take a vacation, and the staff member corresponding to the second account needs to be designated to take his place. However, due to the special position of the staff member of the first account, it is not convenient to share his previous work content with others, and only the data during the vacation period is convenient to share.), but it is still desired to authorize the second account to transmit data through the first data transmission interface and record the transmission source account and data, the following implementation methods can be considered: Interface parameter configuration: In the first data transmission interface, add interface parameters to pass the source account of the data transmission and the data to be transmitted. This can be achieved by adding additional request headers, query parameters or message body fields.

[0076] Authentication and Authorization: Add authentication and authorization mechanisms to the interface to ensure that only authorized second accounts can access the interface. This can be achieved using token verification, API keys, or other effective authentication mechanisms.

[0077] Data recording: In the implementation of the data transmission interface, the source account and the transmitted data are recorded in a log or database. Information such as account ID, data content, and transmission time can be recorded for subsequent tracking and auditing.

[0078] Error handling: Handle error situations in the interface, such as invalid authentication information, unauthorized access, or data transfer failure. Appropriate error codes and error messages can be returned so that the second account can get corresponding feedback and processing.

[0079] To sum up, when the staff corresponding to the first account is on vacation, the data of the first data transmission interface will be shared with the second account. At this time, the corresponding data can be processed by the staff of the second account, and the first data interface can record the source account of the data transmission and the transmitted data for subsequent tracking and auditing.

[0080] In one implementation, shared data is displayed based on tag classification so that multiple departments can read it in real time, including: Step S501, setting corresponding data identifications for multiple departments, where the data identifications include identifications of information that the departments need to know; In an exemplary embodiment, the following method may be used: Data identification setting: Each department determines the data identification that it is concerned about and sets it in the power grid project digital management platform. This can be set through configuration files, background management interfaces or other methods. Data identification can be represented by specific identifiers or names. For example, decision makers can set the data identification of concern to "project planning", "project reserves", "financial situation", etc.; managers can set core indicators, archives, attendance, etc.; executors can set data identification such as personal agency and business notification.

[0081] Data association: In a data table or database, add corresponding data identifiers for each data item. This can be achieved by adding fields to the data model, using tags or metadata, etc. Make sure that the data identifiers correspond to the data identifiers set by each department. For example, in a project database, each data item contains fields such as project planning, financial status, and attendance, and they are marked in the data table.

[0082] Step S502: automatically screening the shared data based on the data identifier to display the data content corresponding to the data identifier.

[0083] In an exemplary embodiment, in the functional module of the digital management platform for power grid projects, data is filtered and displayed according to the user identity and the set data identifier. After the user logs in, the system obtains the corresponding data identifier according to the user role and authority, and then filters out the corresponding data items and displays them to the user. For example, after the decision maker logs in, the digital management platform for power grid projects will filter out data such as project planning, project reserves, and financial conditions based on the data identifiers set by the decision maker, and display them to the user in the form of visualization, reports, or lists.

[0084] In short, the key to implementing data filtering and display based on the corresponding data identification of multiple departments is to clarify the setting of data identification and associate it with the actual data items. Then, according to the identity and authority of the user, the data is filtered and displayed to meet the needs and concerns of different departments.

[0085] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by adding the necessary general hardware platform with the help of software, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0086] In this embodiment, a system for promoting collaborative management of power grid projects is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made are not repeated here. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0087] Figure 6 is a schematic diagram of a system for promoting collaborative management of power grid projects according to an embodiment of the present invention. Figure 6 As shown, the system includes: The data acquisition module 61 is used to acquire data transmitted by various departments; The data processing module 62 is used to integrate and clean various data to obtain shared data, wherein the shared data is provided with at least one of the following labels: early project data, mid-project data, and late project data; The data classification display module 63 is used to display the shared data based on the label classification so that multiple departments can read it in real time.

[0088] In one embodiment, the system is also used to: Create accounts for different departments and grant corresponding data transmission permissions; Provides a data transfer interface to enable accounts to transfer data through the data transfer interface.

[0089] In one embodiment, the system is further used for: when the account is a first account, setting the data transmission interface to the first data transmission interface, so that the first account transmits data through the first data transmission interface.

[0090] In one embodiment, the system is also used to: When the account is a second account, the data transmission interface is set to the second data transmission interface, so that the second account transmits data through the second data transmission interface; When the first account is unable to transmit data, the data transmission authority of the first account is authorized to be delegated to the second account, so that the second account transmits data through the first data transmission interface and / or the second data transmission interface.

[0091] In one embodiment, the system is also used to: Obtain attendance sheets from the EHR system; Identify leave requests based on attendance sheets; Automatically identify the second account designated as a substitute by the first account of the person applying for leave based on the leave request; The data transmission authority of the first account is authorized to be delegated to the second account, so that the second account transmits data through the first data transmission interface.

[0092] In one embodiment, the system is also used to: configure the interface parameters of the first data transmission interface so that when the second account transmits data through the first data transmission interface, the source account of the data transmission and the transmitted data are recorded.

[0093] In one embodiment, the system is also used to: Set corresponding data identification for multiple departments, including identification of information that the departments need to know; Automatically screen shared data based on data identifiers to display the data content corresponding to the data identifiers.

[0094] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0095] An embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.

[0096] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0097] An embodiment of the present invention further provides an electronic device, including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0098] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0099] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.

[0100] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0101] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for promoting collaborative management of power grid projects, characterized in that: include: Obtain data transmitted by various departments; Integrate and clean the multiple data to obtain shared data, wherein the shared data is provided with at least one of the following labels: early project data, mid-project data, and late project data; The shared data is displayed based on the tags and classified so that the multiple departments can read it in real time.

2. The method according to claim 1, characterized in that Get data transmitted by various departments, including: Create accounts for different departments and grant corresponding data transmission permissions; A data transmission interface is provided so that the account can transmit data through the data transmission interface.

3. The method according to claim 2, characterized in that Providing a data transmission interface so that the account can transmit data through the data transmission interface, including: In the case that the account is a first account, the data transmission interface is set to a first data transmission interface, so that the first account transmits data through the first data transmission interface.

4. The method according to claim 3, characterized in that Providing a data transmission interface so that the account can transmit data through the data transmission interface, including: In the case where the account is a second account, setting the data transmission interface to a second data transmission interface, so that the second account transmits data through the second data transmission interface; When the first account is unable to transmit data, the data transmission authority of the first account is authorized to be delegated to the second account, so that the second account transmits data through the first data transmission interface and / or the second data transmission interface.

5. The method according to claim 4, characterized in that In the case that the first account cannot transmit data, authorizing the data transmission authority of the first account to be delegated to the second account so that the second account transmits data through the first data transmission interface includes: Obtain attendance sheets from the EHR system; identifying a leave request based on the attendance sheet; Automatically identifying a second account designated by the first account of the person on leave as a substitute based on the leave request form; The data transmission authority of the first account is authorized to be delegated to the second account, so that the second account transmits data through the first data transmission interface.

6. The method according to claim 4, characterized in that In the case that the first account cannot transmit data, authorizing the data transmission authority of the first account to be delegated to the second account so that the second account transmits data through the first data transmission interface includes: The interface parameters of the first data transmission interface are configured so that when the second account transmits data through the first data transmission interface, the source account of the data transmission and the transmitted data are recorded.

7. The method according to claim 1, characterized in that The shared data is displayed based on the tags so that the multiple departments can read it in real time, including: Setting corresponding data identifiers for the multiple departments, the data identifiers including identifiers of information that the departments need to know; The shared data is automatically screened based on the data identifier to display data content corresponding to the data identifier.

8. A system for promoting collaborative management of power grid projects, characterized in that: include: Data acquisition module, used to obtain data transmitted by various departments; A data processing module, used for integrating and cleaning the multiple data to obtain shared data, wherein the shared data is provided with at least one of the following labels: early project data, mid-project data, and late project data; The data classification display module is used to display the shared data based on the label classification so that the multiple departments can read it in real time.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 7 when executed by a processor.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method described in any one of claims 1 to 7 are implemented.

Images