FFO/Facility Plane
How FFO/Facility models the operator datacenter and DCIM twin — distinct from per-tenant FFO/Platform IT twins, fed by OpenData HyperSync and Frontier Floor.
FFO/Facility Plane
The Federal Frontier Ontology is one ontology family with many TypeDB instances. Operators run a dedicated FFO/Facility instance for the physical estate (datacenter / DCIM twin). Each tenant runs its own FFO/Platform instance for IT. Instances join only through boundary bridges — not one shared mega-graph.
Naming (locked)
| Written | Spoken | Meaning |
|---|---|---|
| FFO/Facility | Facility FFO | Operator datacenter / DCIM twin |
| FFO/Platform | Platform FFO | Per-tenant Federal Frontier Platform IT twin |
| FFO/Platform:<tenant> | Tenant X’s Platform FFO | A specific tenant instance |
| FFO/Applications | Applications FFO | Enterprise application twin (e.g. Oracle EBS) |
Prefer Platform over “Infrastructure” for the IT plane. Prefer Applications for ERP/app twins — do not fold them into Platform.
Why a Facility plane?
Existing FFO docs (compute, Ceph, findings, identity) describe the Platform twin — clusters, nodes, workloads, and related IT entities. Federal and colo operators also need a first-class twin for site → room → rack → asset and DCIM-managed gear:
- Agents and field apps need live facility context (placement, power, cooling adjacency, commissioning state).
- Modius OpenData remains the DCIM System of Record (SoR) for inventory already managed in DCIM.
- FFO/Facility is the agent- and app-facing graph — not a second CMDB and not a replacement DCIM product.
Systems that feed Facility FFO
| System | Role |
|---|---|
| Modius OpenData | DCIM SoR for facility inventory, hierarchy, and many telemetry hooks |
| OpenData HyperSync Scout | Scheduled projector: OpenData → FFO/Facility (bulk reconcile / drift correction) |
| Frontier Floor | iPad field commissioning client — create/place/annotate into FFO/Facility; may propose SoR updates |
| FFO/Platform instances | Per-tenant IT twins — consume facility placement only via boundary bridges |
See Facility Ownership & Data Flow for the ownership matrix and MVP phasing.
What Facility FFO is not
- Not Matter / Thread. DCIM and Floor talk SNMP, Modbus, BACnet, Redfish, and vendor APIs. Frontier Home / Matter HomeAccount is a separate product.
- Not a second DCIM. Frontier Floor complements OpenData; it does not replace OpenData.
- Not the SoR for OpenData-managed inventory. HyperSync projects SoR truth into the twin; Floor fills gaps ahead of or beside OpenData until SoR catches up.
- Not a place to write tenant IT graphs. Clusters, nodes, and workloads stay in FFO/Platform.
Relationship to the Platform schema
The published Schema Reference documents the Platform-oriented modules (compute, storage, security, identity, …). Facility adds the physical hierarchy and DCIM asset model in the Facility instance. Exact TypeQL entity names land with the facility schema work; treat this page as the plane contract, not the full schema dump.