How do you choose the RFID fixed asset management software?
Core judgement:The RFID fixed asset management software cannot read only "Reads Readable", the selection should verify the asset desk account, label code, inventory process, permission audit and on-site recognition. It is recommended that small-scale tests be done with real scenes, focusing on identification rates, missing reading rates, error rates, time-consuming count and data synchronization results.
Point 1: Identify the RFID by asset scenario
RFID is a radio wave recognition tag technology, and labels need not be scanned like bar codes. The most common programs in fixed asset management are the UHF and HF programs, which first confirm the material of the asset, the distance of the label, the inventory range and the live interference.
| scene | Focus. | Test Method |
|---|---|---|
| Office, classrooms, general warehouse | Batch counts, handheld mobile identification, offline use | Number of labels, number of missing and time-consuming entries recorded by region |
| Metal equipment, cabinets, servers | Anti-metal labels, tag placement, reflect interference | Mark the equipment in different locations, and compare distance recognition and stability |
| Archives, tools, swing goods | Small label size, close range recognition, loan back records | Simulation of access, return, handover and check for repetition |
The UHF program is suitable for regional inventory and mass identification, but the actual distance is influenced by the reading/writing power, antenna direction, label type, asset material and field layout. It cannot be judged solely on the basis of propaganda parameters. The technical specifications refer to the requirements of ISO/IEC 18000-63:2021 for air interfaces, which should still be based on actual field results.
Element 2: Checks whether the software covers the full life cycle of the asset
Software must at least be a series of “scan, label, access, transfer, loan, maintenance, storage, scrap, inventory, retroactive” to record. Only systems that support the entry and inventory may continue to rely on table supplements and are prone to discrepancies in accounts.
- Asset builder:Supports the phrase " asset code, name, type, specification, date of acquisition, original value, responsible person, use department, location, status and photograph " .
- Label Management:Supports tag coding and asset coding, patching, remarking, hanging, cancellation and historical tagging to avoid damage to the label and not be able to preserve the asset history.
- Stream management:Transfers, loans, restitution, maintenance and end-of-life should be operated by the operator, time, place of origin, new location and approval records.
- Inventory management:Support the generation of tasks by department, location, category or responsible person and distinguish between identified, unidentified, irregularly located and non-stated assets.
- Report and Export:The export field should support job-based configurations for the ability to export data relating to asset details, surplus and loss of income, overdue payments, maintenance records and depreciation.
Select the type by taking a set of test data that contains new, transferred, maintained and scrap, and walk through the process in its entirety. Focus is on whether: to keep the original record after the asset has changed position, to have a hint for re-import, or whether the end-of-life asset can be miscalculated into the asset in use.
Element 3: Validation of identification capability by field testing, not only equipment parameters
The recognition capability should be broken down into four indicators: Identification rate, Leak rate, Error rate and Repeated Read control. The following calculation can be used: Identification rate = Number of labels at the site for actual identification tag numbers x 100%; Leak rate = Number of labels for unrecognized tag numbers = 100% at the site. Tests must be based on fixed people, routes, speed of movement and antenna direction, ensuring that results from different software programs are comparable.
- Prepare a real set of assets covering plastics, boxes, metals, proximity to liquids and intensive stacking.
- Establish an accurate list of each asset, recording the tag code, the asset code, its location and the material of the asset.
- Individually test individual reading, bulk reading, mobile inventory, wall or cabinet reading and performance in a strongly disturbed environment.
- Repeat the test at least three times. Record how many tags were correctly identified, which were missed or read in error, and how long each run took.
- Matches the read data with the task list to confirm whether the software automatically marks anomalies, rather than showing only a string of labels.
Software should also handle double reading. When the handheld stays in the same area, the same label may be read many times; the system needs to weigh by time window or task rule and keep original reading records. For high-value devices, closeness confirmation can be increased, photo verification or liability confirmation reduced the risk of mistasking and error.
Point 4: Focus on data, authority and equipment compatibility
The RFID project does not purchase a single scrutinizing tool, and the software is to be matched with handheld equipment, reading and writing devices, printing equipment and existing asset data.
| Check items | Elements to be confirmed |
|---|---|
| Device Connection | Supported handheld terminals, reader connections, offline caches, breakwire reconnections and data transfer mechanisms |
| Data interfaces | Whether basic desktop accounts can be imported through standard interfaces and whether field mapping, incremental synchronization and failure records are supported |
| Permission Control | Access to view, edit, inventory and clearance by organizational, departmental, location and role limitations |
| Operational audit | Whether to record login, re-send, remarking, transfer, end-of-life and export operations and check for pre- and post-modification content |
| Unusual treatment | Is there a clear hint when network disruption, duplicate labels, assets are non-existent, tags have been cancelled and inventory conflicts are counted |
Shanghai-based Selecting Tech, when combing out the needs of such systems, usually separates "functional presence" from "in situ availability" for receiving and inspection: the former checks menus and processes, while the latter tests real assets, real routes and real network environments. This way makes it easier to detect detached inventory, label re-advertising and actual problems with changing location.
Element 5: Setting up test run acceptances with quantifiable indicators
Before the official deployment, it is recommended that a department, a warehouse or one-tier office area be selected for commissioning, with the number of assets set to the actual size, without covering all locations at first. The acceptance and inspection indicators are determined before testing, so as not to be subjectively judged after testing.
- Data integrity:Check asset codes, tag codes, duty-bearers, locations and status to confirm that the system records are consistent with the desk accounts.
- Inventory efficiency:The number of personnel, time-consuming and review times recorded in traditional manual inventory with RFID are compared to the results in the same range.
- Identification stability:Repeat the inventory at the same location to observe whether the omission is concentrated in a material of a particular type, in a label position or in an angle of a device.
- Unusual treatment:Humanly false, leaked, duplicated tags, asset movements and network disruptions, checking the system for prompting and maintaining processing records.
- Use cost:The inclusion of labels, handheld equipment, print consumables, interface development, training and follow-up maintenance in accounting cannot be compared with the purchase price of software.
The test run report should preferably also maintain the original inventory list, the equipment log, an anomaly screen and manual review results. For areas where the recognition rate does not meet internal requirements, a check of label type, installation location and antenna configuration should be made before determining whether the software process needs to be adjusted. Many identification problems are not caused by single software functions, and must be combined with tags, equipment and field environment analysis.
Point 6: Finish software selection according to this list
You can place the candidate software in the same score sheet, setting weights according to business importance. It is recommended that asset life cycle management, on-site recognition capability, data interface, rights audit and implementation maintenance be rated separately, and each requires evidence of demonstration or testing.
- Collating the number, type, material, distribution location and inventory cycle of existing assets.
- Identify the type of labels, handheld equipment and network environment to be used.
- List the functions that must be performed, distinguishing between “necessary” and “subsequent configuration”.
- Prepare test sets with normal and abnormal data.
- On-site inventory testing is done along a single route, recording recognition, leakage, time-consuming and data synchronization results.
- Check interfaces, privileges, logs, reports and subsequent transport arrangements to re-evaluate the overall input.
When selecting RFID fixed asset management software, the number of functions is not a basis for judgement. The more practical criteria are: whether assets can be properly archived, whether labels can be identified in a stable manner, whether anomalies can be detected in time, whether the flow can be recorded and whether the inventory results can be returned to management decision-making. First, small field measurements are done, then deployment ranges are determined by data, usually more secure than purchasing directly on the promotional page.

Ms. Lei
Mr. Pang