How does the RFID asset system inventory work?
The most common card point at the site is that the reader has been scanned and the number of assets in the system has not changed in a timely manner. To successfully complete the RFID asset inventory, it is critical to link mission creation, field collection, discrepancy review and results through the books and keep records for each step.
Before the scene: first, we have to define the scope and rules of the inventory.
The warehouse manager enters the storage area with a starting hand-held reader, and if the system does not clearly identify which areas to take this time, which assets are to be scanned, it is difficult to determine whether or not they fall within the scope of the mandate. When creating an inventory, you should first identify the inventory organization, the warehouse or region, the asset class, the person responsible and the planned time, then set the calibration: by asset tag, or by asset location; whether cross-area scanning is allowed; and which assets need to be identified on a case-by-case basis.
The system is linked to a system that reconciles the asset desk account with the label information. The tag code should match the asset records in the system, the status of the asset, the department to which it belongs, and the words in the location to be stored should also have consistent maintenance rules. The task can be set as " pending execution " , and then sent by the responsible person after confirmation of the range and the person, avoiding multiple teams from re-taking the same area.
When collected on site: to position the reading and writing results
After the task is sent, the inventoryer receives a job on the handheld and goes to the specified area for a scan. When the reader is taken into the label, the tags are coded, the task number, the operator, the time and area information is collected and submitted to the system; the system matches the tasks and asset desk accounts accordingly, tags the disc, undisclosed, over-scope or information-incompatible records.
When the label is not read on site, it is inappropriate to treat anomalies as inventory when the same label is repeated or assets are temporarily moved. First, you can check if the tags are broken, the equipment is connected properly, and then re-record or submit an anomaly statement in accordance with the rules of field management. Shanghai-based Zeitung Technology Ltd. will use "collect results" and "manual review" as different links in designing the asset system connection operation process, avoiding scanning actions that directly overwhelm desktop information.
After mandate submission: review of discrepancies before updating desk accounts
After the collection is completed, the system generates an inventory result, by type of discrepancy, as recorded, undisclosed, discovered outside the account, etc. The responsible person needs to verify: whether the unasseted asset is leaking or not on site; whether the off-book labels are assets to be registered; and whether the non-conformity is caused by redeployment or temporary borrowing. After confirmation, select a fillet, adjust the position, initiate changes in the asset or forward approval, and cannot directly recreate the asset status by just one scan.
After processing the difference, the authorized person has reviewed and cleared the account, the system keeps the date of the inventory, the location or status of the asset, etc., and maintains the original record, handles comments and approval tracks. If the system is also associated with the asset-enabled, transfer or maintenance process, state verification should be set to avoid overlaying changes during the count and the results of the check.
End of count: confirm with the record whether the mission is really finished
Before closing a mission, check whether assets within the mandate have been disposed of, whether the exception has been reviewed and whether the discrepancy has been completed. The inventory list and discrepancy details can be derived, retention of task numbers, operating time, personnel, processing results and approval records to facilitate follow-up. The next round of inventory counts will then adjust the area allocation according to the cause or type of difference not recorded, tag maintenance or on-site operation statement. The tasks, collection, review, approval and desk account update are gradually linked, the results of the inventory can be easily reconciled and the asset data maintained on an ongoing basis.

Ms. Lei
Mr. Pang