MRO system data sharing interaction method and device

Abstract

The invention relates to the technical field of railway vehicles, in particular to an MRO system data sharing interaction method and device, and the method comprises the steps: constructing a data medium station; dividing the data center into a plurality of lightweight micro-services by adopting a micro-service architecture, independently deploying each micro-service, and constructing a distributed database; gathering the data of each maintenance service system to the data middle table, and processing the data of each maintenance service system to generate a unified data view; based on the unified data view, the functions of the maintenance service systems are published in a service form; and accessing the MRO system to the data medium station, calling service by the MRO system through the service access interface, and accessing the function and data of each maintenance service system. According to the method, a unified data middle station is constructed, and conversion from strong coupling point-to-point interaction to loose coupling data driving interaction between systems is achieved.

Description

Technical Field

[0001] The present invention relates to the field of rail transit technology, and in particular to a method and device for MRO system data sharing interaction. Background Art

[0002] The traditional rail transit MRO system interacts with external systems based on the OSB point-to-point interface, which results in complex interfaces, serious system coupling, inability to share data, and poor business collaboration. At the same time, the traditional MRO system lacks scientific spare parts management and reserve strategies, and cannot meet the needs of modern rail transit intelligence and leanness. Summary of the invention

[0003] The present invention provides a method and device for MRO system data sharing and interaction, which are used to solve the defects of the prior art that the point-to-point interface is difficult to realize data sharing and business collaboration and the spare parts management is insufficient. Through the data middle-end sharing and interaction, the MRO system decoupling and data fusion are realized, and the business collaboration is improved.

[0004] The present invention provides a MRO system data sharing interaction method, comprising: Build a data middle platform, and set a service access interface in the data middle platform; The data center is divided into multiple lightweight microservices using a microservice architecture, each microservice is independently deployed, and a distributed database is constructed; Aggregate the data of each maintenance business system to the data center, process the data of each maintenance business system, and generate a unified data view; Based on the unified data view, the functions of each maintenance business system are published in the form of services; The MRO system is connected to the data middle platform, and the MRO system calls the service through the service access interface to access the functions and data of each maintenance business system.

[0005] According to the present invention, a method for sharing and interacting MRO system data is provided, wherein the maintenance business system data includes: The train’s history configuration, maintenance materials, maintenance quality information and maintenance procurement information.

[0006] According to the MRO system data sharing and interaction method provided by the present invention, the steps of dividing the data middle platform into multiple lightweight microservices using a microservice architecture specifically include: Adopting a microservice architecture, the data center functions are divided into four lightweight microservices: access gateway, registration center, configuration center, and service governance; Wherein, the access gateway is used to control the service access rights of the MRO system to access the service access interface; The registration center is used to register the service; The configuration center is used to configure parameters of the service and centrally manage the configured services; The governance center is used to monitor interface service performance indicators in real time to ensure service quality; and to uniformly manage data assets and service resources.

[0007] According to the MRO system data sharing interaction method provided by the present invention, the access gateway uses the OAuth2 protocol to control the service access rights of the service access interface.

[0008] According to the MRO system data sharing and interaction method provided by the present invention, the steps of independently deploying each of the microservices and building a distributed database specifically include: Adopt NewSQL technology to distribute data on multiple servers to achieve horizontal expansion; Use data segmentation and hash mapping to distribute data to different shard databases; Use read-write separation and distributed transaction mechanisms to ensure data consistency and high availability; The Crimea database is used to automatically complete the preset management functions, wherein the preset management functions include query optimization, load balancing, and failover.

[0009] According to the MRO system data sharing and interaction method provided by the present invention, the step of aggregating the data of each maintenance business system to the data middle platform specifically includes: Through the service access interface, the data of each maintenance business system is sent to the data center in the form of services or messages.

[0010] According to the MRO system data sharing and interaction method provided by the present invention, the steps of processing the data of each business system to generate a unified data view include: Establish a data lake, transform and integrate the data of each business system, and generate a unified data view.

[0011] According to the MRO system data sharing and interaction method provided by the present invention, the steps of processing the data of each business system to generate a unified data view specifically include: Build an HDFS data lake and use Sqoop or Kafka to incrementally collect data from relational data sources of each maintenance business system to the data lake; Azkaban is used to execute data ETL tasks to perform a first process on the data collected in the data lake, wherein the first process includes cleaning, deduplication, trimming, and labeling; After performing a second processing on the data after the first processing using Apache Spark SQL or taframes, various data sets are generated, wherein the second processing includes aggregation and joining; Import the generated data set into Elasticsearch, use data integration tools to quickly define data mapping and transformation logic, and generate a unified data view.

[0012] According to the MRO system data sharing and interaction method provided by the present invention, after obtaining the unified data view, the method further includes: Build data visualization analysis reports through Kibana or Apache Superset to provide analysis services for various maintenance business systems.

[0013] According to the MRO system data sharing and interaction method provided by the present invention, based on the unified data view, the steps of publishing the functions of each maintenance business system in the form of a service specifically include: Registering the functions of each of the business systems through the registration center; Using service orchestration technology, the functions of each of the registered business systems are published in the form of services, and service access requests corresponding to the functions of each of the business systems are generated; Each of the service access requests is forwarded to each of the business systems through the service gateway.

[0014] According to the MRO system data sharing and interaction method provided by the present invention, the step of connecting the MRO system to the data middle station specifically includes: Modify the service interface and data model of the MRO system to adapt to the interface of the data center; Connect the MRO system to the data center.

[0015] According to the MRO system data sharing and interaction method provided by the present invention, the data center provides a visual process orchestration tool and a process engine; The step of the MRO system calling the service through the service access interface to access the functions and data of each of the business systems specifically includes: Design cross-system collaborative processes based on actual business needs; Based on the cross-system collaborative process, a service access request of the MRO system is obtained; Sending the service access request to the data center to verify the service access permission; After the service access authority is verified, the cross-system collaborative process is generated into a process execution script through the visual process orchestration tool; The script is executed according to the process, and the service of the data center is called by the process engine to complete the cross-system collaborative process.

[0016] According to the MRO system data sharing interaction method provided by the present invention, after completing the cross-system collaboration process, the method further includes: Collect service call logs through the data center; Based on the service call log, a service call monitoring report is generated, and the service call monitoring report is used to provide call statistics information of each service.

[0017] According to the MRO system data sharing interaction method provided by the present invention, after completing the cross-system collaboration process, the method further includes: Generate an operation log of the data center during the entire execution of the cross-system collaborative process; The operation log of the data center is analyzed to optimize the cross-system collaborative process.

[0018] The present invention also provides a MRO system data sharing and interaction device, comprising the following modules: A middle platform construction module is used to construct a data middle platform and set a service access interface in the data middle platform; A microservice partitioning module is used to divide the data center into multiple lightweight microservices using a microservice architecture, independently deploy each microservice, and build a distributed database; A view generation module is used to aggregate the data of each maintenance business system to the data center, process the data of each maintenance business system, and generate a unified data view; A service publishing module, used to publish the functions of each maintenance business system in the form of services based on the unified data view; The service access module is used to connect the MRO system to the data center. The MRO system calls the service through the service access interface to access the functions and data of each maintenance business system.

[0019] The present invention also provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the MRO system data sharing and interaction method described above is implemented.

[0020] The present invention also provides a non-transitory computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the MRO system data sharing and interaction method as described in any one of the above is implemented.

[0021] The present invention also provides a computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the computer program implements any of the above-mentioned MRO system data sharing and interaction methods.

[0022] The MRO system data sharing and interaction method and device provided by the present invention realizes the transformation from strongly coupled point-to-point interaction to loosely coupled data-driven interaction between systems by constructing a unified data middle platform; the data middle platform adopts a microservice architecture design, and different systems can access the data services of the data middle platform through the service access interface. The data middle platform layer can be horizontally expanded and elastically expanded to cope with changes in access traffic; the data middle platform uniformly aggregates data from maintenance business systems from different sources, and generates a unified data view by processing the data, providing high-quality shared data services, and supporting cross-system business collaboration and data analysis; the data middle platform adopts distributed database technology, which can be horizontally expanded to cope with big data scenarios, and supports SQL queries, streaming processing and other data processing modes. Compared with the OSB point-to-point data interaction method, the data middle platform realizes the transformation from strongly coupled point-to-point interaction to loosely coupled data-driven interaction between systems, and improves the scalability, security, and intelligence level of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the present invention or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 It is a flow chart of the MRO system data sharing interaction method provided in an embodiment of the present invention.

[0025] Figure 2 It is a schematic diagram of a specific implementation process of the data middle platform supporting system sharing interaction provided by an embodiment of the present invention.

[0026] Figure 3 A schematic diagram of the structure of an MRO system data sharing and interaction device provided in an embodiment of the present invention.

[0027] Figure 4 A schematic diagram of the physical structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical solution and advantages of the present invention clearer, the technical solution of the present invention will be clearly and completely described below in conjunction with the drawings of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0029] In the description of the embodiments of the present invention, the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance. The specific operating methods in the method embodiments can also be applied to device embodiments or system embodiments. In the description of the present invention, unless otherwise specified, "at least one" includes one or more. "Multiple" refers to two or more. For example, at least one of A, B and C includes: A exists alone, B exists alone, A and B exist at the same time, A and C exist at the same time, B and C exist at the same time, and A, B and C exist at the same time. In the present invention, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a kind of association relationship that describes the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

[0030] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiment of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, without contradiction.

[0031] The following embodiments of the present invention are described in further detail in conjunction with the accompanying drawings and examples. The following examples are used to illustrate the present invention, but are not intended to limit the scope of the present invention.

[0032] In some specific embodiments of the present invention, Figure 1 As shown, the MRO system data sharing interaction method provided by this solution includes the following specific steps: Step 101: Build a data middle platform and set a service access interface in the data middle platform; Step 102: Use a microservice architecture to divide the data center into multiple lightweight microservices, independently deploy each microservice, and build a distributed database; Step 103: Aggregate the data of each maintenance business system to the data center, process the data of each maintenance business system, and generate a unified data view; Step 104: Based on the unified data view, the functions of each maintenance business system are published in the form of services; Step 105: Connect the MRO system to the data middle platform. The MRO system calls the service through the service access interface to access the functions and data of each maintenance business system.

[0033] It should be noted that there are two interpretations of the concept of MRO: one is to define MRO as the maintenance, repair and operation of products, which mainly refers to the maintenance and repair of enterprises' production and working facilities and products to ensure the non-productive materials required for their operation. Another interpretation is that the maintenance, repair and overhaul MRO (Maintenance Repair and Overhaul) of products refers to various maintenance, repair, overhaul and other maintenance service activities carried out during the use and maintenance stages of products. This definition is currently widely used in the field of aviation maintenance. Therefore, the MRO (Maintenance, Repair, Overhaul and Operation) mentioned in this plan, based on the concept of MRO (Maintenance, Repair and Overhaul) in aviation maintenance, adds operation (Operation) business content such as product operation, information, and status monitoring, and incorporates operation management (Operation Management) into the MRO business scope, also known as MRO2.

[0034] At present, existing technologies all have problems with OSB point-to-point interfaces and insufficient spare parts management. For example, the existing MRO system uses point-to-point interfaces, which leads to complicated interfaces and serious coupling, making it difficult to achieve data sharing and business collaboration. The existing system cannot meet the needs of intelligent and lean rail transit, and the spare parts management and reserve strategies are not scientific enough.

[0035] Therefore, the MRO system data sharing and interaction method provided in the embodiment of the present invention realizes seamless upgrade and iteration of the MRO system by constructing a data middle platform, and transforms the previous OSB point-to-point interaction into a shared interaction mode with the data middle platform as the core. Specifically, the data middle platform realizes system decoupling and data sharing, supports intelligent management and decision-making, and provides an implementation plan and implementation method from OSB to data middle platform sharing mode in response to the new needs of lean modern rail transit. Compared with OSB point-to-point interaction, it is an important way to upgrade the traditional MRO system.

[0036] In some possible implementations of the present invention, the maintenance business system data includes: Train history configuration TC, maintenance material WMS, maintenance quality information QMS and maintenance procurement information ERP.

[0037] Specifically, the history configuration TC includes history management and configuration management. History management specifically includes train information management, which manages all train information and is the basic data for subsequent plans and work orders; train information supports importing or receiving SAP mileage information; based on the vehicle configuration of the train, the corresponding safety information of each position is recorded, including serial number, manufacturing date, manufacturer, etc., to support the traceability of key component information. Configuration is the basis of maintenance. Configuration management in the system means managing its maintenance structure and displaying it in layers.

[0038] Furthermore, in accordance with the requirements for collecting the main configuration data, the main configuration data is compiled, including: combining design drawings, maintenance procedures, etc., to construct the main configuration: the components specified in the maintenance scope of each level of maintenance are included in the main configuration, and the hierarchical structure is constructed according to the physical assembly relationship of the train. In terms of material management, the scope of materials for which serial number management is enabled is determined (materials for which serial numbers are enabled must have nameplates or steel stamps to identify their production numbers), and the configuration positions of the components for which serial number management is enabled are split. Only one number of components can be installed in each position, and the life cycle history of a single component is managed based on this. For components that need to be analyzed for faults at different positions, they need to be reflected in the main configuration and split into different configuration positions. Determine whether the relevant configuration position is virtual and mark it. Fill in the material codes, installation rules, and counter rules that are allowed to be installed at the corresponding positions.

[0039] The main configuration maintenance process includes: determining whether train or component history initialization needs to be performed; if it is component history initialization, further determining whether it is a purchased part; if it is train history initialization, further determining whether it is a newly built train.

[0040] Supplier fills in resume information: Determine whether it is a purchased part; if it is a purchased part, the supplier fills in the resume information on the supplier collaboration platform (SNC system) and transmits it to the urban rail MRO system through the interface.

[0041] Receive and enter historical information: Determine whether it is a purchased part; if not, the subsidiary quality department enters the historical information and the process ends. Determine whether it is a newly built train; if it is a newly built train, the subsidiary quality department creates a train number in the urban rail MRO system; if it is not a newly built train, the subsidiary quality department enters the historical information and the process ends. In some possible implementations of the present invention, the steps of using a microservice architecture to divide the data center into multiple lightweight microservices specifically include: Adopting a microservice architecture, the data center functions are divided into four lightweight microservices: access gateway, registration center, configuration center, and service governance; Wherein, the access gateway is used to control the service access rights of the MRO system to access the service access interface; The registration center is used to register the service; The configuration center is used to configure parameters of the service and centrally manage the configured services; The governance center is used to monitor interface service performance indicators in real time to ensure service quality; and to uniformly manage data assets and service resources.

[0042] Specifically, this embodiment provides an implementation method of a data middle platform based on a microservice architecture. By building a unified data middle platform and adopting a microservice architecture, the middle platform functions are split into multiple lightweight services including access gateway, registration center, configuration center, and service governance. Services communicate through RPC. Among them, the gateway is responsible for request routing, current limiting, and fuse functions; the registration center implements service registration; the configuration center centrally manages configuration; and the governance center monitors and alarms services.

[0043] In a possible embodiment, the access gateway uses the OAuth2 protocol to control the service access rights of the service access interface.

[0044] In some possible implementations of the present invention, the steps of independently deploying each of the microservices and building a distributed database specifically include: Adopt NewSQL technology to distribute data on multiple servers to achieve horizontal expansion; Use data segmentation and hash mapping to distribute data to different shard databases; Use read-write separation and distributed transaction mechanisms to ensure data consistency and high availability; The Crimea database is used to automatically complete the preset management functions, wherein the preset management functions include query optimization, load balancing, and failover.

[0045] Specifically, this embodiment provides an implementation method for independently deploying each microservice and building a distributed database. Each microservice is independently deployed and has an independent database. Distributed transactions are used between microservices to ensure data consistency.

[0046] In a possible embodiment, each microservice exchanges data through a RESTful API. The data exchange format uses lightweight JSON, and the API uses OAuth2 for security control.

[0047] In a possible embodiment, Docker and Kubernetes can be used to achieve automated deployment, expansion, and load balancing of microservices.

[0048] In a possible embodiment, the microservice architecture adopts the Spring Cloud microservice development framework, uses SpringBoot to develop microservice applications, and builds components such as the Eureka registry and the Zuul gateway. Each microservice is independently deployed in a Docker container, and Kubernetes is used for container orchestration to achieve automatic scaling and load balancing of services. Declarative HTTP service calls are made between microservices through the Feign client, and Hystrix is ​​used to implement fault-tolerant Fallback. Apache Shiro or Spring Security is used for microservice interface access control, and JWT is used to implement inter-service security authentication.

[0049] In a possible embodiment, a distributed database is constructed, and Citus / Greenplum can be used for distributed storage of large amounts of relational data, supporting parallel computing; the database sharding adopts the Hash or Range method, and PostgreSQL Foreign Data is used to encapsulate the sharding; the 2PC protocol is used to ensure the ACID of distributed transactions, and the timestamp concurrency control solves the read-write concurrency problem; Postgres Streaming Replication is configured to implement dual-machine hot backup to ensure high availability.

[0050] It can be understood that this setting of the present invention decouples and abstracts the MRO system interface service, provides a unified interface service capability through the data middle platform, and realizes loosely coupled interaction with external systems.

[0051] In some possible implementations of the present invention, the step of aggregating the data of each maintenance business system to the data center specifically includes: Through the service access interface, the data of each maintenance business system is sent to the data center in the form of services or messages.

[0052] Specifically, this embodiment provides an implementation method for aggregating the data of each maintenance business system to the data middle platform, and sending the data of each maintenance business system to the data middle platform in the form of services or messages through the service access interface.

[0053] In actual applications, in order to ensure efficient and quality delivery of projects on time, the MRO system construction process will follow the principle of unified planning and step-by-step implementation.

[0054] Specifically, the MRO maintenance and manufacturing execution system is a large information system that involves all aspects of the enterprise and all aspects of maintenance services. Before the implementation of the MRO system, it is necessary to consider the system's foresight, advancement, and integrity, and to combine it with the actual situation. The principle of overall planning and distributed implementation is an important guarantee for the success of such systems. In order to avoid the establishment of "islands" of automated information in various systems of the enterprise, when constructing the MRO system, the information of various departments and systems will be integrated and shared, and existing resources will be fully utilized, including the following aspects: First, MRO should be classified and managed in different ways. MRO can be divided into five categories: wearing parts, which refer to spare parts with a short service life; key parts, which are spare parts with long processing cycles, difficult procurement, large impact on production, large capital occupation, and need to be strengthened; standard parts, which are parts that are widely used in various equipment and whose structure, specifications and various technical parameters meet national standards or industry standards; general accessories, which are general parts on equipment, which are not only widely used by host manufacturers, but also large and wide spare parts needed for equipment maintenance in society; parts that must be reserved according to status monitoring, pre-repair inspection, maintenance consumption records and other special regulations. For example, most of the standard parts of special spare parts can be handled as supplier consignment inventory.

[0055] Secondly, differentiated management of MRO should be implemented according to market supply conditions. For example, for special spare parts with a short supply cycle, an immediate procurement and supply strategy should be adopted, and the goods should be consumed immediately after they arrive at the user unit to avoid inventory. For general spare parts with abundant market resources, oversupply and stable consumption demand, the supplier consignment model should be adopted as much as possible to achieve "zero inventory".

[0056] Third, MRO should be managed according to the equipment maintenance plan. Equipment maintenance methods can be divided into planned maintenance and unplanned maintenance. For planned maintenance, the demand for MRO is predictable, so it can be ordered in advance and a no-inventory management model can be adopted. Under the unplanned maintenance method, spare parts can be divided into key parts and non-key parts according to the size of the loss due to out-of-stock. Key parts refer to spare parts that will cause huge economic losses if they cannot be supplied immediately once the equipment fails, so a safety inventory strategy needs to be implemented for key parts. For non-key parts, joint inventory can be implemented for spare parts, which can greatly reduce the cost of capital occupation.

[0057] Fourthly, adopt dynamic management methods to manage MRO inventory. Dynamically manage MRO in a certain period (such as month, quarter, year), pay attention to changes in inventory management and inventory demand at any time, make timely adjustments, form new operating procedures and standards, and avoid the recurrence of the original problems. In the continuous dynamic management cycle, continuous revisions based on actual conditions can make quota and cost management more reasonable.

[0058] Fifthly, standardized processes and standardized management are adopted, including standardized processes for planning work, inventory management and process formulation, standardized management of MRO product information, MRO quota consumption forecasting processes and standard forecasting methods, etc. Through standardized and process-based operations, the work efficiency of MRO inventory management is improved and work costs are reduced.

[0059] MRO inventory management based on the value chain can improve the inventory management level through the above models and management methods, timely grasp the equipment life cycle information, and be predictive in the purchase of MRO inventory. It can reduce the losses caused by production downtime due to sudden failures, reduce inventory reserves without affecting the progress of equipment maintenance work, and at the same time ensure equipment quality and extend the life cycle.

[0060] On the basis of the above embodiments, in order to meet the requirements of project construction, the maintenance manufacturing execution system continues to use the existing MRO system database and data table architecture, further optimizes the system logic on the basis of meeting the existing business logic, and improves the system processing efficiency and system stability.

[0061] It should be noted that the traditional MRO system lacks scientific spare parts management and reserve strategies, and cannot meet the needs of intelligent and lean modern rail transit.

[0062] Therefore, the embodiment of the present invention uses the data center to unify and aggregate data from different systems, realize data sharing, support intelligent management of spare parts throughout their life cycle, realize universal management of spare parts, make scientific decisions and predictions, and greatly improve the system's coordination and intelligence level. In some possible implementations of the present invention, the steps of processing the data of each of the business systems and generating a unified data view include: Establish a data lake, transform and integrate the data of each business system, and generate a unified data view.

[0063] Specifically, this embodiment provides an implementation method for processing the data of each business system to generate a unified data view. By establishing a data lake, the data of each maintenance business system is converted and integrated to generate a unified data view.

[0064] In some possible implementations of the present invention, the step of processing the business system data to generate a unified data view specifically includes: Build an HDFS data lake and use Sqoop or Kafka to incrementally collect data from relational data sources of each maintenance business system to the data lake; Azkaban is used to execute data ETL tasks to perform a first process on the data collected in the data lake, wherein the first process includes cleaning, deduplication, trimming, and labeling; After performing a second processing on the data after the first processing using Apache Spark SQL or taframes, various data sets are generated, wherein the second processing includes aggregation and joining; Import the generated data set into Elasticsearch, use data integration tools to quickly define data mapping and transformation logic, and generate a unified data view.

[0065] Specifically, this embodiment provides another implementation method for generating a unified data view. Through the data lake and data services, a Hadoop data lake is built to store structured, semi-structured, and unstructured data; Spark, Hive, etc. are used to perform ETL processing on the data to achieve data cleaning, conversion, and association to build a data mart; Elasticsearch is used as the data mart service engine to provide high-performance data query and analysis services; data modeling tools are used to quickly define and publish data services through configuration.

[0066] Furthermore, in a possible embodiment, after obtaining a unified data view, a data visualization analysis report can be constructed through Kibana or Apache Superset to provide analysis services for each maintenance business system.

[0067] In some possible implementations of the present invention, the step of publishing the functions of each business system in the form of a service based on the unified data view specifically includes: Registering the functions of each of the business systems through the registration center; Using service orchestration technology, the functions of each of the registered business systems are published in the form of services, and service access requests corresponding to the functions of each of the business systems are generated; Each of the service access requests is forwarded to each of the business systems through the service gateway.

[0068] Specifically, this embodiment provides a method for publishing services, by registering the functions of each maintenance business system; using service orchestration technology, the registered functions are published in the form of services, and service access requests corresponding to each function are generated; and then each service access request is forwarded to each of the business systems. Compared with the OSB method, the above-mentioned setting of the present invention, the data middle platform realizes innovations such as system decoupling, data sharing, middle platform governance, and service elasticity, and improves the system scalability, security, and intelligence level.

[0069] In some possible implementations of the present invention, the step of connecting the MRO system to the data middle station specifically includes: Modify the service interface and data model of the MRO system to adapt to the interface of the data center; Connect the MRO system to the data center.

[0070] Specifically, this embodiment provides an implementation method for connecting the MRO system to the data middle platform, by modifying the service interface and data model of the MRO system to adapt to the interface of the data middle platform; connecting the MRO system to the data middle platform to achieve the purpose of communication and interaction between the MRO system and the middle platform.

[0071] In some possible implementations of the present invention, the data center provides a visual process orchestration tool and a process engine; The step of the MRO system calling the service through the service access interface to access the functions and data of each of the business systems specifically includes: Design cross-system collaborative processes based on actual business needs; Based on the cross-system collaborative process, a service access request of the MRO system is obtained; Sending the service access request to the data center to verify the service access permission; After the service access authority is verified, the cross-system collaborative process is generated into a process execution script through the visual process orchestration tool; The script is executed according to the process, and the service of the data center is called by the process engine to complete the cross-system collaborative process.

[0072] Specifically, this embodiment provides an implementation method for an MRO system to access the functions of a business system by calling services, transforming and adapting the service interface and data model developed by the MRO system for the OSB method, connecting to the data middle platform, and realizing a new interaction mode based on shared data services.

[0073] In some possible implementations of the present invention, after completing the cross-system collaboration process, the method further includes: Collect service call logs through the data center; Based on the service call log, a service call monitoring report is generated, and the service call monitoring report is used to provide call statistics information of each service.

[0074] Or, generate the operation log of the data center during the whole execution of the cross-system collaborative process; The operation log of the data center is analyzed to optimize the cross-system collaborative process.

[0075] In some possible implementation schemes of the present invention, the data middle platform provided by this scheme has access control and data isolation.

[0076] In a possible embodiment, implementing access control and data isolation includes the following aspects: Integrate LDAP server, implement fine-grained permission control based on RBAC, and be compatible with OAuth and SAML protocols; Deploy firewalls, configure ACL and VLAN for network access control, and block illegal network traffic; The database enables row-level access control, so users and applications can only access data within a specified range; Set up a WAF and other application layer ban lists to defend against SQL injection, XSS and other attacks.

[0077] Specifically, this embodiment provides an implementation method for access control and data isolation in a data middle platform, which integrates LDAP for unified user identity management and supports fine-grained permission control; uses VLAN, VPN and other technologies to achieve logical isolation, and separates the deployment of data within and outside the network; logically isolates data from different systems and users, and prevents direct access to illegal data; and sets up multi-level security protection mechanisms such as whitelists, blacklists, and authentication links.

[0078] In some possible implementation schemes of the present invention, the data middle platform also has a middle platform governance function.

[0079] In a possible implementation, the middle platform governance function includes the following aspects: using open source monitoring tools to achieve all-round monitoring of services, applications, and data; applying SLA protocols and standards to set threshold warnings for core indicators; building a BI system to assist in middle platform tuning and governance decision-making through data analysis; regularly producing service level reports to continuously optimize middle platform performance and specifications.

[0080] In some possible implementation schemes of the present invention, the data middle platform also has a middle platform monitoring platform.

[0081] In a possible embodiment, the middle-office monitoring platform specifically includes: using Prometheus to monitor indicator data and Grafana to build monitoring dashboards; integrating the ELK log analysis platform to monitor the system operation status through logs; using the business Transaction Tracing platform to monitor the system call link and find the system bottleneck; combining real-time alarms with offline analysis to detect system risks in all directions.

[0082] Specifically, this embodiment provides an implementation method of a data middle platform, which distinguishes data between different users and business categories by separating data permissions. Each user can only query and operate his or her own data to ensure data security.

[0083] In some possible implementation schemes of the present invention, the application layer platform adopts distributed deployment to ensure high availability and scalability of services, and to ensure the flexibility and high scalability of the system.

[0084] In a possible embodiment, for the support service layer, a virtualized cluster composed of X86 servers can dynamically expand hardware and dynamically balance resources as business needs change; In a possible implementation, for the data storage layer, the workshop production execution system continues to use the existing Oracle database. Based on the MRO data table and the digital maintenance platform data table, a new data table is added according to the production execution-related business model. After comprehensive analysis of the historical data of the original table, data migration is performed as needed. The system will distinguish data between different applications, different users, and different business modules by separating data permissions to ensure data security and flexible use; In a possible implementation example, for the basic service layer, the maintenance and manufacturing execution system will continue to use the operating interface of the B / S architecture of the existing digital maintenance platform. On the basis of the original maintenance system functions, new related functions are added according to the characteristics of the workshop production execution business. Compared with the current rail transit Oracle Form operating interface, the new platform interface is more beautiful, more user-friendly, and more expandable; conduct a comprehensive and detailed evaluation of the existing EMU MRO system logic, migrate the application interface of the functions related to production execution management according to the application situation, and improve the overall operation efficiency of the MRO system; In a possible implementation example, for the access layer, the internal and external networks are isolated to ensure system security; load balancing is used to achieve balanced resource usage among the nodes in the cluster to ensure high load and high availability of the system.

[0085] In a possible embodiment, for the display layer, the workshop maintenance and manufacturing execution system will provide a visual real-time analysis interface for the workshop and provide data support for the production command center. At the same time, it can provide relevant production reports that are convenient for users to use and analyze through the Fanruan reporting platform.

[0086] In a possible embodiment, the present invention supports PC and mobile terminals, realizes mobile office, and improves work convenience.

[0087] In some specific implementation schemes of the present invention, this scheme realizes the seamless upgrade of the MRO system from the original point-to-point interface service bus (OSB) mode to the data middle platform shared interaction mode by building a data middle platform. The data sharing interaction method provided by this scheme specifically includes the following steps: Step 1: Build a unified data middle platform to achieve the transformation from strongly coupled point-to-point interaction to loosely coupled data-driven interaction between systems; In this step, the MRO system interface services are decoupled and abstracted, and unified interface service capabilities are provided through the data middle platform to achieve loosely coupled interaction with external systems.

[0088] Step 2: The data center adopts a microservice architecture design. Different systems can access the data services of the center through open APIs. The center layer can be expanded horizontally and elastically to cope with changes in access traffic; Step 3: The middle platform gathers data from different source systems, builds a data lake, cleans and converts data, provides high-quality shared data services, and supports cross-system business collaboration and data analysis; In this step, the business system data is uniformly aggregated to the data center, a data lake is established, and data cleaning, conversion, and association are performed to build the shared data services required by each maintenance business system.

[0089] Step 4: The middle platform adopts distributed database technology, which can be horizontally expanded to cope with big data scenarios and support multiple data processing modes such as SQL query and streaming processing; Step 5: The middle platform has access control, data isolation and other mechanisms to ensure data security between different systems and within the system, and supports fine-grained user and role permission control; In this step, the service interface and data model developed by the MRO system for the OSB method are transformed and adapted, connected to the data middle platform, and a new interaction mode based on shared data services is realized.

[0090] Step 6: The middle platform provides the middle platform governance function, which can uniformly monitor the management interface service performance, data quality and other indicators to ensure the service level; In this step, the MRO system is improved in functionality and user experience, data sharing and business collaboration capabilities are enhanced, and the intelligent functions driven by big data are strengthened.

[0091] Through the data center governance function, the interface service performance indicators are monitored in real time to ensure service quality. And data assets, services and other resources are managed in a unified manner.

[0092] Step 7: The middle platform greatly reduces the cost of external system access and upgrade maintenance. External systems can be accessed on demand and incrementally. In this step, a real-time data synchronization mechanism is built between the MRO system and the data center to ensure the consistency of master data and business data.

[0093] Furthermore, the data middle platform is used to support on-demand upgrades of the MRO system, achieve agile iteration, and reduce upgrade and maintenance costs.

[0094] Specifically, this solution provides another implementation method for MRO system data sharing and interaction. Compared with the OSB method, this solution realizes innovations such as system decoupling, data sharing, middle platform governance, and service elasticity through the data middle platform, improving the system's scalability, security, and intelligence. At the same time, this solution uses the data middle platform to unify the data of various maintenance business systems, realize data sharing, support intelligent management of spare parts throughout their life cycle, and realize universal management of spare parts, so as to facilitate users to make scientific decisions and predictions, thereby greatly improving the system's coordination and intelligence.

[0095] In some specific embodiments of the present invention, Figure 2 As shown, Figure 2 : is a schematic diagram of a specific implementation process of the data middle platform supporting system sharing interaction provided by an embodiment of the present invention, and a specific implementation process of the data middle platform supporting system sharing interaction: Step 201: Build a unified data center; In this step, a unified data center is built to provide a unified open service access interface for each external system.

[0096] Specifically, microservice architecture and distributed database technologies are used to build a unified data middle platform.

[0097] Step 202: The system publishes data services; External systems publish their own data to the middle platform in the form of services or messages through open interfaces.

[0098] Specifically, the system registers data services in the middle platform and adopts the RESTful API interface specification; the data format uses standard JSON or XML.

[0099] Step 203: Generate a unified data view; The data center converts and integrates the data sent by external systems to generate a unified data view.

[0100] Specifically, the middle platform obtains data through various system data services; cleans and transforms the data to generate a unified data view; and uses data integration tools to quickly define data mapping and conversion logic.

[0101] Step 204: Release system function services; The data center uses service orchestration technology to publish the service capabilities of external systems in the form of services; Specifically, the system registers its own functional services in the middle platform and defines the service interface specifications; the middle platform uses the service gateway to forward service requests to the original system; and the microservice framework is used to develop proxy services to achieve system adaptation.

[0102] Step 205: The middle platform opens service calls; External systems access the functions and data of other systems by calling the services opened by the middle platform; Specifically, the middle platform opens service calls and provides a unified service access interface to the outside world; the OAuth2 protocol is used to implement service access permission control.

[0103] Step 206: Middle office service authority control; The service gateway of the middle platform controls service access rights and ensures data security.

[0104] Specifically, the middle-office service permission control, the middle-office gateway integrates the permission control module, verifies the authorization status of each service request based on the access policy; if the request authentication fails, access is automatically denied.

[0105] Step 207: Generate a call monitoring report; The middle platform monitors system calls and generates call monitoring reports; Specifically, a call monitoring report is generated, and the middle-office log system collects service call logs; the log analysis system generates a service call monitoring report; and provides statistics such as the number of calls, delays, and failures.

[0106] Step 208: Configure the business collaboration process; Middle office operators can configure collaborative business processes between systems; Specifically, business collaboration processes are configured, and the middle platform provides visual process orchestration tools; operations personnel design cross-system collaboration processes based on needs.

[0107] Step 209: Process engine scheduling service; The process engine calls various system services in the middle platform according to the configuration to complete the business collaboration process; Specifically, the process engine schedules services, and the process orchestration tool generates process execution scripts; the process engine calls the middle office service according to the script to complete the process.

[0108] Step 210, the middle station records the process log; The middle platform uniformly records the process operation log for process optimization; Specifically, the middle platform records process logs, generates operation logs throughout the process execution, analyzes the logs to identify process problems and optimize the process.

[0109] Through the above steps, the data middle platform can support external systems to open up functions and data in the form of services, and external systems can achieve service mutual access and business collaboration based on the middle platform to achieve the goal of system collaborative sharing.

[0110] Compared with the existing point-to-point approach, the shared interaction of the data center realizes system decoupling, data integration, and improves business synergy. It enables business innovation through the empowerment of the center and significantly reduces maintenance costs. At the same time, the data center unifies and aggregates data from different systems to achieve data sharing, support intelligent management of spare parts throughout their life cycle, and achieve universal management of spare parts, providing accurate data support for scientific decision-making and prediction, thereby significantly improving system synergy and intelligence.

[0111] This method realizes seamless upgrade of MRO system from the original point-to-point interface service bus (OSB) mode to the data middle platform shared interaction mode by building a data middle platform. By decoupling and abstracting the interface service of the MRO system, the data middle platform provides unified interface service capabilities to realize loosely coupled interaction with external systems; the business system data is uniformly aggregated to the data middle platform, a data lake is established, and data cleaning, conversion, and association are performed to build the shared data services required by each maintenance business system; the service interface and data model developed for the OSB mode of the MRO system are transformed and adapted, connected to the data middle platform, and a new interaction mode based on shared data services is realized; the MRO system is functionally improved and the user experience is optimized, data sharing and business collaboration capabilities are enhanced, and the intelligent functions driven by big data are strengthened; the interface service performance indicators are monitored in real time through the middle platform governance function of the data middle platform to ensure service quality. And unified management of data assets, services and other resources; a real-time data synchronization mechanism is built between the MRO system and the data middle platform to ensure the consistency of master data and business data; the data middle platform is used to support the implementation of on-demand upgrades of the MRO system, realize agile iteration, and reduce upgrade and maintenance costs.

[0112] Compared with the OSB point-to-point approach, the shared interaction of the data middle platform realizes system decoupling, data integration, improves business collaboration, realizes business innovation through middle platform empowerment, and significantly reduces maintenance costs.

[0113] In some specific embodiments of the present invention, Figure 3 As shown, this solution provides an MRO system data sharing interaction device, and the MRO system data sharing interaction device described below and the MRO system data sharing interaction method described above can be referred to each other. The data sharing interaction device includes: The middle platform construction module 31 is used to construct a data middle platform and set a service access interface in the data middle platform; A microservice partitioning module 32 is used to divide the data center into multiple lightweight microservices using a microservice architecture, independently deploy each microservice, and build a distributed database; A view generation module 33 is used to aggregate the data of each maintenance business system to the data center, process the data of each business system, and generate a unified data view; A service publishing module 34, used to publish the functions of each of the business systems in the form of services based on the unified data view; The service access module 35 is used to connect the MRO system to the data middle platform. The MRO system calls the service through the service access interface to access the functions and data of each business system.

[0114] Preferably, the step of dividing the data center into multiple lightweight microservices using a microservice architecture specifically includes: Adopting a microservice architecture, the data center functions are divided into four lightweight microservices: access gateway, registration center, configuration center, and service governance; Wherein, the access gateway is used to control the service access rights of the MRO system to access the service access interface; The registration center is used to register the service; The configuration center is used to configure parameters of the service and centrally manage the configured services; The governance center is used to monitor interface service performance indicators in real time to ensure service quality; and to uniformly manage data assets and service resources.

[0115] Specifically, this embodiment provides an implementation method for obtaining a data middle platform of a microservice architecture.

[0116] Preferably, the steps of independently deploying each of the microservices and building a distributed database specifically include: Adopt NewSQL technology to distribute data on multiple servers to achieve horizontal expansion; Use data segmentation and hash mapping to distribute data to different shard databases; Use read-write separation and distributed transaction mechanisms to ensure data consistency and high availability; The Crimea database is used to automatically complete the preset management functions, wherein the preset management functions include query optimization, load balancing, and failover.

[0117] Specifically, this embodiment provides an implementation method for independently deploying each microservice to build a distributed database.

[0118] Preferably, the access gateway uses the OAuth2 protocol to control the service access rights of the service access interface.

[0119] Specifically, this embodiment provides an implementation method for accessing a gateway.

[0120] Preferably, the step of aggregating the data of each maintenance business system to the data center specifically includes: Through the service access interface, the data of each maintenance business system is sent to the data center in the form of services or messages.

[0121] Specifically, this embodiment provides an implementation method for aggregating business system data to a data center.

[0122] Preferably, the step of processing the data of each business system to generate a unified data view includes: Establish a data lake, transform and integrate the data of each business system, and generate a unified data view.

[0123] Preferably, the step of processing the data of each business system to generate a unified data view specifically includes: Build an HDFS data lake and use Sqoop or Kafka to incrementally collect data from relational data sources of each maintenance business system to the data lake; Azkaban is used to execute data ETL tasks to perform a first process on the data collected in the data lake, wherein the first process includes cleaning, deduplication, trimming, and labeling; After performing a second processing on the data after the first processing using Apache Spark SQL or taframes, various data sets are generated, wherein the second processing includes aggregation and joining; Import the generated data set into Elasticsearch, use data integration tools to quickly define data mapping and transformation logic, and generate a unified data view.

[0124] Specifically, this embodiment provides two implementation methods for generating a unified data view.

[0125] Preferably, after obtaining a unified data view, a data visualization analysis report is constructed through Kibana or Apache Superset to provide analysis services for various maintenance businesses.

[0126] Specifically, this embodiment provides an implementation method for constructing a data visualization analysis report.

[0127] Preferably, based on the unified data view, the step of publishing the functions of each business system in the form of a service specifically includes: Registering the functions of each of the business systems through the registration center; Using service orchestration technology, the functions of each of the registered business systems are published in the form of services, and service access requests corresponding to the functions of each of the business systems are generated; Each of the service access requests is forwarded to each of the business systems through the service gateway.

[0128] Specifically, this embodiment provides an implementation method for publishing the functions of each maintenance business system in the form of services.

[0129] Preferably, the step of connecting the MRO system to the data middle station specifically includes: Modify the service interface and data model of the MRO system to adapt to the interface of the data center; Connect the MRO system to the data center.

[0130] Specifically, this embodiment provides an implementation method for connecting the MRO system to the data middle platform.

[0131] Preferably, the data center provides a visual process orchestration tool and a process engine; The step of the MRO system calling the service through the open access interface to access the functions and data of each of the business systems specifically includes: Design cross-system collaborative processes based on actual business needs; Based on the cross-system collaborative process, a service access request of the MRO system is obtained; Sending the service access request to the data center to verify the service access permission; After the service access authority is verified, the cross-system collaborative process is generated into a process execution script through the visual process orchestration tool; The script is executed according to the process, and the service of the data center is called by the process engine to complete the cross-system collaborative process.

[0132] Specifically, this embodiment provides an implementation method for an MRO system to perform data sharing interaction through a data middle platform.

[0133] Preferably, after the cross-system collaborative process is completed in the above embodiment, the service call log can be collected through the data middle station; based on the service call log, a service call monitoring report is generated, and the service call monitoring report is used to provide call statistics information of each service; or, the operation log of the data middle station is generated throughout the execution of the cross-system collaborative process; the operation log of the data middle station is analyzed to optimize the cross-system collaborative process.

[0134] It should be noted that the implementation principle and beneficial effects of the MRO system data sharing interaction device provided in the embodiment of the present invention are similar to the implementation principle and beneficial effects of the MRO system data sharing interaction method shown in the above embodiment. Please refer to the implementation principle and beneficial effects of the MRO system data sharing interaction method shown in the above embodiment, and no further details will be given here.

[0135] Figure 4 An example of a physical structure diagram of an electronic device is shown in FIG. Figure 4As shown, the electronic device may include: a processor 410, a communication interface 420, a memory 430 and a communication bus 440, wherein the processor 410, the communication interface 420 and the memory 430 communicate with each other through the communication bus 440. The processor 410 may call the logic instructions in the memory to execute the following MRO system data sharing interaction method: construct a data middle platform, and set a service access interface in the data middle platform; divide the data middle platform into multiple lightweight microservices using a microservice architecture, independently deploy each microservice, and construct a distributed database; aggregate the data of each maintenance business system to the data middle platform, process the data of each business system, and generate a unified data view; based on the unified data view, publish the functions of each business system in the form of services; connect the MRO system to the data middle platform, and the MRO system calls the service through the service access interface to access the functions and data of each business system.

[0136] In addition, the logic instructions in the above-mentioned memory can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the relevant technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0137] An embodiment of the present invention discloses a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes program instructions. When the program instructions are executed by a computer, the computer can execute the methods provided by the above-mentioned method embodiments, for example, including: MRO system data sharing interaction method: constructing a data middle platform, and setting a service access interface in the data middle platform; using a microservice architecture to divide the data middle platform into multiple lightweight microservices, independently deploying each of the microservices, and constructing a distributed database; aggregating the data of each maintenance business system to the data middle platform, processing the data of each business system, and generating a unified data view; based on the unified data view, publishing the functions of each business system in the form of services; connecting the MRO system to the data middle platform, and the MRO system calls the service through the service access interface to access the functions and data of each business system.

[0138] On the other hand, an embodiment of the present invention further provides a non-transitory computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, is implemented to execute the transmission methods provided by the above-mentioned embodiments, for example, including: an MRO system data sharing and interaction method: constructing a data middle platform, and setting a service access interface in the data middle platform; using a microservice architecture to divide the data middle platform into multiple lightweight microservices, independently deploying each of the microservices, and constructing a distributed database; aggregating the data of each maintenance business system to the data middle platform, processing the data of each of the business systems, and generating a unified data view; based on the unified data view, publishing the functions of each of the business systems in the form of services; connecting the MRO system to the data middle platform, and the MRO system calls the service through the service access interface to access the functions and data of each of the business systems.

[0139] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0140] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiment.

[0141] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A data sharing and interaction method for an MRO system, characterized in that: include: Build a data middle platform, and set a service access interface in the data middle platform; The data center is divided into multiple lightweight microservices using a microservice architecture, each microservice is independently deployed, and a distributed database is constructed; Aggregate the data of each maintenance business system to the data center, process the data of each maintenance business system, and generate a unified data view; Based on the unified data view, the functions of each maintenance business system are published in the form of services; The MRO system is connected to the data middle platform, and the MRO system calls the service through the service access interface to access the functions and data of each maintenance business system.

2. The MRO system data sharing and interaction method according to claim 1, characterized in that: The maintenance business system data includes: The train’s history configuration, maintenance materials, maintenance quality information and maintenance procurement information.

3. The MRO system data sharing and interaction method according to claim 2 is characterized in that: The steps of dividing the data center into multiple lightweight microservices using a microservice architecture include: Adopting a microservice architecture, the data center functions are divided into four lightweight microservices: access gateway, registration center, configuration center, and service governance; Wherein, the access gateway is used to control the service access rights of the MRO system to access the service access interface; The registration center is used to register the service; The configuration center is used to configure parameters of the service and centrally manage the configured services; The governance center is used to monitor interface service performance indicators in real time to ensure service quality; and to uniformly manage data assets and service resources.

4. The MRO system data sharing and interaction method according to claim 3 is characterized in that: The access gateway uses the OAuth2 protocol to control the service access rights of the service access interface.

5. The MRO system data sharing and interaction method according to claim 3 is characterized in that: The steps of independently deploying each of the microservices and building a distributed database specifically include: Adopt NewSQL technology to distribute data on multiple servers to achieve horizontal expansion; Use data segmentation and hash mapping to distribute data to different shard databases; Use read-write separation and distributed transaction mechanisms to ensure data consistency and high availability; The Crimea database is used to automatically complete the preset management functions, wherein the preset management functions include query optimization, load balancing, and failover.

6. The MRO system data sharing and interaction method according to claim 5, characterized in that: The step of aggregating the data of each maintenance business system to the data center specifically includes: Through the service access interface, the data of each maintenance business system is sent to the data center in the form of services or messages.

7. The MRO system data sharing and interaction method according to claim 3 is characterized in that: The step of processing the data of each business system to generate a unified data view includes: Establish a data lake, transform and integrate the data of each business system, and generate a unified data view.

8. The MRO system data sharing and interaction method according to claim 7, characterized in that: The step of processing the data of each business system to generate a unified data view specifically includes: Build an HDFS data lake and use Sqoop or Kafka to incrementally collect data from relational data sources of each maintenance business system to the data lake; Azkaban is used to execute data ETL tasks to perform a first process on the data collected in the data lake, wherein the first process includes cleaning, deduplication, trimming, and labeling; After performing a second processing on the data after the first processing using Apache Spark SQL or taframes, various data sets are generated, wherein the second processing includes aggregation and joining; Import the generated data set into Elasticsearch, use data integration tools to quickly define data mapping and transformation logic, and generate a unified data view.

9. The MRO system data sharing and interaction method according to claim 8, characterized in that: After obtaining the unified data view, the method further includes: Build data visualization analysis reports through Kibana or Apache Superset to provide analysis services for various maintenance businesses.

10. The MRO system data sharing and interaction method according to any one of claims 3 to 9, characterized in that: Based on the unified data view, the step of publishing the functions of each maintenance business system in the form of a service specifically includes: Registering the functions of each of the business systems through the registration center; Using service orchestration technology, the functions of each of the registered business systems are published in the form of services, and service access requests corresponding to the functions of each of the business systems are generated; Each of the service access requests is forwarded to each of the business systems through the service gateway.

11. The MRO system data sharing and interaction method according to claim 10, characterized in that: The steps of connecting the MRO system to the data center specifically include: Modify the service interface and data model of the MRO system to adapt to the interface of the data center; Connect the MRO system to the data center.

12. The MRO system data sharing and interaction method according to claim 11, characterized in that: The data center provides visual process orchestration tools and process engines; The step of the MRO system calling the service through the service access interface to access the functions and data of each of the business systems specifically includes: Design cross-system collaborative processes based on actual business needs; Based on the cross-system collaborative process, a service access request of the MRO system is obtained; Sending the service access request to the data center to verify the service access permission; After the service access authority is verified, the cross-system collaborative process is generated into a process execution script through the visual process orchestration tool; The script is executed according to the process, and the service of the data center is called by the process engine to complete the cross-system collaborative process.

13. The MRO system data sharing and interaction method according to claim 12, characterized in that: After completing the cross-system collaboration process, the method further includes: Collect service call logs through the data center; Based on the service call log, a service call monitoring report is generated, and the service call monitoring report is used to provide call statistics information of each service.

14. The MRO system data sharing and interaction method according to claim 12, characterized in that: After completing the cross-system collaboration process, the method further includes: Generate an operation log of the data center during the entire execution of the cross-system collaborative process; The operation log of the data center is analyzed to optimize the cross-system collaborative process.

15. A data sharing and interaction device for an MRO system, characterized in that: include: A middle platform construction module is used to construct a data middle platform and set a service access interface in the data middle platform; A microservice partitioning module is used to divide the data center into multiple lightweight microservices using a microservice architecture, independently deploy each microservice, and build a distributed database; A view generation module is used to aggregate the data of each maintenance business system to the data center, process the data of each maintenance business system, and generate a unified data view; A service publishing module, used to publish the functions of each maintenance business system in the form of services based on the unified data view; The service access module is used to connect the MRO system to the data center. The MRO system calls the service through the service access interface to access the functions and data of each maintenance business system.

Images