How does the warehouse material management system bind the RFID logo? From primary data, from EPC to inventory.
RFID Knowledge

How does the warehouse material management system bind the RFID logo? From primary data, from EPC to inventory.

PublishedShanghai Zejie Smart Technology Co., Ltd.

The RFID binding in the warehouse material management system is essentially an identity governance: the system needs to know what this label represents, which batch, which packaging level it is, and whether the current relationship is still valid. A simple encodement of materials into the EPC will only solve some of the identification problems, cannot handle unboxing, ZoI, re-signing, stale and batch changes. A more secure solution is to tag identity, maintenance of material master data and inventory business relationships, and creation and updating of links through a program that can be audited.

First, three data are separated: master data, label identity and inventory relationship

Material master dataDescription of “what” including material coding, name, specification, unit of measure, packing rules and batch strategy;Tag Identity(a) The description of “which label”, which typically includes the standardized EPC, and records, if necessary, chips TID, loting and security verification information;Inventory relationsDescribe “where and what business it is now”, including the location, quantity, stock status, documentation and time of validity.

The three types of information changes at different rhythms. The name or specification of the material should not lead to a full rewriting of the historical label; and it does not mean that a tray is split, nor does it mean that the tray label continues to represent all the materials in the box. Put them in the same field or in the same simple table, which appears convenient for the short term, and difficult to explain at a later stage.

Recommended data hierarchy
Data Layer Questions answered Typical changes
Material master data What is this material, how to measure and manage it? Name, specification, unit, batch policy adjustments
Tag Identity Which label was read on the scene? Issuance, recovery, scrapping, re-signing
Object Relationship Which single item, box, tray or vehicle the label currently represents Tie, untie, aggregate, split.
Inventory services What happened this time, in the mail, in the vault or in the inventory? Treasury, Treasury, Redeployment, Processing of Variances

If a system is to retain both its current and historical relationship, the relationship sheet should have a status and time of effect, or an independent relationship changes log records. This is how it answers "What this label stands for at some point in time," not just "what it stands for now."

EPC design focuses on stability and uniqueness, not as much information as possible.

The EPC can be used as a business identity for labels, but it is not recommended to encode the library position that changes frequently, the inventory status or the entire current batch. The repository will change, the packaging relationship will change, and the tag identity will be better stable; the business system acquires the current properties by binding relationships, avoiding rewriteing each vault and risking failure to write.

In the actual project you can choose a standardized enterprise and object encoding scheme or generate a single internal number from the system. Either way, you need to define lengths, character sets, case set, lead zero, hexadecimal display and space processing rules in advance. The EPC that returns the device is standardized and then re-enters the library without allowing different terminals to save the same identity in different formats.

The tag chip's TID is usually used to identify the chip itself, and cannot be confused with a writeable business EPC. If business requires greater protection against substitution, it can combine the EPC, TID, label release batches and operation records, but it should still be determined on the basis of actual risk, so that no unmaintainable process is created for the purpose of adding fields.

The binding relationship sheet should at least explain “who, what, where, when”

The binder is not a substitute for the material's primary data, but a bridge between RFID identity and business object. Field design should serve search, verification and traceability, and not just EPC and material coding fields.

RFID Bind Relationship Field Proposal
Field Groups Content of recommendations Purpose
Tag Identity EPC specification, display value, TID (optional), label type Unified search and distinction between business identity and chip identity
Object Identity Object type, material ID, single-serial number, packing level Indicate whether the label represents a single, box, tray or weekly reproduction
Business Properties Batch, quantity, unit of measure, production or validity period (as required) Support for batch management and volume reconciliation
Life cycle Issued, bound, in storage, split, untied, scrapped, etc. Avoiding old labels being used again as valid labels
Audit information Operator, source document, equipment, time, effective and expiry time Mis-routing, re-signing and relationship changes

The "object type" is important. The same material may have individual labels, box labels and tray tags, which cannot be considered the same level because they all point to the same material code. The system should specify paternity and quantitative boundaries, otherwise the inventory will count the tray and the individual item in the box over again.

IV. The binding process should be split into issuance, coding, confirmation and entry into force

Label binding should not be done once by a " save " button. It is recommended that the process be unbroken so that every step can have a checkable result.

  1. Application and allocation:To request labels based on material, packaging levels and business documents, to assign unused tag identity.
  2. Encoding and Printing:Writes EPC to label or print visual information, and keeps it to the device and operation records.
  3. Read back confirmation:Reread the label after writing, verify whether the EPC is complete, format is regulated and duplicate identity appears.
  4. Business binding:Select material, batches, quantity and object levels, establish relationships and verify documents.
  5. Entry into force:Only through a certified relationship is the serviceable status; failure records enter the queue to be processed.

If the label identity is randomly generated by the device, the system still needs to be uniquely verified at the service end; if the EPC is created by the rules, it also has to prevent the simultaneous operation from being assigned to the same serial number. When tied successfully, the system should be able to check the business object from the EPC and find all valid tags from material and batches, without a two-way search.

V. Relationships between trays, boxes and individual items to support aggregation and separation

The most vulnerable scene in the warehouse is not a single binding, but a change in the packaging level. A tray can contain more than one box, and a box may contain more than one item; only a pallet may be bound when received, and then the case or item will be removed when selected. The system needs to record business events that are "relationship-building" and "resolved" and cannot cover the current state.

If an enterprise does not need to trace each individual item in the box, do not force a single relationship for “looks more sophisticated.” The more fine the size of the particle is, the higher the cost of labelling, binding, unpacking and unusual handling, the value of which should be determined by the retroactive value of the business.

Untie, change of sign and write-off as a formal process, not a direct field change

When labels are damaged, materials are repackaged, binding is wrong or the choreographer is scrapped, the system cannot simply change the EPC to another material code. Direct coverage can destroy historical traceability and may also deprive existing inventory services of their original identity.

  1. Freezing of the original relationship, recording of reasons, operator and associated documents.
  2. Confirms whether the old label is still on site and if necessary, marks it as non-reusable or obsolete.
  3. Creates a new identity for the new label, and completes the return reading and unique verification.
  4. New and old label replacement relationships are established in accordance with operational rules, but not to merge the two identities into one.
  5. Continuous records of the time-to-time and subsequent re-signing are maintained in inventory and retroactive queries.

Disconnection also distinguishes between “packaging splits” and “business avoidances”. The former are changes in normal relationships, which may require elimination or re-censorship; and the use of the same button to handle both scenarios, with subsequent difficulties in determining whether the inventory difference is a normal split or misdirected.

VII. ENDING DATA AUTHORITY AND CORRECTIVE COMPLICATIONS ON THE RESPONSE OF EMP, WMS

ERP, WMS, label services and equipment collection procedures may each save a part of the data. Before starting the project, it is clear: name of the material, specification and batch maintained by whom; who distributes the tag identity; who confirms the amount of inventory; or whether the RFID collection service submitted an original event or a judged business event.

The interface shall take into account at least the following:

If multiple systems can modify binding relationships, provide a source, version or log change to avoid one system having just finished the change of signature, another system being covered with old data. Data synchronization is not equal to business relationship, and ultimately it is checked through a disk and business document.

VIII. VERIFICATION LISTS BEFORE THE RELEVANCE

Before being formally used, it is recommended that at least the following inspections be completed:

The check should not be done only on the day of the go-live. The labels and packaging, the storage position and the way you operate, will change, and businesses will also need to set up regular spot checks and relationship anomalies such as long-term unused tags, an EPC for multiple active objects, multiple current labels for the same object, etc.

Conclusion: Manage RFID as an identity system

The difficulty of RFID labels being tied to material master data is not usually "can write an EPC" but how to maintain identity on a continuous basis, with clear relationships and retroactive changes. Stable EPC, clear object level, auditable binding process and interfacing rules, among others, together form a reliable basis. First select one material category or packaging level to complete the closure, then expand to more objects based on actual retrospective value, often to control risk more than once-in-time labelling all materials.