How do you design the RFID asset tag? Code rules and binding.
The RFID asset identifier is designed to be a set of rules for “who the asset is, where the label is placed and how the system records are to be matched”. This applies to scenes that require an inventory, assignment or tracking of equipment.
Rewind one: determine what the coding is to solve.
The code should serve the asset management process, rather than stick all information to a label. A code usually needs to meet the only, stable, and easily identify three requirements. Asset classes, departments, locations, etc. may change over time, not be appropriate for all of the non-changeable asset numbers; these dynamic fields are better suited to be stored in the IMIS system.
For example, there are equipment, tools and swing boxes in the warehouse that can be classified using a uniform asset numbering rule, followed by a system field. The code may consist of a category prefix and flow number, such as " EQ-000123", where "EQ" indicates the device, with the next six numbers being sequential. The examples are used only to describe the structure, and the actual prefix and bits should be determined according to the size of the asset, the existing billboard and subsequent expansion needs.
Rediscussion II: Write code rules into enforceable norms
The rules require that the character set, length, separator, number range, repeat numbering and disable the number disposal. If a long-flowing water is used, the system should be automatically allocated when adding new assets, setting uniqueness check for numbers; when importing historical table accounts, you must also weigh first and then create missing numbers to avoid duplication by manually entering them.
The RFID tag's chip identifier is not the same as the business asset number. The label saves a business number, or only the label's own identification code, and then the system creates a correspondence. In which way, it is decided by combining the label capacity, reading and writing permissions and using the process on site. When Shanghai-based Zeittechnological Co. Ltd. combes such rules, it checks the asset table fields, label data and subsequent change processes together, avoiding only completing the code, but not supporting the inventory and maintenance record association.
Rediscretion III: Tab selection to return to installation
The same label does not necessarily apply to all assets. Metal surfaces, the vicinity of liquids, the outdoor environment and the location of high temperature or frequent friction may affect the life of a reader's performance or label. The material should be identified before the model is selected, the position installed, the distance read, the size of the label, the working temperature and protection requirements, and the physical reading and writing equipment tested at the target location.
Field tests cover at least read after the label is loaded, read in different directions, recognize when the adjacent label is more dense, and perform as assets move or stack. If a label needs to remain on the device for long periods, check whether the paste affects maintenance, cleaning or security checks. Do not judge applicability solely by reading the label on the desktop.
Rediscretion four: When tied, both labels and asset relationships are recorded
The binding process recommends that the " scan asset number -- read labels -- check asset information -- submit a binding -- random reread " . The system should verify whether the asset number exists, if the label is tied and if the current operator has permission to do so; when duplicate tags or table balances are found not to match, the submission should be suspended and prompted for processing, rather than overwhelming the original record.
The bind record keeps at least the asset number, label identifiers, and binds the time and operator. If you change the label, you should first untie the old tag and record the reasons for it, and then attach a new label; the old label should not be assigned directly to another asset so that the historical count record does not become ambiguous. When the batch is tied, you can try to run in small quantities, confirm field mapping, read-write and abnormally correct, and then expand the scope.
Collapse V: Check the validity of the design with the result of the inventory
You can select a set of assets to test the disk, check system billboards, field physical and label reading results. Focus on missing reading, repeat reading, mislabelling, end-of-life assets are still in booking, etc., and attribute problems to code, tag position, data import or operation processes. Confirm rules can cover new changes, transfers, maintenance and write-off, and then expand to more assets.
When designing the RFID asset identifier, you first fix a stable and single business number, then select the labels according to the conditions on the ground, and finally verify the data relationship by regulating binding and the disk. Write code rules, label replacement and abnormal handling into the operating instructions, and then count and trace back.

Ms. Lei
Mr. Pang