Fixed-Asset Management FAQs (RFID + Barcode)
Answers for everyone—non-technical users, business leaders, IT & security, finance, and operations teams.
For Everyone (Non-technical Basics)
RFID + Barcode at a glance.
1) What’s the difference between RFID and barcodes for asset tracking?
Barcodes require line-of-sight and are scanned one-by-one. RFID uses radio waves, so you can read many assets at once—even if the tag isn’t visible.
2) Do I need both RFID and barcodes?
Often yes. RFID accelerates audits; a printed barcode/QR on the same label provides human-readable backup and phone (BYOD) scanning.
3) Will RFID tags work on metal or near liquids?
Yes—if you choose the right tag. Use metal-mount tags on metal and tuned inlays near liquids. Tag selection is the #1 performance factor.
4) Will the tag fit my small or curved items?
There are mini, flexible, and curved-surface options. For very small assets, consider HF/NFC or micro-UHF tags.
5) Is RFID safe?
Yes. Passive UHF tags are battery-free and only reflect energy from a reader. Reader power levels are similar to common Wi-Fi equipment.
6) Can a phone scan RFID?
Phones can read NFC (HF). For long-range UHF (RAIN) used in fast audits, use a handheld reader or phone sled.
7) What happens if an RFID tag is damaged?
Fall back to the printed barcode/QR and human-readable ID. Keep a small spare-tag kit to reprint/retag on the spot.
8) How accurate is RFID counting?
With proper tagging and procedures, 98–99%+ asset-level accuracy is common; audits are typically 10×–50× faster than barcode-only.
9) Do I have to tag every asset?
Prioritize (IT, tools, medical, high-value), then expand in phases. You can mix tagged and untagged items during rollout.
10) How long do tags last?
Polyester labels: 3–7 years indoors. Metal/industrial plates: 10–20+ years. Longevity depends on material, environment, and cleaning chemicals.
For Business & Operations Leaders
What it changes for your audits, utilization, and ROI.
11) What problems does RFID actually solve beyond barcode?
Faster audits, fewer “ghost assets,” better utilization, shorter year-end closes, easier insurance/compliance evidence, and reduced loss/theft.
12) What does a typical solution include?
Asset software (cloud/on-prem), RFID handhelds or sleds (optional fixed readers), an RFID printer/encoder, and dual-tech tags (RFID + barcode/QR).
13) What business data can we see?
Ownership, last-seen location, maintenance status, warranty dates, depreciation class, and movement logs (room→room, site→site).
14) How does it help audits and stock-takes?
Walk the area with a handheld; bulk-read assets in seconds. The app shows found/missing/unexpected live and can prompt photo proof.
15) Can it track assets between locations?
Yes—use check-in/out workflows and, optionally, fixed readers/portals at gates for automated movement logs.
16) What KPIs should we expect?
Audit time ↓ 70–90%, accuracy ↑ to 98–99%+, write-offs ↓, asset utilization ↑, investigation time ↓. Many teams close audits in days, not weeks.
17) What’s the ROI driver?
Labor savings on audits, reduced capital spend from re-use of “found” assets, and compliance risk reduction. Typical payback: 6–18 months (scope-dependent).
18) Will this disrupt operations?
Rollouts are staged: tag critical areas first, run parallel with barcode, train champions, then scale floor-by-floor.
19) How do we manage exceptions?
The app flags duplicates, untagged/new items, and damaged tags. Operators can reprint/retag on the spot with portable printers.
20) What about staff adoption?
Keep scanning flows under 3 taps, show instant feedback (e.g., “found 42/47”), and gamify progress. Pair with short task-based training.
For IT & Information Security
Standards, integration, security, and device management.
21) Cloud or on-prem?
Both work. Cloud (SaaS) speeds deployment and updates; on-prem suits strict data residency. Hybrid is common (edge readers + cloud app).
22) How do readers connect?
Handhelds via Wi-Fi/Bluetooth to the mobile app; fixed readers via Ethernet/PoE or Wi-Fi. Data flows via REST APIs, webhooks, or MQTT.
23) What standards are used?
UHF RFID: EPC Gen2v2 / ISO 18000-63 (RAIN). Barcodes: GS1 (EAN/UPC/Code-128) and Data Matrix/QR. Printing: Thermal transfer with resin ribbons.
24) Security of tags and data?
Network: TLS, SSO (SAML/OIDC). Tags: Gen2v2 access/kill passwords and serialized EPCs; sensitive data stays in the system, not on the tag.
25) Mobile device management (MDM)?
Android/iOS apps support MDM (Intune, VMware, SOTI). Lock down Wi-Fi, certificates, and kiosk mode for shop-floor devices.
26) Identity and roles?
Use SSO groups for roles such as Auditor, Asset Owner, and Admin. Actions (encode, retag, approve disposals) are permission-gated and logged.
27) Offline mode?
Mobile apps should cache asset lists and queue scans; they sync on connectivity return with conflict resolution.
28) Integration points?
ERP/FAMS (master asset list), HR (custodians), ITSM (tickets), Finance (GL/depreciation), BI (Power BI/Tableau). Prefer event-driven sync for movements.
29) Data model best practice?
Use EPC/Barcode as immutable key; model location as Building/Floor/Room; enforce category, owner, and lifecycle state.
30) How do we test RF in our site?
Run an RF survey in the toughest areas (metal rooms, dense racks) to tune tag choice, placement, reader power, and antenna polarization.
For Finance & Procurement
Budgeting, TCO, phasing and ROI.
31) What’s the total cost of ownership (TCO)?
Software (SaaS or license + support), readers (handheld/fixed), printers/consumables, tags/plates, and training. Tags and labor dominate at scale.
32) How do tag choices affect cost?
Paper/poly RFID labels are cents each; rugged metal-mount tags can be several dollars. Match the tag to the environment to avoid over-engineering.
33) Can we phase costs?
Yes—start with handheld-only and dual-tech labels. Add fixed readers later at choke points when automation ROI is clear.
34) What should be in the RFP?
Standards compliance, read performance in your environment, tag samples & test plan, integration approach, SLAs, training, and success metrics.
35) How do we measure ROI?
Baseline current audit hours, shrink/write-offs, and spares. After rollout, track audit time, “found” assets, and inventory accuracy.
For Operations, Tagging & Hardware
Tag types, readers, printing, and on-site procedures.
36) Which tags should we use?
- General indoor: UHF RFID label (poly) + printed QR/Code-128.
- Metal surfaces: Metal-mount UHF tag/label.
- Small electronics: Short inlay or HF/NFC if space is tight.
- Outdoor/harsh: Anodized aluminum or rugged encapsulated UHF + printed code.
- Tamper control: Destructible or VOID tamper-evident labels.
37) What readers do we need?
Handheld UHF (all-in-one or phone sled) for audits; an RFID printer/encoder for labels; optional fixed readers/antennas at doors or cages.
38) Do we need special printers?
For RFID labels, yes—an RFID thermal transfer printer/encoder writes EPCs and prints barcode/QR + text in one pass.
39) How is an asset encoded?
The app generates a unique ID, writes it to the RFID chip, prints the same ID as barcode/QR + text, and registers all metadata.
40) What about label design?
Include asset ID, barcode/QR, RFID logo, asset name/department, and a service-desk URL/QR. Size for easy phone scanning (30–50 cm).
41) What’s the tagging process?
Clean surface → place tag consistently → press firmly (or rivet/epoxy for plates) → encode/print → verify RFID + barcode → capture a photo.
42) How long does tagging take?
Typical throughput: 200–400 assets/day per 2-person team, depending on access and documentation.
43) Can we reuse tags?
Many UHF labels can be re-encoded. Metal tags are reusable if removed and cleaned, but factor labor time.
44) Common causes of poor reads?
Wrong tag type, placing tags on metal/liquid without spacer, tag shadowed by body, low reader power, or antenna polarization issues.
45) Barcode best practices in a hybrid setup?
Use GS1-128 or QR with the same unique key as the RFID EPC; size generously; add protective laminate in harsh areas.
Features & Workflows to Look For
What your software should deliver.
46) Must-have software features?
Found/missing/unexpected logic, room sweeps, offline lists, photo proof, chain-of-custody, bulk updates, reprint/retag, role-based approvals, audit trail.
47) Reporting & analytics?
Accuracy by location, aging & utilization, movement heatmaps, audit SLA, exception dashboards, and BI exports.
48) Compliance & governance?
Immutable IDs, read-only audit logs, retention policies, user access reviews, and evidence packs for auditors (CSV + signed PDF).
49) Mobile UX details that matter?
Hardware trigger mapping, adjustable read power, near/far mode, haptics on finds, large Found/Missing counters.
50) Service & support expectations?
Spares pool for readers, next-day swap, on-site tagging help, and quarterly governance reviews (accuracy, exceptions, tag usage).
Troubleshooting & “What-ifs”
Common edge cases and fixes.
51) What if two assets respond at once?
Modern UHF uses anti-collision to resolve multiple tags. In extreme density, narrow-beam antennas or lower power improves selectivity.
52) A room shows ‘missing’ items we know are there—why?
Sweep from different angles, reduce power to avoid far reads, verify tag placement, and confirm the asset wasn’t moved in software.
53) Can someone clone a tag?
Cloning a plain EPC is possible. Mitigate with serialized EPCs tied to records, tamper labels, and Gen2v2 features (access passwords). Keep sensitive data off-tag.
54) Do fixed readers pick up assets in nearby rooms?
They can if overpowered or mis-aimed. Tune power, use directional antennas/shielding, and apply zoning with signal thresholds.
55) How to track in outdoor yards?
Use rugged metal tags and higher-gain antennas. For real-time location, consider augmenting with BLE/UWB zone beacons.
56) Can we start with barcode and upgrade later?
Yes. Use durable barcode plates now and select label sizes/materials that can be swapped to dual-tech RFID labels later.
1-Page Buyer’s Checklist
- Choose tag per surface/environment (general, metal, harsh, tiny).
- Standardize on RAIN UHF (Gen2v2) + GS1 barcode/QR with one unique ID.
- Start handheld-only, add fixed readers at choke points if needed.
- Require offline audits, exception workflows, photo proof, and open APIs.
- Pilot in your toughest room; tune tag choice and reader power before scaling.
- Baseline audit hours & shrink; track improvements post-go-live.