A business flexible customization platform based on a unified industrial business object model and an implementation method thereof

Abstract

The application discloses a business flexible customization platform and method based on a unified industrial business object model and belongs to the technical field of industrial internet. The platform is divided into a wisdom-linking and fusing support layer, a data center module, a flexible customization configuration module and a multi-terminal adaptation module from bottom to top. The data center is built-in with the unified industrial business object model, contains five types of objects, namely, work orders, work procedures, equipment states, production batches and quality results, is associated with a full-service function module set and uniformly standardizes full-link data semantics. The flexible customization configuration module completes no-code configuration through a visual engine, supports one-key publishing and rapid rollback. The multi-terminal adaptation module realizes bidirectional real-time synchronization of Web and APP, supports offline caching and cross-terminal breakpoint resumption. The application solves the problems of data islands of existing platforms, high customization development cost, multi-terminal business fragmentation and multi-tenant data drift, shortens the digital delivery cycle of manufacturing enterprises and is suitable for manufacturing industries such as building materials, machinery and edible fungi.

Description

Technical Field

[0001] This invention relates to the field of industrial internet technology, and in particular to a flexible business customization platform and method based on a unified industrial business object model, applicable to digital transformation scenarios of enterprises in machinery manufacturing, electronic manufacturing, equipment manufacturing, new building materials, ceramic building materials, edible fungi industry and other industries.

[0002] The term "industrial unified object model" as used in this specification and claims refers to a unified industrial business object model, which includes work order objects, process objects, equipment status objects, production batch objects, and quality result objects, and the objects have fixed industrial semantic relationships. Background Technology

[0003] 1. Existing industrial digital platforms have four major technical defects: inconsistent semantics of multi-source data, drift of data caliber among multi-tenant systems, and lack of unified standards for work orders, processes, equipment, quality inspection, and batches in MES, WMS, ERP, and equipment IoT systems; conflicting data definitions after deployment for multiple customers and projects, semantic gaps in cross-system collaboration, and data statistical distortion.

[0004] 2. Customization relies on underlying code, resulting in high delivery costs and long cycles. Traditional platforms require backend developers to modify code to change processes, forms, and permissions. General low-code platforms lack industry-specific object constraints, leading to higher data structure entropy and more chaotic data with more customized instances. There is no one-click rollback maintenance mechanism, resulting in long recovery times for production line failures.

[0005] 3. Web and APP terminal data are synchronized in one direction and cannot be resumed after interruption. The existing system only synchronizes static data of documents and does not synchronize approval sessions and process context; after a work order is initiated on the computer, the mobile phone cannot continue the operation, and there is no caching and synchronization capability in offline workshop scenarios.

[0006] 4. The links between equipment data acquisition, business modeling, and customized terminals are fragmented. There is no standardized data flow link between the equipment acquisition layer, business function layer, data standardization layer, customized configuration layer, and access terminal layer. Each module operates independently and cannot share a set of industrial data model constraints, resulting in poor overall scalability.

[0007] Currently, while some low-code-based industrial manufacturing management systems support generating business processes through visual drag-and-drop, their configuration and deployment still require backend services to be recompiled and deployed, making it impossible to achieve seamless activation. Furthermore, the lack of a unified industrial data model leads to inconsistencies in data standards among multiple tenants.

[0008] While some other industrial internet data platform systems have achieved the integration of equipment data collection and business data, their data models are defined separately for each business system, and no unified object association relationship has been established across systems. The problem of data semantic heterogeneity still exists, and their terminal synchronization adopts an HTTP polling mechanism, resulting in high synchronization latency and easy data loss in offline scenarios.

[0009] In addition, although some industrial platforms have version management functions in their configuration management, their rollback mechanism requires a service restart to take effect, which cannot meet the high availability requirements in the scenario of continuous production on industrial production lines.

[0010] In summary, existing MES, WMS, and general low-code platforms generally suffer from these problems, lacking an integrated solution with a complete bottom-up chain, unified industrial business object model constraints, no-code visual configuration, and multi-terminal bidirectional real-time synchronization. Furthermore, existing industrial internet platforms often adopt a 'siloed' architecture, with each business system (such as MES and WMS) defining its own data model, leading to heterogeneous data semantics. Simultaneously, adjustments to business processes typically require modification of the underlying source code and recompilation and deployment, resulting in system lag and failing to meet the demands of flexible manufacturing. In addition, data synchronization between mobile and PC terminals often uses polling mechanisms, resulting in high latency and data loss during network outages. Summary of the Invention

[0011] 3.1 Purpose of the Invention This invention aims to solve the technical problems of semantic heterogeneity in industrial data, system rigidity caused by hard-coded business logic, and high latency in multi-terminal data synchronization in existing technologies. Addressing the shortcomings of existing technologies such as data silos, high customization costs, fragmented multi-terminal services, and fragmented links, this invention provides a layered and progressive platform architecture to achieve the following objectives: 1. The unified industrial business object model predefines the metadata architecture of work orders, processes, equipment status, production batches and quality results, and establishes physical association constraints (such as foreign key constraints) across objects; this model serves as the sole data standard for the data platform, forcing all incoming data to conform to the preset schema, thereby achieving semantic consistency of data across the entire chain.

[0012] Build a unified industrial business object model covering work orders / processes / equipment / batches / quality, unify data semantics across the entire chain, and eliminate multi-tenant data drift; build a built-in visual configuration engine, allowing pure configuration customization without modifying the underlying code, and the configuration file supports one-click deployment and quick rollback.

[0013] In the five-layer architecture, this model acts as a 'data semantic bus': downwards, it maps the heterogeneous device data points uploaded by the intelligent connectivity and integration support layer to the model's standard attributes; upwards, it constrains all configuration JSON files generated by the flexible custom configuration module to conform to the association relationships defined by the model, ensuring that the business processes and data forms finally presented to the multi-terminal adaptation module are always strictly consistent with the underlying original device data in terms of semantics.

[0014] 2. Real-time bidirectional synchronization of process context between Web and APP terminals, supporting offline caching in the workshop and cross-terminal resume of interrupted processes; 3. Establish a complete closed-loop data flow encompassing equipment acquisition, data standardization, business functions, flexible customization, and multi-terminal access, with each layer decoupled and independently expandable.

[0015] 3.2 Technical Solution Option 1: A flexible business customization platform based on a unified industrial business object model, as shown in the attached document. Figure 1 As shown, the platform is deployed in layers from bottom to top, namely: Intelligent Connection and Integration Support Layer 1, Full Business Process Functional Module Set 2, Data Platform Module 3, Flexible Customized Configuration Module 4, and Multi-Terminal Adaptation Module 5; the bottom layer connects to industrial equipment, and the top layer provides dual-terminal access capabilities to the outside world. The unified industrial business object model includes five types of structured data objects: work order objects, process objects, equipment status objects, production batch objects, and quality result objects. Each object establishes a fixed association through key fields: work order objects are associated with process objects through work order numbers; process objects are associated with equipment status objects through equipment numbers; production batch objects are associated with work order objects through batch numbers; and quality result objects are associated with production batch objects through quality inspection batch numbers. The model has built-in semantic validation rules: When configuring the release, the validation process object must be bound to the corresponding work order, and the quality result object must be bound to the production batch object. Field type mismatch and missing association are judged as semantic conflicts, and the release is intercepted and the conflict point is reported. Multi-tenants share a unified set of industrial business object model metadata, while tenant business instances are stored in independent databases. The model metadata and tenant business data are isolated and mapped through the tenant ID, ensuring global data standardization while maintaining physical isolation of tenant data. Based on the model, a reverse traceability chain can be realized: quality result object → production batch object → work order object → process object → equipment status object, to fully trace the equipment parameters of abnormal production processes.

[0016] 1. Intelligent Connectivity and Integration Support Layer 1 It has a built-in multi-protocol gateway, edge preprocessing unit, real-time cleaning unit, and time-series storage unit; the multi-protocol gateway connects to industrial equipment such as PLCs, sensors, and machine tools, and is compatible with ModbusTCP and MQTT industrial protocols; it sequentially completes protocol parsing, edge invalid message filtering, real-time data deduplication / completion / anomaly marking, and the time-series database stores the time-series data of the devices; it outputs standardized data streams to the data platform module 3.

[0017] 2. Data Platform Module 3 It receives standardized device data streams from the Intelligent Connectivity and Integration Support Layer 1, and has built-in cleaning, standardization, and modeling processing units; the data platform has two core units for bidirectional association. Unified Industrial Business Object Model: Predefines five core object categories—work order, process, equipment status, production batch, and quality result—along with fixed semantic relationships, serving as the underlying mandatory constraint for data and customized configuration across the entire platform; Full business process functional module set 2: includes microservices for sales, procurement, production, MES, warehousing, equipment, quality inspection, approval, and system management. Each module is loosely coupled and can be deployed pluggably. The data platform relies on a unified industrial business object model to unify and organize equipment data and business document data, connects to the equipment acquisition layer at the bottom, and provides a standardized data foundation for flexible customized configuration modules at the top.

[0018] 3. Flexible Custom Configuration Module 4 The system incorporates a built-in web-based visual configuration engine, storing all configurations in JSON files. The flexible custom configuration module 4 includes a built-in configuration version management unit, employing an incremental storage mechanism to maintain a version snapshot chain for each configuration file. Each configuration release only stores the incremental difference between the current version and the previous version, generating a timestamped version snapshot file. One-click release is supported; in case of an anomaly, a version rollback command is triggered. The system automatically retrieves the snapshot file of the previous stable version, reverse-engineers the complete configuration based on the incremental records, and overwrites the current running configuration, achieving minute-level rapid rollback without recompiling or restarting the service. User configuration operations are received through a visual interactive interface, mapping business processes to JSON structured configuration files conforming to the unified industrial business object model specification. During configuration release, the data platform performs syntax analysis and semantic loop detection on the JSON file, generating executable intermediate code or scripts, which are dynamically loaded into the business module's runtime environment without modifying the underlying source code. Specifically, the template engine uses predefined code templates to match the node types in the abstract syntax tree to the corresponding business microservice interface calls, generating executable scripts or bytecode, which are then dynamically loaded and executed by the business module's class loader.

[0019] The flexible customization configuration module 4 sends the drag-and-drop generated process rules and form configurations to the data platform module 3 for verification. The data platform, based on the unified industrial business object model, verifies whether there are semantic conflicts in the configuration rules, such as process objects not being associated with their respective work orders, quality result objects not being bound to production batch objects, or data field types not matching. If the verification passes, a release permission signal is returned; otherwise, the conflict points are fed back to the configuration layer, and the implementers adjust the configuration before submitting it for release.

[0020] 4. Multi-terminal adaptation module 5 It includes web and mobile app versions, and establishes a long-connection channel based on the WebSocket protocol to achieve full-duplex communication between the server and the client. In offline scenarios, the client generates a local cache database based on a unified industrial business object model. After the network is restored, conflict detection is performed by exchanging data version vectors (VersionVector), and incremental data is merged using a 'server-first' strategy to achieve cross-terminal breakpoint resume.

[0021] The cross-terminal breakpoint continuation is implemented as follows: When the APP is offline, the document data, the current process node ID, and the approval session context are cached locally in a structured format according to the unified industrial business object model; when synchronizing online, the Web client and the APP client exchange the version number of the current process node through WebSocket. If the versions are consistent, the incremental data is merged; if the versions conflict, the latest version saved in the data platform shall prevail; after synchronization is completed, the process status and the filled content on both ends are automatically aligned to achieve seamless continuation of processing.

[0022] Furthermore, in multi-tenant scenarios, customized instances and basic platforms are physically isolated and stored in separate databases, with all tenants sharing the same unified industrial business object model, taking into account both data security and global data standardization.

[0023] Furthermore, the platform's data flow is a bottom-up closed loop: industrial equipment → intelligent connectivity and integration support layer → data platform → flexible customized configuration module → multi-terminal adaptation module, with terminal operation data being transmitted back to the data platform to complete the full-domain update.

[0024] Solution 2: A method for flexible customization of business based on a unified industrial business object model, comprising the following steps: S1, such as Figure 2 The underlying device standardization data acquisition is shown: The intelligent integration support layer collects raw data from machine tools, sensors, and PLCs through a multi-protocol gateway. After edge preprocessing and real-time cleaning, it generates a standardized data stream and pushes it to the data platform module. S2, such as Figure 2The data platform integrates data streams collected from devices with business data from functional modules across the entire business process. It relies on a unified industrial business object model to complete data standardization and indicator modeling, and generates a standardized data service platform. S3, such as Figure 2 The visualization-based, no-code flexible customization is shown below: The flexible customization configuration module calls the unified industrial business object model and basic business components, and allows users to drag and drop configuration processes, forms, interfaces, and permissions through the visualization engine to generate JSON format configuration files; it executes one-click deployment to implement business instances, and allows one-click rollback in case of exceptions; the configuration instance completes verification through bidirectional interaction with the data platform. S4, such as Figure 2 The dual-terminal bidirectional synchronous business collaboration shown: the multi-terminal adaptation module receives customized business instances, and the web terminal and APP terminal bidirectionally synchronize business data and approval session context; offline data entered by the APP is automatically synchronized online, realizing cross-terminal breakpoint continuation.

[0025] Furthermore, in step S1, edge preprocessing includes protocol conversion and jitter data filtering; real-time cleaning includes missing value completion, abnormal data marking, and duplicate data removal; and single data from the equipment is processed in milliseconds at the industrial site level.

[0026] Furthermore, in step S4, the two-way data synchronization delay between the Web client and the APP client is less than 1 second, and both ends share a unified industrial business object model to ensure semantic consistency of the interactive data.

[0027] This platform supports fully localized deployment in enterprise private environments. All device data, business data, and configuration data are stored on the client's intranet, without cloud backhaul or third-party data sharing. Under the above local deployment mode, system performance is limited by the client's hardware resource configuration. However, through edge computing offloading, structured data modeling, and lightweight communication protocol design, it can still stably meet the design indicators of millisecond-level device data processing and multi-terminal sub-second synchronization under typical industrial server configurations, making it suitable for industrial scenarios with strict requirements for data security and network isolation.

[0028] 3.3 Beneficial Effects This invention adopts a bottom-up five-layer closed-loop architecture, relying on a unified industrial business object model to constrain all devices, businesses, and customized data across the entire domain, and solves the problems of data caliber drift and semantic conflict in multiple systems and multiple tenants from the bottom layer. Flexible customization is achieved entirely through visual drag-and-drop configuration, requiring no code development and significantly shortening project delivery cycles; configurations are stored independently in JSON files, reducing fault rollback time and greatly lowering maintenance difficulty; The process context is synchronized in two-way real time between the web and the APP, supporting offline filling in the workshop and cross-terminal approval, solving the pain points of multi-terminal fragmentation and process interruption in traditional platforms; Each level of module is loosely coupled and decoupled, and the equipment acquisition, data modeling, business functions, customized configuration, and terminal access can be expanded independently in layers, allowing small and medium-sized enterprises to activate functions in stages as needed. Equipment data edge preprocessing distributes cloud computing power, and real-time cleaning reduces the computing pressure on the middle platform, meeting the millisecond-level data acquisition and control needs of industrial production lines.

[0029] This platform significantly reduces cloud computing pressure by offloading computationally intensive operations such as protocol parsing and jitter filtering to the edge of the intelligent connectivity and convergence support layer. At the same time, the bidirectional communication mechanism based on the WebSocket protocol avoids the polling overhead of the traditional HTTP request-response model. Combined with the standardized constraints of the data structure by the unified industrial business object model, it can stably achieve millisecond-level device data processing capabilities and sub-second multi-terminal synchronization performance in a local deployment environment, meeting the real-time and reliability requirements of industrial sites.

[0030] This effect is not achieved simply by relying on the data platform or the model itself, but by using the unified industrial business object model as the 'constitution' for configuration verification and the 'dictionary' for bidirectional synchronization. This ensures that any configuration that has not been verified by the model cannot be published and any semantically inconsistent data cannot be synchronized, thus eliminating the possibility of data drift from a fundamental mechanism. This is something that traditional point-based optimization solutions cannot achieve. Attached Figure Description

[0031] Figure 1 This is a schematic diagram of the full-layer architecture and data interaction of the platform of this invention; the attached figures are labeled as follows: Intelligent Connection and Integration Support Layer 1, Full Business Process Functional Module Set 2, Data Platform Module 3, Flexible Custom Configuration Module 4, Multi-Terminal Adaptation Module 5; the solid arrows in the figure represent the path of business data uplink or customized instance downlink, and the direction of the arrows represents the direction of data flow.

[0032] Figure 2 This is a flowchart illustrating the business flexibility customization implementation method of the present invention; the flowchart sequentially represents the steps of S1 standardized data collection from underlying devices, S2 unified modeling of global data, S3 visual, code-free flexible customization, and S4 bidirectional collaborative access from dual terminals, with diamond-shaped boxes representing verification and judgment nodes.

[0033] Hierarchy and data flow description: 1. The lowest level industrial equipment connects to the intelligent connectivity and integration support layer 1, and the intelligent connectivity and integration support layer 1 outputs standardized data flow to the data platform module 3. 2. The data platform module 3 is associated with the unified industrial business object model and the full business process function module set 2, respectively, and provides a data and component foundation for the flexible customized configuration module 4. 3. Flexible Custom Configuration Module 4: Built-in Web Visual Configuration Engine, enabling one-click deployment / rollback via JSON configuration, bidirectional interaction with the data platform to configure rules and instance status; Upward and Multi-Platform Adaptation Module 5: Distribute business instances. 4. The multi-terminal adaptation module 5 includes a web terminal and an app terminal, which synchronize data and process context in both directions and provide terminal operation access to the outside world; The arrows in the diagram represent the direction of data flow: device data collection uplink, bidirectional interaction of configuration rules, uplink push of customized instances, and bidirectional communication of terminal data. Detailed Implementation

[0034] Example 1: Deployment and Implementation of Refractory Building Materials Factory Platform 1. Data Acquisition from Underlying Devices (Intelligent Connectivity and Integration Support Layer 1) The refractory building material factory's kilns, molding machines, and temperature and pressure sensors are connected to a multi-protocol gateway; the edge unit filters meaningless jitter messages, unifies data units, and fills in missing data due to sensor disconnection; the time-series database stores device operating parameters in hourly segments; and standardized JSON data streams are continuously pushed to the data platform module 3, controlling the processing time of a single data item to the millisecond level for efficient data acquisition and processing.

[0035] 2. Unified Data Modeling (Data Platform Module 3) The middle platform receives equipment data streams and production, warehousing, and quality inspection business documents; retrieves standardized work orders, firing processes, kiln equipment, production batches, and quality inspection judgment standards from the unified industrial business object model; automatically calculates industrial indicators such as equipment OEE, firing yield, and inventory turnover; and simultaneously opens up the basic components of production, warehousing, and approval for the entire business process functional module set, providing flexible customized configuration modules upwards.

[0036] Work order objects are associated with process objects through the "Work Order Number" field. Each work order corresponds to at least one process node, and process nodes are arranged in a preset process sequence (such as batching → molding → firing → inspection). Process objects are associated with equipment status objects through the "Equipment Number" field, recording the operating parameters (temperature, pressure, running time, etc.) of the corresponding equipment during the execution of each process. Production batch objects are associated with work order objects through the "Batch Number" field, and one work order corresponds to one production batch. Quality result objects are associated with production batch objects through the "Quality Inspection Batch Number" field, recording the quality inspection results of the batch of products.

[0037] When the quality inspection conclusion of a certain batch of quality result objects is "unqualified", the system traces the associated work order objects through the "batch number", traces the associated process objects through the work order objects, and traces the associated equipment status objects through the process objects, forming a complete reverse traceability link of "quality result → batch → work order → process → equipment", and locking the process node where the anomaly occurred and the corresponding equipment operating parameters.

[0038] 3. No-code visual customization (flexible customization configuration module 4) Implementers log in to the Web-based visual configuration engine, drag and drop components to build multi-level approval processes for refractory brick firing, customize graded quality inspection forms, configure workshop data dashboards, and assign data access permissions by work group. All configurations are automatically generated into independent JSON files, and a single click to publish makes them effective across the entire platform. The configuration management system maintains a version snapshot chain of configuration files based on an incremental storage mechanism. When a configuration conflict or runtime anomaly is detected, a version rollback command is triggered, and the system automatically retrieves the snapshot file of the previous stable version and overwrites the current configuration, achieving minute-level fault self-healing. Configuration instances are distributed to the data platform for verification and implementation, and the instance running status is fed back to the configuration layer.

[0039] 4. Multi-device bidirectional collaborative access (multi-device adaptation module 5) Once configured, business instances are synchronized to the Web management terminal and the workshop APP terminal. Office managers can create production work orders through the Web terminal, and workshop operators can fill in molding and firing records offline using the APP in an offline environment. After the network is restored, the APP automatically synchronizes the offline data. Managers can view the quality inspection records submitted by the workshop APP on the Web terminal and continue the approval process. The process status and filled content of both ends are synchronized in real time.

[0040] Example 2: Implementation in an edible fungi manufacturing enterprise A mushroom processing company deployed this platform to complete its digital transformation: 1. The intelligent integration support layer connects to temperature and humidity sensors in the mushroom house and PLCs in the packaging production line to collect environmental and production equipment data in real time; 2. The data platform relies on a unified industrial business object model to unify the batches of mushroom bags, cultivation processes, and quality inspection standards, thereby eliminating data definition conflicts between the original warehousing and production systems; 3. By using flexible customizable configuration modules to visually build the mushroom house cultivation and control process and finished product quality inspection forms, the implementation cycle is significantly shortened compared to traditional development, and the labor implementation cost is significantly reduced; 4. Workshop employees use the APP to fill in the temperature and humidity records of the mushroom room offline, and managers approve production and outbound documents in batches on the computer, with seamless connection across terminals; when the system has a configuration failure, the rollback operation only takes a few minutes, reducing the difficulty of platform operation and maintenance and shortening the fault recovery time.

[0041] In local deployment scenarios, when the edge computing node is configured with a quad-core ARM architecture processor with a main frequency of 1.5GHz, the server is configured with an eight-core x86 architecture processor with 16GB of memory, and the network latency between the terminal and the server does not exceed 10ms, a single piece of device data can be processed in milliseconds in the industrial field, and the two-way data synchronization latency between the Web client and the APP client can be stably controlled within 1 second.

Claims

1. A flexible business customization platform based on a unified industrial business object model, characterized in that... The architecture is structured in layers from bottom to top: Intelligent Integration Support Layer 1, Full Business Process Functional Module Set 2, Data Platform Module 3, Flexible Customized Configuration Module 4, and Multi-Terminal Adaptation Module 5, forming a five-layer closed-loop architecture.

2. The intelligent interconnection and fusion support layer 1 includes a multi-protocol gateway, an edge preprocessing unit, a real-time cleaning unit, and a time-series storage unit, used to collect and standardize raw data from industrial equipment; The full business process functional module set 2 includes multiple loosely coupled and pluggable business microservices such as sales management, procurement management, production management, MES manufacturing execution, warehouse management, equipment management, quality management, approval management, and system management. Each module is loosely coupled and pluggable. The data platform module 3 incorporates a unified industrial business object model. This model predefines five object categories: work orders, processes, equipment status, production batches, and quality results, along with fixed industrial semantic relationships. This unified industrial business object model serves as the sole data semantic anchor for the entire platform, constraining the configuration generation of the flexible customization module from top to bottom and standardizing the device data mapping of the intelligent connectivity and integration support layer from bottom to top. All inflow / outflow data must pass semantic verification by this model to ensure complete consistency of data semantics across the five-layer architecture. The fixed industrial semantic relationships include: work order objects are associated with process objects via work order numbers; process objects are associated with equipment status objects via equipment numbers; and production batch objects are associated with batch numbers. The system associates work order objects and quality result objects with production batch objects via quality inspection batch numbers. The unified industrial business object model incorporates semantic validation rules. During configuration release, it verifies that process objects must be bound to corresponding work orders, and quality result objects must be bound to production batch objects. Field type mismatches or missing associations are considered semantic conflicts and release is blocked. The data platform module 3 has a built-in validation engine that performs semantic consistency validation on the JSON structured configuration file based on predefined association relationships in the unified industrial business object model. If a configuration item violates the fixed industrial semantic association relationship or has a logical conflict, the validation fails and release is blocked, generating a feedback report containing conflict information. The flexible custom configuration module 4 has a built-in web-based visual configuration engine. All configuration operations do not require modification of the underlying source code or compilation and restart of backend services. Business instances are made effective by publishing JSON format configuration files. It supports one-click deployment of business instances and one-click rollback in abnormal scenarios. During rollback, the version snapshot chain based on incremental storage automatically restores the configuration of the previous stable version. The version snapshot chain uses a directed acyclic graph structure to store the differences between versions. The rollback operation only needs to switch the current version pointer. There is no need to reload or restart any business microservices. The rollback time is no more than a few minutes. The flexible custom configuration module 4 and the data platform module 3 interact bidirectionally to configure rules and instance verification status. The multi-terminal adaptation module 5 includes a web client and an APP client. The web client and the APP client achieve bidirectional real-time data synchronization based on WebSocket. The APP client supports offline caching of documents and automatically synchronizes offline data after connecting to the network, realizing cross-terminal approval session breakpoint continuation. The data flow of each layer forms a closed loop: the uplink data collected by the industrial equipment is pushed to the data middle platform module 3 through the intelligent connection and integration support layer 1, the flexible customized configuration module 4 issues customized business instances to the multi-terminal adaptation module 5, and the terminal operation data is back-transmitted to the data middle platform module 3 for full-domain update.

3. A business flexibility customization platform based on a unified industrial business object model according to claim 1, characterized in that, The semantic consistency verification specifically adopts a graph topology-based dependency checking algorithm: the JSON structured configuration file is parsed into an object node graph, and the connection edges between nodes are traversed to detect whether there are isolated nodes that are not bound to parent objects or circular dependencies in data flow; if isolated nodes or circular dependencies are detected, conflicting nodes are located and conflict point reports are generated.

4. A business flexibility customization platform based on a unified industrial business object model according to claim 1, characterized in that, The flexible custom configuration module 4 includes a Web visualization configuration engine; the Web visualization configuration engine is used to provide a drag-and-drop interactive interface, allowing users to generate custom business processes based on the unified industrial business object model.

5. A business flexibility customization platform based on a unified industrial business object model according to claim 1, characterized in that, The intelligent connectivity and integration support layer 1 includes a multi-protocol gateway, edge computing nodes, and a time-series database. The edge computing nodes are used to clean and standardize the collected raw industrial data, mapping it to standard attributes in the unified industrial business object model. Single piece of equipment data is processed in milliseconds at the industrial site.

6. A business flexibility customization platform based on a unified industrial business object model according to claim 1, characterized in that, In the multi-terminal adaptation module 5, the Web client and the APP client synchronize business documents, process nodes and approval session contexts in real time through a WebSocket channel, and both ends share a unified industrial business object model to ensure data semantic consistency.

7. A method for flexible business customization based on a unified industrial business object model, characterized in that, Includes the following steps: S1. Standardized Data Acquisition from Bottom-Level Equipment: The intelligent integration support layer collects raw equipment data from machine tools, sensors, PLCs, etc., through a multi-protocol gateway. It then sequentially completes protocol parsing, edge invalid message filtering, real-time data deduplication, missing value completion, and anomaly marking. After processing, it generates a standardized time-series data stream and pushes it to the data platform module. Single piece of equipment data can be processed in milliseconds at the industrial site. S2. Unified Data Modeling Across the Entire Domain: The data platform module integrates standardized equipment data streams with various business documents from the full business process functional module set. Relying on a unified industrial business object model, it completes end-to-end data standardization and industrial indicator modeling. The industrial indicator modeling directly references predefined equipment status object attributes (such as temperature, pressure, and runtime) in the model for aggregation calculation, generating derived indicators such as equipment comprehensive efficiency and yield, ensuring global consistency in indicator calculation methods, and building a standardized data service foundation. The unified industrial business object model uniformly constrains the semantic relationships between work orders, processes, equipment status, production batches, and quality result objects. In multi-tenant scenarios, all tenants share the same unified industrial business object model, and tenant-customized instances are physically isolated and stored in separate databases. S3, Visualized No-Code Flexible Customization: The flexible customization configuration module calls the unified industrial business object model and basic business components, receives user configuration operations through a visual interactive interface, and maps business processes into JSON structured configuration files that conform to the unified industrial business object model specification; when the configuration is published, the data platform performs syntax analysis and semantic loop detection on the JSON file to generate executable intermediate code or scripts, which are dynamically loaded into the business module's runtime environment without modifying the underlying source code; S4. Dual-terminal bidirectional collaborative access: The multi-terminal adaptation module receives customized business instances, and the Web client and APP client bidirectionally synchronize business data and approval session context. Offline data entered via the app is automatically synchronized online, enabling cross-device continuation of services even after interruption.

8. The method for flexible customization of business based on a unified industrial business object model according to claim 5, characterized in that, All configuration operations in step S3 do not require modification of the underlying source code, nor do they require compilation and restart of the backend service.

9. A method for flexible business customization based on a unified industrial business object model according to claim 5, characterized in that, In step S4, the Web client and the APP client are synchronized in real time. Both clients share a unified industrial business object model, and all interactive data is mapped to the corresponding object attributes in the model to ensure data semantic consistency and process context continuity.

10. A business flexibility customization platform based on a unified industrial business object model according to claim 1, characterized in that, When the web client and the APP client are synchronizing, they exchange version vectors containing terminal identifiers, operation timestamps, and data version numbers. If the version vectors of the same data object are found to be inconsistent, a version conflict is determined, and a "server priority" strategy is executed. The latest version stored in the data platform module is used as the standard for forced merging, and a conflict log is recorded for users to review.

Images