Scene-oriented rail transit operation business process standardization design method

Abstract

The invention discloses a scene-oriented rail transit operation business process standardization design method, and relates to the technical field of urban rail transit standard digital transformation, and the method comprises the steps: carrying out the classification and grading processing of an urban rail transit standard file and an urban rail transit operation standard, and obtaining machine readable standard data; based on the service architecture, performing service splitting processing on the machine readable standard data to obtain professional data containing a multi-level interface; according to the professional data, constructing a scene-based operation knowledge graph; carrying out secondary disassembly and recombination processing on the scene-based operation knowledge graph to obtain minimum scene unit data; and performing systematization processing on the minimum scene unit data to obtain a standardized operation business process. According to the invention, the operation management business process is standardized, so that the operation efficiency and the operation safety are improved.

Description

Technical Field

[0001] The present application relates to the technical field of digital transformation of urban rail transit standards, and in particular to a scenario-oriented standardization design method for rail transit operation business processes. Background Art

[0002] With the deep integration of advanced digital technologies such as the internet, the Internet of Things, big data, and cloud computing, urban rail transit systems are accelerating their intelligent transformation, gradually forming a smart subway model that integrates smart services, smart operations and maintenance, and smart construction. This trend not only improves the overall operational efficiency of rail transit systems but also brings new opportunities and challenges to the digitalization of industry standards. Globally, the digitalization of standards has become a key development direction in the standardization field. The relevant standardization development guidelines clearly call for the promotion of machine-readable and open-source standards, realizing the digitalization, networking, and intelligent upgrading of standardization work.

[0003] Despite continuous improvements in rail transit system construction and a growing capability to control operational risks, numerous problems persist in daily management. First, while grassroots rail transit staff possess high professional qualifications, knowledge base, and physical fitness requirements, some employees, lacking safety awareness or professional ethics, are prone to oversight during routine safety inspections, leading to minor safety hazards being overlooked. Second, some employees fail to update their professional knowledge promptly, preventing them from quickly identifying solutions when problems arise. This delays the optimal time to address them and allows minor issues to escalate into major problems. Furthermore, most hidden risks stem from negligence and lax management. Due to incomplete management systems or lax implementation of technical standards, routine safety inspections and protective measures are often oversighted, or even perfunctory. This leads to hidden risks remaining undetected, potentially leading to even greater safety hazards.

[0004] In view of the problems of complex processes and non-standard operations in the operation and management of urban rail transit, there is an urgent need to achieve process reconstruction and standardized management through technical means. Summary of the Invention

[0005] The purpose of this application is to provide a scenario-oriented rail transit operation business process standardization design method, which can standardize the operation management business process, thereby improving operational efficiency and safety.

[0006] To achieve the above objectives, this application provides the following solutions:

[0007] First, this application provides a scenario-oriented standardized design method for rail transit operation business processes, including:

[0008] The urban rail transit machine-readable standard model classifies and grades the acquired urban rail transit standard documents and urban rail transit operation standards to obtain machine-readable standard data;

[0009] The scenario operation management shell performs business splitting processing on the machine-readable standard data based on the preset business architecture to obtain professional data containing multi-level interfaces;

[0010] The scenario-based operation knowledge graph model constructs a scenario-based operation knowledge graph based on the professional data;

[0011] The scenario operation standard data information structure model performs secondary disassembly and reorganization processing on the scenario operation knowledge graph to obtain the minimum scenario unit data;

[0012] The flexible digital business process editing system systematically processes the minimum scene unit data to obtain standardized operational business processes.

[0013] According to the specific embodiments provided in this application, this application discloses the following technical effects:

[0014] The present application provides a scenario-oriented rail transit operation business process standardization design method. The present application classifies and hierarchically processes urban rail transit operation standards and standard documents through a machine-readable standard model for urban rail transit, which can convert traditional operation processes and operation standards into machine-readable standard data, realize the standardization of data and processes in urban rail transit operation management, and improve the consistency and predictability of management. Moreover, through the scenario operation management shell based on the preset business architecture, the machine-readable standard data is split into business, and professional data containing multi-level interfaces is obtained, which can help to achieve seamless data connection and collaboration between stations, regions, lines and different levels of the road network, thereby achieving more efficient cross-system and cross-departmental cooperation and improving operational efficiency. In addition, after the scenario operation knowledge graph model constructs the scenario operation knowledge graph, it can more accurately describe and manage various operation scenarios of rail transit, and disassemble and reorganize the scenario operation knowledge graph through the scenario operation standard data information structure model, which can extract the smallest scenario unit data from the overall business process, and can more accurately reflect the execution requirements and standards of each detailed step, helping to reduce complexity and make the entire business process more concise and efficient. It can be seen that the standardized design of rail transit operation business processes can help improve operational efficiency and reduce errors and uncertainties caused by human intervention, thereby making urban rail transit operation management safer. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments. 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 creative work.

[0016] Figure 1 This is an application environment diagram of a scenario-oriented rail transit operation business process standardization design method in one embodiment of the present application;

[0017] Figure 2 A flowchart of a scenario-oriented rail transit operation business process standardization design method provided in one embodiment of the present application;

[0018] Figure 3 A schematic diagram of the functional modules of a scenario-oriented rail transit operation business process standardization design system provided in one embodiment of the present application.

[0019] Figure 4 A schematic diagram of the functional modules of a machine-readable standard model of urban rail transit provided in one embodiment of the present application. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0021] In order to make the above-mentioned purposes, features and advantages of the present application more obvious and easy to understand, the present application is further described in detail below with reference to the accompanying drawings and specific implementation methods.

[0022] The scenario-oriented rail transit operation business process standardization design method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown. Among them, the terminal 102 communicates with the server 104 through the network. The data storage system can store the data that the server 104 needs to process. The data storage system can be set up separately, integrated on the server 104, or placed on the cloud or other servers. The terminal 102 can send the urban rail transit standard files and operating standards to be processed to the server 104. After the server 104 receives the urban rail transit standard files and operating standards, the server 104 classifies and grades the urban rail transit standard files and operating standards to obtain machine-readable standard data; based on the preset business architecture, the machine-readable standard data is subjected to business splitting processing to obtain professional data containing multi-level interfaces; based on the professional data, a scenario-based operation knowledge graph is constructed; the scenario-based operation knowledge graph is subjected to secondary disassembly and reorganization processing to obtain the minimum scenario unit data; the minimum scenario unit data is systematically processed to obtain a standardized operation business process. The server 104 can feedback the obtained standardized operation business process to the terminal 102. In addition, in some embodiments, the standardization design method for rail transit operation business processes can also be implemented independently by the server 104 or the terminal 102. For example, the terminal 102 can directly process the standard files and operating standards to be processed, or the server 104 can obtain the standard files and operating standards to be processed from the data storage system and process them.

[0023] The terminal 102 may be, but is not limited to, various desktop computers, laptop computers, and IoT devices. The server 104 may be implemented as an independent server or a server cluster consisting of multiple servers, or a cloud server.

[0024] In an exemplary embodiment, Figure 2 As shown, a scenario-oriented rail transit operation business process standardization design method is provided. The method is executed by a computer device, specifically a computer device such as a terminal or a server, or a terminal and a server. In the embodiment of the present application, the method is applied to Figure 1 The server 104 in the example is used as an example to illustrate the process, including the following steps 201 to 205.

[0025] In step 201 , the urban rail transit machine-readable standard model classifies and grades the acquired urban rail transit standard documents and urban rail transit operation standards to obtain machine-readable standard data.

[0026] In step 202 , the scenario operation management shell performs business splitting processing on the machine-readable standard data based on the preset business architecture to obtain professional data containing multi-level interfaces.

[0027] Step 203: The scenario-based job knowledge graph model constructs a scenario-based job knowledge graph based on professional data.

[0028] In step 204, the scenario operation standard data information structure model performs secondary disassembly and reorganization processing on the scenario operation knowledge graph to obtain the minimum scenario unit data.

[0029] In step 205 , the flexible digital business process editing system systematically processes the minimum scene unit data to obtain a standardized operational business process.

[0030] By implementing steps 201 to 205 above, and by classifying and grading urban rail transit operating standards and standard documents, traditional operating procedures and standards can be converted into machine-readable standard data. This standardizes data and processes in urban rail transit operations management, improving consistency and predictability. Furthermore, by segmenting machine-readable standard data into business units based on a pre-set business architecture, specialized data containing multi-level interfaces is generated. This facilitates seamless data integration and collaboration across different levels of stations, regions, lines, and the network, enabling more efficient cross-system and cross-departmental collaboration and improving operational efficiency. Furthermore, constructing a scenario-based operational knowledge graph allows for more precise description and management of various rail transit operational scenarios. By decomposing and reorganizing the scenario-based operational knowledge graph, the smallest scenario unit data can be extracted from the overall business process, more accurately reflecting the execution requirements and standards for each detailed step, helping to reduce complexity and making the overall business process more streamlined and efficient. Thus, the standardized design of rail transit operational business processes helps improve operational efficiency and reduce the errors and uncertainties caused by manual intervention, thereby making urban rail transit operations management safer.

[0031] Furthermore, in step 202, the business architecture includes business segments, business levels, and scenario operation constraints. Business segments include passenger transport and driving operations. Business levels include station level, region level, route level, and road network level. Scenario operation constraints are constraints between stations, regions, routes, and road networks. Based on this, the scenario operation management shell performs business decomposition processing on machine-readable standard data based on the preset business architecture, obtaining professional data with multi-level interfaces, specifically including:

[0032] In step 221, based on the business segments, the machine-readable standard data is split into business segments to obtain different scenario operations.

[0033] Step 2022: Based on the scene operation constraint relationship, the scene operation is standardized to obtain an initial scene unit; there are multiple initial scene units.

[0034] Step 2023: Classify each first scene unit in the scene operation into the corresponding business level, and build the association relationship and data interface between different business levels to obtain professional data containing multi-level interfaces.

[0035] Furthermore, in step 203, the scenario-based operation knowledge graph model constructs a scenario-based operation knowledge graph based on professional data, specifically including:

[0036] In step 2031, a deep learning model is used to perform entity extraction and entity relationship extraction operations on the professional data to obtain entity data and entity relationship data; wherein the deep learning model is a Bert-CRF model.

[0037] In step 2032, a data modeling operation is performed on the entity data and entity relationship data using a modeling tool, wherein the modeling tool is a Neo4j graph database, to obtain a scenario-based operation knowledge graph.

[0038] Furthermore, the attributes corresponding to the minimum scene unit data in step 204 include operation time, position, operation content, operation location, operation items, on-site execution standards and superior files.

[0039] Furthermore, in step 205, the flexible digital business process editing system systematically processes the minimum scene unit data to obtain a standardized operational business process, which specifically includes:

[0040] The minimum scene unit data is imported into a data form center and a standard management center to obtain form data and corresponding standard files.

[0041] Based on the process template center, the form data and the corresponding standard files are processed to obtain a standardized operational business process.

[0042] Furthermore, before systematically processing the minimum scene unit data to obtain standardized operational business process steps, it also includes: supplementing and updating professional data based on the minimum scene unit data to obtain updated professional data.

[0043] In another exemplary embodiment, Figure 3 As shown, a systematic functional description is provided for the urban rail transit machine-readable standard model, scenario operation management shell, scenario operation knowledge graph model, scenario operation standard data information structure model and flexible digital business process editing system.

[0044] (1) Machine-readable standard model for urban rail transit

[0045] In the intelligent operation and management of urban rail transit, standards can be divided into various types, including but not limited to standards used by people, standards used by machines, and standards for human-machine collaboration. However, there are obvious differences in the way people and machines interpret the content of standards. To address this issue, this application proposes a machine-readable standard model for urban rail transit, such as Figure 4 Each level of the model is further built on the technology of the previous level, which can carefully evaluate the standard machine interoperability capability level, thus laying a solid foundation for the standardization of smart subway passenger management processes.

[0046] The urban rail transit machine-readable standard model is used to classify and grade urban rail transit standard documents and urban rail transit operation standards to obtain machine-readable standard data.

[0047] (2) Scene operation management shell

[0048] The scene operation management shell provided in this application is an innovative tool for urban rail transit operation management. It is a digital representation of a specific operation scene. It provides a standardized and systematic framework that can unify the management and standardization of all information and functions in the operation scene, and is used to handle various tasks and decisions in operations. The overall value of the business, functions, information and assets of the operation scene is reflected through digital models and languages, so that the various components of the operation scene can be connected and communicated with each other. The scene operation management shell is mainly composed of a "scene navigation directory" and a "scene control center" as well as a series of business sub-models.

[0049] The scenario-based operation management shell establishes a dynamic integration mechanism between the group company's standard data and station scenario-based operations. By adjusting and optimizing the interaction and data exchange between various business layers in real time, it ensures the accuracy and timeliness of information, thereby improving overall operational efficiency and reliability. The scenario-based operation management shell can be built and expanded in a highly modular manner, mapping the operation scenario modules of specific station operations with the group company's business layers to achieve information interoperability and communication. This modular and standardized approach improves operational management efficiency and enhances the system's flexibility and scalability.

[0050] The scenario operation management shell is used to split the standard documents and operation standards of urban rail transit in a more detailed manner, dividing them into different business segments (such as passenger business, driving business, etc.) and business levels (such as station level, regional level, line level, road network level), thereby forming a professional data system for urban rail transit operation business. Specifically, based on the business segments, the machine-readable standard data is split into business segments to obtain different scenario operations; different scenario operations are standardized based on the scenario operation constraint relationship (i.e., the constraint relationship between stations, regions, lines and road networks), and standardized into specific scenario units (i.e., initial scenario units), and each initial scenario unit in the scenario operation is classified into the corresponding business level, and the association relationship between the initial scenario units at different business levels in the same scenario operation is constructed, forming a data interface between station-level business and regional-level business, regional-level business and line-level business, and line-level and road network-level business, completing data interaction and transmission.

[0051] (3) Scenario-based operation knowledge graph model

[0052] The scenario-based operation knowledge graph model receives specialized data from the scenario-based operation management shell and uses an event knowledge entity extraction method based on the Bert-CRF model to extract and determine entity relationships. After determining these relationships, a scenario-based knowledge graph for station passenger operations is constructed using Python using the Neo4j graph database. The graph model is then output to visualize the scenario-based knowledge graph. The resulting topological structure of nodes and relationships covers key nodes such as location, position, and operation content, as well as complex relationships such as belonging, involving, and corresponding. The entity and relationship types are shown in Table 1. The scenario-based operation knowledge graph visualizes the correspondence between information such as the staff and work locations involved in specific station scenario operations and station-level business operations (i.e., the relationships between entities). Table 2 shows these relationships, making it easier to observe whether each position completes its work according to standards and establishing a connection between scenario-based operations, initial scenario units, and the business hierarchy.

[0053] Table 1. Entity and relationship types

[0054]

[0055] Table 2. Relationships between entities

[0056] entity relation (Location, Position) Job Positions (Assignment content, location) Locations involved (Homework content, items) Involved items (Job content, position) Positions involved (Work content, station-level business) Corresponding business (Station-level business, regional-level business) Belong (regional services, line services) Belong (Line-level services, network-level services) Belong

[0057] (4) Standard data information structure model for scenario operations

[0058] The scenario-based operation standard data information structure model is an abstract model proposed in this application to address the information and digital management needs of urban rail transit operations. This model aims to standardize and optimize complex operational standards and process management. It defines rules for disassembling, linking, and reassembling the smallest scenario units, ensuring seamless exchange and sharing of data and business processes across stations, regions, lines, and networks, thereby supporting the interoperability and maintainability of the entire urban rail transit operations management network.

[0059] The scenario operation standard data information structure model is used to perform secondary decomposition of the scenario operation knowledge graph to form the smallest scenario unit that can be directly imported into the flexible digital business process editing system driven by typical scenarios. The attributes corresponding to the minimum scenario unit data include operation time, position, operation content, operation location, operation items, on-site execution standards, and superior documents. At the same time, the minimum scenario unit data is associated and reorganized according to the rules established by the scenario operation standard data information structure model, and specific functions are implemented in different applications in the flexible digital business process editing system driven by typical scenarios. At the same time, the scenario operation standard data information structure model feeds back the data after secondary decomposition and reorganization to the scenario navigation directory and scenario control center in the scenario operation management shell for data supplementation and update, so that management personnel can view and manage it.

[0060] (5) Flexible digital business process editing system

[0061] The flexible digital business process editing system, driven by typical scenarios, can read data from the scenario-based job management shell and the standard data information structure model for scenario-based jobs (such as job items, job sequences, job objects, job locations, job tools, and compliance requirements). Through interactive editing operations like dragging and dropping, and clicking, it recombines various elements to create scalable digital business scenarios. This flexible digital business process editing system, driven by typical scenarios, primarily consists of four centers: a data form center, a standard management center, a process template center, and a job task center.

[0062] A flexible digital business process editing system driven by typical scenarios is used to receive professional data (i.e., minimum scenario unit data) transmitted by the standard data information structure model of scenario operations, import it into the data form center and the standard management center, and obtain standardized operational business processes.

[0063] Among them, the above-mentioned data form center converts the smallest scenario unit deconstructed from the business scenario into form elements according to the standard data information structure model of the scenario operation. Add corresponding form elements according to different task requirements. In different tasks, there will be different form requirements. In order to meet the diverse form requirements, the background allows you to design the form format by yourself, add text content, and define the required feedback content. You can require text feedback or take a photo and upload (there may be video requirements). After completing the form design, when creating a task, you can select the created form as the form to fill in. At the same time, the form center can retrieve fault reporting information based on the title, submitter, creation time, and processing results. You can view the picture information of the fault report, modify the status of the fault report, delete the fault report information, and export the fault report information.

[0064] The Standards Management Center allows users to view standard clauses, associated processes (corresponding to the work instruction), upgrade, modify (modify the work instruction's title, file name, type, description, standard version, and notes), delete, and add new standard documents. The Standards Management Center also features a reverse workflow feature. By clicking View Standard Clauses, users can search for entered standard clauses by title and type. Users can also click Add to add new standard clauses to the standard document, which will be synchronized with the standard clauses.

[0065] The core function of the Process Template Center is to create workflow templates. By linking form data designed in the Data Form Center with standard files provided by the Standard Management Center, backend users can create task templates, edit reference standards (forms, images, videos), pre-submitted content (forms, images, videos), and search for complete employee workflows. Backend administrators can create daily workflows as templates and save them in the system. This allows on-duty station managers to directly select these templates when assigning daily tasks, improving workflow efficiency. The process engine controls the overall workflow framework and manages the transitions between tasks. The process engine annotates parallel or serial relationships between tasks during creation. During execution, process control is based on these annotations. By editing process templates, workflows are generated, allowing on-duty station managers to quickly deploy the same workflows. Backend administrators use a visual process designer to edit workflows, which are then deployed once completed.

[0066] The Process Template Center assigns specific tasks to operators based on process templates. Published tasks are transferred to the Operation Task Center. Operators can view specific tasks in the Task Center on handheld devices and execute them according to associated digital forms and standards. Back-end administrators can view all task execution and submission records in the Operation Task Center and cancel tasks. Past task submission forms can be viewed in the Operation Task Center to confirm task completion. By digitizing paper forms, search efficiency is improved. Task execution and submission records are tracked and recorded in real time, ensuring transparency and traceability of the operation process.

[0067] For completed tasks, you can click "Details" to view the submitted task form. For unfinished tasks, you can click "Cancel" and enter the reason for deletion to delete the task. The task completion status is returned to the data form center in the form of a form for feedback and subsequent review.

[0068] In summary, the beneficial effects of this application are mainly reflected in the following aspects:

[0069] (1) Standardized management: Through the scenario operation standard data information structure model, the standardization of data and processes in urban rail transit operation management is achieved, and the consistency and predictability of management are improved.

[0070] (2) Seamless exchange of data and business processes: This ensures seamless exchange and sharing of data and business processes between stations, regions, lines, and road networks, enhancing interoperability.

[0071] (3) Improve efficiency: By disassembling, associating, and reorganizing the smallest scene units, the management process is simplified and the efficiency of operation management is improved.

[0072] (4) Enhanced interoperability: Optimized the integration between different levels and improved the interoperability of different levels of urban rail transit operation and management.

[0073] (5) Flexibility and scalability: The system can flexibly adjust and reorganize different scenario units according to actual application requirements and quickly respond to business needs and environmental changes.

[0074] (6) Reduce errors and improve stability: Standardization reduces errors in operations and improves the stability and maintainability of the system.

[0075] (7) Data integration: It realizes the connection of specific operations at different business levels and improves the efficient integration of data and processes.

[0076] (8) Continuous optimization: Through regular evaluation and user feedback, the system can be continuously optimized to maintain its advanced nature and competitiveness.

[0077] (9) Promote digital transformation: As a management idea, this application promotes the digital transformation and intelligent development of urban rail transit operation and management business, laying the foundation for future technological progress and business innovation.

[0078] (10) Adaptability to diverse needs: The flexibility of the scenario unit enables the system to adapt to diverse needs and application scenarios, enhancing the practicality and breadth of the system.

[0079] The present application also provides an application scenario, which applies the above-mentioned scenario-oriented rail transit operation business process standardization design method. Specifically: the rail transit operation business process standardization design method provided in this embodiment can be applied in the rail transit operation management scenario. The rail transit operation management scenario includes a standard document processing link and an operation business process display link; the standard document processing link is used to process urban rail transit standard documents and operating standards to obtain standardized operation business processes; the operation business process display link is used to display standardized operation business processes. The rail transit operation business process standardization design method provided in this embodiment belongs to the standard document processing link.

[0080] In an exemplary embodiment, a computer device is provided, which may be a server or a terminal. The computer device includes a processor, a memory, an input / output interface (I / O) and a communication interface. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface is connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store and process data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a scenario-oriented standardization design method for rail transit operation business processes is implemented.

[0081] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0082] Those skilled in the art will understand that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM may be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0083] The databases involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processors involved in the various embodiments provided herein may include, but are not limited to, general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic units, data processing logic units based on quantum computing, and the like.

[0084] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, 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.

[0085] This document uses specific examples to illustrate the principles and implementation methods of this application. The description of the above examples is only intended to help understand the method and core concept of this application. At the same time, for those skilled in the art, based on the concept of this application, there may be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as limiting this application.

Claims

1. A scenario-oriented rail transit operation business process standardization design method, characterized by: The scenario-oriented rail transit operation business process design method includes: The urban rail transit machine-readable standard model classifies and grades the acquired urban rail transit standard documents and urban rail transit operation standards to obtain machine-readable standard data; The scenario operation management shell performs business splitting processing on the machine-readable standard data based on the preset business architecture to obtain professional data containing multi-level interfaces; The scenario-based operation knowledge graph model constructs a scenario-based operation knowledge graph based on the professional data; The scenario operation standard data information structure model performs secondary disassembly and reorganization processing on the scenario operation knowledge graph to obtain the minimum scenario unit data; The flexible digital business process editing system systematically processes the minimum scene unit data to obtain standardized operational business processes.

2. The scenario-oriented rail transit operation business process standardization design method according to claim 1 is characterized in that: The business architecture includes business segments, business levels, and scenario operation constraint relationships. The scenario operation management shell performs business splitting processing on the machine-readable standard data based on the preset business architecture to obtain professional data containing multi-level interfaces, specifically including: Based on the business segments, the machine-readable standard data is split into business segments to obtain different scenario operations; Based on the scene operation constraint relationship, the scene operation is standardized to obtain an initial scene unit; the initial scene unit is multiple; Each initial scenario unit in the scenario operation is classified into a corresponding business level, and association relationships and data interfaces between different business levels are constructed to obtain professional data containing multi-level interfaces.

3. The scenario-oriented rail transit operation business process standardization design method according to claim 2 is characterized in that: The business segments include passenger transport business and driving business; the business levels include station level, regional level, line level and road network level; the scenario operation constraint relationship is the constraint relationship between stations, regions, lines and road networks.

4. The scenario-oriented rail transit operation business process standardization design method according to claim 1 is characterized in that: The scenario-based operation knowledge graph model constructs a scenario-based operation knowledge graph based on the professional data, specifically including: Performing entity extraction and entity relationship extraction operations on the professional data using a deep learning model to obtain entity data and entity relationship data; A modeling tool is used to perform data modeling operations on the entity data and the entity relationship data to obtain a scenario-based operation knowledge graph.

5. The scenario-oriented rail transit operation business process standardization design method according to claim 4 is characterized in that: The deep learning model is the Bert-CRF model, and the modeling tool is the Neo4j graph database.

6. The scenario-oriented rail transit operation business process standardization design method according to claim 1 is characterized in that: The attributes corresponding to the minimum scene unit data include operation time, position, operation content, operation location, operation items, on-site execution standards and superior documents.

7. The scenario-oriented rail transit operation business process standardization design method according to claim 1 is characterized in that: The flexible digital business process editing system includes a data form center, a standard management center, and a process template center. The flexible digital business process editing system systematically processes the minimum scenario unit data to obtain a standardized operational business process, specifically including: Importing the minimum scene unit data into the data form center and the standard management center to obtain form data and corresponding standard files; Based on the process template center, the form data and the corresponding standard files are processed to obtain a standardized operational business process.

8. The scenario-oriented rail transit operation business process standardization design method according to claim 1 is characterized in that: For example, before the flexible digital business process editing system systematically processes the minimum scene unit data to obtain standardized operational business process steps, it also includes: the scene operation standard data information structure model supplements and updates the professional data according to the minimum scene unit data to obtain updated professional data.

Images