Power grid relocation project management method and device, storage medium and server

Abstract

The embodiment of the invention discloses a power grid relocation project management method and device, a storage medium and a server, and relates to the field of office automation. According to the method, the current project application form is received and the voltage level information is analyzed, so that the corresponding target auditing process is determined, the process comprises a plurality of links in a specified sequence, and each link is associated with an auditing user and an uploaded attachment type. Sending the application form to an auditing user in sequence, and enabling the auditing user to upload an auditing attachment according to requirements; and then the project information and the audit process information are written into a project ledger database, and the asset information is written into an asset ledger database. And when a query request exists, respectively querying items, auditing processes and asset information in the corresponding databases. And finally, presenting the project, the auditing process and the asset information of each power grid relocation project in a visual mode on a management user server, thereby realizing standard and efficient online management from application to information display.

Description

Technical Field

[0001] This application relates to the field of office automation, and in particular to a management method, device, storage medium and server for power grid relocation projects. Background Technology

[0002] In recent years, the reform of transmission and distribution pricing has been continuously deepened, and cost supervision has increasingly stringent requirements for the verification of effective assets. At the same time, urban and rural planning and infrastructure construction have been accelerated, and power grid companies have received a large number of relocated and renovated assets formed by government subsidies and are responsible for their subsequent operation and maintenance. During the relocation and renovation projects, the company's original transmission and distribution assets are dismantled, and newly relocated or newly constructed assets need to be recorded in a timely and accurate manner and managed in a standardized manner.

[0003] Currently, there are many shortcomings in the management of relocated assets. On the one hand, the asset management process is not optimized enough, resulting in untimely asset recording. Relocation projects involve multiple stages such as asset demolition, relocation, and new construction. Poor information transmission and cumbersome processes prevent the value of relocated or newly constructed assets from being reflected in the company's accounts in a timely manner, affecting the company's lean management of assets and projects, and failing to meet the stringent requirements of transmission and distribution price reform and cost supervision. On the other hand, there is a lack of effective new models for relocated asset management. Existing management methods are mostly offline operations, making it difficult to achieve real-time monitoring and dynamic management of the entire process. Information updates are not timely or accurate, which easily leads to management loopholes and errors. In addition, offline management methods are inefficient, consuming a lot of manpower, material resources, and time costs, and cannot meet the needs of the company's rapid development. Summary of the Invention

[0004] This application provides a management method, apparatus, storage medium, and server for power grid relocation projects, which can solve the problems of non-standard process management and untimely asset recording in existing power grid relocation projects. The technical solution is as follows:

[0005] In a first aspect, embodiments of this application provide a management method for power grid relocation projects, the method comprising:

[0006] Receive the application form for the current power grid relocation project, and parse the application form to obtain the voltage level information; the voltage level information indicates <35 kV or ≥35 kV.

[0007] The corresponding target review process is determined based on the voltage level information; the target review process includes multiple steps in a specified order, and each step is associated with review user information and uploaded attachment type information;

[0008] According to the specified order, the application form is sent sequentially to the review user information associated with each stage, and the review user is instructed to upload a specified type of review attachment according to the upload attachment type information;

[0009] write the project information and the audit process information of the current grid migration project into a project ledger database, and write the asset information of the grid migration project into an asset ledger database;

[0010] query the project information and the audit process information in the project ledger database based on a project query request, and query the asset information in the asset ledger database based on an asset query request;

[0011] visually display the project information, the audit process information and the asset information of each grid migration project on a server of a management user.

[0012] In a second aspect, the embodiments of the present application provide a grid migration project management device, which comprises:

[0013] a parsing unit, configured to receive an application form of a current grid migration project, and parse the application form to obtain voltage grade information; the voltage grade information indicates < 35 kV or >= 35 kV;

[0014] a determining unit, configured to determine a target audit process according to the voltage grade information; the target audit process comprises a plurality of links in a specified order, and each link is associated with audit user information and upload attachment type information;

[0015] an executing unit, configured to sequentially send the application form to audit users indicated by the audit user information associated with each link according to the specified order, and instruct the audit users to upload audit attachments of a specified type according to the upload attachment type information;

[0016] a writing unit, configured to write the project information and the audit process information of the current grid migration project into a project ledger database, and write the asset information of the grid migration project into an asset ledger database;

[0017] a querying unit, configured to query the project information and the audit process information in the project ledger database based on a project query request, and query the asset information in the asset ledger database based on an asset query request;

[0018] a pushing unit, configured to visually display the project information, the audit process information and the asset information of each grid migration project on a server of a management user.

[0019] In a third aspect, the embodiments of the present application provide a computer storage medium, which stores a plurality of instructions suitable for being loaded and executed by a processor to perform the method steps described above.

[0020] In a fourth aspect, an embodiment of the present application provides a server, which can include a processor and a memory; wherein the memory stores a computer program, the computer program is suitable for being loaded by the processor and performing the method steps described above.

[0021] The technical scheme provided by some embodiments of the present application has at least the following beneficial effects:

[0022] By receiving the application form and analyzing the voltage level information, determining the corresponding target audit process, and sending the application form to the audit user in order, the entire audit process is standardized, the confusion and delay of information transmission are reduced, the project advancement is more orderly, the migration or newly-built asset information can be transmitted to the subsequent link in a timely manner, the timely accounting of assets is ensured, and the problem of untimely accounting caused by non-optimal process is effectively solved.

[0023] The target audit process includes multiple links in a specified order, and each link is associated with audit user information and upload attachment type information. The audit user uploads the specified type of audit attachment as required, which ensures the standardization and normalization of the audit work. At the same time, the project information and audit process information are written into the project ledger database, and the asset information is written into the asset ledger database, realizing the classified storage and standardized management of information, and solving the problem of non-standard management of the existing management mode.

[0024] Based on the project query request and the asset query request, information is queried in the corresponding database, and the project information, audit process information and asset information are visually displayed on the management user server, breaking the limitations of traditional offline management, realizing the online whole-process management of the migration asset from application, audit to information query and display, improving the management efficiency, reducing the cost of manpower, material resources and time, and meeting the needs of the rapid development of the company. BRIEF DESCRIPTION OF DRAWINGS

[0025] In order to more clearly illustrate the technical scheme in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiment or prior art description. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of these drawings.

[0026] Figure 1 is a network architecture schematic diagram provided by an embodiment of the present application;

[0027] Figure 2 is a flowchart of a management method of a power grid migration project provided by an embodiment of the present application;

[0028] Figure 3 is a structural schematic diagram of a management device of a power grid migration project provided by the present application;

[0029] Figure 4 is a schematic diagram of a computer storage medium provided by an embodiment of the present application.

[0030] Figure 5 is a structural schematic diagram of a server provided by the present application. DETAILED DESCRIPTION

[0031] In order to make the purpose, technical scheme and advantages of the present application clearer, the following will further describe the embodiments of the present application in combination with the drawings.

[0032] It should be noted that the power grid relocation project management method provided by the present application is generally executed by a server, and accordingly, the power grid relocation project management device is generally arranged in the server.

[0033] Figure 1 An exemplary network architecture that can be applied to the power grid relocation project management method or the power grid relocation project management device of the present application is shown.

[0034] As shown in Figure 1 , the network architecture can include a terminal device 101 and a server 102. The terminal device 101 and the server 102 can communicate through a network, and the network is a medium for providing a communication link between the above-mentioned units. The network can include various types of wired communication links or wireless communication links, for example, the wired communication links include optical fiber, twisted pair or coaxial cable, etc., and the wireless communication links include Bluetooth communication link, wireless fidelity (WIreless-FIdelity, Wi-Fi) communication link or microwave communication link, etc.

[0035] Among them, the server 102 controls the execution of the audit process of the power grid relocation project, and the terminal device is the client of each audit user.

[0036] It should be noted that the terminal device 101 and the server 102 can be hardware or software. When the terminal device 101 and the server 102 are hardware, they can be implemented as a distributed server cluster composed of multiple servers, or as a single server. When the terminal device 101 and the server 102 are software, they can be implemented as multiple software or software modules (for example, used to provide distributed services), or as a single software or software module, which is not specifically limited here.

[0037] Various communication client applications can be installed on the terminal device of the present application, such as video recording applications, video playing applications, voice interaction applications, search applications, instant messaging tools, mailbox clients, social platform software, etc.

[0038] The terminal device can be hardware or software. When the terminal device is hardware, it can be various terminal devices with a display screen, including but not limited to a smart phone, a tablet computer, a laptop computer, a desktop computer, and the like. When the terminal device is software, it can be installed in the terminal devices listed above. It can be implemented as multiple software or software modules (for example, to provide distributed services), or as a single software or software module, which is not specifically limited here.

[0039] When the terminal device is hardware, a display device and a camera can also be installed thereon. The display device can be various devices that can achieve a display function, and the camera is used to collect a video stream. For example, the display device can be a cathode ray tube display (CR), a light-emitting diode display (LED), an electronic ink screen, a liquid crystal display (LCD), a plasma display panel (PDP), and the like. A user can use the display device on the terminal device to view displayed text, pictures, videos, and the like.

[0040] It should be understood that Figure 1 The number of terminal devices, networks, and servers in the above description is only illustrative. According to the needs of implementation, there can be any number of terminal devices, networks, and servers.

[0041] The following will be described in detail with reference to the accompanying drawings. Figure 2 The power grid relocation project management method provided by the embodiment of the application will be described in detail. The power grid relocation project management device in the embodiment of the application can be a server as shown in the server. Figure 1

[0042] Please refer to Figure 2 A flowchart of a power grid relocation project management method provided by the embodiment of the application is shown. As shown in the flowchart, the method provided by the embodiment of the application can include the following steps: Figure 2

[0043] S201, receiving an application form of a current power grid relocation project, and obtaining voltage level information by analyzing the application form.

[0044] The server continuously listens to network requests from a client or other systems through a specific network port configured by the server. When a new power grid relocation project application form is transmitted, the server first performs integrity check on the transmitted data packet to ensure that the data is not damaged or lost during transmission. The check methods include but are not limited to checksum calculation, data packet length verification, and the like. ​​

[0045] After the data packet is complete, the server parses the data according to the preset application form format specification (such as XML, JSON, etc. structured format). During the parsing process, the server will extract the field information of each field in the application form according to the field definition in the format specification. For the voltage level information field, the server will check whether its value meets the preset rules (such as numerical range, unit, etc.) to ensure the accuracy of the data. The voltage level information represents < 35 kilovolts or ≥ 35 kilovolts.

[0046] The server will store the voltage level information obtained by parsing in a temporary variable in the memory for subsequent processing. At the same time, the server will also record the receiving time, source IP address, etc. of the application form for subsequent log recording and audit tracking.

[0047] For example: Suppose the server listens on port 8080, when the client sends a JSON format application form to the port through HTTP POST request, the server first checks the header information of the request to ensure that the format and content type of the request meet the requirements. Then, the server reads the JSON data in the request body, parses the values of each field according to the JSON format specification. If the application form contains a field named "voltageLevel" with a value of "20kV", the server will extract the value and check whether it is within the preset range of 0-35 kilovolts. If the check is passed, the server will store "20kV" in the temporary variable and record the current time as the receiving time of the application form.

[0048] In one possible embodiment of the present application, the received application form for the current power grid relocation project, the voltage level information obtained by parsing the application form includes:

[0049] Receive the application form for the current power grid relocation project through the message queue;

[0050] Generate a Boolean value label by comparing the rule engine with the preset threshold;

[0051] If the voltage level field value is missing, prompt the applicant to complete the information through a pop-up window.

[0052] Wherein, the server establishes an asynchronous communication channel through the configuration of the message queue middleware (such as RabbitMQ or Kafka), and deploys a consumer service instance in the receiving end to listen to the specified queue. When the external system submits the application form for the power grid relocation project, the producer service serializes the application form data into standard JSON format and delivers it to the queue, and the consumer service uses the long polling mechanism to obtain messages in real time. The parsing stage adopts a hierarchical processing architecture: first extract the original field through the XML / JSON parser, and then verify the field type (such as voltage level should be numeric) and format specification through the data verification module.

[0053] The rule engine is implemented by Drools or a custom state machine, preset thresholds are dynamically managed through a configuration center, and a hot update mechanism is supported. The engine compares the parsed voltage level value with preset voltage level intervals (such as 0.4 kV, 10 kV, 35 kV, etc.) to generate a structured label containing an "is_valid_voltage" Boolean value and a "voltage_level" enumerated value. When the voltage level field is detected to be empty or null, a data integrity check process is triggered, and real-time notifications are pushed to the front end through the WebSocket protocol, a modal dialog box is popped up on the applicant's operation interface, and the dialog box contains a highlight prompt for required fields and an example value explanation.

[0054] This embodiment decouples the time sequence dependence of application form submission and processing through a message queue, improves system throughput, independently deploys the rule engine to separate business rules from core logic, shortens the online period of new voltage level standards from weeks to minutes, and greatly improves the information completion rate through the front-end real-time pop-up mechanism, effectively reduces the process rollback caused by data missing, and improves the timeliness of overall business processing.

[0055] S202, determining a corresponding target review process according to the voltage level information; the target review process includes a plurality of links in a specified order, and each link is associated with review user information and upload attachment type information.

[0056] Among them, the server pre-stores the review process configuration information corresponding to different voltage levels. These configuration information can exist in the form of database table, configuration file or data structure in memory, etc. After the server obtains the voltage level information, it will find the corresponding review process in the configuration information according to the preset matching rule (such as exact match, range match, etc.).

[0057] The review process configuration information includes the name, order, associated review user information, and upload attachment type information of each link. When the server determines the target review process, it will load these configuration information into the memory and build a review process object that contains detailed information of the review process for subsequent processing.

[0058] In order to improve the search efficiency, the server can use cache technology to cache frequently used review process configuration information in memory. When the target review process needs to be determined, the server first searches in the cache. If it does not exist in the cache, it is loaded from the database or configuration file and the cache is updated.

[0059] For example: Suppose the review process configuration information stored in the server is as follows:

[0060] For projects with voltage levels less than 35 kV, the review process is "business acceptance - scheme reply - drawing review - project construction - project acceptance - scrap and capital increase", and the associated review user information and uploaded attachment type information at each link are also defined.

[0061] When the server obtains the voltage level information as "20 kV", the server will look up the corresponding review process in the configuration information according to the exact matching rule. The server first looks up in the cache, if not found, loads the configuration information from the database, and caches it in the memory. Then, the server constructs a review process object according to the loaded configuration information, which contains the detailed information of the above six links.

[0062] For projects with voltage levels greater than or equal to 35 kV, the server queries the corresponding review process template from the process configuration database, which includes the following links: business acceptance → feasibility study review → preliminary design reply → project construction → intermediate acceptance → completion acceptance → scrap and capital increase, and the associated review user roles of each link are: business acceptance personnel, development department, construction department, design unit, construction unit, equipment department, and financial personnel. The types of attachments that need to be uploaded include acceptance reports, etc.

[0063] In some possible embodiments of the present application, the server reads the mapping relationship between voltage levels and process templates from the configuration center (such as Nacos, Consul or database table process_config) in real time. The configuration is stored in the form of key-value pairs, for example:

[0064] Key: Voltage level (such as 35 kV, 110 kV).

[0065] Value: Process template identifier (such as PROCESS_TEMPLATE_35KV).

[0066] The configuration center supports hot updates, when the administrator modifies the mapping relationship, the server receives the change notification through the publish-subscribe mode (such as WebSocket or MQ), and immediately refreshes the local cache, avoiding restarting the service.

[0067] After the server locates the target process template according to the mapping relationship, the following verifications are performed:

[0068] Structural integrity check: confirm that the template contains the required fields (link order, review user group, attachment rule), and there is no circular dependency between links.

[0069] Pre-verification of permissions: verify whether the pre-defined review user group in the template exists in the system user directory, if the user group does not exist, mark it as an exception and record the log.

[0070] Attachment rule legality: Check if the attachment rules (e.g., file type restrictions [.pdf,.docx], size upper limit 10MB) comply with the system security policy.

[0071] If the template validation fails, the server triggers an alarm and falls back to the default process template, ensuring business continuity.

[0072] The server generates a process instance based on the validated template, key operations include:

[0073] Context variable initialization: Assign a unique identifier to the instance and inject initial variables (e.g., project ID, voltage level, applicant information), which can be referenced or modified in subsequent stages.

[0074] Stage status initialization: Set all stage statuses to not started and construct a directed acyclic graph (DAG) based on stage order information to clarify the dependency between stages (e.g., "technical review" must be completed before entering "budget approval").

[0075] Timeout control configuration: Set the expected completion time for each stage (e.g., 48 hours), and automatically trigger a reminder or transfer mechanism after the timeout.

[0076] The server assigns a unique identifier to each stage in the process instance and associates the following rules:

[0077] Audit user binding: According to the user group identifier in the template, dynamically parse the user list that can currently execute the stage from the permission system (support filtering by department, role, skill label).

[0078] Attachment rule application: Embed the attachment rules defined in the template (e.g., "technical scheme needs to upload a PDF file stamped with a seal") into the stage operation interface, and the front end renders the file upload component according to the rules and implements client-side validation.

[0079] Dynamic routing rules: If the stage supports conditional branching (e.g., "add safety review when voltage level ≥ 110kV"), the server parses the rule expression in the template (e.g., ${voltage} > = 110) and determines the subsequent path at runtime.

[0080] Through the above design, the server realizes: decoupling of voltage level and audit process, administrators can quickly adjust rules through configuration center without modifying code or restarting service. Audit user group and link are associated in real time, supporting flexible allocation of approvers according to business scenarios (such as automatic expansion of approval pool during peak period). All rule checks are completed when the process instance is generated, avoiding process interruption due to configuration errors during runtime. Unique link ID and context variables run through the entire process, providing complete data chain for audit logs and problem troubleshooting. Finally, the system's adaptability to diversified audit requirements of power grid relocation projects is improved, while the operational complexity is reduced.

[0081] S203、According to the specified order, the application form is sent to the audit user indicated by the audit user information associated with each link in turn, and the audit user is instructed to upload the specified type of audit attachment according to the upload attachment type information.

[0082] Among them, the server will process each link in turn according to the link order defined in the audit process object after determining the target audit process. For each link, the server will determine the identity and contact information (such as username, email address, mobile phone number, etc.) of the audit user according to the associated audit user information.

[0083] The server will send a notification to the audit user through a preset notification mechanism (such as email, SMS, system message, etc.), informing them that there is a new application form to be audited. The notification content will include the basic information of the application form, the audit requirements, and the type information of the uploaded attachments, etc.

[0084] When the audit user receives the notification, they can access the application form information on the server through the client and upload the specified type of audit attachment according to the upload attachment type information. The server will perform format checking and size limit checking on the uploaded attachments to ensure that the attachments meet the requirements. After passing the verification, the server will store the attachments associated with the application form and update the audit status of the application form.

[0085] In order to ensure the smooth progress of the audit process, the server will record the audit time, audit result and operation information of the audit user of each link for subsequent log recording and audit tracking.

[0086] For example: Assuming that the current link is "business acceptance" and the associated audit user information is the username "user1". The server will send a notification to "user1" through email, and the email content includes the basic information of the application form (such as project name, applicant, etc.), the audit requirements (such as the completeness and accuracy of the audit application form), and the type information of the uploaded attachments (such as applicant's identification, project feasibility report, etc.).

[0087] After receiving the email, "user1" logs in to the client and accesses the application form information on the server. In the client interface, "user1" can see the detailed information of the application form and the option to upload attachments. "user1" uploads the specified type of audit attachment according to the requirements and submits the audit result. After receiving the submission request from "user1", the server performs format verification and size limit check on the uploaded attachment. If the check passes, the server stores the attachment in association with the application form and updates the audit status of the application form to "business acceptance passed".

[0088] In some possible embodiments of the present application, the server acts as the core scheduler of the entire audit process. Upon receiving the instruction to start the audit process, it accurately locates and extracts the audit user information associated with the current link from the database according to the pre-set target audit process. These audit user information includes but is not limited to user unique identifier, user role, user permission range, and other key data, which are the basis for ensuring accurate push of audit tasks.

[0089] In order to realize efficient and reliable push of audit tasks, the server adopts message queue mechanism. As an asynchronous communication method, message queue has the advantages of decoupling, peak shaving, and asynchronous processing. The server encapsulates the single audit task into a specific format message and puts it into the message queue. The message queue will accurately push the message to the client used by the corresponding audit user according to the pre-set routing rules. This mechanism not only improves the concurrent processing capability of the system, but also effectively deals with sudden high traffic situations, ensuring stable transmission of audit tasks.

[0090] When the audit user client receives the audit task message, it will immediately send an audit request to the server. After receiving the request, the server will start a strict identity verification and permission check process. Identity verification mainly matches the authentication information submitted by the audit user (such as username, password, digital certificate, etc.) with the legal user information stored in the database to ensure that the request comes from a legal audit user. Permission check checks whether the user has the permission to audit the current application form according to the role of the audit user and the pre-set permission rules. Only the audit user whose identity and permission are verified can continue the subsequent audit operation.

[0091] After verification, the server will obtain the detailed information of the application form from the database. These detailed information covers the basic information of the application form (such as application number, application time, applicant, etc.), business-related data (such as project name, amount, purpose, etc.), and historical audit records, etc. The server will arrange and encapsulate these detailed information according to the pre-set format, and then return it to the audit user client, so that the audit user can fully and accurately understand the situation of the application form.

[0092] After the user reviews the detailed information of the document on the client side, the user fills in the review opinion according to the review responsibility and business rules. The review opinion can be an approval, a query, a suggestion for modification, etc. At the same time, the user can upload the specified type of attachment according to the needs, such as relevant proof documents, approval basis, etc. After filling in the review opinion and uploading the attachment, the user submits the review result. After receiving the review result, the server parses and encapsulates the review result, extracts the key review information such as the review status (pass, reject), the review opinion, and the attachment information, etc.

[0093] The server updates the review status and the review opinion of the application form in the database according to the parsed review result. The update of the review status can reflect the progress of the application form in the review process in real time, and the record of the review opinion provides an important basis for subsequent audit and traceability.

[0094] If the review result is pass, the server will automatically obtain the review user information of the next link from the database according to the preset review process, and push the application form to the review user of the next link according to the same process as above, to promote the smooth progress of the review process.

[0095] If the review result is reject, the server will return the application form to the current review user, and record the rejection reason and modification requirement in the return information. The rejection reason can be that the content of the application form does not meet the business specification, the data is incomplete, etc., and the modification requirement clearly indicates the specific content and standard that need to be modified by the review user. The review user can modify the application form according to the information and then resubmit the review.

[0096] Through the above detailed review task pushing, identity and permission verification, information interaction and state updating, etc., the server realizes the automation, standardization and traceability of the review process. The message queue mechanism improves the concurrent processing capability and stability of the system, the strict identity and permission verification ensures the security and compliance of the review process, and the detailed information interaction and state updating provides a convenient and efficient review experience for the review user, and provides accurate and timely data support for the business management and decision-making of the enterprise.

[0097] In some possible embodiments of the present application, the server is continuously in a listening state to receive a plurality of file blocks uploaded from the review user client. The review user performs a block processing operation on the attachment to be uploaded on the client side. This process is based on a pre-set block rule, such as splitting according to a fixed size, and splitting a complete attachment into a plurality of file blocks. At the same time, the client uses multi-thread technology to create multiple parallel working threads, and each thread is responsible for uploading one or more file blocks, so as to realize parallel uploading, fully utilize network bandwidth resources, and improve uploading efficiency.

[0098] When the server receives these file blocks, it will first check each file block. The checking method usually uses a checksum algorithm. The server calculates the corresponding checksum based on the received file block data and compares it with the checksum sent by the client during uploading. If the comparison result is consistent, it means that the file block has not been damaged or lost during transmission, and the file block passes the check; if the comparison is inconsistent, it means that the file block transmission is abnormal, and the server will send a retransmission request to the client, requiring the client to upload the file block again until the check passes.

[0099] After all the file blocks are checked, the server enters the file recombination phase. The server combines these scattered file blocks according to the original order based on the file block number sequence, block division rules, and other meta-information, and restores them into a complete attachment. This process needs to accurately handle the boundaries and data connections of file blocks to ensure that the recombined attachment is completely consistent with the original attachment.

[0100] After completing the file recombination, the server stores the complete attachment obtained in the pre-configured file system. The file system can be a local disk storage or a distributed file system, and the specific choice depends on the size and performance requirements of the system. During storage, the server will generate a unique storage path for the attachment, which is usually organized according to a certain directory structure to facilitate management and searching.

[0101] At the same time, the server records the relevant information of the attachment in the database, including the storage path, file name, and the number of the document it belongs to. The storage path is used for subsequent quick positioning and access to the location of the attachment in the file system; the file name is used to identify the name of the attachment for user identification; and the number of the document it belongs to establishes the association between the attachment and the specific business document, facilitating the tracing and management of the attachment during business processing.

[0102] This embodiment can effectively deal with the network bandwidth limitations and transmission timeout problems during large attachment uploading by receiving file blocks uploaded in parallel by the client, improving the stability and efficiency of uploading. Checking the file blocks ensures the accuracy and integrity of data transmission, avoiding damage or data loss caused by transmission errors. File recombination and storage operations realize the centralized management and persistent storage of attachments, facilitating subsequent queries and use.

[0103] In some possible embodiments of the present application, the following are further included:

[0104] receiving a file from an operating personnel; the file is an acceptance report used by the operating personnel to hook to a plurality of power grid renovation projects;

[0105] After the server verifies the identity of the operating personnel, it will respectively attach the corresponding files to the selected power grid relocation project.

[0106] Among them, the server establishes a controlled file receiving channel through the configuration of the secure file transfer protocol (such as SFTP or HTTPS), and deploys identity authentication middleware (such as OAuth2.0 or JWT) in the gateway layer to perform permission verification on the requests submitted by the operating personnel. The verification process includes: parsing the access token in the request header, verifying the legitimacy of the operating personnel identity through token signature; query the role permission table in the database to confirm whether the operating personnel has the upload permission of the acceptance report of the corresponding power grid relocation project; if using digital certificate authentication, verify the certificate validity period and revocation status through the CA center.

[0107] In the file attachment stage, a distributed file storage system (such as MinIO or HDFS) is used to manage the acceptance report. The server first generates a unique identifier (UUID) for each file and persists the file metadata (including file name, size, MD5 checksum) to the database. Subsequently, the server parses the project list selected by the operating personnel on the front end (usually through a multi-select box or batch import method), iterates through each project ID, and creates a record in the "project-document association table" in the database, establishing a many-to-many relationship between the file UUID and the project ID. If the number of projects is large, the server uses an asynchronous task queue (such as Celery or Spring Batch) to process the attachment operation in batches to avoid blocking the main thread.

[0108] To ensure data consistency, the server will check the project status (such as whether it is in the "acceptance" stage) before attachment, and refuse the operation and return an explicit error code if the project status is not consistent; at the same time, basic checks are performed on the file content (such as whether the file format is PDF / DOCX, and whether the size exceeds the threshold), and real-time alarms are pushed to the front end through WebSocket when the check fails. All operations are recorded in the audit log table, including the operator, operation time, project ID, and file hash value, supporting subsequent traceability.

[0109] This embodiment effectively reduces the risk of illegal file upload through the dual mechanism of identity authentication and permission verification; the distributed file storage and asynchronous attachment design enables the system to support concurrent upload of batch files per second, greatly improving the performance compared to traditional monolithic architecture; the complete record of audit logs meets the Level 2 compliance requirements of the electric power industry, and the precise management of project-file association relationship effectively improves the efficiency of acceptance report retrieval, significantly reducing manual checking time.

[0110] S204, write the project information and audit process information of the current power grid relocation project into the project ledger database, and write the asset information of the power grid relocation project into the asset ledger database.

[0111] In the process of processing the application form, the server collects relevant information of the project (such as project name, project number, project leader, project budget, etc.) and audit process information (such as audit time, audit result, audit user of each link, etc.). These information will be organized into specific data structure to be written into the project ledger database.

[0112] For asset information, the server will extract and organize it according to the relevant information in the application form (such as the type, quantity, and specification of the power facilities to be relocated). The asset information will be written into the asset ledger database and associated with the project information for subsequent asset management and query.

[0113] Before writing into the database, the server will re-verify the data to ensure its integrity and consistency. The verification content includes non-empty field check, data type check, data range check, etc. If the verification is passed, the server will use the database connection pool to obtain the database connection and write the data into the corresponding database table through SQL statements.

[0114] To improve the performance and reliability of data writing, the server can use batch writing to write multiple project information and asset information into the database at one time. At the same time, the server will record the time of data writing, the operator, etc. for subsequent log recording and audit tracking.

[0115] For example, suppose the project information of the current power grid relocation project includes the project name "XX small community power grid relocation project", the project number "XM-2023-001", the project leader "Zhang San", the project budget "100 million yuan", etc.; the audit process information includes "business acceptance-pass (user1, 2023-10-01 10:00:00), scheme reply-pending audit", etc.; the asset information includes 1 transformer to be relocated, 1000 meters of cable, etc.

[0116] The server organizes these information into specific data structure and obtains database connection through database connection pool. Then, the server executes corresponding SQL statements to write project information and audit process information into "project information table" and "audit process table" of project ledger database, write asset information into "asset information table" of asset ledger database, and associate asset information with project information through foreign key association.

[0117] S205, based on the project query request, query the project information and audit process information in the project ledger database, and based on the asset query request, query the asset information in the asset ledger database.

[0118] When a client or other system sends a project query request or an asset query request to the server, the server parses the request and extracts the query conditions (such as project name, project number, asset type, asset number, etc.).

[0119] For a project query request, the server constructs a corresponding SQL query statement in the project ledger database according to the query conditions, obtains a database connection through a database connection pool, and performs a query operation. The query result is returned to the server in the form of a dataset.

[0120] For an asset query request, the server constructs a corresponding SQL query statement in the asset ledger database according to the query conditions, obtains a database connection through a database connection pool, and performs a query operation. The query result is returned to the server in the form of a dataset.

[0121] The server performs format conversion and processing on the query result, converting it into a format suitable for the client or other system to display (such as JSON, XML, etc.). At the same time, the server also records the time of the query request, the query conditions, the query result, etc. for subsequent log recording and audit tracking.

[0122] For example, suppose the client sends a project query request with the query condition "XX Small District Power Grid Renovation Project". The server parses the request and constructs the following SQL query statement in the project ledger database: "SELECT * FROM project information table WHERE project name = 'XX Small District Power Grid Renovation Project'".

[0123] The server obtains a database connection through a database connection pool, executes the query statement, and obtains the query result. Then, the server converts the query result into JSON format and returns it to the client.

[0124] Suppose the client sends an asset query request with the query condition "Transformer". The server parses the request and constructs the following SQL query statement in the asset ledger database: "SELECT * FROM asset information table WHERE asset type = 'Transformer'".

[0125] The server obtains a database connection through a database connection pool, executes the query statement, and obtains the query result. Then, the server converts the query result into JSON format and returns it to the client.

[0126] S206, on the terminal device of the management user, display the project information, audit process information and asset information of each power grid renovation project in a visual manner.

[0127] Wherein, after receiving the query request of the client and returning the query result, the client will generate a visual interface on the terminal device of the management user according to the query result. The visual interface can display the information of the project, the audit process information and the asset information in the form of charts, tables, maps and the like.

[0128] For the project information and the audit process information, the client can use Gantt chart, flowchart and the like to display the progress of the project and the state of the audit process. For example, the Gantt chart can display the time arrangement and the actual progress of each stage of the project, and the flowchart can display each link of the audit process and the current link.

[0129] For the asset information, the client can use tables, maps and the like to display the detailed information and the distribution of the assets. For example, the table can display the name, type, quantity, specification and the like of the assets, and the map can display the location distribution of the assets.

[0130] In order to improve the interactivity and user experience of the visual interface, the client can provide some interactive functions such as filtering, sorting, zooming, dragging and the like. The management user can further analyze and process the data through these interactive functions.

[0131] For example, assuming that the client receives the project information and the audit process information of the "XX small area power grid relocation project" returned by the server, and generates a Gantt chart and a flowchart on the terminal device of the management user. The Gantt chart displays the time arrangement and the actual progress of each stage (such as business acceptance, scheme reply, drawing review and the like) of the project, and the flowchart displays each link (such as business acceptance, scheme reply, drawing review and the like) of the audit process and the current link (such as scheme reply-pending audit).

[0132] Assuming that the client receives the transformer asset information returned by the server, and generates a table and a map on the terminal device of the management user. The table displays the name, type, quantity, specification and the like of the transformer, and the map displays the location distribution of the transformer. The management user can view the detailed information of each transformer through the markers on the map, and can filter and sort the transformers through the table.

[0133] Specifically, after receiving the request for generating visual display content for the terminal device of the management user, the server will first comprehensively and accurately extract the relevant data of each power grid relocation project from the database, which covers the project information, the audit process information and the asset information. The asset information includes the name, type, quantity, specification and location coordinates of the power grid assets and the like.

[0134] For the generation of the power grid asset statistics table, the server will organize the extracted power grid asset data according to the predetermined table format. It will take the name of the power grid asset as a column of the table, clearly showing the unique identification of each asset; the type column classifies the assets, such as transformers, transmission lines, etc., facilitating the user's quick understanding of the asset category; the quantity column intuitively presents the specific number of each asset; the specification column describes the parameters of the asset in detail, such as the capacity of the transformer, the voltage level of the transmission line, etc. In this way, the server generates a clear structure, complete information of the power grid asset statistics table, and sends it to the terminal device of the management user for display.

[0135] In terms of generating the power grid asset map, the server will use geographic information system (GIS) technology. It will accurately locate the position of each asset on the map base map according to the location coordinate data of the power grid asset, and generate corresponding markers for each position. These markers can adopt different shapes, colors or icons to distinguish different types of power grid assets, such as red circles for transformers, blue lines for transmission lines, etc. The server sends the power grid asset map with markers to the management user terminal device, enabling the user to intuitively see the distribution of various power grid assets in geographical space.

[0136] When the management user issues a viewing instruction on the marker on the terminal device, the terminal device will transmit the instruction to the server. After receiving the instruction, the server will quickly find the detailed information of the power grid asset corresponding to the marker from the database, which may include the purchase time, service life, maintenance record, etc. in addition to the content in the previous statistics table. The server will send these detailed information back to the terminal device after sorting, and display it to the user in the form of a pop-up window or other appropriate form, facilitating the user's in-depth understanding of the specific situation of the asset.

[0137] For the filtering instruction or sorting instruction issued by the management user on the terminal device on the power grid asset statistics table, the terminal device will also transmit the instruction to the server. If it is a filtering instruction, the server will filter the power grid asset data in the database according to the user-specified filtering conditions, such as asset type, quantity range, specification parameters, etc., only retaining the data that meets the conditions, and sending the filtered results back to the terminal device to generate a new statistics table. If it is a sorting instruction, the server will sort the power grid asset data according to the user-specified sorting field (such as asset name, quantity, etc.) and sorting method (ascending or descending), and then send the sorted statistics table to the terminal device for display.

[0138] The embodiment generates a power grid asset statistics table and a power grid asset map by a server and displays the same on a management user terminal device, realizes visual presentation of power grid relocation project asset information, enables a user to intuitively and comprehensively understand the distribution and basic conditions of power grid assets, and in response to a user's viewing instruction on a map mark, can quickly provide detailed information of the assets, facilitating the user to make in-depth analysis and decision. The filtering and sorting functions of the statistics table further improve the efficiency of the user to obtain the required information, enabling the user to flexibly view and analyze asset data according to different needs, and providing strong support for the management and optimization of the power grid relocation project.

[0139] The present application has the following specific advantages:

[0140] By receiving the application form and analyzing the voltage level information, the corresponding target audit process is determined, and the application form is sent to the audit user in order, which standardizes the entire audit process, reduces the confusion and delay of information transmission, makes the project advancement more orderly, and can more timely transmit the migration or newly-built asset information to the subsequent link, provides protection for timely asset accounting, and effectively solves the problem of untimely accounting caused by non-optimal process.

[0141] The target audit process includes multiple links in a specified order, and each link is associated with audit user information and upload attachment type information. The audit user uploads the specified type of audit attachment as required, which ensures the standardization and normalization of the audit work. At the same time, the project information and audit process information are written into the project account database, and the asset information is written into the asset account database, realizing the classified storage and standardized management of information, and solving the problem of non-standard management of the existing management mode.

[0142] Based on the project query request and the asset query request, information is queried in the corresponding database, and the project information, audit process information and asset information are visually displayed on the management user server, breaking the limitations of traditional offline management, realizing online whole-process management of relocation assets from application, audit to information query and display, improving the management efficiency, reducing the cost of manpower, material resources and time, and meeting the needs of rapid development of the company.

[0143] The following is an embodiment of the device of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

[0144] Please refer to Figure 3 which shows a structure schematic diagram of a power grid relocation project management device provided by an example embodiment of the present application, hereinafter referred to as device 3. The device 3 can be realized by software, hardware or a combination of the two to become all or part of a server. The device 3 comprises an analysis unit 301, a determination unit 302, an execution unit 303, a writing unit 304, a query unit 305 and a pushing unit 306.

[0145] The parsing unit 301 is configured to receive an application form of a current power grid modification project, and parse the application form to obtain voltage level information; the voltage level information indicates <35 kV or >35 kV;

[0146] The determining unit 302 is configured to determine a corresponding target review process according to the voltage level information; the target review process includes a plurality of links in a specified order, and each link is associated with review user information and upload attachment type information;

[0147] The executing unit 303 is configured to sequentially send the application form to review users indicated by the review user information associated with each link according to the specified order, and instruct the review users to upload review attachments of a specified type according to the upload attachment type information;

[0148] The writing unit 304 is configured to write project information and review process information of the current power grid modification project into a project ledger database, and write asset information of the power grid modification project into an asset ledger database;

[0149] The querying unit 305 is configured to query project information and review process information in the project ledger database based on a project query request, and query asset information in the asset ledger database based on an asset query request;

[0150] The pushing unit 306 is configured to display project information, review process information and asset information of each power grid modification project in a visual manner on a server of a management user.

[0151] In one or more possible embodiments, the receiving of the application form of the current power grid modification project and the parsing of the application form to obtain the voltage level information include:

[0152] The application form of the current power grid modification project is received through a message queue;

[0153] A Boolean value label is generated by comparing a rule engine with a preset threshold;

[0154] If the voltage level field value is missing, a pop-up window is prompted to complete the information of the applicant.

[0155] In one or more possible embodiments, the determining of the corresponding target review process according to the voltage level information includes:

[0156] A mapping relationship between voltage levels and process templates is read from a configuration center;

[0157] A process template managed by the voltage level information is determined according to the mapping relationship; the process template includes link order information, review user information and attachment rules;

[0158] generating a process instance according to the process template, initializing each link state and context variable;

[0159] allocating a unique ID for each link, and associating predefined audit user information and attachment rules for each link.

[0160] In one or more possible embodiments, the sending the application form to the audit user indicated by the audit user information associated with each link in turn according to the specified order comprises:

[0161] The server obtains the audit user information of the current link from the database according to the target audit process, and pushes the document audit task to the corresponding audit user client through the message queue. After receiving the audit task, the audit user client sends an audit request to the server;

[0162] After receiving the audit request, the server verifies the identity and authority of the audit user. After verification, it obtains the detailed information of the document from the database and returns it to the audit user client. After the audit user views the detailed information of the document, he fills in the audit opinion and uploads the specified type of attachment, and submits the audit result. After encapsulating the audit result, it is sent to the server;

[0163] After the server receives the audit result, it updates the audit state and audit opinion of the application form in the database;

[0164] If the audit is passed, the server pushes the application form to the audit user of the next link according to the preset process;

[0165] If the audit is rejected, the server returns the application form to the audit user of the current link for modification, and records the rejection reason and modification requirements.

[0166] In one or more possible embodiments, it further comprises:

[0167] The receiving unit is configured to receive a plurality of file blocks from the audit user. The plurality of file blocks are obtained by the user through the client to perform block processing on the attachments, and are uploaded to the server in parallel through the multi-thread mode.

[0168] The plurality of file blocks are checked and recombined to obtain a complete attachment, and the complete attachment is stored in the file system, and the storage path, file name and belonging document number are recorded in the database.

[0169] In one or more possible embodiments, the receiving unit is further configured to:

[0170] Receive a file from an operator; the file is an acceptance report used by the operator to connect to a plurality of power grid relocation projects.

[0171] After the server verifies the identity of the operator, it will attach the corresponding files to the selected power grid relocation project.

[0172] In one or more possible embodiments, the step of visually displaying project information, review process information, and asset information for each power grid relocation project on the user management server includes:

[0173] A power grid asset statistics table and a power grid asset map are generated on the server of the management user; the power grid asset statistics table displays the name, type, quantity and specifications of each power grid asset, and the power grid asset map displays markers indicating the location distribution of each power grid asset;

[0174] In response to a user's command to view a marker on the map, detailed information about the power grid asset corresponding to that marker is displayed;

[0175] In response to the user's filtering or sorting instructions for the power grid asset statistics table, the power grid assets in the power grid asset statistics table are filtered or sorted.

[0176] It should be noted that the device 3 provided in the above embodiments, when executing the management method for power grid relocation projects, is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the equipment can be divided into different functional modules to complete all or part of the above functions. In addition, the power grid relocation project management device and the power grid relocation project management method embodiments provided in the above embodiments belong to the same concept, and the implementation process is detailed in the method embodiments, which will not be repeated here.

[0177] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0178] See Figure 4 The diagram shown is a schematic of a computer storage medium provided in an embodiment of this application. The computer storage medium can store multiple instructions (i.e., Figure 4 The computer program shown above, the instructions of which are adapted to be loaded and executed by a processor as described above. Figure 2 The method steps of the illustrated embodiment can be found in the following documentation for detailed execution. Figure 2 The specific details of the illustrated embodiments will not be elaborated here.

[0179] This application also provides a computer program product that stores at least one instruction, which is loaded and executed by the processor to implement the power grid relocation project management method described in the above embodiments.

[0180] Please seeFigure 5 A structural schematic diagram of a server is provided for the embodiments of the present application. As shown in the figure, the server 500 can include at least one processor 501, at least one network interface 504, a user interface 503, a memory 505, and at least one communication bus 502. Figure 5

[0181] The communication bus 502 is configured to realize the connection and communication between the components.

[0182] The user interface 503 can include a display screen (Display) and a camera (Camera). Optionally, the user interface 503 can further include a standard wired interface and a wireless interface.

[0183] The network interface 504 can optionally include a standard wired interface and a wireless interface (such as a WI-FI interface).

[0184] The processor 501 can include one or more processing cores. The processor 501 connects various parts in the server 500 through various interfaces and lines, executes various functions of the server 500 and processes data by running or executing instructions, programs, code sets or instruction sets stored in the memory 505, and calling data stored in the memory 505. Optionally, the processor 501 can be implemented in at least one of the following hardware forms: Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 501 can be integrated with a combination of one or more of the following: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a modem. The CPU is mainly used to process the operating system, user interface, and application programs. The GPU is used to render and draw the content to be displayed on the display screen. The modem is used to process wireless communication. It can be understood that the above-mentioned modem can also not be integrated into the processor 501, but can be realized by a separate chip.

[0185] ​The memory 505 can include a random access memory (RAM) and can also include a read-only memory (ROM). Optionally, the memory 505 includes a non-transitory computer-readable storage medium. The memory 505 can be used to store instructions, programs, codes, code sets, or instruction sets. The memory 505 can include a program storage area and a data storage area, where the program storage area can store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the above various method embodiments, etc.; and the data storage area can store data involved in the above various method embodiments, etc. The memory 505 can also be at least one storage device located away from the processor 501. As shown in Figure 5 the memory 505 as a computer storage medium can include an operating system, a network communication module, a user interface module, and an application program.

[0186] In the server 500 as shown in Figure 5 , the user interface 503 is mainly used to provide an interface for user input and obtain user input data; and the processor 501 can be used to call an application program stored in the memory 505 and specifically execute the method as shown in Figure 2 , and the specific process can refer to Figure 2 , which will not be described here.

[0187] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by a computer program instructing related hardware, and the program can be stored in a computer readable storage medium. When the program is executed, it can include the processes of the above-mentioned method embodiments. The storage medium can be a magnetic disc, an optical disc, a read-only memory, or a random access memory, etc.

[0188] The above disclosure is only the preferred embodiment of the present application, and of course cannot limit the scope of the rights of the present application, so the equivalent changes made according to the claims of the present application still fall within the scope of the present application.

Claims

1. A management method for power grid relocation projects, characterized in that, include: Receive the application form for the current power grid relocation project and parse the application form to obtain voltage level information; Voltage level information indicates <35 kV or ≥35 kV; The corresponding target review process is determined based on the voltage level information; the target review process includes multiple steps in a specified order, and each step is associated with review user information and uploaded attachment type information; According to the specified order, the application form is sent sequentially to the review user information associated with each stage, and the review user is instructed to upload a specified type of review attachment according to the upload attachment type information; Write the project information and review process information of the current power grid relocation project into the project ledger database, and write the asset information of the power grid relocation project into the asset ledger database; Based on the project query request, query project information and review process information in the project ledger database; based on the asset query request, query asset information in the asset ledger database. The terminal devices used to manage users display project information, review process information, and asset information for each power grid relocation project in a visual manner.

2. The method according to claim 1, characterized in that, The process of receiving the application form for the current power grid relocation project and parsing the application form to obtain voltage level information includes: Receive application forms for the current power grid relocation project through a message queue; Boolean labels are generated by comparing the rules with preset thresholds using a rules engine. If the voltage level field value is missing, a pop-up window will prompt the applicant to complete the information.

3. The method according to claim 1 or 2, characterized in that, The step of determining the corresponding target review process based on the voltage level information includes: Read the mapping relationship between voltage level and process template from the configuration center; The process template for managing the voltage level information is determined based on the mapping relationship. The process template includes the sequence information of the steps, the information of the reviewing user, and the rules for attachments. Generate a process instance based on the process template, and initialize the state and context variables of each step; Assign a unique ID to each stage, and associate each stage with predefined audit user information and attachment rules.

4. The method according to claim 3, characterized in that, The step of sequentially sending the application form to the review user indicated by the review user information associated with each stage according to the specified order includes: According to the target review process, the server retrieves the review user information of the current stage from the database and pushes the document review task to the corresponding review user client through a message queue. After receiving the review task, the review user client sends a review request to the server. After receiving the review request, the server verifies the identity and permissions of the reviewing user. If the verification is successful, the server retrieves the document details from the database and returns them to the reviewing user's client. After viewing the document details, the reviewing user fills in the review comments, uploads attachments of the specified type, and submits the review result. The server then encapsulates the review result and sends it to the server. After receiving the review result, the server updates the review status and review comments of the application in the database; If the application is approved, the server will push the application form to the next reviewer according to the preset process; If the application is rejected, the server will return the application to the user who reviewed it at the current stage for modification, and record the reason for rejection and the modification requirements.

5. The method according to claim 1, 2, or 4, characterized in that, Also includes: Receive multiple file blocks from the reviewing user; the multiple file blocks are generated by the user splitting attachments into blocks through the client and uploading them to the server in parallel using a multi-threaded approach; The multiple file blocks are verified and reassembled to obtain a complete attachment, which is then stored in the file system, and the storage path, file name, and document number are recorded in the database.

6. The method according to claim 5, characterized in that, Also includes: Receive files from operators; The document in question is the acceptance report used by the operators to connect to multiple power grid relocation projects; After the server verifies the identity of the operator, it will attach the corresponding files to the selected power grid relocation project.

7. The method according to claim 1, characterized in that, The terminal equipment for managing users displays project information, review process information, and asset information for each power grid relocation project in a visual manner, including: A power grid asset statistics table and a power grid asset map are generated on the terminal device of the management user; the power grid asset statistics table displays the name, type, quantity and specifications of each power grid asset, and the power grid asset map displays markers indicating the location distribution of each power grid asset; In response to a user's command to view a marker on the map, detailed information about the power grid asset corresponding to that marker is displayed; In response to the user's filtering or sorting instructions for the power grid asset statistics table, the power grid assets in the power grid asset statistics table are filtered or sorted.

8. A management device for a power grid relocation project, characterized in that, include: The parsing unit is used to receive the application form for the current power grid relocation project and parse the application form to obtain voltage level information; Voltage level information indicates <35 kV or ≥35 kV; The determining unit is used to determine the corresponding target review process based on the voltage level information; the target review process includes multiple steps in a specified order, and each step is associated with review user information and uploaded attachment type information; The execution unit is used to send the application form sequentially to the review user information indicated by the review user information associated with each stage according to the specified order, and to instruct the review user to upload a review attachment of a specified type according to the upload attachment type information; The writing unit is used to write the project information and review process information of the current power grid relocation project into the project ledger database, and to write the asset information of the power grid relocation project into the asset ledger database. The query unit is used to query project information and review process information in the project ledger database based on a project query request, and to query asset information in the asset ledger database based on an asset query request. The push unit is used to display project information, review process information, and asset information of each power grid relocation project in a visual manner on the terminal devices of management users.

9. A computer storage medium, characterized in that, The computer storage medium stores a plurality of instructions, which are adapted to be loaded by a processor and executed as method steps as claimed in any one of claims 1 to 7.

10. A server, characterized in that, include: A processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and executed the method steps as claimed in any one of claims 1 to 7.

Images