How do you write the warehouse code management system solution?
RFID Knowledge

How do you write the warehouse code management system solution?

PublishedShanghai Zejie Smart Technology Co., Ltd.

The only way to get a warehouse code management system solution is to add "barcode fits single, RFID fits bulk." What really needs to be clear is: why does the same box be scanned and read by RFID doorman, and why does it not add two additional inventories; how does the original load list fail when the pallet is broken down; whether manual re-entry has the authority and audit record when the reader is offline. The key to coding with RFID is to have different collections serve with one set of target identities, tasks and inventory rules. This section is subject to an assessable, available, accessible, and receiving program.

The first page of the scheme is covered by the first page, rather than by a pre-written device model

The request statement should at least give the type of warehouse, material and packaging, the size of the management particle, the shift, the order or tray peak, the existing ERP/WMS boundary, and specific errors. If the pain is a queue for receipt registration, the time taken to verify each tray from arrival to confirm; if the pain is a batch of mixed materials, the number must be clearly verified at which node; if the problem is not registered in the migration library, simply adding an entry reader will not be effective.

The scope also indicates the ability not to cover. For example, only the whole box is retrofitted and the whole consignment is shipped in this period, and PDAs are still used for all undefeating in the vault; only the swing boxes are identified without declaring that they have been verified individually; only the goods are confirmed at designated points of contact and no commitment is made to locate them continuously to each warehouse. Once the boundary is clear, there is a consistent basis for the quantity of equipment, interface costs and acceptance standards.

Two carriers of one object: a single business identity, not an original string

Barcodes and RFID are data carriers whose contents identify commodity specifications, individual pieces, boxes, logistics units or assets. They cannot be considered to carry static information only, nor can RFID labels be used as a direct inventory record. The storage system first needs stable operational object IDs, then the code decompose results and RFIDs such as EPC are mapped to objects; different coding formats for different vectors may differ, but the target and validity period must be clear.[1][2]

For example, the internal box number BOX001 has both scanned bar code and RFID identification. The scan is given a box number, radio frequency reads to access the EPC, and both paths are deciphered and map to BOX001. Here, BOX001 is only an internal process indication, not an example of GS1 standard code. If supply chain interconnection is required, Gtin, serial numbers, SSCC, etc. should be selected and used correctly by object type; The ordinary commodity bar code does not automatically distinguish between two boxes or two items of the same kind if only the class of identification.[1][2]

Maps should record the type of vehicle, original value, regularized identity, object type, validity and history of binding. The receiving field keeps the agreed lead zero, characters and separator, not all of which are processed in integers. When labels are supplemented or replaced, check the business object before ending the old relationship and registering a new one; no physical addition to the system is made by changing a label.

A detachment statement: Read the tray, not counting all the cargo in the box

Examples of process design are given below:The tray P001 contains 10 boxes, 12 in each box, 120 in all; the tray is marked with RFID, only the number of boxes outside the box, and individual pieces are not marked with RFID. Read to P001, only the pallet identity can be identified directly. The system can search its loading list and start the whole transfer as agreed, but it cannot claim that this time it has independently identified 10 boxes or verified 120 on a case-by-case basis.

If two cases are removed for dispatch, operators scan the case codes. The system should remove both from P001's current load and record the corresponding inventory movements in accordance with the workflow. P001's manifest should then show eight cases, not the original list of 120 units. The next time the portal detects P001, it should link it only to the updated list. Defining when a loading association starts and ends has more impact on accuracy than the choice of reader.

If the business needs to independently verify each box, then the identifying particle size should be deposited into the box and the corresponding label or scanned step should be used instead of relying on a tray label to extrapolate all lower objects.

The most important rule of double-channel collection: one check only for the same business

For example, the operator manually completes the receipt and then the tray goes through the RFID channel; if both sets of interfaces are directly "stock up one" they are recorded repeatedly. It is not sufficient to weigh only on the short time of the EPC, because the scrutinizing results may differ from those of the EPC, and the same object may have been legally present many times over different stages of the operation.

It is recommended that the collection and over-the-counter be split into two steps: capture record retention equipment, carrier, original value and time; business recognition is linked to IID, document or task ID, object identity, action type and status version. Automatically and manually use the same business confirmation rules, submit the same operation again and again to return the results; objects are read again after receipt, leaving only duplicate collection records without adding additional stocks.

Partial receipt or measurement of material cannot be permanently weighed as task ID+SKU. There may be multiple legal batches under a mission, which should assign the operator ID each time, check the amount of units and cumulative amounts of completion. Backup after device-disconnection cache, recovery after manual retrofitting and mission cancellation are verified in the same state. Otherwise, while the system avoids duplicate tags, it may discard the real second batch as duplicate messages.

Configure the carrier by operational node, and the program sheet is to write the confirmation basis

The device configuration is derived from the operational action: which nodes need to be identified by object, which can be mass-crossing at the validated reading area, and which must be manually judged abnormal. The respective coding and RFID identifications are verified with live packaging and equipment. No promise of bar code being printed clearly will never be scanned, nor will it be read without contact under labels, but by default any sealed box or stacking will be read in full.

Job Node Optional Collection Group Requirements for confirmation to be written in the programme
Receipt Box code sweep, or empirical RFID collection Matching of expected documents, handling of multiples, small quantities and unknown objects, and clarifying differences between container identification and detailed acceptance
Up and Move Library Object code + repository bit code, or combined with device task Matching evidence, validation of source-place, failed mission status
Disable the pick PDA scan and quantity confirmation Box relationship update, batch binding, partial completion and unit conversion
Checkpoint RFID collects candidate pools, bar codes or manual review of differences Scope of the mandate, unread subject review, reconciliations during inventory
Treasury review RFID checks to mark the target, abnormal sweep code. Confirmation of conformity of the mission with goods and review of results as a substitute for final shipment or withholding conditions for all operations

Common delivery criteria for vendors when acceptances are written as fault and recovery scripts

The following scripts may serve as the starting point for the pilot review, and the specific threshold is determined in conjunction with the on-site metronmic and error risk:

  1. After the sweep, we cross the RFID door again:The same object was collected in the same receiving mission by two carriers, with only one valid change of inventory and both retroactive.
  2. The neighbourhood static label was read:Original readings are retained, but may not be included in the current mandate without justification; records are kept of reasons for exclusion or for referral to review.
  3. The whole thing is to be broken down in two boxes and then through:New loading relationships are being used correctly and removed boxes will not be re-taken back to the original tray by the old list.
  4. The mission was cancelled and delayed news received:Expiry collection is not recognized as a new task; late recording of events is done and manual verification is carried out under delegated authority.
  5. RFID offline, recovery after the scan:Cache readings are repeated and failure to complete the task is allowed to continue. Offline operations require prior agreement on operational scope and conflict management, and two uninformed terminals cannot be allowed to identify the same inventory without restriction.
  6. Label break or hit:The validity, human rights and operational history of the old and new markings are consistent and no new stocks will be generated when the old labels re-emerge.

The indicator should distinguish between physical reading and operational results, such as target object capture completeness rate, non-target object error integration rate, document completion accuracy, abnormal processing time and recovery of duplicated number of accounts. Batch recognition tests should list target pools, adjacent goods, speed, placement methods and additional read conditions; " Accumulations are many" cannot replace identification results for different objects.

Budget and revenue are accounted for separately, so that savings in working hours are not directly reflected as job reductions

The list of investments should include labels and consumables, printing and reading and writing equipment, antennas and installation, network power, software authorization or development, ERP/WMS interfaces, field testing, training, spare parts and maintenance. Unlike the one-time tag and recycle label cost, existing bar code equipment should not be charged for a new set of duplicates. The offer should be confirmed on the basis of actual material lists and deployment conditions, and it is inappropriate to extrapolate total investment at no time, with no model market average.

The earnings from working hours can be estimated on the basis of “the annual amount of work that meets the scope of the retrofit x a single net cost of working hours x unit cost of working hours”; the net savings for one time are offset by additional operations resulting from additional work due to the double-reading, unusual review, maintenance of labels and equipment.

The benefits of reducing miscalculation, loss or return should be accounted for using verifiable historical records and preventing the same loss from being calculated over multiple indicators. The operational time and anomaly rates measured on a pilot basis are conservative, the baseline and better scenarios are used to estimate annual net gains; only when the annual net proceeds are positive can a simple recovery period “the annual net cash income from initial inputs” be interpreted as an alternative to formal investment analysis.

The deliverables should include data, interfaces, operational and liability boundaries at the same time

The final delivery list should include: the scope of operations and non-covered items, object identification and tag map, rules for the relationship between boxing and loading, operating charts for each node, record of equipment points and physical tests, interface fields and retest protocols, abnormal operation privileges, acceptance scripts and operational maintenance responsibilities. Only "relay ERP" is too general, and it is clear which system creates documentation, which maintenance material and units, who confirms inventory and how to compensate for failure.

When cross-system recording changes in objects, reference can be made to the way that the EPCIS object, time, location and context organize events; it does not require that each event must come from RFID or that an enterprise rebuilds the entire system simply by using bar code plus RFID.[3] The purchaser should request the supplier to take a true form of business, from identification to inventory confirmation and then restore the whole abnormally. It explains why the same item is only recorded once, why a programme that does not string after detaching is easier to receive than a full package with a full set of equipment parameters.

Information based

[1] GS1 Application Identifiers, describing the meaning of identification and attributes;[2] GS1 EPC Tag Data Standard, which is used to check the EPC coding programme for different objects;[3] GS1 EPCIS and CBV Implementation Guideline, which is used to refer to business events and cross-system data sharing. Object numbers in text, load quantities and test scripts are design examples that do not represent client cases or product performance commitments.