Model every building, floor, and room you manage — one structured record that everything else pins to.
Most FM operations maintain some version of a space record — a floor plan, a property list, a room schedule in a spreadsheet. The problem is that these records live separately from everything that happens inside the space. A work order references "Tower 7, Floor 12" as free text. A meter reading has no formal address. An asset's location is a note on the asset record, not a link to a shared spatial hierarchy. When a client asks which floor is consuming the most energy, or which building has the most reactive faults this quarter, the answer requires someone to manually cross-reference four different fields from three different systems. Coreziyo Space Hierarchy establishes the spatial backbone of your operation — a structured, shared tree that every other operational record pins to. Buildings contain floors. Floors contain rooms and zones. Every asset, every energy meter, every work order, every permit is placed within this hierarchy at the point it is created. The location is not a free-text note; it is a linked record that can be filtered, reported on, and cross-referenced in real time. At portfolio scale — 1,000+ buildings, thousands of floors, tens of thousands of rooms — the difference between a spatial hierarchy and a location field is the difference between operational intelligence and data that requires manual interpretation every time a question is asked.
Space hierarchy is the foundation that makes every other operational system useful at scale. Without it, location is a text field — a reference that means something to the person who typed it and requires interpretation by everyone else. With it, location is a structured, shared record that every operational event inherits automatically.
Coreziyo’s space hierarchy is not a standalone floor-plan tool. It is the spatial backbone of the entire platform. When a technician closes a work order, the location is recorded. When a meter reading is entered, it belongs to a specific room. When a permit is issued, it is linked to the exact zone where the work will happen. None of this requires manual cross-referencing because the hierarchy was established once and everything else references it.
For GCC operators managing portfolios at scale, this is the prerequisite for operational intelligence — not just data about what happened, but data about where it happened, structured in a way that makes the question “how is building X performing compared to building Y?” answerable without a data project every time it is asked.
What you actually get
Multi-building, multi-floor, multi-room structure
Build a portfolio tree that reflects your real estate as it exists — company, region, building, floor, room, zone. Unlimited depth. Rename any level to match your terminology — tower, block, unit, bay.
Space type and area classification
Tag every space with type (office, plant room, common area, car park, retail unit) and net/gross area in square metres. Area data feeds directly into cost-per-m² and utilisation calculations — no manual entry each time a report is needed.
Asset and meter placement within the hierarchy
Every asset and every energy meter is assigned to a node in the spatial tree. When an asset is moved, its location updates across all linked records — work orders, inspection history, insurance certificates. The spatial record and the operational record are always in sync.
Work orders and permits linked to rooms, not just buildings
A reactive fault is raised on 'Floor 3, Server Room 3B', not just 'Building A'. Technicians navigate to the exact space. Managers can filter backlog by floor or zone without manual tagging after the fact.
Portfolio views and spatial filters
Every report, dashboard, and backlog view is filterable by any node in the spatial tree — building group, individual building, floor, or room type. A regional director sees the whole portfolio. A facilities manager sees their building. A shift supervisor sees their floor.
How it shows up in real operations
A UAE real-estate developer managing a mixed-use portfolio across 12 districts uses Coreziyo Space Hierarchy to structure 1,200+ buildings, 18,000 floors, and 140,000+ rooms in a single spatial tree. Every asset, every meter, and every work order raised across the portfolio is placed within this hierarchy on creation. When institutional investors ask for energy consumption per building type, the report runs in seconds — the spatial and operational records are co-located, not assembled from separate sources. The practical impact is visible at the FM manager level. Before the hierarchy was established, answering "which five floors had the most reactive faults last month?" required a spreadsheet extraction and an hour of manual matching. With Space Hierarchy in place, it is a filtered dashboard view. That time is spent on the next problem, not reconstructing the last one.