Controlled location hierarchy
Each level receives a governed code and parent relationship instead of relying on free-text location names.
All modules
Module 01
Spatial backboneProperties and Locations
An estate tree that codes itself.
Sites, buildings, floors, rooms, service areas, drawings, codes, and QR access form the physical hierarchy used by every operating module.
1 treefor every site, building, floor, and room
Plan coverage92%
Buildings / floors12 / 86
Rooms and areas1,240
Open requests by locationLive view
HQ Tower31
Riyadh Campus23
Dammam Warehouse13
Jeddah Branch8
Hierarchy controlsCurrent state
Code cascade12 child locations aligned
goodDeletion guardHistory blocks unsafe delete
reviewDrawing gap7 floors unmapped
reviewRepresentative CAFMPRO interface
Built from the approved module specification as a representative system view. Final production screens may differ.
Operational value
Properties and Locations gives the platform one controlled estate structure, so assets, work, people, contracts, security, and documents inherit the correct physical context.
Drawings stay accountable
Plan coverage and missing drawings remain visible by building and floor, while mapped work keeps the source location.
History protects the structure
Relocation and deletion rules preserve linked operational history rather than silently breaking downstream records.
Operational story
How the module works in practice.
01
Structure
Create the estate, building, floor, and space hierarchy.
02
Code
Apply controlled identifiers and location QR access.
03
Map
Attach drawings and operational objects to place.
04
Connect
Give every module a consistent physical context.
Connected by design
The record keeps moving.
Asset Management Space Management Security Maintenance Contracts and KPI