Tire project visualization view generation method and system based on data service bus

Abstract

The invention provides a tire project visual view generation method, system and equipment based on a data service bus and a medium, automation and timing / event-driven synchronization of cross-system data are realized through the data service bus, a unified data model taking a tire project as a core and a production number as a key tracking unit is constructed, and the data service bus is established. The method comprises the following steps of: establishing a project panoramic view by business roles such as a project manager in a self-service manner on the basis of the dimension and real-time data, defining project data dimensions specific to the industry, and adopting a low-code view generator, so that dynamic linkage of view data and a business system is realized, and regular update and safety management and control of information such as material inventory, project progress and process parameters are guaranteed; and full-process visual management of the tire project is realized.

Description

Technical Field

[0001] This disclosure relates to the field of visualization technology, and in particular to a method, system, device, and medium for generating visualization views of tire projects based on a data service bus. Background Technology

[0002] Currently, existing visualization view generation systems are mostly designed for general scenarios or specific non-industrial fields (such as finance and taxation). They are overly generalizable and lack industry depth, failing to deeply understand the business processes, data characteristics, and decision-making needs of the tire manufacturing industry. Data integration solutions are outdated, often relying on traditional point-to-point interfaces or ETL tools, which cannot achieve real-time, standardized data delivery. The view generation logic is tightly coupled with the data acquisition logic, resulting in high architectural coupling and poor system scalability, making it difficult to adapt to the frequently changing business needs of tire projects. Furthermore, there is a lack of dedicated visualization components and unified data models for tire manufacturing projects, requiring business personnel to have specialized technical backgrounds to configure professional views. Therefore, it is necessary to provide a technical solution that enables cross-system data synchronization, establishes a dedicated data warehouse for tire projects, and achieves dynamic linkage between view data and business systems. Summary of the Invention

[0003] The purpose of this disclosure is to provide a method, system, device, and medium for generating visual views of tire projects based on a data service bus, in order to solve at least one of the aforementioned technical problems.

[0004] To achieve the above objectives, in a first aspect, this disclosure provides a method for generating a visual view of a tire project based on a data service bus, comprising the following steps: The project source data is obtained from several existing business systems of the tire project through a data service bus, and the project source data is converted into standardized data; wherein, the existing business systems include PLM system, U9 system, and OA system; Based on the standardized data, cross-system data relationships are established and project data dimensions are calculated to construct a dedicated data warehouse for the tire project. Establishing cross-system data relationships includes: associating design tasks from the PLM system with procurement requirements from the U9 system using material codes and project production numbers; associating purchase orders from the U9 system with inventory materials using material codes; and associating approval nodes from the OA system with project stages using project production numbers and process types. The project data dimensions include production number availability rate, design-procurement-production linkage progress, customer project association, and cross-system critical path dimensions. A low-code view generator is used to provide a configuration interface for users; Data is read from the tire project's dedicated data warehouse based on the user's configuration operations on the configuration interface, and a visualization view is generated.

[0005] In a preferred embodiment, the project source data includes design data from the PLM system, supply chain and production data from the U9 system, and approval flow data from the OA system.

[0006] In a preferred embodiment, project source data is obtained from the existing business system of the tire project, and the project source data is converted into standardized data, including: Proactively acquire project source data from various existing business systems; The source data of the project is cleaned and transformed to form standardized data that conforms to the tire project data model; The standardized data is synchronously updated according to preset rules or preset events.

[0007] In a preferred embodiment, the low-code view generator includes a library of visualization components for project management; it reads data from the tire project-specific data warehouse based on user configuration operations on the configuration interface to generate a visualization view, including: The configuration interface displays project parameters and project data dimensions; Receives user selections of project parameters and project data dimensions on the configuration interface; Receive drag-and-drop operations from users, such as dragging chart components from the visualization component library onto the canvas; Bind the dragged chart components to the selected project parameters and project data dimensions to complete the visualization view configuration.

[0008] In a preferred embodiment, data is read from the tire project-specific data warehouse based on the user's configuration operations on the configuration interface to generate a visualization view, and the method further includes: Once the configuration is complete, a visual view link will be generated; When an end user clicks the visualization view link, the visualization view is loaded; Based on the visualization view configuration operation, a data query request is initiated to the tire project's dedicated data warehouse; Combine the query results of the data query request with the visualization view component to render the final visualization view and display it.

[0009] In a preferred embodiment, when the project source data changes, an update is automatically pushed to achieve real-time refresh of the visualization view.

[0010] Secondly, this disclosure provides a tire project visualization view generation system based on a data service bus, which is implemented through the following modules: The data service bus module is used to acquire project source data from several existing business systems of the tire project through the data service bus, and convert the project source data into standardized data; wherein, the existing business systems include PLM system, U9 system, and OA system; The data warehouse construction module is used to establish cross-system data relationships based on the standardized data and calculate project data dimensions to build a dedicated data warehouse for the tire project. Establishing cross-system data relationships includes: associating design tasks from the PLM system with procurement requirements from the U9 system using material codes and project production numbers; associating purchase orders from the U9 system with inventory materials using material codes; and associating approval nodes from the OA system with project stages using project production numbers and process types. The project data dimensions include production number availability rate, design-procurement-production linkage progress, customer project association, and cross-system critical path dimensions. The view configuration module is used to provide a configuration interface for users using a low-code view generator. The view generation module is used to read data from the tire project's dedicated data warehouse based on the user's configuration operations on the configuration interface and generate a visual view.

[0011] In a preferred embodiment, the data service bus module includes an adapter for a PLM system, an adapter for a U9 system, and an adapter for an OA system; the data service bus module connects to existing business systems via an Enterprise Service Bus (ESB) or API gateway.

[0012] In one preferred implementation, the low-code view generator includes: A visualization component library that provides chart components for tire projects; The data dimension selection and configuration panel provides an interface for selecting project data dimensions and configuring project parameters. The view canvas and interaction logic configuration area is used to provide view layout and interaction configuration functions.

[0013] In one preferred embodiment, a display terminal module is also included for displaying a visual view.

[0014] Thirdly, this disclosure also provides an electronic device, including: a memory and one or more processors; the memory is used to store one or more computer programs; when the one or more computer programs are executed by the one or more processors, the method for generating a tire project visualization view based on a data service bus as described in any embodiment of the first aspect of this disclosure is implemented.

[0015] Fourthly, this disclosure also provides a computer storage medium storing a computer program; when the computer program is executed by a processor, it implements the tire project visualization view generation method based on a data service bus as described in any embodiment of the first aspect of this disclosure.

[0016] Beneficial effects:

[0017] Compared to existing technologies, the tire project visualization view generation method, system, equipment, and medium provided in this disclosure, based on a data service bus, achieves automated, timed / event-driven synchronization of cross-system data through the data service bus. It constructs a unified data model with the tire project as the core and the production number as the key tracking unit, defines industry-specific project data dimensions, and adopts a low-code view generator. This enables project managers and other business roles to build a panoramic view of the project based on the above dimensions and real-time data, achieving dynamic linkage between view data and business systems. This ensures timely updates and secure control of information such as material inventory, project progress, and process parameters, realizing full-process visualized management of tire projects. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of this disclosure and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 A flowchart of the method for generating a visual view of a tire project based on a data service bus, as provided in this disclosure.

[0020] Figure 2 A schematic diagram of the system architecture for generating a visualization view of a tire project based on a data service bus, as provided in this disclosure.

[0021] Figure 3 This is a schematic diagram of the tire project visualization view generation system based on the data service bus provided in this disclosure.

[0022] Figure 4 A schematic block diagram of an electronic device also provided in this disclosure. Detailed Implementation

[0023] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. The components of the embodiments of this disclosure described and shown in the accompanying drawings can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed disclosure, but merely represents selected embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0024] Please see Figure 1 This is a flowchart of a method for generating a visual view of a tire project based on a data service bus, provided in Embodiment 1 of this disclosure. It should be noted that the method of this disclosure is not limited to the order of the following steps, and in other embodiments, the method of this disclosure may include only a portion of the following steps, or some steps may be deleted.

[0025] The tire project visualization view generation method provided in this embodiment can be applied to a tire project visualization view generation system based on a data service bus. This method uses the data service bus to automate and synchronize PLM (design data), U9 ERP (supply chain and production data), and OA (approval flow data) on a scheduled / event-driven basis. It constructs a unified data model with the tire project as the core and the production number as the key tracking unit, defines industry-specific project data dimensions, and provides a low-code view generator. This enables project managers and other business roles to build a panoramic view of the project based on the above dimensions and real-time data, achieving dynamic linkage between view data and business systems. It ensures timely updates and secure management of information such as material inventory, project progress, and process parameters, and can solve the problems of data fragmentation, fixed views, and delayed decision-making in tire equipment production projects.

[0026] The tire project visualization view generation method based on a data service bus provided in this embodiment includes the following steps: Step S10: Obtain project source data from several existing business systems of the tire project through the data service bus, and convert the project source data into standardized data.

[0027] Specifically, the tire project visualization view generation system based on the data service bus includes a data service bus module. The cross-system data service bus serves as the core hub and is configured with adapters for various existing business systems, enabling the integration of heterogeneous data from various systems.

[0028] In some implementations, the existing business systems include a PLM system, a U9 system, and an OA system, and the project source data includes design data from the PLM system, supply chain and production data from the U9 system, and approval flow data from the OA system.

[0029] In some implementations, step S10 includes: Proactively acquire project source data from various existing business systems; The source data of the project is cleaned and transformed to form standardized data that conforms to the tire project data model; The standardized data is synchronously updated according to preset rules or preset events.

[0030] Specifically, the cross-system data service bus serves as the core hub, configured with adapters for the PLM system (for extracting design data such as design tasks, BOMs, and drawing version status), adapters for the U9 system (for extracting supply chain and production data such as purchase orders, inventory materials, and production work orders), and adapters for the OA system (for extracting approval flow data such as project-related approval processes and forms). This bus can be synchronized according to preset rules (e.g., every hour) or events (e.g., PLM task completion, OA process node approval). This disclosure achieves automated, timed / event-driven synchronization of PLM (design data), U9 ERP (supply chain and production data), and OA (approval flow data) through the data service bus.

[0031] The data service bus module can connect to existing business system layers via Enterprise Service Bus (ESB) or API gateway. Specifically, it connects to the PLM system via Web Service API, to the U9 system via direct database connection or middleware connection, and to the OA system via RESTful API, achieving cross-system data integration.

[0032] The data service bus module is the core of this disclosure for realizing cross-system data integration. It includes: a data extraction unit for actively acquiring data from various source systems; a timed / event-triggered synchronization unit for controlling the timing and frequency of data synchronization; and a data cleaning and transformation unit for converting source data into a format that conforms to the industry data model.

[0033] Understandably, data cleaning involves removing duplicate records, correcting format errors, and handling null values, while data transformation involves mapping fields and converting formats according to the tire project data model. Step S10 integrates, cleans, and transforms the raw data scattered across PLM, U9, and OA systems according to the needs of tire project management, providing unified and standardized data services for upper-level applications.

[0034] Step S20: Based on the standardized data, establish cross-system data relationships and calculate project data dimensions to construct a dedicated data warehouse for the tire project.

[0035] Specifically, the system may include a data warehouse construction module. For a dedicated data warehouse for tire projects, the data model is based on the equipment project as the main entity, with the project production number attached, which is the unique production number of a specific piece of equipment.

[0036] Furthermore, in step S20, establishing cross-system data relationships includes: Associate design tasks from the PLM system with procurement requirements from the U9 system using material codes and project numbers; Link purchase orders from the U9 system with inventory materials using material codes; The approval nodes from the OA system are associated with the project stages through the project product number and process type.

[0037] Furthermore, in step S20, the project data dimensions include, but are not limited to, the product number completeness rate dimension, the design-procurement-production linkage progress dimension, the customer project association dimension, and the cross-system critical path dimension.

[0038] Specifically, the product number matching rate dimension calculates the matching ratio of all planned materials to actual available materials for a given product number. The design-procurement-production linkage progress dimension tracks the entire chain of procurement needs, purchase orders, warehousing, and final production work orders triggered by a design task. The customer project association dimension categorizes and analyzes projects by customer, contract, and project type (e.g., new products, modifications, spare parts). The cross-system critical path dimension identifies key bottlenecks affecting project delivery, such as "waiting for design review (OA) - waiting for drawing release (PLM) - waiting for long-lead-time parts procurement (U9)".

[0039] The tire project's dedicated data warehouse stores processed, standardized data, which may include: a unified data model storage area for storing data tables organized according to the tire project model; and a project data dimension engine for predefining and calculating industry-specific data dimensions.

[0040] Understandably, the data service bus module can write the processed data to the tire project's dedicated data warehouse via JDBC connection. This dedicated data warehouse not only stores data but also transforms the raw data into business metrics that can be directly used for project management through predefined data dimensions and computational logic.

[0041] Step S30: Use a low-code view generator to provide a configuration interface for users.

[0042] Specifically, the system may include a view configuration module, which uses a low-code view generator to provide users with a configuration interface. The low-code project view generator can provide a library of visual components for tire project management, such as "Project Gantt Chart (Enhanced Version)," "Production Number Matching Rate Radar Chart," and "Customer Project Distribution Tree Chart," enabling project managers and other business roles to build a panoramic view of the project on their own based on the above dimensions and real-time data.

[0043] The low-code project view generator provides a user configuration interface, which may include: a project management visualization component library, providing chart components specifically for tire projects; a project data dimension selection and configuration panel, providing a dimension selection and parameter configuration interface; and a view canvas and interaction logic configuration area, providing view layout and interaction configuration functions.

[0044] Step S40: Read data from the tire project-specific data warehouse according to the user's configuration operation on the configuration interface and generate a visualization view.

[0045] Specifically, the system may include a view generation module that can read data from the tire project's dedicated data warehouse according to user configuration and generate a visual view.

[0046] In some implementations, step S40 includes: The configuration interface displays project parameters and project data dimensions; Receives user selections of project parameters and project data dimensions on the configuration interface; Receive drag-and-drop operations from users, such as dragging chart components from the visualization component library onto the canvas; Bind the dragged chart components to the selected project parameters and project data dimensions to complete the visualization view configuration.

[0047] In some implementations, step S40 further includes: Once the configuration is complete, a visual view link will be generated; When an end user clicks the visualization view link, the visualization view is loaded; Based on the visualization view configuration operation, a data query request is initiated to the tire project's dedicated data warehouse; Combine the query results of the data query request with the visualization view component to render the final visualization view and display it.

[0048] Specifically, the project parameters displayed on the configuration interface can be the project number. Users generate views through the process of "selecting the project number → selecting one or more unique data dimensions → binding visualization components → configuring display rules." A low-code view generator is used, enabling project managers and other business roles to build a comprehensive project view based on the aforementioned dimensions and real-time data. This achieves dynamic linkage between view data and the business system, ensuring timely updates and secure control of information such as material inventory, project progress, and process parameters, thus realizing full-process management of tire projects.

[0049] Understandably, the tire project visualization view generation system based on the data service bus also includes a display terminal module for displaying the visualization view. The visualization view rendering and display terminal is used to display the final view.

[0050] Furthermore, the low-code project view generator reads data from the tire project's dedicated data warehouse through the data access layer and communicates with the visualization view rendering and display terminal via the HTTP / WebSocket protocol.

[0051] In some implementations, updates are automatically pushed when the source data of the project changes, enabling real-time updates of the visualization. That is, the system can establish a WebSocket connection and automatically push updates when the source data changes, ensuring the timeliness of the visualization.

[0052] The electrical signal (data flow) flow of the tire project visualization view generation system based on the data service bus is as follows: Data acquisition signal flow: PLM / U9 / OA system → Data service bus API interface → Data extraction service → Message queue (Kafka) → Data processing service; Data processing signal flow: Raw data → Cleaning and filtering → Format conversion → Business calculation → Standardized data → Data warehouse; View query signal flow: User action → HTTP request → View generator backend → SQL query → Data warehouse → Query results → JSON response → Frontend rendering; Real-time update of signal stream: source data change → event publication → WebSocket push → front-end reception → partial view update.

[0053] Please see Figure 2This is a schematic diagram of the system architecture for generating a visual view of a tire project based on a data service bus, as provided in this disclosure. This disclosure solves the problem of data silos, improves management efficiency, and integrates heterogeneous data from PLM, U9, and OA through a dedicated database. It unifies core fields and association rules, avoiding the tedious manual cross-system queries and data aggregation. The time for project managers to obtain full-process information is reduced from hours to minutes, improving management efficiency by over 80%. It also ensures data accuracy and timeliness. The daily incremental synchronization mechanism only synchronizes newly added and changed data. Combined with built-in data validation rules, it reduces manual entry errors and data lag, increasing data accuracy to over 99%, providing reliable data support for project progress assessment and decision-making. Furthermore, it enables visualized management and control of the entire project process. Based on a no-code platform, the display screen and visualized project details page intuitively present core indicators such as the number of projects at each stage, progress completion rate, and overdue warnings. It supports multi-dimensional filtering and querying, solving the pain points of opaque project status and difficulty in tracking process nodes in traditional management, facilitating timely detection and rapid handling of overdue and stalled issues. It can also reduce management costs, eliminating the need to rely on professional developers to customize development views. Management pages can be quickly configured through a visual platform, reducing system development and maintenance costs. At the same time, it avoids the manpower consumption of cross-system data verification, reducing the manpower and time costs of project management.

[0054] The specific implementation methods of the above steps are described below by way of example.

[0055] The data service bus module is implemented using a microservice architecture and the Spring Cloud framework. Specifically, it includes the following microservices: a data acquisition service, which implements data extraction unit functionality and uses Apache Camel for multi-protocol adaptation; a task scheduling service, which implements timed / event-triggered synchronization unit functionality and uses Quartz Scheduler; and a data processing service, which implements data cleaning and transformation unit functionality, with its core comprising a tire industry data model mapping rule engine.

[0056] Specifically, the implementation method of data model mapping rules in the tire industry is shown in the following example: json { "mapping_rules": [ { "source_system": "PLM", "source_field": "design_task.progress", "target_model": "project.unified_design_progress", "transformation": "convert_percentage_to_decimal" }, { "source_system": "U9", "source_field": "inventory.material_status", "target_model": "project.material_availability", "transformation": "map_status_code_to_availability" } ] }

[0057] The core function of the data service bus module is to integrate, clean, and transform the raw data scattered in PLM, U9, and OA according to the needs of tire project management, and provide unified and standardized data services for upper-level applications.

[0058] Furthermore, a dedicated data warehouse for the tire project is constructed, including data model design and calculation of the project data dimension engine.

[0059] Specifically, the implementation method of data model design is shown in the following example: SQL -- Core Project List CREATE TABLE device_project ( project_id VARCHAR(50) PRIMARY KEY, project_name VARCHAR(200), customer_id VARCHAR(50), project_type VARCHAR(50), -- e.g., new product development, modification project, spare parts project start_date DATE, end_date DATE, project_manager VARCHAR(100) ); -- Product Number Table (Key Entity) CREATE TABLE production_number ( prod_no VARCHAR(50) PRIMARY KEY, project_id VARCHAR(50), equipment_type VARCHAR(100), -- Equipment type: molding machine, winding machine, etc. planned_delivery_date DATE, actual_progress DECIMAL(5,2), FOREIGN KEY (project_id) REFERENCES device_project(project_id) ); -- Cross-system association table CREATE TABLE cross_system_relation ( relation_id BIGINT PRIMARY KEY, source_system VARCHAR(20), -- PLM / U9 / OA source_object_id VARCHAR(100), -- Source system object ID target_system VARCHAR(20), target_object_id VARCHAR(100), project_id VARCHAR(50), relation_type VARCHAR(50) -- e.g., Design-Material Association, Approval-Task Association ).

[0060] Specifically, the calculation logic of the project data dimension engine is shown in the following example: Calculation of complete product number matching rate: text Product number completeness rate = (Quantity of completed materials / Planned quantity of materials) × 100%.

[0061] Calculation of the design-procurement-production linkage schedule: Python def calculate_design_procurement_linkage(project_id): # Get the design task completion status design_completion = get_design_completion_rate(project_id) # Get the procurement progress of related materials procurement_progress = get_related_procurement_progress(project_id) # Calculate the linkage coefficient linkage_score = min(design_completion, procurement_progress) 0.7+ max(design_completion, procurement_progress) 0.3 return linkage_score.

[0062] Furthermore, the low-code project view generator adopts a front-end and back-end separation architecture. The back-end uses Java Spring Boot to provide a REST API, including: component metadata management service, view definition persistence service, and data query optimization service. The front-end uses the Vue.js framework, including: a drag-and-drop canvas component (based on vue-draggable), a dynamic form generator (for dimension parameter configuration), and a real-time preview engine.

[0063] Examples of implementations of components specific to the tire equipment industry are as follows: javascript / / Production Number Matching Rate Radar Chart Component const EquipmentCompletionRadar = { name: 'equipment-completion-radar', props: ['projectId', 'dimensionConfig'], data() { return { chartInstance: null, chartData: []} }, methods: { async fetchData() { / / Call the backend API to get the product number matching rate data. const response = await axios.get( ` / api / projects / ${this.projectId} / dimensions / completion-rate`, { params: this.dimensionConfig} ); this.chartData = this.transformData(response.data); }, transformData(rawData) { / / Convert the data to the format required for a radar chart return rawData.map(item => ({ name: item.production_number, value: [ item.mechanical_completion, item.electrical_completion, item.standard_parts_completion ] })); } } }

[0064] Low-code view generators enable project managers to create complex visual views that meet business needs without writing code by providing an intuitive configuration interface and a rich set of industry components.

[0065] The following is an exemplary description of the process of generating a visual view of a tire project based on a data service bus, as provided in this disclosure, in practical application.

[0066] First, configure multi-source data connection and synchronization rules. The system administrator configures connection parameters for the PLM, U9, and OA systems respectively in the data service bus management interface. Configure synchronization strategies for each data object: PLM design task data is incrementally synchronized every 30 minutes; U9 material inventory data is synchronized every 15 minutes, with synchronization triggered immediately upon inventory changes; OA approval process data is synchronized when the approval status changes. Configure data association rules, such as the mapping relationship between material codes in PLM design tasks and U9 material master data codes.

[0067] Then, data synchronization and industry-specific integration are performed. The data service bus extracts data from various source systems according to the configured strategy. The data processing service performs cleaning and transformation, removing duplicate records, correcting format errors, and handling null values. Data transformation is performed, and field mapping and format conversion are carried out according to the tire project data model. Data association is performed, and cross-system data relationships are established based on the configured association rules. Dimension calculation is performed, and the project data dimension engine is called to calculate business indicators such as product number matching rate and linkage progress in real time. The processed data is then stored in a dedicated data warehouse.

[0068] Then, configure the visualization view based on the project's specific dimensions. Taking the creation of a "Molding Machine Project Delivery Risk Monitoring Dashboard" as an example: The project manager logs into the low-code view builder and creates a new view; in the project selector, select the target project "XJ2023-01-001 Molding Machine Project"; from the dimension selection panel, check the dimensions to be monitored. Required dimensions include product number completeness rate and design task progress; optional dimensions include key approval node status and number of customer change requests; drag components from the component library to the canvas, drag the "Enhanced Project Gantt Chart" component to the main area, and drag the "Product Number Completeness Rate Trend Chart" component. Go to the right-hand auxiliary area; configure component data binding, bind the task data source of the Gantt chart to the "Design Task Progress" dimension, bind the task color of the Gantt chart to the "Product Number Complete Set Rate" dimension value (set thresholds: green > 90%, yellow 70-90%, red < 70%), bind the trend chart to the historical complete set rate data of each product number; configure the interaction logic, set that when a task in the Gantt chart is clicked, the trend chart will automatically focus on displaying the complete set rate change of the product number associated with that task, and set that when the complete set rate is lower than 70%, an early warning entry will be automatically generated in the risk warning list.

[0069] Finally, the view is published and rendered in real time. After configuration, clicking the publish button generates a link. When an end user accesses the view, the front-end rendering engine loads the view definition file, sends a data query request to the data warehouse according to the data source configuration in the definition, combines the query results with the component configuration, and renders the final visual interface. The system establishes a WebSocket connection, and automatically pushes updates when the source data changes, realizing real-time refresh of the view.

[0070] Please see Figure 3 This is a schematic diagram of the tire project visualization view generation system based on a data service bus provided in Embodiment 2 of this disclosure. The tire project visualization view generation system 100 based on a data service bus provided in this disclosure includes: The data service bus module 10 is used to acquire project source data from several existing business systems of the tire project through the data service bus, and convert the project source data into standardized data; wherein, the existing business systems include PLM system, U9 system, and OA system; The data warehouse construction module 20 is used to establish cross-system data relationships based on the standardized data and calculate project data dimensions to construct a dedicated data warehouse for the tire project. Establishing cross-system data relationships includes: associating design tasks from the PLM system with procurement requirements from the U9 system using material codes and project production numbers; associating purchase orders from the U9 system with inventory materials using material codes; and associating approval nodes from the OA system with project stages using project production numbers and process types. The project data dimensions include production number availability rate, design-procurement-production linkage progress, customer project association, and cross-system critical path dimensions. View configuration module 30 is used to provide a configuration interface for users using a low-code view generator; The view generation module 40 is used to read data from the tire project-specific data warehouse based on the user's configuration operations on the configuration interface and generate a visual view.

[0071] In some implementations, the data service bus module includes an adapter for a PLM system, an adapter for a U9 system, and an adapter for an OA system; the data service bus module connects to existing business systems via an Enterprise Service Bus (ESB) or API gateway.

[0072] In some implementations, the low-code view generator includes: A visualization component library that provides chart components for tire projects; The data dimension selection and configuration panel provides an interface for selecting project data dimensions and configuring project parameters. The view canvas and interaction logic configuration area is used to provide view layout and interaction configuration functions.

[0073] In some implementations, the system also includes a display terminal module for displaying visual views.

[0074] Understandably, the aforementioned functional modules can be stored in memory as software programs and executed by a processor. In alternative embodiments, the aforementioned functional modules can also be hardware with specific functions, such as chips programmed with specific software.

[0075] It should be noted that, in implementation, the tire project visualization view generation method based on the data service bus can be implemented using the aforementioned tire project visualization view generation system 100 based on the data service bus. The tire project visualization view generation system 100 based on the data service bus can achieve the generation of low-code visualization views of tire projects based on the data service bus, realizing full-process management of tire projects, by employing one or more specific embodiments of the tire project visualization view generation method based on the data service bus described in the above embodiments. That is, all embodiments of the tire project visualization view generation method based on the data service bus provided in this disclosure are applicable to the tire project visualization view generation system 100 based on the data service bus provided in this disclosure, and all can achieve the same or similar beneficial effects, which will not be elaborated upon here.

[0076] Please see Figure 4 This disclosure also provides an electronic device, including: a memory 210 and one or more processors 220.

[0077] Specifically, the memory 210 is used to store one or more computer programs; when the one or more computer programs are executed by one or more processors 220, the tire project visualization view generation method based on the data service bus described in Embodiment 1 is implemented.

[0078] The memory 210 may be, but is not limited to, Random Access Memory (RAM), Read Only Memory (ROM), Programmable Read-Only Memory (PROM), Erasable Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), etc. The memory 210 stores programs, and the processor 220 runs these programs after receiving execution instructions to implement the tire project visualization view generation method based on the data service bus described in Embodiment 1. It is understood that access to the memory 210 by the processor 220 and other possible components can be performed under the control of the memory controller.

[0079] The processor 220 may be an integrated circuit chip with signal processing capabilities. The processor 220 may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc., or it may be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, capable of implementing or executing the methods and steps disclosed in Embodiment 1 of this disclosure.

[0080] This disclosure also provides a computer storage medium storing a computer program, which, when executed by a processor, implements the tire project visualization view generation method based on a data service bus as described in Embodiment 1 above.

[0081] This disclosure also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implement the tire project visualization view generation method based on a data service bus as described in Embodiment 1 above.

[0082] The above description is merely an embodiment of this disclosure and does not limit the patent scope of this disclosure. Any equivalent structural or procedural transformations made using the content of this disclosure and its drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this disclosure.

Claims

1. A method for generating a visual view of a tire project based on a data service bus, characterized in that, Includes the following steps: The project source data is obtained from several existing business systems of the tire project through a data service bus, and the project source data is converted into standardized data; wherein, the existing business systems include PLM system, U9 system, and OA system; Based on the standardized data, cross-system data relationships are established and project data dimensions are calculated to construct a dedicated data warehouse for the tire project. Establishing cross-system data relationships includes: associating design tasks from the PLM system with procurement requirements from the U9 system using material codes and project production numbers; associating purchase orders from the U9 system with inventory materials using material codes; and associating approval nodes from the OA system with project stages using project production numbers and process types. The project data dimensions include production number availability rate, design-procurement-production linkage progress, customer project association, and cross-system critical path dimensions. A low-code view generator is used to provide a configuration interface for users; Data is read from the tire project's dedicated data warehouse based on the user's configuration operations on the configuration interface, and a visualization view is generated.

2. The method for generating a visual view of a tire project based on a data service bus as described in claim 1, characterized in that, The project source data includes design data from the PLM system, supply chain and production data from the U9 system, and approval flow data from the OA system.

3. The method for generating a visual view of a tire project based on a data service bus as described in claim 1, characterized in that, Obtain project source data from the existing business system of the tire project and convert the project source data into standardized data, including: Proactively acquire project source data from various existing business systems; The source data of the project is cleaned and transformed to form standardized data that conforms to the tire project data model; The standardized data is synchronously updated according to preset rules or preset events.

4. The method for generating a visual view of a tire project based on a data service bus as described in claim 1, characterized in that, The low-code view generator includes a library of visualization components for project management; Based on the user's configuration operations on the configuration interface, data is read from the tire project's dedicated data warehouse to generate a visualization view, including: The configuration interface displays project parameters and project data dimensions; Receives user selections of project parameters and project data dimensions on the configuration interface; Receive drag-and-drop operations from users, such as dragging chart components from the visualization component library onto the canvas; Bind the dragged chart components to the selected project parameters and project data dimensions to complete the visualization view configuration.

5. The method for generating a visual view of a tire project based on a data service bus as described in claim 4, characterized in that, Based on the user's configuration operations on the configuration interface, data is read from the tire project's dedicated data warehouse to generate a visualization view, which also includes: Once the configuration is complete, a visual view link will be generated; When an end user clicks the visualization view link, the visualization view is loaded; Based on the visualization view configuration operation, a data query request is initiated to the tire project's dedicated data warehouse; Combine the query results of the data query request with the visualization view component to render the final visualization view and display it.

6. The method for generating a visual view of a tire project based on a data service bus as described in any one of claims 1-5, characterized in that, When the source data of the project changes, updates are automatically pushed to achieve real-time refresh of the visualization view.

7. A tire project visualization view generation system based on a data service bus, characterized in that, This can be achieved through the following modules: The data service bus module is used to acquire project source data from several existing business systems of the tire project through the data service bus, and convert the project source data into standardized data; wherein, the existing business systems include PLM system, U9 system, and OA system; The data warehouse construction module is used to establish cross-system data relationships based on the standardized data and calculate project data dimensions to build a dedicated data warehouse for the tire project. Establishing cross-system data relationships includes: associating design tasks from the PLM system with procurement requirements from the U9 system using material codes and project production numbers; associating purchase orders from the U9 system with inventory materials using material codes; and associating approval nodes from the OA system with project stages using project production numbers and process types. The project data dimensions include production number availability rate, design-procurement-production linkage progress, customer project association, and cross-system critical path dimensions. The view configuration module is used to provide a configuration interface for users using a low-code view generator. The view generation module is used to read data from the tire project's dedicated data warehouse based on the user's configuration operations on the configuration interface and generate a visual view.

8. The tire project visualization view generation system based on a data service bus as described in claim 7, characterized in that, The data service bus module includes an adapter for PLM systems, an adapter for U9 systems, and an adapter for OA systems; the data service bus module connects to existing business systems via Enterprise Service Bus (ESB) or API gateway.

9. The tire project visualization view generation system based on a data service bus as described in claim 7, characterized in that, The low-code view generator includes: A visualization component library that provides chart components for tire projects; The data dimension selection and configuration panel provides an interface for selecting project data dimensions and configuring project parameters. The view canvas and interaction logic configuration area is used to provide view layout and interaction configuration functions.

10. The tire project visualization view generation system based on a data service bus as described in claim 7, characterized in that, It also includes a display terminal module for displaying visual views.

11. An electronic device, characterized in that, include: Memory and one or more processors; The memory is used to store one or more computer programs; When the one or more computer programs are executed by the one or more processors, the method for generating a tire project visualization view based on a data service bus as described in any one of claims 1-6 is implemented.

12. A computer storage medium storing a computer program; characterized in that, When the computer program is executed by the processor, it implements the tire project visualization view generation method based on any one of claims 1-6.

Images