Location Hierarchy and Naming

The four location types

Each node carries a type: building, floor, room, or area. Type is not decoration. Only floor and building nodes can host a floor plan, so a tree made entirely of areas gives you nowhere to upload one.

Naming a path

A path is written with a space, a slash, and a space between segments, as in Building A / Floor 2 / Pump room 204. On import Rivolq also accepts the greater-than sign, the vertical bar, the backslash, and the arrow characters that BMS and CAFM exports emit. Hyphens and commas are deliberately not separators, so AHU-1 and Room 204, North Wing stay single names. A node name is up to 150 characters and a full path up to 500.

How types are guessed on import

When a path arrives without explicit types, Rivolq guesses from the segment text, most specific pattern first:

• Starts with Bldg or Building becomes building.
• Floor 2, Fl. 2, Level 3, Lvl 3, or F2 becomes floor, as do Basement, Mezzanine, and Penthouse.
• Contains room, suite, office, lab, bay, ward, or unit becomes room.

If nothing matches, position decides: the first segment becomes a building, the second a floor, and anything deeper an area. Naming a floor "Floor 2" rather than "2" is the difference between a node that can carry a plan and one that cannot.

Matching is on the full path

An imported path matches an existing node only when the whole path matches. Building A / Floor 2 / 204 will not attach to a node called 204 in Building B. This stops identically numbered rooms in two buildings from merging, but a typo in an upper segment creates a new branch, so review the tree after a large import.

Editing and deleting by hand

Location editing is an admin action. Open the facility, use the Locations tab, and add nodes under the right parent. You can rename a node, change its type, and reorder siblings. Renaming rewrites the full path of everything beneath it, so imports that used the old string start creating new nodes. Change names before a bulk import, not after.

Deleting a node is a soft delete and never orphans equipment. Every asset in the subtree moves to the nearest surviving ancestor, or to the facility's Unassigned node; each move is written to the asset's location history, and floor-plan pins on those assets are cleared. Rivolq refuses the delete when the subtree holds more than 1,000 assets, returning a subtree_too_large conflict; delete smaller child locations first. Next: Uploading and replacing floor plans.