In asset tracking, a zone is an area that means something operationally: the IT store, the operating theatres, the yard, Site B. Zones are typically built from locations in your location hierarchy and, where readers are installed, from the area each RFID reader or portal covers.
Why it matters
Zones turn raw reads into meaning. "Tag …3F2A read by reader 7" is noise; "Infusion pump 22 entered Ward 3" is information. They also let you set where each asset belongs — which is what makes zone-exit alerts possible.
Designing zones
- Match zones to decisions — if nobody would act differently knowing an asset moved between two rooms, they can be one zone.
- Put readers at the boundaries that matter (doors, gates), not everywhere.
- Define allowed zones per asset or per category rather than one by one.
Example
Zone "Secure Store" = Store Room 1 + Store Room 2, covered by Portal-04 at the only exit. Category "AV equipment" is allowed in Secure Store and the Events Hall.
In Asetavo
Zones (Business plan) map locations to reader coverage, with allowed zones set per asset or category. You can also run zone-scoped audits with handheld readers before fixed readers are installed.