What should be the functionality of the RFID asset management software?
The core of the RFID asset management software is not a single-read label, but a retroactivity process that links asset slotting, tag recognition, position and status change, inventory, maintenance and reporting. This applies to organizations with dispersed assets, frequent flow or time-consuming manual inventory; the model should be selected by checking on-site operations and then checking for consistency in the modules.
Reassembly-building links: asset information needs to be physical
Software usually requires asset billing, classification management and tag binding. The account records the asset number, name, category, use department, responsible person, place of storage, purchase date, etc.; the RFID label is associated with the asset record by a unique code. This way, when the reading/writing device recognizes the label, the system can move out the corresponding asset instead of showing only one set of codes.
When actually configured, you should identify which fields are to be filled, which roles can be added or modified and change records kept. For the same type of asset, you also have to support bulk import, batch file and label printing, and reduce entry by article. Shanghai-based & Cheetech, when combing such needs, will check the account fields, tag code rules and field management calibres together, avoiding a system name for the asset, numbering one with the physical label.
Rediscovering link: Once you read the label, you have to judge business events
The RFID identification module is responsible for receiving tag information that reads, writes or handheld terminals. Software requires a combination of equipment, time, location and operator, which converts the result into business records such as a library, access, return, transfer or exit. If only raw data from the label are available, the person still needs to make a manual judgement about how the asset has changed, and the automation effect will be limited.
- Equipment and regional configuration:Maintains the correspondence between reading and writing devices, fixed reading points and regions.
- Event rules:Sets the business meaning of different identifiers and addresses instances of double reading, misreading and non-matching labels.
- Manual review:Provide records that identify incomplete or unsatisfactory business conditions to be processed and avoid the direct change of asset status by unusual data.
Rewinding flow links: a common set of status for inventory, loan and maintenance
The asset flow module should cover common processes such as receipt, return, transfer, loan, maintenance and write-off, and record the operator, time, place and location. The inventory module supports task generation by department, region or asset class, tagging through handheld devices, creating differences in the discs, undiscounted, not where they are located, and non-account assets. Differences need to be entered into review and processing processes, not just to export a list.
The key is to check whether the status of the asset can be connected: after it has been repaired, the transfer of the rear account should be updated simultaneously and the process should keep a record of approvals and disposals. The software should also provide control over authority and logbooks to track when the asset information was modified. If there are areas in which the network is unstable on site, verify whether the equipment supports offline collection and how to synchronize and deal with conflicts once the connection is restored.
Rewind selection: accept and accept with the actual process, not just on the functional list
The report and query module should enable the asset number, category, department, location and status filter, and check for inventory differences, flow records, maintenance and asset distribution. Selecting tests can select an asset to go through a full process: build and tag, complete the application, transfer and count, check the desk account, log and report consistency; and test for double-identification, not readable labels, and non-alignment of assets.
Operationally, it is important to sort out the type of asset, the rules of management, the area on site and the existing equipment, and then to check and receive them individually by "show-identify-flow-check." It is important to make sure that the functional modules are fully functional, and to make sure that business status is up to date and anomalies can be detected and processed; this is more appropriate than simply comparing the number of menus.

Ms. Lei
Mr. Pang