Power grid project management method and device based on central data warehouse

Abstract

The present application provides a power grid project management method and device based on a central data warehouse. The power grid project management system includes a central data warehouse for connecting a PMS system, an ERP system, and an OMS system and storing data from each system. The method includes: when obtaining a collaborative management instruction sent by the PMS system in response to an engineering project management task, parsing the collaborative management instruction; when the collaborative management instruction includes a material supply instruction, forwarding it to the ERP system; when the collaborative management instruction includes a power dispatching instruction, forwarding it to the OMS system; when obtaining a data dispatching instruction sent by the ERP system or the OMS system, obtaining feedback data from the central data warehouse, correspondingly feeding back to the ERP or OMS system, and generating a management log based on the collaborative management instruction. This embodiment utilizes a central data warehouse that centrally stores data to implement an automated parsing and forwarding mechanism for instructions, reduce the need for manual operations, and improve project management efficiency.

Description

Technical Field

[0001] The present application relates to the technical field of power project management, and in particular to a power grid project management method and device based on a central data warehouse. Background Art

[0002] Power grid construction project management is a complex process that not only includes the operation of the engineering production management system, but also covers the management of material resources and the guarantee of power supply. In current practice, these different management functions are often performed by independent systems. For example, the engineering production management system is responsible for monitoring and guiding the construction process of power grid construction, the material resource management system focuses on the procurement, storage and distribution of materials, and the power supply system ensures the stable operation of the power grid and the effective distribution of electricity. However, there is a problem of data islands between these systems, that is, the data in the dispatching system cannot be effectively shared and transmitted with other systems. This situation has led to the formation of information barriers, forcing managers of each system to rely on manual methods to import and export data, thereby reducing the overall efficiency of project management. Summary of the invention

[0003] The embodiments of the present application provide a power grid project management method and device based on a central data warehouse to solve the problem of low overall efficiency of project management.

[0004] In a first aspect, an embodiment of the present application provides a power grid project management method based on a central data warehouse, wherein the power grid project management system includes a central data warehouse for connecting a power production management system (PMS), an enterprise resource planning (ERP) system, and an outage management system (OMS) and storing data from each system, the method comprising:

[0005] When obtaining the collaborative management instruction sent by the PMS system in response to the engineering project management task, parsing the collaborative management instruction;

[0006] When the collaborative management instruction includes a material supply instruction, forwarding the material supply instruction to the ERP system; when the collaborative management instruction includes a power dispatch instruction, forwarding the power dispatch instruction to the OMS system;

[0007] When the data scheduling instruction sent by the ERP system or the OMS system is obtained, feedback data is obtained from the central data warehouse, and corresponding feedback is given to the ERP system or the OMS system, and a management log is generated based on the collaborative management instruction.

[0008] In a possible implementation, the obtaining feedback data from the central data warehouse and correspondingly feeding back the feedback data to the ERP system or the OMS system includes:

[0009] According to the data scheduling instruction sent by the ERP system, feedback data is obtained and a first data format corresponding to the ERP system is obtained, and the feedback data is packaged according to the first data format and fed back to the ERP system;

[0010] According to the data scheduling instruction sent by the OMS system, feedback data is obtained and a second data format corresponding to the OMS system is obtained, and the feedback data is packaged according to the second data format and fed back to the OMS system.

[0011] In a possible implementation, generating a management log based on the collaborative management instruction includes:

[0012] generating a management log record and a record identifier according to the instruction information corresponding to the collaborative management instruction;

[0013] Among them, the instruction information includes two or more of material supply instructions, data scheduling instructions, instruction generation time, data feedback time, data feedback results and account login information.

[0014] In a possible implementation, the method further includes:

[0015] When the log search instruction is obtained, the log search instruction is parsed to determine an identifier or a keyword;

[0016] The corresponding management log record is located according to the identifier or the keyword.

[0017] In a possible implementation manner, before obtaining the feedback data from the central data warehouse, the method further includes:

[0018] Parsing the collaborative management instruction to determine account login information;

[0019] Determine whether the user is an authenticated user based on the account login information;

[0020] When the account login information corresponds to an authenticated user, determine the operation authority corresponding to the account login information, and obtain corresponding feedback data from the central data warehouse when the user has access rights to the ERP system data, and obtain corresponding feedback data from the central data warehouse when the user has access rights to the OMS system data;

[0021] When the account login information corresponds to a temporary user, an authentication operation interface is generated to perform user authentication.

[0022] In a possible implementation, the method further includes:

[0023] Obtain basic data sets of the PMS system, ERP system and OMS system for commonality analysis; wherein the basic data sets include project information, material information, order details, inventory status and financial information;

[0024] Establishing a mapping relationship between each system data field and a standard data model, and identifying the same fields in each system according to the mapping relationship;

[0025] A common data list is generated based on the same fields for storage; wherein the common data list includes key information such as data item name, data type, data format, data source system, etc.

[0026] In a possible implementation, the method further includes:

[0027] The common data list is updated according to the set update conditions.

[0028] In a possible implementation, the PMS system, the ERP system and the OMS system include independent databases;

[0029] The method further comprises:

[0030] When the central data warehouse is restored from an offline state to an online state, a data synchronization instruction is sent to the PMS system, the ERP system and the OMS system respectively; wherein the data synchronization instruction includes the offline time of the central data warehouse;

[0031] Acquire data packets sent by the PMS system, the ERP system and the OMS system; wherein the data packets include data change logs of the PMS system, the ERP system and the OMS system; the data change time in the data change log is determined according to the offline time of the central data warehouse;

[0032] The data stored in the central data warehouse is updated according to the data packet.

[0033] In a second aspect, an embodiment of the present application provides a power grid project management device based on a central data warehouse, wherein the power grid project management system includes a central data warehouse for connecting a PMS system, an ERP system, and an OMS system and storing data from each system, and the device includes:

[0034] A parsing module, configured to parse the collaborative management instruction when acquiring the collaborative management instruction sent by the PMS system in response to the engineering project management task;

[0035] a sending module, configured to forward the material supply instruction to the ERP system when the collaborative management instruction includes a material supply instruction; and forward the power dispatch instruction to the OMS system when the collaborative management instruction includes a power dispatch instruction;

[0036] A data processing module, configured to obtain feedback data from the central data warehouse when obtaining a data scheduling instruction sent by the ERP system or the OMS system;

[0037] The sending module is further used to feed back the feedback data to the ERP system or the OMS system accordingly;

[0038] A log module is used to generate a management log based on the collaborative management instruction.

[0039] The embodiment of the present application provides a power grid project management method and device based on a central data warehouse. The power grid project management system integrates a central data warehouse connected to the PMS system, the ERP system and the OMS system, and is responsible for storing the data interacting between the systems. The system realizes the automatic processing of instructions by real-time parsing the collaborative management instructions issued by the PMS system in response to the engineering project management tasks. When the collaborative management instructions involve material supply, the system will automatically forward the instructions to the ERP system; if the instructions involve power dispatching, the instructions will be transferred to the OMS system. In addition, the system can also respond to data dispatching instructions issued by the ERP system or the OMS system, extract corresponding feedback data from the central data warehouse, and accurately feed back these data to the corresponding system. Based on the collaborative management instructions, the system will also automatically generate a management log. Through this automated instruction parsing and forwarding mechanism, the need for manual operation is greatly reduced, thereby significantly improving the efficiency of project management. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0041] Figure 1 This is an application scenario diagram of a power grid project management method based on a central data warehouse provided in an embodiment of the present application;

[0042] Figure 2 is a flowchart of an implementation of a power grid project management method based on a central data warehouse provided in another embodiment of the present application;

[0043] Figure 3It is a structural diagram of a power grid project management device based on a central data warehouse provided in one embodiment of the present application. DETAILED DESCRIPTION

[0044] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.

[0045] The terms "first", "second", etc. in the specification and claims of the embodiments of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the numbers used in this way can be interchanged where appropriate, so that the embodiments of the embodiments of the present application described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0046] Unless otherwise stated, the term "plurality" means two or more.

[0047] In the embodiment of the present application, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B means: A or B.

[0048] The term "and / or" is a description of the association relationship between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or, A and B.

[0049] The words used in this application are only used to describe the embodiments and are not used to limit the claims. As used in the description of the embodiments and claims, unless the context clearly indicates, the singular forms of "a", "an" and "the" are intended to include the plural forms as well. Similarly, the term "and / or" as used in this application refers to any and all possible combinations of one or more associated listings. In addition, when used in this application, the term "comprise" and its variants "comprises" and / or including (comprising) refer to the existence of stated features, wholes, steps, operations, elements, and / or components, but do not exclude the existence or addition of one or more other features, wholes, steps, operations, elements, components and / or these groups. In the absence of more restrictions, the elements defined by the statement "including one..." do not exclude the existence of other identical elements in the process, method or device including the elements. In this application, each embodiment may focus on the differences from other embodiments, and the same and similar parts between the embodiments may refer to each other. For the methods, products, etc. disclosed in the embodiments, if they correspond to the method part disclosed in the embodiments, then the relevant parts can be found in the description of the method part.

[0050] In order to make the purpose, technical solutions and advantages of the present application clearer, specific embodiments will be described below in conjunction with the accompanying drawings.

[0051] Figure 1 : is an application scenario diagram of a power grid project management method based on a central data warehouse provided in an embodiment of the present application. Figure 1 As shown, the power grid project management system includes a central data warehouse for connecting the PMS system, the ERP system and the OMS system and storing data from each system.

[0052] In addition, the power grid project management system also includes a management system and management terminal for managing the central data warehouse to achieve visual management of the central data warehouse, making data monitoring, analysis and reporting more intuitive and efficient. Through the central data warehouse and management system, users can easily track the operation status of the power grid, discover and solve potential problems in a timely manner, and ensure the stability and reliability of the power grid.

[0053] In other embodiments, real-time updating of the central data warehouse and query of historical data are also supported, providing powerful data support for the long-term planning and optimization of the power grid.

[0054] Figure 2 is a flowchart of an implementation of a power grid project management method based on a central data warehouse provided in an embodiment of the present application, such as Figure 2As shown, the method comprises the following steps:

[0055] S201, when obtaining the collaborative management instruction sent by the PMS system in response to the engineering project management task, parsing the collaborative management instruction.

[0056] The power grid project management method based on the central data warehouse described in the embodiment of the present application can be executed by a management system that manages the central data warehouse or by a management terminal. For ease of understanding, the embodiment of the present application selects the management terminal as the execution subject for specific example description.

[0057] In the actual implementation process, relevant staff will issue instructions for project management tasks through the management terminal connected to the PMS system. After receiving these project management task instructions, the PMS system will send collaborative management instructions to the central data warehouse to obtain the required data. Subsequently, the PMS system will issue a coordination request to the ERP system and OMS system to ensure that the entire project management task can proceed smoothly.

[0058] S202, when the collaborative management instruction includes a material supply instruction, forward the material supply instruction to the ERP system; when the collaborative management instruction includes a power dispatching instruction, forward the power dispatching instruction to the OMS system.

[0059] If the analysis result shows that the collaborative management instruction contains a material supply instruction, the central data warehouse forwards the instruction to the ERP system. After receiving the material supply instruction, the ERP system allocates materials according to the instruction content and updates the ERP system database.

[0060] If the analysis result shows that the collaborative management instruction contains a power dispatch instruction, the central data warehouse forwards the instruction to the OMS system. After receiving the power dispatch instruction, the OMS system dispatches power resources according to the instruction content and updates the OMS system database.

[0061] S203, when the data scheduling instruction sent by the ERP system or the OMS system is obtained, feedback data is obtained from the central data warehouse, corresponding feedback is given to the ERP system or the OMS system, and a management log is generated based on the collaborative management instruction.

[0062] After completing the instruction, the ERP system or OMS system will send a data scheduling instruction to the central data warehouse to request feedback data. The central data warehouse extracts the corresponding data from the warehouse according to the data scheduling instruction and feeds it back to the ERP system or OMS system.

[0063] Each parsing and forwarding of collaborative management instructions and the response to data scheduling instructions will be recorded in the management log. The management log records in detail the sending time, recipient, instruction content and execution results of the instruction, providing traceability and transparency for project management.

[0064] In other possible implementations, if an exception occurs during instruction parsing or forwarding, the system will trigger an exception handling mechanism, such as retrying the transmission, notifying the administrator, etc. The exception handling mechanism ensures the stability of the system and the reliability of instruction execution.

[0065] The introduction of exception handling mechanism improves the robustness of the system and ensures rapid response and processing when problems arise.

[0066] In this embodiment, the power grid project management system integrates a central data warehouse connecting the PMS system, the ERP system and the OMS system, which is responsible for storing the data interacting between the systems. The system realizes the automatic processing of instructions by real-time parsing the collaborative management instructions issued by the PMS system in response to the engineering project management task. When the collaborative management instruction involves material supply, the system will automatically forward the instruction to the ERP system; if the instruction involves power dispatching, the instruction will be transferred to the OMS system. In addition, the system can also respond to the data dispatching instruction issued by the ERP system or the OMS system, extract the corresponding feedback data from the central data warehouse, and accurately feed back the data to the corresponding system. Based on the collaborative management instruction, the system will also automatically generate a management log. Through this automated instruction parsing and forwarding mechanism, the need for manual operation is greatly reduced, thereby significantly improving the efficiency of project management. As the core of data sharing, the central data warehouse ensures the consistency of data between the PMS system, the ERP system and the OMS system. The system strengthens the collaborative working ability between different systems through automated instruction flow, making the project management process smoother. The generation of management logs provides the necessary transparency for the project management process, ensuring that all operations can be traced and enhancing the traceability of the project. Through the data collected and analyzed by the central data warehouse, the power grid project management obtains more accurate decision support. This embodiment effectively improves the efficiency and reliability of power grid project management.

[0067] In a possible implementation, feedback data is obtained from the central data warehouse and fed back to the ERP system or OMS system, including:

[0068] According to the data scheduling instruction sent by the ERP system, feedback data is obtained and a first data format corresponding to the ERP system is obtained, and the feedback data is packaged according to the first data format and fed back to the ERP system;

[0069] According to the data scheduling instruction sent by the OMS system, the feedback data is obtained and the second data format corresponding to the OMS system is obtained, and the feedback data is packaged according to the second data format and fed back to the OMS system;

[0070] The first data format is different from the second data format.

[0071] By compressing feedback data in different data formats, the accuracy, timeliness and security of data flow between different systems are ensured, thereby improving the efficiency and responsiveness of the entire supply chain management.

[0072] During the specific implementation process, the ERP system can receive data on key links such as production, inventory, and sales in a timely manner, while the OMS system can obtain real-time information on order processing, logistics distribution and other links, allowing enterprises to adjust operating strategies more flexibly and optimize resource allocation.

[0073] In addition, this data feedback mechanism can also help companies respond quickly to market changes. By analyzing feedback data, companies can predict market trends and formulate more scientific and reasonable production and sales plans.

[0074] In this embodiment, by obtaining feedback data from the central data warehouse and accurately feeding it back to the ERP system and OMS system, the enterprise can achieve data-driven decision-making and improve overall project management efficiency.

[0075] In a possible implementation, generating a management log based on the collaborative management instruction includes:

[0076] Generate a management log record and a record identifier according to the instruction information corresponding to the collaborative management instruction;

[0077] Among them, the instruction information includes two or more of material supply instructions, data scheduling instructions, instruction generation time, data feedback time, data feedback results and account login information.

[0078] Among them, the detailed record of instruction information is crucial for subsequent query and audit work, so each log entry is assigned a unique identifier. The generated management log will be stored in a secure log database to ensure data integrity and confidentiality. In addition, the design of the log database must take into account the needs of efficient data retrieval and long-term storage, and must have security measures to prevent unauthorized access.

[0079] In this embodiment, a management log record and its unique identifier are generated based on the instruction information corresponding to the collaborative management instruction, ensuring the transparency and traceability of all collaborative management activities, and providing solid support for internal management of the organization and external compliance audits.

[0080] In a possible implementation, the method further includes:

[0081] When the log search instruction is obtained, the log search instruction is parsed to determine the identifier or keyword;

[0082] Locate the corresponding management log record based on the identifier or keyword.

[0083] In this embodiment, the review and analysis of collaborative management activities can be effectively implemented through log retrieval instructions, thereby improving management efficiency and accuracy.

[0084] In a possible implementation, before obtaining the feedback data from the central data warehouse, the following is further included:

[0085] Parse collaborative management instructions to determine account login information;

[0086] Determine whether the user is a certified user based on the account login information;

[0087] When the account login information corresponds to the authenticated user, determine the operation authority corresponding to the account login information, and obtain the corresponding feedback data from the central data warehouse when the access authority for ERP system data is available; and obtain the corresponding feedback data from the central data warehouse when the access authority for OMS system data is available;

[0088] When the account login information corresponds to a temporary user, an authentication operation interface is generated for user authentication.

[0089] In a specific embodiment, users are divided into temporary users or authenticated users. In addition, in order to improve data security, data access rights are further allocated to authenticated users. If the account login information corresponds to an authenticated user, then the operation rights corresponding to the account login information need to be determined next. Once it is confirmed that you have the authority to access the ERP system data, you can obtain the corresponding feedback data from the central data warehouse. Similarly, if you have the authority to access the OMS system data, you can also obtain the corresponding feedback data from the central data warehouse. If the account login information corresponds to a temporary user, the management terminal will generate an authentication operation interface to facilitate user authentication.

[0090] In this embodiment, by using account login information to identify the user's identity and the permissions they have, we have effectively improved the security of the data access process. This mechanism ensures that only users with appropriate permissions can access sensitive data.

[0091] In a possible implementation, the method further includes:

[0092] Obtain basic data sets from the PMS system, ERP system, and OMS system for commonality analysis; basic data sets include project information, material information, order details, inventory status, and financial information;

[0093] Establish the mapping relationship between the data fields of each system and the standard data model, and identify the same fields in each system based on the mapping relationship;

[0094] Generate a common data list based on the same fields for storage; the common data list includes key information such as data item name, data type, data format, and data source system.

[0095] Among them, the basic data sets of the PMS system, ERP system and OMS system are obtained for commonality analysis to achieve unified management and efficient use of data. In a possible implementation, the basic data set is data with public viewing permissions to avoid sensitive data leakage.

[0096] The content of the basic data set covers project information, material information, order details, inventory status, financial information and other aspects, which are all key data that are indispensable in enterprise operations. In order to achieve the interconnection and interoperability of data between different systems, it is necessary to establish a mapping relationship between the data fields of each system and a unified standard data model. Through this mapping relationship, the same data fields in each system can be identified, thus laying the foundation for subsequent data integration and commonality analysis.

[0097] In this embodiment, the establishment of a common data list not only helps the enterprise understand and grasp the overall picture of its own data resources, but also facilitates further processing and analysis of the data.

[0098] In a possible implementation, the method further includes:

[0099] Update the common data list according to the set update conditions.

[0100] Optionally, setting the update condition includes setting the update interval to be equal to the set update cycle, and / or receiving a data change request instruction from the PMS system, the ERP system, and the OMS system, wherein the data change request instruction includes a data modification instruction, a data addition instruction, or a data deletion instruction.

[0101] Among them, regular or irregular updates of common data lists according to these preset update conditions can ensure the timeliness and accuracy of the data lists, thereby providing more reliable data support for corporate decision-making.

[0102] Optionally, setting the update condition also includes restoring the central data warehouse status from an offline state to an online state.

[0103] In the actual implementation process, the central data warehouse may experience offline failures or other failures, which may cause data inconsistency and delay. Therefore, when the central data warehouse is restored, the common data list needs to be updated to ensure the latest status of the data and ensure the integrity and consistency of the data.

[0104] In this embodiment, the common data list is dynamically updated to ensure that the data list can reflect the latest data status.

[0105] In one possible implementation, the PMS system, the ERP system, and the OMS system include independent databases;

[0106] The method also includes:

[0107] When the central data warehouse is restored from an offline state to an online state, a data synchronization instruction is sent to the PMS system, the ERP system, and the OMS system respectively; wherein the data synchronization instruction includes the offline time of the central data warehouse;

[0108] Obtain data packets sent by the PMS system, ERP system and OMS system; wherein the data packets include data change logs of the PMS system, ERP system and OMS system; the data change time in the data change log is determined according to the offline time of the central data warehouse;

[0109] Update the data stored in the central data warehouse according to the data package.

[0110] During the specific implementation process, the PMS system, ERP system and OMS system each have an independent database, which do not interfere with each other and maintain the independence and integrity of the data.

[0111] When the central data warehouse is restored from an offline state to an online state, the management terminal will automatically send data synchronization instructions to the PMS system, ERP system, and OMS system. These data synchronization instructions clearly include the offline time of the central data warehouse so that each system knows the starting time point of synchronization. Subsequently, the management terminal will obtain data packets sent by the PMS system, ERP system, and OMS system. These data packets contain data change logs of each system. These logs record the data changes that have occurred in each system since the central data warehouse went offline. The time point of data change is determined based on the offline time of the central data warehouse, which ensures data consistency and synchronization accuracy, and improves data synchronization efficiency.

[0112] Finally, the management terminal updates the data stored in the central data warehouse based on these data packets to ensure that the data in the central data warehouse is up-to-date and reflects the latest data status of the PMS system, ERP system and OMS system.

[0113] In this way, based on the data change logs of the PMS system, ERP system and OMS system, the asynchronous update of the central data warehouse is realized, ensuring the real-time and accuracy of the data, while also improving the stability and reliability of the system.

[0114] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0115] The following is an embodiment of the device of the present application. For details not described in detail, please refer to the corresponding method embodiment described above.

[0116] Figure 3 is a schematic diagram of the structure of a power grid project management device based on a central data warehouse provided in an embodiment of the present application, such as Figure 3 For the sake of convenience, only the parts related to the embodiment of the present application are shown. Figure 3 As shown, the device comprises:

[0117] The parsing module 301 is used to parse the collaborative management instruction when acquiring the collaborative management instruction sent by the PMS system in response to the engineering project management task;

[0118] The sending module 302 is used to forward the material supply instruction to the ERP system when the collaborative management instruction includes the material supply instruction; and forward the power dispatching instruction to the OMS system when the collaborative management instruction includes the power dispatching instruction;

[0119] The data processing module 303 is used to obtain feedback data from the central data warehouse when obtaining the data scheduling instruction sent by the ERP system or the OMS system;

[0120] The sending module 302 is also used to feed back the feedback data to the ERP system or the OMS system accordingly;

[0121] The log module 304 is used to generate a management log based on the collaborative management instruction.

[0122] In a possible implementation, the sending module 302 is specifically configured to:

[0123] According to the data scheduling instruction sent by the ERP system, feedback data is obtained and a first data format corresponding to the ERP system is obtained, and the feedback data is packaged according to the first data format and fed back to the ERP system;

[0124] According to the data scheduling instruction sent by the OMS system, feedback data is obtained and a second data format corresponding to the OMS system is obtained, and the feedback data is packaged according to the second data format and fed back to the OMS system.

[0125] In a possible implementation, the log module 304 is specifically configured to:

[0126] generating a management log record and a record identifier according to the instruction information corresponding to the collaborative management instruction;

[0127] Among them, the instruction information includes two or more of material supply instructions, data scheduling instructions, instruction generation time, data feedback time, data feedback results and account login information.

[0128] In a possible implementation, the parsing module 301 is further configured to parse the log retrieval instruction to determine an identifier or a keyword when the log retrieval instruction is obtained;

[0129] The data processing module 303 is further configured to locate a corresponding management log record according to the identifier or the keyword.

[0130] In a possible implementation, the parsing module 301 is further configured to parse the collaborative management instruction to determine account login information before obtaining the feedback data from the central data warehouse; and determine whether the user is an authenticated user according to the account login information;

[0131] The data processing module 303 is specifically used to determine the operation authority corresponding to the account login information when the account login information corresponds to the authenticated user, and obtain the corresponding feedback data from the central data warehouse when the user has the access authority to the ERP system data, and obtain the corresponding feedback data from the central data warehouse when the user has the access authority to the OMS system data;

[0132] The device also includes a display module, which is used to generate an authentication operation interface for user authentication when the account login information corresponds to a temporary user.

[0133] In a possible implementation, the data processing module 303 is further configured to:

[0134] Obtain basic data sets of the PMS system, ERP system and OMS system for commonality analysis; wherein the basic data sets include project information, material information, order details, inventory status and financial information;

[0135] Establishing a mapping relationship between each system data field and a standard data model, and identifying the same fields in each system according to the mapping relationship;

[0136] A common data list is generated based on the same fields for storage; wherein the common data list includes key information such as data item name, data type, data format, data source system, etc.

[0137] In a possible implementation, the data processing module 303 is further configured to update the common data list according to a set update condition.

[0138] In a possible implementation, the PMS system, the ERP system and the OMS system include independent databases;

[0139] The sending module 302 is further used to send data synchronization instructions to the PMS system, the ERP system and the OMS system respectively when the central data warehouse is restored from an offline state to an online state; wherein the data synchronization instruction includes the offline time of the central data warehouse;

[0140] The data processing module 303 is used to obtain data packets sent by the PMS system, the ERP system and the OMS system; wherein the data packets include data change logs of the PMS system, the ERP system and the OMS system; the data change time in the data change log is determined according to the offline time of the central data warehouse;

[0141] The data stored in the central data warehouse is updated according to the data packet.

[0142] In this embodiment, the power grid project management system integrates a central data warehouse connecting the PMS system, the ERP system and the OMS system, which is responsible for storing the data interacting between the systems. The system realizes the automatic processing of instructions by real-time parsing the collaborative management instructions issued by the PMS system in response to the engineering project management task. When the collaborative management instruction involves material supply, the system will automatically forward the instruction to the ERP system; if the instruction involves power dispatching, the instruction will be transferred to the OMS system. In addition, the system can also respond to the data dispatching instruction issued by the ERP system or the OMS system, extract the corresponding feedback data from the central data warehouse, and accurately feed back the data to the corresponding system. Based on the collaborative management instruction, the system will also automatically generate a management log. Through this automated instruction parsing and forwarding mechanism, the need for manual operation is greatly reduced, thereby significantly improving the efficiency of project management. As the core of data sharing, the central data warehouse ensures the consistency of data between the PMS system, the ERP system and the OMS system. The system strengthens the collaborative working ability between different systems through automated instruction flow, making the project management process smoother. The generation of management logs provides the necessary transparency for the project management process, ensuring that all operations can be traced and enhancing the traceability of the project. Through the data collected and analyzed by the central data warehouse, the power grid project management obtains more accurate decision support. This embodiment effectively improves the efficiency and reliability of power grid project management.

[0143] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described or recorded in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0144] Those of ordinary skill in the art will appreciate that the templates, units, and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0145] If the module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above-mentioned embodiments of the power grid project management method based on the central data warehouse can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device that can carry the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory, random access memory, electrical carrier signal, telecommunication signal and software distribution medium.

[0146] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A power grid project management method based on a central data warehouse, characterized in that: The power grid project management system includes a central data warehouse for connecting a PMS system, an ERP system, and an OMS system and storing data from each system. The method includes: When obtaining the collaborative management instruction sent by the PMS system in response to the engineering project management task, parsing the collaborative management instruction; When the collaborative management instruction includes a material supply instruction, forwarding the material supply instruction to the ERP system; when the collaborative management instruction includes a power dispatch instruction, forwarding the power dispatch instruction to the OMS system; When the data scheduling instruction sent by the ERP system or the OMS system is obtained, feedback data is obtained from the central data warehouse, and corresponding feedback is given to the ERP system or the OMS system, and a management log is generated based on the collaborative management instruction.

2. The power grid project management method based on the central data warehouse according to claim 1 is characterized in that: The obtaining of feedback data from the central data warehouse and correspondingly feeding back to the ERP system or the OMS system includes: According to the data scheduling instruction sent by the ERP system, feedback data is obtained and a first data format corresponding to the ERP system is obtained, and the feedback data is packaged according to the first data format and fed back to the ERP system; According to the data scheduling instruction sent by the OMS system, feedback data is obtained and a second data format corresponding to the OMS system is obtained, and the feedback data is packaged according to the second data format and fed back to the OMS system; The first data format is different from the second data format.

3. The power grid project management method based on the central data warehouse according to claim 1 is characterized in that: Generating a management log based on the collaborative management instruction includes: generating a management log record and a record identifier according to the instruction information corresponding to the collaborative management instruction; Among them, the instruction information includes two or more of material supply instructions, data scheduling instructions, instruction generation time, data feedback time, data feedback results and account login information.

4. The power grid project management method based on the central data warehouse according to claim 3 is characterized in that: Also includes: When the log search instruction is obtained, the log search instruction is parsed to determine an identifier or a keyword; The corresponding management log record is located according to the identifier or the keyword.

5. The power grid project management method based on the central data warehouse according to claim 1 is characterized in that: Before obtaining the feedback data from the central data warehouse, the method further includes: Parsing the collaborative management instruction to determine account login information; Determine whether the user is an authenticated user based on the account login information; When the account login information corresponds to an authenticated user, determine the operation authority corresponding to the account login information, and obtain corresponding feedback data from the central data warehouse when the user has access rights to the ERP system data, and obtain corresponding feedback data from the central data warehouse when the user has access rights to the OMS system data; When the account login information corresponds to a temporary user, an authentication operation interface is generated to perform user authentication.

6. The power grid project management method based on the central data warehouse according to claim 1 is characterized in that: Also includes: Obtain basic data sets of the PMS system, ERP system and OMS system for commonality analysis; wherein the basic data sets include project information, material information, order details, inventory status and financial information; Establishing a mapping relationship between each system data field and a standard data model, and identifying the same fields in each system according to the mapping relationship; A common data list is generated based on the same fields for storage; wherein the common data list includes key information such as data item name, data type, data format, data source system, etc.

7. The power grid project management method based on central data warehouse according to claim 6 is characterized in that: Also includes: The common data list is updated according to the set update conditions.

8. The power grid project management method based on the central data warehouse according to claim 7 is characterized in that: The set update conditions include the update interval being equal to the set update cycle, and / or receiving data change request instructions from the PMS system, ERP system and OMS system; wherein the data change request instructions include data modification instructions, data addition instructions or data deletion instructions.

9. A power grid project management device based on a central data warehouse, characterized in that: The power grid project management system includes a central data warehouse for connecting the PMS system, ERP system and OMS system and storing data from each system. The device includes: A parsing module, configured to parse the collaborative management instruction when acquiring the collaborative management instruction sent by the PMS system in response to the engineering project management task; A sending module, configured to forward the material supply instruction to the ERP system when the collaborative management instruction includes a material supply instruction; and forward the power dispatch instruction to the OMS system when the collaborative management instruction includes a power dispatch instruction; A data processing module, configured to obtain feedback data from the central data warehouse when obtaining a data scheduling instruction sent by the ERP system or the OMS system; The sending module is further used to feed back the feedback data to the ERP system or the OMS system accordingly; A log module is used to generate a management log based on the collaborative management instruction.

10. The power grid project management device based on the central data warehouse according to claim 9, characterized in that: The log module is specifically used to generate a management log record and a record identifier according to the instruction information corresponding to the collaborative management instruction; Among them, the instruction information includes two or more of material supply instructions, data scheduling instructions, instruction generation time, data feedback time, data feedback results and account login information.

Images