Temporary work order generation method and system, electronic equipment and computer storage medium

Abstract

The invention discloses a temporary work order generation method and system, electronic equipment and a computer storage medium, and the method comprises the steps: displaying a work order management interface in response to the received abnormal state information of a battery swap station; in response to completion of selection of the task work order component in the work order management interface, generating a work order configuration file in a preset format according to the selected task work order component; and generating a temporary work order according to the work order configuration file. According to the method and the device, when the abnormal state information of the battery swap station is received, a work order management interface matched with the abnormal state information is displayed, and after the work order management interface completes selection of a task work order component according to the actual demand of the current abnormal task, the task work order component is selected; and according to the selected task work order component, generating a work order configuration file which is generated in a user-defined manner and is used for describing the structure and layout of the component. And finally, according to the work order configuration file, generating a temporary work order which is high in adaptability and can take effect immediately. Therefore, the temporary work order creation difficulty is effectively reduced, and the creation efficiency and quality are improved.

Description

Technical Field

[0001] This invention relates to the field of battery swapping station operation and maintenance technology, and in particular to a temporary work order generation method, system, electronic device, and computer storage medium. Background Technology

[0002] Battery swapping station operation and maintenance work is mainly divided into two categories: routine planned tasks (such as equipment inspection, regular equipment maintenance, and city self-inspection) and ad-hoc, unforeseen tasks (such as affixing battery codes and emergency equipment modifications). For routine planned tasks, the existing work order system typically processes them through preset standardized templates and fixed approval processes, which already achieves high efficiency. However, for ad-hoc, unforeseen tasks, the existing work order system has significant shortcomings and cannot provide effective support.

[0003] The existing work order system is designed for routine tasks and has poor template adaptability for temporary tasks. Specifically, the existing system lacks work order templates designed for temporary tasks, forcing maintenance personnel to forcibly apply templates designed for routine tasks, resulting in misaligned, redundant, or missing form fields and difficulty in accurately recording key information.

[0004] Industry data shows that although temporary tasks account for only about 7% of the total number of work orders for battery swapping stations, they consume more than 52% of the operation and maintenance resources, and the error rate of these work orders is 2 to 3 times higher than that of regular tasks, with an average processing time exceeding 60%. The industry has attempted to solve this problem using general-purpose low-code platforms or self-developed systems, but these solutions are not tailored to the specific characteristics of battery swapping station operation and maintenance, lack dedicated component libraries and industry data integration capabilities, and have failed to fundamentally address the core pain points of difficult temporary work order creation, low efficiency, and poor quality.

[0005] Therefore, there is an urgent need for a solution that can generate temporary work orders efficiently, flexibly and accurately to improve the overall efficiency and reliability of battery swapping station operation and maintenance. Summary of the Invention

[0006] The purpose of this application is to provide a method, system, electronic device, and computer storage medium for generating temporary work orders, aiming to solve the problems of difficulty, low efficiency, and poor quality in creating temporary work orders.

[0007] To achieve the above objectives: In a first aspect, embodiments of this application provide a method for generating temporary work orders, the method comprising: In response to receiving abnormal status information from the battery swapping station, the work order management interface is displayed; In response to the selection of task work order components in the work order management interface, a work order configuration file in a preset format is generated based on the selected task work order components. A temporary work order is generated based on the work order configuration file.

[0008] In one embodiment, the step of responding to the selection of a task work order component in the work order management interface and generating a work order configuration file in a preset format based on the selected task work order component includes: In response to a selection operation in the work order management interface, at least one task work order component from the candidate area is added to the form design area; Based on the layout of the task order component in the form design area, a preset format work order configuration file is generated.

[0009] In one embodiment, before the selection of the task order component in the work order management interface is completed, the method further includes: Based on the type of the abnormal status information, and / or the current status of the battery swapping station, and / or the historical work order data of the battery swapping station, one or more preset work order templates are recommended in the work order management interface. The response to selecting the task completion work order component includes: In response to selecting any of the recommended preset work order templates.

[0010] In one embodiment, before generating a preset format work order configuration file based on the selected work order configuration, the method further includes: A front-end framework with a preset format is constructed, which is used to parse the work order configuration file.

[0011] In one embodiment, generating a temporary work order based on the work order configuration file includes: The front-end framework is invoked to parse the work order configuration file in order to dynamically render and generate an interactive temporary work order page; In response to the completion of task information entry on the temporary work order page, the temporary work order page is uploaded to the server to obtain a temporary work order with a unique number.

[0012] In one embodiment, after generating a temporary work order based on the work order configuration file, the method further includes: In response to the successful approval of the temporary work order, the battery swapping station will be associated with the station administrator; Based on the urgency of the abnormal status information and / or the type of the temporary work order, the temporary work order is assigned to the terminal device of the target maintenance personnel, or pushed to the station administrator for manual assignment.

[0013] In one embodiment, after generating a temporary work order based on the work order configuration file, the method further includes: In response to the completion of the temporary work order, the work order configuration file, execution process data and result data are uploaded to the server, and tagged and archived in the preset work order template library.

[0014] Secondly, a temporary work order generation system, the system comprising: The display module is used to respond to abnormal status information received from the battery swapping station and display the work order management interface; The work order configuration file generation module is used to generate a work order configuration file in a preset format in response to the selection of task work order components in the work order management interface. The temporary work order generation module is used to generate temporary work orders based on the work order configuration file.

[0015] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the temporary work order generation method described above.

[0016] Fourthly, embodiments of this application provide a computer storage medium storing a computer program, which, when executed by the processor, implements the steps of the temporary work order generation method described above.

[0017] In this application, upon receiving abnormal status information from a battery swapping station, a work order management interface adapted to the abnormal status information is displayed. After selecting the task work order components based on the actual needs of the current abnormal task within the work order management interface, a custom-generated work order configuration file describing the component structure and layout is generated based on the selected task work order components. Finally, a highly adaptable and immediately effective temporary work order is generated based on the work order configuration file. This effectively reduces the difficulty of creating temporary work orders and improves creation efficiency and quality. Attached Figure Description

[0018] Figure 1 This is a flowchart illustrating a temporary work order generation method provided in an embodiment of the present invention.

[0019] Figure 2 This is a schematic diagram of a temporary work order generation system provided in an embodiment of the present invention.

[0020] Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention.

[0021] Explanation of reference numerals in the attached figures: 10. Display module; 20. Work order configuration file generation module; 30. Temporary work order generation module; 310. Processor; 311. Memory; 312. Network interface; 313. Bus system. Detailed Implementation

[0022] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0023] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, components, features, and elements with the same names in different embodiments of this application may have the same meaning or different meanings, the specific meaning of which must be determined by its interpretation in that specific embodiment or further in conjunction with the context of that specific embodiment.

[0024] It should be understood that although the terms first, second, third, etc., may be used herein to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this document, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if," as used herein, can be interpreted as "when," "when," or "in response to determination." Furthermore, as used herein, the singular forms "a," "an," and "the" are intended to also include the plural forms unless the context indicates otherwise. It should be further understood that the terms "comprising," "including," indicate the presence of the stated feature, step, operation, element, component, item, kind, and / or group, but do not exclude the presence, occurrence, or addition of one or more other features, steps, operations, elements, components, items, kinds, and / or groups. The terms "or" and "and / or" as used herein are to be interpreted as inclusive, or mean any one or any combination thereof. Therefore, "A, B, or C" or "A, B, and / or C" means "any one of the following: A; B; C; A and B; A and C; B and C; A, B, and C". Exceptions to this definition will only occur if the combination of elements, functions, steps, or operations is inherently mutually exclusive in some way.

[0025] It should be understood that although the steps in the flowcharts of this application's embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some of the steps in the figures may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times, and their execution order is not necessarily sequential, but can be performed alternately or in turn with other steps or at least a portion of the sub-steps or stages of other steps.

[0026] It should be noted that step designations such as S1 and S2 are used in this document for the purpose of more clearly and concisely describing the corresponding content, and do not constitute a substantial limitation on the order. In specific implementation, those skilled in the art may execute S2 first and then S1, etc., but these should all be within the protection scope of this application.

[0027] It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0028] In the following description, the use of suffixes such as "module," "part," or "unit" to denote elements is solely for the purpose of illustrative purposes and has no specific meaning in itself. Therefore, "module," "part," or "unit" may be used interchangeably.

[0029] The following is a brief explanation of the terms that may be used in this application: AMIS is a low-code front-end framework based on JSON configuration. It enables developers to quickly build data-driven applications through declarative programming. It provides a rich component library and flexible UI layout options, allowing developers to define the interface and interactions through simple JSON configuration, thereby significantly improving development efficiency and reducing development costs.

[0030] JSON (JavaScript Object Notation) is an open standard file and data exchange format designed based on a subset of ECMAScript. It is easy for humans to read and write, and also easy for machines to parse and generate. JSON is language-independent, and many programming languages ​​support JSON for data exchange. JSON is a commonly used data format with various applications in electronic data interchange, including data exchange between web applications and servers. Its concise and clear hierarchical structure effectively improves network transmission efficiency, making it an ideal data exchange language. Its files typically use the .json extension.

[0031] Please refer to Figure 1 , Figure 1 A flowchart illustrating a method for generating temporary work orders is shown. The method includes the following steps: S1. In response to receiving abnormal status information from the battery swapping station, display the work order management interface. Understandably, traditional systems provide users with a fixed, pre-set list of standard templates when creating a work order. Users can only "forcefully select" the closest one from these unrelated templates, which is the root cause of poor adaptability. Specifically, in this embodiment, the innovation of this step lies in the precision of the triggering mechanism. The system does not provide a general template library, but rather activates the work order creation process based on specific, real-time abnormal events (such as "battery temperature sensor alarm" or "robotic arm lag"). This ensures that all subsequent configuration operations revolve around solving this specific problem, avoiding template-task mismatches from the outset.

[0032] S2. In response to the selection of task work order components in the work order management interface, a preset format work order configuration file is generated based on the selected task work order components. It is understandable that the "template" in traditional solutions is an indivisible whole with fixed fields that cannot be flexibly added or deleted. Users cannot quickly create a simple work order containing only two fields, "battery code" and "photo," for the task "Paste Battery Code." Instead, they must use a complex maintenance work order containing numerous unrelated fields (such as "Maintenance Oil Type" and "Replacement Part Number"). Specifically, in this embodiment, the system breaks down the complete work order into the smallest, functionally independent components (such as "Text Input Box," "Image Upload," "Geographic Location," and "Battery Code Scanner"). Users can freely select and combine the required components according to the actual needs of the current abnormal task, like building blocks. The preset format work order configuration file is preferably a JSON configuration file.

[0033] For example, to handle the "Battery Antifreeze Detection" task, you only need to select the "Thermometer Input Component," "Photo Upload Component," and "Result Selection Component"; to handle the "Paste Encoding" task, you only need to select the "Text Input" or "QR Code Scanning Component" and "Photo Upload Component." Selecting the corresponding task work order component as needed completely eliminates the problems of misaligned, redundant, or missing fields. Thus, the final work order format is no longer a rigid template, but a fully custom-generated work order configuration file (such as a JSON file) describing the component structure and layout. This file dynamically defines a "custom template" that is perfectly adapted to the current temporary task.

[0034] Furthermore, the battery swapping station system has a built-in, expandable library of dedicated battery swapping station components (such as battery coding scanning frames and equipment temperature input controls), which supports drag-and-drop integration. When new differentiated tasks need to be added, only the corresponding task work order component needs to be developed for rapid deployment, and it supports cross-site sharing, achieving "develop once, reuse across the entire network".

[0035] S3. Generate a temporary work order based on the work order configuration file. Understandably, traditional technical solutions merge and categorize multiple maintenance processes before submitting them to the product team. The product team then generates a requirements document, and developers conduct research, testing, and deployment for each specific requirement. This process has a development cycle of several weeks, resulting in high costs, severely limited configuration flexibility, and urgent work order timeliness requirements, leaving battery swapping station personnel and the product team in a constant reactive state. Specifically, in this embodiment, the system can immediately instantiate the work order configuration file generated in step S2 into a highly adaptable, immediately effective, operable, and submittable temporary work order, without relying on development intervention. This means that "custom" behaviors can take effect immediately, without any programming or deployment waiting process, achieving "what you want is what you get" adaptability.

[0036] By executing steps S1~S3, the following were achieved: (1) Breakthrough in timeliness: The generation of temporary work orders was shortened from several weeks to minutes, enabling timely response to urgent tasks and completely solving the timeliness bottleneck; (2) Sharp reduction in cost: 80% reduction in repetitive development, requiring only component-level development, reducing operation and maintenance costs by more than 50%; (3) Operational autonomy: Station administrators can freely configure temporary work orders with zero technical threshold, flexibly adapting to the differentiated standards of various cities; (4) Efficient reuse of task work order components: The custom component library supports cross-site sharing, increasing the speed of new requirement implementation by 3 times and avoiding reinventing the wheel. In this way, the difficulty of creating temporary work orders was effectively reduced, and the creation efficiency and quality were improved.

[0037] Optionally, step S2, which involves responding to the selection of a task work order component in the work order management interface and generating a work order configuration file in a preset format based on the selected task work order component, includes: responding to the selection operation in the work order management interface by adding at least one task work order component from the candidate area to the form design area; and generating a work order configuration file in a preset format based on the layout of the task work order components in the form design area. Understandably, in traditional technical solutions, users are faced with a fixed and complete template library. For a newly emerging temporary task (such as "checking ground waterproofing"), users can only choose the closest one from unrelated templates such as "equipment maintenance" and "battery inspection," then manually delete a large number of irrelevant fields and hope that there are usable fields to fill in information such as "water depth" and "photos." This process is cumbersome, and the result is often a compromised "hybrid." Furthermore, adding a field or modifying the layout requires front-end engineers to modify code, test, package, and deploy, a lengthy process that cannot respond to the urgency of temporary tasks.

[0038] In this embodiment, users no longer select "templates" but instead choose "components" (building blocks). For the task of "checking ground waterproofing," users only need to precisely drag and drop three components from the candidate area: "numerical input box" (for recording water depth), "image upload" (for capturing the scene), and "text notes" (for explaining the situation). Through atomic component combination, the generated work order form achieves 100% matching with task requirements, realizing precise and personalized work order configuration and completely eliminating field misalignment and redundancy. Furthermore, station administrators (without technical background) can complete the form construction through this visual drag-and-drop operation. The system automatically converts the UI layout and component attributes into a structured work order configuration file (such as JSON) in real time. This means that once an element is already in the component library, any form change can be completed immediately without development, testing, and release processes, greatly freeing up development resources and improving the operation and maintenance team's autonomous response capability and speed to sudden demands, achieving "what you think is what you get."

[0039] Optionally, before selecting the task work order component in the work order management interface in step S2, the method further includes: recommending one or more preset work order templates in the work order management interface based on the type of abnormal status information, and / or the current status of the swapping station, and / or the historical work order data of the swapping station; responding to the selection of the task work order component includes: responding to selecting any of the recommended preset work order templates. Specifically, in this embodiment, the system recommends one or more preset work order templates to station management personnel in the work order management interface based on the type of abnormal status information, and / or the current status of the swapping station, and / or the historical work order data of the swapping station. Station management personnel only need to select the recommended preset work order template to use it immediately. Thus, on the one hand, inexperienced employees may not know which items to check or which data to record when handling a specific fault. Intelligent recommendation is equivalent to a built-in expert system, directly providing them with the best operating procedures that have been refined, avoiding the omission of key steps, and ensuring the standardization and quality of operation and maintenance work. On the other hand, whenever a temporary work order is successfully processed and closed, its work order configuration and process can be saved as a new pre-set template and labeled with the corresponding fault type (i.e., supporting custom expansion and iteration of components). When a similar fault occurs again (whether at the same site or a different site), the system can retrieve and recommend the template from the template library through algorithms (matching the anomaly type, device code, etc.), realizing "one-time creation, benefiting the whole domain", which greatly improves the organization's overall operation and maintenance capabilities.

[0040] The types of abnormal status information may include, but are not limited to: equipment fault alarms (such as BMS communication timeout, battery swapping robot servo alarm, abnormal liquid cooling system pressure, door lock sensor failure, etc.), sensor data exceeding limits (such as excessive battery temperature, smoke detector alarm, excessive ambient humidity, etc.), software system abnormalities (such as loss of background service heartbeat, full database connection pool, etc.), and manually reported events (such as customer complaints, inspection findings, headquarters instructions, etc.). The current status of the battery swapping station may include, but is not limited to: service load status (such as the current number of vehicles in the queue, battery inventory in the station, the current service mode being "peak mode" or "maintenance and debugging mode", etc.), equipment operation status (such as robot status, charging rack status, network status, etc.), and environmental and business status (such as time period, weather status, station type, etc.). The historical work order data of the battery swapping station may include, but is not limited to: work unit data (such as work order type, resolution time, associated faults, etc.), work order content data (such as templates / components used, execution results, etc.), and resource allocation data (such as assigned personnel, required spare parts, etc.).

[0041] Optionally, before generating the preset format work order configuration file according to the selected work order configuration in step S2, the method further includes: building a preset format front-end framework, which is used to parse the work order configuration file. It is understandable that in traditional technical solutions, the appearance of a work order (UI), what needs to be filled in (business logic), and how to submit (execution) are all hard-coded in the software program. Changing a single field requires recoding, testing, and deployment. Specifically, in this embodiment, the preset format front-end framework is the low-code front-end framework Amis, which can instantly parse JSON and render the page in the user's browser. This means that from clicking "Generate" to seeing the work order form, it is almost instantaneous, without waiting for server-side rendering, resulting in a smooth experience. Furthermore, the Amis framework supports custom components. When the business requires a new, special field type (such as a "battery health rating slider" or an "AR glasses-assisted inspection component"), developers only need to develop this one component based on the Amis specifications. Once this new component is registered in the framework and platform's component library, it can be immediately used by all site administrators via drag-and-drop, without requiring any modifications to the engine itself.

[0042] Amis, acting as the execution layer, is a general-purpose and stable rendering engine. It only parses the JSON configuration and transforms it into realistic, interactive web page elements; it doesn't concern itself with the specific business logic. The work order configuration file, acting as the configuration layer, is a purely descriptive data file. It only describes "an input field is required," "an image upload is required," and "these are required fields," but it has no execution capabilities of its own. This separation ensures that changing the work order format does not require modifying the engine code, and upgrading the engine will not affect existing work order configurations. Both can develop and iterate independently, greatly improving the system's flexibility and maintainability.

[0043] Optionally, the step S3 of generating a temporary work order based on the work order configuration file includes: S31. The front-end framework is invoked to parse the work order configuration file and dynamically render an interactive temporary work order page. Specifically, in this embodiment, the front-end framework (Amis) acts as a rendering engine. This rendering engine parses the work order configuration file (JSON) and immediately renders an interactive temporary work order page dynamically. The temporary work order page contains form elements (input boxes, buttons, lists, etc.), and all interactive logic (validation, calculation, click events) is configured by default.

[0044] S32; In response to the completion of task information entry on the temporary work order page, the temporary work order page is uploaded to the server to obtain a temporary work order with a unique number. Specifically, in this embodiment, the server assigns a unique ID to the temporary work order, which is a unique identifier for the work order throughout its entire lifecycle. All subsequent execution, feedback, extension, and closure operations revolve around this ID. The work order data (configuration + user-entered content) is uploaded to the server and is no longer temporary data in memory. In other words, even if the browser is closed or the network is interrupted, the temporary work order will not be lost. In this way, refined and process-oriented management of temporary tasks is achieved, solving the problem of difficulty in tracking and evaluating temporary tasks in traditional methods, and providing a data foundation for the transparency and quantification of operation and maintenance management.

[0045] Optionally, after generating a temporary work order based on the work order configuration file as described in step S3, the method further includes: in response to the successful approval of the temporary work order, associating the battery swapping station with the station administrator; and assigning the temporary work order to the terminal device of the target maintenance personnel, or pushing it to the station administrator for manual assignment, based on the urgency of the abnormal status information and / or the type of the temporary work order. Specifically, in this embodiment, after the temporary work order is approved, the system first automatically associates the work order with the battery swapping station to which it belongs and the station administrator responsible for that station. This means that the "location of the incident" and the "responsible person" of the work order are determined. Then, the system will automatically make a dispatch decision based on two key factors—the urgency of the work order (e.g., high-risk faults require immediate handling) and the type of work order (e.g., mechanical faults require maintenance personnel, software problems require programmers).

[0046] For urgent work orders with clearly defined rules, the system skips manual approval and directly dispatches them to the terminal of the most suitable target maintenance personnel. For work orders that are complex or less urgent, the system pushes the work order to the station administrator, who then manually assigns it based on the site conditions and personnel availability. This seamless transition from "work order creation" to "work order execution," coupled with the ability to manually associate temporary work orders with designated station administrators after successful approval, allows for one-click access to the responsible person, eliminating redundant approvals and accelerating task response by 60%.

[0047] Optionally, after generating a temporary work order based on the work order configuration file as described in step S3, the method further includes: in response to the completion of the temporary work order, uploading the work order configuration file, execution process data, and result data to the server, and categorizing and archiving them into a preset work order template library by labeling them respectively. Specifically, in this embodiment, the system does not simply mark the work order as "completed," but uploads the three core data, namely the work order configuration file, execution process data, and result data, to the server in a package and uploads it to the server. Then, the system automatically or manually adds one or more category tags to this set of data. Finally, this tagged "data package" is systematically archived into the preset work order template library. In this way, the templates in the template library are no longer the initial few preset ones, but continue to grow and enrich as work orders are completed. When the system encounters a similar abnormal state again (such as the same device alarm), the intelligent recommendation algorithm can find the historical template with the highest matching degree from this "proven successful" template library and recommend it to the user, greatly improving the reliability of the recommendation function and user trust.

[0048] Understandably, in traditional technical solutions, when an experienced employee handles a complex fault, their experience may only exist in their personal notebook or memory, making it difficult to effectively share and pass on. New employees encountering the same problem still need to figure it out from scratch. However, through this embodiment, the experienced worker's successful handling process, including their customized work order format (configuration file), operation flow (process data), and final result (result data), is completely "learned" by the system and saved as a new template in the pre-built work order template library. In this way, personal experience is transformed into organizational assets, avoiding "knowledge loss" caused by staff turnover. The next time any employee at any site encounters the same problem, there is no need to redesign the work order by dragging and dropping components; they can simply search for and call this archived template directly from the recommendation list or template library, achieving "create once, reuse infinitely."

[0049] The work order configuration file refers to the JSON configuration file previously generated by dragging and dropping components; it is the "blueprint" of this work order. The execution process data refers to all records during the execution of the work order, such as the operation time, operator, and intermediate results for each step. The result data refers to the final processing result, conclusion, uploaded images, and measured values ​​of the work order.

[0050] Please refer to Figure 2 , Figure 2 A schematic diagram of a temporary work order generation system is shown. The system includes: Display module 10 is used to display the work order management interface in response to receiving abnormal status information from the battery swapping station. Specifically, in this embodiment, the work order management interface is dynamically generated through a JSON configuration file based on the low-code front-end framework Amis. Display module 10 is essentially a low-code page configuration module, responsible for defining temporary work order forms, lists, filters, statistics panels, and other page structures through the JSON configuration file. It also supports visual drag-and-drop and online configuration, reducing the frequency of front-end personnel intervention. Furthermore, it supports directly displaying algorithm-recommended work order templates or previously preset templates.

[0051] The work order configuration file generation module 20, electrically connected to the display module 10, is used to generate a preset format work order configuration file in response to the selection of task work order components in the work order management interface. Specifically, in this embodiment, the work order configuration file generation module 20 is used to generate a JSON configuration file based on the task work order components selected by the user. The task work order components can be, for example, "text input box," "image upload," "geolocation," "battery code scanner," etc., and are not limited here.

[0052] The temporary work order generation module 30 is electrically connected to the work order configuration file generation module 20 and is used to generate temporary work orders based on the work order configuration file. Specifically, in this embodiment, the temporary work order generation module 30 calls the front-end framework Amis to parse the JSON work order configuration file to dynamically render and generate an interactive temporary work order page. Then, in response to the completion of task information entry on the temporary work order page, the temporary work order page is uploaded to the server to obtain a temporary work order with a unique number. This achieves refined and process-oriented management of temporary tasks, solves the problem of difficulty in tracking and evaluating temporary tasks in traditional methods, and provides a data foundation for the transparency and quantification of operation and maintenance management.

[0053] It is understandable that when the battery swapping station implements the temporary work order generation system, it achieves the same beneficial effects as the temporary work order generation method described above, which will not be elaborated here.

[0054] Based on the same inventive concept as the foregoing embodiments, this invention provides an electronic device, such as... Figure 3 As shown, the device includes: a processor 310 and a memory 311 storing a computer program; wherein, Figure 3 The processor 310 shown in the diagram does not indicate that there is only one processor 310, but only indicates the positional relationship of the processor 310 relative to other devices. In practical applications, there can be one or more processors 310; similarly, Figure 3The memory 311 illustrated herein has the same meaning, that is, it is only used to indicate the positional relationship of memory 311 relative to other devices. In practical applications, there can be one or more memories 311. When the processor 310 runs the computer program, the method applied to the above-mentioned device is implemented.

[0055] The device may also include at least one network interface 312. The various components of the device are coupled together via a bus system 313. It is understood that the bus system 313 is used to implement communication between these components. In addition to a data bus, the bus system 313 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 3 The general designated all buses as Bus System 313.

[0056] The memory 311 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 311 described in the embodiments of the present invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0057] The memory 311 in this embodiment of the invention is used to store various types of data to support the operation of the device. Examples of this data include: any computer programs used to operate on the device, such as operating systems and applications; contact data; phonebook data; messages; pictures; videos, etc. The operating system includes various system programs, such as the framework layer, core library layer, driver layer, etc., used to implement various basic services and handle hardware-based tasks. Applications can include various applications, such as media players, browsers, etc., used to implement various application services. Here, the program implementing the method of this embodiment of the invention can be included in the application.

[0058] Based on the same inventive concept as the foregoing embodiments, this embodiment also provides a computer-readable storage medium storing a computer program. The computer-readable storage medium can be a magnetic random access memory (FRAM), a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM), etc.; it can also be various devices including one or any combination of the above-mentioned memories, such as mobile phones, computers, tablet devices, personal digital assistants, etc. When the computer program stored in the computer-readable storage medium is run by a processor, it implements the above method. For the specific steps implemented when the computer program is executed by the processor, please refer to [link to relevant documentation]. Figure 1 The description of the illustrated embodiments will not be repeated here.

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

[0060] In this document, the terms “comprising,” “including,” or any other variations thereof are intended to cover non-exclusive inclusion, which includes not only the elements listed but also other elements not expressly listed.

[0061] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for generating temporary work orders, characterized in that, The method includes: In response to receiving abnormal status information from the battery swapping station, the work order management interface is displayed; In response to the selection of task work order components in the work order management interface, a work order configuration file in a preset format is generated based on the selected task work order components. A temporary work order is generated based on the work order configuration file.

2. The method according to claim 1, characterized in that, The response involves selecting a task work order component in the work order management interface and generating a work order configuration file in a preset format based on the selected task work order component, including: In response to a selection operation in the work order management interface, at least one task work order component from the candidate area is added to the form design area; Based on the layout of the task order component in the form design area, a preset format work order configuration file is generated.

3. The method according to claim 1, characterized in that, Before the response involves selecting the task order component in the task order management interface, the method further includes: Based on the type of the abnormal status information, and / or the current status of the battery swapping station, and / or the historical work order data of the battery swapping station, one or more preset work order templates are recommended in the work order management interface. The response to selecting the task completion work order component includes: In response to selecting any of the recommended preset work order templates.

4. The method according to claim 1, characterized in that, Before generating a preset format work order configuration file based on the selected work order configuration, the method further includes: A front-end framework with a preset format is constructed, which is used to parse the work order configuration file.

5. The method according to claim 4, characterized in that, The step of generating a temporary work order based on the work order configuration file includes: The front-end framework is invoked to parse the work order configuration file in order to dynamically render and generate an interactive temporary work order page; In response to the completion of task information entry on the temporary work order page, the temporary work order page is uploaded to the server to obtain a temporary work order with a unique number.

6. The method according to claim 1, characterized in that, After generating a temporary work order based on the work order configuration file, the method further includes: In response to the successful approval of the temporary work order, the battery swapping station will be associated with the station administrator; Based on the urgency of the abnormal status information and / or the type of the temporary work order, the temporary work order is assigned to the terminal device of the target maintenance personnel, or pushed to the station administrator for manual assignment.

7. The method according to claim 1, characterized in that, After generating a temporary work order based on the work order configuration file, the method further includes: In response to the completion of the temporary work order, the work order configuration file, execution process data and result data are uploaded to the server, and tagged and archived in the preset work order template library.

8. A temporary work order generation system, characterized in that, The system includes: The display module is used to respond to abnormal status information received from the battery swapping station and display the work order management interface; The work order configuration file generation module is used to generate a work order configuration file in a preset format in response to the selection of task work order components in the work order management interface. The temporary work order generation module is used to generate temporary work orders based on the work order configuration file.

9. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the temporary work order generation method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the temporary work order generation method as described in any one of claims 1 to 7.

Images