A digital-twin-based material storage visual management method

Abstract

The application discloses a kind of based on digital twinning's material warehousing visual management method, it is related to material warehousing management technical field, comprising: obtaining warehousing basic data, generates warehousing digital twinning basic record and warehousing object relationship record;According to the business performance determination record of pending business document, and write into the release slice of expectation, receiving result, release receiving result and affected business document number;According to the business performance determination record, generate warehousing operation scheme, warehousing operation restriction record or warehousing operation sub-scheme;According to warehousing operation scheme and visual configuration data, generate multi-layer warehousing visual management result;According to job execution feedback data, generate job completion status record, partial completion status record or execution feedback restriction record, and write back status code and source record number.The application realizes that warehousing business state is received and visual state is synchronously updated.

Description

Technical Field

[0001] This invention relates to the field of materials storage management technology, and in particular to a materials storage visualization management method based on digital twins. Background Technology

[0002] Material warehousing management typically relies on warehouse management systems, barcode or RFID devices, storage location management rules, and work scheduling data to record and schedule operations such as material receiving, issuing, transferring, inventory counting, and freezing release. As requirements for batch management, project attribution, storage location time slot occupancy, and path resource allocation increase in warehousing scenarios, digital twin technology is increasingly being used to present warehouse space, storage location status, work orders, and resource operation in a data-driven manner. This allows managers to visualize inventory distribution, work progress, and resource occupancy.

[0003] However, existing methods still have two limitations: First, business documents, material batches, storage locations, time periods, and route resources are mostly managed as independent records, and the status continuity between outbound commitments, inbound receipts, transfer releases, and affected business documents is not continuous enough; second, the visualization results focus more on displaying location or inventory quantity, and the binding relationship between the source, source record, and associated objects and layer status is not clear enough, making it difficult to support the synchronous update of status after operation execution feedback. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a material warehousing visualization management method based on digital twins, which solves the problem that the status continuity between material warehousing business documents, material batches, storage location time periods, path resources and visualization layers is not continuous, making it difficult to synchronize the update of restricted sources and operation feedback status.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: This invention provides a method for visual management of material warehousing based on digital twins. The method includes: acquiring basic warehousing data; generating basic digital twin records for warehousing; forming warehousing object relationship records based on the correspondence between business documents, material batches, storage location time periods, path resources, and visualization status; reading pending business documents through the warehousing object relationship records; generating business performance judgment records according to document type; writing the expected release slices from outbound shipments, the receiving results from inbound shipments, the release and receiving results from transfers, and the affected business document numbers into the business performance judgment records; and reading warehousing object relationships based on the business performance judgment records. The system generates warehousing operation plans or warehousing operation restriction records based on batch commitment status, storage location time period status, route resource status, and affected business document status. When the same document corresponds to dispersed operation objects, a warehousing operation sub-plan is generated. Based on the warehousing operation plan, warehousing operation restriction records, and operation execution feedback data, the system reads the visualization configuration data, writes the operation status, restriction source, associated object, and status code and source record number generated by the feedback into the corresponding layer, generates multi-layer warehousing visualization management results and status confirmation results corresponding to the warehousing digital twin basic record version, and writes the status confirmation results into the warehousing digital twin basic record.

[0007] As a preferred embodiment of the material warehousing visualization management method based on digital twins described in this invention, the step of acquiring basic warehousing data, generating basic warehousing digital twin records, and forming warehousing object relationship records based on the correspondence between business documents, material batches, storage location time periods, path resources, and visualization status includes: when generating the basic warehousing digital twin records, the processor binds the business documents to the material batches with a commitment field, binds the material batches to the storage location with an occupancy field, binds the storage location to the scheduling time period with an occupancy time, binds the storage location to the path resources with an accessibility field, and binds the business objects to the visualization status with a status field, thereby forming warehousing object relationship records.

[0008] As a preferred embodiment of the material warehousing visualization management method based on digital twins described in this invention, the step of writing the expected release slices formed by outbound shipments, the receiving results formed by inbound shipments, the release and receiving results formed by transfer shipments, and the affected business document numbers into the business performance judgment record includes: when generating the business performance judgment record, the processor reads the quality status code, freeze status code, project ownership, validity period, committable quantity, and outbound order of the outbound shipment, filters candidate batches and generates batch commitment results, generates expected release slices based on the location of the committed batch and the completion time of the outbound plan, and writes the expected release quantity, release time, source outbound shipment, and source batch into the business performance judgment record.

[0009] As a preferred embodiment of the material storage visualization management method based on digital twins described in this invention, the step of writing the expected release slice formed by outbound, the receiving result formed by inbound, the release and receiving result formed by transfer, and the affected business document number into the business performance judgment record includes: when generating the business performance judgment record, the processor reads the remaining capacity, remaining capacity, and storage status of the candidate storage location from the inbound order; when the candidate storage location meets the receiving conditions, a direct receiving record is generated; when the current storage location does not meet the receiving conditions and there is a referenceable expected release slice, a waiting-to-release receiving record is generated; when the direct receiving quantity and the waiting-to-release receiving quantity do not cover the inbound demand, a receiving difference record is generated.

[0010] As a preferred embodiment of the material warehousing visualization management method based on digital twins described in this invention, the step of writing the expected release slice formed by outbound shipment, the receiving result formed by inbound shipment, the release and receiving result formed by transfer shipment, and the affected business document number into the business performance judgment record further includes: when generating the business performance judgment record, the processor reads the batch occupancy quantity of the outbound storage location and the receiving conditions of the target storage location from the transfer shipment order. When the outbound storage location meets the release conditions, the original storage location release record is generated. When the target storage location meets the capacity, bearing capacity, and material category conditions, the target storage location receiving record is generated. When any condition is not met, a transfer restriction record is generated. Business documents referencing the same batch, storage location, path, or resource are written into the affected business document number.

[0011] As a preferred embodiment of the material warehousing visualization management method based on digital twins described in this invention, the step of reading the warehousing object relationship record based on the business performance judgment record and generating a warehousing operation plan or warehousing operation restriction record according to the batch commitment status, storage location time period status, path resource status, and affected business document status includes: when generating a warehousing operation plan or warehousing operation restriction record, the processor first reads the batch commitment status and storage location time period status from the business performance judgment record, and then reads the path resource status and affected business document status; when none of the statuses trigger the restriction conditions, a warehousing operation plan is generated; when any of the statuses of batch, storage location time period, path resource, or affected business document triggers the restriction conditions, a warehousing operation restriction record is generated.

[0012] As a preferred embodiment of the material warehousing visualization management method based on digital twins described in this invention, the step of generating a warehousing operation sub-scheme when the same document corresponds to a distributed operation object includes: when generating a warehousing operation sub-scheme, the processor splits the distributed operation objects under the same business document according to the batch number, starting location number, target location number and operation quantity, and reads the corresponding path number, resource number and planned time respectively to generate a warehousing operation sub-scheme with the same scheme number and different sub-scheme numbers.

[0013] As a preferred embodiment of the material warehousing visualization management method based on digital twins described in this invention, the step of writing the operation status, restriction source, associated object, and status code and source record number formed by feedback into the corresponding layer includes: when generating multi-layer warehousing visualization management results, the processor reads the warehousing operation plan, warehousing operation restriction record, affected business document prompt record, inventory object set, and visualization configuration data, writes the fulfillment status of the business document into the document fulfillment layer, the batch commitment status into the batch commitment layer, the storage location occupancy and release status into the storage location time period layer, the path resource occupancy status into the path resource layer, the operation plan status into the operation plan layer, the warehousing operation restriction record into the restriction source layer, and the inventory object status into the inventory object layer; after the operation execution feedback data is formed, the processor writes the status code and source record number corresponding to the operation completion status record, the partial completion status record, or the execution feedback restriction record into the corresponding layer, the execution feedback restriction record into the restriction source layer, and the operation completion status record or the partial completion status record into the document fulfillment layer, the batch commitment layer, the storage location time period layer, the path resource layer, or the operation plan layer.

[0014] As a preferred embodiment of the material warehousing visualization management method based on digital twins described in this invention, the generation of multi-layered warehousing visualization management results and status confirmation results corresponding to the version of the warehousing digital twin basic record includes: when generating multi-layered warehousing visualization management results, the processor writes the object number, status code, source record number, associated object number, and update time into the layer display record. The source record number includes the record number corresponding to the business performance judgment record, warehousing operation plan, warehousing operation restriction record, affected business document prompt record, inventory object set, operation completion status record, partially completed status record, or execution feedback restriction record; when the same layer number, the same object number, and the same source record number correspond to at least two status codes, the primary status code is determined in the order of restricted status, pending verification status, reserved status, expected release status, current occupied status, and executable status, and the statuses not used as primary status codes are written into the auxiliary status field; the processor binds the layer display record with the version number of the warehousing digital twin basic record to form a multi-layered warehousing visualization management result corresponding to the version of the warehousing digital twin basic record.

[0015] As a preferred embodiment of the material warehousing visualization management method based on digital twins described in this invention, the step of writing the status confirmation result into the warehousing digital twin basic record includes: after reading the operation execution feedback data, the processor establishes a correspondence between the operation execution feedback data and the warehousing operation plan according to the feedback number, plan number, and sub-plan number, and generates an operation execution status record; when the feedback data meets the confirmation fields of the warehousing operation plan, an operation completion status record is generated; when the feedback quantity is less than the plan quantity and batch fulfillment is allowed, a partial completion status record is generated; when the feedback data triggers batch, quantity, location, path, or resource restrictions, an execution feedback restriction record is generated; the processor updates the multi-layer warehousing visualization management results according to the operation completion status record, the partial completion status record, or the execution feedback restriction record, and writes the status code and source record number formed by the feedback into the warehousing digital twin basic record.

[0016] The beneficial effects of this invention are as follows: By generating business performance determination records based on warehouse object relationship records, the expected release slice, receiving result, release receiving result, and affected business document number are continuously written, realizing the status connection between business documents, material batches, storage location time periods, and path resources, which supports the generation of warehouse operation plans and warehouse operation restriction records; through the linkage update of multi-layer warehouse visualization management results and execution feedback restriction records, the restriction source, source record number, and feedback status are written into the warehouse digital twin basic record, achieving the effect of continuous transmission of business status and synchronous update of visualization status. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a flowchart of a digital twin-based visual management method for material warehousing.

[0019] Figure 2 Generate a flowchart for business performance determination records.

[0020] Figure 3 Generate flowcharts for warehousing operation plans.

[0021] Figure 4 Update the flowchart for the visualization management results and execution feedback of multi-level warehouses.

[0022] Figure 5 A comparison chart showing the effective formation rate of warehousing operation solutions under different business document association scenarios.

[0023] Figure 6 A comparison chart of the completion rate of the layer status synchronization for different task execution feedback types. Detailed Implementation

[0024] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0025] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0026] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0027] Reference Figures 1-6 As one embodiment of the present invention, this embodiment provides a material warehousing visualization management method based on digital twins, including the following steps: S1. Obtain basic warehousing data, generate basic warehousing digital twin records, and form warehousing object relationship records based on the correspondence between business documents, material batches, storage location time periods, path resources, and visualization status.

[0028] In this process, the basic warehouse data includes warehouse space data, storage location attribute data, material batch data, business document data, warehouse resource data, operation rule data, and visualization configuration data. After reading the basic warehouse data, the processor generates a basic digital twin record of the warehouse according to the correspondence between business documents, material batches, storage location time periods, path resources, and visualization status.

[0029] Acquire warehouse space data, location attribute data, material batch data, business document data, warehousing resource data, operation rule data, and visualization configuration data to generate a basic record for the warehouse digital twin. This basic record stores the object relationships between warehouse space, material batches, business documents, location time periods, warehousing resources, and visualization configurations, and provides data sources for batch commitment determination, location acceptance determination, route resource determination, and visualization status generation.

[0030] Warehouse space data includes warehouse number, storage area number, shelf number, storage location number, aisle number, loading / unloading port number, temporary storage area number, verification area number, isolation area number, storage location coordinates, aisle start point, aisle end point, aisle direction, and a storage location access path table. The storage location access path table includes starting storage location number, target storage location number, loading / unloading port number, path number, path node sequence, aisle direction field, and path availability status code. The path node sequence is generated from the aisle start point, aisle end point, and aisle direction fields in the warehouse space data and is bound and stored with the starting storage location number, target storage location number, and loading / unloading port number. The path availability status code includes available, occupied, restricted, and pending confirmation, used to indicate whether the path can participate in the generation of warehousing operation plans within the corresponding resource time period.

[0031] The location attribute data includes location number, location quantity capacity, location volume capacity, maximum carrying capacity, permitted material categories, prohibited material categories, currently occupied quantity, currently occupied volume, currently occupied weight, reserved occupied quantity, reserved occupied volume, reserved occupied weight, frozen occupied quantity, frozen occupied volume, frozen occupied weight, expected release quantity, expected release volume, expected release weight, quantity to be verified, volume to be verified, weight to be verified, location time slot number, and location status code. The location time slot number is generated based on the warehouse operation plan time, the minimum scheduling time unit in the scheduling configuration table, and the operation record timestamp. The minimum scheduling time unit is read from the scheduling configuration table and can be 5 minutes, 10 minutes, 15 minutes, 30 minutes, or 60 minutes, determined according to the scheduling precision configuration of the warehouse management system. When the processor generates the storage location time slot number, it assigns the planned start time backward to the nearest scheduling time boundary and the planned finish time backward to the nearest scheduling time boundary. When the planned finish time falls exactly on a scheduling time boundary, that finish time is assigned to the start of the next scheduling time slot and is not counted twice in the previous scheduling time slot. Storage location time slots, resource time slots, and expected release time slots are all generated using the same minimum scheduling time unit.

[0032] The remaining capacity of a storage location is calculated by subtracting the currently occupied, reserved, frozen, and pending verification quantities from the storage location's capacity. The remaining usable volume of a storage location is calculated by subtracting the currently occupied, reserved, frozen, and pending verification volumes from the storage location's volume capacity. The remaining weight capacity of a storage location is calculated by subtracting the currently occupied, reserved, frozen, and pending verification weights from the maximum weight capacity. The remaining capacity, available volume, and weight of a storage location are used as the quantity, volume, and weight fields for inbound receipt, transfer receipt, and storage location restriction determination, respectively, and are not interchangeable. Storage location status codes include currently occupied, reserved, expected release, frozen, pending verification, direct receipt, awaiting release, and receipt difference. Current occupancy indicates the quantity, volume, and weight of items already physically occupied in a storage location; reserved occupancy indicates the quantity, volume, and weight of items already occupied by business documents but not yet physically delivered; expected release indicates the quantity, volume, and weight of items released by outbound or transfer orders and referenced by inbound orders; frozen occupancy indicates the quantity, volume, and weight of items that cannot participate in operational arrangements due to quality review, inventory verification, or business freeze; pending verification occupancy indicates the occupancy status where the batch number, quantity, volume, weight, or storage location number has not yet been confirmed.

[0033] Material batch data includes material number, material name, specifications, batch number, supplier number, warehousing time, production date, expiration date, quality status code, frozen status code, project ownership number, book inventory quantity, committed quantity, quantity awaiting shipment, quantity awaiting verification, available committed quantity, location number, and shipment sequence code. Quality status codes include available, pending inspection, and expired, with pending inspection indicating that the quality status of the material batch needs confirmation. Frozen status codes include unfrozen and frozen, used to indicate whether the material batch has been restricted from commitment due to business documents, quality review, or inventory verification.

[0034] When the freeze status code is unfrozen and the quality status code is available, the processor generates a committable quantity based on the book inventory quantity after deducting the committed quantity, the quantity to be shipped, and the quantity to be verified. If the result after deduction is greater than zero, the committable quantity is written to the deduction result; if the result after deduction is less than or equal to zero, the committable quantity is written to zero, and a batch quantity verification record is generated. The batch quantity verification record includes the material number, batch number, book inventory quantity, committed quantity, quantity to be shipped, quantity to be verified, deduction result, and reason for verification. The reason for verification is used to mark an anomaly in quantity deduction among the book inventory quantity, committed quantity, quantity to be shipped, or quantity to be verified. When the freeze status code is frozen, or the quality status code is pending inspection or expired, the committable quantity is written to zero, and the corresponding material batch does not participate in the candidate batch selection.

[0035] The outbound sequence code is generated based on material category rules, inbound time, expiration time, and business-specified rules. It is used to sort the committable batches under the same material number. When the processor filters candidate batches, it only reads material batches with a quality status code of "available," a "frozen" status code of "not frozen," and a committable quantity greater than zero. Material batches with pending batch quantity verification records will not participate in the batch commitment result generation until the reason for the pending verification is resolved.

[0036] Business document data includes inbound slips, outbound slips, transfer slips, return slips, inventory slips, freeze slips, and release slips. Each business document includes document number, document type, material number, required quantity, designated batch number, designated warehouse area number, project ownership number, planned start time, planned completion time, document priority code, committed quantity, pending committed quantity, and document status code. Document status codes include pending commitment, pending receipt, pending scheduling, commitment completed, commitment difference, direct receipt, awaiting release of receipt, receipt difference, in progress, completed, partially completed, and restricted. "Pending Commitment" indicates that the business document has not yet completed batch commitment or location allocation; "Pending Receipt" indicates that the inbound, return, or release order has not yet completed location receipt determination, or the receipt result has been confirmed and revoked and needs to be re-executed; "Pending Scheduling" indicates that the business performance determination record has been formed, but the warehousing operation plan has not yet been generated, or the warehousing operation plan has been confirmed and revoked and needs to be regenerated; "Executing" indicates that the warehousing operation plan corresponding to the business document has entered execution; "Completed" indicates that the operation quantity corresponding to the business document has been completed; "Partially Completed" indicates that the operation quantity corresponding to the business document has been partially completed and there is an incomplete quantity; "Restricted" indicates that the business document cannot enter the warehousing operation plan generation or cannot continue execution due to batch, location, route resources, execution feedback, or inventory status.

[0037] Warehouse resource data includes resource IDs, resource locations, resource status codes, executable operation types, resource time slot numbers, occupancy start times, and occupancy end times for forklifts, stacker cranes, conveyor equipment, barcode scanners, weighing equipment, operators, reviewers, and loading / unloading points. Resource time slot numbers are generated based on the warehouse operation plan time, the minimum scheduling time unit in the scheduling configuration table, and the resource occupancy record timestamp. The location time slot number and resource time slot number within the same operation plan use the same time window. Resource status codes include available, occupied, restricted, and pending confirmation. Executable operation types include inbound handling, shelving, outbound picking, transfer, return, inventory counting, and review. When a resource status code is occupied or restricted, the corresponding resource is not included in the resource candidate set of the warehouse operation plan. When a resource status code is pending confirmation, the processor generates a resource review record. After review confirmation confirms availability, the resource is allowed to enter the resource candidate set. If the review fails or no confirmation result is generated after the feedback confirmation time has expired, the resource is marked as restricted. When device execution feedback is missing, resource occupation end time is not formed, or resource status is not confirmed, the corresponding resource status code is marked as pending confirmation.

[0038] The operational rule data includes material category rules, validity period rules, project affiliation rules, batch commitment rules, location receiving rules, expected release reference rules, path resource occupancy rules, inventory object formation rules, and status code mapping rules. Material category rules determine whether a material category falls into a location-allowed material category and not a location-prohibited material category. Validity period rules determine whether the validity period expiration time is later than the planned completion time of the business document, and whether the remaining days between the validity period expiration time and the planned completion time are not less than the minimum remaining validity period days. The minimum remaining validity period days are configured in the material category rule table according to the material category and quality management requirements, with a value range of zero to 365 days. When the business document has a specified remaining validity period requirement, the larger value between the specified requirement and the value configured in the material category rule table is used. Project affiliation rules determine whether the project affiliation number of the material batch matches the business document's... The project ownership number is consistent; the batch commitment rule is used to determine the order and quantity of the batch's committable quantity to meet the document's demand; the location receiving rule is used to determine the inbound receiving conditions based on the location's remaining capacity, remaining available volume, remaining load capacity, and expected release quantity; the expected release referencing rule is used to limit the expected release slice to be referenced by only one inbound order within the same location time period; the path resource occupancy rule is used to determine the occupancy conditions of paths, equipment, personnel, and loading / unloading ports within the resource time period; the inventory object formation rule is used to determine whether the batch and location are included in the inventory object set; the status code mapping rule is used to determine the display record of the business status in the visualization layer.

[0039] The visualization configuration data includes layer number, layer name, object type, object number, display position, status code field, source field, and display field. Layer names include document fulfillment layer, batch commitment layer, location / time period layer, route resource layer, work plan layer, restricted source layer, and inventory object layer. Object numbers are taken from document number, batch number, location number, route number, resource number, plan number, or restricted record number, depending on the object type. The document fulfillment layer is indexed by the document number; the batch commitment layer by the batch number; the location / time period layer by the location number and location / time period number; the route resource layer by the route number, resource number, and resource time period number; the work plan layer by the plan number; the restricted source layer by the restricted record number; and the inventory object layer by the inventory sheet number and inventory object number.

[0040] The processor generates five types of relationship records based on the aforementioned data. The first type is the document-batch commitment relationship, with document number, material number, batch number, and committed quantity as the record units. This includes document number, material number, batch number, committed quantity, executed quantity, pending execution quantity, source rule number, and commitment status code. The source rule number records the material category rule, validity period rule, project affiliation rule, or batch commitment rule used in this commitment relationship. The document-batch commitment relationship is used for batch commitment determination and to identify the fulfillment batch and committed quantity corresponding to the business document.

[0041] The second category is batch-location occupancy relationships, recorded using batch number, location number, and occupied quantity as the unit of record. This includes batch number, location number, occupied quantity, frozen quantity, committed quantity, committable quantity, quantity awaiting verification, and occupancy status code. The committed quantity originates from the document-batch commitment relationship; the committable quantity originates from the batch's book inventory quantity minus the committed quantity, the quantity awaiting shipment, and the quantity awaiting verification. Batch-location occupancy relationships are used for determining location occupancy and inventory quantity.

[0042] The third category is the location-time occupancy relationship, recorded using location number, location time period number, occupancy start time, and occupancy end time as the recording units. This includes location number, location time period number, current occupied quantity, reserved occupied quantity, expected release quantity, frozen occupied quantity, quantity awaiting verification, source document number, source batch number, benefiting document number, and location status code. The source document number records the business document that generated the reserved occupancy, expected release, or frozen occupancy; the source batch number records the material batch corresponding to the change in location occupancy; and the benefiting document number records the receiving document referencing the expected release quantity. The location-time occupancy relationship is used for determining direct receipt, pending release receipt, expected release, and inventory items.

[0043] The fourth category is the location-route resource relationship, recorded using the starting location number, target location number, route number, resource number, and resource time period number as the recording units. This includes the starting location number, target location number, route number, resource number, loading / unloading port number, resource time period number, occupancy start time, occupancy end time, and resource status code. The route number is generated from the location access route table; the resource number is generated based on the executable operation type and resource status code; and the resource time period number is generated based on the planned start and completion times of the operation. The location-route resource relationship is used to determine the occupancy of routes, equipment, personnel, and loading / unloading ports.

[0044] The fifth category is the business object-visual status relationship, which uses document number, batch number, storage location number, path number, resource number, and layer number as record units. It includes layer number, object number, object type, source document number, source batch number, source storage location number, source time period number, source plan number, source restriction record number, and visual status code. The visual status code is configured to correspond to document status code, commitment status code, storage location status code, resource status code, plan status code, and restriction status code. The business object-visual status relationship is used to generate display records for each layer.

[0045] In this process, the warehouse object relationship records include document-batch commitment relationships, batch-location occupancy relationships, location-time slot occupancy relationships, location-path resource relationships, and business object-visual status relationships. These warehouse object relationship records are used to read the batch commitment field, location occupancy field, location time slot field, path resource field, and visual status field during business document processing.

[0046] The processor writes five types of relationship records into the warehouse digital twin base record, configuring a relationship number, object number, status code, source field, and update time for each type of relationship record. The document-batch commitment relationship serves as the starting relationship for business documents entering batch commitment processing; the batch-location occupancy relationship is used for location acceptance determination and inventory quantity judgment; the location-time period occupancy relationship is used for direct acceptance, waiting-to-release acceptance, expected release, and inventory object judgment; the location-path resource relationship is used for path, equipment, personnel, and loading / unloading port occupancy judgment in the work plan; and the business object-visualization status relationship is used when generating display records for each layer. After completing the writing, the processor generates the version number and generation time of the warehouse digital twin base record.

[0047] S2. Read the pending business documents through the warehouse object relationship record, generate a business performance judgment record according to the document type, and write the expected release slice formed by outbound, the receipt result formed by inbound, the release and receipt result formed by transfer, and the affected business document number into the business performance judgment record.

[0048] The system reads pending business documents, document-batch commitment relationships, batch-location occupancy relationships, location-time period occupancy relationships, location access path tables, operational rule data, and warehouse digital twin basic records to generate a business performance judgment record. This record stores the field processing results of business documents during batch commitment, location receipt, location release, inventory object formation, freeze processing, release processing, and return receipt. It also serves as the read data for generating warehouse operation plans, multi-layer warehouse visualization management results, and inventory object layers. The business performance judgment record includes the judgment record number, document number, document type, material number, required quantity, specified batch number, specified warehouse area number, project ownership number, planned start time, planned completion time, candidate batch number, candidate location number, committed quantity, committed quantity, pending commitment quantity, expected release quantity, reserved occupied quantity, received quantity, received difference quantity, source rule number, associated time period number, associated path number, affected business document number, and business performance status code. Business performance status codes include commitment completed, commitment difference, direct receipt, waiting for release of receipt, receipt difference, original location release established, target location receipt established, inventory object formed, and restriction.

[0049] The processor categorizes business documents to be processed according to document type. When the document type is an outbound order, the processor performs batch commitment determination; when the document type is an inbound order, the processor performs location acceptance determination; when the document type is a transfer order, the processor performs original location release determination and target location acceptance determination; when the document type is an inventory count order, the processor performs inventory object formation determination; when the document type is a return order, freeze order, or release order, the processor generates corresponding batch status adjustment record, location status adjustment record, or return acceptance record based on material number, batch number, location number, and document status code, and writes the processing result to the business fulfillment determination record.

[0050] When the business document is an outbound order, the processor reads the material number, required quantity, specified batch number, project ownership number, planned completion time, and document priority from the outbound order. It also reads the batch number, quality status code, freeze status code, project ownership number, committable quantity, location number, expiry date, and outbound sequence code from the batch-location occupancy relationship. The processor filters candidate batches based on the following field conditions: quality status code is available; freeze status code is not frozen; project ownership number matches the outbound order's project ownership number; specified batch number is empty, or specified batch number matches the batch number; expiry date is later than the outbound order's planned completion time; the remaining days between the expiry date and the planned completion time are not less than the minimum remaining validity period; and the committable quantity is greater than zero.

[0051] Batches meeting the field conditions are written into the candidate batch set. After the candidate batch set is formed, the processor sorts them according to the order of outbound sequence code, expiration date, inbound time, and batch number. The processor generates document-batch commitment relationships sequentially along the sorted candidate batch set, with the committed quantity not exceeding the batch's committable quantity and not exceeding the outbound order's pending commitment quantity. For each document-batch commitment relationship formed, the processor updates the committed quantity, batch committed quantity, batch committable quantity, batch pending outbound quantity, outbound order committed quantity, and outbound order pending commitment quantity. If the outbound order's pending commitment quantity is reduced to zero, the processor marks the outbound order status code as commitment completed; if the outbound order's pending commitment quantity is still greater than zero after reading the candidate batch set, the processor marks the outbound order status code as commitment difference and generates a commitment difference record. The commitment difference record includes the document number, material number, required quantity, committed quantity, pending commitment quantity, summary value of the candidate batch's committable quantity, and difference source field.

[0052] After the outbound order generates a document-batch commitment relationship, the processor reads the location number and planned completion time of the committed batch to generate an expected release slice. The expected release slice includes a release slice number, location number, source outbound order number, source batch number, expected release quantity, expected release time, expected release period number, referenceable flag, referenced flag, release confirmation status, and benefiting document number. The expected release quantity is consistent with the committed quantity in the corresponding document-batch commitment relationship, and the expected release time is the planned completion time of the source outbound order. The expected release period number is generated based on the expected release time and the minimum scheduling time unit in the scheduling configuration table. The initial value of the referenceable flag is "referenceable," the initial value of the referenced flag is "not referenced," and the initial value of the release confirmation status is "not released." After the operation completion status record corresponding to the source outbound order is formed, the release confirmation status is updated to "released." If the operation completion status record corresponding to the source outbound order is not formed, partially completed, or has an execution feedback restriction record, the release confirmation status remains "not released" or a partial release status is generated based on the actual completed quantity. The processor writes the expected release quantity into the expected release quantity field of the location-time period occupancy relationship, and writes the source outbound order number, source batch number, and source rule number into the corresponding source field.

[0053] When the business document is an inbound order, the processor reads the material number, required quantity, designated storage area number, project ownership number, planned start time, and planned completion time from the inbound order, and also reads the location attribute data, location-time period occupancy relationship, expected release slice, and material category rule table. The volume corresponding to the inbound quantity is obtained by multiplying the volume of the material unit by the inbound quantity, and the weight corresponding to the inbound quantity is obtained by multiplying the weight of the material unit by the inbound quantity; the volume and weight of the material unit are read from the material master data or material batch data. If the volume or weight of the material unit is missing, zero, or inconsistent with the storage location volume capacity or upper limit, the processor generates a material measurement data to be verified record, marks the inbound order status code as pending acceptance, and does not proceed to the direct acceptance judgment or the waiting-for-release acceptance judgment. The processor filters candidate storage locations based on the designated storage area number, material category rule table, allowed material categories, prohibited material categories, frozen occupancy status, and pending verification occupancy status.

[0054] The receiving results generated during the inbound processing include direct receiving records, waiting-to-release receiving records, and receiving difference records. The processor performs a direct receiving determination on candidate storage locations, reading the remaining capacity, available volume, and weight of the storage location. When the remaining capacity is greater than or equal to the inbound quantity, the remaining available volume is greater than or equal to the volume corresponding to the inbound quantity, and the remaining weight is greater than or equal to the weight corresponding to the inbound quantity, the processor generates a direct receiving record. The direct receiving record includes the inbound order number, candidate storage location number, received quantity, received volume, received weight, storage location time slot number, reserved quantity, reserved volume, reserved weight, and direct receiving status code. The processor writes the inbound quantity, the volume corresponding to the inbound quantity, and the weight corresponding to the inbound quantity into the reserved occupancy field of the storage location and marks the inbound order status code as direct receiving.

[0055] If the directly received record does not cover the quantity required by the inbound order, the processor reads the expected release slice and performs a pending release reception determination. The pending release reception determination reads the expected release quantity, expected release volume, expected release weight, expected release time, available-to-reference flag, referenced flag, remaining capacity of the storage location, remaining available volume of the storage location, and remaining weight that the storage location can handle. When the inbound material category meets the storage location material category conditions, the expected release time is earlier than or equal to the planned start time of the inbound order, the available-to-reference flag is referenced, the referenced flag is unreferenced, and the receivable quantity, receivable volume, and receivable weight formed after release all cover the current allocation reception requirement, the processor generates a pending release reception record. The pending release reception record includes the inbound order number, candidate storage location number, source release slice number, source outbound order number, source batch number, expected release quantity, received quantity, received volume, received weight, benefit document number, and pending release reception status code. The processor writes the inbound order number to the benefit document number field of the expected release slice, updates the referenced flag to referenced, and marks the inbound order status code as pending release reception.

[0056] When the processor performs acceptance determination on an inbound order, it allows the same inbound order to be accepted by at least two candidate storage locations. The processor first allocates the receiving quantity according to the direct receiving record, then reads the referenceable expected release slices in order of expected release time (earliest to latest), remaining available storage volume (largest to smallest), and storage location number, generating one or more waiting-to-release receiving records. Each direct receiving record or waiting-to-release receiving record corresponds to a candidate storage location number, a storage location time period number, and a receiving quantity, forming a corresponding warehousing operation sub-plan when the warehousing operation plan is generated. If the total receiving quantity corresponding to the direct receiving record and the waiting-to-release receiving record still does not cover the required quantity of the inbound order, the processor generates a receiving difference record and marks the inbound order status code as receiving difference. The receiving difference record includes the inbound order number, material number, required quantity, direct receiving quantity, waiting-to-release receiving quantity, receiving difference quantity, candidate storage location number set, and difference source field.

[0057] When the business document is a transfer order, the processor reads the material number, batch number, outgoing location number, target location number, transfer quantity, planned start time, and planned completion time from the transfer order, and also reads the batch-location occupancy relationship and location-time period occupancy relationship. The processor performs an original location release determination for the outgoing location. If there is a batch number and outgoing location number that match the transfer order in the batch-location occupancy relationship, and the occupied quantity is greater than or equal to the transfer quantity, and the quantity to be verified for that batch is zero, and the occupancy status code is not pending verification, the processor generates an original location release record. The original location release record includes the transfer order number, outgoing location number, batch number, release quantity, estimated release time, release time period number, source rule number, and original location release established status code. The estimated release time is taken as the planned completion time of the transfer order.

[0058] The release and acceptance results generated by the transfer process include the original storage location release record, the target storage location acceptance record, and the transfer restriction record. The processor performs a target storage location acceptance determination on the target storage location, reading the allowed material categories, prohibited material categories, remaining storage location capacity, remaining available volume, remaining weight capacity, frozen occupancy quantity, reserved occupancy quantity, and pending verification quantity. When the target storage location is allowed to receive the material category, is not in a frozen or pending verification state, and the remaining capacity, available volume, and remaining weight capacity all meet the requirements for the transfer quantity, the corresponding volume, and the corresponding weight, the processor generates a target storage location acceptance record. The processor only writes the expected release quantity of the transferred storage location and the reserved occupancy quantity of the target storage location into the currently valid storage location-time period occupancy relationship and marks the transfer order status as "in progress" when both the original storage location release determination and the target storage location acceptance determination are valid. If either determination is invalid, the processor does not change the currently valid storage location occupancy field and only generates a transfer restriction record.

[0059] When the business document is an inventory count sheet, the processor reads the inventory count sheet number, inventory area number, inventory plan time, and inventory object rules from the inventory count sheet, and also reads the document-batch commitment relationship, batch-location occupancy relationship, and location-time period occupancy relationship. If the inventory count sheet is configured with an inventory area number, the processor extracts inventory objects from the locations and batches within that area; if the inventory area number is empty, the processor extracts inventory objects from all locations and batches in the warehouse digital twin basic record. Trigger fields include committed quantity, reserved occupancy quantity, expected release quantity, frozen occupancy quantity, and quantity pending verification. When a batch or location has any trigger field and the trigger field value is greater than zero, the processor writes the batch or location into the inventory object set. The inventory object set includes the inventory object number, inventory count sheet number, batch number, location number, trigger field, trigger field value, source document number, source batch number, location time period number, and object status code.

[0060] For a freeze order, the processor reads the batch number, location number, frozen quantity, and freeze reason fields from the freeze order. When the freeze order contains a batch number, the processor determines the batch's freezeable quantity based on the book inventory quantity, committed quantity, quantity to be shipped, quantity to be verified, and already frozen quantity. If the frozen quantity is less than or equal to the batch's freezeable quantity, the processor marks the corresponding batch's freeze status code as frozen and generates a batch freeze processing record. If the frozen quantity is greater than the batch's freezeable quantity, the processor generates a batch freeze restriction record. When the freeze order contains a location number, the processor determines the location's freezeable quantity based on the current occupied quantity, frozen occupied quantity, and quantity to be verified. If the frozen quantity is less than or equal to the location's freezeable quantity, the processor increases the corresponding location's frozen occupied quantity and generates a location freeze processing record. If the frozen quantity is greater than the location's freezeable quantity, the processor generates a location freeze restriction record. When the freeze order contains both a batch number and a location number, the processor performs batch freeze determination and location freeze determination separately.

[0061] For release orders, the processor reads the batch number, location number, release quantity, release reason field, and source freeze record number from the release order, and matches it with the batch freeze processing record or location freeze processing record based on the source freeze record number. When the release order contains a batch number, the release quantity must not exceed the unreleased frozen quantity in the source batch freeze processing record; when the release quantity meets the boundary, the processor deducts the unreleased frozen quantity from the source freeze record. When the unreleased frozen quantity is reduced to zero, the freeze status code of the corresponding batch is marked as unfrozen, and a batch release processing record is generated; when the release quantity exceeds the unreleased frozen quantity, a batch release restriction record is generated. When the release order contains a location number, the release quantity must not exceed the unreleased frozen quantity in the source location freeze processing record, and the frozen occupied quantity after release must not be less than zero; when the release quantity meets the boundary, the processor deducts the frozen occupied quantity of the corresponding location and generates a location release processing record; when the release quantity exceeds the unreleased frozen quantity, a location release restriction record is generated. When a release restriction record is generated, the corresponding batch or location is marked as pending verification, and the restriction record number is written to the restriction source layer.

[0062] For a return order, the processor reads the source document number, return batch number, return quantity, and return quality status code. When the return batch number matches the outbound batch number in the source document, the return quantity is not greater than the source outbound quantity, and the return quality status code is available or pending inspection, the processor generates a return receipt record according to the location acceptance method of the inbound order, and writes the source document number, return batch number, and target location number into the business fulfillment judgment record. When the return batch number, return quantity, or return quality status code does not meet the field relationship requirements, the processor generates a return restriction record.

[0063] The processor determines the affected business documents based on the planned start time and field reference relationships. An affected business document is one whose planned start time is later than the current business document's planned start time and shares the same material number, batch number, location number, path number, or resource number as the current business document. When an outbound order forms a projected release slice, inbound orders, transfer orders, and inventory count orders referencing the same location number are written into the affected business document number field. When an inbound order forms a reservation, transfer orders, outbound orders, and inventory count orders referencing the same location number are written into the affected business document number field. When a transfer order forms an original location release record or a target location receiving record, business documents referencing the same location number, batch number, or path number are written into the affected business document number field.

[0064] After the processor completes the determination of the document type, it outputs a business performance determination record and writes it to the same version number of the warehouse digital twin basic record. The document number, batch number, storage location number, storage location time period number, source rule number, status code, and affected business document number in the business performance determination record are used as read fields for generating warehouse operation plans, generating multi-level warehouse visualization management results, and generating inventory object layers.

[0065] S3. Based on the business performance judgment record, read the warehouse object relationship record, generate a warehouse operation plan or warehouse operation restriction record according to the batch commitment status, storage location time period status, path resource status and affected business document status, and generate a warehouse operation sub-plan when the same document corresponds to a dispersed operation object.

[0066] The system reads business fulfillment determination records, document-batch commitment relationships, batch-location occupancy relationships, location-time slot occupancy relationships, location-path resource relationships, location access path tables, warehouse space data, warehousing resource data, and operation rule data to generate a warehousing operation plan. The warehousing operation plan records the material batch, starting location, target location, path, equipment, personnel, loading / unloading points, and planned time corresponding to the business documents, and distinguishes between executable and restricted operation arrangements. The generation of the warehousing operation plan begins with the status code in the business fulfillment determination record, sequentially reading the batch commitment status, location time slot status, path occupancy status, resource occupancy status, and affected business document status.

[0067] The warehousing operation plan includes plan number, sub-plan number, decision record number, document number, document type, operation type, material number, batch number, starting storage location number, target storage location number, route number, equipment number, personnel number, loading / unloading port number, planned start time, planned completion time, storage location time slot number, resource time slot number, operation quantity, operation volume, operation weight, preceding status code, plan status code, affected business document number, confirmation field set, and restriction record number. Operation types include inbound putaway, outbound picking, transfer handling, return receipt, inventory verification, and freeze processing. Plan status codes include executable, batch restriction, storage location restriction, time slot overlap restriction, waiting for release restriction, route time slot restriction, resource time slot restriction, affected business document restriction, and pending confirmation. The confirmation field set includes confirmation source field and confirmation result field. The source confirmation fields include confirmation of the scanning point, weighing point, cargo location, route point, and loading / unloading port point, used to determine the collection location or equipment for the operation execution feedback data. The result confirmation fields include batch confirmation, quantity confirmation, starting cargo location confirmation, target cargo location confirmation, route confirmation, resource confirmation, and loading / unloading port confirmation, used to verify the operation execution feedback data against the batch number, operation quantity, starting cargo location number, target cargo location number, route number, resource number, and loading / unloading port number in the warehousing operation plan. The prerequisite status code is formed by combining the business performance status code in the business performance judgment record, the commitment status code in the document-batch commitment relationship, the cargo location status code in the cargo location-time period occupancy relationship, and the resource status code in the cargo location-route resource relationship.

[0068] The planned start and finish times of the warehousing operation plan are retrieved from the planned start and finish times of the corresponding business documents in the business performance determination record. When the same business document corresponds to multiple batches, multiple target storage locations, or multiple expected release slices, the processor generates separate warehousing operation sub-plans. Each warehousing operation sub-plan corresponds to a batch number, a starting storage location number, a target storage location number, an operation quantity, and a resource time period number. Multiple warehousing operation sub-plans are generated sequentially according to business document priority, batch sorting results, storage location time period number, and resource time period number.

[0069] In this process, distributed operation objects include multiple batches, multiple target storage locations, or multiple expected release slices corresponding to the same business document. The processor generates a warehousing operation sub-plan based on a batch number, a starting storage location number, a target storage location number, and a job quantity, so that different operation objects under the same business document are assigned plan numbers and sub-plan numbers respectively.

[0070] For an outbound order, the processor reads the batch number, committed quantity, pending quantity, and commitment status code from the document-batch commitment relationship, and also reads the document status code of the outbound order. When the commitment status code in the document-batch commitment relationship is "committed," the outbound order status code is "commitment completed" or "commitment shortfall," and the pending quantity is greater than zero, the processor generates an outbound picking sub-plan for the committed portion. The outbound picking sub-plan writes the location number of the committed batch to the starting location number, the loading / unloading port number corresponding to the outbound handover to the loading / unloading port number field, and the pending quantity to the operation quantity. When the outbound order status code is "commitment shortfall," the processor only generates an outbound picking sub-plan for the committed portion and generates a batch restriction record for the uncommitted portion. The batch restriction record includes the document number, material number, required quantity, committed quantity, pending commitment quantity, restriction field, and batch restriction status code.

[0071] For inbound orders, the processor reads the direct receipt record, pending release receipt record, and receipt difference record from the business fulfillment judgment record. When the inbound order status code is "direct receipt," the processor writes the candidate storage location number from the direct receipt record to the target storage location number, writes the received quantity to the operation quantity, and writes the storage location time period number to the warehousing operation sub-plan. When the inbound order status code is "pending release receipt," the processor reads the expected release slice and the source outbound order status code. If the source outbound order status code is "committed to completion," "in execution," or "completed," the referenceable flag of the expected release slice is set to "referenceable," the referenced flag is set to "referenced," the benefiting document number matches the inbound order number, and the expected release time is earlier than or equal to the planned start time of the inbound order, the processor generates an inbound shelving sub-plan. If any field condition is not met, the processor marks the plan status code as "pending release restriction." When the inbound order status code is "receive difference," the processor generates a storage location restriction record but does not generate an executable sub-plan.

[0072] For a transfer order, the processor reads the original location release record and the target location receiving record. When both the original location release status code and the target location receiving status code are present, the processor writes the transfer location number to the starting location number, the target location number to the target location number, the transfer quantity to the operation quantity, and generates a transfer handling sub-plan. When only the original location release status code or only the target location receiving status code exists, the processor generates a location restriction record, writing the restriction field to the unformed judgment status code. For a return order, the processor reads the return receiving record and writes the return batch number, target location number, return quantity, and return quality status code to the return receiving sub-plan; when a return restriction record exists, the processor marks the plan status code as either batch restriction or location restriction based on the restriction field.

[0073] After determining the batch number, starting location number, and target location number, the processor reads the location-time slot occupancy relationship and performs time slot occupancy determination on the starting and target locations. Time slot occupancy determination reads the location time slot number, current occupied quantity, reserved occupied quantity, expected release quantity, frozen occupied quantity, pending verification quantity, occupancy start time, occupancy end time, and location status code. When the target location status code is frozen occupied or pending verification, the scheme status code is marked as location restricted. If a warehousing operation sub-scheme depends on an expected release slice, and the expected release time of the expected release slice is later than the planned start time, the scheme status code is marked as waiting for release restriction. If there is a registered reserved occupied slice between the planned start time and planned completion time for either the starting or target location, and the start time of the registered reserved occupied slice is earlier than the current sub-scheme's planned completion time, and the end time of the occupied slice is later than the current sub-scheme's planned start time, the processor generates a time slot overlap restriction record.

[0074] For inbound shelving and relocation operations, the processor reads the remaining capacity and remaining load capacity of the target storage location. The operation volume is obtained by multiplying the volume of a single item by the quantity to be moved, and the operation weight is obtained by multiplying the weight of a single item by the quantity to be moved. The volume and weight of a single item are read from the material master data or the material batch data. When the available volume corresponding to the remaining capacity of the storage location is less than the operation volume, or the remaining load capacity of the storage location is less than the operation weight, the processor generates a storage location restriction record. The storage location restriction record includes the scheme number, target storage location number, operation quantity, operation volume, operation weight, remaining storage location capacity, remaining storage location load capacity, and restriction fields.

[0075] When the storage location time period does not trigger a restriction status code, the processor reads the storage location access path table based on the starting storage location number, target storage location number, and loading / unloading port number, extracts the path number, path node sequence, and channel direction fields, and generates candidate path records. Candidate path records include a scheme number, starting storage location number, target storage location number, loading / unloading port number, path number, path node sequence, resource time period number, and path status code. Candidate path records are sorted in ascending order of the number of path nodes; if the number of path nodes is the same, path numbers that have not yet formed an occupied record within the resource time period are read first; if there are still identical sorting results, they are sorted in ascending order of path number.

[0076] The processor performs path occupancy determination on candidate path records. If the start time of an existing path occupancy record is earlier than the planned completion time of the current sub-scheme, and the end time of an existing path occupancy record is later than the planned start time of the current sub-scheme, the processor determines that the path is occupied within the current resource time period and excludes that path number from the candidate path records. When all candidate path records are excluded, the processor generates a path time period restriction record. The path time period restriction record includes the scheme number, starting storage location number, target storage location number, loading / unloading port number, excluded path number, resource time period number, occupancy start time, occupancy end time, and path time period restriction status code.

[0077] When an available path number exists, the processor reads the warehouse resource data and filters the equipment, personnel, and loading / unloading points that match the job type. Equipment corresponding to outbound picking, inbound shelving, and transfer includes forklifts, stacker cranes, or conveyor equipment; resources corresponding to inventory verification include barcode scanners, weighing equipment, inventory personnel, and verification personnel; resources corresponding to return receiving include loading / unloading points, barcode scanners, weighing equipment, and verification personnel. The processor reads the resource status code, resource time period number, start time of occupation, and end time of occupation. If the resource status code is available and there is no overlap in occupation time between the planned start time and planned completion time, the corresponding resource is added to the resource candidate set. If the resource status code is occupied, restricted, or pending confirmation, the corresponding resource is not added to the resource candidate set.

[0078] When the equipment candidate set, personnel candidate set, or loading / unloading port candidate set is empty, the processor generates a resource time-limit restriction record. The resource time-limit restriction record includes the plan number, operation type, resource type, resource number, resource status code, resource time-limit number, start time of occupation, end time of occupation, and resource time-limit restriction status code. When records exist in all three candidate sets (equipment, personnel, and loading / unloading ports), the processor determines the equipment number, personnel number, and loading / unloading port number in ascending order of resource status code availability, resource occupation end time earlier than the current planned start time, and resource number. The processor then writes these information into the warehousing operation plan.

[0079] When generating a warehouse operation plan, the processor reads the affected business document number field and performs field occupancy checks on the affected business documents. Affected business documents are those whose planned start time is later than the current business document's planned start time and reference the same material number, batch number, location number, path number, or resource number. If the batch number occupied by the current outbound plan has already been written into the candidate batch set of the affected outbound order, the processor generates an affected business document notification record and marks the affected outbound order as a candidate batch pending confirmation. If the target location number occupied by the current inbound plan has already been written into the target location set of the affected transfer order, the processor generates an affected business document notification record and marks the affected transfer order as a target location pending confirmation. If the current transfer plan changes the batch number in a location, the processor generates an affected business document notification record and marks inventory lists whose count scope includes that location number or batch number as inventory objects pending confirmation.

[0080] The document priority code is determined by the document priority configuration table in the business document data or operation rule data. The value is a positive integer, with smaller values ​​indicating higher priority. The document priority configuration table generates document priority codes based on document type, project affiliation, planned start time, and manual priority marker. If no manual priority marker is configured, the default priority code corresponding to the document type is used. When two business documents have the same priority code, the processor first sorts them by planned start time from earliest to latest. If the planned start times are the same, they are sorted by document generation time from earliest to latest. If both planned start time and document generation time are the same, they are sorted by document number.

[0081] When the priority code of the affected business document is lower than that of the current business document, and the planned start time of the affected business document is earlier than the planned completion time of the current warehousing operation sub-scheme, the processor marks the current scheme status code as "affected business document restriction." When the priority code of the affected business document is greater than that of the current business document, or the planned start time of the affected business document is not earlier than the planned completion time of the current warehousing operation sub-scheme, the processor retains the affected business document notification record and does not mark the current scheme status code as "affected business document restriction." When the priority code of the affected business document is equal to that of the current business document, the processor determines the sorting result according to the planned start time, document generation time, and document number. If the sorting result indicates that the affected business document will be executed before the current business document, and the planned start time of the affected business document is earlier than the planned completion time of the current warehousing operation sub-scheme, the processor marks the current scheme status code as "affected business document restriction"; otherwise, it retains the affected business document notification record.

[0082] When none of the batch, location time period, path, resource, and affected business document fields trigger a restriction status code, the processor generates an executable warehousing operation plan. An executable warehousing operation plan includes a plan number, sub-plan number, document number, batch number, starting location number, target location number, path number, equipment number, personnel number, loading / unloading port number, planned start time, planned completion time, operation quantity, operation volume, operation weight, confirmed barcode scanning point, confirmed weighing point, confirmed storage point, confirmed path point, confirmed loading / unloading port point, and plan status code. The confirmed barcode scanning point is generated based on the starting location number, target location number, and batch number; the confirmed weighing point is generated based on the operation quantity and weighing equipment number; the confirmed storage point is generated based on the starting location number and target location number; the confirmed path point is generated based on the path node sequence; and the confirmed loading / unloading port point is generated based on the loading / unloading port number.

[0083] When any field triggers a restriction status code, the processor generates a warehouse operation restriction record. The warehouse operation restriction record includes the restriction record number, scheme number, sub-scheme number, document number, restriction type, restriction field, field value, associated batch number, associated location number, associated path number, associated resource number, affected business document number, and restriction status code. Restriction types include batch restriction, location restriction, time period overlap restriction, pending release restriction, path time period restriction, resource time period restriction, and affected business document restriction. The warehouse operation restriction record is bound and saved with the corresponding business performance determination record and is used as the read data when generating the restriction source layer.

[0084] After the processor completes the generation of a warehouse operation plan or warehouse operation restriction record, it writes the plan number, sub-plan number, restriction record number, plan status code, path number, resource number, and confirmation field set into the same version number of the warehouse digital twin base record. The warehouse operation plan serves as the read data when generating multi-layer warehouse visualization management results, and the warehouse operation restriction record serves as the read data when generating restriction source layers and affected business document display records.

[0085] S4. Based on the warehouse operation plan, warehouse operation restriction records and operation execution feedback data, read the visualization configuration data, write the operation status, restriction source, associated object, and status code and source record number generated by the feedback into the corresponding layer, generate multi-layer warehouse visualization management results and status confirmation results corresponding to the warehouse digital twin basic record version, and write the status confirmation results into the warehouse digital twin basic record.

[0086] The system reads basic records from the warehouse digital twin, including business performance judgment records, document-batch commitment relationships, batch-location occupancy relationships, location-time slot occupancy relationships, location-path resource relationships, warehouse operation plans, warehouse operation restriction records, affected business document prompt records, inventory object sets, visualization configuration data, and operation execution feedback data. It then generates multi-layered warehouse visualization management results and status confirmation results. The multi-layered warehouse visualization management results are used to save the display records of business documents, material batches, location time slots, path resources, warehouse operation plans, warehouse operation restriction records, and inventory objects in their corresponding layers. The status confirmation results are used to save operation execution status records, operation completion status records, partially completed status records, or execution feedback restriction records generated from operation execution feedback.

[0087] The multi-layered warehouse visualization management results include document fulfillment layers, batch commitment layers, storage location time slot layers, route resource layers, work plan layers, restricted source layers, and inventory object layers. The processor generates layer display records in the following order: document fulfillment layer, batch commitment layer, storage location time slot layer, route resource layer, restricted source layer, work plan layer, and inventory object layer. Each layer display record includes the layer number, layer name, object type, object number, display position, display field, status code field, source field, associated object number, associated plan number, associated restricted record number, and update time. If the same source record triggers both the restricted source layer and the work plan layer simultaneously, the processor first generates the restricted source layer display record, and then writes the restricted record number into the work plan layer display record.

[0088] The processor determines the layer name, object type, display fields, and layer update conditions based on the visualization configuration data. Layer update conditions include the formation of business fulfillment judgment records, warehousing operation plans, warehousing operation restriction records, affected business document prompt records, inventory object sets, operation execution feedback data, and status code changes. Display locations are generated based on object type: storage locations correspond to storage location coordinates; paths correspond to path node sequences; resources correspond to resource locations and resource time periods; business documents correspond to line numbers in the document fulfillment layer and are bound to associated storage location coordinates; material batches correspond to the storage location coordinates of the batch; warehousing operation plans correspond to the starting storage location number, target storage location number, path number, and loading / unloading port number; warehousing operation restriction records correspond to associated storage location numbers, associated path numbers, or associated resource numbers; and inventory objects correspond to the storage location number of the inventory object or the storage location number of the batch.

[0089] The document fulfillment layer generates document fulfillment display records indexed by document number. The processor reads business document data, business fulfillment judgment records, and document-batch commitment relationships, and writes the document type, material number, required quantity, committed quantity, pending commitment quantity, commitment batch number, committed quantity, document status code, and affected business document number into the document fulfillment display record. When the document status code is "commitment completed," the committed quantity, commitment batch number, commitment location number, and planned completion time are written; when the document status code is "commitment difference," the pending commitment quantity, difference source field, and summary value of the candidate batch's committable quantity are written; when the document status code is "direct receipt" or "awaiting release receipt," the target location number, received quantity, location time period number, expected release slice number, source outbound order number, source batch number, and benefiting document number are written; when the document status code is "receive difference" or "restriction," the restriction field, field value, and restriction record number are written.

[0090] The batch commitment layer generates batch commitment display records indexed by batch number. The processor reads material batch data, document-batch commitment relationships, and batch-location occupancy relationships, and writes the material number, book inventory quantity, committed quantity, quantity to be shipped, quantity to be verified, committable quantity, location number, associated document number, quality status code, frozen status code, and commitment status code into the batch commitment display record. When the quality status code is pending inspection or expired, the quality status code and restriction field are written; when the frozen status code is frozen, the frozen reason field and frozen quantity are written; when the commitment status code is committed or fulfilled, the commitment document number, committed quantity, quantity to be executed, executed quantity, or completion time are written.

[0091] The storage location time slot layer generates storage location time slot display records using the storage location number and storage location time slot number as indexes. The processor reads the storage location attribute data and the storage location-time slot occupancy relationship, and writes the storage location coordinates, current occupied quantity, reserved occupied quantity, expected release quantity, frozen occupied quantity, quantity pending verification, source document number, source batch number, benefiting document number, and storage location status code into the storage location time slot display record. When the storage location status code is currently occupied, reserved occupied, expected release, waiting for release, frozen occupied, or pending verification, the corresponding occupied quantity, expected release slice number, expected release time, benefiting inbound document number, and the frozen reason field or verification object field are written respectively.

[0092] The path resource layer generates path resource display records indexed by path number, resource number, and resource time period number. The processor reads the location access path table, location-path resource relationships, and warehouse resource data, and writes the path node sequence, resource type, path availability status code, resource status code, occupancy start time, occupancy end time, and associated scheme number into the path resource display record. When a path or resource is available, the executable operation type is written; when a path or resource is occupied, restricted, or pending confirmation, the occupancy scheme number, occupancy time, restriction field, pending confirmation field, or associated restriction record number is written.

[0093] The restriction source layer generates restriction display records indexed by the restriction record number. The processor reads the warehouse operation restriction record and the execution feedback restriction record, and writes the scheme number, sub-scheme number, document number, restriction type, restriction field, field value, associated batch number, associated location number, associated path number, associated resource number, and restriction status code into the restriction display record. When the restriction type is batch restriction, location restriction, time period overlap restriction, waiting release restriction, path time period restriction, resource time period restriction, affected business document restriction, inventory restriction, or feedback restriction, the corresponding scheme field value, feedback field value, occupied time, inventory quantity, and source record number are written respectively.

[0094] The work plan layer generates work plan display records using the plan number and sub-plan number as indexes. The processor reads the warehouse work plan and writes the document number, work type, batch number, starting storage location number, target storage location number, route number, equipment number, personnel number, loading / unloading port number, planned time, work quantity, work volume, work weight, confirmation field set, and plan status code into the work plan display record. When the plan status code is executable, the confirmation source field and confirmation result field are written; the confirmation source field includes confirmation of barcode scanning point, confirmation of weighing point, confirmation of storage location, confirmation of route point, and confirmation of loading / unloading port point; the confirmation result field includes batch confirmation field, quantity confirmation field, starting storage location confirmation field, target storage location confirmation field, route confirmation field, resource confirmation field, and loading / unloading port confirmation field.

[0095] The inventory object layer generates inventory object display records using the inventory check sheet number and inventory object number as indices. The processor reads the inventory object set, batch-location occupancy relationship, location-time period occupancy relationship, and inventory feedback data, and writes the inventory object number, inventory check sheet number, batch number, location number, trigger field, trigger field value, source document number, location time period number, object status code, and inventory quantity into the inventory object display record. When the inventory feedback quantity does not correspond to the book inventory quantity in the batch-location occupancy relationship, the inventory restriction record number and quantity difference are written.

[0096] The processor reads the corresponding status code based on the object type and writes the status code, source field, and associated object into the layer display record. When the same layer number, the same object number, and the same source record number correspond to at least two status codes, the processor determines the primary status code in the order of restricted status, pending verification status, reserved status, expected release status, currently occupied status, and executable status, and writes the other status codes into the auxiliary status field. After generating each layer display record, the processor performs deduplication based on the layer number, object number, status code, and source record number, and merges the layer display records into a multi-layer warehouse visualization management result, which is then bound to the version number of the warehouse digital twin basic record for storage.

[0097] After the multi-layered warehouse visualization management results are generated, the processor establishes a correspondence between the operation execution feedback data and the warehouse operation plan based on the feedback number, plan number, and sub-plan number, and generates an operation execution status record. The operation execution feedback data includes barcode scanning feedback data, weighing feedback data, location confirmation feedback data, route traversal feedback data, equipment execution feedback data, personnel confirmation feedback data, loading / unloading port confirmation feedback data, and inventory feedback data. The operation execution status record includes the execution record number, plan number, sub-plan number, document number, operation type, plan field, actual feedback field, feedback time, execution status code, and execution feedback restriction record number.

[0098] The processor reads the set of confirmation fields from the warehousing operation plan, reads the operation execution feedback data according to the confirmation source field, and verifies the operation execution feedback data according to the confirmation result field. Scan feedback data is used to verify the batch confirmation field; weighing feedback data is used to verify the quantity confirmation field; location confirmation feedback data is used to verify the starting location confirmation field and the target location confirmation field; path traversal feedback data is used to verify the path confirmation field; equipment execution feedback data and personnel confirmation feedback data are used to verify the resource confirmation field; loading / unloading port confirmation feedback data is used to verify the loading / unloading port confirmation field. When the actual feedback field falls into the corresponding plan field set, the corresponding confirmation field is marked as passed; when the actual quantity is less than the plan quantity but greater than zero, and partial fulfillment is allowed, the quantity confirmation field is marked as partially passed.

[0099] When the batch confirmation field, quantity confirmation field, starting location confirmation field, target location confirmation field, route confirmation field, resource confirmation field, and loading / unloading port confirmation field are all marked as passed, the processor generates a job completion status record. For outbound picking operations, the processor updates the executed quantity and pending quantity in the document-batch commitment relationship, deducts the pending outbound quantity and the current occupied quantity of the corresponding location in the batch-location occupancy relationship, and marks the release confirmation status of the expected release slice as released. For inbound putaway operations, the processor increases the occupied quantity in the batch-location occupancy relationship, deducts the reserved occupied quantity, and increases the current occupied quantity; when the source is a waiting-to-release receiving record, if the release confirmation status is released, the location occupancy field is updated; otherwise, a waiting-to-release feedback restriction record is generated. For transfer and handling operations, the processor deducts the current occupied quantity of the moved-out location and the expected release quantity of the original location, deducts the reserved occupied quantity of the target location, increases the current occupied quantity of the target location, and updates the batch-location occupancy relationship. For return receipt operations, the processor updates the quantity occupied in the target storage location and the return order status code; for inventory verification operations, the processor updates the status code of the inventory objects according to the inventory quantity and generates an inventory confirmation record.

[0100] When the quantity confirmation field is marked as partially passed, the processor generates a partially completed status record. The partially completed status record includes the scheme number, sub-scheme number, scheme quantity, actual quantity, uncompleted quantity, completed batch number, uncompleted batch number, completed location number, uncompleted location number, and document status code. The uncompleted quantity corresponding to an outbound order is retained in the pending quantity field of the document-batch commitment relationship; the uncompleted quantity corresponding to an inbound order and a transfer order is retained in the uncompleted quantity field of the partially completed status record, without changing the current occupied quantity of the target location.

[0101] When any confirmation field fails, the processor generates an execution feedback constraint record. The execution feedback constraint record includes constraint record number, execution record number, scheme number, sub-scheme number, document number, constraint type, constraint field, scheme field value, feedback field value, associated batch number, associated storage location number, associated path number, associated resource number, and constraint status code. The execution feedback constraint record does not change the occupied quantity in the batch-storage location occupancy relationship, does not change the batch's committable quantity, and does not change the current occupied quantity in the storage location-time period occupancy relationship. When the actual batch, quantity, storage location, path, or resource field does not meet the corresponding scheme field set, the processor generates the corresponding batch feedback constraint record, quantity feedback constraint record, storage location feedback constraint record, path feedback constraint record, or resource feedback constraint record. Before the constraint is lifted, the corresponding batch, storage location, path, or resource is not written into the candidate field set of the warehousing operation scheme.

[0102] The processor updates the multi-layered warehouse visualization management results based on the job completion status record, partial completion status record, and execution feedback constraint record. When a job completion status record is generated, the status code, completed quantity, completion time, and associated object number in the document fulfillment layer, batch commitment layer, storage location time period layer, route resource layer, and job plan layer are updated. When a partial completion status record is generated, the completed quantity and incomplete quantity are written in the document fulfillment layer, and the partial completion status code is written in the job plan layer. When an execution feedback constraint record is generated, the constraint type, constraint field, plan field value, feedback field value, and constraint status code are written in the constraint source layer, and the auxiliary status field is written in the corresponding layer.

[0103] The review and confirmation results include confirmation of execution, confirmation of correction, confirmation of cancellation, and confirmation of maintaining restrictions. Upon confirmation of execution, the processor updates the corresponding document, batch, location, route resource, and visualization layer status according to the job completion status record. Upon confirmation of correction, the processor updates the corresponding fields according to the reviewed batch number, quantity, location number, route number, or resource field, and generates a correction confirmation record. Upon confirmation of cancellation, the processor releases the corresponding committed quantity, reserved quantity, and route resource occupancy records, and determines the rollback status based on the business document type and the source of the record before cancellation. Upon confirmation of maintaining restrictions, the restriction status code is maintained, and the relevant batch, location, route, or resource is not written into the candidate field set of the warehousing operation plan.

[0104] The processor writes the results of multi-layered warehouse visualization management, operation execution status records, operation completion status records, partial completion status records, execution feedback restriction records, inventory confirmation records, correction confirmation records, freeze processing records, release processing records, review confirmation results, and status confirmation results into the same version number of the warehouse digital twin base record. The status confirmation result includes the version number, document number, batch number, storage location number, path number, resource number, scheme number, restriction record number, status code, source record type, source record number, and update time. After the status code and source record number generated from execution feedback, inventory confirmation, review correction, freeze processing, or release processing are written into the corresponding business object data, the processor writes the updated business object data into the warehouse digital twin base record.

[0105] In this embodiment, as Figure 5 The diagram shows a comparison of the effective formation rate of warehousing operation plans under different business document association scenarios. The test samples consisted of business document records, batch occupancy records, storage location time slot occupancy records, and path resource occupancy records generated within 30 consecutive working days at the same warehousing site. The total number of sample business documents was 500, including 100 samples each for single-batch outbound, cross-batch outbound, waiting-to-release inbound, transfer-continuation inbound, and outbound affecting inventory count. Both the conventional warehousing management system visualization method and the method of this invention use the same business documents, material batches, storage locations, path resources, and operation time data for processing. Specifically, the conventional warehousing management system visualization method refers to recording business documents, material batches, storage location time slots, and path resources separately, and generating operation prompts primarily based on inventory quantity and storage location occupancy status. The effective formation rate of warehousing operation plans refers to the proportion of sample business documents that can form warehousing operation plans or warehousing operation restriction records, and whose corresponding batch number, storage location number, path number, resource number, and source record number are all written, out of the total number of sample business documents. Figure 5 It is evident that, in scenarios such as single-batch outbound, cross-batch outbound, pending release inbound, transfer-follow-up inbound, and outbound affecting inventory count, the effective formation rate of warehousing operation plans corresponding to the method of this invention is higher than that corresponding to the visualization method of conventional warehousing management systems, especially in the scenarios of pending release inbound and transfer-follow-up inbound. This indicates that by recording the acceptance of business performance judgment records through warehousing object relationship records, and writing the expected release slice, receiving result, release receiving result, and affected business document number into the same business processing chain, the status acceptance relationship between outbound, inbound, transfer, and inventory count can be maintained continuously, thereby improving the completeness of the formation of warehousing operation plans and warehousing operation constraint records.

[0106] In this embodiment, as Figure 6The image shows a comparison of the completion rate of layer status synchronization under different job execution feedback types. The test samples are from... Figure 5 The corresponding warehouse operation execution feedback data generated within the same statistical period has a total of 500 samples, including 100 samples each for operation completion feedback, partial completion feedback, batch feedback restrictions, storage location feedback restrictions, and route resource feedback restrictions. Both the conventional warehouse management system visualization method and the method of this invention use the same warehouse operation plan, warehouse operation restriction records, and operation execution feedback data for processing. Specifically, the conventional warehouse management system visualization method refers to a processing method that, after operation execution feedback is generated, mainly updates document status or inventory quantity, without synchronously writing operation completion status records, partial completion status records, or execution feedback restriction records into the multi-layer display records. Layer status synchronization completion rate refers to the proportion of feedback samples in the document fulfillment layer, batch commitment layer, storage location time period layer, route resource layer, operation plan layer, restricted source layer, or inventory object layer, where the corresponding object can have its status code, source record number, and associated object number written, relative to the total number of similar feedback samples after operation execution feedback is generated. Figure 6 As can be seen, under various feedback types, including operation completion feedback, partial completion feedback, batch feedback restrictions, location feedback restrictions, and path resource feedback restrictions, the layer status synchronization completion rate of the method of this invention is higher than that of conventional warehouse management system visualization methods, especially in scenarios involving partial completion feedback and path resource feedback restrictions. This indicates that by integrating warehouse operation plans and warehouse operation restriction records with multi-layered warehouse visualization management results, and generating operation completion status records, partial completion status records, or execution feedback restriction records after execution feedback is formed, the source of the restriction, the source record number, and the feedback status can be written into the warehouse digital twin basic record, thereby improving the synchronization update capability between the visualization layer and the business object status.

[0107] In summary, this invention generates business performance determination records based on warehouse object relationship records, continuously writing the expected release slice, receiving result, release receiving result, and affected business document number, realizing the status handover between business documents, material batches, storage location time periods, and path resources, which supports the generation of warehouse operation plans and warehouse operation restriction records. Through the linkage update of multi-layer warehouse visualization management results and execution feedback restriction records, the restriction source, source record number, and feedback status are written into the warehouse digital twin basic record, achieving the effect of continuous transmission of business status and synchronous update of visualization status.

[0108] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A visual management method for material warehousing based on digital twins, characterized in that, include: Acquire basic warehousing data, generate basic warehousing digital twin records, and form warehousing object relationship records based on the correspondence between business documents, material batches, storage location time periods, path resources, and visualization status; Read pending business documents through warehouse object relationship records, generate business performance judgment records according to document type, and write the expected release slices formed by outbound, the receiving results formed by inbound, the release and receiving results formed by transfer, and the affected business document numbers into the business performance judgment records. Based on the business performance judgment record, read the warehouse object relationship record, generate warehouse operation plan or warehouse operation restriction record according to batch commitment status, storage location time period status, route resource status and affected business document status, and generate warehouse operation sub-plan when the same document corresponds to scattered operation objects. Based on the warehouse operation plan, warehouse operation restriction records, and operation execution feedback data, the visualization configuration data is read and the operation status, restriction source, associated object, and status code and source record number generated by the feedback are written into the corresponding layer. This generates multi-layer warehouse visualization management results and status confirmation results corresponding to the warehouse digital twin basic record version, and the status confirmation results are written into the warehouse digital twin basic record.

2. The material warehousing visualization management method based on digital twin as described in claim 1, characterized in that, The process of acquiring basic warehousing data, generating basic warehousing digital twin records, and forming warehousing object relationship records based on the correspondence between business documents, material batches, storage location time periods, path resources, and visualization status includes: When generating the basic records of the warehouse digital twin, the processor binds the business documents to the material batch with the commitment field, binds the material batch to the storage location with the occupancy field, binds the storage location to the scheduling period with the occupancy time, binds the storage location to the path resource with the accessibility field, and binds the business object to the visualization status with the status field, forming a warehouse object relationship record.

3. The material warehousing visualization management method based on digital twin as described in claim 2, characterized in that, The step of writing the expected release slices generated from outbound shipments, the receipt results generated from inbound shipments, the release and receipt results generated from transfers, and the affected business document numbers into the business performance determination record includes: When generating a business performance determination record, the processor reads the quality status code, freeze status code, project ownership, validity period, committable quantity, and outbound order from the outbound order, filters candidate batches and generates batch commitment results, generates expected release slices based on the location of the committed batch and the completion time of the outbound plan, and writes the expected release quantity, release time, source outbound order, and source batch into the business performance determination record.

4. The material warehousing visualization management method based on digital twin as described in claim 3, characterized in that, The step of writing the expected release slices generated from outbound shipments, the receipt results generated from inbound shipments, the release and receipt results generated from transfers, and the affected business document numbers into the business performance determination record includes: When generating a business performance determination record, the processor reads the remaining capacity, remaining capacity, and location status of the candidate storage locations from the inbound order. If the candidate storage location meets the receiving conditions, a direct receiving record is generated. If the current storage location does not meet the receiving conditions and there is a referenceable expected release slice, a waiting-to-release receiving record is generated. If the direct receiving quantity and the waiting-to-release receiving quantity do not cover the inbound requirements, a receiving difference record is generated.

5. The material storage visualization management method based on digital twin as described in claim 3 or 4, characterized in that, The step of writing the expected release slices generated from outbound shipments, the receipt results generated from inbound shipments, the release and receipt results generated from transfers, and the affected business document numbers into the business performance judgment record also includes: When generating a business performance determination record, the processor reads the batch occupancy quantity of the outgoing storage location and the receiving conditions of the target storage location from the transfer order. When the outgoing storage location meets the release conditions, an original storage location release record is generated. When the target storage location meets the capacity, load-bearing capacity, and material category conditions, a target storage location receiving record is generated. If any condition is not met, a transfer restriction record is generated. Business documents that reference the same batch, storage location, path, or resource are written to the affected business document number.

6. The material warehousing visualization management method based on digital twin as described in claim 5, characterized in that, The process of reading warehouse object relationship records based on business performance judgment records and generating warehouse operation plans or warehouse operation restriction records according to batch commitment status, storage location time period status, route resource status, and affected business document status includes: When generating a warehousing operation plan or warehousing operation restriction record, the processor first reads the batch commitment status and storage location time period status in the business performance judgment record, and then reads the path resource status and the status of the affected business documents. A warehousing operation plan is generated when no restrictions are triggered in any of the states. A warehousing operation restriction record is generated when any of the states in the batch, storage location time period, route resources, or affected business documents triggers a restriction.

7. The material warehousing visualization management method based on digital twin as described in claim 6, characterized in that, The method of generating a warehouse operation sub-scheme when the same document corresponds to a distributed operation object includes: When generating a warehousing operation sub-plan, the processor splits the scattered operation objects under the same business document according to the batch number, starting location number, target location number and operation quantity, and reads the corresponding path number, resource number and planned time respectively to generate warehousing operation sub-plans with the same plan number and different sub-plan numbers.

8. The material warehousing visualization management method based on digital twin as described in claim 7, characterized in that, The step of writing the operation status, restricted source, associated object, and the status code and source record number generated by the feedback into the corresponding layer includes: When generating multi-layer warehouse visualization management results, the processor reads the warehouse operation plan, warehouse operation restriction record, affected business document prompt record, inventory object set and visualization configuration data, writes the fulfillment status of business documents to the document fulfillment layer, writes the batch commitment status to the batch commitment layer, writes the location occupancy and release status to the location time period layer, writes the path resource occupancy status to the path resource layer, writes the operation plan status to the operation plan layer, writes the warehouse operation restriction record to the restriction source layer, and writes the inventory object status to the inventory object layer; After the operation execution feedback data is generated, the processor writes the status code and source record number corresponding to the operation completion status record, partial completion status record, or execution feedback restriction record into the corresponding layer. The execution feedback restriction record is written into the restriction source layer, and the operation completion status record or partial completion status record is written into the document fulfillment layer, batch commitment layer, storage location time period layer, route resource layer, or operation plan layer.

9. The material warehousing visualization management method based on digital twin as described in claim 8, characterized in that, The generated multi-layered warehouse visualization management results and status confirmation results corresponding to the basic record version of the warehouse digital twin include: When generating multi-layer warehouse visualization management results, the processor writes the object number, status code, source record number, associated object number, and update time into the layer display record. The source record number includes the record number corresponding to the business performance judgment record, warehouse operation plan, warehouse operation restriction record, affected business document prompt record, inventory object set, operation completion status record, partial completion status record, or execution feedback restriction record. When the same layer number, the same object number, and the same source record number correspond to at least two status codes, the primary status code is determined in the order of restricted status, pending verification status, reserved status, expected release status, current occupied status, and executable status, and the statuses that are not used as primary status codes are written into the secondary status field. The processor binds the layer display records to the version number of the warehouse digital twin base record, forming a multi-layer warehouse visualization management result corresponding to the version of the warehouse digital twin base record.

10. The material warehousing visualization management method based on digital twin as described in claim 9, characterized in that, The step of writing the status confirmation result into the warehouse digital twin basic record includes: After reading the job execution feedback data, the processor establishes a correspondence between the job execution feedback data and the warehouse operation plan based on the feedback number, plan number, and sub-plan number, and generates a job execution status record. When the feedback data meets the confirmation fields of the warehousing operation plan, an operation completion status record is generated; When the number of feedback responses is less than the number of solutions and partial fulfillment is allowed, a partial completion status record is generated. When feedback data triggers batch, quantity, location, route, or resource restrictions, an execution feedback restriction record is generated. The processor updates the multi-layer warehouse visualization management results based on the job completion status record, partial completion status record, or execution feedback constraint record, and writes the status code and source record number generated by the feedback into the warehouse digital twin basic record.

Images