Operation and maintenance service management method, model, storage medium and equipment

Abstract

The invention relates to an operation and maintenance service management method and model, a storage medium and equipment. The method comprises the following steps: generating a maintenance plan based on a pre-constructed process library; and the process library comprises a plurality of process packages. And performing pre-operation management operation according to the maintenance plan, generating a maintenance task after the pre-operation management operation is completed, and entering a task management process. And generating a work order according to task receiving and distribution conditions in the task management process, and entering a work order management process. And creating a work ticket and an operation ticket according to the work order planning link and the work order execution link in the work order management process, and entering a two-ticket management process. And according to the execution condition of the work ticket in the two-ticket management process, working procedure acceptance and task acceptance are carried out in sequence. And when a preset condition is satisfied, closing the work order. Through resource integration, process integration, data fusion and service fusion, an operation and maintenance service management system is formed, task closed loop and supervision of the whole system are completed, information islands are eliminated, and core data unification is achieved.

Description

Technical Field

[0001] The present invention relates to the field of operation and maintenance business technology, and in particular to an operation and maintenance business management method, model, storage medium and equipment. Background Art

[0002] Currently, major companies in the new energy industry have developed information systems according to their own management models, but they are basically fragmented and isolated. From the perspective of the business system, no company has yet made systematic plans for the production management system. Summary of the Invention

[0003] The technical problem to be solved by the present invention is to provide an operation and maintenance business management method, model, storage medium and device.

[0004] The technical solution adopted by the present invention to solve the technical problem is: an operation and maintenance business management method, comprising the following steps:

[0005] S1. Generate a maintenance plan based on a pre-built process library; the process library includes multiple process packages;

[0006] S2. Perform pre-operation management operations according to the maintenance plan, generate a maintenance task after completing the pre-operation management operations, and enter the task management process;

[0007] S3. Generate a work order based on the task collection and allocation in the task management process and enter the work order management process;

[0008] S4. Create work tickets and operation tickets according to the work order planning stage and work order execution stage in the work order management process, and enter the two-ticket management process;

[0009] S5. Carry out process acceptance and task acceptance in sequence according to the execution status of the work tickets in the two-ticket management process;

[0010] S6. When the preset conditions are met, close the work order.

[0011] Furthermore, in the operation and maintenance business management method of the present invention, the process library includes a model process package, an aircraft type process package, and a station process package, and step S1 includes:

[0012] Automatically generate maintenance plans based on the execution cycle of the process package in the process library.

[0013] Furthermore, in the operation and maintenance business management method of the present invention, in step S3, the task management process includes:

[0014] The user receives the maintenance task or assigns the maintenance task through the terminal;

[0015] Generate a work order based on the maintenance task or after combining the maintenance task with other tasks, and enter the work order management process;

[0016] When it is determined that the maintenance task needs to be released, if it is determined that the maintenance task has not been executed, the maintenance task is released.

[0017] Furthermore, in the operation and maintenance business management method of the present invention, step S4 includes:

[0018] Based on a pre-established basic database, in the work order planning phase, the resource scheduling required for the work order is determined. The resource scheduling includes at least one of vehicle scheduling, key scheduling, ship scheduling, and spare parts scheduling. The basic database is generated based on relevant data obtained from an external system, and includes equipment information, vehicle and ship information, regional and personnel information, and outsourcing information.

[0019] After completing the work order planning, create a work ticket and an operation ticket based on the resource scheduling outbound order generated by scanning the code during the work order execution phase, as well as the synchronized material collection information and material return information, and enter the two-ticket management process.

[0020] Furthermore, in the operation and maintenance business management method of the present invention, the basic database also stores historical work tickets, typical security measures, and typical operation tickets. The steps of creating work tickets and operation tickets and entering the two-ticket management process include:

[0021] The work ticket is created by combining the historical work ticket and the typical measures, and based on the resource scheduling and delivery order generated by scanning the code during the work order execution phase, as well as the synchronized material collection information and material return information;

[0022] Determine the current operation ticket corresponding to the work order according to the typical operation ticket;

[0023] When the work ticket issuance process is completed and the work ticket is determined to be a type of ticket, the work ticket is permitted according to the current operation ticket and executed.

[0024] Furthermore, in the operation and maintenance business management method of the present invention, step S5 includes:

[0025] The process is inspected and accepted based on the execution of the work tickets in the two-ticket management process; if the inspection fails, it is confirmed whether to re-issue the ticket; if it passes, the maintenance task is completed;

[0026] The maintenance task is inspected and accepted; if the inspection and acceptance passes, the maintenance project is completed; if not, a defect is generated or the maintenance task is regenerated.

[0027] Furthermore, in the operation and maintenance business management method of the present invention, in step S6, the preset conditions include:

[0028] Condition 1: Confirm the termination of all work tickets based on the work ticket execution status in the two-ticket management process;

[0029] Condition 2: Confirm that all materials required for the work order have been returned;

[0030] Condition 3: Confirm that all keys required for on-site operation and maintenance management of the work order have been returned;

[0031] Condition 4: Confirm that all maintenance tasks of the work order have been completed, or that there are maintenance tasks that cannot be executed and are not subject to defect conversion, or that there are maintenance tasks that need to be converted to defect execution applications;

[0032] When all of the above conditions are met, the work order is closed to form an information closed loop.

[0033] In addition, the present invention also provides an operation and maintenance business management model, including:

[0034] A maintenance plan generating unit, configured to generate a maintenance plan based on a pre-built process library; the process library includes a plurality of process packages;

[0035] A maintenance task generating unit, configured to perform pre-operation management operations according to the maintenance plan, generate a maintenance task after completing the pre-operation management operations, and enter a task management process;

[0036] The work order generation unit is used to generate work orders according to the task collection and allocation in the task management process and enter the work order management process;

[0037] The management unit is used to create work tickets and operation tickets according to the work order planning stage and work order execution stage in the work order management process, and enter the two-ticket management process;

[0038] The acceptance unit is used to carry out process acceptance and task acceptance in sequence according to the execution status of the work tickets in the two-ticket management process;

[0039] The management unit is further configured to close the work order when a preset condition is met.

[0040] In addition, the present invention also provides a computer-readable storage medium, which stores a computer program. The computer program is suitable for being loaded by a processor to execute the steps of the operation and maintenance business management method as described above.

[0041] In addition, the present invention also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the steps of the above-mentioned operation and maintenance business management method by calling the computer program stored in the memory.

[0042] The implementation of the operation and maintenance business management method, model, storage medium and equipment of the present invention has the following beneficial effects: the present invention mainly processes all resources in the production process, forms an operation and maintenance business management system by integrating resources, processes, data and business, completes the task loop and supervision of the entire system, eliminates information islands, and realizes the unification of core data. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The present invention will be further described below with reference to the accompanying drawings and embodiments, in which:

[0044] Figure 1 This is a flowchart of the operation and maintenance business management method provided by an embodiment of the present invention;

[0045] Figure 2 This is a flowchart of the operation and maintenance business management method provided by an embodiment of the present invention;

[0046] Figure 3 This is a schematic diagram of the working principle of the device management model provided by an embodiment of the present invention;

[0047] Figure 4 It is a structural diagram of the operation and maintenance business management model provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0048] In order to have a clearer understanding of the technical features, purposes and effects of the present invention, the specific embodiments of the present invention are now described in detail with reference to the accompanying drawings. In the following description, it should be understood that the directions or positional relationships indicated by "front", "back", "up", "down", "left", "right", "longitudinal", "horizontal", "vertical", "horizontal", "top", "bottom", "inside", "outside", "head", "tail", etc. are based on the directions or positional relationships shown in the accompanying drawings and are constructed and operated in specific directions. They are only for the convenience of describing the technical solution and do not indicate that the devices or components referred to must have specific directions. Therefore, they should not be understood as limiting the present invention.

[0049] It should also be noted that, unless otherwise clearly specified and limited, terms such as "installed", "connected", "connected", "fixed", and "set" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integrated connection; it can be a mechanical connection or an electrical connection; it can be directly connected or indirectly connected through an intermediate medium, and it can be the internal connection of two elements or the interaction relationship between two elements. When an element is referred to as being "on" or "under" another element, the element can be "directly" or "indirectly" located on the other element, or there may be one or more intervening elements. The terms "first", "second", "third", etc. are only for the convenience of describing the present technical solution, and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first", "second", "third", etc. may explicitly or implicitly include one or more of such features. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to the specific circumstances.

[0050] In the following description, specific details such as particular system structures and techniques are provided for purposes of illustration, not limitation, to facilitate a thorough understanding of the embodiments of the present invention. However, it will be apparent to those skilled in the art that the present invention may be practiced in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present invention with unnecessary detail.

[0051] refer to Figure 1 and Figure 2 In a preferred embodiment, the operation and maintenance business management method of this embodiment includes the following steps:

[0052] S1. Generate a maintenance plan based on a pre-built process library. The process library includes multiple process packages. Specifically, the process library includes model process packages, machine type process packages, and site process packages.

[0053] In some embodiments, this step automatically generates a maintenance plan based on the execution cycle of the process packages in the process library. Specifically, the process library is a process management library for quality control, containing multiple process packages. Each process package has an execution cycle, and the maintenance plan is automatically generated based on the execution cycle.

[0054] As you can understand, a process package generally refers to a collection of detailed workflows and steps for various phases of a wind turbine project, such as construction, installation, and maintenance. Each process package includes key information such as the detailed steps required to complete a specific task, as well as required resources, timelines, quality control, and safety management. In the wind power sector, model process packages, machine type process packages, and site process packages are collections of detailed workflows and steps for different aspects of a wind turbine project. These process packages help ensure that all aspects of a wind turbine project are carried out efficiently and orderly. A model process package generally refers to a series of steps and processes in the design and manufacturing of a wind turbine, including conceptual design, detailed design, prototype testing, manufacturing, and quality control. A machine type process package refers to the detailed steps and processes for the manufacturing, installation, and maintenance of a specific wind turbine model. A site process package generally refers to a series of steps and processes in the construction of a wind farm, including site selection, infrastructure development, and power transmission system construction. These process packages have certain dependencies. For example, the design results in the model process package will influence the manufacturing and installation processes in the machine type process package, while the installation results in the machine type process package will influence the infrastructure development in the site process package. To ensure the smooth progress of wind power projects, these process packages need to be coordinated and consistent to ensure smooth connection between all links. Process library management requires comprehensive management of these process packages to ensure projects are completed on time, on budget, and with quality.

[0055] S2. Perform pre-operation management operations according to the maintenance plan. After completing these operations, a maintenance task is generated and the task management process begins. Pre-operation management operations may include plan approval, plan preparation approval, briefing confirmation, and personnel training.

[0056] S3. In the task management process, a work order is generated based on the task collection and allocation situation, and enters the work order management process.

[0057] In some embodiments, the task management process of step S3 includes: a user receiving a maintenance task or assigning a maintenance task through a terminal; generating a work order based on the maintenance task or combining the maintenance task with other tasks, and entering the work order management process; and upon determining that the maintenance task needs to be released, if it is determined that the maintenance task has not been executed, releasing the maintenance task.

[0058] S4. In the work order management process, a work ticket and an operation ticket are created according to the work order planning stage and the work order execution stage, and the two-ticket management process is entered. Optionally, during the work order management process, a notification ticket is generated for unplanned tasks.

[0059] As you can understand, work tickets are a crucial document and safety management tool used to guide and regulate operations such as power equipment inspection, maintenance, and construction, ensuring safety and compliance. They prevent electrical equipment misoperation by electrical operators and help quickly identify and properly address issues after incidents, preventing similar incidents from recurring. The work ticket process encompasses the CET two-ticket management system: filling out, reviewing, and executing work tickets. Operation tickets are the written documentation for electrical operations in the power system, also known as task tickets or switching operation tickets. By documenting the standardized operational sequence for switching electrical equipment from one state to another, operation tickets ensure that equipment operations are strictly carried out according to the prescribed procedures. Operation tickets are the primary measure to prevent misoperation (such as accidentally opening or closing, opening with load, closing disconnectors, and closing with ground wires). Any substation that requires multiple switching operations to change equipment status requires operation tickets.

[0060] In some embodiments, this step can be based on a pre-established basic database. During the work order planning phase, the resource scheduling required for the work order can be determined. The resource scheduling includes at least one of vehicle scheduling, key scheduling, ship scheduling, and spare parts scheduling. The basic database is established and generated based on relevant data obtained from external systems. The basic database includes equipment information, vehicle and ship information, regional and personnel information, and outsourcing information. After the work order planning is completed, based on the resource scheduling outbound order generated by scanning the code during the work order execution phase, as well as the synchronized material collection and return information, a work ticket and operation ticket are created, and the two-ticket management process is entered.

[0061] It is understood that the basic database also stores historical work tickets, typical security measures, and typical operation tickets. The steps for creating work tickets and operation tickets and entering the two-ticket management process include: combining historical work tickets and typical security measures, and creating a work ticket based on the resource scheduling and delivery order generated by scanning the code during the work order execution phase, as well as synchronized material collection and return information. The current operation ticket corresponding to the work order is determined based on the typical operation ticket. After completing the work ticket issuance process and determining that the work ticket is a ticket, the work ticket is authorized based on the current operation ticket and executed.

[0062] S5. Carry out process acceptance and task acceptance in sequence according to the execution status of the work tickets in the two-ticket management process.

[0063] In some embodiments, this step can inspect the process based on the work order execution status in the two-ticket management process. If the inspection fails, a confirmation is made as to whether a new invoice should be issued. If the inspection passes, the maintenance task is completed. The inspection task is inspected. If the inspection passes, the maintenance project is completed. If the inspection fails, a defect is generated or the maintenance task is re-generated.

[0064] S6. When the preset conditions are met, close the work order.

[0065] Specifically, the preconditions include:

[0066] Condition 1: Confirm the termination of all work tickets based on the execution status of the work tickets in the two-ticket management process.

[0067] Condition 2: Confirm that all materials required for the work order have been returned.

[0068] Condition 3: Confirm that all keys required for on-site operation and maintenance management of the work order have been returned.

[0069] Condition 4: Confirm that all maintenance tasks of the work order have been completed, or there are maintenance tasks that cannot be executed and are not applied for defect conversion, or there are maintenance tasks that need to be converted to defect execution applications.

[0070] When all the above conditions are met, the work order is closed to form an information closed loop.

[0071] This embodiment mainly links all resources in the production process in a process-based manner, and forms an operation and maintenance business management system through resource integration, process integration, data integration, and business integration, completing the task loop and supervision of the entire system, eliminating information silos, and achieving core data unification.

[0072] It can be understood that the present invention relies on master data to achieve consistency of master data in the entire production operation and maintenance management system. After the process is connected, all business data are shared in the shared database according to the nodes, and detailed data of the maintenance process is generated. The relevant records are automatically entered into the one-machine-one-file system to generate equipment files, and the pendant indicators are shared to the production operation and maintenance system through the shared database for information display and query. The entire production operation and maintenance management system process is carried out around the three key cores of notification, work order, and work ticket. The entire process planning includes: task generation, issuance of notification, issuance of work order, issuance of work ticket, notification of task and related resource collection, operation, settlement of ticket, return of materials, termination of work order, and result feedback task triggering system.

[0073] When a task is issued to a notification form, data exchange primarily involves equipment and task-related information. This is all done automatically, with manual confirmation. After manual confirmation, a work order is generated and issued. Key information for the issued work order is recorded and aggregated, including but not limited to the task start and end time, the person responsible for the task, materials, and the status of the maintenance vehicle. After the work order is issued, the person responsible for the task issues an invoice, primarily assigning tasks to team members, collecting materials, and identifying vehicles and equipment. The entire process is performed by scanning a code. Planned maintenance operations are primarily monitored by the maintenance quality management system; unplanned maintenance operations currently lack a system and require development. After the operation is completed, the time the equipment was left, the remaining materials were verified, and the equipment status was calibrated. All this is automatically recorded by the system. Material returns are returned entirely by scanning a code, with this information automatically recorded. The work order closing process primarily records and triggers the status of the equipment, materials, maintenance vehicles, and the task, completing the task closure and monitoring process for the entire system. This process is all automatically recorded, triggered, and uploaded by the system.

[0074] In some embodiments, the device information in the basic database, also known as the device management model, is currently managed by establishing device codes and device attributes. This primarily manages static attributes such as device location, system, component, and manufacturer model at the device level, failing to support the increasingly lean management requirements of digital transformation of device management. The present invention comprehensively considers the needs of digital device management and constructs a device management model through resource integration to meet the structural requirements of large-scale AI intelligence.

[0075] like Figure 3 The following is a schematic diagram of the working principle of the device management model. The device management model of this embodiment mainly includes basic information management, device model management, model management, and file management. The specific construction steps are as follows:

[0076] Establish a unified basic information management library to uniformly manage meta-models, equipment types, manufacturers, models, and batches to achieve effective management of equipment front-end information. Through complete front-end information, equipment can be effectively and clearly classified and defined.

[0077] Establish a unified metadata database to achieve normalization, standardization, and unification of business data and management data. Establish an association between the metadata database and the device model library to achieve flexible association between devices and metadata.

[0078] Based on the unified equipment model, a unified model is created and a model library is formed. Each station establishes a station equipment model by referencing the model library data. At the same time, combined with the station and project master data, a systematic management structure of regions, stations, projects, places, models, locations, systems, parts, and components is realized, which is suitable for the equipment management needs of various business formats.

[0079] Create a site equipment archive based on the site equipment model, and establish the master data of the equipment measurement points to manage the site equipment and the master data of the measurement points. Perform measurement point monitoring on the key parts and components of the equipment to achieve integrated management of the equipment, measurement points, and equipment archives. This facilitates support for equipment status history management and provides basic data for equipment management decision-making related applications.

[0080] Establish equipment management cycles and tasks based on a complete equipment model and conduct work order management to achieve integrated management of site, project master data, manufacturer model master data, equipment master data, equipment metadata, measurement master data, and business master data.

[0081] This embodiment realizes resource integration and data fusion by building a complete equipment management model, which mainly includes a systematic management structure of regions, stations, projects, locations, models, locations, systems, components, elements, and measurement points, and is conducive to forming an operation and maintenance business management system, thereby completing the task loop and supervision of the entire system, eliminating information silos, and realizing core data unification, which can be applied to the equipment management needs of various industries.

[0082] refer to Figure 4 In another preferred embodiment, the operation and maintenance business management model of this embodiment includes:

[0083] The maintenance plan generation unit is used to generate maintenance plans based on a pre-built process library. The process library includes various process packages.

[0084] The maintenance task generation unit is used to perform pre-operation management operations according to the maintenance plan, generate maintenance tasks after completing the pre-operation management operations, and enter the task management process.

[0085] The work order generation unit is used to generate work orders according to the task collection and allocation in the task management process and enter the work order management process.

[0086] The management unit is used to create work tickets and operation tickets according to the work order planning stage and work order execution stage in the work order management process, and enter the two-ticket management process.

[0087] The acceptance unit is used to carry out process acceptance and task acceptance in sequence according to the execution status of the work tickets in the two-ticket management process.

[0088] The management unit is also used to close the work order when the preset conditions are met.

[0089] In another preferred embodiment, the computer-readable storage medium of this embodiment stores a computer program, and the computer program is suitable for being loaded by a processor to execute the steps of the operation and maintenance business management method as described in the above embodiment.

[0090] In another preferred embodiment, the computer device of this embodiment includes a memory and a processor, the memory stores a computer program, and the processor executes the steps of the operation and maintenance business management method of the above embodiment by calling the computer program stored in the memory.

[0091] The computer-readable storage medium of the present invention can be any computer-readable storage medium that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disk.

[0092] The processor of the present invention is used to provide computing and control capabilities to support the operation of the entire device. It should be understood that in the embodiments of the present application, the processor can be a central processing unit (CPU), and the processor can also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc.

[0093] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0094] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0095] It is understandable that the above embodiments only express the preferred implementation modes of the present invention, and the description thereof is relatively specific and detailed, but it cannot be understood as limiting the patent scope of the present invention. It should be pointed out that for ordinary technicians in this field, without departing from the concept of the present invention, the above technical features can be freely combined, and several deformations and improvements can be made, all of which fall within the scope of protection of the present invention. Therefore, all equivalent changes and modifications made to the scope of the claims of the present invention should fall within the scope of coverage of the claims of the present invention.

Claims

1. A method for operation and maintenance business management, characterized in that: The following steps are involved: S1. Generate a maintenance plan based on a pre-built process library; the process library includes multiple process packages; S2. Perform pre-operation management operations according to the maintenance plan, generate a maintenance task after completing the pre-operation management operations, and enter the task management process; S3. Generate a work order based on the task collection and allocation in the task management process and enter the work order management process; S4. Create work tickets and operation tickets according to the work order planning stage and work order execution stage in the work order management process, and enter the two-ticket management process; S5. Carry out process acceptance and task acceptance in sequence according to the execution status of the work tickets in the two-ticket management process; S6. When the preset conditions are met, close the work order.

2. The operation and maintenance business management method according to claim 1, characterized in that: The process library includes model process packages, machine type process packages and station process packages. Step S1 includes: Automatically generate maintenance plans based on the execution cycle of the process package in the process library.

3. The operation and maintenance business management method according to claim 1, characterized in that: In step S3, the task management process includes: The user receives the maintenance task or assigns the maintenance task through the terminal; Generate a work order based on the maintenance task or after combining the maintenance task with other tasks, and enter the work order management process; When it is determined that the maintenance task needs to be released, if it is determined that the maintenance task has not been executed, the maintenance task is released.

4. The operation and maintenance business management method according to claim 1, characterized in that: Step S4 includes: Based on a pre-established basic database, in the work order planning phase, the resource scheduling required for the work order is determined. The resource scheduling includes at least one of vehicle scheduling, key scheduling, ship scheduling, and spare parts scheduling. The basic database is generated based on relevant data obtained from an external system, and includes equipment information, vehicle and ship information, regional and personnel information, and outsourcing information. After completing the work order planning, create a work ticket and an operation ticket based on the resource scheduling outbound order generated by scanning the code during the work order execution phase, as well as the synchronized material collection information and material return information, and enter the two-ticket management process.

5. The operation and maintenance business management method according to claim 4, characterized in that: The basic database also stores historical work tickets, typical security measures, and typical operation tickets. The steps of creating work tickets and operation tickets and entering the two-ticket management process include: The work ticket is created by combining the historical work ticket and the typical measures, and based on the resource scheduling and delivery order generated by scanning the code during the work order execution phase, as well as the synchronized material collection information and material return information; Determine the current operation ticket corresponding to the work order according to the typical operation ticket; When the work ticket issuance process is completed and the work ticket is determined to be a type of ticket, the work ticket is permitted according to the current operation ticket and executed.

6. The operation and maintenance business management method according to claim 1, characterized in that: Step S5 includes: The process is inspected and accepted based on the execution of the work tickets in the two-ticket management process; if the inspection fails, it is confirmed whether to re-issue the ticket; if it passes, the maintenance task is completed; The maintenance task is inspected and accepted; if the inspection and acceptance passes, the maintenance project is completed; if not, a defect is generated or the maintenance task is regenerated.

7. The operation and maintenance business management method according to claim 1, characterized in that: In step S6, the preset conditions include: Condition 1: Confirm the termination of all work tickets based on the work ticket execution status in the two-ticket management process; Condition 2: Confirm that all materials required for the work order have been returned; Condition 3: Confirm that all keys required for on-site operation and maintenance management of the work order have been returned; Condition 4: Confirm that all maintenance tasks of the work order have been completed, or that there are maintenance tasks that cannot be executed and are not subject to defect conversion, or that there are maintenance tasks that need to be converted to defect execution applications; When all of the above conditions are met, the work order is closed to form an information closed loop.

8. An operation and maintenance business management model, characterized in that: include: A maintenance plan generation unit, used to generate maintenance plans based on a pre-built process library; The process library includes multiple process packages; A maintenance task generating unit, configured to perform pre-operation management operations according to the maintenance plan, generate a maintenance task after completing the pre-operation management operations, and enter a task management process; The work order generation unit is used to generate work orders according to the task collection and allocation in the task management process and enter the work order management process; The management unit is used to create work tickets and operation tickets according to the work order planning stage and work order execution stage in the work order management process, and enter the two-ticket management process; The acceptance unit is used to carry out process acceptance and task acceptance in sequence according to the execution status of the work tickets in the two-ticket management process; The management unit is further configured to close the work order when a preset condition is met.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and the computer program is suitable for being loaded by a processor to execute the steps of the operation and maintenance business management method according to any one of claims 1 to 7.

10. A computer device, characterized in that: The system comprises a memory and a processor, wherein a computer program is stored in the memory, and the processor executes the steps of the operation and maintenance business management method according to any one of claims 1 to 7 by calling the computer program stored in the memory.

Images