WO2023098375A1 - 操作票处理方法、装置、存储介质及电子装置 - Google Patents

操作票处理方法、装置、存储介质及电子装置 Download PDF

Info

Publication number
WO2023098375A1
WO2023098375A1 PCT/CN2022/129037 CN2022129037W WO2023098375A1 WO 2023098375 A1 WO2023098375 A1 WO 2023098375A1 CN 2022129037 W CN2022129037 W CN 2022129037W WO 2023098375 A1 WO2023098375 A1 WO 2023098375A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
ticket
target operation
operation ticket
server
Prior art date
Application number
PCT/CN2022/129037
Other languages
English (en)
French (fr)
Inventor
余鹏
洪建兵
赖峰
王大鹏
谭宏军
李刚
向金卫
李灶培
Original Assignee
珠海优特电力科技股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 珠海优特电力科技股份有限公司 filed Critical 珠海优特电力科技股份有限公司
Priority to GB2309281.0A priority Critical patent/GB2619167A/en
Priority to AU2022403593A priority patent/AU2022403593A1/en
Publication of WO2023098375A1 publication Critical patent/WO2023098375A1/zh

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40Business processes related to the transportation industry

Definitions

  • Embodiments of the present disclosure relate to the field of vehicle depot maintenance, and in particular, relate to a method, device, storage medium, and electronic device for processing an operation ticket.
  • the conventional processing method in the related technology is: the maintenance personnel print the maintenance work order, and then contact the maintenance dispatcher to perform the power supply stop operation in the maintenance area according to the maintenance work order stop power supply request, and the maintenance dispatcher receives the After the maintenance application, the operation ticket is simulated in the error prevention system, and then the operation ticket is transmitted to the computer key for operation. After the operation is completed, the maintenance dispatcher needs to contact the on-site operator to receive the operation ticket, and the maintenance personnel will go to the maintenance area to work.
  • the maintenance work order in this process is not uniformly managed electronically, and the maintenance The operation of the personnel to apply to the maintenance dispatcher to stop the power supply in a certain area is not associated with the pre-printed maintenance work order. This operation may cause that if the maintenance is performed in the A-share channel, the maintenance dispatcher stops the B-share channel.
  • the operation ticket is simulated in the anti-mistake system, and the operation ticket is transmitted to the computer key for operation.
  • the maintenance dispatcher needs to contact the on-site operator to receive the operation ticket, and the maintenance personnel go to the maintenance area In this process, all power outages and power transmission processes need to be simulated for maintenance and dispatch.
  • the intelligentization of invoicing is not complete, and the functions of intelligent automatic ticketing, subpoena, and receipt of tickets have not been realized, and the manual receipt of tickets by maintenance personnel may cause other teams in other areas to be repaired to take over. Wrong tickets will result in incorrect information reception and additionally prolong the time to be repaired.
  • Embodiments of the present disclosure provide an operation ticket processing method, device, storage medium, and electronic device, so as to at least solve the problems of high maintenance scheduling error rate and long maintenance time in the related art.
  • a method for processing an operation ticket including: acquiring operation ticket information from a server, wherein the operation ticket information is information determined by the server based on a selection instruction sent by a target application APP ; Based on the operation ticket information, determine the target operation mode from a variety of pre-configured operation modes; when it is determined that the target operation condition is currently met, generate a target operation ticket according to the target operation mode; Send to the target key corresponding to the target operation ticket, wherein the target key has the ability to automatically receive the ticket and execute the operation ticket.
  • an operation ticket processing device including: an acquisition module configured to acquire operation ticket information from a server, wherein the operation ticket information is sent by the server based on the target application APP Select the information determined by the instruction; the determination module is configured to determine the target operation mode from a variety of pre-configured operation modes based on the operation ticket information; the generation module is configured to determine that the current target operation condition is met, according to The target operation mode generates a target operation ticket; the sending module is configured to send the target operation ticket to a target key corresponding to the target operation ticket, wherein the target key has the ability to automatically receive the ticket and execute the operation ticket .
  • a computer-readable storage medium wherein a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to perform any one of the above-mentioned methods when running Steps in the examples.
  • an electronic device including a memory and a processor, wherein a computer program is stored in the memory, and the processor is configured to run the computer program to perform any of the above Steps in the method examples.
  • the operation ticket information can be determined based on the selection instruction sent by the APP, and then the operation ticket can be automatically generated based on the operation ticket information.
  • the operation ticket can also be sent to the target key, and then the target key can Automatic receipt of tickets, the entire operation process realizes the electronic management of operation work orders, and can realize the functions of automatic ticket formation, automatic subpoena and automatic receipt of tickets according to actual needs, avoiding miscommunication or misconnection of operation tickets during transmission, ensuring The successful execution of the operation shortens the operation cycle to a certain extent, and effectively solves the problems of high maintenance scheduling error rate and long maintenance time in related technologies.
  • FIG. 1 is a block diagram of a hardware structure of a mobile terminal of an operation ticket processing method according to an embodiment of the present disclosure
  • FIG. 2 is a flow chart of a method for processing an operation ticket according to an embodiment of the present disclosure
  • FIG. 3 is a system overall architecture diagram according to an embodiment of the present disclosure.
  • Fig. 4 is a flow chart of automatically forming a ticket and receiving a subpoena for a depot maintenance operation according to an embodiment of the present disclosure
  • Fig. 5 is a process of generating an operation ticket according to an embodiment of the present disclosure
  • FIG. 6 is the second operation ticket generation process according to an embodiment of the present disclosure.
  • FIG. 7 is the third operation ticket generation process according to an embodiment of the present disclosure.
  • Fig. 8 is a structural block diagram of an operation ticket processing device according to an embodiment of the present disclosure.
  • the power transmission operation includes the opening and closing operation of the isolating switch and the ground wire (temporary grounding or visual grounding device) connection and removal operation, but the maintenance process and shutdown Power transmission is not related, each process exists independently, and the implementation of the process is relatively backward. How to link these processes and how to manage the closed-loop process is an urgent problem to be solved.
  • this disclosure example proposes a set of maintenance work orders, operation tickets, keys, anti-misjudgment, wireless summons,
  • the depot maintenance operation automatic ticket subpoena ticket receiving system that integrates automatic receipt of tickets can realize the closed-loop management of the whole process of the depot, and the generated operation tickets are automatically summoned and keys are automatically received, which greatly improves the efficiency of production operations.
  • FIG. 1 is a block diagram of a hardware structure of a mobile terminal according to an operation ticket processing method according to an embodiment of the present disclosure.
  • the mobile terminal may include one or more (only one is shown in Figure 1) processors 102 (processors 102 may include but not limited to processing devices such as microprocessor MCU or programmable logic device FPGA, etc.) and a memory 104 configured to store data, wherein the mobile terminal may further include a transmission device 106 and an input/output device 108 configured to communicate.
  • processors 102 may include but not limited to processing devices such as microprocessor MCU or programmable logic device FPGA, etc.
  • a transmission device 106 and an input/output device 108 configured to communicate.
  • the mobile terminal may also include more or fewer components than those shown in FIG. 1 , or have a different configuration from that shown in FIG. 1 .
  • the memory 104 can be set to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the operation ticket processing method in the embodiment of the present disclosure, and the processor 102 runs the computer program stored in the memory 104, thereby Executing various functional applications and data processing is to realize the above-mentioned method.
  • the memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include a memory that is remotely located relative to the processor 102, and these remote memories may be connected to the mobile terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • the transmission device 106 is configured to receive or transmit data via a network.
  • the specific example of the above-mentioned network may include a wireless network provided by the communication provider of the mobile terminal.
  • the transmission device 106 includes a network interface controller (NIC for short), which can be connected to other network devices through a base station so as to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, referred to as RF) module, which is configured to communicate with the Internet in a wireless manner.
  • RF radio frequency
  • FIG. 2 is a flow chart of the method for processing an operation ticket according to an embodiment of the disclosure. As shown in FIG. 2 , the process includes the following steps:
  • Step S202 acquiring operation ticket information from the server, wherein the operation ticket information is information determined by the server based on the selection instruction sent by the target application APP;
  • Step S204 determining a target operation mode from multiple pre-configured operation modes based on the operation ticket information
  • Step S206 when it is determined that the target operation condition is satisfied, generate a target operation ticket according to the target operation mode;
  • Step S208 sending the target operation ticket to a target key corresponding to the target operation ticket, wherein the target key has the capability of automatically receiving the ticket and executing the operation ticket.
  • the operation ticket module may be located in, for example, a mobile terminal, a computer terminal, etc. Processing equipment or processing units, etc.
  • the target APP can receive the maintenance work order from the server (for example, a cloud server), and then display the contents of the maintenance work order in the target APP (the content of the work order can include: track, serial number , team and other information), in addition, other information can also be displayed in the target APP, such as operation selection information such as stop/supply, hang/remove the ground wire, etc., and then the operator (for example, the person in charge) can log in After the target APP, select relevant information in the target APP to generate operation ticket information.
  • the server for example, a cloud server
  • the content of the work order can include: track, serial number , team and other information
  • other information can also be displayed in the target APP, such as operation selection information such as stop/supply, hang/remove the ground wire, etc.
  • the operator for example, the person in charge
  • the above-mentioned target operation mode is actually selected from a plurality of predetermined modes, that is, the corresponding operation mode can be selected according to the operation ticket information.
  • the predetermined multiple modes include at least the following modes: open the isolating switch, close the isolating switch, open the isolating switch and then hang a group of ground wires, remove a group of ground wires and then close the isolating switch, open the isolating switch and then hang two groups of ground wires, disassemble Two sets of ground wires are then connected to the disconnect switch, where the operation in each mode can be pre-specified.
  • the operation ticket information can be determined based on the selection instruction sent by the APP, and then the operation ticket can be automatically generated based on the operation ticket information.
  • the operation ticket can also be sent to the target key, and then the target key Automatic receipt of tickets, the entire operation process realizes the electronic management of operation work orders, and can realize the functions of automatic ticket formation, automatic subpoena and automatic receipt of tickets according to actual needs, avoiding misinformation or misconnection of operation tickets during transmission, ensuring The successful implementation of the operation is ensured, and the operation cycle is shortened to a certain extent, and the problems of high maintenance scheduling error rate and long maintenance time in the related technologies are effectively solved.
  • the above method when it is determined that the target operation condition is currently met, before generating the target operation ticket according to the target operation mode, the above method further includes: determining whether the current target operation condition is satisfied by at least performing the following judgment operations: Target operation conditions; unique operation right judgment, misjudgment prevention, judgment on whether the channel is normal, judgment on whether the target key has an operation ticket; among them, after determining that the only operation right is satisfied, there is no false trigger, the channel is in a normal state, and all If there is no other operation ticket for the target key, it is determined that the target operation condition is currently met.
  • the entire process of generating an operation ticket requires judgment on the sole operation right (whether the mobile terminal or computer terminal with decision-making ability has the only operation right), anti-misjudgment (the stop/power transmission channel is correct or the connection/removal of the ground is correct). Line operation is correct, etc.), whether the channel is normal judgment (transfer operation ticket channel), whether the target key has an operation ticket judgment (corresponding to the mobile terminal or computer terminal that receives the operation ticket to process the idle state), after determining that the only operation right is satisfied, When there is no false trigger, the channel is in a normal state, and the target key has no other operation ticket, it is determined that the target operation condition is currently satisfied, and the target operation ticket can be generated according to the above target mode.
  • the above method further includes at least one of the following: when the target operation ticket is generated according to the target operation mode, sending to the server a message set to indicate that the target operation ticket has been successfully generated
  • the first notification message is to instruct the server to notify the target application that the target operation ticket has been successfully generated; if it is determined that the target operation condition is not met, send the message set to indicate that the target application has not been successfully generated to the server.
  • the second notification message of the target operation ticket to instruct the server to notify the target application that the target application failed to generate the target operation ticket and the failure reason, wherein the second notification message carries the instruction message.
  • a first notification message set to indicate that the target operation ticket has been successfully generated may be sent to the server to instruct the server to notify the target APP that it has succeeded
  • the above-mentioned operation ticket is generated, so that the user of the target APP can know in time that the target operation ticket has been successfully generated.
  • the server also needs to be notified, that is, a setting is sent to the above server to indicate that the target operation has not been successfully generated
  • the second notification message of the ticket may also carry the reason of failure to instruct the server to notify the target APP that the target APP failed to generate the target operation ticket and the reason for the failure, for example, when the current target key
  • the reason for the failure can pop up in the above target APP: the target key has already been processed by other operation tickets, and the generation of the operation ticket fails, so that the user of the target APP can know the target operation ticket in time The reason for the build failure.
  • the above method further includes: determining the configuration attribute of the target device on which the target operation is to be performed, wherein the target operation is determined based on the target operation mode;
  • the target device executes a first operation step required by the target operation; and the target operation ticket is generated based on the first operation step.
  • the operation ticket module will pre-store the configuration attributes (that is, related information such as cables) of the target device to be operated (for example, the cable to be repaired, etc.), and then before generating the above-mentioned operation ticket, Operational steps for a device may be determined based on configuration properties of the device.
  • the configuration attributes of the devices are also different, and the corresponding relationship between the configuration attributes of the devices and the operation steps may be pre-configured.
  • the above method further includes: determining the device type of the target device to perform the target operation, wherein the target operation is determined based on the target operation mode; determining the target device according to the device type The target device executes a second operation step required by the target operation; and the target operation ticket is generated based on the second operation step.
  • the operation ticket module pre-stores information about the type of the target device to be operated, and then before generating the operation ticket, the operation steps for the device can be determined based on the type information of the device. Wherein, the corresponding relationship between device types and operation steps may be pre-configured.
  • the above method further includes: determining the operation type of the target device to perform the target operation, wherein the target operation is determined based on the target operation mode;
  • the target device executes a third operation step required by the target operation; and the target operation ticket is generated based on the third operation step.
  • the operation type of the target device to be operated is pre-stored in the operation ticket module, and the operation steps for the device can be determined based on the operation type of the device before the operation ticket is generated.
  • the corresponding relationship between the operation type of the device and the operation steps may be pre-configured.
  • the method further includes: the target key executes the target key included in the target operation ticket Before each operation step, send an inquiry message to the server to inquire whether the operation step to be executed is allowed to be executed; the target key executes the operation step to be executed after receiving the response of allowing execution returned by the server.
  • the operation steps to be executed when the target key receives a response that the execution is not allowed returned by the server, it terminates the execution of the operation steps to be executed and subsequent operation steps.
  • the target key before performing each operation, the target key will judge whether the operation is allowed to be performed.
  • the specific judgment method may include confirming to the server whether the current operation can be performed, or, in the case that the target key has the ability of logical judgment Next, the judgment operation can also be performed by the target key itself (for example, the target key obtains the status of each device and line in the system from the server in advance, and then judges whether to allow the current operation based on the obtained information).
  • the target key obtains the status of each device and line in the system from the server in advance, and then judges whether to allow the current operation based on the obtained information.
  • Fig. 3 is a diagram of the overall system architecture according to an embodiment of the present disclosure.
  • the one-click subpoena solution for the depot maintenance operation is through a video server, a communication machine, a cloud server, a smart phone, an isolating switch, a visual grounding device, a mobile ground wire, and a computer. Keys, various locks, etc. are realized through the unified analysis and unified management of the depot management and control system.
  • FIG. 3 for details.
  • Fig. 4 is a flow chart of automatically forming a ticket and receiving a subpoena for a depot maintenance operation according to an embodiment of the present disclosure. The process includes the following steps:
  • the maintenance module generates a maintenance work order and transmits it to the cloud server (corresponding to 1 in Figure 4);
  • the cloud server sends the maintenance work order to the smart phone APP (corresponding to the above-mentioned target APP) (corresponding to 2 in Figure 4);
  • the person in charge logs on to the smart phone APP to check the maintenance work order content (the work order content already includes information such as stock route, serial number, team and group, etc.), and at the same time selects stop/delivery in the smart phone APP according to the work order stop power transmission requirements Electricity, hanging/removing ground wire operation, click one key to generate operation (corresponding to 3 in Figure 4);
  • the cloud server receives the information that needs to generate an operation ticket and notifies the operation ticket module (corresponding to 4 in Figure 4);
  • the operation ticket module starts one key into a ticket: the operation ticket module completes the information collection (stock track + serial number, etc.), and at the same time, according to the operation mode selected by the person in charge on the smart phone APP (separate isolating switch, closing isolating switch, Separate the isolation switch and then hang a group of ground wires, remove a group of ground wires and then close the isolation switch, separate the isolation switch and then hang two groups of ground wires, remove the two groups of ground wires and then close the isolation switch, etc.) to generate an operation ticket (the entire process of generating an operation ticket Carry out unique operation right judgment, anti-misjudgment, whether the channel is normal judgment, whether the above-mentioned target key has a ticket, etc.), and send the result of generating the operation ticket to the cloud server (corresponding to 5 in Figure 4);
  • the operation ticket is successfully generated, and the cloud server transmits the information that the one-key operation ticket is successfully generated to the smartphone APP, and if the operation ticket fails to be generated, the cloud server transmits the information that the one-key operation ticket generation fails and the reason for the failure to the smartphone APP, For example, the reason for the failure to generate an operation ticket with one key (corresponding to 6 in Figure 4):
  • the state of the operating equipment is different from the current state
  • Wrong mode selection that is, the closing isolating switch is selected and the grounding wire is selected, or the right isolating switch is selected and the grounding wire is removed, etc.;
  • the current stock channel has a plan to send and receive cars, so it cannot issue tickets
  • the operation ticket module sends the successfully generated operation ticket to the network controller (corresponding to 7 in Figure 4);
  • the network controller determines the corresponding key (the above-mentioned target key) to transmit the operation ticket according to the team information of the operation ticket, and simultaneously the key (the above-mentioned target key) automatically receives the ticket, and the ticket is successfully received (8 in corresponding figure 4);
  • the key operates the electric or manual isolating switch, and there is real-time logic judgment during the operation process. If abnormal displacement occurs during the operation process, the operation will be prohibited (corresponding to 9 in Figure 4);
  • the key operates a visual grounding device or a flowing ground wire, and there is a real-time logic judgment during the operation process. If there is an abnormal displacement during the operation process, the operation will be prohibited (corresponding to 10 in Figure 4).
  • the computer key in view of the configuration properties of the equipment to be operated, supports two modes of common ground wire, and supports the functions of mobile ground wire and fixed ground wire mode.
  • the two modes of common ground wire are mainly to realize the The maintenance process realizes two modes of prior electric inspection and ground wire first, and supports mobile ground wires (you can choose a certain group of ground wires), or fixed ground wire mode (directly bound to the nearest ground wire), and guarantees through the process of connecting the ground wire The safety of on-site maintenance personnel is guaranteed.
  • the following describes how to generate an operation ticket based on configuration attributes in conjunction with Figure 5:
  • the operation ticket module before the operation ticket module generates the operation ticket, it needs to obtain the configuration attribute of the equipment to be operated (whether it is a fixed ground or a mobile ground), wherein, in the mobile ground mode, the ground wire can be taken from multiple groups of ground wires Any ground wire that is not used, in the fixed ground wire mode, one ground wire is fixed at each ground point, and the fixed ground wire is automatically associated when the ticket is automatically formed.
  • the ground wire only the fixed ground wire can be taken (corresponding to 1 in Figure 5 );
  • the operation ticket module generates an operation ticket according to the configuration attribute, and passes it to the computer key (corresponding to 2 in Figure 5);
  • the computer key supports two modes of common ground wire, and the computer key performs each operation step in the operation ticket (corresponding to 3 in Figure 5), including:
  • the computer key supports common ground wires, visual grounding devices and automatic ticketing. The following describes how to generate an operation ticket based on the type of equipment in conjunction with FIG. 6:
  • the operation ticket module determines the equipment type (ordinary ground wire, visual grounding device), and generates an operation ticket based on the equipment type (corresponding to 1 in Figure 6);
  • the computer key supports ordinary ground wires and visual grounding devices and automatic ticketing.
  • the computer key executes the operation steps automatically generated according to the type of equipment (corresponding to 2 in Figure 6), mainly including the following two operation modes:
  • Mode 1 If the equipment type is a common ground wire, then according to the two modes described in Figure 5 (1, take the ground wire first and then conduct an electrical test (the electrical test is after the ground wire is taken) 2, take the ground wire after the electrical test (electrical test) Before taking the ground wire)) one of the operations (in Figure 6 is only an example of an operation of "taking the ground wire first and then testing the electricity", in practical applications it may also be “testing the electricity first and then taking the ground Line” operation);
  • the computer key supports the on-site (including manual and electric) and remote operation processes of the isolation switch and the visual grounding device. The following describes how to generate operations based on the equipment operation type Tickets are explained:
  • the operation ticket module obtains configuration attributes (whether it is local operation or remote operation) (corresponding to 1 in Figure 7);
  • the operation ticket module generates an operation ticket and passes it to the computer key (corresponding to 2. in Fig. 7) according to the configuration attribute (be the following mode 1 or mode 2);
  • the computer key supports two operating modes of isolating switch and visual grounding device, and the computer key executes each operation step in the operation ticket (corresponding to 3 in Figure 7):
  • Mode 1 Operate the isolating switch or visual grounding device locally, and open the mechanical lock for manual local operation.
  • Mode 2 Remotely operate the isolating switch or visual grounding device, press the remote button on the key, and perform remote remote operation on the system at the same time.
  • the present disclosure changes the maintenance and operation ticket separation, manual, and inefficient operation mode at the present stage, and improves the work efficiency of the maintenance personnel and ensures the safety of the personnel through one-click ticketing.
  • the embodiment of the disclosure also achieved the following objectives:
  • Realize closed-loop management functions including: maintenance work orders, APP display maintenance work orders, automatic generation of operation tickets by selecting areas that need power outage or power transmission on the APP, automatic receipt of tickets according to the computer keys bound to the team, and feedback of on-site operation status. There will be no situation where the team receives the wrong ticket.
  • the method according to the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation.
  • the technical solution of the present disclosure can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to make a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) execute the methods described in various embodiments of the present disclosure.
  • an operation ticket processing device is also provided, which is configured to implement the above embodiments and preferred implementation modes, and those that have already been described will not be repeated.
  • the term "module” may be a combination of software and/or hardware that realizes a predetermined function.
  • the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.
  • Fig. 8 is a structural block diagram of an operation ticket processing device according to an embodiment of the present disclosure. As shown in Fig. 8, the device includes:
  • the obtaining module 802 is configured to obtain operation ticket information from the server, wherein the operation ticket information is information determined by the server based on the selection instruction sent by the target application APP;
  • a determination module 804 configured to determine a target operation mode from multiple pre-configured operation modes based on the operation ticket information
  • the generation module 806 is configured to generate a target operation ticket according to the target operation mode when it is determined that the target operation condition is currently satisfied;
  • the sending module 808 is configured to send the target operation ticket to a target key corresponding to the target operation ticket, wherein the target key has the capability of automatically receiving tickets and executing the operation ticket.
  • the determining module 804 includes: a judging unit, configured to determine whether the target operation condition is currently met by at least performing the following judging operations: judging the sole operation right, preventing misjudgment, whether the channel is normal Judging, judging whether the target key has an operation ticket; wherein, when it is determined that the only operation right is satisfied, there is no false trigger, the channel is in a normal state, and the target key does not have other operation tickets, it is determined that the current requirement is satisfied. target operating conditions.
  • the above-mentioned device further includes at least one of the following modules: a first notification module, configured to send a target operation ticket to the server when the target operation ticket is generated according to the target operation mode.
  • the first notification message of successfully generating the target operation ticket is used to instruct the server to notify the target application that the target operation ticket has been successfully generated;
  • the second notification module is configured to determine that the target operation condition is currently not met In this case, sending to the server a second notification message set to indicate that the target operation ticket was not successfully generated, so as to instruct the server to notify the target application that the target operation ticket was not successfully generated and the reason for the failure, wherein the The second notification message carries an indication message set to indicate the cause of the failure.
  • the generating module 806 includes: a first determining unit configured to determine configuration attributes of a target device to perform a target operation, wherein the target operation is determined based on the target operation mode
  • the second determining unit is configured to determine the configuration attribute of the target device to perform the target operation, wherein the target operation is determined based on the target operation mode
  • the first generating unit is configured to determine based on the first The operation step generates the target operation ticket.
  • the generating module 806 includes: a third determining unit configured to determine a device type of a target device to perform a target operation, wherein the target operation is determined based on the target operation mode the fourth determination unit is configured to determine the second operation steps required to perform the target operation on the target device according to the device type; the second generation unit is configured to generate the Target action ticket.
  • the generating module 806 includes: a fifth determining unit configured to determine an operation type of a target device to perform a target operation, wherein the target operation is determined based on the target operation mode
  • the sixth determination unit is configured to determine a third operation step required to perform the target operation on the target device according to the operation type; the third generation unit is configured to generate the third operation step based on the third operation step Target action ticket.
  • the above-mentioned target key includes the following module: an inquiry module, configured to send an inquiry message to the server before executing each operation step included in the target operation ticket, to inquire whether to allow the execution The current operation steps to be executed; the receiving module is configured to execute the operation steps to be executed when the target key receives the execution permission response returned by the server; the processing module is configured to be the target key In the case of receiving a response that the execution is not allowed returned by the server, the execution of the operation steps to be executed and subsequent operation steps is terminated.
  • an inquiry module configured to send an inquiry message to the server before executing each operation step included in the target operation ticket, to inquire whether to allow the execution The current operation steps to be executed
  • the receiving module is configured to execute the operation steps to be executed when the target key receives the execution permission response returned by the server
  • the processing module is configured to be the target key In the case of receiving a response that the execution is not allowed returned by the server, the execution of the operation steps to be executed and subsequent operation steps is terminated.
  • the above-mentioned modules can be realized by software or hardware. For the latter, it can be realized by the following methods, but not limited to this: the above-mentioned modules are all located in the same processor; or, the above-mentioned modules can be combined in any combination The forms of are located in different processors.
  • Embodiments of the present disclosure also provide a computer-readable storage medium, in which a computer program is stored, wherein the computer program is set to execute the steps in any one of the above method embodiments when running.
  • the above-mentioned computer-readable storage medium may include but not limited to: U disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM) , mobile hard disk, magnetic disk or optical disk and other media that can store computer programs.
  • ROM read-only memory
  • RAM random access memory
  • mobile hard disk magnetic disk or optical disk and other media that can store computer programs.
  • Embodiments of the present disclosure also provide an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
  • the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.
  • each module or each step of the above-mentioned disclosure can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices In fact, they can be implemented in program code executable by a computing device, and thus, they can be stored in a storage device to be executed by a computing device, and in some cases, can be executed in an order different from that shown here. Or described steps, or they are fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present disclosure is not limited to any specific combination of hardware and software.
  • the eye tracking method based on light field perception has the following beneficial effects: the eye tracking can be performed without relying on the corneal spherical reflection model or the flicker position to calculate the corneal center of the user's eye, and does not need to use external
  • the illumination source is positioned at a specific position relative to the light field camera, which greatly improves the data quality, stability and tracking accuracy of eye tracking.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Economics (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Marketing (AREA)
  • Theoretical Computer Science (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Primary Health Care (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Development Economics (AREA)
  • Devices For Checking Fares Or Tickets At Control Points (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Automatic Disk Changers (AREA)
  • Sheets, Magazines, And Separation Thereof (AREA)
  • Debugging And Monitoring (AREA)
  • Control Or Security For Electrophotography (AREA)

Abstract

一种操作票处理方法、装置、存储介质及电子装置,其中,方法包括:获取来自服务器的操作票信息,其中,操作票信息为服务器基于目标应用APP发送的选择指令所确定的信息;基于操作票信息从预先配置的多种操作模式中确定出目标操作模式;在确定当前满足目标操作条件的情况下,按照目标操作模式生成目标操作票;将目标操作票发送给与目标操作票对应的目标钥匙,其中,目标钥匙具备自动接票并执行操作票的能力。本方案解决了现有技术中存在的检修调度失误率高以及检修时间长的问题。

Description

操作票处理方法、装置、存储介质及电子装置 技术领域
本公开实施例涉及车辆段检修领域,具体而言,涉及一种操作票处理方法、装置、存储介质及电子装置。
背景技术
随着车辆技术和运输能力的突飞猛进,目前车辆段的检修和维护也是备受社会关注,交通安全问题受到日益重视。
针对车辆段检修操作票的处理,相关技术中常规的处理方式是:检修人员打印检修工单,再根据检修工单停送电要求联系检修调度对检修区域进行停送电操作,检修调度接收到检修申请后在防误***进行模拟开操作票,随后将操作票传到电脑钥匙进行操作,操作完成后,检修调度需联系现场操作人员接收操作票,检修人员再到检修区域工作。
其中,在检修人员打印检修工单,再根据检修工单停送电要求联系检修调度对检修区域进行停送电操作的情况下,此过程内的检修工单未统一按电子化管理,且检修人员向检修调度申请某个区域停送电的操作未与预先打印的检修工单关联,该操作可能会导致若在A股道检修,而检修调度停的是B股道的电。
另外,检修调度接收到检修申请后在防误***模拟开操作票,并将操作票传到电脑钥匙进行操作,操作完成后,检修调度需联系现场操作人员接收操作票,检修人员再到检修区域工作,此过程内检修调度所有停送电过程需要模拟开票智能化不完全,未实现智能自动成票、传票、接票功能,且检修人员人工接票操作可能会导致其他待检修区域的班组接错票,造成信息接收有误,额外延长待检修的时间。
针对相关技术中存在的检修调度失误率高以及检修时间长的问题,目前尚未提出有效的解决方案。
发明内容
本公开实施例提供了一种操作票处理方法、装置、存储介质及电子装置,以至少解决相关技术中存在的检修调度失误率高以及检修时间长的问题。
根据本公开的一个实施例,提供了一种操作票处理方法,包括:获取来自服务器的操作票信息,其中,所述操作票信息为所述服务器基于目标应用APP发送的选择指令所确定的信息;基于所述操作票信息从预先配置的多种操作模式中确定出目标操作模式;在确定当前满足目标操作条件的情况下,按照所述目标操作模式生成目标操作票;将所述目标操作票发送给与所述目标操作票对应的目标钥匙,其中,所述目标钥匙具备自动接票并执行操作票的能力。
根据本公开的另一个实施例,提供了一种操作票处理装置,包括:获取模块,设置为获取来自服务器的操作票信息,其中,所述操作票信息为所述服务器基于目标应用APP发送的选择指令所确定的信息;确定模块,设置为基于所述操作票信息从预先配置的多种操作模式中确定出目标操作模式;生成模块,设置为在确定当前满足目标操作条件的情况下,按照所述目标操作模式生成目标操作票;发送模块,设置为将所述目标操作票发送给与所述目标操作票对应的目标钥匙,其中,所述目标钥匙具备自动接票并执行操作票的能力。
根据本公开的又一个实施例,还提供了一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机程序,其中,所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本公开的又一个实施例,还提供了一种电子装置,包括存储器和处理器,所述存储器中存储有计算机程序,所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
通过本公开,可以基于APP发送的选择指令确定操作票信息,进而基于该操作票信息来自动生成操作票,此外,在生成操作票后,还可以将操 作票发送给目标钥匙,继而目标钥匙进行自动接票,整个操作过程实现了操作工单的电子化管理,可以根据实际需求实现自动成票自动传票以及自动接票功能,避免了操作票在传输过程中的误传或误接,保证了操作的成功执行,进而在一定程度上缩短了操作周期,有效解决相关技术中存在的检修调度失误率高以及检修时间长的问题。
附图说明
图1是本公开实施例的一种操作票处理方法的移动终端的硬件结构框图;
图2是根据本公开实施例的操作票处理方法的流程图;
图3是根据本公开实施例的***整体架构图;
图4是根据本公开实施例的车辆段检修作业自动成票传票接票的流程图;
图5是根据本公开实施例的操作票生成流程一;
图6是根据本公开实施例的操作票生成流程二;
图7是根据本公开实施例的操作票生成流程三;
图8是根据本公开实施例的操作票处理装置的结构框图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本公开的实施例。
需要说明的是,本公开的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是设置为区别类似的对象,而不必设置为描述特定的顺序或先后次序。
随着交通事业的不断发展,交通越来越便利,车辆技术随着科技的发展日渐新进,交通基础建设的检修已逐渐日常化和规范化,在日常检修过程中需要根据检修的情况对股道或列位进行停送电操作,停送电操作包括对隔离开关分、合闸操作和地线(临时接地或可视化接地装置)挂拆操作, 但是相关技术中的车辆段应用中检修过程和停送电没有关联,每个流程都是独立存在,流程实施方式相对落后,如何将这些流程关联,如何对流程闭环管理是亟待解决的问题。为了避免落后繁琐的操作票流程带来的安全隐患和对车辆段的检修带来的影响,本公开实例中提出了一套集检修作业工单、操作票、钥匙、防误判断、无线传票、自动接票于一体的车辆段检修作业自动成票传票接票***,该***能够实现车辆段全流程闭环管理,并且生成的操作票自动传票,钥匙自动接票,大大提高生产操作效率。下面结合实施例对本公开进行说明:
本申请实施例中所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在移动终端上为例,图1是本公开实施例的一种操作票处理方法的移动终端的硬件结构框图。如图1所示,移动终端可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和设置为存储数据的存储器104,其中,上述移动终端还可以包括设置为通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解,图1所示的结构仅为示意,其并不对上述移动终端的结构造成限定。例如,移动终端还可包括比图1中所示更多或者更少的组件,或者具有与图1所示不同的配置。
存储器104可设置为存储计算机程序,例如,应用软件的软件程序以及模块,如本公开实施例中的操作票处理方法对应的计算机程序,处理器102通过运行存储在存储器104内的计算机程序,从而执行各种功能应用以及数据处理,即实现上述的方法。存储器104可包括高速随机存储器,还可包括非易失性存储器,如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中,存储器104可进一步包括相对于处理器102远程设置的存储器,这些远程存储器可以通过网络连接至移动终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106设置为经由一个网络接收或者发送数据。上述的网络具 体实例可包括移动终端的通信供应商提供的无线网络。在一个实例中,传输装置106包括一个网络适配器(Network Interface Controller,简称为NIC),其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中,传输装置106可以为射频(Radio Frequency,简称为RF)模块,其设置为通过无线方式与互联网进行通讯。
在本实施例中提供了一种操作票处理方法,图2是根据本公开实施例的操作票处理方法的流程图,如图2所示,该流程包括如下步骤:
步骤S202,获取来自服务器的操作票信息,其中,所述操作票信息为所述服务器基于目标应用APP发送的选择指令所确定的信息;
步骤S204,基于所述操作票信息从预先配置的多种操作模式中确定出目标操作模式;
步骤S206,在确定当前满足目标操作条件的情况下,按照所述目标操作模式生成目标操作票;
步骤S208,将所述目标操作票发送给与所述目标操作票对应的目标钥匙,其中,所述目标钥匙具备自动接票并执行操作票的能力。
其中,执行上述操作的可以是操作票模块,其中,该操作票模块可以位于,例如,移动终端、计算机终端等设备中,此外,上述操作的执行主体还可以是控制器或者为具备类似处理能力的处理设备或处理单元等。
在上述实施例中,目标APP可以接收来自服务器(例如,云服务器)的检修工单,进而在目标APP中显示该检修工单中的内容(工单内容中可以包括:股道、列位号、班组等信息),此外,该目标APP中还可以显示其他的信息,例如,停/送电、挂/拆地线等操作选择信息,进而,操作者(例如,工作负责人)可以在登录目标APP后,在该目标APP中选择相关信息,以生成操作票信息。
此外,上述的目标操作模式实际上是从预先确定的多种模式中选择出来的,即,可以根据操作票信息选择对应的操作模式。预先确定的多种模式至少包括如下模式:分隔离开关、合隔离开关、分隔离开关然后挂一组 地线、拆一组地线然后合隔离开关、分隔离开关然后挂二组地线、拆二组地线然后合隔离开关,其中,每种模式下的操作可以是预先规定好的。
通过上述实施例,可以基于APP发送的选择指令确定操作票信息,进而基于该操作票信息来自动生成操作票,此外,在生成操作票后,还可以将操作票发送给目标钥匙,继而目标钥匙进行自动接票,整个操作过程实现了操作工单的电子化管理,可以根据实际需求实现自动成票自动传票以及自动接票功能,避免了操作票在传输过程中的误传或误接,保证了操作的成功执行,进而在一定程度上缩短了操作周期,有效解决相关技术中存在的检修调度失误率高以及检修时间长的问题。
在一个可选的实施例中,在确定当前满足目标操作条件的情况下,按照所述目标操作模式生成目标操作票之前,上述方法还包括:通过至少执行以下判断操作来确定当前是否满足所述目标操作条件;唯一操作权判断、防误判断、通道是否正常判断、所述目标钥匙是否已有操作票判断;其中,在确定满足唯一操作权、不存在误触发、通道处于正常状态,且所述目标钥匙没有其他操作票的情况下,确定当前满足所述目标操作条件。在本实施例中,整个生成操作票过程都需要进行唯一操作权(具备决策能力的移动终端或计算机终端是否具备唯一操作权)判断、防误判断(停/送电通道正确或挂/拆地线操作正确等)、通道是否正常判断(传操作票通道)、所述目标钥匙是否已有操作票判断(对应接收操作票的移动终端或计算机终端处理空闲状态),在确定满足唯一操作权、不存在误触发、通道处于正常状态,且所述目标钥匙没有其他操作票的情况下,确定当前满足所述目标操作条件,即可按照上述目标模式生成目标操作票。
在一个可选的实施例中,上述方法还包括以下至少之一:在按照所述目标操作模式生成目标操作票的情况下,向所述服务器发送设置为指示已成功生成所述目标操作票的第一通知消息,以指示所述服务器通知所述目标应用已成功生成所述目标操作票;在确定当前不满足所述目标操作条件的情况下,向所述服务器发送设置为指示未成功生成所述目标操作票的第二通知消息,以指示所述服务器通知所述目标应用未成功生成所述目标操 作票以及失败原因,其中,所述第二通知消息中携带设置为指示所述失败原因的指示消息。在本实施例中,在按照上述目标模式成功生成目标操作票后,可以向上述服务器发送设置为指示已成功生成所述目标操作票的第一通知消息,以指示上述服务器通知上述目标APP已成功生成上述目操作票,从而使得目标APP的使用者能够及时知悉目标操作票已成功生成。此外,在确定无法正常生成目标操作票的情况下,例如,在当前不满足所述目标操作条件的情况下,也需要告知服务器,即,向上述服务器发送设置为指示未成功生成所述目标操作票的第二通知消息,其中,该第二通知消息中也可以携带未成功的原因,以指示上述服务器通知述目标APP未成功生成所述目标操作票以及失败原因,例如,在由于当前目标钥匙正在处理其他操作票而导致目标操作票生成失败时,上述目标APP中可以弹出失败原因:目标钥匙已有其他操作票处理,操作票生成失败,从而使得目标APP的使用者能够及时知悉目标操作票生成失败的原因。
在一个可选的实施例中,上述方法还包括:确定待执行目标操作的目标设备的配置属性,其中,所述目标操作是基于所述目标操作模式所确定的;按照所述配置属性确定对所述目标设备执行所述目标操作所需要的第一操作步骤;基于所述第一操作步骤生成所述目标操作票。在本实施例中,操作票模块内部会预先存储有关待操作的目标设备(例如,待检修的线缆等)的配置属性(即,线缆等相关信息),进而在生成上述操作票之前,可以基于设备的配置属性来确定处针对该设备的操作步骤。其中,针对不同的设备,设备配置属性也有差异,设备的配置属性和操作步骤之间的对应关系可以是预先配置好的。
在一个可选的实施例中,上述方法还包括:确定待执行目标操作的目标设备的设备类型,其中,所述目标操作是基于所述目标操作模式所确定的;按照所述设备类型确定对所述目标设备执行所述目标操作所需要的第二操作步骤;基于所述第二操作步骤生成所述目标操作票。在本实施例中,操作票模块内部会预先存储有关待操作的目标设备的类型信息,进而可以在生成上述操作票之前,基于设备的类型信息来确定出针对该设备的操作 步骤。其中,设备类型与操作步骤之间的对应关系可以是预先配置好的。
在一个可选的实施例中,上述方法还包括:确定待执行目标操作的目标设备的操作类型,其中,所述目标操作是基于所述目标操作模式所确定的;按照所述操作类型确定对所述目标设备执行所述目标操作所需要的第三操作步骤;基于所述第三操作步骤生成所述目标操作票。在本实施例中,操作票模块内部会预先存储有关待操作的目标设备的操作类型,进而可以在生成上述操作票之前,可以基于设备的操作类型来确定出针对该设备的操作步骤。其中,设备的操作类型与操作步骤之间的对应关系可以是预先配置好的。
在一个可选的实施例中,在将所述目标操作票发送给与所述目标操作票对应的目标钥匙之后,所述方法还包括:所述目标钥匙在执行所述目标操作票中包括的每一步操作步骤之前,向所述服务器发送询问消息,以询问是否允许执行当前待执行的操作步骤;所述目标钥匙在接收到所述服务器返回的允许执行的响应的情况下,执行所述待执行的操作步骤;所述目标钥匙在接收到所述服务器返回的不允许执行的响应的情况下,终止执行所述待执行的操作步骤以及之后的操作步骤。在本实施例中,目标钥匙在执行每一步操作之前,都会对是否允许执行该操作进行判断,具体判断方式可以包括向服务器确认是否可以执行当期操作,或者,在目标钥匙具备逻辑判断能力的情况下,还可以由目标钥匙自己执行判断操作(例如,目标钥匙预先从服务器获取***中各个器件及线路的状态,进而基于获取的信息来判断是否允许执行当前的操作)。通过实施逻辑判断,可以保障操作执行的安全性和可靠性。
显然,上述所描述的实施例仅仅是本公开一部分的实施例,而不是全部的实施例
下面结合具体实施例对本公开进行具体说明:
图3是根据本公开实施例的***整体架构图,车辆段检修作业一键成票传票方案是通过视频服务器、通讯机、云服务器、智能手机、隔离开关、 可视化接地装置、流动地线、电脑钥匙、各类锁具等通过车辆段管控***实现统一分析、统一管理的方法实现,各模块之间的连接关系具体可以参见附图3。
图4是根据本公开实施例的车辆段检修作业自动成票传票接票的流程图,该流程包括如下步骤:
S402,检修模块生成检修工单传给云服务器(对应图4中的①);
S404,云服务器将检修工单传给智能手机APP(对应于上述的目标APP)(对应图4中的②);
S406,工作负责人登录智能手机APP查看检修工单内容(工单内容已包括:股道、列位号、班组等信息),同时在智能手机APP根据工单停送电要求,选择停/送电、挂/拆地线操作,点击一键生成操作(对应图4中的③);
S408,云服务器接收到需要生成操作票信息并通知操作票模块(对应图4中的④);
S410,操作票模块开始一健成票:操作票模块完成信息收集(股道+列位号等),同时根据工作负责人在智能手机APP上选择的操作模式(分隔离开关、合隔离开关、分隔离开关然后挂一组地线、拆一组地线然后合隔离开关、分隔离开关然后挂二组地线、拆二组地线然后合隔离开关等)生成操作票(整个生成操作票过程进行唯一操作权判断、防误判断、通道是否正常判断、上述目标钥匙是否已有票等判断),将生成操作票的结果发送给云服务器(对应图4中的⑤);
S412,操作票生成成功,云服务器将一键生成操作票成功的信息传送给智能手机APP,操作票生成失败,云服务器将一键生成操作票失败的信息以及失败的原因传送给智能手机APP,例如,一键生成操作票失败的原因(对应图4中的⑥):
1、股道、列位、班组信息(对应钥匙)不全;
2、即没有停/送电也有没挂/拆电线操作;
3、操作设备状态和当前状态不同;
4、选择股道、列位没有找到;
5、模式选择错误:即选了合隔离开关又选择了挂地线,或者即选对了分隔离开关又选择了拆地线等;
6、违反唯一操作权功能;
7、防误逻辑不通过原因某某开关状态不对;
8、没有可用的地线(当不固定地线时);
9、对应班组没有传票通道;
10、传票通道没有开启;
11、当前股道有收发车计划,不能开票;
12、对应班组的钥匙已接到操作票不能接票等。
S414,操作票模块将成功生成的操作票发送给网络控制器(对应图4中的⑦);
S416,网络控制器根据操作票的班组信息确定相应的钥匙(上述目标钥匙)传送操作票,同时钥匙(上述目标钥匙)自动接票,接票成功(对应图4中的⑧);
S418,钥匙操作电动或手动隔离开关,操作过程还有实时逻辑判断如果操作过程发生异常变位会禁止操作(对应图4中的⑨);
S420,钥匙操作可视化接地装置或流动地线,操作过程还有实时逻辑判断如果操作过程发生异常变位会禁止操作(对应图4中的⑩)。
在本公开实施例中,针对待操作设备的配置属性,电脑钥匙支持普通地线两种模式、支持流动地线和固定地线模式功能,其中,普通地线两个模式主要是实现车辆段常用检修过程实现先验电和先取地线两种模式,同时支持流动地线(可以选择某组地线),或固定地线模式(直接和最近的地线绑定),通过挂接地的过程保障了现场检修人员的安全。下面结合图5对如何基于配置属性生成操作票进行说明:
S502,操作票模块在生成操作票之前,需要先获取待操作设备的配置属性(是固定地线还是流动地线),其中,流动地线模式时,取地线可以从多组地线中取没有用的任一地线,固定地线模式时,每个接地点固定一个地线,自动成票时自动关联固定地线,取地线时只能取固定的地线(对应图5中的①);
S504,操作票模块根据配置属性来生成操作票,并传给电脑钥匙(对应图5中的②);
S506,电脑钥匙支持普通地线两种模式,电脑钥匙执行操作票中的各个操作步骤(对应图5中的③),包括:
1、先取地线后验电(验电在取地线之后):挂地线流程:取地线——验电——挂地线——拆验电器拆地线流程:拆地线-放回地线。
2、先验电后取地线(验电在取地线之前):挂地线流程:先验电——取地线——挂地线——拆验电器拆地线流程:拆地线-放回地线)。
在本公开实施例中,针对待操作设备的类型信息,电脑钥匙支持普通地线和可视化接地装置和自动成票,下面结合图6对如何基于设备类型生成操作票进行说明:
S602,操作票模块确定设备类型(普通地线、可视化接地装置),基于设备类型生成操作票(对应图6中的①);
S604,电脑钥匙支持普通地线和可视化接地装置和自动成票,电脑钥匙执行根据设备类型自动生成的操作步骤(对应图6中的②),主要包括如下两种操作模式:
模式1:若设备类型为普通地线,则根据图5描述的两种模式(1、先取地线后验电(验电在取地线之后)2、先验电后取地线(验电在取地线之前))中的一种进行操作(图6中仅示例性地列出一种“先取地线后验电”的操作,在实际应用中还可能是“先验电后取地线”的操作);
模式2:如果是可视化接地装置生成操作步骤为:
接地操作:打开柜门--远方转就地--钥匙打开遥闭—自动验电--按接地按钮—完成接地-就地转远方;
拆地线操作:打开柜门---远方转就地--钥匙打开遥闭--按分闸按钮—分闸成功-就地转远方。
在本公开实施例中,针对待操作设备的操作类型,电脑钥匙支持隔离开关和可视化接地装置就地(包括手动、和电动)和远方操作过程,下面结合图7对如何基于设备操作类型生成操作票进行说明:
S702,操作票模块获取配置属性(是就地操作还是远方操作)(对应图7中的①);
S704,操作票模块根据配置属性(是下述的模式1或者模式2)生成操作票传给电脑钥匙(对应图7中的②);
S706,电脑钥匙支持隔离开关和可视化接地装置两种操作模式,电脑钥匙执行操作票中的各个操作步骤(对应图7中的③):
模式1、就地操作隔离开关或可视化接地装置,打开机械锁进行手动就地操作。
模式2、远方操作隔离开关或可视化接地装置,在钥匙上按远方,同时在***进行遥控远方操作。
通过上述步骤,本公开改变了现阶段检修和操作票分离、人工化、低效的作业模式,通过一键成票即提高了检修人员的工作效率也保障了人员安全,此外,本公开实施例还实现了如下目的:
实现了检修工单的电子化管理,提高了生产效率。
实现根据检修工单中停送电要求实现自动成票及自动传票自动接票功能,检修人员向检修调度申请对某个区域停送电和检修工单关联,不会出现,在A股道检修,而检修调度停的是B股道电的情况。
实现闭环管理功能,包括:检修工单、APP显示检修工单、APP上选择需要停电或送电区域实现自动生成操作票、根据班组绑定的电脑钥匙自 动接票、现场操作状态回传。不会出现班组接错票的情况。
实现了自动成操作票支持普通地线两种模式(验电提前、取地线提前)、支持流动地线模式和固定地线模式、支持普通地线和可视化接地装置、自动成操作票支持就地和远方操作。支持现场所有使用模式,方便可靠。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本公开的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,或者网络设备等)执行本公开各个实施例所述的方法。
在本实施例中还提供了一种操作票处理装置,该装置设置为实现上述实施例及优选实施方式,已经进行过说明的不再赘述。如以下所使用的,术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现,但是硬件,或者软件和硬件的组合的实现也是可能并被构想的。
图8是根据本公开实施例的操作票处理装置的结构框图,如图8所示,该装置包括:
获取模块802,设置为获取来自服务器的操作票信息,其中,所述操作票信息为所述服务器基于目标应用APP发送的选择指令所确定的信息;
确定模块804,设置为基于所述操作票信息从预先配置的多种操作模式中确定出目标操作模式;
生成模块806,设置为在确定当前满足目标操作条件的情况下,按照所述目标操作模式生成目标操作票;
发送模块808,设置为将所述目标操作票发送给与所述目标操作票对应的目标钥匙,其中,所述目标钥匙具备自动接票并执行操作票的能力。
在一个可选的实施例中,所述确定模块804包括:判断单元,设置为通过至少执行以下判断操作来确定当前是否满足所述目标操作条件:唯一操作权判断、防误判断、通道是否正常判断、所述目标钥匙是否已有操作票判断;其中,在确定满足唯一操作权、不存在误触发、通道处于正常状态,且所述目标钥匙没有其他操作票的情况下,确定当前满足所述目标操作条件。
在一个可选的实施例中,上述装置还包括以下模块至少之一:第一通知模块,设置为在按照所述目标操作模式生成目标操作票的情况下,向所述服务器发送设置为指示已成功生成所述目标操作票的第一通知消息,以指示所述服务器通知所述目标应用已成功生成所述目标操作票;第二通知模块,设置为在确定当前不满足所述目标操作条件的情况下,向所述服务器发送设置为指示未成功生成所述目标操作票的第二通知消息,以指示所述服务器通知所述目标应用未成功生成所述目标操作票以及失败原因,其中,所述第二通知消息中携带设置为指示所述失败原因的指示消息。
在一个可选的实施例中,所述生成模块806包括:第一确定单元,设置为确定待执行目标操作的目标设备的配置属性,其中,所述目标操作是基于所述目标操作模式所确定的;第二确定单元,设置为确定待执行目标操作的目标设备的配置属性,其中,所述目标操作是基于所述目标操作模式所确定的;第一生成单元,设置为基于所述第一操作步骤生成所述目标操作票。
在一个可选的实施例中,所述生成模块806包括:第三确定单元,设置为确定待执行目标操作的目标设备的设备类型,其中,所述目标操作是基于所述目标操作模式所确定的;第四确定单元,设置为按照所述设备类型确定对所述目标设备执行所述目标操作所需要的第二操作步骤;第二生成单元,设置为基于所述第二操作步骤生成所述目标操作票。
在一个可选的实施例中,所述生成模块806包括:第五确定单元,设置为确定待执行目标操作的目标设备的操作类型,其中,所述目标操作是 基于所述目标操作模式所确定的;第六确定单元,设置为按照所述操作类型确定对所述目标设备执行所述目标操作所需要的第三操作步骤;第三生成单元,设置为基于所述第三操作步骤生成所述目标操作票。
在一个可选的实施例中,上述目标钥匙包括如下模块:询问模块,设置为在执行所述目标操作票中包括的每一步操作步骤之前,向所述服务器发送询问消息,以询问是否允许执行当前待执行的操作步骤;接收模块,设置为所述目标钥匙在接收到所述服务器返回的允许执行的响应的情况下,执行所述待执行的操作步骤;处理模块,设置为所述目标钥匙在接收到所述服务器返回的不允许执行的响应的情况下,终止执行所述待执行的操作步骤以及之后的操作步骤。
需要说明的是,上述各个模块是可以通过软件或硬件来实现的,对于后者,可以通过以下方式实现,但不限于此:上述模块均位于同一处理器中;或者,上述各个模块以任意组合的形式分别位于不同的处理器中。
本公开的实施例还提供了一种计算机可读存储介质,该计算机可读存储介质中存储有计算机程序,其中,该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中,上述计算机可读存储介质可以包括但不限于:U盘、只读存储器(Read-Only Memory,简称为ROM)、随机存取存储器(Random Access Memory,简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本公开的实施例还提供了一种电子装置,包括存储器和处理器,该存储器中存储有计算机程序,该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中,上述电子装置还可以包括传输设备以及输入输出设备,其中,该传输设备和上述处理器连接,该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所 描述的示例,本实施例在此不再赘述。
通过本公开提供的信息集中管控作业流程,确保了每个操作环节的安全,实现了整个作业流程的智能化,无纸化,真正提升了现场运维作业的效率。
显然,本领域的技术人员应该明白,上述的本公开的各模块或各步骤可以用通用的计算装置来实现,它们可以集中在单个的计算装置上,或者分布在多个计算装置所组成的网络上,它们可以用计算装置可执行的程序代码来实现,从而,可以将它们存储在存储装置中由计算装置来执行,并且在某些情况下,可以以不同于此处的顺序执行所示出或描述的步骤,或者将它们分别制作成各个集成电路模块,或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样,本公开不限制于任何特定的硬件和软件结合。
以上所述仅为本公开的优选实施例而已,并不设置为限制本公开,对于本领域的技术人员来说,本公开可以有各种更改和变化。凡在本公开的原则之内,所作的任何修改、等同替换、改进等,均应包含在本公开的保护范围之内。
工业实用性
如上所述,本公开实施例提供的基于光场感知的眼球追踪方法具有以下有益效果:不需要依靠角膜球面反射模型或闪烁位置来计算用户眼睛的角膜中心即可眼球追踪,也不需要将外部照明源定位在相对于光场摄像头的特定位置,从而很大程度上改善眼球追踪的数据质量,稳定性和追踪精度。

Claims (10)

  1. 一种操作票处理方法,包括:
    获取来自服务器的操作票信息,其中,所述操作票信息为所述服务器基于目标应用APP发送的选择指令所确定的信息;
    基于所述操作票信息从预先配置的多种操作模式中确定出目标操作模式;
    在确定当前满足目标操作条件的情况下,按照所述目标操作模式生成目标操作票;
    将所述目标操作票发送给与所述目标操作票对应的目标钥匙,其中,所述目标钥匙具备自动接票并执行操作票的能力。
  2. 根据权利要求1所述的方法,其中,在确定当前满足目标操作条件的情况下,按照所述目标操作模式生成目标操作票之前,所述方法还包括:
    通过至少执行以下判断操作来确定当前是否满足所述目标操作条件:
    唯一操作权判断、防误判断、通道是否正常判断、所述目标钥匙是否已有操作票判断;
    其中,在确定满足唯一操作权、不存在误触发、通道处于正常状态,且所述目标钥匙没有其他操作票的情况下,确定当前满足所述目标操作条件。
  3. 根据权利要求1所述的方法,其中,所述方法还包括以下至少之一:
    在按照所述目标操作模式生成目标操作票的情况下,向所述服务器发送设置为指示已成功生成所述目标操作票的第一通知消息,以指示所述服务器通知所述目标应用已成功生成所述目标操作票;
    在确定当前不满足所述目标操作条件的情况下,向所述服务器发 送设置为指示未成功生成所述目标操作票的第二通知消息,以指示所述服务器通知所述目标应用未成功生成所述目标操作票以及失败原因,其中,所述第二通知消息中携带设置为指示所述失败原因的指示消息。
  4. 根据权利要求1所述的方法,其中,按照所述目标操作模式生成目标操作票包括:
    确定待执行目标操作的目标设备的配置属性,其中,所述目标操作是基于所述目标操作模式所确定的;
    按照所述配置属性确定对所述目标设备执行所述目标操作所需要的第一操作步骤;
    基于所述第一操作步骤生成所述目标操作票。
  5. 根据权利要求1所述的方法,其中,按照所述目标操作模式生成目标操作票包括:
    确定待执行目标操作的目标设备的设备类型,其中,所述目标操作是基于所述目标操作模式所确定的;
    按照所述设备类型确定对所述目标设备执行所述目标操作所需要的第二操作步骤;
    基于所述第二操作步骤生成所述目标操作票。
  6. 根据权利要求1所述的方法,其中,按照所述目标操作模式生成目标操作票包括:
    确定待执行目标操作的目标设备的操作类型,其中,所述目标操作是基于所述目标操作模式所确定的;
    按照所述操作类型确定对所述目标设备执行所述目标操作所需要的第三操作步骤;
    基于所述第三操作步骤生成所述目标操作票。
  7. 根据权利要求1所述的方法,其中,在将所述目标操作票发送给与所述目标操作票对应的目标钥匙之后,所述方法还包括:
    所述目标钥匙在执行所述目标操作票中包括的每一步操作步骤之前,向所述服务器发送询问消息,以询问是否允许执行当前待执行的操作步骤;
    所述目标钥匙在接收到所述服务器返回的允许执行的响应的情况下,执行所述待执行的操作步骤;
    所述目标钥匙在接收到所述服务器返回的不允许执行的响应的情况下,终止执行所述待执行的操作步骤以及之后的操作步骤。
  8. 一种操作票处理装置,包括:
    获取模块,设置为获取来自服务器的操作票信息,其中,所述操作票信息为所述服务器基于目标应用APP发送的选择指令所确定的信息;
    确定模块,设置为基于所述操作票信息从预先配置的多种操作模式中确定出目标操作模式;
    生成模块,设置为在确定当前满足目标操作条件的情况下,按照所述目标操作模式生成目标操作票;
    发送模块,设置为将所述目标操作票发送给与所述目标操作票对应的目标钥匙,其中,所述目标钥匙具备自动接票并执行操作票的能力。
  9. 一种计算机可读存储介质,所述计算机可读存储介质中存储有计算机程序,其中,所述计算机程序被处理器执行时实现所述权利要求1至7任一项中所述的方法的步骤。
  10. 一种电子装置,包括存储器、处理器以及存储在所述存储器上并可在所述处理器上运行的计算机程序,所述处理器执行所述计算机程序时实现所述权利要求1至7任一项中所述的方法的步骤。
PCT/CN2022/129037 2021-12-01 2022-11-01 操作票处理方法、装置、存储介质及电子装置 WO2023098375A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
GB2309281.0A GB2619167A (en) 2021-12-01 2022-11-01 Operation sheet processing method and device, storage medium, and electronic device
AU2022403593A AU2022403593A1 (en) 2021-12-01 2022-11-01 Operation sheet processing method and device, storage medium, and electronic device

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111456390.XA CN114330764B (zh) 2021-12-01 2021-12-01 操作票处理方法、装置、存储介质及电子装置
CN202111456390.X 2021-12-01

Publications (1)

Publication Number Publication Date
WO2023098375A1 true WO2023098375A1 (zh) 2023-06-08

Family

ID=81047775

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/129037 WO2023098375A1 (zh) 2021-12-01 2022-11-01 操作票处理方法、装置、存储介质及电子装置

Country Status (4)

Country Link
CN (1) CN114330764B (zh)
AU (1) AU2022403593A1 (zh)
GB (1) GB2619167A (zh)
WO (1) WO2023098375A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116484826A (zh) * 2023-06-19 2023-07-25 广东电网有限责任公司 一种操作票生成方法、装置、设备及存储介质
CN117114362A (zh) * 2023-10-18 2023-11-24 江苏秉信科技有限公司 一种电网操作计划排程方法、***、终端设备及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114330764B (zh) * 2021-12-01 2023-09-26 珠海优特电力科技股份有限公司 操作票处理方法、装置、存储介质及电子装置
CN114419870B (zh) * 2022-03-31 2022-07-15 长园共创电力安全技术股份有限公司 基于低功耗无线通信的传感采集***的通信方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997038399A1 (en) * 1996-04-04 1997-10-16 Lottery Products Pty. Ltd. Dispensing apparatus
CN107121606A (zh) * 2017-04-24 2017-09-01 国网浙江省电力公司台州供电公司 用于变电站操作及巡视的智能终端
CN108470313A (zh) * 2018-03-12 2018-08-31 雅砻江流域水电开发有限公司 一种基于移动互联网络的运行操作全过程管控方法和***
CN109711567A (zh) * 2018-12-14 2019-05-03 珠海优特电力科技股份有限公司 检修工作安全措施信息自动生成方法和***
CN111583453A (zh) * 2020-04-20 2020-08-25 深圳供电局有限公司 二次设备屏柜操作方法、装置、计算机设备和存储介质
CN114330764A (zh) * 2021-12-01 2022-04-12 珠海优特电力科技股份有限公司 操作票处理方法、装置、存储介质及电子装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105739405A (zh) * 2014-12-11 2016-07-06 珠海优特电力科技股份有限公司 车辆段接触网停送电过程******及方法
CN104851052B (zh) * 2015-04-02 2017-03-01 国网山东省电力公司青岛供电公司 一种用于输出调度操作票的智能防误方法及***
CN105787668A (zh) * 2015-04-02 2016-07-20 国网山东省电力公司青岛供电公司 一种用于电网远程操作的操作票生成方法及***
CN110690762A (zh) * 2019-10-29 2020-01-14 珠海华伟电气科技股份有限公司 二次设备防误闭锁装置及其方法
CN111106671B (zh) * 2019-12-16 2024-01-30 国网安徽省电力有限公司宿州供电公司 一种变电站编码锁的五防管理控制方法及***
CN113344509A (zh) * 2021-05-27 2021-09-03 深圳供电局有限公司 操作票的生成方法、装置、设备及存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997038399A1 (en) * 1996-04-04 1997-10-16 Lottery Products Pty. Ltd. Dispensing apparatus
CN107121606A (zh) * 2017-04-24 2017-09-01 国网浙江省电力公司台州供电公司 用于变电站操作及巡视的智能终端
CN108470313A (zh) * 2018-03-12 2018-08-31 雅砻江流域水电开发有限公司 一种基于移动互联网络的运行操作全过程管控方法和***
CN109711567A (zh) * 2018-12-14 2019-05-03 珠海优特电力科技股份有限公司 检修工作安全措施信息自动生成方法和***
CN111583453A (zh) * 2020-04-20 2020-08-25 深圳供电局有限公司 二次设备屏柜操作方法、装置、计算机设备和存储介质
CN114330764A (zh) * 2021-12-01 2022-04-12 珠海优特电力科技股份有限公司 操作票处理方法、装置、存储介质及电子装置

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116484826A (zh) * 2023-06-19 2023-07-25 广东电网有限责任公司 一种操作票生成方法、装置、设备及存储介质
CN116484826B (zh) * 2023-06-19 2024-04-26 广东电网有限责任公司 一种操作票生成方法、装置、设备及存储介质
CN117114362A (zh) * 2023-10-18 2023-11-24 江苏秉信科技有限公司 一种电网操作计划排程方法、***、终端设备及存储介质
CN117114362B (zh) * 2023-10-18 2024-02-06 江苏秉信科技有限公司 一种电网操作计划排程方法、***、终端设备及存储介质

Also Published As

Publication number Publication date
GB2619167A (en) 2023-11-29
CN114330764A (zh) 2022-04-12
CN114330764B (zh) 2023-09-26
AU2022403593A9 (en) 2024-02-08
AU2022403593A1 (en) 2023-07-06

Similar Documents

Publication Publication Date Title
WO2023098375A1 (zh) 操作票处理方法、装置、存储介质及电子装置
CN106355357B (zh) 配电网故障处理方法及信息处理***
CN104036348A (zh) 一种电子移动操作票***
CN105057928A (zh) 一种焊接生产线的信息管理***
CN103997079A (zh) 一种电动汽车交流充电桩及其使用方法
CN110969341A (zh) 一种配电终端智能维护方法、装置及***
CN105471982A (zh) 物联网网关与云平台的交互方法及***
CN110289685A (zh) 配电网资源的巡检方法、终端设备和存储介质
CN102448057A (zh) 一种物联网***及其组网方法
CN111552904A (zh) 一种电网运行信息智能发布***
US11505082B2 (en) Charging device for electric vehicles and automatic trobleshooting method thereof
CN106022648A (zh) 一种电力调度报表协调与生成方法
CN204631866U (zh) 输电线路应急抢修数据查询终端***
CN115085921B (zh) 模型训练方法、节点检测方法、装置、设备及介质
CN113013992B (zh) 一种保信主站功能监控方法及装置
TW202218909A (zh) 充電設備之故障診斷與排除系統及其自動故障診斷及排除的方法及電腦程式產品
CN110103761A (zh) 新能源车的充电故障追溯方法与***、服务器及存储介质
CN114095343A (zh) 基于双活***的容灾方法、装置、设备及存储介质
CN115442389A (zh) 路侧单元的故障检测方法、装置、服务器及介质
CN111652394A (zh) 工单处理方法、装置和设备
WO2023236816A1 (zh) 通信连接方法、电子设备、计算机可读存储介质
CN109444802A (zh) 智能电表检测方法及装置、设备、介质
EP3637119A1 (en) Device and method for diagnosing battery pack
CN111030297A (zh) 机房市电停电监测方法及装置
CN111199328A (zh) 一种宽带业务处理***、方法和装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 202309281

Country of ref document: GB

Kind code of ref document: A

Free format text: PCT FILING DATE = 20221101

ENP Entry into the national phase

Ref document number: 2022403593

Country of ref document: AU

Date of ref document: 20221101

Kind code of ref document: A

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22900180

Country of ref document: EP

Kind code of ref document: A1