In 2026, most operations carry the same physical space in four or five different systems with four or five different names. The maintenance crew calls it "Pump Room B." The inventory system labels it "STG-04-WST." Facilities calls it "Building 2 Mechanical." The work order app shows it as "Z3-Plant Floor." When the safety inspector asks for the location of the incident, nobody is sure whether all four references point to the same room or to four different rooms. The audit drags. The corrective action plan takes a week to assemble.

The cost compounds anywhere physical space crosses departmental lines. Inventory cannot tell you where an asset is housed because asset management uses a different naming scheme. A work order arrives at the wrong building because the requester used a label the technician's app does not recognize. Compliance audits demand a unified site map that the operations team has to construct manually from four conflicting source files. Every new facility makes the problem worse.

Locations and Zones replaces that mess with one space model. Each physical area gets defined once, with the attributes the business actually uses: site, building, zone, aisle, bin, room, production area. The model is hierarchical, so a bin lives inside an aisle, which lives inside a zone, which lives inside a building, which lives inside a site. Every other app (inventory, assets, work orders, checklists) reads from the same location records. When somebody asks "where is X," every system gives the same answer.

Each location carries a type that defines what it represents: site, building, floor, zone, aisle, bin, room, production area, parking lot, or custom category for industry-specific needs. The hierarchy is configurable rather than hard-coded. A distribution center models down to the bin level for inventory accuracy. Manufacturing campuses model down to the production cell. A multi-tenant office complex tracks down to the floor or suite for IT asset tracking. Each business defines its own depth without forcing the model into shapes that do not fit.

Custom attributes attach to any location type. A bin carries size plus capacity figures. Production areas carry hazard class plus required PPE. A server room carries cooling capacity plus access restrictions. A loading dock carries door dimensions plus the approved carrier list. The attributes are user-defined so the data captured at each location matches the actual operational reality of that space, not a vendor's idea of what should be tracked.

Default location assignment is what makes the model useful day to day in the field. A monthly preventive maintenance checklist defaults to the production cells it covers. Equipment records default to their installed locations. A vendor receipt defaults to the receiving zone. A work order template defaults to where the work usually happens. The defaults populate automatically when staff create new records, plus they can be overridden when the work actually happens elsewhere. Filter any data view (tasks, assets, inventory, history) by zone, area, or floorplan to see exactly what is happening in a specific space.