How does RFID solid fund management work? Process and data synchronization mechanism
RFID Knowledge

How does RFID solid fund management work? Process and data synchronization mechanism

PublishedShanghai Zejie Smart Technology Co., Ltd.

One count, we're on the RFID.

At year-end last year, an electronic components factory took its annual inventory. Three staff with Excel sheets walked from the first-floor warehouse to the fourth-floor offices, checking over 1,000 fixed asset records individually. It took nearly three weeks, and the figures still did not match. Of 47 laptops on the books, only 38 could be found, while 12 pieces of equipment in the warehouse had no record.

This "no-good" is almost the wall that every firm will hit with a fixed asset management. The more it gets, the more it gets. The more RFID is fixed, the more it goes. The next three pieces are clear, the process and the synchronized mechanism.

Phase one: Don't be too quick to label and get the basics right.

Many teams step through the pits directly into the label, and find that the accounts are per se messy. RFID is a tool that can tie "physical" and "system records" more precisely, but it can't help you correct your already dysfunctional accounts.

The first is to take an asset inventory, to put the existing accounts and objects one by one, to register the latest position, to find the missing process that requires a scrap or loss, to leave a written record. Second, to make code rules, it is recommended that each item be singled out in the manner of "corporate code + large class + sequence" with 8 to 12 more long, appropriate for length, too short to repeat, too long to manage. Third is label selection, metal surfaces, plastic casings, paper files, and RFID labels are different, metal environments generally need anti-metal tags, and read distances are stable. The fourth is the segregation of inventory areas, which are divided into warehouses, workshops, office areas by floor and function, with clear responsibility for each area.

In one of the projects we did, it took two weeks to do that step. It was slow and later found that the two weeks saved three months of work — the accounts were clear and the labels were useful.

Stage 2: Apply Tags, Place Readers, and Collect Data

Once preparation is complete, put the tags into actual service. The most common problems at this stage are tags that cannot be read after application and readers installed at a doorway that achieve only a 60% identification rate.

Tab Paste LocationIt is. Put it on the flat surface of the article as much as possible, avoid direct contact with metals (unless on-metal tag is used), avoid high temperature sources (such as equipment heat vents) and avoid the edges that are easily worn. An office computer, labeling on the side of the host, is more securely located at the bottom; a machine-bed device, attached to the outside of the control cabinet. After this, a reading test is done each case, confirming that the signal is properly re-logged into the system.

Reader & Write PointThe warehouse entrance usually contains UHF channel readers (UHF, working frequency 860-960 MHz), reading distances of 3-8 metres, which can be automatically identified when a cart or person passes. The office area door is restricted to an intermediate frequency reader (HF, 13.56 MHz), reading distance 10-30 cm, and requires people to draw their own cards in close proximity. Some places need to be located at a fixed location, such as the archives room, valuable equipment rooms, are equipped with desktop readers, and help with a single disk.

Reader's place is finished and you have to connect. Each one of the devices goes on a system run, the simulated man-carrying passes, and records the drop rate and error rate. The general requirement is less than 5% for missing and less than 1% for error. If a certain location does not meet the standard, you first check the label angle and the reader antenna for a direction, and see if there are any sources of interference around it.

There are two ways to trigger data collection. One is:Event Trigger, the reader detects a record of the label entering or leaving the signal range; the other isTime-activatedFor example, you can take an automatic inventory of the entire time at two o'clock a day and generate a list in place.

Phase three: Data Synchronization, which is the key to whether RFID will land.

The label is all right, the reader is all set, and many teams come here and think it's over. But what really determines whether the system works is how back-office data can be connected to existing ERP, financial systems. This piece of work could turn into an island if nobody looks at it.

There are usually three mechanisms for data synchronization.

The first is real time synchronization.Reader reads the label, immediately pushes data to the ERP asset module through API (interfacing between systems). Usually, you use message queues (such as RabitMQ, Kafka) to do the middle layer, avoiding peak-time data accumulation. Real-time synchronization has the advantage of keeping the accounts up to date, and the downside is that it requires a high level of network stability, and the net can be lost as soon as the data breaks.

The second is the regular sync.Readers first place records in local databases, and push them to central servers every 5 to 15 minutes. This is a strong network-resistant approach, with some delay -- items have been moved, but the system may not show changes until 10 minutes. For most asset management scenarios, 10 minutes are acceptable.

The third is offline sync.Handheld terminals are counted in a grid-breaker environment, data are stored locally and connected to be uploaded as one after the connection is restored. This approach is suitable for deep-seated or outdoor operating scenarios and complements the first two mechanisms.

We usually combine these three types of projects: the entrance goes real time, the normal office area goes regular and the field count goes off line. The middle is converted by a single data medium, however it is collected at the front end, to an ERP that is standardized in a consistent format.

There are two more details in the sync mechanism that can be ignored. One is:Data Validation, every record that pushes past is subject to weight and legitimacy checks, or the same label is read over and over again.An unusual alarm.For example, when a device originally located in a warehouse appears suddenly at the door, the system should automatically trigger an "unauthorized move" alert to asset managers. These rules are not adequate in advance and they are passive when data is filled with problems.

Implementation of the rhythm recommendation: go online in stages, not one-time spread

Another lesson learned is that one step in the way of "in place" should not be pursued. One-time integration of all regions and assets into the RFID system often makes it difficult to deal with them in a timely manner because problems are concentrated.

A more stable approach is to pilot a typical scene -- for example, to build a warehouse that covers 200 to 500 items of assets. The pilot cycle is contained in 4 to 8 weeks, running through labels, readers, back-office systems, data synchronised full links. The pilot stabilizes and then gradually expands into workshops, office areas, and eventually covers all fixed assets. Each extension of a region, re-enacting processes and norms that have already been validated in the previous phase, except for the argument and the dot to be re-modified.

The pilot phase focuses on several indicators: Label reading success (more than 95% recommended), Data HotSync Delay (real time scene controlled at seconds, time scenario not exceeding 15 minutes), Time-Cutting Comparison (which should be 70% less than manual count), and Conformity Rates (optimal status more than 99%, allowing for a reasonable error of about 1%, such as scraping assets to process).

Common issues and responses

Finally, the problems encountered by HF during implementation are listed and psychological preparations are made in advance.

Read distance not to meet target: Usually the label does not match the reading and writing frequency, or the antenna is not aligned. Try re-programping the metal tags, then adjusting the reader power and antenna angles, most of the cases can be solved.

Data Synced with Big DelayChecks if the message queue is stacked, whether the network bandwidth is sufficient and whether database writing is a bottleneck. Synchronization delays from the minute to the second, often with an indexing or batch writing policy for the database being optimized.

The label is covered by metal.The solution is to change the label to anti-metal or to place it on non-metallic surfaces (e.g. plastic case, back of a sign).

The accounts are still not in line.: This is not usually a problem for RFID, but it is an error in the previous account. RFID can expose the problem, but it cannot solve the source. It is impossible to go back to the first stage of asset inventory.

Get the process running. More important than technology selection.

The RFID solid fund management is not very difficult to implement, and the technology is relatively sophisticated. But if it really works, it's not about how advanced the reader is, how much more frequent, but how well it is prepared for a previous period, how poorly designed the data synchronization mechanism is, or how the anomaly process was conceived in advance. These links need to be sharpened a little bit in the project.

If you're planning to start a RFID solid fund management project, it is recommended that you start with a small pilot, run the whole chain and expand it gradually. And treat the data synchronization mechanism as an equally important job for hardware deployment, define interface specifications in advance, synchronize policy and unusual alarm rules in advance. The more well prepared you are, the better you are going to be.