Facilities and the Location Model

What a facility is

A facility is one physical site: a hospital, a plant, a campus building, a distribution centre. It is the top of the spatial hierarchy. Assets belong to a facility; work orders, PM schedules, and maintenance requests all carry one; and reporting, risk, and capital planning roll up by facility. With a single facility Rivolq still works, but the model matters as soon as you have two, because every count you read afterwards is scoped by it.

The four things under a facility

• Location nodes are the tree inside the site: buildings, floors, rooms, and areas. This is the structure the rest of the product trusts.
• Floor plans are images attached to a location node. A plan is not its own hierarchy; it is a picture bound to a floor or building that already exists in the tree.
• Asset pins are coordinates stored on the asset, saying where on that plan the equipment sits.
• Zones are optional 3D bounding boxes used by the digital twin and layout surfaces. They are separate from the location tree and most workspaces never need them.

The rule that keeps this coherent

The location tree is the source of truth for where an asset lives. A floor plan helps a person see that place; it never becomes a second, competing answer. Pinning an asset does not change its location, and deleting a parsed room shape does not move any pin. If the plan disagrees with the tree, every report, filter, and rollup uses the tree. Fix the location first, then fix the picture.

How assets attach

Every asset has a facility and a location, and the location must belong to that facility. Each facility owns one system node named Unassigned, created the first time something needs it. Imports and API calls that supply no location fall back to it, so an asset never ends up with no location at all. A large Unassigned node is not corruption; it is a work queue. See Unlocated assets and location cleanup. Admins can enable the Enforce Asset Location (Manual) setting so manual creation rejects a blank location instead of defaulting.

What the plan tier changes

Facilities, the location tree, and the Unassigned node exist on every plan. Floor plans, asset pins, site maps, and room parsing need Professional or above. On Core the facility and its tree work normally, there is just no plan viewer.

Where to go next

Build the tree with Location hierarchy and naming, then add a plan with Uploading and replacing floor plans.