Mountain rail transit electric power work ticket management system and method

Abstract

The invention discloses a mountain rail transit electric power work ticket management system and method, the system comprises a server-side subsystem and a user interaction subsystem, and the server-side subsystem comprises a process configuration module, a work ticket management module and a database. The work ticket management module comprises a work ticket compiling sub-module and a work ticket issuing sub-module. The database comprises an operation ticket template library, an operation ticket instance library, a workflow library and a personnel library. The user interaction subsystem comprises a plurality of server interaction modules, a plurality of operation site interaction modules, a plurality of operation executor terminals and a plurality of approver terminals. The method comprises the steps of compiling a job ticket template, configuring a job ticket issuing process, issuing job tickets, verifying job execution personnel by the job site interaction module and the like. According to the method, the electronic work ticket and an online examination and approval mode are adopted, the examination and approval and execution efficiency of the mountain rail transit electric power work can be improved, and the examination and approval process can be flexibly configured and supervised according to different work conditions.

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 is an important mode of transportation connecting mountainous areas and the outside world, and is of great significance to promoting the economic development of mountainous areas. As the key support of mountain rail transit systems, the stability and reliability of power operations directly affect the transportation capacity and service quality of rail transit.

[0003] The power operation ticket is a standardized management tool necessary for power operations. However, the traditional power operation ticket management method mostly adopts the method of manual filling and paper approval, which has many shortcomings. First, manual filling is prone to errors and omissions, resulting in inaccurate information on the operation ticket, affecting the safety of the operation. Secondly, the paper approval process is cumbersome and the approval efficiency is low, which is difficult to meet the efficiency requirements of power operations. In addition, the traditional management method also has problems such as difficult data traceability and difficult statistical analysis. 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 operating conditions.

[0005] In order to achieve the purpose of the present invention, the following technologies are proposed: A mountain rail transit power operation ticket management system, comprising: The service terminal subsystem includes a process configuration module, a job ticket management module, and a database; the job ticket management module includes a job ticket preparation 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 initiation methods, job contents, and safety regulations whose preset values ​​are all predefined. The to-be-filled fields include job names, job locations, job times, and job execution personnel whose preset values ​​are all empty. The workflow library is used to store workflow information corresponding to the job ticket templates one by one. 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 types. The personnel types include job execution personnel, approval personnel, job management personnel, system management personnel, and template preparation personnel. The initiation methods include initiation by job execution personnel and initiation by job management personnel. 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 submodule.

[0006] A method for managing electric power operation tickets for mountain rail transit using a mountain rail transit electric power operation ticket management system comprises the following steps: S100: The job ticket preparation submodule prepares a number of job ticket templates and stores them in a job ticket template library, each of which includes a template ID automatically generated by the job ticket preparation submodule; S200: configuring a corresponding job ticket issuing process for each job ticket template; S300: Performing the process of issuing a work ticket, including the following steps: S3000: After receiving the job ticket issuance request, the job ticket issuance submodule creates a job ticket instance and performs approval; 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 a 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 a 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 fails to pass the approval, S300 ends and S500 is directly executed; S400: the operation site interaction module verifies the operation executor, and after 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 issue job tickets and perform power operations using a job ticket template that does not exist in the database, then execute S100, S200, S300, and S400 in sequence. If you do not need to continue job ticket management, end the process.

[0007] Furthermore, 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 editor completes the setting of the initiation method, job content, and safety regulations of the created job ticket template, the job ticket editing submodule stores the job ticket template in the job ticket template library; S150: If another job ticket template needs to be compiled, return to S130 for execution; if another job ticket template does not need to be compiled, end S100.

[0008] Furthermore, 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 list of approving personnel IDs, 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 of the creation personnel ID restriction and approval parameters of the workflow information, the process 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.

[0009] Furthermore, S3000 includes: S310: The job ticket issuing submodule receives the job ticket issuing request: when the job executor needs to initiate a job ticket request, the job executor terminal of the person initiating the job ticket request is connected to the job ticket issuing submodule; when the job manager needs to initiate 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 issuing 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 the job ticket templates of all the initiation methods of the job executor from the job ticket template library; 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 the job ticket templates of all the initiation methods of the job manager from the job ticket template library; S330: After the person who initiates 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 issuing submodule determines whether the value of the creation personnel ID restriction in the creation parameters 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 returns to S330 for execution; 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 executor 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.

[0010] Further, 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 executor terminal and reads the electronic job ticket of the job executor; 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 execution personnel terminal indicating that the work location is wrong, and S400 ends. If yes, S430 is executed; S430: The second clock submodule determines whether the time of receiving the short-distance communication 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 execution personnel terminal indicating that the operation time is wrong, and ends S400. If yes, execute S440; S440: The personnel identifier of the operation site interaction module obtains the personnel identification information, and then the operation site interaction module communicates with the server terminal system, obtains the personnel information of the operation executor in the electronic operation 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 operation site interaction module sends a message to the operation executor terminal to prompt the operator of an error, and S400 ends; S450: The operation site interaction module opens the operation tool box and waits for the operation executor 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.

[0011] Furthermore, S360 includes: S361: The job ticket issuing submodule sets j=1; S362: the work ticket issuing submodule sends the work ticket instance to the approval personnel terminals of all the approval personnel corresponding to the approval personnel ID in the approval personnel ID list in the jth single link sub-parameter; S363: After the work ticket issuing submodule receives the 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 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 approval, S365 is directly executed. If the approval operation is modification, the job ticket issuance submodule updates the job ticket instance according to the modification content of the job ticket instance by the approver, and then S365 is executed. If the approval operation is rejection, the job ticket instance described in S350 is not approved, and the job ticket issuance submodule returns a message of approval failure to the server terminal operated by the person who initiated the job ticket request or the job execution personnel terminal, and ends S360. S365: Determine whether j=m. If so, execute S366. If not, then j=j+1, and then return to S362 for execution; S366: The job ticket instance described in S350 is approved.

[0012] Furthermore, S500 also includes: If the job ticket template is to be modified, S600 is executed: 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.

[0013] Further, 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 setting 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.

[0014] Further, 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 into the workflow library.

[0015] The beneficial effects of this technical solution are: 1. First of all, electronic operation tickets are used to replace the original method of using paper operation tickets. In addition, the operation ticket issuance process is configured based on the operation ticket template, and online approval is performed to improve the approval and execution efficiency of mountain rail transit power operations.

[0016] 2. Based on different job ticket templates, the job 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 job executor can initiate the job ticket request and set fewer approval links. If the power operation is relatively complex and the danger is high, the job ticket request can be initiated by the operation manager 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 managers for approval through personnel ID.

[0017] 3. Through permission 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 detection of the personnel identifier before they can continue their respective business. When working, 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

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

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

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

[0021] Figure 4 A specific flow chart of S200 of an embodiment of the present application is shown.

[0022] Figure 5 A specific flow chart of S3000 of an embodiment of the present application is shown.

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

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

[0025] The present application is further described below in conjunction with the accompanying drawings and embodiments.

[0026] like Figure 1 A mountain rail transit power operation ticket management system shown includes a service terminal system and a user interaction subsystem.

[0027] The service terminal subsystem includes a process configuration module, a job ticket management module, and a database; the job ticket management module includes a job ticket preparation 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 initiation methods, job contents, and safety regulations whose preset values ​​are all predefined. The to-be-filled fields include job names, job locations, job times, and job execution personnel whose preset values ​​are all empty. The workflow library is used to store workflow information that corresponds one to one with 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 types. Personnel types include job execution personnel, approval personnel, job management personnel, system management personnel, and template compilation personnel. The initiation methods include initiation by job execution personnel and initiation by job management personnel.

[0028] 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.

[0029] like Figure 2~Figure 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: S100: Preparation of job ticket template, including the following steps: 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 editor completes the setting of the initiation method, job content, and safety regulations of the created job ticket template, the job ticket editing submodule stores the job ticket template in the job ticket template library; S150: if another job ticket template is to be compiled, then return to S130 for execution; if another job ticket template is not to be compiled, then end S100; S200: Configuring a corresponding job ticket issuing process for each job ticket template includes the following steps: 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 list of approving personnel IDs, 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 of the creation personnel ID restriction and approval parameters of the workflow information, the process configuration module stores the workflow information in the workflow library; S280: Determine whether i=n, ​​if yes, then end S200, if no, then i=i+1, then return to S250 for execution; S300: Performing the process of issuing a work ticket, including the following steps: S310: The job ticket issuing submodule receives the job ticket issuing request: when the job executor needs to initiate a job ticket request, the job executor terminal of the person initiating the job ticket request is connected to the job ticket issuing submodule; when the job manager needs to initiate 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 issuing 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 the job ticket templates of all the initiation methods of the job executor from the job ticket template library; 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 the job ticket templates of all the initiation methods of the job manager from the job ticket template library; S330: After the person who initiates 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 issuing submodule determines whether the value of the creation personnel ID restriction in the creation parameters 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 returns to S330 for execution; S350: The job ticket issuing 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 terminal or the job execution 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 issuing submodule. The job ticket issuing submodule obtains the approval parameters of the workflow information corresponding to the job ticket template used to create the instance; S360: Approving the work ticket instance described in S350 to determine whether it is approved, including the following steps: S361: The job ticket issuing submodule sets j=1; S362: the work ticket issuing submodule sends the work ticket instance to the approval personnel terminals of all the approval personnel corresponding to the approval personnel ID in the approval personnel ID list in the jth single link sub-parameter; S363: After the work ticket issuing submodule receives the 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 other approvers, and the first clock submodule records the execution time of this S363; 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 approval, S365 is directly executed. If the approval operation is modification, the job ticket issuance submodule updates the job ticket instance according to the modification content of the job ticket instance by the approver, and then S365 is executed. If the approval operation is rejection, the job ticket instance described in S350 is not approved, and the job ticket issuance submodule returns a message of approval failure to the server terminal operated by the person who initiated the job ticket request or the job execution personnel terminal, and ends S360. At the same time, the first clock submodule records the execution time of S364; S365: Determine whether j=m. If so, execute S366. If not, then j=j+1, and then return to S362 for execution. At the same time, the job ticket issuing submodule compares the total execution time of S363 and S364 with the approval time limit in the j-th single link subparameter. If the total time is greater than the approval time limit, the log information of the timeout when executing the approval of the j-th link of the job ticket instance in S350 is recorded in the approval log library; S366: The job ticket instance described in S350 is approved; S370: If the job ticket instance in S360 is approved, then: If the person who initiates the job ticket request is a 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 a 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 fails to pass the approval, S300 ends and S500 is directly executed; S400: Executing electrical work, including the following steps: 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 electronic work ticket of the work executor. In this embodiment, NFC (Near Field Communication) is used between the work ticket identifier and the work executor terminal. 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 execution personnel terminal indicating that the job location is wrong, and sends the message to the service terminal subsystem, stores it in the job log library, and ends S400. If yes, execute S430; S430: The second clock submodule determines whether the time of receiving the short-distance communication 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 execution personnel terminal indicating that the operation time is wrong, and sends the message to the service terminal subsystem, stores it in the operation log library, and ends S400. If yes, execute S440; S440: The personnel identifier of the operation site interaction module obtains personnel identification information. In this embodiment, the personnel identifier also includes a camera module, and the face is obtained as the personnel identification information through the camera module. In other embodiments, the personnel identifier may also include a fingerprint reading module to obtain the fingerprint as the personnel identification information through the fingerprint reading module. Then the operation site interaction module communicates with the service end subsystem, obtains the personnel information of the operation executor in the electronic operation ticket read in S410 from the personnel library, compares the personnel identification information and the personnel identification data, and determines whether they match. If so, S450 is executed. If not, the operation site interaction module sends a message to the operation executor terminal to prompt the operator of the error, and sends the message to the service end subsystem, stores it in the operation log library, and ends S400; S450: The operation site interaction module opens the operation tool box and waits for the operation executor to perform the power operation. Meanwhile, the second clock submodule records the operation start time. S460: After the operation executor completes the power operation and returns the tools taken from the operation tool box and closes the operation tool box, the second clock submodule records the operation end time, and the operation site interaction module sends the operation start time and the operation end time to the service subsystem, S400 ends, and S500 is executed; S500: If the existing work ticket template and work ticket issuance process are to be continued to be used to issue work tickets and perform power work, S300 and S400 are continued to be executed in sequence. If the work ticket template that does not exist in the database is to be used to issue work tickets and perform power work, S100, S200, S300, and S400 are executed in sequence. If the work ticket template is to be modified, S600 is executed. If the work ticket issuance process of a work ticket template is to be modified, S700 is executed. If it is not necessary to continue the work ticket management, the process ends. 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 editor completes setting the values ​​of the initiation method, operation content, and safety regulations of the selected job ticket template, the job ticket editing submodule updates the job ticket template to the job ticket template library; 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 into the workflow library.

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

[0031] 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 system, characterized in that: include: The service subsystem includes the process configuration module, the job ticket management module, and the database; The job ticket management module includes a job ticket preparation 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 fields to be filled in that are defined through configuration. The fixed fields include initiation methods, job contents, and safety regulations whose preset values ​​are all predefined. The fields to be filled in include job names, job locations, job times, and job execution personnel whose preset values ​​are all empty. The workflow library is used to store workflow information that corresponds to the job ticket templates one by one. 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 types. The personnel types include job execution personnel, approval personnel, job management personnel, system management personnel, and template preparation personnel. The initiation methods include initiation by job execution personnel and initiation by job management personnel. 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 submodule.

2. A method for managing electric power operation tickets for mountain rail transit, characterized in that: The mountain rail transit power operation ticket management system according to claim 1 comprises the following steps: S100: The job ticket preparation submodule prepares a number of job ticket templates and stores them in a job ticket template library, each of which includes a template ID automatically generated by the job ticket preparation submodule; S200: configuring a corresponding job ticket issuing process for each job ticket template; S300: Performing the process of issuing a work ticket, including the following steps: S3000: After receiving the job ticket issuance request, the job ticket issuance submodule creates a job ticket instance and performs approval; 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 a 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 a 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 fails to pass the approval, S300 ends and S500 is directly executed; S400: the operation site interaction module verifies the operation executor, and after 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 issue job tickets and perform power operations using a job ticket template that does not exist in the database, then execute S100, S200, S300, and S400 in sequence. If you do not need to continue job ticket management, end the process.

3. The method for managing electric power operation tickets for mountain rail transit according to claim 2, 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 editor completes the setting of the initiation method, job content, and safety regulations of the created job ticket template, the job ticket editing submodule stores the job ticket template in the job ticket template library; S150: If another job ticket template needs to be compiled, return to S130 for execution; if another job ticket template does not need to be compiled, end S100.

4. The mountain rail transit power operation ticket management method according to claim 2 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 list of approving personnel IDs, 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 of the creation personnel ID restriction and approval parameters of the workflow information, the process 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.

5. The method for managing electric power operation tickets for mountain rail transit according to claim 4 is characterized in that: S3000 includes: S310: The job ticket issuing submodule receives the job ticket issuing request: when the job executor needs to initiate a job ticket request, the job executor terminal of the person initiating the job ticket request is connected to the job ticket issuing submodule; when the job manager needs to initiate 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 issuing 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 the job ticket templates of all the initiation methods of the job executor from the job ticket template library; 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 the job ticket templates of all the initiation methods of the job manager from the job ticket template library; S330: After the person who initiates 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 issuing submodule determines whether the value of the creation personnel ID restriction in the creation parameters 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 returns to S330 for execution; 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 executor 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.

6. The mountain rail transit power operation ticket management method according to claim 2 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 executor terminal and reads the electronic job ticket of the job executor; 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 execution personnel terminal indicating that the work location is wrong, and S400 ends. If yes, S430 is executed; S430: The second clock submodule determines whether the time of receiving the short-distance communication 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 execution personnel terminal indicating that the operation time is wrong, and ends S400. If yes, execute S440; S440: The personnel identifier of the operation site interaction module obtains the personnel identification information, and then the operation site interaction module communicates with the server terminal system, obtains the personnel information of the operation executor in the electronic operation 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 operation site interaction module sends a message to the operation executor terminal to prompt the operator of an error, and S400 ends; S450: The operation site interaction module opens the operation tool box and waits for the operation executor 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.

7. The method for managing electric power operation tickets for mountain rail transit according to claim 5, 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 approval personnel terminals of all the approval personnel corresponding to the approval personnel ID in the approval personnel ID list in the jth single link sub-parameter; S363: After the work ticket issuing submodule receives the 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 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 approval, S365 is directly executed. If the approval operation is modification, the job ticket issuance submodule updates the job ticket instance according to the modification content of the job ticket instance by the approver, and then S365 is executed. If the approval operation is rejection, the job ticket instance described in S350 is not approved, and the job ticket issuance submodule returns a message of approval failure to the server terminal operated by the person who initiated the job ticket request or the job execution personnel terminal, and ends S360. S365: Determine whether j=m. If so, execute S366. If not, then j=j+1, and then return to S362 for execution; S366: The job ticket instance described in S350 is approved.

8. The method for managing electric power operation tickets for mountain rail transit according to claim 2, characterized in that: The S500 also includes: If the job ticket template is to be modified, S600 is executed: 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.

9. The method for managing electric power operation tickets for mountain rail transit according to claim 8, 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 setting 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.

10. The method for managing electric power operation tickets for mountain rail transit according to claim 8, 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 into the workflow library.

Images