Industrial full-link through implementation method based on unique identification and double contract anchoring

Abstract

The application discloses an industrial full-link through implementation method based on unique identification and double contract anchoring, and belongs to the technical field of intelligent manufacturing informatization. The method takes a plan number as a unique and unchangeable identification throughout the full life cycle from raw material warehousing to finished product warehousing, takes a contract hash value as a cross-table association anchor point, adopts a step-by-step anchoring mechanism of sales contract priority binding and procurement contract subsequent binding, and combines batch processing, transaction safety control and full-chain backtracking synchronization technology to realize bidirectional synchronous updating of procurement and sales contract information in full life cycle data tables such as raw material inventory tables and production process quality inspection record tables. The application breaks the strong coupling of the procurement and production processes, supports cost information post-recording, solves the pain points of data disconnection, untraceability, low efficiency and maintenance difficulty of traditional industrial software, has a simple architecture, high performance and stable operation, and is suitable for various intelligent manufacturing systems such as MES and ERP. The application has been applied in actual industrial scenes and has industrialization popularization capability.

Description

Technical Field

[0001] This invention relates to the fields of industrial production informatization, intelligent manufacturing MES and ERP system architecture technology, specifically a method for end-to-end industrial data connectivity based on unique through identifiers, dual contract hash anchoring, step-by-step binding, and post-event backtracking and synchronous updates. Background Technology

[0002] Existing industrial production management software generally suffers from problems such as data fragmentation, complex relationships, easily broken links, and difficulty in traceability. Traditional architectures separate procurement, production, and inventory data, resulting in cumbersome multi-table relationships that lead to low system performance. Furthermore, the procurement process is strongly coupled with the production process; without binding procurement information, production scheduling or editing of production data is impossible, severely impacting production efficiency. Simultaneously, completed production records cannot be retrospectively updated with cost and contract information, leading to discrepancies between accounts and actual production, and inconsistent data across the entire supply chain. Existing systems lack a unique and stable identifier spanning the entire lifecycle from raw materials to finished products, making accurate cross-table relationships and batch processing impossible. They often employ a single-record processing approach, which is inefficient, has poor transaction security, and disperses business logic across multiple modules, making system maintenance difficult and failing to meet the management needs of modern industrial production for high efficiency, stability, and flexibility. Summary of the Invention

[0003] This invention addresses the shortcomings of existing technologies by proposing a method for achieving end-to-end industrial connectivity based on unique identifiers and dual-contract anchoring. Through technologies such as unique identifiers for plan numbers and volume numbers, step-by-step anchoring of sales / procurement dual contracts, batch processing, transaction security control, and end-to-end backtracking and synchronization, it fundamentally solves industry pain points such as data disconnection, process blockage, lack of traceability, and low efficiency, achieving decoupling of production and cost, end-to-end data connectivity, and unified encapsulation of business logic.

[0004] The technical solution of this invention specifically includes the following core steps: The plan number and volume number are defined as unique, unchanging identifiers from raw material warehousing and processing at each stage to finished product warehousing. This identifier is written into all industrial production lifecycle data tables, such as the raw material inventory table and the production process quality inspection record table. It serves as the unique primary key for precise cross-table association, penetrating query, and backtracking synchronization, ensuring the uniqueness and stability of the data link and laying the foundation for seamless data flow across the entire chain.

[0005] The dual-contract phased anchoring and binding adopts a phased mechanism that prioritizes sales contracts and follows with procurement contracts, thereby decoupling production and cost processes. The binding and unbinding operations of the two contracts are both implemented through a unified batch processing entry point, ensuring the consistency of business logic. Sales contract binding: Prioritize the batch binding of sales contract information to the corresponding data table, synchronize information such as product specifications, delivery targets, salespersons, and unit prices in sales orders, and use it as the core basis for production planning. This does not rely on purchase contract information and ensures the normal progress of the production process. Purchase contract binding: Purchase contract information can be added and bound after production is completed or during the production process. It is mainly used to determine the source of raw materials, unit price, cost and supplier information. The binding operation does not block production scheduling or affect the production records that have been generated, thus decoupling production and cost.

[0006] Contract hash values ​​are used for precise cross-table association. A unique contract hash value is generated for each sales and purchase contract, serving as the anchor point for cross-table associations. This enables accurate matching of contract information with raw material inventory and production process quality inspection data. After a sales contract is bound, the contract hash value is used to associate it with the sales order details table, synchronizing production and settlement information. Similarly, after a purchase contract is bound, the contract hash value is used to associate it with the purchase order details table, synchronizing cost and supplier information, thus avoiding data corruption caused by multi-table associations.

[0007] Unified batch processing and transaction security control use table-valued parameters as a unified data entry point, supporting the batch import of information such as multiple raw material volume numbers, contract numbers, contract hash values, bound parties, and operation types into a unified stored procedure. This stored procedure uniformly encapsulates all business logic for binding and unbinding procurement and sales contracts. By identifying the operation type, it automatically executes corresponding multi-table linked updates, reducing the number of front-end and back-end interactions and improving system efficiency. All contract binding, unbinding, and cross-table synchronization operations are wrapped in database transactions. If any step in the transaction fails, all executed update operations will be rolled back, ensuring that updates to the raw material inventory table and the production process quality inspection record table succeed simultaneously or fail simultaneously, avoiding data inconsistencies, dirty data, and intermediate states, and guaranteeing data security.

[0008] When binding or unbinding a procurement contract, the system automatically retrieves all completed production process quality inspection records using the plan number and volume number as unique association keys. It synchronously updates information such as the procurement contract number, procurement contract hash value, raw material unit price, and total price, enabling post-event supplementation and retrospective updating of procurement contract information. This ensures consistency between the raw material inventory table and the production process quality inspection record table across the entire production chain, guaranteeing that completed production records are traceable and reconcilable.

[0009] Flexible unbinding of binding relationships: When the specifications and materials of materials do not match the requirements of the original sales contract, the binding relationship of the original sales contract can be unbound with one click through the unified storage process. Only the contract-related information is cleared, while core identification fields such as plan number, volume number, and contract hash value are retained to ensure that the materials can be rebound in the future, providing data support for flexible production. Beneficial effects

[0010] Compared with the prior art, the present invention has the following significant advantages: Production and cost are decoupled, and the process is unobstructed: The mechanism of prioritizing sales contracts and binding purchase contracts later is adopted. The binding of purchase information does not depend on the production process, and production scheduling does not need to wait for purchase contracts. It also supports the retroactive entry of cost information, which completely solves the problem of strong coupling of traditional architecture processes and ensures production efficiency and delivery timeliness. Full-chain data traceability and penetration: Using the plan number and volume number as unique and unchanging identifiers, it runs through the entire life cycle from raw materials to finished products. Combined with the contract hash value, it enables precise cross-table association, realizing full data traceability and penetration query of raw material source, contract information, production process, etc. at any stage; High batch processing efficiency: Data is input in batches using table-valued parameters and batch processing is achieved through a unified stored procedure. The processing efficiency is much higher than the traditional single-row processing method, which is suitable for the large-scale data processing needs of industrial production. High data security and consistency: The entire process adopts a transaction security control mechanism to avoid dirty data and intermediate states, and the procurement contract binding supports full-link backtracking and synchronization to ensure that the information in all data tables such as raw material inventory, production process quality inspection, etc. is consistent and the accounts match the actual situation; The architecture is simple, easy to maintain and extend: business logic is uniformly encapsulated into a unified stored procedure, there are no redundant SQL statements on the front end, the wide table structure reduces multi-table joins, the system is easy to maintain, and subsequent new business only requires extending the stored procedure logic, which has strong scalability; Highly flexible and adaptable to actual production needs: It supports the flexible unbinding of binding relationships, retains core identification fields, provides data support for subsequent rebinding of materials, and adapts to actual scenarios such as material specification deviations and contract adjustments in industrial production. High engineering maturity: This method has been fully implemented in actual industrial ERP systems and can run stably in real production environments for a long time. It has mature engineering value and industrial promotion capabilities, and is suitable for various discrete intelligent manufacturing industries such as steel and machinery manufacturing. Detailed Implementation

[0011] The following detailed description of the specific implementation of this invention is based on a real-world application scenario of an MES system in the steel manufacturing industry. This embodiment involves four core data tables: a hot-rolled coil warehouse information table (raw material inventory table), a production process quality inspection record table, a sales order details table, and a purchase order details table. All data tables use a plan number / coil number field as a unique identifier. Sales contracts and purchase contracts generate unique contract hash values ​​as cross-table association anchors. SQL Server database table-valued parameters and a unified stored procedure are used to achieve batch processing and business logic encapsulation. The front-end uses a unified public function to implement parameter encapsulation and stored procedure calls. Implementation Step 1: Batch Binding of Sales Contracts

[0012] The front end collects information such as the raw material roll number / finished product roll number, sales contract number, contract hash value, binding person, binding address, etc. to be bound, sets the operation type to bind contract, encapsulates it as a table-valued parameter, and calls the unified stored procedure BangDingXiaoShouHeTongOrCancel; The stored procedure initiates a database transaction, first batch updating information such as sales contract number, contract hash value, bound person, bound address, and bound time to the hot-rolled coil warehouse information table and the production process quality inspection record table; Using the contract hash value as the association key, the sales order details table is linked, and information such as salesperson, delivery deadline, and unit price are updated synchronously to the above two data tables. The total price of the steel coil is automatically calculated as: unit price × finished product weight. If all update operations are executed successfully, commit the transaction and return a successful binding and the number of volumes processed to the front end; if any step fails, roll back all operations and return a binding failure message. Implementation Step 2: Post-event registration and binding of procurement contracts

[0013] During the production process, the front end collects information such as the raw material roll number, purchase contract number, purchase contract hash value, purchaser, supplier, and raw material unit price to be bound. The operation type is set to bind contract, encapsulated as table-valued parameters, and the unified stored procedure BangDingCaiGouHeTongOrCancel is called. The stored procedure initiates a transaction, first batch updates the purchase contract information, supplier, and unit price in the hot-rolled coil warehouse information table, and then calculates the total raw material price = incoming material weight × unit price; Using the plan number and volume number as the unique association key, the purchase contract number, purchase contract hash value and other information in the production process quality inspection record table are updated retrospectively and synchronously to realize the supplementary entry of purchase information that has been produced; After verifying that all data tables have been updated successfully, commit the transaction; if it fails, roll back and return a message indicating that the data entry failed. Implementation Step 3: Flexible Decoupling of Sales Contracts

[0014] When the material of a raw material roll does not match the requirements of the original sales contract, the front end collects the raw material roll number, sets the operation type to binding release, encapsulates it as a table-valued parameter, and calls the unified stored procedure of the sales contract. The stored procedure starts a transaction and only clears contract-related information such as sales contract number, bound person, and bound address from the hot-rolled coil warehouse information table and the production process quality inspection record table, while retaining core identifier fields such as plan number, coil number, and contract hash value. If the operation is successful, the transaction is committed and a success message is returned; if it fails, the transaction is rolled back to ensure data consistency. Implementation Step 4: Unbinding the Procurement Contract and Synchronizing the Full-Chain Backtracking

[0015] When the purchase contract information needs to be modified, the front end collects the raw material roll numbers to be unbound, sets the operation type to unbind, encapsulates it as a table-value parameter, and calls the unified stored procedure for purchase contracts. The stored procedure starts a transaction and first clears the purchase contract-related information in the hot-rolled coil warehouse information table. Using the plan number and volume number as the association key, the system automatically backtracks and retrieves all associated production process and quality inspection records, clears the procurement contract information, and achieves synchronized updates across the entire supply chain. If the operation succeeds, the transaction is committed; if it fails, it is rolled back.

[0016] This embodiment is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. All equivalent modifications made based on the technical solutions of the present invention fall within the protection scope of the present invention.

Claims

1. A method for achieving end-to-end industrial connectivity based on unique identifiers and dual contract anchoring, characterized in that, Includes the following steps: The plan number and volume number are set as a unique identifier that runs through all industrial production lifecycle data tables, such as the raw material inventory table and the production process quality inspection record table. This serves as the unique primary key for precise cross-table association, penetrating positioning, and backtracking synchronization. A step-by-step binding mechanism for sales contracts and purchase contracts is adopted. Sales contracts are bound in batches first, followed by purchase contracts. Purchase contract binding is not strongly coupled with the production process and supports binding during or after production. Both binding and unbinding operations are implemented through a unified batch processing entry point. Using contract hash values ​​as cross-table association anchors, we can achieve precise association between sales and procurement contract information and raw material and production data. After a sales contract is bound, production information such as product specifications and delivery requirements are synchronized. After a procurement contract is bound, cost information such as raw material costs and suppliers is synchronized. All contract binding, unbinding, and cross-table update operations are wrapped by transaction safety mechanisms to ensure that update operations on the raw material inventory table and the production process quality inspection record table are successful or rolled back simultaneously, avoiding the generation of dirty data and intermediate states. When binding or unbinding a procurement contract, the plan number and volume number are used as unique association keys to automatically backtrack and synchronously update the contract information and cost information in the raw material inventory table and the production process quality inspection record table that has been produced, so as to achieve data consistency across the entire chain. When materials do not match the original sales contract, the original binding relationship is removed through unified processing logic, while the core identification fields are retained to provide data support for subsequent rebinding of materials.

2. The method according to claim 1, characterized in that, Step 2) Prioritizing the binding of sales contracts involves batch updating information such as the sales contract number, contract hash value, binding person, and binding address to the corresponding data table. At the same time, it links the sales order details table and synchronously fills in production and settlement information such as salesperson, delivery deadline, and unit price, which serves as the core basis for production planning and does not depend on purchase contract information.

3. The method according to claim 1, characterized in that, Step 2) The specific binding of the purchase contract is as follows: the purchase contract number, purchase contract hash value, purchaser, supplier, raw material unit price and other information are updated in batches to the raw material inventory table, and the corresponding purchase information in the production process quality inspection record table is updated retrospectively and synchronously with the plan number and roll number as the association key. At the same time, the total price of raw materials, the total price of finished steel coils and other cost data are automatically calculated without blocking the existing production process.

4. The method according to claim 1, characterized in that, The unified batch processing entry point mentioned in step 2) is a unified stored procedure that encapsulates all business logic for binding / unbinding sales and purchase contracts. It batch-transmits multiple raw material roll numbers, contract information and operation instructions through table-value parameters, reducing the number of interactions between the front-end and back-end and realizing a unified interface for business logic.

5. The method according to claim 1, characterized in that, Step 5) describes the full-link backtracking and synchronization of historical data that has been completed in production. Even if the production process has ended, cost information can still be supplemented and refreshed through the binding of procurement contracts, ensuring that the data of raw material inventory, production process quality inspection and other full-link data are consistent with the actual situation.

6. The method according to claim 1, characterized in that, Both the raw material inventory table and the production process quality inspection record table adopt a wide table structure design, which centrally stores contract information, process information and cost information throughout the entire life cycle, reducing multi-table associations and redundant calculations. The front end only needs to call a unified public function to realize data interaction, without redundant SQL statements.