A management system and method for electric operation tickets of mountain rail transit

Abstract

The present invention discloses a mountain rail transit power operation ticket management system and method. The system includes a service terminal subsystem and a user interaction subsystem. The service terminal subsystem includes a process configuration module, a work ticket management module, and a database. The work ticket management module includes a work ticket compilation submodule and a work ticket issuance submodule. The database includes a work ticket template library, a work ticket instance library, a workflow library, and a personnel library. The user interaction subsystem includes a plurality of server-side interaction modules, a work site interaction module, a work execution personnel terminal, and an approval personnel terminal. The method includes the steps of compiling a work ticket template, configuring a work ticket issuance process, issuing work tickets, and verifying the work execution personnel by the work site interaction module. The present invention adopts an electronic work ticket and an online approval method to improve the approval and execution efficiency of mountain rail transit power operations, and can flexibly configure the approval process and conduct supervision according to different operation situations.

Description

Technical Field

[0001] The present invention relates to the technical field of mountain rail transit power operation management, and in particular to a mountain rail transit power operation ticket management system and method. Background Art

[0002] Mountain rail transit, as a vital mode of transportation connecting mountainous areas, plays a crucial role in promoting economic development in these areas. Power supply operations, a key component of mountain rail transit systems, have a direct impact on their transport capacity and service quality, ensuring their stability and reliability.

[0003] Power work tickets are an essential, standardized management tool for power operations. However, traditional methods of managing power work tickets often rely on manual entry and paper-based approval, which presents numerous shortcomings. First, manual entry is prone to errors and omissions, resulting in inaccurate work ticket information and compromising operational safety. Second, the paper-based approval process is cumbersome and inefficient, making it difficult to meet the efficiency requirements of power operations. Furthermore, traditional management methods pose challenges such as difficulty tracing data and making statistical analysis difficult. Summary of the Invention

[0004] In response to the above-mentioned defects, the present invention provides a mountain rail transit power operation ticket management system and method, which adopts electronic operation tickets and online approval to improve the approval and execution efficiency of mountain rail transit power operations, and can flexibly configure the approval process and conduct supervision according to different operation conditions.

[0005] In order to achieve the purpose of the present invention, the following technologies are proposed:

[0006] A mountain rail transit power operation ticket management system, comprising:

[0007] The service subsystem includes a process configuration module, a job ticket management module, and a database; the job ticket management module includes a job ticket compilation submodule and a job ticket issuance submodule; the database includes a job ticket template library, a job ticket instance library, a workflow library, and a personnel library. The job ticket template library is used to store job ticket templates. The job ticket template includes an automatically generated template ID, as well as fixed fields and to-be-filled fields defined through configuration. The fixed fields include the initiation method, job content, and safety regulations, all of which have pre-defined preset values. The to-be-filled fields include the job name, job location, job time, and job executor, all of which have empty preset values. The workflow library is used to store workflow information that corresponds one-to-one to the job ticket template. The workflow information includes template ID, creation parameters, and approval parameters. The personnel library is used to store personnel information. The personnel information includes personnel ID, personnel identification data, and personnel type. Personnel types include job executors, approvers, job managers, system managers, and template compilers. The initiation methods include initiation by job executors and initiation by job managers.

[0008] The user interaction subsystem includes multiple server-side interaction modules, job site interaction modules, job execution personnel terminals, and approval personnel terminals; the server-side interaction module is used by job management personnel, system management personnel, and template compilation personnel, including a server-side personnel terminal and a personnel identifier; the job site interaction module is used by job execution personnel, including a job ticket identifier, a personnel identifier, a job toolbox, and a second clock sub-module.

[0009] A mountain rail transit power operation ticket management method using a mountain rail transit power operation ticket management system includes the following steps:

[0010] S100: The job ticket preparation submodule prepares several job ticket templates and stores them in the job ticket template library. Each job ticket template includes a template ID automatically generated by the job ticket preparation submodule;

[0011] S200: configuring a corresponding job ticket issuance process for each job ticket template;

[0012] S300: The process of issuing a work ticket includes the following steps:

[0013] S3000: After receiving the job ticket issuance request, the job ticket issuance submodule creates a job ticket instance and approves it;

[0014] S360: Determine whether the job ticket instance is approved;

[0015] S370: If the job ticket instance in S360 is approved, then:

[0016] If the person who initiates the job ticket request is the job executor, the job ticket issuance submodule issues an electronic job ticket to the job executor's terminal. If the person who initiates the job ticket request is the job management person, the job ticket issuance submodule issues an electronic job ticket to the job executor's terminal of the job executor in the job ticket instance.

[0017] At the same time, the work ticket issuing submodule obtains the work location from the electronic work ticket, and then sends the electronic work ticket as identification information to the work ticket identifier of the work site interaction module installed at the work location;

[0018] Then, S300 ends and S400 is executed;

[0019] If the job ticket instance in S360 is not approved, then S300 ends and S500 is directly executed;

[0020] S400: The operation site interaction module verifies the operation executor. If the verification is passed, the operation executor is allowed to perform the power operation, and then S500 is executed;

[0021] S500: If you want to continue using the existing job ticket template and job ticket issuance process to issue job tickets and perform power operations, continue to execute S300 and S400 in sequence. If you want to use a job ticket template that does not exist in the database to issue job tickets and perform power operations, then execute S100, S200, S300, and S400 in sequence. If you do not need to continue job ticket management, end.

[0022] Furthermore, S100 includes:

[0023] S110: The personnel identifier of the server-side interaction module identifies the template compiler;

[0024] S120: The server terminal operated by the template compiler is connected to the job ticket compilation submodule;

[0025] S130: After receiving the job ticket preparation request, the job ticket preparation submodule creates a job ticket template and automatically generates a template ID;

[0026] S140: After the template compiler completes the settings of the initiation method, work content, and safety regulations of the created job ticket template, the job ticket compilation submodule stores the job ticket template in the job ticket template library;

[0027] S150: If another job ticket template needs to be compiled, the process returns to S130 for execution. If another job ticket template does not need to be compiled, the process ends S100.

[0028] Furthermore, S200 includes:

[0029] S210: The personnel identifier of the server-side interaction module identifies the system administrator;

[0030] S220: The server terminal operated by the system administrator is connected to the process configuration module;

[0031] S230: After receiving the process configuration request, the process configuration module obtains the number n of job ticket templates from the database;

[0032] S240: The process configuration module sets i=1;

[0033] S250: Create workflow information in the workflow library. The template ID of the workflow information is the same as the template ID of the corresponding job ticket template. The creation parameters include the type of creator and the creator ID restriction. The values of the creator ID restriction include unlimited and restricted. If the value of the creator ID restriction is restricted, the creation parameters also include a creator ID list. The approval parameters include the number of approval links m and the same number of single link sub-parameters as the number of approval links m. The single link sub-parameters include the link sequence number, the approver ID list, and the approval time limit.

[0034] S260: The process configuration module automatically obtains the initiation method of the job ticket template and configures the creation personnel type to be the same as the personnel type described in the initiation method;

[0035] S270: After the system administrator completes setting the ID restriction for the creator and the approval parameters for the workflow information, the workflow configuration module stores the workflow information in the workflow library;

[0036] S280: Determine whether i=n. If so, end S200. If not, i=i+1, and then return to S250 for execution.

[0037] Furthermore, S3000 includes:

[0038] S310: The job ticket issuance submodule receives a job ticket issuance request. When a job executor initiates a job ticket request, the job executor terminal of the person initiating the job ticket request is connected to the job ticket issuance submodule. When a job manager initiates a job ticket request, after the person identifier of the server-side interaction module identifies the job manager, the server-side personnel terminal operated by the job manager is connected to the job ticket issuance submodule.

[0039] S320: If the job ticket request received by the job ticket issuing submodule in S310 is from the job executor, the job ticket issuing submodule obtains from the job ticket template library all job ticket templates whose initiation methods are values of the job executor. If the job ticket request received by the job ticket issuing submodule in S310 is from the job manager, the job ticket issuing submodule obtains from the job ticket template library all job ticket templates whose initiation methods are values of the job manager.

[0040] S330: After the person who initiated the job ticket request selects a job ticket template, the job ticket issuing submodule obtains the person ID of the person and obtains the workflow information corresponding to the selected job ticket template from the workflow library;

[0041] S340: The job ticket issuance submodule determines whether the value of the creation personnel ID restriction in the creation parameter of the workflow information in S330 is restricted. If not, the selected job ticket template is used to create the instance and S350 is executed. If so, it is determined whether the personnel ID obtained in S330 is in the creation personnel ID list. If so, the selected job ticket template is used to create the instance and S350 is executed. If not, a message to reselect the job ticket template is returned to the server personnel terminal or the job execution personnel terminal operated by the person who initiated the job ticket request, and then the process returns to S330 for execution.

[0042] S350: The job ticket issuance submodule creates a job ticket instance with the same format as the job ticket template used to create the instance, and sends the job ticket instance to the server personnel terminal or the job execution personnel terminal. The person who initiates the job ticket request fills in all the fields to be filled in and then sends the job ticket instance back to the job ticket issuance submodule. The job ticket issuance submodule obtains the approval parameters of the workflow information corresponding to the job ticket template used to create the instance.

[0043] Furthermore, S400 includes the following steps:

[0044] S410: The job ticket identifier of the job site interaction module receives a short-range communication request from the job execution personnel terminal and reads the job execution personnel's electronic job ticket;

[0045] S420: The work ticket identifier determines whether the work location in the electronic work ticket read in S410 matches the location of the work site interaction module. If not, the work site interaction module sends a message to the work executor terminal indicating that the work location is incorrect, and S400 ends. If so, S430 is executed.

[0046] S430: The second clock submodule determines whether the time of receiving the NFC request in S410 is within the operation time of the read electronic operation ticket. If not, the operation site interaction module sends a message to the operation executor terminal indicating that the operation time is incorrect, and S400 ends. If so, S440 is executed.

[0047] S440: The personnel identifier of the work site interaction module obtains personnel identification information. The work site interaction module then communicates with the server subsystem to obtain the personnel information of the work executor in the electronic work ticket read in S410 from the personnel database. The personnel identification information is compared with the personnel identification data to determine whether they match. If so, S450 is executed. If not, the work site interaction module sends a message to the work executor terminal to inform the operator of an error, and S400 ends.

[0048] S450: The operation site interaction module opens the operation toolbox and waits for the operation execution personnel to perform the power operation;

[0049] S460: After the operator completes the electrical work and returns the tools taken from the work tool box and closes the work tool box, S400 ends and S500 is executed.

[0050] Furthermore, S360 includes:

[0051] S361: The job ticket issuing submodule sets j=1;

[0052] S362: The work ticket issuing submodule sends the work ticket instance to the approver terminals of all approvers corresponding to the approver IDs in the approver ID list in the jth single link sub-parameter;

[0053] S363: After the work ticket issuing submodule receives an approval request from one of the approvers who have the work ticket instance to be approved, the work ticket issuing submodule deletes the work ticket instance from the approver terminals of the other approvers;

[0054] S364: After the approver who issued the approval request returns the approval operation to the work ticket issuing submodule, the work ticket issuing submodule determines:

[0055] If the approval operation is "Agree," S365 is directly executed. If the approval operation is "Modify," the job ticket issuance submodule updates the job ticket instance based on the changes made by the approver to the job ticket instance, and then S365 is executed. If the approval operation is "Reject," the job ticket instance described in S350 is rejected, and the job ticket issuance submodule returns a message of rejection to the server terminal operated by the person who initiated the job ticket request or the job execution terminal, and ends S360.

[0056] S365: Determine whether j = m. If so, execute S366. If not, determine j = j + 1, and then return to S362 for execution.

[0057] S366: The job ticket instance described in S350 is approved.

[0058] Furthermore, S500 also includes:

[0059] If you want to modify the job ticket template, execute S600: the job ticket preparation submodule modifies the existing job ticket template;

[0060] If the job ticket issuing process of a job ticket template is to be modified, execute S700: modify the existing workflow information through the process configuration module.

[0061] Furthermore, S600 includes the following steps:

[0062] S610: Execute S110 and S120 in sequence;

[0063] S620: The job ticket preparation submodule receives a job ticket template modification request;

[0064] S630: After the template compiler completes the settings of the initiation method, operation content, and safety regulations of the selected job ticket template, the job ticket compilation submodule updates the job ticket template to the job ticket template library.

[0065] Furthermore, S700 includes the following steps:

[0066] S710: Execute S210 and S220 in sequence;

[0067] S720: The process configuration module receives a process configuration request;

[0068] S730: After the system administrator completes the modification of the selected workflow information, the workflow configuration module stores the workflow information in the workflow library.

[0069] The beneficial effects of this technical solution are:

[0070] 1. First, electronic work tickets replace the original method of working with paper work tickets. In addition, the work ticket issuance process is configured based on the work ticket template and online approval is performed, which can improve the approval and execution efficiency of mountain rail transit power operations.

[0071] 2. Based on different work ticket templates, the work ticket issuance and execution process can be flexibly configured from multiple angles, including: setting the creation personnel type, the number of approval links, and the approval personnel according to the difficulty and danger of different power operations. If the power operation is relatively simple and the danger is low, the work ticket request can be initiated by the work executor and fewer approval links can be set. If the power operation is relatively complex and the danger is high, the work ticket request can be initiated by the work management personnel and more approval links can be set. The approval personnel for each link can also be configured. Certain approval links can be limited to high-level management personnel for approval through personnel ID.

[0072] 3. Through authority control, the security of the work ticket issuance process and the execution of power operations can be improved. Personnel using the server-side interaction module need to pass the personnel identifier detection before continuing their respective business. During the operation, they need to use the work ticket identifier to perform various identifications on the electronic work ticket, and at the same time, they need to use the personnel identifier of the work site interaction module to identify the personnel, so as to avoid the situation of falsely claiming work tickets to perform power operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] Figure 1 The overall architecture diagram of the mountain rail transit power operation ticket management system according to an embodiment of the present application is shown.

[0074] Figure 2 The overall flow chart of the mountain rail transit power operation ticket management method according to an embodiment of the present application is shown.

[0075] Figure 3 A specific flow chart of S100 of an embodiment of the present application is shown.

[0076] Figure 4 The specific flow chart of S200 of the embodiment of the present application is shown.

[0077] Figure 5 The specific flow chart of S3000 of the embodiment of the present application is shown.

[0078] Figure 6 A specific flow chart of S400 of an embodiment of the present application is shown.

[0079] Figure 7 The specific flow chart of S360 of the embodiment of the present application is shown. DETAILED DESCRIPTION

[0080] The present application will be further described below with reference to the accompanying drawings and examples.

[0081] like Figure 1 The illustrated mountain rail transit power operation ticket management system includes a service terminal system and a user interaction subsystem.

[0082] The service subsystem includes a process configuration module, a job ticket management module, and a database; the job ticket management module includes a job ticket compilation submodule, a job ticket issuance submodule, and a first clock submodule; the database includes a job ticket template library, a job ticket instance library, a workflow library, a personnel library, an approval log library, and a job log library. The job ticket template library is used to store job ticket templates. The job ticket template includes an automatically generated template ID, as well as fixed fields and to-be-filled fields defined through configuration. The fixed fields include the initiation method, job content, and safety regulations whose preset values are all pre-defined. The to-be-filled fields include the job name, job location, job time, and job executor whose preset values are all empty. The workflow library is used to store workflow information that corresponds one-to-one to the job ticket template. The workflow information includes template ID, creation parameters, and approval parameters. The personnel library is used to store personnel information. The personnel information includes personnel ID, personnel identification data, and personnel type. Personnel types include job executors, approvers, job managers, system managers, and template compilers. The initiation methods include initiation by job executors and initiation by job managers.

[0083] The user interaction subsystem includes multiple server-side interaction modules, job site interaction modules, job executor terminals, and approval personnel terminals; the server-side interaction module is used by job managers, system managers, and template compilers, and includes a server-side personnel terminal and a personnel identifier; the job site interaction module is used by job executors, and includes a job ticket identifier, a personnel identifier, a job toolbox, and a second clock sub-module.

[0084] like Figures 2 to 7 As shown, a mountain rail transit power operation ticket management method using a mountain rail transit power operation ticket management system is operated in the following steps:

[0085] S100: Preparation of a job ticket template, including the following steps:

[0086] S110: The personnel identifier of the server-side interaction module identifies the template compiler;

[0087] S120: The server terminal operated by the template compiler is connected to the job ticket compilation submodule;

[0088] S130: After receiving the job ticket preparation request, the job ticket preparation submodule creates a job ticket template and automatically generates a template ID;

[0089] S140: After the template compiler completes the settings of the initiation method, work content, and safety regulations of the created job ticket template, the job ticket compilation submodule stores the job ticket template in the job ticket template library;

[0090] S150: If another job ticket template is to be compiled, the process returns to S130 for execution. If another job ticket template is not to be compiled, S100 ends.

[0091] S200: Configuring a corresponding job ticket issuance process for each job ticket template includes the following steps:

[0092] S210: The personnel identifier of the server-side interaction module identifies the system administrator;

[0093] S220: The server terminal operated by the system administrator is connected to the process configuration module;

[0094] S230: After receiving the process configuration request, the process configuration module obtains the number n of job ticket templates from the database;

[0095] S240: The process configuration module sets i=1;

[0096] S250: Create workflow information in the workflow library. The template ID of the workflow information is the same as the template ID of the corresponding job ticket template. The creation parameters include the type of creator and the creator ID restriction. The values of the creator ID restriction include unlimited and restricted. If the value of the creator ID restriction is restricted, the creation parameters also include a creator ID list. The approval parameters include the number of approval links m and the same number of single link sub-parameters as the number of approval links m. The single link sub-parameters include the link sequence number, the approver ID list, and the approval time limit.

[0097] S260: The process configuration module automatically obtains the initiation method of the job ticket template and configures the creation personnel type to be the same as the personnel type described in the initiation method;

[0098] S270: After the system administrator completes setting the ID restriction for the creator and the approval parameters for the workflow information, the workflow configuration module stores the workflow information in the workflow library;

[0099] S280: Determine whether i=n. If so, end S200. If not, i=i+1, and then return to S250 for execution.

[0100] S300: The process of issuing a work ticket includes the following steps:

[0101] S310: The job ticket issuance submodule receives a job ticket issuance request. When a job executor initiates a job ticket request, the job executor terminal of the person initiating the job ticket request is connected to the job ticket issuance submodule. When a job manager initiates a job ticket request, after the person identifier of the server-side interaction module identifies the job manager, the server-side personnel terminal operated by the job manager is connected to the job ticket issuance submodule.

[0102] S320: If the job ticket request received by the job ticket issuing submodule in S310 is from the job executor, the job ticket issuing submodule obtains from the job ticket template library all job ticket templates whose initiation methods are values of the job executor. If the job ticket request received by the job ticket issuing submodule in S310 is from the job manager, the job ticket issuing submodule obtains from the job ticket template library all job ticket templates whose initiation methods are values of the job manager.

[0103] S330: After the person who initiated the job ticket request selects a job ticket template, the job ticket issuing submodule obtains the person ID of the person and obtains the workflow information corresponding to the selected job ticket template from the workflow library;

[0104] S340: The job ticket issuance submodule determines whether the value of the creation personnel ID restriction in the creation parameter of the workflow information in S330 is restricted. If not, the selected job ticket template is used to create the instance and S350 is executed. If so, it is determined whether the personnel ID obtained in S330 is in the creation personnel ID list. If so, the selected job ticket template is used to create the instance and S350 is executed. If not, a message to reselect the job ticket template is returned to the server personnel terminal or the job execution personnel terminal operated by the person who initiated the job ticket request, and then the process returns to S330 for execution.

[0105] S350: The job ticket issuance submodule creates a job ticket instance in the same format as the job ticket template used to create the instance, and sends the job ticket instance to the server terminal or the job executor terminal. The person who initiated the job ticket request fills in all the required fields and then sends the job ticket instance back to the job ticket issuance submodule. The job ticket issuance submodule obtains the approval parameters of the workflow information corresponding to the job ticket template used to create the instance.

[0106] S360: Approving the job ticket instance described in S350 to determine whether it is approved includes the following steps:

[0107] S361: The job ticket issuing submodule sets j=1;

[0108] S362: The work ticket issuing submodule sends the work ticket instance to the approver terminals of all approvers corresponding to the approver IDs in the approver ID list in the jth single link sub-parameter;

[0109] S363: After the job ticket issuing submodule receives an approval request from one of the approvers with the job ticket instance to be approved, the job ticket issuing submodule deletes the job ticket instance from the approver terminals of the other approvers, and the first clock submodule records the execution time of S363;

[0110] S364: After the approver who issued the approval request returns the approval operation to the work ticket issuing submodule, the work ticket issuing submodule determines:

[0111] If the approval operation is "Agree," S365 is directly executed. If the approval operation is "Modify," the job ticket issuance submodule updates the job ticket instance based on the changes made by the approver to the job ticket instance, and then S365 is executed. If the approval operation is "Reject," the job ticket instance described in S350 is rejected, and the job ticket issuance submodule returns a message of rejection to the server terminal operated by the person who initiated the job ticket request or the job execution terminal, and ends S360.

[0112] At the same time, the first clock submodule records the execution time of S364;

[0113] S365: Determine whether j = m. If so, execute S366. If not, set j = j + 1, and then return to S362 for execution. At the same time, the job ticket issuance submodule compares the total execution time of S363 and S364 with the approval time limit in the j-th single link sub-parameter. If the total time is greater than the approval time limit, a log message indicating that a timeout occurred when executing the j-th link of the job ticket instance in S350 is recorded in the approval log library.

[0114] S366: The job ticket instance described in S350 is approved;

[0115] S370: If the job ticket instance in S360 is approved, then:

[0116] If the person who initiates the job ticket request is the job executor, the job ticket issuance submodule issues an electronic job ticket to the job executor's terminal. If the person who initiates the job ticket request is the job management person, the job ticket issuance submodule issues an electronic job ticket to the job executor's terminal of the job executor in the job ticket instance.

[0117] At the same time, the work ticket issuing submodule obtains the work location from the electronic work ticket, and then sends the electronic work ticket as identification information to the work ticket identifier of the work site interaction module installed at the work location;

[0118] Then, S300 ends and S400 is executed;

[0119] If the job ticket instance in S360 is not approved, then S300 ends and S500 is directly executed;

[0120] S400: Executing electrical work, including the following steps:

[0121] S410: The work ticket identifier of the work site interaction module receives a near field communication request from the work executor terminal and reads the work executor's electronic work ticket. In this embodiment, NFC (Near Field Communication) is used between the work ticket identifier and the work executor terminal.

[0122] S420: The job ticket identifier determines whether the job location in the electronic job ticket read in S410 matches the location of the job site interaction module. If not, the job site interaction module sends a message to the job executor terminal indicating that the job location is incorrect, and sends the message to the server terminal subsystem for storage in the job log library. S400 ends. If yes, S430 is executed.

[0123] S430: The second clock submodule determines whether the time of receiving the NFC request in S410 is within the operation time of the read electronic operation ticket. If not, the operation site interaction module sends a message to the operation executor terminal indicating that the operation time is incorrect, and sends the message to the server subsystem and stores it in the operation log library, ending S400. If yes, execute S440;

[0124] S440: The personnel identifier of the work site interaction module obtains personnel identification information. In this embodiment, the personnel identifier also includes a camera submodule, which obtains a face as personnel identification information through the camera module. In other embodiments, the personnel identifier may also include a fingerprint reading module to obtain a fingerprint as personnel identification information through the fingerprint reading module. Then, the work site interaction module communicates with the server subsystem, obtains the personnel information of the work executor in the electronic work ticket read in S410 from the personnel database, compares the personnel identification information with the personnel identification data, and determines whether they match. If so, S450 is executed. If not, the work site interaction module sends a message to the work executor terminal to prompt the work executor of the error, and sends the message to the server subsystem to store it in the work log database, and ends S400.

[0125] S450: The operation site interaction module opens the operation toolbox and waits for the operation executor to perform the power operation. Meanwhile, the second clock submodule records the operation start time.

[0126] S460: After the operator completes the electrical work and returns the tools taken from the work tool box and closes the work tool box, the second clock submodule records the work end time, and the work site interaction module sends the work start time and work end time to the service subsystem. S400 ends and S500 is executed.

[0127] S500: If the existing work ticket template and work ticket issuance process are to be used to issue work tickets and perform power work, then S300 and S400 are to be executed in sequence. If a work ticket template that does not exist in the database is to be used to issue work tickets and perform power work, then S100, S200, S300, and S400 are to be executed in sequence. If the work ticket template is to be modified, then S600 is to be executed. If the work ticket issuance process of a work ticket template is to be modified, then S700 is to be executed. If no further work ticket management is required, then the process ends.

[0128] S600 includes the following steps:

[0129] S610: Execute S110 and S120 in sequence;

[0130] S620: The job ticket preparation submodule receives a job ticket template modification request;

[0131] S630: After the template editor completes setting the initiation method, work content, and safety regulations of the selected work ticket template, the work ticket editing submodule updates the work ticket template to the work ticket template library;

[0132] S700 includes the following steps:

[0133] S710: Execute S210 and S220 in sequence;

[0134] S720: The process configuration module receives a process configuration request;

[0135] S730: After the system administrator completes the modification of the selected workflow information, the workflow configuration module stores the workflow information in the workflow library.

[0136] Preferably, in this embodiment, the three types of personnel, namely, the approval personnel, the operation management personnel, and the system management personnel, have the authority to review the approval log library and the operation log library, and can analyze the records of the issued operation tickets and the completed power operations, so as to know from the aspects of approval and power operation execution which steps in the whole process are less efficient, which facilitates subsequent management and adjustment.

[0137] The above are only some of the embodiments listed in this application and are not intended to limit this application.

Claims

1. A mountain rail transit power operation ticket management method, characterized in that: Adopt the mountain rail transit power operation ticket management system, the system includes: The service subsystem includes a process configuration module, a job ticket management module, and a database; the job ticket management module includes a job ticket compilation submodule and a job ticket issuance submodule; the database includes a job ticket template library, a job ticket instance library, a workflow library, and a personnel library. The job ticket template library is used to store job ticket templates. The job ticket template includes an automatically generated template ID, as well as fixed fields and to-be-filled fields defined through configuration. The fixed fields include the initiation method, job content, and safety regulations, all of which have pre-defined preset values. The to-be-filled fields include the job name, job location, job time, and job executor, all of which have empty preset values. The workflow library is used to store workflow information that corresponds one-to-one to the job ticket template. The workflow information includes template ID, creation parameters, and approval parameters. The personnel library is used to store personnel information. The personnel information includes personnel ID, personnel identification data, and personnel type. Personnel types include job executors, approvers, job managers, system managers, and template compilers. The initiation methods include initiation by job executors and initiation by job managers. The user interaction subsystem includes multiple server-side interaction modules, job site interaction modules, job execution personnel terminals, and approval personnel terminals. The server-side interaction module is used by job managers, system managers, and template developers, and includes a server-side personnel terminal and a personnel identifier. The job site interaction module is used by job execution personnel, and includes a job ticket identifier, a personnel identifier, a job toolbox, and a second clock submodule. The method comprises the steps of: S100: The job ticket preparation submodule prepares several job ticket templates and stores them in the job ticket template library. Each job ticket template includes a template ID automatically generated by the job ticket preparation submodule; S200: Configure the corresponding job ticket issuance process for each job ticket template; S300: The process of issuing a work ticket includes the following steps: S3000: After receiving the job ticket issuance request, the job ticket issuance submodule creates a job ticket instance and approves it. S3000 includes: S310: The job ticket issuance submodule receives a job ticket issuance request. When a job executor initiates a job ticket request, the job executor terminal of the person initiating the job ticket request is connected to the job ticket issuance submodule. When a job manager initiates a job ticket request, after the person identifier of the server-side interaction module identifies the job manager, the server-side personnel terminal operated by the job manager is connected to the job ticket issuance submodule. S320: If the job ticket request received by the job ticket issuing submodule in S310 is from the job executor, the job ticket issuing submodule obtains from the job ticket template library all job ticket templates whose initiation methods are values of the job executor. If the job ticket request received by the job ticket issuing submodule in S310 is from the job manager, the job ticket issuing submodule obtains from the job ticket template library all job ticket templates whose initiation methods are values of the job manager. S330: After the person who initiated the job ticket request selects a job ticket template, the job ticket issuing submodule obtains the person ID of the person and obtains the workflow information corresponding to the selected job ticket template from the workflow library; S340: The job ticket issuance submodule determines whether the value of the creation personnel ID restriction in the creation parameter of the workflow information in S330 is restricted. If not, the selected job ticket template is used to create the instance and S350 is executed. If so, it is determined whether the personnel ID obtained in S330 is in the creation personnel ID list. If so, the selected job ticket template is used to create the instance and S350 is executed. If not, a message to reselect the job ticket template is returned to the server personnel terminal or the job execution personnel terminal operated by the person who initiated the job ticket request, and then the process returns to S330 for execution. S350: The job ticket issuance submodule creates a job ticket instance in the same format as the job ticket template used to create the instance, and sends the job ticket instance to the server terminal or the job executor terminal. The person who initiated the job ticket request fills in all the required fields and then sends the job ticket instance back to the job ticket issuance submodule. The job ticket issuance submodule obtains the approval parameters of the workflow information corresponding to the job ticket template used to create the instance. S360: Determine whether the job ticket instance is approved; S370: If the job ticket instance in S360 is approved, then: If the person who initiates the job ticket request is the job executor, the job ticket issuance submodule issues an electronic job ticket to the job executor's terminal. If the person who initiates the job ticket request is the job management person, the job ticket issuance submodule issues an electronic job ticket to the job executor's terminal of the job executor in the job ticket instance. At the same time, the work ticket issuing submodule obtains the work location from the electronic work ticket, and then sends the electronic work ticket as identification information to the work ticket identifier of the work site interaction module installed at the work location; Then, S300 ends and S400 is executed; If the job ticket instance in S360 is not approved, then S300 ends and S500 is directly executed; S400: The operation site interaction module verifies the operation executor. If the verification is passed, the operation executor is allowed to perform the power operation, and then S500 is executed; S500: If you want to continue using the existing job ticket template and job ticket issuance process to issue job tickets and perform power operations, continue to execute S300 and S400 in sequence. If you want to use a job ticket template that does not exist in the database to issue job tickets and perform power operations, then execute S100, S200, S300, and S400 in sequence. If you do not need to continue job ticket management, end.

2. The mountain rail transit power operation ticket management method according to claim 1 is characterized in that: S100 includes: S110: The personnel identifier of the server-side interaction module identifies the template compiler; S120: The server terminal operated by the template compiler is connected to the job ticket compilation submodule; S130: After receiving the job ticket preparation request, the job ticket preparation submodule creates a job ticket template and automatically generates a template ID; S140: After the template compiler completes the settings of the initiation method, work content, and safety regulations of the created job ticket template, the job ticket compilation submodule stores the job ticket template in the job ticket template library; S150: If another job ticket template needs to be compiled, the process returns to S130 for execution. If another job ticket template does not need to be compiled, the process ends S100.

3. The mountain rail transit power operation ticket management method according to claim 1 is characterized in that: S200 includes: S210: The personnel identifier of the server-side interaction module identifies the system administrator; S220: The server terminal operated by the system administrator is connected to the process configuration module; S230: After receiving the process configuration request, the process configuration module obtains the number n of job ticket templates from the database; S240: The process configuration module sets i=1; S250: Create workflow information in the workflow library. The template ID of the workflow information is the same as the template ID of the corresponding job ticket template. The creation parameters include the type of creator and the creator ID restriction. The values of the creator ID restriction include unlimited and restricted. If the value of the creator ID restriction is restricted, the creation parameters also include a creator ID list. The approval parameters include the number of approval links m and the same number of single link sub-parameters as the number of approval links m. The single link sub-parameters include the link sequence number, the approver ID list, and the approval time limit. S260: The process configuration module automatically obtains the initiation method of the job ticket template and configures the creation personnel type to be the same as the personnel type described in the initiation method; S270: After the system administrator completes setting the ID restriction for the creator and the approval parameters for the workflow information, the workflow configuration module stores the workflow information in the workflow library; S280: Determine whether i=n. If so, end S200. If not, i=i+1, and then return to S250 for execution.

4. The mountain rail transit power operation ticket management method according to claim 1 is characterized in that: S400 includes the following steps: S410: The job ticket identifier of the job site interaction module receives a short-range communication request from the job execution personnel terminal and reads the job execution personnel's electronic job ticket; S420: The work ticket identifier determines whether the work location in the electronic work ticket read in S410 matches the location of the work site interaction module. If not, the work site interaction module sends a message to the work executor terminal indicating that the work location is incorrect, and S400 ends. If so, S430 is executed. S430: The second clock submodule determines whether the time of receiving the NFC request in S410 is within the operation time of the read electronic operation ticket. If not, the operation site interaction module sends a message to the operation executor terminal indicating that the operation time is incorrect, and S400 ends. If so, S440 is executed. S440: The personnel identifier of the work site interaction module obtains personnel identification information. The work site interaction module then communicates with the server subsystem to obtain the personnel information of the work executor in the electronic work ticket read in S410 from the personnel database. The personnel identification information is compared with the personnel identification data to determine whether they match. If so, S450 is executed. If not, the work site interaction module sends a message to the work executor terminal to inform the operator of an error, and S400 ends. S450: The operation site interaction module opens the operation toolbox and waits for the operation execution personnel to perform the power operation; S460: After the operator completes the electrical work and returns the tools taken from the work tool box and closes the work tool box, S400 ends and S500 is executed.

5. The mountain rail transit power operation ticket management method according to claim 1 is characterized in that: S360 includes: S361: The job ticket issuing submodule sets j=1; S362: The work ticket issuing submodule sends the work ticket instance to the approver terminals of all approvers corresponding to the approver IDs in the approver ID list in the jth single link sub-parameter; S363: After the work ticket issuing submodule receives an approval request from one of the approvers who have the work ticket instance to be approved, the work ticket issuing submodule deletes the work ticket instance from the approver terminals of the other approvers; S364: After the approver who issued the approval request returns the approval operation to the work ticket issuing submodule, the work ticket issuing submodule determines: If the approval operation is "Agree," S365 is directly executed. If the approval operation is "Modify," the job ticket issuance submodule updates the job ticket instance based on the changes made by the approver to the job ticket instance, and then S365 is executed. If the approval operation is "Reject," the job ticket instance described in S350 is rejected, and the job ticket issuance submodule returns a message of rejection to the server terminal operated by the person who initiated the job ticket request or the job execution terminal, and ends S360. S365: Determine whether j = m. If so, execute S366. If not, determine j = j + 1, and then return to S362 for execution. S366: The job ticket instance described in S350 is approved.

6. The mountain rail transit power operation ticket management method according to claim 1 is characterized in that: The S500 also includes: If you want to modify the job ticket template, execute S600: the job ticket preparation submodule modifies the existing job ticket template; If the job ticket issuing process of a job ticket template is to be modified, execute S700: modify the existing workflow information through the process configuration module.

7. The mountain rail transit power operation ticket management method according to claim 6 is characterized in that: S600 includes the following steps: S610: Execute S110 and S120 in sequence; S620: The job ticket preparation submodule receives a job ticket template modification request; S630: After the template compiler completes the settings of the initiation method, operation content, and safety regulations of the selected job ticket template, the job ticket compilation submodule updates the job ticket template to the job ticket template library.

8. The mountain rail transit power operation ticket management method according to claim 6 is characterized in that: S700 includes the following steps: S710: Execute S210 and S220 in sequence; S720: The process configuration module receives a process configuration request; S730: After the system administrator completes the modification of the selected workflow information, the workflow configuration module stores the workflow information in the workflow library.

Images