Literature and electricity management method and device based on passenger car MRO system
By realizing the identification, storage and management of text and telephone information in the bus MRO system, the complex problem of text and telephone information management of the Ministry of Railways and Vehicles has been solved, the management efficiency and accuracy are improved, and the rework phenomenon is reduced.
Patent Information
- Application Number
- CN202411800082.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-09
- Publication Date
- 2025-03-28
AI Technical Summary
The management of the literature and electricity of the National Railway Bus Department is complex, involving a long time span, a large vehicle coverage, a different manufacturer, a different batch number, a different special project. Traditional paper document recordings are prone to inadequate identification and management omissions, which leads to the subsequent failure to meet the owner's requirements, resulting in rework and other phenomena.
Provide a method for managing text and telecommunications based on a passenger bus MRO system, including receiving text and telecommunications to be processed, identifying text and telecommunications types, separating technical text and telecommunications information from non-technical text and telecommunications information, storing these information into the passenger bus MRO system, and generating an inspection task list based on the non-technical text and telecommunications information, and storing it in the system.
Through digital means, a document structure system is established, the departmental department and departmental departmental department information is archived, and numbering is maintained to ensure the management efficiency and accuracy of railway bus maintenance business and reduce rework.
Smart Images

Figure CN119722012A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of railway transportation technology, and in particular to a document management method based on a passenger car MRO system. The present application also relates to a document management device based on a passenger car MRO system, a computing device, and a computer-readable storage medium. Background Art
[0002] The management of documents and electronics in the National Railway Passenger Car Department is complex, involving a long time span, a wide range of vehicle models, different manufacturers, different batch numbers, different professions, and different special projects. The use of traditional paper documents for recording is prone to inadequate identification of documents and electronics, management omissions, etc., resulting in subsequent failure to meet the owner's requirements and resulting in rework. Summary of the invention
[0003] In view of this, the embodiment of the present application provides a document management method based on a bus MRO system to solve the technical defects existing in the prior art. The embodiment of the present application also provides a document management device based on a bus MRO system, a computing device, and a computer-readable storage medium.
[0004] According to a first aspect of an embodiment of the present application, a document management method based on a bus MRO system is provided, comprising:
[0005] Receive documents to be processed;
[0006] Identify the documents to be processed, and determine the technical documents and non-technical documents to be processed;
[0007] Storing the non-technical document information to be processed and the technical document information to be processed in the bus MRO system;
[0008] Generate an occasional inspection task list based on the non-technical document and electronic information to be processed, and store the occasional inspection task list in the passenger car MRO system.
[0009] Optionally, the identifying the documents to be processed and determining the technical documents to be processed and the non-technical documents to be processed include:
[0010] Scan the document to be processed to obtain the document information to be processed;
[0011] The document information to be processed is processed by a pre-trained recognition model to determine the document type corresponding to the document to be processed, wherein the document type includes technical and non-technical types, the technical type corresponds to the technical document information to be processed, and the non-technical type corresponds to the non-technical document information to be processed.
[0012] Optionally, the storing the to-be-processed non-technical documents and the to-be-processed technical documents in a bus MRO system includes:
[0013] Based on a preset first splitting rule, split the non-technical document and electronic information to be processed to obtain a non-technical document and electronic information group;
[0014] Splitting the to-be-processed technical document and electronic information based on a preset second splitting rule to obtain a technical document and electronic information group;
[0015] Storing the non-technical text and electronic information group in a first storage location of the passenger car MRO system;
[0016] The technical text and electronic information group is stored in a second storage location of the passenger car MRO system.
[0017] Optionally, generating a list of occasional inspection tasks according to the non-technical document and electronic information to be processed includes:
[0018] Based on a preset semantic recognition model, the non-technical document and electronic information to be processed is processed to obtain a list of occasional inspection tasks.
[0019] Optionally, it also includes:
[0020] Constructing a work order based on the occasional inspection task list;
[0021] The execution of the work order is monitored within a preset time period, and the monitoring results are written into the passenger car MRO system.
[0022] According to a second aspect of an embodiment of the present application, a document management device based on a bus MRO system is provided, comprising:
[0023] A receiving module, configured to receive documents to be processed;
[0024] An identification module is configured to identify the documents to be processed, and determine the technical documents to be processed and the non-technical documents to be processed;
[0025] A storage module, configured to store the non-technical document and electronic information to be processed and the technical document and electronic information to be processed in a bus MRO system;
[0026] The occasional inspection module is configured to generate an occasional inspection task list according to the non-technical document and electronic information to be processed, and store the occasional inspection task list in the passenger car MRO system.
[0027] According to a third aspect of an embodiment of the present application, a computing device is provided, including:
[0028] Memory and processor;
[0029] The memory is used to store computer-executable instructions, and the processor implements the steps of the document and electronic management method based on the bus MRO system when executing the computer-executable instructions.
[0030] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores computer-executable instructions, and when the instructions are executed by a processor, the steps of the document and electronic management method based on the bus MRO system are implemented.
[0031] According to a fifth aspect of an embodiment of the present application, a chip is provided, which stores a computer program. When the computer program is executed by the chip, the steps of the document and electronic management method based on the bus MRO system are implemented.
[0032] The document management method based on the passenger car MRO system provided by the present application receives documents to be processed; identifies the documents to be processed, determines the technical document information to be processed and the non-technical document information to be processed; stores the non-technical document information to be processed and the technical document information to be processed in the passenger car MRO system; generates an occasional inspection task list based on the non-technical document information to be processed, and stores the occasional inspection task list in the passenger car MRO system. Establish a file structure system, archive and manage department documents and department documents, maintain department document and department document numbers and other information, and ensure that the railway passenger car maintenance feature business can be managed by using digital means for passenger car maintenance business management. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0034] Figure 1 This is a flow chart of a document management method based on a bus MRO system provided by an embodiment of the present application;
[0035] Figure 2 It is a structural schematic diagram of a document management device based on a passenger car MRO system provided by an embodiment of the present application;
[0036] Figure 3 It is a structural block diagram of a computing device provided in one embodiment of the present application. DETAILED DESCRIPTION
[0037] Many specific details are described in the following description to facilitate a full understanding of the present application. However, the present application can be implemented in many other ways than those described herein, and those skilled in the art can make similar generalizations without violating the connotation of the present application, so the present application is not limited by the specific implementation disclosed below.
[0038] The terms used in one or more embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of the present application. The singular forms of "a", "said" and "the" used in one or more embodiments of the present application and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of the present application refers to and includes any or all possible combinations of one or more associated listed items.
[0039] It should be understood that, although the terms first, second, etc. may be used to describe various information in one or more embodiments of the present application, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of the present application, the first may also be referred to as the second, and similarly, the second may also be referred to as the first.
[0040] In the present application, a document management method based on a bus MRO system is provided. The present application also relates to a document management device based on a bus MRO system, a computing device, and a computer-readable storage medium, which are described in detail one by one in the following embodiments.
[0041] Figure 1 A flowchart of a document management method based on a bus MRO system provided according to an embodiment of the present application is shown, which specifically includes the following steps:
[0042] Step S102: receiving documents to be processed;
[0043] Step S104: Identify the documents to be processed, and determine the technical documents to be processed and the non-technical documents to be processed;
[0044] Step S106: storing the non-technical document information to be processed and the technical document information to be processed in the bus MRO system;
[0045] Step S108: Generate an occasional inspection task list according to the non-technical document and electronic information to be processed, and store the occasional inspection task list in the passenger car MRO system.
[0046] Furthermore, in step S104, the process of identifying the documents to be processed and determining the technical documents to be processed and the non-technical documents to be processed is specifically implemented as follows in this embodiment:
[0047] Scan the documents to be processed to obtain the document information to be processed; process the document information to be processed through a pre-trained recognition model to determine the document type corresponding to the document to be processed, wherein the document type includes technical and non-technical categories, the technical category corresponds to the technical document information to be processed, and the non-technical category corresponds to the non-technical document information to be processed.
[0048] Furthermore, in step S106, the process of storing the to-be-processed non-technical documents and the to-be-processed technical documents to the bus MRO system is specifically implemented as follows in this embodiment:
[0049] Based on a preset first splitting rule, the non-technical document and electronic information to be processed is split to obtain a non-technical document and electronic information group; based on a preset second splitting rule, the technical document and electronic information to be processed is split to obtain a technical document and electronic information group; the non-technical document and electronic information group is stored in a first storage location of the bus MRO system; the technical document and electronic information group is stored in a second storage location of the bus MRO system.
[0050] Furthermore, in step S108, the process of generating a list of occasional inspection tasks according to the non-technical document and electronic information to be processed is specifically implemented as follows in this embodiment:
[0051] Based on a preset semantic recognition model, the non-technical document and electronic information to be processed is processed to obtain a list of occasional inspection tasks.
[0052] Furthermore, after step S108, it is also necessary to clarify the work order execution result. In this embodiment, the specific implementation method is as follows:
[0053] A work order is constructed according to the occasional inspection task list; and the execution of the work order is monitored within a preset time period, and the monitoring results are written into the bus MRO system.
[0054] Among them, railway passenger car maintenance technology is updated slowly, the management method is extensive and the concept is backward, and railway passenger car maintenance is also facing the transformation of information management. With the development of passenger car maintenance business, in order to meet the requirements of digital-driven enterprise development, it is necessary to adopt information technology to improve the process control of maintenance products, clarify and solidify the maintenance business management process, and improve the passenger car maintenance service system.
[0055] Existing documents are stored in paper format, which makes retrieval and query more troublesome. This embodiment implements refined information control on railway passenger car maintenance business, fully considers the unified maintenance mode, and uses digital means to manage railway passenger car maintenance business for railway passenger car maintenance special business.
[0056] In addition, this embodiment adopts the structured management of the departmental documents and electronic documents of the national railway passenger car, so that the technicians can associate the departmental documents and electronic information under the occasional inspection task list, and associate it with the specific vehicle model, vehicle number, and location information, and then take effect through the occasional inspection task list to generate a work order. The team executes according to the work order to achieve the relevant changes brought about by the closed-loop management business process of the departmental documents and electronic documents. The execution of the documents and electronic documents is monitored and closed in association with other information systems, such as QMS, KMIS, and after-sales.
[0057] It should be noted that this embodiment supports the management of departmental documents and telegrams. A file structure system can be established according to the year of release, etc., and departmental documents and telegrams can be archived and managed, and information such as departmental document and telegram numbers can be maintained. Custom conditions are supported for quick query, and online reading is supported. In addition, departmental documents and telegrams are associated with processes. When creating a process, it supports referencing information such as departmental document and telegram numbers to establish an association between processes and departmental documents and telegrams, so that the corresponding process content can be queried based on departmental documents and telegrams. Finally, work order tracing is based on departmental documents and telegrams. The system supports querying work order data based on departmental documents and telegrams, and can intuitively view the execution status and completion status of work orders.
[0058] Specifically, in step S102, the document structured management of the Ministry of Railway Passenger Car Department is implemented. The Passenger Car Division receives the Ministry of Railway Department documents issued by the China Railway Corporation. In step S104, the scanning results of the Ministry of Railway Department documents are identified through the pre-trained recognition model. In step S106, the recognition results are imported into the MRO system for archiving management, which is convenient for the subsequent maintenance of the basic information of the Ministry of Railway Department documents and the establishment of the structured documents of the Ministry of Railway Department documents. In step S108, the documents that do not involve technical processing are not processed in the MRO system. For the documents that involve technical processing, the occasional inspection task list is established in the MRO to associate the Ministry of Railway Department documents. Specifically, it can be realized through the semantic recognition model, and the occasional task list is packaged and planned to generate the unissued task plan, and the work order is issued according to the maintenance plan within the preset period. After accepting the work order, the branch executes it according to the passenger car production business blueprint, generates the material kanban data, and finally confirms the execution of the work order in the MRO system to trigger the closing technical notification.
[0059] Corresponding to the above method embodiment, the present application also provides an embodiment of a document management device based on a bus MRO system, Figure 2 FIG. 1 shows a schematic diagram of the structure of a document management device based on a bus MRO system provided by an embodiment of the present application. Figure 2 As shown, the device comprises:
[0060] The receiving module 202 is configured to receive documents to be processed;
[0061] The identification module 204 is configured to identify the documents to be processed, and determine the technical documents to be processed and the non-technical documents to be processed;
[0062] The storage module 206 is configured to store the to-be-processed non-technical document and electronic information and the to-be-processed technical document and electronic information in the bus MRO system;
[0063] The occasional inspection module 208 is configured to generate an occasional inspection task list according to the non-technical document and electronic information to be processed, and store the occasional inspection task list in the passenger car MRO system.
[0064] In an optional embodiment, the identification module 204 is further configured to:
[0065] Scan the documents to be processed to obtain the document information to be processed; process the document information to be processed through a pre-trained recognition model to determine the document type corresponding to the document to be processed, wherein the document type includes technical and non-technical categories, the technical category corresponds to the technical document information to be processed, and the non-technical category corresponds to the non-technical document information to be processed.
[0066] In an optional embodiment, the storage module 206 is further configured to:
[0067] Based on a preset first splitting rule, split the non-technical document and electronic information to be processed to obtain a non-technical document and electronic information group;
[0068] Splitting the to-be-processed technical document and electronic information based on a preset second splitting rule to obtain a technical document and electronic information group;
[0069] Storing the non-technical text and electronic information group in a first storage location of the passenger car MRO system;
[0070] The technical text and electronic information group is stored in a second storage location of the passenger car MRO system.
[0071] In an optional embodiment, the occasional detection module 208 is further configured to:
[0072] Based on a preset semantic recognition model, the non-technical document and electronic information to be processed is processed to obtain a list of occasional inspection tasks.
[0073] In an optional embodiment, the document management device based on the passenger car MRO system further includes:
[0074] The work order module is configured to construct a work order according to the occasional inspection task list; monitor the execution of the work order within a preset time period, and write the monitoring results into the bus MRO system.
[0075] The document management device based on the passenger car MRO system provided by the present application receives documents to be processed; identifies the documents to be processed, determines the technical document information to be processed and the non-technical document information to be processed; stores the non-technical document information to be processed and the technical document information to be processed in the passenger car MRO system; generates an occasional inspection task list based on the non-technical document information to be processed, and stores the occasional inspection task list in the passenger car MRO system. Establish a file structure system, archive and manage department documents and department documents, maintain department document and department document numbers and other information, and ensure that the railway passenger car maintenance feature business can be managed by digital means.
[0076] The above is a schematic scheme of a document and electronic management device based on a bus MRO system of this embodiment. It should be noted that the technical scheme of the document and electronic management device based on the bus MRO system and the technical scheme of the document and electronic management method based on the bus MRO system belong to the same concept. For details not described in detail in the technical scheme of the document and electronic management device based on the bus MRO system, please refer to the description of the technical scheme of the document and electronic management method based on the bus MRO system. In addition, each component in the device embodiment should be understood as a functional module that must be established to implement each step of the program flow or each step of the method, and each functional module is not an actual functional division or separation definition. The device claim defined by such a group of functional modules should be understood as a functional module architecture that mainly implements the solution through the computer program recorded in the specification, and should not be understood as a physical device that mainly implements the solution through hardware.
[0077] Figure 3 The block diagram of a computing device 300 provided according to an embodiment of the present application is shown. The components of the computing device 300 include but are not limited to a memory 310 and a processor 320. The processor 320 is connected to the memory 310 via a bus 330, and the database 350 is used to store data.
[0078] The computing device 300 also includes an access device 340 that enables the computing device 300 to communicate via one or more networks 360. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 340 may include one or more of any type of network interface (e.g., a network interface card (NIC)) whether wired or wireless, such as an IEEE 802.11 wireless local area network (WLAN) wireless interface, a World Wide Interoperability for Microwave Access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like.
[0079] In one embodiment of the present application, the above components of the computing device 300 and Figure 3 Other components not shown in the figure may also be connected to each other, for example, via a bus. It should be understood that Figure 3 The computing device structure block diagram shown is only for the purpose of illustration, and is not intended to limit the scope of the present application. Those skilled in the art may add or replace other components as needed.
[0080] The computing device 300 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smart phone), a wearable computing device (e.g., a smart watch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or PC. The computing device 300 may also be a mobile or stationary server.
[0081] The processor 320 is used to execute computer executable instructions for each step of the document and electronic management method based on the bus MRO system.
[0082] The above is a schematic scheme of a computing device of this embodiment. It should be noted that the technical scheme of the computing device and the technical scheme of the document management method based on the bus MRO system are of the same concept, and the details not described in detail in the technical scheme of the computing device can be found in the description of the technical scheme of the document management method based on the bus MRO system.
[0083] An embodiment of the present application further provides a computer-readable storage medium storing computer instructions, which, when executed by a processor, are used to execute the steps of the document and electronic management method based on the bus MRO system.
[0084] The above is a schematic scheme of a computer-readable storage medium of this embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the document management method based on the bus MRO system are of the same concept, and the details not described in detail in the technical scheme of the storage medium can be found in the description of the technical scheme of the document management method based on the bus MRO system.
[0085] An embodiment of the present application further provides a chip storing a computer program, which implements the steps of the document and electronic management method based on the bus MRO system when executed by the chip.
[0086] The above describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0087] The computer instructions include computer program codes, which may be in source code form, object code form, executable files or some intermediate forms, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc. It should be noted that the content contained in the computer-readable medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electric carrier signals and telecommunication signals.
[0088] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.
[0089] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0090] The preferred embodiments of the present application disclosed above are only used to help explain the present application. The optional embodiments do not describe all the details in detail, nor do they limit the invention to the specific implementation methods described. Obviously, many modifications and changes can be made according to the content of the present application. The present application selects and specifically describes these embodiments in order to better explain the principles and practical applications of the present application, so that those skilled in the art can understand and use the present application well. The present application is only limited by the claims and their full scope and equivalents.
Claims
1. A document management method based on a passenger car MRO system, characterized in that: include: Receive documents to be processed; Identify the documents to be processed, and determine the technical documents and non-technical documents to be processed; Storing the non-technical document information to be processed and the technical document information to be processed in the bus MRO system; Generate an occasional inspection task list based on the non-technical document and electronic information to be processed, and store the occasional inspection task list in the passenger car MRO system.
2. The method according to claim 1, characterized in that The step of identifying the documents to be processed and determining the technical documents and information to be processed and the non-technical documents and information to be processed includes: Scan the document to be processed to obtain the document information to be processed; The document information to be processed is processed by a pre-trained recognition model to determine the document type corresponding to the document to be processed, wherein the document type includes technical and non-technical types, the technical type corresponds to the technical document information to be processed, and the non-technical type corresponds to the non-technical document information to be processed.
3. The method according to claim 1, characterized in that The storing of the to-be-processed non-technical documents and the to-be-processed technical documents in the bus MRO system includes: Based on a preset first splitting rule, split the non-technical document and electronic information to be processed to obtain a non-technical document and electronic information group; Based on a preset second splitting rule, split the to-be-processed technical document and electronic information to obtain a technical document and electronic information group; Storing the non-technical text and electronic information group in a first storage location of the bus MRO system; The technical text and electronic information group is stored in a second storage location of the passenger car MRO system.
4. The method according to claim 1, characterized in that: The generating of the occasional inspection task list according to the non-technical document and electronic information to be processed includes: Based on a preset semantic recognition model, the non-technical document and electronic information to be processed is processed to obtain a list of occasional inspection tasks.
5. The method according to claim 1, characterized in that: After storing the occasional inspection task list in the bus MRO system, the method further includes: Constructing a work order based on the occasional inspection task list; The execution of the work order is monitored within a preset time period, and the monitoring results are written into the passenger car MRO system.
6. A document management device based on a passenger car MRO system, characterized in that: include: A receiving module, configured to receive documents to be processed; An identification module is configured to identify the documents to be processed, and determine the technical documents to be processed and the non-technical documents to be processed; A storage module, configured to store the non-technical document and electronic information to be processed and the technical document and electronic information to be processed in a bus MRO system; The occasional inspection module is configured to generate an occasional inspection task list according to the non-technical document and electronic information to be processed, and store the occasional inspection task list in the passenger car MRO system.
7. A computing device, characterized in that include: Memory and processor; The memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement the steps of the document management method based on the passenger car MRO system as described in any one of claims 1 to 5.
8. A computer-readable storage medium storing computer instructions, characterized in that: When the instruction is executed by the processor, the steps of the document management method based on the passenger car MRO system as described in any one of claims 1 to 5 are implemented.