A low-code-based production and sales system rapid customization method

Abstract

This application provides a method for rapid customization of production and sales systems based on low-code. Through low-code visual configuration and component reuse, it significantly shortens the development cycle, and plug-in extensions avoid system reconstruction, reducing development and maintenance manpower costs, while also minimizing system upgrade and adaptation costs. It is applicable to multiple industries such as steel, manufacturing, and metallurgy, and is particularly suitable for production and sales scenarios in process manufacturing. It can quickly customize production and sales modules to suit different enterprise sizes and business models, while supporting multi-terminal adaptation and improving management convenience. Compared with traditional customized development, the plug-in extension mechanism does not require modification of the system's core code, enabling on-demand addition, removal, upgrading, and iteration of business functions. It adapts to enterprise business upgrades, new scenarios, and multi-site management needs, offering high flexibility, efficient data collaboration, convenient operation and maintenance, and improved system stability and availability.

Description

Technical Field

[0001] This invention relates to the field of production and sales management technology, specifically to a method for rapid customization of a production and sales system based on low-code, applicable to multiple industries such as steel, manufacturing, and metallurgy, and particularly suited to the full-process production and sales management needs of process manufacturing industries. Background Technology

[0002] With the deepening of industrial digital transformation, the demand for production and sales collaborative management systems in process manufacturing industries such as steel, manufacturing, and metallurgy is becoming increasingly urgent. Enterprises typically run multiple existing information systems in parallel: for example, ERP handles functions such as sales, materials, shipping, finance, and macro planning / cost accounting; WMS / warehousing and logistics systems manage warehouse locations, receiving and shipping, and batch flow; metering systems (rail scales / truck scales / crane scales, etc.) provide measurement vouchers and weight data for incoming and outgoing materials; and MES / process machine or production line control systems are responsible for issuing process-level operation instructions and collecting production data.

[0003] As the core link connecting a company's sales orders and production execution, the production and sales system needs to handle the entire process of business, including order management, production planning, production scheduling, inventory delivery, and data statistics in real time. It also needs to collaborate with heterogeneous systems from multiple sources, such as ERP, WMS, and metering systems, to ensure the efficient operation of the company's production.

[0004] However, existing production and sales systems mostly adopt traditional customized code development models. Under this model, the system architecture is typically highly coupled, and changes to business logic often involve extensive modifications to the underlying core code. Especially when enterprises upgrade their business, add new business scenarios (such as steel companies adding heat treatment processes), or need to adapt to centralized management across multiple bases, existing technologies lack flexible expansion mechanisms. This usually requires redeveloping or refactoring the system, resulting in development cycles lasting several months and extremely high manpower and trial-and-error costs, making it impossible to quickly respond to the rapid iteration needs of enterprise businesses. Summary of the Invention

[0005] This application provides a method for rapid customization of production and sales systems based on low code, which solves the problem of excessively long customization development cycles caused by high code coupling in traditional production and sales systems.

[0006] This application provides a method for rapid customization of a low-code production and sales system, the method comprising: A low-code production and sales system is constructed, comprising an operations and maintenance layer, a configuration layer, a component layer, an engine layer, and a data layer. The operations and maintenance layer is configured to perform system monitoring; the configuration layer is configured to provide a visual interactive interface to receive user commands; the component layer is configured to store encapsulated business function units; the engine layer is configured to parse configuration information, schedule the execution order of business components, handle data transmission, and manage system access permissions; and the data layer is configured to handle data storage and transmission. Based on the pre-defined business in the production and sales process business list, multiple business components are encapsulated, and pre-defined business logic, standard data interfaces and pre-defined configuration parameters are configured for the business components. In response to the user's selection, layout, and parameter configuration of business components in the drag-and-drop visual editor of the low-code platform, a business customization request is generated; based on the business customization request, the corresponding first business component is selected, and the running parameters, business flow process, and data association relationship of the first business component are configured to generate production and sales business module configuration information; the production and sales business module is an independent business unit generated by the configuration layer, containing specific business processes and component configurations; The configuration information of the production and sales business module is sent to the engine layer, which then parses the configuration information and calls the corresponding business components to render and generate a runnable production and sales business module. When a business expansion requirement is detected, the corresponding business expansion plugin is obtained, and the business expansion plugin is registered to the system through a pre-set expansion interface. The plugin scheduling module built into the engine layer dynamically calls the business expansion plugin according to the operational requirements of the production and sales business module. The plugin scheduling module is configured to manage the lifecycle of the plugin and allocate plugin execution resources as needed. During the operation of the production and sales business module, a communication connection is established with at least one third-party system, including the ERP system, WMS system, and metering system, through the data layer to perform real-time data synchronization and format conversion; The operation and maintenance layer collects the operating indicators of the production and sales business modules. When abnormal data is detected, an alarm mechanism is triggered, and the parameter configuration of the business components is dynamically adjusted according to the configuration policy.

[0007] In some possible implementations, the operational metrics of the production and sales business module collected through the operations and maintenance layer include: The system monitors the operation status, component call status, and data transmission efficiency of the production and sales business module in real time, and collects system operation indicators, including at least one of component response time, data transmission latency, and system load. Set up a tiered alarm mechanism and predefine at least one of the following abnormal trigger conditions: component call failure, data transmission delay, configuration error, or data anomaly. When the above-mentioned abnormal triggering conditions are detected, an alarm message is issued and an abnormal log is recorded to the operation and maintenance layer.

[0008] In some possible implementations, the operations and maintenance layer is also configured to perform log management, which includes: Record all operation logs, exception logs, and runtime logs of the aforementioned production and sales business module; In response to a fault investigation or problem tracing request, the operation log, exception log or running log is retrieved to locate the system fault point; Based on the analysis results of the operation logs, exception logs, or running logs, a business process defect handling strategy is generated.

[0009] In some possible implementations, the method also includes dynamic optimization and version management through the operations and maintenance layer, including: Based on the system's operating status and changes in the enterprise's business, at least one of the customized production and sales business modules, component configurations, and extended plugins should be dynamically adjusted to optimize business processes and system performance, and achieve continuous adaptation between the system and the enterprise's business. The customized versions of the production and sales business modules, the component versions of the business components, and the plugin versions of the extended plugins are managed in a unified manner. In response to a version rollback command, perform a version rollback operation based on stored historical version data, or perform a version comparison and version release operation.

[0010] In some possible implementations, the engine layer has a built-in plugin registration module, plugin scheduling module, and plugin management module; The plugin registration module is configured to receive business extension plugins, perform identity verification and version registration on the business extension plugins, and generate a valid plugin identifier. The plugin scheduling module is configured to dynamically call the business extension plugin with a valid plugin identifier according to the running node and business requirements of the production and sales business module, and return the execution result of the plugin to the production and sales business module. The plugin management module is configured to perform installation, uninstallation, version upgrade, and runtime status monitoring operations on the business extension plugins, and to update the plugins.

[0011] In some possible implementations, the plugin registration module performs identity verification and registration of the business extension plugin, including: Verify the validity of the digital signature of the business extension plugin to ensure the plugin's origin is trustworthy; Check whether the version number of the business extension plugin is compatible with the current low-code production and sales system version to avoid version conflicts; Confirm whether all dependencies of the business extension plugin have been installed. If any dependencies are missing, refuse registration and prompt the user to install the missing dependencies. After all verifications are passed, a unique plugin identifier is assigned to the business extension plugin, and the basic information of the plugin is stored in the system plugin library.

[0012] In some possible implementations, the engine layer incorporates a low-code rendering engine, a process scheduling engine, a data interaction engine, and a permission control engine. The rendering engine is configured to render the visual configuration results into a runnable business interface in real time. The process scheduling engine is configured to coordinate the execution order of various business components to achieve automated flow of production and sales business processes; The data interaction engine is configured to handle data transmission and format conversion between components and between the system and third-party platforms; The access control engine is configured to assign permissions for component invocation, configuration modification, and data viewing based on roles, ensuring the security of business data.

[0013] In some possible implementations, multiple business components are encapsulated based on pre-defined business processes in the production and sales process business list, including: A modular encapsulation approach is adopted, encapsulating each business component into an independent unit containing a component identifier, configuration parameters, business logic scripts, and data interfaces; The component identifier is used to uniquely identify the business component, the configuration parameters are used to adapt to different business scenarios, the business logic script is used to implement preset business functions, and the data interface is used to interact with other components or systems; and the components communicate with each other through a standardized interface, which uses the same protocol specification.

[0014] In some possible implementations, responding to user operations on selecting, laying out, and configuring parameters of business components in a drag-and-drop visual editor on a low-code platform also includes: The configuration layer displays the business rule configuration interface, which provides configuration options for order splitting rules, production scheduling priority rules, inventory warning rules, and sales statistics rules. In response to the user's drop-down selection or parameter input operation of the configuration options, business rule configuration data is generated; The business rule configuration data is sent to the engine layer, where the process scheduling engine loads and executes the business rules.

[0015] In some possible implementations, the preset business functions of multiple business components are encapsulated based on the preset business functions in the production and sales process business list, including: order management, production planning, production scheduling, production performance, inventory delivery, data statistics, and report generation.

[0016] As described above, this application provides a method for rapid customization of a low-code production and sales system. Through low-code visual configuration and component reuse, it significantly shortens the development cycle, and plug-in extensions avoid system reconstruction, reducing development and maintenance manpower costs, while also minimizing system upgrade and adaptation costs. It is applicable to multiple industries such as steel, manufacturing, and metallurgy, especially suitable for production and sales scenarios in process manufacturing. It can quickly customize production and sales modules to suit different enterprise sizes and business models, while supporting multi-terminal adaptation and improving management convenience. Compared with traditional customized development, the plug-in extension mechanism does not require modification of the system's core code, enabling on-demand addition, removal, upgrading, and iteration of business functions. It adapts to enterprise business upgrades, new scenarios, and multi-site management needs, offering high flexibility, efficient data collaboration, convenient operation and maintenance, and improved system stability and availability. Attached Figure Description

[0017] To more clearly illustrate the technical solution of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating the method for rapid customization of a low-code-based production and sales system provided in this application.

[0019] Figure 2 This is a schematic diagram of a low-code production and sales system provided in an embodiment of this application.

[0020] Figure 3 A schematic diagram of the low-code-based rapid customization method for a production and sales system provided in Embodiment 1 of this application. Figure 1 .

[0021] Figure 4 A schematic diagram of the low-code-based rapid customization method for a production and sales system provided in Embodiment 1 of this application. Figure 2 .

[0022] Figure 5 This is a schematic diagram of a multi-base production and sales application architecture for steel enterprises provided in an embodiment of this application. Detailed Implementation

[0023] This application provides a method for rapid customization of production and sales systems based on low-code. This method builds the basic framework of the production and sales system on a low-code platform. Through component-based encapsulation, visual configuration, and plug-in extension, it enables rapid customization, flexible adjustment, and dynamic expansion of production and sales business modules. The core includes six steps: infrastructure construction, business component encapsulation, visual customization configuration, plug-in extension, data collaboration and linkage, and full-process operation and maintenance monitoring. It is compatible with production and sales scenarios across multiple industries, especially suitable for process manufacturing industries such as steel. Business customization can be completed without excessive development, significantly shortening the development cycle and reducing development costs. It also supports on-demand addition, removal, and functional upgrades of business modules, achieving dynamic adaptation of the production and sales system to enterprise development and improving the efficiency and intelligence level of the production and sales system.

[0024] In some embodiments, such as Figure 1 As shown, the method for rapid customization of a low-code-based production and sales system provided in this application includes the following steps.

[0025] S1: Build a low-code production and sales infrastructure (low-code production and sales system) A five-layer low-code production and sales infrastructure is constructed, with each layer working together to provide stable support for business customization and expansion, as detailed below: Engine Layer: As the core support layer, it includes a low-code rendering engine, a process scheduling engine, a data interaction engine, and a permission control engine. It is responsible for rendering the business interface, scheduling the process, transmitting data, and managing permissions to ensure the stable operation of the system. The engine layer also has a built-in plugin registration module, a plugin scheduling module, and a plugin management module, which respectively complete plugin verification and registration, dynamic invocation, and full lifecycle management. Component Layer: Encapsulates the core components of the entire production and sales process, forming the basis for business customization. Components cover order management, production planning, production scheduling, production operations, inventory delivery, sales management, data statistics, report generation, etc. Each component contains preset business logic, data interfaces, and configurable parameters, supporting independent calls and combinations. Configuration layer: Provides a drag-and-drop visual editor and parameter configuration interface. Users can customize business modules by dragging and dropping components and configuring parameters without writing code. It also supports visual configuration of business rules. Data layer: Responsible for data storage, processing and collaboration, including database, data interface adaptation module, data standardization module, to achieve unified management of production and sales data and collaboration of multi-source data, and to break down data barriers with third-party systems such as ERP and WMS; Operations and Maintenance Layer: Responsible for the full-process operation and maintenance monitoring of the system, including component operation monitoring, data transmission monitoring, anomaly alarms, log management and version management, to ensure the stable operation of the system.

[0026] S2: Core components for packaging and sales business By adopting a modular and standardized encapsulation approach, the core business processes throughout the production and sales chain are broken down into independent, reusable components, as specifically implemented below: Component decomposition: According to the production and sales business process, business links such as order entry, order review, order splitting, production planning, production scheduling optimization, production performance, inventory query, inventory warning, outbound management, sales statistics, and report generation are decomposed into independent components, with each component focusing on a single business function; Component encapsulation: Each component contains a component identifier, configuration parameters, business logic scripts, and data interfaces. The component encapsulates the preset business logic and reserves configurable parameters. Users can adjust the parameters according to enterprise needs to adapt to different business scenarios. Component standardization: Unify the interface specifications and data formats of components to ensure that components can communicate through standardized interfaces, support hot updates, reuse and flexible combination of components, and reduce redundant development.

[0027] S3: Visualized Custom Configuration of Production and Sales Business Modules A visual editor based on the configuration layer enables rapid customization of production and sales business modules without writing underlying code. The specific process is as follows: Component selection: Users can select the required business components from the component layer, such as order management components, production scheduling components, production performance components, and inventory delivery components, through a drag-and-drop visual editor, and drag them to the editing interface to complete the layout of the components; Parameter configuration: For each selected component, you can set the component parameters through the configuration interface, such as the order type and approval process of the order management component, the production priority and capacity constraints of the production scheduling component, and the safety stock threshold of the inventory component. The parameter configuration supports real-time preview. Process configuration: Through the visual process editor, configure the business flow logic between each component, such as automatically triggering the production plan formulation after the order is approved, and automatically synchronizing to the production scheduling module after the production plan is completed, so as to realize the automated flow of business processes; Rule configuration: Set production and sales business rules, including order splitting rules, production scheduling priority rules, inventory warning rules, sales statistics rules, etc. Rule configuration is completed through drop-down selection and parameter input. The rule configuration takes effect in real time after confirmation and can be dynamically modified. Preview and Release: After completing the customized configuration, you can preview the running effect of the business module through the preview function. Once you confirm that everything is correct, you can release it to the production environment with one click to complete the rapid deployment of the business module.

[0028] S4: Plug-in-based dynamic expansion of business functions Based on the infrastructure's extension interfaces, a plug-in mechanism is used to dynamically extend business functions without modifying the system's core code. The specific implementation is as follows: Plugin Development: Develop corresponding extension plugins based on new business requirements. Plugin types include plugins for new business functions, data integration plugins, and third-party system integration plugins. Plugin development follows a unified interface specification. Plugin registration: Upload the completed plugin to the low-code platform, complete the identity verification and registration through the plugin registration module, obtain the plugin identifier, and ensure the legality and compatibility of the plugin; Plugin activation and scheduling: Users can activate corresponding plugins through the plugin management interface according to their business needs. The plugin scheduling module automatically calls the plugins according to the business process and configuration to achieve the integration of new functions. S5: Enables collaborative linkage of production and sales data By employing data layer technologies, we break down data barriers between low-code production and sales systems and third-party systems, enabling real-time synchronization and collaboration of data across the entire production and sales process. Specifically: Data interface adaptation: For third-party systems such as ERP, WMS, and metering, develop corresponding interface adaptation modules to realize data interface docking between different systems and support bidirectional data transmission; Data standardization processing: Through the data standardization module, production and sales data (such as order data, production data, and inventory data) from different sources and in different formats are standardized, cleaned, and anonymized to ensure data consistency and accuracy; Real-time data synchronization: Establish a real-time data synchronization mechanism to achieve real-time synchronization of order data, production plan data, production scheduling data, production data, actual performance data, inventory data, and sales data, ensuring data consistency across all business processes and guaranteeing a closed-loop business process; Data correlation analysis: Through the data correlation module, the relationship between various business data is established, such as the relationship between order data, production data, and inventory data, so as to realize the linkage query and analysis of data and provide data support for enterprise decision-making.

[0029] S6: End-to-End Operation and Maintenance Monitoring and Optimization By implementing end-to-end monitoring and continuous optimization of the production and sales business system through the operations and maintenance layer, the system's stable operation is ensured, as detailed below: Operation monitoring: Real-time monitoring of the operational status of business modules, component invocation, and data transmission efficiency; collection of system operation metrics, such as component response time, data transmission latency, and system load. Anomaly Alarms: Set up a tiered alarm mechanism. When the system encounters problems such as component call failure, data transmission delay, configuration error, or data anomaly, it will automatically issue alarm information to notify the operation and maintenance personnel to handle it in a timely manner, and record the anomaly log at the same time. Log management: Completely records the system's operation logs, running logs, and exception logs. The running logs continuously collect operational metrics such as component response time, plugin resource usage, and API call frequency. Dynamic optimization: Based on the system's operating status and changes in enterprise business, the customized business modules, component configurations, and extended plugins are dynamically adjusted to optimize business processes and system performance, achieving continuous adaptation between the system and enterprise business; Version management: Unified management of customized versions, component versions, and plugin versions of business modules, supporting version rollback, version comparison, and version release, avoiding system failures caused by accidental operations, and ensuring system stability and traceability.

[0030] This application solves the expansion problem caused by the high coupling of code in traditional production and sales systems from the underlying architecture through component-based encapsulation and a five-layer architecture design. It enables the system to achieve "hot-swappable" addition and removal of business functions through a plug-in mechanism, thereby reducing the customization cycle from months to days without modifying the core code, combined with visual drag-and-drop configuration. At the same time, the standardized data interface derived from this architecture effectively breaks down the data barriers between heterogeneous systems such as ERP and WMS, ensuring real-time collaboration of multi-source data and closed-loop processes. Furthermore, it achieves dynamic adjustment of system performance and version traceability through full lifecycle operation and maintenance monitoring, ultimately achieving a unified system for rapid delivery, flexible expansion, and stable operation of production and sales systems in multiple industries and scenarios.

[0031] Example 1 This embodiment uses the addition of a heat treatment module to the production and sales operations of a steel company as an example to illustrate the specific application process of the low-code-based rapid customization method for production and sales systems proposed in this application. This steel company is a multi-base group enterprise with three production bases. Its production and sales operations involve order management, production planning, production scheduling, production operations, inventory delivery, sales statistics, and multi-base collaboration. Base A adds a heat treatment process and possesses equipment such as heat treatment furnaces, quenching machines, straightening machines, cooling beds, sampling shears, and marking machines. Traditional production and sales systems cannot adapt to the needs of multi-base collaboration and rapid business iteration. After adopting the method provided in this application, the specific implementation steps are as follows: Step 1: Basic Architecture Setup The system establishes a low-code production and sales infrastructure. The engine layer deploys a rendering engine, a process scheduling engine, a data interaction engine, and a permission control engine to achieve interface rendering, process scheduling, and permission management. The component layer encapsulates core components such as order management, production planning, production scheduling, production performance, inventory management, sales statistics, and multi-site collaboration. The configuration layer provides a drag-and-drop visual editor. The data layer interfaces with the enterprise's existing ERP and WMS systems to achieve data collaboration. The operations and maintenance layer deploys monitoring and log management modules to achieve end-to-end operations and maintenance.

[0032] Among them, such as Figure 2 The composition of the low-code production and sales infrastructure (low-code production and sales system) shown is as follows: Operations and maintenance layer: includes operation monitoring module, anomaly alarm module, log management module, and version management module.

[0033] The logs collected by the operations and maintenance layer are divided into three categories: 1. Operation logs: record human operations such as account login, component drag-and-drop configuration, plugin installation and activation, and version release; 2. Run logs: record runtime data such as component response time, API call frequency, system load, and plugin resource usage; 3. Exception logs: record fault information such as data transmission failure, component call errors, parameter configuration errors, and API timeouts.

[0034] The operations and maintenance layer sets up a three-tiered alarm mechanism: Level 1 alarms are minor delays, which are only logged in the system background; Level 2 alarms are component call timeouts and data synchronization interruptions, which push in-system messages to operations and maintenance personnel; Level 3 alarms are core component failures and a large number of data anomalies, which push SMS and platform alarms simultaneously. The system predefines four types of trigger conditions: component call failure, data transmission delay exceeding the threshold, configuration error, and data logic anomaly. When the corresponding indicator is detected, the corresponding alarm level is matched and a prompt is pushed.

[0035] Configuration layer: includes a visual editor, parameter configuration module, process configuration module, rule configuration module, and production and sales business module generated from the configuration.

[0036] Component layer: includes order management component, production planning component, production scheduling component, inventory management component, sales management component, and extended plug-in component.

[0037] Engine layer: includes rendering engine, process scheduling engine, data interaction engine, permission control engine, and built-in plugin scheduling module.

[0038] The plugin scheduling module manages the entire lifecycle of plugins, covering the states of plugins awaiting activation, running, paused, and uninstalled / destroyed. At the same time, it dynamically allocates plugin execution resources based on the current CPU, memory, and database connection pool load of the system, and limits the number of concurrent calls to non-core plugins in high-load scenarios to ensure that core production and sales business components have priority in occupying system resources.

[0039] Data layer: includes database, interface adaptation module, data standardization module, and data association module.

[0040] Step 2: Business Component Encapsulation Based on the characteristics of steel enterprises' production and sales operations, core components are packaged, including: an order entry component (supporting multi-base order differentiation and order specification entry), an order splitting component (supporting order splitting by production line and base), a production planning component (supporting multi-base planning collaboration), a production scheduling component (supporting production scheduling for hot rolling and cold rolling production lines), an inventory management component (supporting unified inventory query and early warning across multiple bases), a sales statistics component (supporting statistics by base and product type), and a multi-base collaboration component (supporting cross-base order allocation and capacity sharing). Each component has reserved configurable parameters, such as the production scheduling component which can be configured with production scheduling priority and capacity constraints, and the inventory component which can be configured with a safety stock threshold.

[0041] Step 3: Customize Business Modules like Figure 3 As shown, users can drag and drop to select the required components using the visual editor to customize the multi-base production and sales business module. Layout configuration: Drag and drop the order management, production planning, production scheduling, production operation, inventory delivery, sales statistics, and multi-site collaboration components to the editing interface to complete the module layout; Parameter configuration: Set the order type (regular order, urgent order) and review process (base review → group review) for the order management component; set the production priority (urgent orders first, high value-added products first) and capacity constraints (capacity limit of each base's production line) for the production scheduling component; set the safety stock threshold for the inventory component (raw material inventory ≥ 600 tons, finished product inventory ≥ 1000 tons). Process configuration: Configure business flow logic. After the order is approved, the production plan is automatically triggered. The production plan is allocated to each base. The production scheduling module of each base completes the scheduling according to the plan. The production performance is synchronized to the inventory module. The inventory module updates the inventory data in real time. The sales module performs sales scheduling based on the inventory data. Rule configuration: Set order splitting rules (split by product specifications and base capacity), inventory warning rules (automatic alarm when below the safety stock threshold), and multi-base collaboration rules (prioritize the allocation of orders from bases with sufficient capacity); Preview and Release: After confirming that the module is running correctly in the preview, it can be released to the production environment with one click. The entire customization process takes only 3 working days, which is significantly shorter than the traditional development cycle.

[0042] Step 4: Business Function Expansion like Figure 4 As shown, Base A has added a heat treatment module business requirement, which necessitates the expansion of the production and sales system. This can be achieved using a plug-in expansion approach. Plug-in development: Develop heat treatment process module plug-ins (supporting order entry, heat treatment process standards, and performance management), heat treatment furnace area docking plug-ins (three heating furnaces and two quenching machines), straightening machine area docking plug-ins (straightening machine, cooling bed, and surface inspection), and finished product area docking plug-ins (sampling shear and marking machine); Plugin Registration and Activation: Developed plugins are uploaded to the low-code platform via the system's pre-built standardized extension interface. The plugin registration module performs identity verification, version compatibility verification, dependency verification, and registration. Once verification is successful, a unique plugin identifier is assigned. Plugin Scheduling: Through the configuration interface, the heat treatment module workflow is set. After the heat treatment plan is entered, the system automatically calls the production and sales system's interface plugins to obtain order information, and calls the interface plugins for the heat treatment furnace area, straightening machine area, and finished product area to synchronize logistics information, achieving the integration of heat treatment business. The entire extension process does not require modification of the system's core code, and online testing was completed in just one working day.

[0043] Step 5: Data Collaboration and Operation & Maintenance Monitoring The data layer has a built-in dedicated interface adapter module for process equipment. It designs standardized data interaction interfaces for offline process equipment such as heat treatment heating furnaces, quenching machines, straightening machines, cooling beds, sampling shears, and marking machines, unifies the data format collected by the equipment, and realizes bidirectional transmission and synchronous conversion of equipment production performance and process parameters.

[0044] like Figure 5 As shown, the data layer enables data synchronization between the low-code production and sales system and the enterprise ERP, WMS system, and heat treatment area. Order data, production data, inventory data, and logistics data are synchronized in real time to ensure a closed-loop business process. The operation and maintenance layer monitors the system's operating status in real time. When there is a delay in the transmission of heat treatment order data, an alarm is automatically issued, and operation and maintenance personnel can promptly investigate and handle the problem. At the same time, log management is used to trace the cause of the problem and ensure the stable operation of the system.

[0045] After adopting the method provided in this application, the customization cycle of the steel company's production and sales business module was shortened from 3 months to 3 working days, realizing multi-base production and sales collaborative management and control, and the new heat treatment business was quickly launched. This effectively solved the shortcomings of the traditional production and sales system and adapted to the rapid iteration of enterprise business and multi-scenario needs.

[0046] As described above, this application provides a method for rapid customization of a low-code production and sales system. Through low-code visual configuration and component reuse, it significantly shortens the development cycle, and plug-in extensions avoid system reconstruction, reducing development and maintenance manpower costs, while also minimizing system upgrade and adaptation costs. It is applicable to multiple industries such as steel, manufacturing, and metallurgy, especially suitable for production and sales scenarios in process manufacturing. It can quickly customize production and sales modules to suit different enterprise sizes and business models, while supporting multi-terminal adaptation and improving management convenience. Compared with traditional customized development, the plug-in extension mechanism does not require modification of the system's core code, enabling on-demand addition, removal, upgrading, and iteration of business functions. It adapts to enterprise business upgrades, new scenarios, and multi-site management needs, offering high flexibility, efficient data collaboration, convenient operation and maintenance, and improved system stability and availability.

Claims

1. A method for rapid customization of a production and sales system based on low-code, characterized in that, The method includes: A low-code production and sales system is constructed, comprising an operations and maintenance layer, a configuration layer, a component layer, an engine layer, and a data layer. The operations and maintenance layer is configured to perform system monitoring; the configuration layer is configured to provide a visual interactive interface to receive user commands; the component layer is configured to store encapsulated business function units; the engine layer is configured to parse configuration information, schedule the execution order of business components, handle data transmission, and manage system access permissions; and the data layer is configured to handle data storage and transmission. Based on the pre-defined business in the production and sales process business list, multiple business components are encapsulated, and pre-defined business logic, standard data interfaces and pre-defined configuration parameters are configured for the business components. In response to the user's selection, layout, and parameter configuration of business components in the drag-and-drop visual editor of the low-code platform, a business customization request is generated; based on the business customization request, the corresponding first business component is selected, and the running parameters, business flow process, and data association relationship of the first business component are configured to generate production and sales business module configuration information; the production and sales business module is an independent business unit generated by the configuration layer, containing specific business processes and component configurations; The configuration information of the production and sales business module is sent to the engine layer, which then parses the configuration information and calls the corresponding business components to render and generate a runnable production and sales business module. When a business expansion requirement is detected, the corresponding business expansion plugin is obtained, the business expansion plugin is registered to the system through a pre-set expansion interface, and the plugin scheduling module built into the engine layer dynamically calls the business expansion plugin according to the operation requirements of the production and sales business module. During the operation of the production and sales business module, a communication connection is established with at least one external object among the ERP system, WMS system, metering system, and offline process equipment through the data layer to perform real-time data synchronization and format conversion; The operation and maintenance layer collects the operating indicators of the production and sales business modules. When abnormal data is detected, an alarm mechanism is triggered, and the parameter configuration of the business components is dynamically adjusted according to the configuration policy.

2. The method for rapid customization of a low-code production and sales system according to claim 1, characterized in that, The operational metrics collected by the operations and maintenance layer for the production and sales business module include: The system monitors the operation status, component call status, and data transmission efficiency of the production and sales business module in real time, and collects system operation indicators, including at least one of component response time, data transmission latency, and system load. Set up a tiered alarm mechanism and predefine at least one of the following abnormal trigger conditions: component call failure, data transmission delay, configuration error, or data anomaly. When the above-mentioned abnormal triggering conditions are detected, an alarm message is issued and an abnormal log is recorded to the operation and maintenance layer.

3. The method for rapid customization of a production and sales system based on low-code as described in claim 1, characterized in that, The operations and maintenance layer is also configured to perform log management, which includes: Record all operation logs, exception logs, and runtime logs of the aforementioned production and sales business module; In response to a fault investigation or problem tracing request, the operation log, exception log or running log is retrieved to locate the system fault point; Based on the analysis results of the operation logs, exception logs, or running logs, a business process defect handling strategy is generated.

4. The method for rapid customization of a low-code production and sales system according to claim 3, characterized in that, The method also includes dynamic optimization and version management through the operations and maintenance layer, including: Based on the system's operating status and changes in the enterprise's business, at least one of the customized production and sales business modules, component configurations, and extended plugins should be dynamically adjusted. The customized versions of the production and sales business modules, the component versions of the business components, and the plugin versions of the extended plugins are managed in a unified manner. In response to a version rollback command, perform a version rollback operation based on stored historical version data, or perform a version comparison and version release operation.

5. The method for rapid customization of a production and sales system based on low-code according to claim 1, characterized in that, The engine layer has a built-in plugin registration module, plugin scheduling module, and plugin management module. The plugin registration module is configured to receive business extension plugins, perform identity verification and version registration on the business extension plugins, and generate a valid plugin identifier. The plugin scheduling module is configured to dynamically call the business extension plugin with a valid plugin identifier according to the running node and business requirements of the production and sales business module, and return the execution result of the plugin to the production and sales business module. The plugin management module is configured to perform installation, uninstallation, version upgrade, and runtime status monitoring operations on the business extension plugins, and to update the plugins.

6. The method for rapid customization of a low-code production and sales system according to claim 5, characterized in that, The plugin registration module performs identity verification and registration for the business extension plugin, including: Verify the validity of the digital signature of the business extension plugin; Check whether the version number of the business extension plugin is compatible with the current version of the low-code production and sales system; The plugin registration module confirms whether all dependencies of the business extension plugin are installed. If there are any missing dependencies, it refuses to register and prompts the user to install the missing dependencies. After all verifications are passed, a unique plugin identifier is assigned to the business extension plugin, and the basic information of the plugin is stored in the system plugin library.

7. The method for rapid customization of a low-code production and sales system according to claim 1, characterized in that, The engine layer includes a low-code rendering engine, a process scheduling engine, a data interaction engine, and a permission control engine. The rendering engine is configured to render the visual configuration results into a runnable business interface in real time. The process scheduling engine is configured to coordinate the execution order of various business components to achieve automated flow of production and sales business processes; The data interaction engine is configured to handle data transmission and format conversion between components and between the system and third-party platforms; The access control engine is configured to assign permissions for component invocation, configuration modification, and data viewing based on roles, ensuring the security of business data.

8. The method for rapid customization of a low-code production and sales system according to claim 1, characterized in that, Based on the pre-defined business processes in the production and sales process business list, multiple business components are encapsulated, including: A modular encapsulation approach is adopted, encapsulating each business component into an independent unit containing a component identifier, configuration parameters, business logic scripts, and data interfaces; The component identifier is used to uniquely identify the business component, the configuration parameters are used to adapt to different business scenarios, the business logic script is used to implement preset business functions, and the data interface is used to interact with other components or systems.

9. The method for rapid customization of a low-code production and sales system according to claim 1, characterized in that, In response to user operations on selecting, laying out, and configuring parameters of business components in the drag-and-drop visual editor of the low-code platform, the following also applies: The configuration layer displays the business rule configuration interface, which provides configuration options for order splitting rules, production scheduling priority rules, inventory warning rules, and sales statistics rules. In response to the user's drop-down selection or parameter input operation of the configuration options, business rule configuration data is generated; The business rule configuration data is sent to the engine layer, where the process scheduling engine loads and executes the business rules.

10. The method for rapid customization of a low-code production and sales system according to claim 1, characterized in that, The pre-defined business components based on the pre-defined business in the production and sales process business list include: order management, production planning, production scheduling, production performance, inventory delivery, multi-base collaboration, data statistics, and report generation.

Images