Hardware
One Platform, Any Hardware Vendor
Connect RFID, BLE, UWB, GPS, or IoT through a vendor-agnostic Hardware Abstraction Layer — so you never lock the platform to one reader brand.
Overview
What hardware covers in the platform
One abstraction layer normalizes device events onto the same asset record.
- 01
Vendor-agnostic connectors
Plug in RFID, BLE, UWB, GPS, or IoT without rewriting the core platform.
- 02
Normalized location events
Reads and presence land as structured updates finance and ops already trust.
- 03
Grow into RTLS
Start simple, then add real-time location when the site is ready.
Challenges
What HAL solves
Vendor lock-in
The asset system only talks to one RFID brand — swapping hardware means swapping software.
Mixed device chaos
Sites run different readers and tags, so every integration becomes a one-off project.
RTLS feels bolted on
Location streams live outside the register, so ops still reconcile by hand.
Start or stall
Teams delay go-live because hardware is mandatory — even when QR would be enough.
Capabilities
What HAL delivers
What is HAL
The Hardware Abstraction Layer sits between devices and AssetZA so hardware brands can change without changing the platform.
Hardware types
Connect RFID, BLE, UWB, GPS, barcode, and IoT sources through the same integration path.
RTLS capability
Stream presence and movement into the register when sites need continuous location, not only scans.
No vendor lock-in
Keep the freedom to mix brands and replace readers without ripping out the asset system.
Start without hardware
Run Standard with QR and mobile scanning first — activate Hardware-Ready or Enterprise RTLS when you need it.
Audit handoff
HAL feeds physical verification and RFID sweeps so counts finish on the same asset timeline.
Evolve the stack
Change readers, tags, or vendors over time — the abstraction layer keeps AssetZA stable underneath.
Need physical verification next? Continue to Audit & Reconciliation.
How it works
Five steps, one hardware path
- 01Connect
- →
- 02Abstract
- →
- 03Stream
- →
- 04Locate
- →
- 05Record
Outcomes
What teams gain from vendor-agnostic HAL
No hardware hostage
Change readers without rewriting the asset platform.
One event pipeline
Scans and location streams join the same register ops already uses.
Right-sized rollout
Start without RFID, then add BLE or RTLS when the site needs it.
Who it's for
Built for the teams that own the stack
Three roles. One abstraction layer.
IT & security
Integrate devices without locking the estate to a single vendor roadmap.
Ops & facilities
Use scans and location events that land on the same asset record.
Systems integrators
Connect mixed hardware portfolios without custom forks per brand.
Continue exploring
Related capabilities
Frequently asked questions
What is a Hardware Abstraction Layer?
A Hardware Abstraction Layer (HAL) sits between physical devices and AssetZA. It normalizes RFID, BLE, UWB, GPS, and IoT events so the platform stays stable even when hardware brands change.
Can asset management software work with any RFID reader brand?
AssetZA is designed to be vendor-agnostic through HAL — connect supported RFID and related hardware without locking the core platform to one manufacturer.
Do I need RFID hardware to use AssetZA?
No. Standard operates with QR, barcode, and mobile camera scanning. Hardware-Ready and Enterprise RTLS tiers activate RFID, BLE, and real-time location when you need them.
What is RTLS in AssetZA?
Real-time location (RTLS) streams presence and movement into the asset register through HAL — for sites that need continuous location, not only scan events.
How does HAL help audits?
HAL-fed reads power physical verification and RFID sweeps so counts and exceptions stay on the same asset timeline as Audit & Reconciliation.