What are the functions of the RFID Access Library Management System? Documents and inventory management
RFID Knowledge

What are the functions of the RFID Access Library Management System? Documents and inventory management

PublishedShanghai Zejie Smart Technology Co., Ltd.

What does the RFID access management system deal with?

The system uses RFID electronic tags (a wirelessly readable electronic identity card) to replace traditional bar codes, to match a fixed or hand-held reader, so that goods can be automatically identified and recorded from the library, up, pick up, exit to the inventory. It is not as simple as "cleaning" -- core is to turn documents flow, stock flow, physical stream three flows, stock data moving along with the goods, not back-up. The system usually covers five main modules: document management, real-time inventory updating, bank position and batch back-up, abnormal alarms, docking with data from ERP/WMS.

What exactly does document management do? What types of documents are common?

The system runs five main types of documents: purchase the warehouse, sell the bill, transfer, take a list, other access to and from the warehouse (use, report loss, etc.). Each type of document follows the same process from generation to archiving: produce the billing and review the write-off file, but the logic behind each step is different.

The purchase order usually comes from a purchase order, the RFID portal automatically reads the labels upon arrival in the warehouse, identifies SKU (the smallest inventory unit, i.e., each specific product regulation), quantity, batch, system and purchase order lines, and separate red alarms are given for the difference. The sales warehouse is similar, first creating pre-sorting tasks on a sales order, and the warehouse personnel directs the pick-up through light or PDA, and the exit door automatically reviews whether the actual number of out-of-stock accounts corresponds to the documents.

The document review chain usually supports a first-level or multiple-level review, the approved document is executed and unauthorized access to the library is avoided.

How do you bind the documents and the objects? How do you prevent "unconformity"?

The key to binding is three mechanisms. First, the vaults are tied: each label is bound to a specific repository at the time of entry, the migration bank must be coded and it cannot be moved outside the system. Second, there is batch segregation: the system has to be separated by production date or batch, first by system hint rather than by workers ' memory, 30 days in advance, 7 days in two. Third is document write-off: physical tags, document lines, matching of the three in the library to complete the write-off, and any mismatch triggers an anomaly.

One of the kinds of errors that is common in the actual scene is a mistransmission: 100 documents, 98 access doors, an immediate alarm and denial of release by the system, and a manual review. This is much safer than the traditional bar code "Book-up before Reproduction."

How do inventory data work in real time? Can RFID count really replace manual?

The RFID inventory is faster and less leak. A medium-sized warehouse (5,000 to 10,000 storage places) usually takes 3-5 days; a first reading on the shelf with RFID handheld, 3-6 hours for initial disks, and 1-2 hours for review of differences. If you have a read-and-write device (also known as RFID manual inventory or smart shelf) on the shelf or channel, the goods are automatically read and almost not manually.

Here's a little bit of detail that can be ignored: metal and liquid environments interfere with RFID signals, and general labels are not read in full on metal shelves. So the system configuration is usually "label-fitting" for metal parts, wood products, liquids are selected to use antimetallic labels or adjust the reading and writing frequency.

How does the RFID system usually connect to ERP?

There are three common docking methods: database middle table, WebService/API interface, file exchange. Most ERPs use intermediate table, file header, line item data for the middle table, RFID system for this form generation, execute and write back to the middle table, ERP for the other way. This way is small for ERP, but less real time, it is suitable for minutes-level synchronization.

If it is high for real time, such as electronic signatures on documents, it is recommended to go through the API interface or read the ERP database view directly. The interface fields typically include document numbers, material code, batches, planned number, planned repository positions, actual quantity, physical repository position, operator, time stamp. Data flow is two-way: ERP down, RFID returns the execution results and inventory snapshots.

What pits are easily stepped upon in actual deployment?

The top four are the label type, the reader deployment density, network stability, and personnel practices. The label type is mentioned above, and the metal liquid environment must be labelled with a specific label. Reader's deployment density depends on the size of the label, the antenna gain and the space of the library position, usually with a channel antenna every 3-5 metres, or each reservoir at a separate antenna.

Network stability is easily underestimated. WiFi's dead corner in the warehouse, PDA's file execution data will slow down to the local level, but the storage slot binding may be lost, so key jobs suggest a cable network as backup. Personnel practicer is more subtle: many of the project's early online systems run well, but the data start dirty after several months – the source is that people are having trouble getting through the sweeps. So the system is designed to minimize the number of sweeps, so workers can read them automatically through the portal; and irregular logbooks are created, and reconciliations are regularly conducted.

What size is the system for a warehouse? It's worthless.

See the amount of SKU and the frequency of access to the storage, not the size of the warehouse. Usually SKU has more than 500 or more than 50 daily documents for access to the library, and the return on RFID's input is beginning to appear. The more SKU, the higher the batch management requirements (for medicine, food, gas) and the greater the relative value of the RFID bar code. If SKU has only a few dozen, the daily number of files, the traditional bar codes and manual are actually more cost-effective.

Shanghai Zejie Technology has run the numbers on RFID warehouse projects in several industries. In typical cases, inventory accuracy rises from around 95% with barcodes to over 99.5%, counting labor drops 70%–80%, and wrong or missed shipments fall by an order of magnitude. Hardware and software for a complete midsize warehouse with 3,000–8,000 locations typically pay for themselves in two to three years.

If you're assessing whether to go on the RFID system, you might suggest that three figures be combed out: what is the accuracy of existing stocks, how much annual losses are caused by mistransmissions, and how high SKU and batch complexity can be. These three numbers will help you to judge the value of inputs is not valuable, and it will facilitate and focus on the programme by suppliers.