A file-level design-data-level collaborative railway engineering collaborative design method

Abstract

The application discloses a railway engineering collaborative design method of file-level design-data-level cooperation, comprising the following steps: planning and constructing a technical framework, establishing a top-level guidance scheme for collaborative design covering the whole cycle and all specialties; unifying entity definition, attribute description, correlation, data exchange content and format of railway engineering data of all specialties, forming a machine-readable railway engineering data mode, synchronizing the railway engineering data mode to all specialty design software and a railway engineering collaborative design platform, wherein the railway engineering collaborative design platform comprises a client-side collaborative workstation and a server-side data hub; collaboratively modifying the existing specialty design software, setting a standardized input interface and an output interface for the railway engineering collaborative design platform; developing data cooperation adaptation middleware, carrying out collaborative design test verification, verifying the effectiveness of collaborative work through a typical railway engineering project, and driving continuous optimization of the system. The method significantly reduces the development cost and popularization difficulty.

Description

Technical Field

[0001] This invention belongs to the field of collaborative design technology for railway engineering, specifically relating to a collaborative design method for railway engineering that combines document-level design with data-level collaboration. Background Technology

[0002] Collaborative design technology is a key technology for the digital transformation of railway survey and design enterprises. Its core idea is to provide designers with a basic platform and tools for data interaction and sharing, aiming to improve work efficiency and design quality. Currently, collaborative design technology exhibits a "three-level leap": from file-level collaboration to component-level collaboration, and then to data-level collaboration. File-level collaboration consists of multiple linked models or drawings, requiring weak or no association between models. Component-level collaboration is based on a central model and is suitable for single-building design, section design of long linear projects, and work point design. Data-level collaboration breaks down the boundaries between traditional files and physical models, decomposing engineering design information into fine-grained attributes, parameters, and geometric data objects, uniformly stored in the underlying database. Relying on a single data source, it supports real-time concurrent access, parameter transfer, association updates, and conflict detection across multiple disciplines and levels, and is suitable for the entire lifecycle construction of long linear projects with complex interfaces, high professional coupling, and massive data volumes.

[0003] Railway engineering design involves multiple disciplines, both before and after the station, and the work of these disciplines is interdependent. Data versions are rapidly iterated and repeated. In response to these characteristics, domestic and foreign software vendors have developed a variety of collaborative design software products based on different technical approaches.

[0004] Well-known international collaborative design software includes ProjectWise from Bentley Systems (USA), Vault and Autodesk Construction Cloud from Autodesk (USA), and ENOVIA from Dassault Systèmes (France). ProjectWise is a typical example of file-level collaboration, supporting cross-regional team collaboration through centralized management of project documents, data, and processes. Vault primarily focuses on component-level collaboration, achieving version control and collaborative design through deep integration with Autodesk's design tools. ENOVIA offers data-level collaboration, providing centralized data management through integrated plugins that connect deeply with CAD tools such as Dassault Systèmes CATIA and SOLIDWORKS. All of these software programs are commercial, highly versatile, and mature, widely used in international infrastructure construction. However, they are incompatible with the production organization methods, quality control models, and existing software technology systems of domestic railway survey and design enterprises, and adaptation is difficult. Furthermore, international software generally provides services based on public cloud platforms, posing a significant risk of data leakage when uploading core survey and design data.

[0005] Domestic mainstream collaborative design software can be divided into general-purpose architectural design software and industry-specific design software. General-purpose architectural design software includes platforms such as Gouli Technology BIMBase, Glodon BIM Design Collaboration Platform, HaoChen CAD Collaborative Design System, and Tianzheng Collaborative Design System. This type of software primarily targets the architectural design field, providing collaboration among architecture, structure, and MEP (Mechanical, Electrical, and Plumbing) professionals, but lacks railway-specific functions and cannot support collaborative design across multiple disciplines along the entire railway line. Industry-specific design software includes railway BIM collaborative design platforms developed by domestic railway design companies based on foreign commercial software. However, due to high secondary development costs, these platforms have not been widely adopted and are also subject to "bottleneck" risks. On the other hand, domestic railway design companies have persisted in independent research and development for many years, accumulating a large amount of software assets, such as line design software and track layout design systems. These software programs are highly efficient in design, drawing, and quantity calculation within a single discipline. However, due to the long-term independent evolution of various professional software, significant differences exist in architecture, databases, and interfaces, resulting in serious "data silos." Frequent cross-disciplinary data submissions, version conflicts, and other issues lead to a significant amount of time being spent on data verification, communication, and rework, hindering further improvements in design efficiency and output quality. Summary of the Invention

[0006] To address the problems existing in the prior art, this invention provides a collaborative design method for railway engineering based on file-level design and data-level collaboration. This method solves problems such as insufficient localization of foreign software, high secondary development costs, data security and product supply disruption risks, as well as the formation of "data silos" by domestically developed single-discipline software and difficulties in cross-discipline data collaboration.

[0007] To achieve the above objectives, the present invention adopts the following technical solution:

[0008] A collaborative design method for railway engineering, involving document-level design and data-level collaboration, includes the following steps:

[0009] S1 proposes a technical framework for collaborative design of railway engineering: planning and constructing a technical framework that includes compiling railway engineering data standards, developing a collaborative design platform for railway engineering, collaboratively transforming existing professional design software, developing data collaboration adaptation middleware, and conducting collaborative design testing and verification, and establishing a top-level guidance scheme for collaborative design covering the entire life cycle and all professions.

[0010] S2, Compile railway engineering data standards: unify the entity definitions, attribute descriptions, relationships, data exchange content and formats of railway engineering data across different disciplines, form a machine-readable railway engineering data model, and synchronize the railway engineering data model to the design software of each discipline and the railway engineering collaborative design platform, providing a unified semantic foundation for cross-discipline data-level collaboration;

[0011] S3, Develop a collaborative design platform for railway engineering: The collaborative design platform for railway engineering includes a client-side collaborative workbench and a server-side data hub. The client-side collaborative workbench provides a graphical collaborative design environment and a railway engineering data operation interface. The server-side data hub is responsible for the centralized storage, management and distribution of all engineering data, ensuring data security, consistency and high availability.

[0012] S4. To make existing professional design software more collaborative, standardized input and output interfaces are set up for the railway engineering collaborative design platform.

[0013] S5, Research and Development Data Collaboration Adaptation Middleware: The data collaboration adaptation middleware is used to present the collaborative design environment to the designers and automatically complete the parsing and extraction of the design result files, convert the extracted information into structured data objects and synchronize them to the railway engineering collaborative design platform. The design result files are obtained by the designers of each profession using existing professional design software for design modeling.

[0014] S6. Conduct collaborative design testing and verification, verify the effectiveness of collaborative design methods through typical railway engineering projects, and drive the continuous optimization of the entire system.

[0015] In the above method, step S2 includes:

[0016] 1) Needs survey and analysis: Conduct in-depth research on the design process, data interaction needs and existing data formats of various disciplines before and after the railway station construction. Analyze the results of the needs survey, clarify the scope and granularity of railway engineering data standards, and form a survey report and a list of interactive data.

[0017] 2) Definition of core entities: Based on the survey report and the interactive data list, the core entities in the entire life cycle of railway engineering are extracted to obtain a list of core entities, and each core entity is assigned a unique identifier;

[0018] 3) Attribute and Relationship Modeling: Define in detail the attributes of each core entity in the core entity list and the relationships between it and other core entities to obtain the logical data topology and attribute matrix, forming a logically rigorous entity relationship model;

[0019] 4) Data exchange format design: Determine the exchange format of the structured data objects, and use a platform-independent and easily parsed text format for exchange; at the same time, clarify the association method between unstructured data objects and structured data objects, and form a draft standard data exchange model and file association specifications;

[0020] 5) Expert Review and Revision: Organize senior experts in the industry, chief engineers of various specialties, and front-line designers to conduct multiple rounds of review on the draft standard exchange data model and document association specifications. If the multiple rounds of review fail, propose modification suggestions from the perspectives of business logic, technical feasibility, and ease of use, and return to step 3); if the multiple rounds of review pass, solidify the data standard and form a formal standard document;

[0021] 6) Release and version management: Release the official standard document and establish a standard version management mechanism; pre-embed the standard exchange data mode in the railway engineering collaborative design platform.

[0022] In step S3, the client collaborative workbench includes:

[0023] 1) Attribute View and Project Structure Tree:

[0024] A hierarchical tree structure is used to display the engineering breakdown structure of the entire project. Designers can quickly locate any engineering object through this engineering structure. After selecting an engineering entity, the attribute view dynamically displays all the attribute information of the engineering entity and supports editing and saving.

[0025] 2) Secondary development toolkit:

[0026] This toolkit provides standardized application programming interfaces and plugin development frameworks for use by various professional design software and data collaboration adaptation middleware. It encapsulates data synchronization modules, data topology construction modules, and version control modules, shielding the underlying data storage and communication details.

[0027] The data synchronization module is used for bidirectional data synchronization between the client and the server, including pushing local modifications to the server and pulling the latest data from the server to the local machine; it also receives the structured data object and performs local data merging and consistency verification; the data topology construction module is used to construct a real-time updated engineering data topology based on the entity association model, which intuitively displays the dependencies between various engineering entities; the version control module is used to establish a complete version history for each engineering entity, supporting version comparison, backtracking and merging operations.

[0028] The server-side data hub includes:

[0029] 1) Data storage center:

[0030] A hybrid storage architecture of structured and unstructured data objects is adopted, which centrally stores structured and unstructured data objects. The structured data objects refer to engineering entities, geometric attributes, relationships, and personnel organization information extracted from design deliverables. This information is modeled and stored based on the railway engineering data standard. The unstructured data objects refer to the original design deliverables. Each original design deliverable is assigned a globally unique identifier and associated with the corresponding structured engineering entity, supporting version management and traceability of design deliverables.

[0031] 2) Data synchronization service:

[0032] It provides an efficient and reliable data synchronization interface, supports concurrent access from multiple clients, data conflict detection and automatic merging mechanisms, and ensures the consistency and real-time performance of data in the collaborative design environment.

[0033] 3) File management service:

[0034] Unstructured files are stored and accessed in a unified manner, supporting file upload, download and preview, and are associated with corresponding engineering entities in structured data objects to form a complete engineering data asset system.

[0035] In step S4, the input interface is used to enable the design software to change from reading local data sources to accessing the railway engineering collaborative design platform based on API; the output interface is used to enable the design software to change from writing to local files to submitting design results to the railway engineering collaborative design platform based on API.

[0036] In step S5, the data collaboration and adaptation middleware includes:

[0037] (1) Design Environment Embedded Component: This component is responsible for presenting the design software environment of the client collaborative workbench in the user interface of the design software in the form of an embedded panel. When the designer starts the design software from the client collaborative workbench, this component reads the client collaborative workbench data, creates a project structure tree and attribute view, and loads the context information into the current design session. During the design process, the designer can create new project entities and add or modify attribute information through this component.

[0038] (2) Data Extraction Component: Responsible for parsing and extracting data from the design deliverables after the design is completed. When the designer completes the design and clicks the "Submit" button, the data extraction component is triggered and performs the following operations:

[0039] 1) Perform in-depth analysis of the current design deliverables, extract the engineering entities, geometric parameters, material properties, and correlation information based on the railway engineering data standard, and transform / parse them into fine-grained structured data objects that conform to the definition of the railway engineering data standard;

[0040] 2) Upload the design deliverables to the local cache directory specified in the client's collaborative workbench;

[0041] 3) Push the fine-grained structured data object obtained in step 1) to the client collaborative workbench through the secondary development toolkit;

[0042] 4) The client-side collaborative workbench merges the received fine-grained structured data objects, automatically handles versions and conflicts, and updates the data topology;

[0043] 5) After the designers confirm that everything is correct, they will perform the "Synchronize with Server" operation in the client-side collaborative workbench. At this time, all fine-grained structured data objects and unstructured data objects will be uploaded to the server for other team members to access synchronously.

[0044] Step S6 includes the following steps:

[0045] S61, Test Preparation:

[0046] Select a typical railway section that involves multiple disciplines and has complex interface relationships, and deploy the railway engineering data standard, railway engineering collaborative design platform and the modified design software for each discipline.

[0047] S62, Collaborative Design Applications:

[0048] Organize a team to conduct collaborative design for railway engineering during the construction drawing phase, including:

[0049] 1) Collaborative initialization and task distribution: The project administrator creates a project and configures initial resources in the railway engineering collaborative design platform; the overall project establishes an engineering structure tree based on the engineering decomposition structure and distributes task permissions to each professional section, thus completing the initialization of the data collaboration environment;

[0050] 2) Basic data release and initial design: The surveying / geology professionals submit the initial topographic map data of the project area to the railway engineering collaborative design platform; the track professionals pull the initial topographic map data and carry out track design. After completion, the initial track centerline without gaps and the corresponding drawings are released to the railway engineering collaborative design platform as a spatial reference benchmark for subsequent designs by various professions.

[0051] 3) Interface Boundary Definition and Iterative Survey: The station, bridge, tunnel, and roadbed specialties extract the centerline of the line without gaps, generate work points for their respective specialties through the "gap identification" and interface extraction mechanism, and send the interface boundary information back to the railway engineering collaborative design platform; the line specialties collect all gaps and publish horizontal and vertical profile drawings; subsequently, the surveying and geology specialties use the updated line and work point data to conduct detailed field surveys and submit detailed topographic and geological data to the railway engineering collaborative design platform; the station specialties receive the horizontal and vertical profile drawings and carry out station layout design;

[0052] 4) Parallel Detailed Design and Overall Integration: Each professional specialization receives the aforementioned topographic and geological data, as well as the data from adjacent interfaces, proposes boundary constraints such as land use scope and track expansion, and conducts parallel detailed design of its own construction drawings. Upon completion, the structured design results and drawing files are submitted simultaneously to the railway engineering collaborative design platform. Finally, the project as a whole uses the data verification tool of the railway engineering collaborative design platform to check the data quality of the entire line's design results, confirming the consistency of each professional interface and the integrity of the data, thus achieving a closed loop in the collaborative design business.

[0053] S63, Evaluate and compare the effects of the collaborative design;

[0054] S64. Based on the results of the collaborative design, a detailed test report is generated, summarizing the advantages and disadvantages of the collaborative design method for railway engineering. In response to the problems found in the collaborative design test, the railway engineering data standards, the functions of the railway engineering collaborative design platform, and the performance of the data collaboration adaptation middleware are iteratively optimized to form a mature solution that can be promoted on a large scale.

[0055] The evaluation includes the following indicators:

[0056] 1) Efficiency indicators: Statistically compare the average time spent on cross-disciplinary data collection, data verification, and design change notification before and after adopting the aforementioned collaborative design method for railway engineering;

[0057] 2) Quality indicators: Calculate the number of design errors, omissions, and gaps caused by conflicts in professional interfaces and inconsistent data versions, and compare them with historical project data;

[0058] 3) Satisfaction survey: Collect designers' subjective feelings about the ease of operation and practicality of the new system through questionnaires and interviews.

[0059] Compared with the prior art, the present invention has the following beneficial effects:

[0060] 1. The file-level design-data-level collaboration model in this invention preserves designers' operational habits with existing professional design software on the design side, maximizing the protection of the enterprise's software assets and personnel skills. On the collaboration side, through data standards and middleware technology, it achieves unified management and sharing of heterogeneous data, fundamentally breaking the limitations of "file-throwing" collaboration.

[0061] 2. The collaborative design method of this invention achieves independent control over the entire technology chain from data standards and data parsing to data storage, effectively avoiding the risks of foreign software supply disruptions and data export security risks.

[0062] 3. This invention, through a lightweight data collaboration adaptation middleware, endows existing professional design software with data-level collaboration capabilities in a "minimally invasive" manner, significantly reducing development costs and promotion difficulties, and providing designers with a seamless transition from individual operation to efficient collaboration.

[0063] 4. This invention achieves precise transmission and fine-grained version control of cross-disciplinary interface parameters by constructing a unified engineering data topology. Any data change can be automatically notified to all affected disciplines through correlation, greatly reducing communication costs and design rework, and changing the situation of version chaos and information lag in traditional collaboration processes. Attached Figure Description

[0064] Figure 1 This is a flowchart of the collaborative design method for railway engineering in this invention;

[0065] Figure 2 This is a flowchart of the compilation process for railway engineering data standards in this invention;

[0066] Figure 3 This is a diagram showing the data flow between the C / S architecture and core modules of the railway engineering collaborative design platform in this invention.

[0067] Figure 4 This is a flowchart of a collaborative design method for railway engineering according to an embodiment of the present invention. Detailed Implementation

[0068] The technical solution of the present invention will be described in detail below with reference to the accompanying drawings and embodiments.

[0069] In this invention, the file-level design-data-level collaboration working mode refers to the use of existing professional design software by designers from various disciplines to perform design modeling and obtain design outcome files. These design outcome files are stored and managed locally in file formats such as dwg, rvt, and p3d, aiming to preserve the original design habits of designers and the software assets of the enterprise to the greatest extent. Through data collaboration adaptation middleware, the design outcome files are automatically parsed, and information such as engineering entities, geometric attributes, and relationships are extracted. This information is then transformed into structured data objects and synchronized to the railway engineering collaborative design platform. A unified data topology is constructed based on engineering logic to achieve centralized storage, refined management, and cross-professional data-level collaboration of engineering data.

[0070] like Figure 1 As shown, the document-level design-data-level collaborative design method for railway engineering of the present invention specifically includes the following steps:

[0071] S1 proposes a technical framework for collaborative design in railway engineering: This framework includes planning and constructing a system encompassing the development of railway engineering data standards, the research and development of a collaborative design platform, the collaborative transformation of existing specialized design software, the development of data collaboration adaptation middleware, and the implementation of collaborative design testing and verification. By establishing a collaborative mechanism based on "documents" as the fundamental design unit and "data" as the refined collaborative dimension, a top-level guiding scheme for collaborative design covering the entire lifecycle and all disciplines is established.

[0072] S2, Compile railway engineering data standards: unify the entity definitions, attribute descriptions, relationships, data exchange content and formats of railway engineering data across different disciplines, form a machine-readable railway engineering data model, and synchronize the railway engineering data model to the design software of each discipline and the railway engineering collaborative design platform, providing a unified semantic foundation for cross-discipline data-level collaboration.

[0073] like Figure 2 As shown, the compilation of railway engineering data standards follows these six steps to ensure their scientific rigor, completeness, and practicality:

[0074] 1) Needs Survey and Analysis: Conduct in-depth research on the design processes, data interaction requirements, and existing data formats of various disciplines before and after the railway station construction. Analyze the results of the needs survey, clarify the scope and granularity of railway engineering data standards, and form a survey report and a list of interactive data.

[0075] 2) Definition of core entities: Based on the survey report and the interactive data list, the core entities in the entire life cycle of railway engineering are extracted to obtain a list of core entities, and each core entity is assigned a unique identifier.

[0076] 3) Attribute and Relationship Modeling: Define in detail the attribute set, attributes, and relationships between each core entity in the core entity list and other core entities to obtain the logical data topology and attribute matrix, forming a logically rigorous entity relationship model.

[0077] 4) Data exchange format design: Determine the exchange format of the structured data objects, and give priority to using platform-independent and easily parsed text formats such as JSON or XML for exchange; at the same time, clarify the association method between unstructured data objects (design results) and structured data objects, and form a standard exchange data schema draft and document association specifications.

[0078] 5) Expert review and revision: Organize senior experts in the industry, chief engineers of various disciplines and front-line designers to conduct multiple rounds of review on the draft standard exchange data model and document association specifications. If the multiple rounds of review fail, suggestions for modification will be made from the perspectives of business logic, technical feasibility and ease of use, and the process will return to step 3); if the multiple rounds of review pass, the data standard will be solidified and a formal standard document will be formed.

[0079] 6) Release and version management: Release the official standard document and establish a standard version management mechanism; pre-embed the standard exchange data mode in the railway engineering collaborative design platform to ensure the evolvability and backward compatibility of the railway engineering data standard.

[0080] S3, Development of a collaborative design platform for railway engineering: The collaborative design platform for railway engineering is the core and carrier for realizing data-level collaboration. It adopts a client-server (C / S) architecture and consists of two parts: a client-side collaborative workbench and a server-side data hub. Figure 3 This demonstrates the platform's client / server architecture and the data flow between its core modules. Details are as follows:

[0081] The client-side collaborative workbench is deployed locally on the designer's computer, serving as a unified entry point for interaction between the designer and the railway engineering collaborative design platform. It provides a graphical collaborative design environment (engineering structure tree, attribute information, context information, etc.) and a railway engineering data operation interface. The client-side collaborative workbench includes:

[0082] 1) Attribute View and Project Structure Tree:

[0083] A hierarchical tree structure is used to create an engineering structure tree, which displays the engineering breakdown structure of the entire project (e.g., project-section-work point-specialty-engineering entity). Designers can quickly locate any engineering object through this structure tree. After selecting an engineering entity, the attribute view on the right dynamically displays all attribute information of that entity, and supports editing and saving, enabling real-time feedback of design intent and maintenance of data consistency.

[0084] 2) Secondary Development Toolkit (SDK):

[0085] This SDK provides a standardized application programming interface (API) and plugin development framework for use by various professional design software and data collaboration middleware. It encapsulates data synchronization, data topology construction, and version control modules, shielding the underlying data storage and communication details, significantly lowering the barrier to entry for heterogeneous software and laying the foundation for rapid integration. Specifically:

[0086] The data synchronization module is used for bidirectional data synchronization between the client and the server, including pushing local modifications to the server and pulling the latest data from the server to the local machine; at the same time, it also receives structured data objects from the data extraction component in S5, performs local data merging and consistency verification, and ensures the consistency and traceability of data versions during the collaboration process.

[0087] The data topology construction module is used to build a real-time updated engineering data topology based on the entity association model defined in S2, intuitively displaying the dependencies between various engineering entities. Designers can quickly understand the impact of changes to engineering entities through this engineering data topology, assisting in design decisions.

[0088] The version control module is used to establish a complete version history for each engineering entity, supporting version comparison, backtracking and merging operations to ensure that the design process is traceable and auditable, and to meet the quality management requirements of railway engineering.

[0089] The server-side data hub is the core of the entire platform, responsible for the centralized storage, management, and distribution of all engineering data, ensuring data security, consistency, and high availability. The server-side data hub includes:

[0090] 1) Data storage center:

[0091] A hybrid storage architecture combining structured and unstructured data objects is adopted, centrally storing both structured and unstructured data objects. The structured data objects refer to information such as engineering entities, geometric attributes, relationships, and personnel organization extracted from design deliverables. This information is modeled and stored based on railway engineering data standards compiled by S2. The unstructured data objects refer to original design deliverables (such as dwg, rvt, p3d, etc.). Each original design deliverable is assigned a globally unique identifier and associated with the corresponding structured engineering entity, supporting version management and traceability of design deliverables.

[0092] 2) Data synchronization service:

[0093] It provides an efficient and reliable data synchronization interface, supports concurrent access from multiple clients, data conflict detection and automatic merging mechanisms, and ensures the consistency and real-time performance of data in the collaborative design environment.

[0094] 3) File management service:

[0095] Unstructured files are stored and accessed in a unified manner, supporting file upload, download, and preview, and are associated with corresponding engineering entities in structured data objects to form a complete engineering data asset system.

[0096] S4 involves the collaborative transformation of existing professional design software, setting up standardized input and output interfaces for railway engineering collaborative design platforms.

[0097] This step serves as a bridge connecting the platform and the software. While maintaining the existing functional integrity of each professional design software and preserving user operating habits, it adds standardized input and output interfaces for the railway engineering collaborative design platform based on the secondary development toolkit in S31. Specifically:

[0098] The input interface is used to enable the design software to change from reading local data sources (Excel, binary files, tagged text, local databases, etc.) to accessing the railway engineering collaborative design platform based on API.

[0099] The output interface enables the design software to switch from writing to local files (DWG drawings, RVT or P3D models, etc.) to submitting design results to the railway engineering collaborative design platform via API.

[0100] Through the above operations, single-discipline design software is transformed from a "data silo" into a "professional design terminal" in the enterprise collaborative design system. This not only preserves the working habits of designers but also enables them to participate in multi-discipline data-level collaboration.

[0101] S5, a middleware for R&D data collaboration and adaptation:

[0102] The data collaboration and adaptation middleware is the execution unit for automated workflow. Embedded within the runtime environment of basic design software (AutoCAD, ZWCAD, Revit, BIMBase, etc.), it is responsible for presenting the collaborative design environment (engineering structure tree, attribute information, context information, etc.) described in S3 to designers. It automatically parses and extracts the design deliverables, transforms the extracted information into structured data objects, and synchronizes them to the railway engineering collaborative design platform, improving the designers' visual interaction experience and ease of operation. See also... Figure 3 This middleware contains two types of core components:

[0103] (1) Design Environment Embedded Component: This component is responsible for presenting the design software environment of the client collaborative workbench in the user interface of the design software as an embedded panel. When the designer starts the design software from the client collaborative workbench, this component reads the client collaborative workbench data, creates a project structure tree and attribute view, and loads the context information (personnel, organization, role, etc.) into the current design session. During the design process, the designer can use this component to create new project entities and add or modify attribute information.

[0104] (2) Data Extraction Component: Responsible for parsing and extracting data from the design deliverables after the design is completed. This component is triggered when the designer completes the design and clicks the "Submit" button, and performs the following operations:

[0105] 1) Perform in-depth analysis of the current design deliverables, extract information such as engineering entities, geometric parameters, material properties, and relationships based on the railway engineering data standard compiled by S2, and transform / parse them into fine-grained structured data objects that conform to the definition of the railway engineering data standard.

[0106] 2) Upload the design deliverables to the local cache directory specified in the client's collaborative workbench.

[0107] 3) Push the fine-grained structured data object obtained in step 1) to the client collaborative workbench through the secondary development toolkit.

[0108] 4) The client-side collaborative workbench merges the received fine-grained structured data objects, automatically handles versions and conflicts, and updates the data topology.

[0109] 5) After the designers confirm that everything is correct, they will perform the "Synchronize with Server" operation in the client-side collaborative workbench. At this time, all fine-grained structured data objects and unstructured data objects will be uploaded to the server for other team members to access synchronously.

[0110] S6, Conduct collaborative design testing and verification:

[0111] Collaborative design testing and verification is a verification step to ensure the effectiveness of the system. It verifies the effectiveness of collaborative work through typical railway engineering projects and drives the continuous optimization of the entire system.

[0112] In one embodiment of the present invention, a typical railway engineering project is selected to conduct multi-disciplinary collaborative design applications, verifying the support capabilities of railway engineering data standards, railway engineering collaborative design platforms, and modified professional design software for complex railway engineering design scenarios. This includes:

[0113] S61, Test Preparation:

[0114] Select typical railway sections that involve multiple disciplines such as bridges, tunnels, roadbeds, and stations, and have complex interface relationships, and deploy the railway engineering data standard, railway engineering collaborative design platform, and modified design software for each discipline as described in this invention.

[0115] S62, Collaborative Design Applications:

[0116] like Figure 4 As shown, the team conducts collaborative design for railway engineering during the construction drawing phase. To clearly illustrate the process of multi-disciplinary concurrent data provision and flow, the collaborative design testing and verification process is summarized into the following four stages:

[0117] 1) Collaborative initialization and task distribution: The project administrator creates a project and configures initial resources in the railway engineering collaborative design platform; the overall project establishes an engineering structure tree based on the engineering decomposition structure and distributes task permissions to each professional section, thus completing the initialization of the data collaboration environment.

[0118] 2) Basic Data Release and Initial Design: The surveying / geology professionals submit initial topographic map data of the project area to the railway engineering collaborative design platform. The alignment professionals retrieve the initial topographic map data and conduct alignment scheme design. Upon completion, they release the initial alignment centerline without gaps and corresponding drawings to the railway engineering collaborative design platform as a spatial reference benchmark for subsequent designs by various disciplines.

[0119] 3) Interface Boundary Definition and Iterative Survey: The station, bridge, tunnel, and roadbed specialties extract the centerline of the line without gaps, generate work points for their respective specialties through the "gap identification" and interface extraction mechanism, and transmit the interface boundary information back to the railway engineering collaborative design platform; the line specialties collect all gaps along the line and publish horizontal and vertical profile drawings. Subsequently, the surveying and geology specialties use the updated line and work point data to conduct detailed field surveys and submit detailed topographic and geological data to the railway engineering collaborative design platform; the station specialties receive the horizontal and vertical profile drawings and carry out station layout design.

[0120] 4) Parallel Detailed Design and Overall Integration: Each professional specialization receives the aforementioned topographic and geological data, as well as the data from adjacent interfaces, proposes boundary constraints such as land use and track expansion, and conducts parallel detailed design of its own construction drawings. Upon completion, the structured design results and drawing files are submitted simultaneously to the railway engineering collaborative design platform. Finally, the project as a whole uses the data verification tools of the railway engineering collaborative design platform to check the data quality of the entire line's design results, confirming the consistency of the interfaces among various specializations and the integrity of the data, thus achieving a closed loop in the collaborative design process.

[0121] S63, Effectiveness Evaluation and Comparison, including:

[0122] 1) Efficiency indicators: Statistically compare the average time spent on cross-disciplinary data collection, data verification, and design change notification before and after adopting the aforementioned collaborative design method for railway engineering.

[0123] 2) Quality indicators: Count the number of design errors, omissions and missing parts caused by professional interface conflicts and inconsistent data versions, and compare them with historical project data.

[0124] 3) Satisfaction survey: Collect the designers' subjective feelings about the ease of operation and practicality of the new system through questionnaires and interviews.

[0125] S64, Summary and Optimization:

[0126] Based on the results of the collaborative design test, a detailed test report is generated, summarizing the advantages and disadvantages of the collaborative design method for railway engineering. In response to the problems found in the collaborative design test, the railway engineering data standards, the functions of the railway engineering collaborative design platform, and the performance of the data collaboration adaptation middleware are iteratively optimized to form a mature solution that can be promoted on a large scale.

Claims

1. A collaborative design method for railway engineering based on document-level design and data-level collaboration, characterized in that, Includes the following steps: S1 proposes a technical framework for collaborative design of railway engineering: planning and constructing a technical framework that includes compiling railway engineering data standards, developing a collaborative design platform for railway engineering, collaboratively transforming existing professional design software, developing data collaboration adaptation middleware, and conducting collaborative design testing and verification, and establishing a top-level guidance scheme for collaborative design covering the entire life cycle and all professions. S2, Compile railway engineering data standards: unify the entity definitions, attribute descriptions, relationships, data exchange content and formats of railway engineering data across different disciplines, form a machine-readable railway engineering data model, and synchronize the railway engineering data model to the design software of each discipline and the railway engineering collaborative design platform, providing a unified semantic foundation for cross-discipline data-level collaboration; S3, Develop a collaborative design platform for railway engineering: The collaborative design platform for railway engineering includes a client-side collaborative workbench and a server-side data hub. The client-side collaborative workbench provides a graphical collaborative design environment and a railway engineering data operation interface. The server-side data hub is responsible for the centralized storage, management and distribution of all engineering data, ensuring data security, consistency and high availability. S4. To collaboratively modify existing professional design software, standardized input and output interfaces are set up for the railway engineering collaborative design platform. S5, Research and Development Data Collaboration Adaptation Middleware: The data collaboration adaptation middleware is used to present the collaborative design environment to the designers and automatically complete the parsing and extraction of the design result files, convert the extracted information into structured data objects and synchronize them to the railway engineering collaborative design platform. The design result files are obtained by the designers of each profession using existing professional design software for design modeling. S6. Conduct collaborative design testing and verification, verify the effectiveness of collaborative design methods through typical railway engineering projects, and drive the continuous optimization of the entire system.

2. The collaborative design method for railway engineering according to claim 1, characterized in that, S2 includes the following steps: 1) Needs survey and analysis: Conduct in-depth research on the design process, data interaction needs and existing data formats of various disciplines before and after the railway station construction. Analyze the results of the needs survey, clarify the scope and granularity of railway engineering data standards, and form a survey report and a list of interactive data. 2) Definition of core entities: Based on the survey report and the interactive data list, the core entities in the entire life cycle of railway engineering are extracted to obtain a list of core entities, and each core entity is assigned a unique identifier; 3) Attribute and Relationship Modeling: Define in detail the attributes of each core entity in the core entity list and the relationships between it and other core entities to obtain the logical data topology and attribute matrix, forming a logically rigorous entity relationship model; 4) Data exchange format design: Determine the exchange format of the structured data objects, and use a platform-independent and easily parsed text format for exchange; at the same time, clarify the association method between unstructured data objects and structured data objects, and form a draft standard data exchange model and file association specifications; 5) Expert Review and Revision: Organize senior experts in the industry, chief engineers of various specialties, and front-line designers to conduct multiple rounds of review on the draft standard exchange data model and document association specifications. If the multiple rounds of review fail, propose modification suggestions from the perspectives of business logic, technical feasibility, and ease of use, and return to step 3); if the multiple rounds of review pass, solidify the data standard and form a formal standard document; 6) Release and version management: Release the official standard document and establish a standard version management mechanism; pre-embed the standard exchange data mode in the railway engineering collaborative design platform.

3. The collaborative design method for railway engineering according to claim 2, characterized in that, The client-side collaborative workbench described in S3 includes: 1) Attribute View and Project Structure Tree: A hierarchical tree structure is used to display the engineering breakdown structure of the entire project. Designers can quickly locate any engineering object through this engineering structure. After selecting an engineering entity, the attribute view dynamically displays all the attribute information of the engineering entity and supports editing and saving. 2) Secondary development toolkit: This toolkit provides standardized application programming interfaces and plugin development frameworks for use by various professional design software and data collaboration adaptation middleware. It encapsulates data synchronization modules, data topology construction modules, and version control modules, shielding the underlying data storage and communication details.

4. The collaborative design method for railway engineering according to claim 3, characterized in that: The data synchronization module is used for bidirectional data synchronization between the client and the server, including pushing local modifications to the server and pulling the latest data from the server to the local machine; at the same time, it also receives the structured data object and performs local data merging and consistency verification. The data topology construction module is used to construct a real-time updated engineering data topology based on the entity association model, which intuitively displays the dependencies between various engineering entities. The version control module is used to establish a complete version history for each project entity, and supports version comparison, backtracking and merging operations.

5. The collaborative design method for railway engineering according to claim 2, characterized in that, The server-side data hub includes: 1) Data storage center: A hybrid storage architecture of structured and unstructured data objects is adopted, which centrally stores structured and unstructured data objects. The structured data objects refer to engineering entities, geometric attributes, relationships, and personnel organization information extracted from design deliverables. This information is modeled and stored based on the railway engineering data standard. The unstructured data objects refer to the original design deliverables. Each original design deliverable is assigned a globally unique identifier and associated with the corresponding structured engineering entity, supporting version management and traceability of design deliverables. 2) Data synchronization service: It provides an efficient and reliable data synchronization interface, supports concurrent access from multiple clients, data conflict detection and automatic merging mechanisms, and ensures the consistency and real-time performance of data in the collaborative design environment. 3) File management service: Unstructured files are stored and accessed in a unified manner, supporting file upload, download and preview, and are associated with corresponding engineering entities in structured data objects to form a complete engineering data asset system.

6. The collaborative design method for railway engineering according to claim 5, characterized in that, In S4: The input interface is used to enable the design software to change from reading local data sources to accessing the railway engineering collaborative design platform based on APIs. The output interface is used to enable the design software to submit design results to the railway engineering collaborative design platform via API instead of writing to local files.

7. The collaborative design method for railway engineering according to claim 6, characterized in that, The data collaboration and adaptation middleware described in S5 includes: (1) Design Environment Embedded Component: This component is responsible for presenting the design software environment of the client collaborative workbench in the user interface of the design software in the form of an embedded panel. When the designer starts the design software from the client collaborative workbench, this component reads the client collaborative workbench data, creates a project structure tree and attribute view, and loads the context information into the current design session. During the design process, the designer can create new project entities and add or modify attribute information through this component. (2) Data extraction component: responsible for parsing and extracting data from the design output files after the design is completed.

8. The collaborative design method for railway engineering according to claim 7, characterized in that, When the designer completes the design and clicks the "Submit" button, the data extraction component is triggered and performs the following operations: 1) Perform in-depth analysis of the current design deliverables, extract the engineering entities, geometric parameters, material properties, and correlation information based on the railway engineering data standard, and transform / parse them into fine-grained structured data objects that conform to the definition of the railway engineering data standard; 2) Upload the design deliverables to the local cache directory specified in the client's collaborative workbench; 3) Push the fine-grained structured data object obtained in step 1) to the client collaborative workbench through the secondary development toolkit; 4) The client-side collaborative workbench merges the received fine-grained structured data objects, automatically handles versions and conflicts, and updates the data topology; 5) After the designers confirm that everything is correct, they will perform the "Synchronize with Server" operation in the client-side collaborative workbench. At this time, all fine-grained structured data objects and unstructured data objects will be uploaded to the server for other team members to access synchronously.

9. The collaborative design method for railway engineering according to claim 8, characterized in that, S6 includes the following steps: S61, Test Preparation: Select a typical railway section that involves multiple disciplines and has complex interface relationships, and deploy the railway engineering data standard, railway engineering collaborative design platform and the modified design software for each discipline. S62, Collaborative Design Applications: Organize a team to conduct collaborative design for railway engineering during the construction drawing phase, including: 1) Collaborative initialization and task distribution: The project administrator creates a project and configures initial resources in the railway engineering collaborative design platform; the overall project establishes an engineering structure tree based on the engineering decomposition structure and distributes task permissions to each professional section, thus completing the initialization of the data collaboration environment; 2) Basic data release and initial design: The surveying / geology professionals submit the initial topographic map data of the project area to the railway engineering collaborative design platform; the track professionals pull the initial topographic map data and carry out track design. After completion, the initial track centerline without gaps and the corresponding drawings are released to the railway engineering collaborative design platform as a spatial reference benchmark for subsequent designs by various professions. 3) Interface Boundary Definition and Iterative Survey: The station, bridge, tunnel, and roadbed specialties extract the centerline of the line without gaps, generate work points for their respective specialties through the "gap identification" and interface extraction mechanism, and send the interface boundary information back to the railway engineering collaborative design platform; the line specialties collect all gaps and publish horizontal and vertical profile drawings; subsequently, the surveying and geology specialties use the updated line and work point data to conduct detailed field surveys and submit detailed topographic and geological data to the railway engineering collaborative design platform; the station specialties receive the horizontal and vertical profile drawings and carry out station layout design; 4) Parallel Detailed Design and Overall Integration: Each professional specialization receives the aforementioned topographic and geological data, as well as the data from adjacent interfaces, proposes boundary constraints such as land use scope and track expansion, and conducts parallel detailed design of its own construction drawings. Upon completion, the structured design results and drawing files are submitted simultaneously to the railway engineering collaborative design platform. Finally, the project as a whole uses the data verification tool of the railway engineering collaborative design platform to check the data quality of the entire line's design results, confirming the consistency of each professional interface and the integrity of the data, thus achieving a closed loop in the collaborative design business. S63, Evaluate and compare the effects of the collaborative design; S64. Based on the results of the collaborative design, a detailed test report is generated, summarizing the advantages and disadvantages of the collaborative design method for railway engineering. In response to the problems found in the collaborative design test, the railway engineering data standards, the functions of the railway engineering collaborative design platform, and the performance of the data collaboration adaptation middleware are iteratively optimized to form a mature solution that can be promoted on a large scale.

10. The collaborative design method for railway engineering according to claim 9, characterized in that, The assessment includes the following indicators: 1) Efficiency indicators: Statistically compare the average time spent on cross-disciplinary data collection, data verification, and design change notification before and after adopting the aforementioned collaborative design method for railway engineering; 2) Quality indicators: Calculate the number of design errors, omissions, and gaps caused by conflicts in professional interfaces and inconsistent data versions, and compare them with historical project data; 3) Satisfaction survey: Collect designers' subjective feelings about the ease of operation and practicality of the new system through questionnaires and interviews.

Images