Two-ticket full life cycle optimization and management method and system based on workflow

Abstract

The invention relates to the technical field of power two-ticket management, and discloses a two-ticket full life cycle optimization and management method and system based on workflow, and the method comprises the steps: obtaining the basic data of personnel qualification, equipment state and flow rule, and constructing a typical work ticket library and a typical operation ticket library; calling a work ticket template or an operation ticket template to perform information supplement, performing double verification, and then completing graded auditing and electronic signature according to preset nodes to generate an effective work ticket and an executable operation ticket; and monitoring the execution process of the effective work ticket and the executable operation ticket, and archiving execution data to a historical database to realize multi-dimensional two-ticket full-process data query, generation of an analysis report, update of basic data, a work ticket typical ticket library and an operation ticket typical ticket library. The standardized typical ticket library is constructed by integrating basic data, monitoring and archiving traceability of two tickets are achieved, standardized intelligent management of the two tickets is achieved, and the problems that existing data are scattered, compliance is poor, traceability is difficult, and no improved closed loop exists are solved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of power two-ticket management, in particular to a two-ticket full life cycle optimization and management method and system based on a work flow. BACKGROUND

[0002] In the safety production management of the power industry, the work ticket and the operation ticket, i.e. the two tickets, are the core management tools for standardizing the operation process and preventing safety risks, and the management quality directly affects the safety and operation efficiency of the power grid equipment. However, there are still many technical shortcomings in the current two-ticket management process, which is difficult to meet the standardized and intelligent management needs of the full life cycle.

[0003] Firstly, the basic data management is scattered, and personnel qualifications, equipment information and process rules are often stored in independent systems. The data is not synchronized in time, which leads to the need for manual cross-system data retrieval during subsequent ticket creation and verification. Not only is the efficiency low, but also the problems such as qualification misjudgment and equipment state mismatch are easily caused by data deviation. Secondly, the typical ticket library management lacks a standardized system, the ticket template classification is chaotic, the version update is lagging behind, a large amount of information needs to be repeatedly entered when calling, and an effective multi-department joint audit mechanism has not been established, which makes it difficult to guarantee the security and applicability of the template.

[0004] In the ticket creation and verification link, personnel qualification verification and time logic verification are mostly completed manually, which is prone to cause compliance problems such as incompatible qualifications and time conflicts due to human negligence. The change process of the work responsible person lacks standardized control, the change record is incomplete, and it is difficult to trace back. In the execution stage, there is a lack of real-time monitoring means, and it is difficult to discover and deal with the operation progress and abnormal situations (such as step skipping and overtime operation) in time. In the archiving management, the ticket and associated data (such as signature record and abnormal log) are easy to be missing, and a closed-loop mechanism of “problem analysis-optimization feedback” has not been formed, which leads to the repeated occurrence of similar management problems and the inability to achieve continuous improvement.

[0005] In summary, the existing two-ticket management method has defects such as low efficiency, high risk, difficult traceability and no optimization closed loop, and it is necessary to provide a two-ticket optimization management method covering the full life cycle, data driven and process standardized, to improve the management efficiency and safety control level. SUMMARY

[0006] Therefore, it is necessary to provide a two-ticket full life cycle optimization and management method and system based on a work flow, which integrates basic data to build a standardized typical ticket library, realizes two-ticket execution monitoring and archiving traceability, realizes two-ticket standardized and intelligent management, and solves the problems of existing data scattering, poor compliance, difficult traceability and no improvement closed loop.

[0007] In a first aspect, the present application provides a two-ticket full life cycle optimization and management method based on a work flow, comprising:

[0008] Acquire basic data on personnel qualifications, equipment status, and process rules, and construct a typical work order library and a typical operation order library based on the basic data;

[0009] The required work ticket template or operation ticket template is called from the typical work ticket library and the typical operation ticket library to supplement information. After dual verification of personnel qualifications and time logic, the hierarchical review and electronic signature are completed according to the preset nodes to generate effective work tickets and executable operation tickets.

[0010] The execution process of the effective work tickets and executable operation tickets is monitored to generate standardized tickets, and the execution data and associated record data are archived to the historical database; wherein, the associated record data includes change logs and electronic signatures;

[0011] Based on the archived work tickets and operation tickets data, multi-dimensional full-process data queries for both tickets are performed, generating analysis reports on pass rate, change rate, and timeout rate. The basic data, typical work ticket database, and typical operation ticket database are updated based on the optimization suggestions in the analysis reports.

[0012] In one embodiment, the acquisition of basic data on personnel qualifications, equipment status, and process rules, and the construction of a typical work order library and an operation order library based on the basic data, includes:

[0013] Acquire personnel qualification data, equipment status data, and process rule data as basic data, and construct a qualification association table based on the personnel qualification data, construct an equipment mapping table based on the equipment status data, and formulate audit node rules and audit standard data based on the process rule data;

[0014] Based on the basic data, multiple work order templates are constructed according to the dual dimensions of equipment type and work task. Fixed fields and editable fields are preset for the work order templates. After the multiple work order templates are reviewed, they are stored in the database to form the typical work order library.

[0015] Based on the basic data, multiple operation ticket templates are constructed according to the dual dimensions of operation task and equipment status. Operation steps, operation subjects, preconditions and risk warnings are preset for each operation ticket template. After the multiple operation ticket templates are reviewed, they are stored in the database to form the typical operation ticket library.

[0016] In one embodiment, the step of retrieving the required work ticket template or operation ticket template from the typical work ticket library and the typical operation ticket library for information supplementation, and after dual verification of personnel qualifications and time logic, completing hierarchical review and electronic signature according to preset nodes to generate effective work tickets and executable operation tickets includes:

[0017] The required work ticket template is retrieved from the typical work ticket database. After the editable fields are filled in the work ticket template, personnel qualification verification and first-time logical verification are performed to generate an initial work ticket with a verification pass indicator.

[0018] The initial work order is pushed to the preset review nodes for review in the order of nodes, and change information is recorded during the review process. After the review is approved, the initial work order is marked as an effective work order and pushed to all participants, and a unique ticket number is generated.

[0019] The required operation ticket template is retrieved from the typical operation ticket database. The operation plan time and the name of the supervisor are added to the operation ticket template, and a second time logic verification is performed to generate an operation ticket to be reviewed with a verification pass mark.

[0020] The operation ticket to be reviewed is pushed to the preset review nodes for review in the order of nodes. After the review is passed, the operation ticket to be reviewed is marked as an executable operation ticket and pushed to the operator's mobile terminal, and a unique ticket number is generated.

[0021] In one embodiment, the personnel qualification verification includes: retrieving the qualification association table, first verifying whether the person in charge of the work has the qualification of the person in charge of the corresponding equipment, and secondly verifying whether the participants have the basic qualifications for this type of work. If any person's qualification is missing or expired, a window warning is issued and submission is prohibited. If all qualifications are compliant, the time logic verification is initiated.

[0022] The first time logic verification includes: associating the maintenance plan data in the equipment status data, checking whether the working time of the current work order overlaps with the time of other effective work orders, and checking whether the working duration exceeds the equipment's allowed power outage duration. If the time logic is compliant, an initial work order with a verification pass flag is generated.

[0023] In one embodiment, the second time logic verification includes: verifying whether the time of each operation exceeds a preset threshold according to the order of operation steps in the operation ticket template; if the order of verification steps is reversed or the time interval exceeds the preset threshold, an early warning is issued and the submission of the operation ticket is prohibited; if the verification passes, the review process begins.

[0024] In one embodiment, monitoring the execution process of the effective work ticket and executable operation ticket to generate standardized tickets and archiving the execution data and associated record data to a historical database includes:

[0025] During the execution of the work order, secondary personnel qualification verification and timeout warnings are performed, and during the execution of the operation ticket, operation time is recorded and anomaly reminders are issued. At the same time, the real-time progress and anomaly record information of the work order and operation ticket are monitored.

[0026] The completed work orders and operation tickets are checked for missing data. After the check passes, the execution data and associated record data of the work orders and operation tickets are stored in the historical database according to the preset hierarchical structure, and access control is set.

[0027] In one embodiment, secondary personnel qualification verification and timeout warnings are performed during the execution of the work order, and operation time is recorded and anomaly alerts are issued during the execution of the operation ticket. Simultaneously, the real-time progress and anomaly record information of the work order and operation ticket are monitored, including:

[0028] When a work order is executed, the qualifications of the person in charge are verified twice and compared with the personnel qualification data. If the verification is successful, the start time and end time are recorded, the actual working time is calculated, and if the actual working time exceeds the preset value of the planned time, an early warning is issued.

[0029] The operator performs the operation step by step, records the operation after each step is completed, and the supervisor confirms the actual execution time of the recorded operation step. If an operation is confirmed to be abnormal, the operation ticket is locked and the abnormal information is pushed.

[0030] Operation and maintenance personnel can monitor the progress and anomaly records of all work tickets and operation tickets in real time. They can also view the participants, execution time, signature records, and remote real-time images from the on-site video monitoring equipment through the unique ticket number of the work ticket and operation ticket.

[0031] In one embodiment, the step of performing multi-dimensional full-process data query on the archived work order and operation order data, generating analysis reports on pass rate, change rate, and timeout rate, and updating the basic data, typical work order database, and typical operation order database based on the optimization suggestions in the analysis reports includes:

[0032] Multi-dimensional traceability query: Query historical data in the historical database through multiple dimensions, including query by ticket number, query by time range, query by personnel, and query by equipment. The query results display every step of the record from creation to archiving, including the operator, time, signature, and reason for the anomaly.

[0033] Generate analysis reports: Automatically generate management analysis reports for work tickets and operation tickets on a monthly and quarterly basis. Core indicators include the pass rate of the two tickets, the change rate of the person in charge, the execution timeout rate, and the typical ticket call rate. The analysis reports are displayed in chart form and problems are marked as items to be optimized.

[0034] Optimize the feedback loop: categorize and feed back the items to be optimized in the analysis report to the basic data, typical work ticket library, and typical operation ticket library, and track the improvement effect in the next analysis report to form a continuous improvement loop of analysis-optimization-verification.

[0035] In one embodiment, the associated record data includes at least one of change logs, signature traceability records, execution exception records, and print records.

[0036] Secondly, this application also provides a workflow-based two-ticket lifecycle optimization and management system, including:

[0037] The module is used to acquire basic data on personnel qualifications, equipment status, and process rules, and to build a typical work ticket library and a typical operation ticket library based on the basic data.

[0038] The generation module is used to call the required work ticket template or operation ticket template from the typical work ticket library and the typical operation ticket library to supplement information. After double verification of personnel qualifications and time logic, it completes hierarchical review and electronic signature according to preset nodes to generate effective work tickets and executable operation tickets.

[0039] The monitoring module is used to monitor the execution process of the effective work tickets and executable operation tickets to generate standardized tickets and archive the execution data and related record data to the historical database; wherein, the related record data includes change logs and electronic signatures;

[0040] The update module is used to perform multi-dimensional full-process data query of the archived work tickets and operation tickets, generate analysis reports on pass rate, change rate, and timeout rate, and update the basic data, typical work ticket library, and typical operation ticket library based on the optimization suggestions of the analysis reports.

[0041] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method proposed in the first aspect of the embodiments of this application.

[0042] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method proposed in the first aspect of the embodiments of this application.

[0043] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, implements the method proposed in the first aspect of the embodiments of this application.

[0044] The aforementioned workflow-based optimization and management methods and systems for the entire lifecycle of work tickets and operation tickets achieve unified control over core data such as personnel qualifications, equipment information, and process rules, as well as standardized access to typical ticket templates, by constructing a centralized database of basic data and standardized typical work tickets and operation tickets. This improves data consistency and template applicability. Through personnel qualification verification, time logic verification, and standardized hierarchical review and work supervisor change processes, compliance risks such as qualification discrepancies and time conflicts caused by human error are reduced, while ensuring complete and traceable records of supervisor changes. A real-time monitoring mechanism during the execution phase of the work tickets and operation tickets can promptly capture and quickly handle abnormal situations such as skipped steps and overtime work, ensuring safe and controllable on-site operations. Relying on a complete ticket archiving management and optimization feedback mechanism, complete traceability of work ticket and operation ticket lifecycle data is achieved, effectively improving the shortcomings of traditional work ticket and operation ticket management, such as low efficiency, high risk, difficulty in traceability, and lack of continuous improvement. This comprehensively enhances the standardization, intelligence, and safety control efficiency of work ticket and operation ticket management in the power industry. Attached Figure Description

[0045] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0046] Figure 1 This is an application environment diagram of a workflow-based two-ticket full lifecycle optimization and management method in one embodiment.

[0047] Figure 2 This is a flowchart illustrating a workflow-based two-ticket full lifecycle optimization and management method in one embodiment;

[0048] Figure 3 This is a block diagram of a workflow-based two-ticket lifecycle optimization and management system in one embodiment;

[0049] Figure 4 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0050] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0051] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0052] The workflow-based two-ticket full lifecycle optimization and management method provided in this application can be applied to, for example... Figure 1 In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or located on the cloud or other network servers. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, drones, low-altitude aircraft, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, projection devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. Head-mounted devices can be virtual reality (VR) devices, augmented reality (AR) devices, smart glasses, etc. Server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0053] In one exemplary embodiment, such as Figure 2 As shown, a workflow-based two-ticket full lifecycle optimization and management method is provided, which is then applied to... Figure 1 Taking server 104 as an example, the explanation includes the following steps S1 to S4. Wherein:

[0054] S1. Obtain basic data on personnel qualifications, equipment status, and process rules, and construct a typical work order library and a typical operation order library based on the basic data.

[0055] S101. Obtain personnel qualification data, equipment status data, and process rule data as basic data, and construct a qualification association table based on personnel qualification data, construct an equipment mapping table based on equipment status data, and formulate audit node rules and audit standard data based on process rule data.

[0056] For example, obtain basic data:

[0057] (1) Personnel qualification data: Core personnel information, including name, work group, and job title, is synchronized through the application programming interface (API). The certificate numbers and validity periods of high voltage electrician certificates and work supervisor qualification certificates are extracted. A qualification association table of personnel identity document (ID)-qualification type-validity period is established to ensure that each type of qualification is accurately matched with the corresponding work scope.

[0058] (2) Equipment status data: Import all equipment information from the equipment management system, including equipment unique number, model and specifications, current operating status (operating / maintaining / standby), and maintenance plan data. Based on the equipment voltage level and wiring method, establish an equipment mapping table of equipment number-permitted working range-permitted operation type to clarify the work and operation boundaries that different equipment can carry out.

[0059] (3) Process rule data: Jointly formulate review node rules for work tickets and operation tickets with multiple departments. For example, the review of work tickets is set up with three levels of nodes: team leader → specialist → shift leader, and the review of operation tickets is set up with three levels of nodes: supervisor → shift leader → dispatcher. At the same time, review standard data is set up, including signature permission matrix (such as only the shift leader can sign the final review opinion) and time threshold (such as the maximum validity period of work tickets is 15 days and the interval between each step of operation ticket execution is no more than 10 minutes).

[0060] Finally, develop data synchronization and early warning interfaces, build a real-time synchronization channel to ensure that basic data is updated within 1 hour after personnel qualification changes or equipment status updates in the equipment management system; for scenarios such as expired personnel qualifications or adjustments to equipment maintenance plans, an automatic early warning mechanism can be set up to provide early warnings 15 days in advance, which will be pushed to relevant personnel via system messages.

[0061] S102. Based on the basic data, construct multiple types of work ticket templates according to the dual dimensions of equipment type and work task, and preset fixed fields and editable fields for the work ticket templates. After the multiple types of work ticket templates are reviewed, they are stored in the database to form a typical work ticket library.

[0062] Work order templates are built according to two dimensions: equipment type and work task, forming a typical work order library. For example, 110kV transformer maintenance, 35kV line inspection, 10kV switchgear maintenance, etc. Each work order template includes fixed fields and editable fields. The fixed fields are preset with the work location (associated with the equipment number), standard safety measures (such as setting up fences, hanging stop signs, high voltage hazard signs), and risk points (such as falls from heights, electric shock). The editable fields reserve space for the start and end time of the work, the specific person in charge, and the participants to fill in.

[0063] Obtain the departments involved in each type of work order template, and conduct joint review by multiple departments based on the corresponding part of the work order. For example, the safety supervision department reviews whether the safety measures cover all risk points of the equipment (such as confirming whether the grounding measures are in place when overhauling a transformer), and the operation and maintenance department reviews whether the operation steps conform to on-site work habits. After the final review is approved, the version number of the work order is marked and stored in the typical work order library. If the review is not approved, feedback is provided to modify the work order template for that type of work order.

[0064] Develop template retrieval and fill functions, and build a retrieval engine to enable users to perform fuzzy searches by equipment number, such as entering 110kV-001 to match related work order templates, and to perform precise searches by work type, such as selecting maintenance to display all maintenance work order templates; when a user calls a work order template, the fixed field content is automatically filled in, and the user only needs to add the editable fields, reducing the workload of repetitive data entry, and at the same time, the template call frequency is recorded for future optimization reference.

[0065] S103. Based on the basic data, construct multiple types of operation ticket templates according to the dual dimensions of operation task and equipment status, and preset operation steps, operation subjects, preconditions and risk warnings for the operation ticket templates. After reviewing the multiple types of operation ticket templates, store them in the database to form a typical operation ticket library.

[0066] Based on the dual dimensions of operation task and equipment status, multiple operation ticket templates are constructed to form a typical operation ticket library. For example, 110kV line switching operation (from operation to maintenance), 35kV capacitor switching (from standby to operation), 10kV switchgear energization (from maintenance to operation), etc. Each operation ticket template clearly defines fixed operation steps (such as switching operation must follow the sequence of disconnecting the switch → opening the isolating switch → verifying voltage → hanging the grounding wire), and marks the subject of execution of each operation (such as operator, supervisor).

[0067] Label the preconditions and risk warnings for operation: Based on the current operating status (operating / maintenance / standby) in the equipment status data in step S1, add preconditions after each operation step. For example, before disconnecting the 110kV line switch, it is necessary to confirm that the line current has dropped to 0A; before opening the isolating switch, it is necessary to confirm that the corresponding switch has been disconnected. At the same time, add risk warnings, such as using a qualified voltage detector when testing for voltage to prevent misjudgment. Finally, the safety supervision department reviews the accuracy of the preconditions to ensure operational safety.

[0068] In addition, dynamic management of operation ticket templates is implemented. When the equipment wiring method changes (such as adding a disconnecting switch) or the power grid operation mode is adjusted (such as line load transfer), the operation ticket template is updated to modify the operation ticket template and review it again. The approved operation ticket template is marked with the new version number and replaces the old version. At the same time, the old version is not deleted but archived in the historical template library and operation records (such as usage time and number of times) are retained for subsequent traceability and analysis.

[0069] S2. Retrieve the required work ticket template or operation ticket template from the typical work ticket library and the typical operation ticket library to supplement information. After double verification of personnel qualifications and time logic, complete hierarchical review and electronic signature according to preset nodes to generate effective work tickets and executable operation tickets.

[0070] S201. Retrieve the required work ticket template from the typical work ticket database, and after filling in the editable fields in the work ticket template, perform personnel qualification verification and time logic verification, and generate an initial work ticket with a verification pass indicator.

[0071] The work supervisor locates the corresponding work ticket template in the typical work ticket database, then fills in the start and end times, participant list, and specific work content in the editable fields. After completing the editable fields, the verification process begins. Verification includes personnel qualification verification and initial logical verification.

[0072] (1) Verification of the qualifications of the personnel: Retrieve the qualification association table in step S1. First, verify whether the person in charge of the work has the qualifications of the person in charge of the corresponding equipment. For example, to create a 110kV transformer work ticket, the person in charge must hold a 110kV equipment work supervisor certificate. Second, verify whether the participants have the basic qualifications for this type of work, such as a high-voltage electrician certificate. If any person's qualifications are missing or expired, a window warning will be issued and submission will be prohibited. If all qualifications are compliant, proceed to time logic verification.

[0073] (2) Perform the first time logic verification: associate the maintenance plan data in the equipment status data in step S1, first check whether the working time of the current work ticket overlaps with the time of other effective work tickets. For example, if the same equipment has a maintenance plan on September 22, the work ticket time is determined to be conflicted if it includes September 22. Secondly, check whether the working duration exceeds the equipment's allowed power outage duration. For example, if a line is allowed a maximum power outage of 8 hours, and the work ticket duration is 10 hours, it will prompt that the limit is exceeded. If there is a conflict or the limit is exceeded, an adjustment suggestion will be prompted, such as suggesting that the time be adjusted to 8:00-16:00 on September 23. If the time logic is compliant, an initial work ticket will be generated and a verification pass mark will be attached.

[0074] S202. Push the initial work ticket to the preset review nodes for review in the order of nodes, record the change information during the review process, and mark the initial work ticket as an effective work ticket to all participants after the review is passed, and generate a unique ticket number.

[0075] The initial work order is pushed to the preset review nodes for review in the order of nodes. The review focuses on the completeness of security measures, the rationality of the configuration of participating personnel, technical feasibility, and overall compliance. After each node is approved, an electronic signature is signed. The electronic signature is associated with the personnel identity information in the personnel qualification data in step S1 to ensure the authenticity of the signature.

[0076] If the person in charge needs to be changed during the review process or after the change takes effect, the personnel qualification verification in step S201 will be triggered again after the change. If the qualification is in compliance with the rules, the information of the person in charge of the work order will be updated and a change log will be generated to record the original person in charge, the new person in charge, the change time, and the approver. If the qualification is not in compliance, the change application will be rejected and the reason will be explained.

[0077] Once all preset review nodes have passed the review, the initial work ticket will be marked as an effective work ticket, a unique ticket number will be generated, and the effective work ticket will be pushed to all participants. At the same time, the effective work ticket will be synchronized to the equipment management system, and the operation status of the corresponding equipment will be updated to pending execution to avoid duplicate ticketing.

[0078] S203. Retrieve the required operation ticket template from the typical operation ticket database, and after supplementing the operation plan time and the supervisor's name in the operation ticket template, perform a second time logic verification to generate an operation ticket pending review with a verification pass mark.

[0079] Retrieve the required operation ticket template from the typical operation ticket database, add the planned operation time, supervisor's name, and remarks. After completing the operation ticket creation, execute the second time logic verification. The second time logic verification includes: verifying the time rationality of each operation step according to the operation step sequence in the operation ticket template (whether it exceeds the preset threshold). For example, the interval between disconnecting the switch and opening the isolating switch must be within 5 minutes to avoid safety risks caused by not opening the isolating switch for a long time after the switch is disconnected. The voltage test must be performed within 10 minutes after opening the isolating switch. If the verification step sequence is reversed or the time interval exceeds the limit, a warning will be issued and the submission of the operation ticket will be prohibited. If the verification passes, the review process will begin.

[0080] In addition, considering that some substations have no network coverage, when no network is detected, the operation ticket data is automatically temporarily stored locally; when the operator returns to an area with network coverage, data synchronization is triggered, the offline-created operation ticket is uploaded, and it is re-verified with the real-time device status data in the device status data in step S1. After successful synchronization, an operation ticket with a verification pass mark is generated for review.

[0081] S204. Push the operation ticket to be reviewed to the preset review nodes for review in the order of nodes. After the review is passed, mark the operation ticket to be reviewed as an executable operation ticket and push it to the operator's mobile terminal, and generate a unique ticket number.

[0082] Operation tickets awaiting review are pushed to preset review nodes for review in sequence to determine whether the operation steps are complete, whether the preconditions meet the actual site conditions, whether the operation risk control measures are in place, and whether the operation instructions conform to the power grid operation plan. Each node's review is approved, and an electronic signature is signed. The electronic signature is linked to the personnel identity information in the personnel qualification data of step S1 to ensure the authenticity of the signature. Specifically, biometric verification, such as fingerprint or facial recognition, is used during signing, comparing the signature with the personnel biometric information database in step S1. Only after successful verification can the signature be completed. Simultaneously, signature information, including the signer, signature time, mobile IP address, and location information (accurate to the substation name), is recorded to generate a signature traceability record, ensuring the signature cannot be tampered with.

[0083] Once the operation ticket is approved, it will be marked as an executable operation ticket, a unique ticket number will be generated, and the operation steps in the executable operation ticket will be synchronized to the operator's mobile device in sequence so that the operator can view the detailed information of the operation step sequence. At the same time, a reminder message that the operation ticket is executable will be pushed to the regulator.

[0084] S3. Monitor the execution process of effective work tickets and executable operation tickets to generate standardized tickets and archive the execution data and related record data to the historical database; among which, the related record data includes change logs and electronic signatures.

[0085] S301. During the execution of the work order, perform secondary personnel qualification verification and timeout warning, and during the execution of the operation ticket, record the operation time and provide abnormal reminders. At the same time, monitor the real-time progress and abnormal record information of the work order and operation ticket.

[0086] (1) Work order execution and overtime warning: When the work order is executed, the qualification of the person in charge is verified twice and compared with the personnel qualification data in step S1 to prevent the work from being started by proxy. After the verification is passed, the start time and end time are recorded and the actual working time is calculated. If the time exceeds the preset value of the planned time, such as 10%, an early warning message is immediately sent to the person in charge. The early warning message includes the ticket number, the overtime duration, and the current work content. The person in charge must explain the reason for the overtime and approve it before the work can continue.

[0087] (2) Step-by-step execution and abnormal locking of operation tickets: The operator performs the operation step by step, records the operation after each step is completed, and the supervisor confirms it on-site and records the actual execution time of the operation step; if the operator skips a step or the interval between two operation steps exceeds the time limit, the operation ticket will be automatically locked to remind the operator of the abnormal operation, and the abnormal information will be pushed and unlocked after confirmation to avoid misoperation.

[0088] (3) Real-time monitoring by management personnel: Operation and maintenance management personnel can view the progress of all work tickets and operation tickets being executed, as well as abnormal record information (such as timeouts and skipped steps) through the monitoring platform. For example, work ticket WG20250901001 has been executed 60% and operation ticket CZ20250901001 has been executed up to step 3. Through the unique ticket number of work tickets and operation tickets, the personnel involved, execution time, signature records, and remote real-time images of on-site video monitoring equipment can be viewed to intuitively monitor the operation.

[0089] S302. Perform data missing verification on completed work orders and operation tickets, and after the verification is passed, store the execution data of the work orders and operation tickets and related record data into the historical database according to the preset hierarchical structure, and set access control.

[0090] Generate standardized operation tickets: After the operation ticket is executed, an operation ticket conforming to the power industry standards is generated, which includes ticket number, operation task, operation steps (including planned time and actual time), all signatures (electronic signatures converted to image format), and exception records.

[0091] Both work tickets and operation tickets are archived in a unified manner: After the work ticket and operation ticket are executed, the main text of the work ticket and operation ticket (including all versions) and related data (change log, signature traceability record, execution exception record, and print record) are packaged and stored in the historical database in a hierarchical structure of year-month-device number. Distributed storage is used to ensure data security. When archiving, the archived status is marked and access control is set to ensure that the archived data cannot be tampered with.

[0092] Archived data integrity verification: Automatic verification is performed before archiving to check for missing data, such as missing signatures on work tickets, missing execution times for certain steps on operation tickets, and missing approver information in change logs. If missing data is found, an archived data missing reminder is sent, listing the specific missing items. After the missing data is added, the archive is re-archived until the verification passes, ensuring that the archived data is complete and traceable.

[0093] S4. Based on the archived work tickets and operation tickets data, perform multi-dimensional full-process data queries for both tickets, generate analysis reports on pass rate, change rate, and timeout rate, and update the basic data, typical work ticket library, and typical operation ticket library based on the optimization suggestions in the analysis reports.

[0094] (1) Multi-dimensional traceability query: Historical data can be queried in the historical database through multiple dimensions. For example, you can query by ticket number to view the entire process of the work ticket; query by time range to view all operation tickets and work tickets within the selected time length; query by personnel to view all work tickets for which they are in charge; query by equipment to view all operation tickets related to the equipment by equipment name; the query results display every step of the record from creation to archiving, including the operator, time, signature, and reason for the exception.

[0095] (2) Generate analysis reports: Automatically generate management analysis reports for work tickets and operation tickets on a monthly and quarterly basis. Core indicators include the pass rate of the two tickets (number of tickets that have passed verification / total number of tickets created), the change rate of the person in charge (number of tickets with changed persons in charge / total number of tickets that have taken effect), the execution timeout rate (number of tickets that have been executed overtime / total number of tickets executed), and the typical ticket call rate (number of tickets created by calling the template / total number of tickets created). The reports are displayed in the form of charts, such as bar charts to show the monthly pass rate changes and pie charts to show the percentage of abnormal reasons. At the same time, high-frequency problems are identified (such as the abnormality rate of a certain type of typical ticket reaching 20%) and marked as items to be optimized.

[0096] (3) Optimize the feedback loop of results: categorize and feed back the items to be optimized in the analysis report to the basic data, typical work ticket library, and typical operation ticket library. For example, if there are frequent warnings for personnel qualification verification, feed back to step S1, update the qualification threshold in the basic data, such as extending the qualification validity period warning time to 30 days; if the omission rate of safety measures for a certain type of work ticket is high, feed back to step S2, typical work ticket library, optimize the fixed fields of this type of typical ticket, and supplement the missing safety measures; if the operation ticket step sequence is unreasonable, feed back to step S2, typical operation ticket library, adjust the operation step sequence of the typical ticket to fit the actual situation on site; after optimization, track the improvement effect in the next report, such as whether the omission rate of this type of work ticket has decreased, forming a continuous improvement closed loop of analysis-optimization-verification.

[0097] This application's embodiments achieve unified management and standardized use of typical work tickets and operation tickets by constructing a centralized basic data and standardized typical ticket library, thereby improving data consistency and template applicability. Through personnel qualification verification, time logic verification, and standardized hierarchical review and work supervisor change processes, compliance risks such as qualification discrepancies and time conflicts caused by human error are reduced, while ensuring the complete traceability of supervisor change records. A real-time monitoring mechanism during the two-ticket execution phase can promptly capture and quickly handle abnormal situations such as skipped steps and overtime work, ensuring safe and controllable on-site operations. Relying on a complete ticket archiving management and optimization feedback mechanism, complete traceability of the entire lifecycle of two-ticket data is achieved, effectively improving the shortcomings of traditional two-ticket management, such as low efficiency, high risk, difficulty in traceability, and lack of continuous improvement, comprehensively enhancing the standardization, intelligence, and safety control efficiency of two-ticket management in the power industry.

[0098] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0099] Based on the same inventive concept, this application also provides a workflow-based two-ticket lifecycle optimization and management system for implementing the workflow-based two-ticket lifecycle optimization and management method described above. The solution provided by this system is similar to the implementation scheme described in the above method. Therefore, the specific limitations of one or more workflow-based two-ticket lifecycle optimization and management system embodiments provided below can be found in the limitations of the workflow-based two-ticket lifecycle optimization and management method described above, and will not be repeated here.

[0100] In one exemplary embodiment, such as Figure 3 As shown, a workflow-based two-ticket full lifecycle optimization and management device is provided, including: a construction module 1, a generation module 2, a monitoring module 3, and an update module 4, wherein:

[0101] Module 1 is used to acquire basic data on personnel qualifications, equipment status, and process rules, and to construct a typical work ticket library and a typical operation ticket library based on the basic data.

[0102] The generation module 2 is used to call the required work ticket template or operation ticket template from the typical work ticket library and the typical operation ticket library to supplement information. After double verification of personnel qualifications and time logic, it completes hierarchical review and electronic signature according to preset nodes to generate effective work tickets and executable operation tickets.

[0103] Monitoring module 3 is used to monitor the execution process of the effective work tickets and executable operation tickets to generate standardized tickets and archive the execution data and related record data to the historical database; wherein, the related record data includes change logs and electronic signatures;

[0104] The update module 4 is used to perform multi-dimensional full-process data query of the archived work tickets and operation tickets, generate analysis reports on pass rate, change rate, and timeout rate, and update the basic data, typical work ticket library, and typical operation ticket library based on the optimization suggestions of the analysis reports.

[0105] In one embodiment, acquiring basic data on personnel qualifications, equipment status, and process rules, and constructing a typical work order library and an typical operation order library based on the basic data, includes:

[0106] Acquire personnel qualification data, equipment status data, and process rule data as basic data, and construct a qualification association table based on the personnel qualification data, construct an equipment mapping table based on the equipment status data, and formulate audit node rules and audit standard data based on the process rule data;

[0107] Based on the basic data, multiple work order templates are constructed according to the dual dimensions of equipment type and work task. Fixed fields and editable fields are preset for the work order templates. After the multiple work order templates are reviewed, they are stored in the database to form the typical work order library.

[0108] Based on the basic data, multiple operation ticket templates are constructed according to the dual dimensions of operation task and equipment status. Operation steps, operation subjects, preconditions and risk warnings are preset for each operation ticket template. After the multiple operation ticket templates are reviewed, they are stored in the database to form the typical operation ticket library.

[0109] In one embodiment, the step of retrieving the required work ticket template or operation ticket template from the typical work ticket library and the typical operation ticket library to supplement information, and after dual verification of personnel qualifications and time logic, completing hierarchical review and electronic signature according to preset nodes to generate effective work tickets and executable operation tickets includes:

[0110] The required work ticket template is retrieved from the typical work ticket database. After the editable fields are filled in the work ticket template, personnel qualification verification and first-time logical verification are performed to generate an initial work ticket with a verification pass indicator.

[0111] The initial work order is pushed to the preset review nodes for review in the order of nodes, and change information is recorded during the review process. After the review is approved, the initial work order is marked as an effective work order and pushed to all participants, and a unique ticket number is generated.

[0112] The required operation ticket template is retrieved from the typical operation ticket database. The operation plan time and the name of the supervisor are added to the operation ticket template, and a second time logic verification is performed to generate an operation ticket to be reviewed with a verification pass mark.

[0113] The operation ticket to be reviewed is pushed to the preset review nodes for review in the order of nodes. After the review is passed, the operation ticket to be reviewed is marked as an executable operation ticket and pushed to the operator's mobile terminal, and a unique ticket number is generated.

[0114] Furthermore, the personnel qualification verification includes: retrieving the qualification association table, first verifying whether the person in charge of the work has the qualification to be the person in charge of the corresponding equipment, and secondly verifying whether the participants have the basic qualifications for this type of work. If any person's qualification is missing or expired, a window warning will be issued and submission will be prohibited. If all qualifications are compliant, the time logic verification will proceed.

[0115] The first time logic verification includes: associating the maintenance plan data in the equipment status data, checking whether the working time of the current work order overlaps with the time of other effective work orders, and checking whether the working duration exceeds the equipment's allowed power outage duration. If the time logic is compliant, an initial work order with a verification pass flag is generated.

[0116] Furthermore, the second time logic verification includes: verifying whether the time of each operation exceeds a preset threshold according to the order of operation steps in the operation ticket template; if the order of verification steps is reversed or the time interval exceeds the preset threshold, an early warning is issued and the submission of the operation ticket is prohibited; if the verification passes, the review process begins.

[0117] In one embodiment, monitoring the execution process of the effective work ticket and executable operation ticket to generate standardized tickets and archiving the execution data and associated record data to a historical database includes:

[0118] During the execution of the work order, secondary personnel qualification verification and timeout warnings are performed, and during the execution of the operation ticket, operation time is recorded and anomaly reminders are issued. At the same time, the real-time progress and anomaly record information of the work order and operation ticket are monitored.

[0119] The completed work orders and operation tickets are checked for missing data. After the check passes, the execution data and associated record data of the work orders and operation tickets are stored in the historical database according to the preset hierarchical structure, and access control is set.

[0120] Furthermore, during the execution of the work order, secondary personnel qualification verification and timeout warnings are performed, and during the execution of the operation ticket, operation time is recorded and anomaly alerts are issued. Simultaneously, the real-time progress and anomaly record information of the work order and operation ticket are monitored, including:

[0121] When a work order is executed, the qualifications of the person in charge are verified twice and compared with the personnel qualification data. If the verification is successful, the start time and end time are recorded, the actual working time is calculated, and if the actual working time exceeds the preset value of the planned time, an early warning is issued.

[0122] The operator performs the operation step by step, records the operation after each step is completed, and the supervisor confirms the actual execution time of the recorded operation step. If an operation is confirmed to be abnormal, the operation ticket is locked and the abnormal information is pushed.

[0123] Operation and maintenance personnel can monitor the progress and anomaly records of all work tickets and operation tickets in real time. They can also view the participants, execution time, signature records, and remote real-time images from the on-site video monitoring equipment through the unique ticket number of the work ticket and operation ticket.

[0124] In one embodiment, the step of performing multi-dimensional full-process data query on the archived work order and operation order data, generating analysis reports on pass rate, change rate, and timeout rate, and updating the basic data, typical work order database, and typical operation order database based on the optimization suggestions in the analysis reports includes:

[0125] Multi-dimensional traceability query: Query historical data in the historical database through multiple dimensions, including query by ticket number, query by time range, query by personnel, and query by equipment. The query results display every step of the record from creation to archiving, including the operator, time, signature, and reason for the anomaly.

[0126] Generate analysis reports: Automatically generate management analysis reports for work tickets and operation tickets on a monthly and quarterly basis. Core indicators include the pass rate of the two tickets, the change rate of the person in charge, the execution timeout rate, and the typical ticket call rate. The analysis reports are displayed in chart form and problems are marked as items to be optimized.

[0127] Optimize the feedback loop: categorize and feed back the items to be optimized in the analysis report to the basic data, typical work ticket library, and typical operation ticket library, and track the improvement effect in the next analysis report to form a continuous improvement loop of analysis-optimization-verification.

[0128] In one embodiment, the associated record data includes at least one of change logs, signature traceability records, execution exception records, and print records.

[0129] The modules in the workflow-based two-ticket lifecycle optimization and management system described above can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the computer device's memory as software, so that the processor can invoke and execute the corresponding operations of each module.

[0130] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 4 As shown, this computer device includes a processor, memory, input / output interfaces (I / O), and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores workflow-based two-ticket lifecycle optimization and management data. The I / O interfaces are used for information exchange between the processor and external devices. The communication interface is used for communication with external terminals via a network connection. When executed by the processor, the computer program implements a workflow-based two-ticket lifecycle optimization and management method.

[0131] Those skilled in the art will understand that Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0132] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the workflow-based two-ticket full lifecycle optimization and management method of this application embodiment.

[0133] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the workflow-based two-ticket full lifecycle optimization and management method of this application embodiment.

[0134] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the workflow-based two-ticket full lifecycle optimization and management method of this application embodiment.

[0135] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0136] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0137] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A workflow-based two-ticket full life cycle optimization and management method, characterized in that, The method comprises: acquiring basic data of personnel qualification, equipment state and process rules, and constructing a typical work ticket library and a typical operation ticket library according to the basic data; calling a required work ticket template or operation ticket template from the typical work ticket library and the typical operation ticket library to supplement information, and after personnel qualification and time logic double verification, completing hierarchical review and electronic signature according to preset nodes, generating an effective work ticket and an executable operation ticket; monitoring the execution process of the effective work ticket and the executable operation ticket to generate standardized tickets, and archiving execution data and associated record data to a historical database; wherein the associated record data comprises change logs and electronic signatures; realizing multi-dimensional two-ticket full-process data query according to the archived work ticket and operation ticket data, generating qualified rate, change rate and overtime rate analysis reports, and updating the basic data, the typical work ticket library and the typical operation ticket library according to optimization suggestions of the analysis reports.

2. The method of claim 1, wherein, The acquiring of the basic data of personnel qualification, equipment state and process rules, and the constructing of the typical work ticket library and the typical operation ticket library according to the basic data comprise: acquiring personnel qualification data, equipment state data and process rule data as basic data, and constructing a qualification association table according to the personnel qualification data, constructing an equipment mapping table according to the equipment state data, and formulating review node rules and review standard data according to the process rule data; constructing multiple work ticket templates according to equipment types + work tasks in two dimensions according to the basic data, and presetting fixed fields and editable fields for the work ticket templates, and storing the multiple work ticket templates in a database after review to form the typical work ticket library; constructing multiple operation ticket templates according to operation tasks + equipment states in two dimensions according to the basic data, and presetting operation steps, operation subjects, preconditions and risk prompts for the operation ticket templates, and storing the multiple operation ticket templates in a database after review to form the typical operation ticket library.

3. The method of claim 2, wherein, The calling of a required work ticket template or operation ticket template from the typical work ticket library and the typical operation ticket library to supplement information, and the generation of an effective work ticket and an executable operation ticket after personnel qualification and time logic double verification according to preset nodes comprise: calling a required work ticket template from the typical work ticket library, and after filling editable fields in the work ticket template, performing personnel qualification verification and first time logic verification to generate an initial work ticket with a verification pass identifier; pushing the initial work ticket to a preset review node for review according to node order, and recording change information during the review process, and after the review passes, marking the initial work ticket as an effective work ticket and pushing it to all participating personnel, and generating a unique ticket number; calling a required operation ticket template from the typical operation ticket library, and after supplementing operation plan time and supervisor name in the operation ticket template, performing second time logic verification to generate a to-be-reviewed operation ticket with a verification pass identifier; The to-be-audited operation ticket is pushed to a preset audit node for audit in a node order, and after the audit is passed, the to-be-audited operation ticket is marked as an executable operation ticket and pushed to a mobile terminal of an operator, and a unique ticket number is generated.

4. The method of claim 3, wherein, The personnel qualification verification comprises: calling the qualification association table, first verifying whether the work responsible person has the work responsible person qualification of the corresponding equipment, and second verifying whether the participants have the basic qualification of the work, if any personnel qualification is missing or expired, a window warning is performed and submission is prohibited, if all qualifications are compliant, time logic verification is entered; The first time logic verification comprises: associating the maintenance plan data in the equipment state data, checking whether the work time of the current work ticket overlaps with the time of other effective work tickets, and checking whether the work duration exceeds the allowed power-off duration of the equipment, if the time logic is compliant, an initial work ticket with a verification pass identifier is generated.

5. The method of claim 3, wherein, The second time logic verification comprises: according to the operation step order in the operation ticket template, verifying whether the time of each operation step exceeds a preset threshold, if the step order is reversed or the time interval exceeds the preset threshold, a warning is performed and the submission of the operation ticket is prohibited, if the verification is passed, the audit process is entered.

6. The method of claim 3, wherein, The execution process of the effective work ticket and the executable operation ticket is monitored to generate a standardized ticket, and the execution data and associated record data are archived to a historical database, comprising: Secondary personnel qualification verification and timeout warning are performed during the execution of the work ticket, and operation time recording and abnormality reminding are performed during the execution of the operation ticket, while the real-time progress and abnormality record information of the work ticket and the operation ticket are monitored; Data missing verification is performed on the executed work ticket and operation ticket, and after the verification is passed, the execution data and associated record data of the work ticket and the operation ticket are stored in the historical database according to a preset hierarchical structure, and permission control is set.

7. The method of claim 6, wherein, Secondary personnel qualification verification and timeout warning are performed during the execution of the work ticket, and operation time recording and abnormality reminding are performed during the execution of the operation ticket, while the real-time progress and abnormality record information of the work ticket and the operation ticket are monitored, comprising: Secondary verification of the responsible person's qualification is performed during the execution of the work ticket, and the personnel qualification data is compared, after the verification is passed, the start time and end time are recorded, the actual work duration is calculated, and if it exceeds the planned duration preset value, a warning is performed; The operator executes the operation step by step, records the operation after each step is completed, and the actual execution time of the operation step is confirmed by the supervisor, if the operation is confirmed to be abnormal, the operation ticket is locked and abnormal information is pushed; The operation ticket and the operation ticket are executed in real time, the progress and abnormality record information of all the work ticket and the operation ticket are monitored, the unique ticket number of the work ticket and the operation ticket is viewed to view the participants, the execution time, the signature record, and the remote real-time picture of the on-site video monitoring equipment is viewed.

8. The method of claim 7, wherein, The multi-dimensional two-ticket full-process data query is realized according to the archived work ticket and operation ticket data, qualified rate, change rate, overtime rate analysis report is generated, and the basic data, work ticket typical ticket library and operation ticket typical ticket library are updated according to the optimization suggestions of the analysis report, including: Multi-dimensional traceability query: query historical data in the historical database through multiple dimensions, including query by ticket number, query by time range, query by personnel, query by equipment, the query result shows each step record from creation to archiving, including operator, time, signature, abnormal reason; Generate analysis report: automatically generate work ticket and operation ticket management analysis report monthly and quarterly, core indicators include two-ticket qualified rate, principal change rate, execution overtime rate, typical ticket calling rate, the analysis report is displayed in the form of a chart and identifies problems marked as optimization items to be optimized; Optimization result feedback loop: classify the optimization items to be optimized in the analysis report and feed back to the basic data, work ticket typical ticket library and operation ticket typical ticket library, and track the improvement effect in the next analysis report to form an analysis-optimization-verification continuous improvement closed loop.

9. The method of claim 6, wherein, The associated record data includes at least one of change log, signature traceability record, execution exception record and print record.

10. A workflow-based two-vote full life cycle optimization and management system, characterized in that, The system includes: A construction module is configured to obtain basic data of personnel qualifications, equipment status and process rules, and to construct a work ticket typical ticket library and an operation ticket typical ticket library according to the basic data; A generation module is configured to call a required work ticket template or operation ticket template from the work ticket typical ticket library and operation ticket typical ticket library to supplement information, and to complete hierarchical review and electronic signature according to preset nodes after personnel qualification and time logic double-checking, to generate an effective work ticket and an executable operation ticket; A monitoring module is configured to monitor the execution process of the effective work ticket and the executable operation ticket to generate standardized tickets, and to archive execution data and associated record data to a historical database; wherein the associated record data includes change log and electronic signature; An update module is configured to realize multi-dimensional two-ticket full-process data query according to the archived work ticket and operation ticket data, to generate qualified rate, change rate, overtime rate analysis report, and to update the basic data, work ticket typical ticket library and operation ticket typical ticket library according to the optimization suggestions of the analysis report.

Images