Facility Ownership & Data Flow

Ownership matrix and data flow for DCIM SoR (via HyperSync DCIM adapters), Frontier Floor, and FFO/Facility — including MVP phasing and conflict rules.

This page is the operational contract for who writes what into FFO/Facility, and how that relates to the site’s DCIM System of Record reached through HyperSync DCIM adapters. OpenData HyperSync is the Modius adapter #1 job only — not the product capability name.

Ownership matrix

Concern DCIM SoR (via adapter) HyperSync DCIM Frontier Floor FFO/Facility
DCIM-managed inventory already in SoR Authoritative Projects / reconciles into twin Reads / annotates; does not silently overwrite SoR truth Live twin copy + provenance
New aisle discoveries (not yet in SoR) Catch-up target May later ingest if SoR gains them Creates in twin Holds field-created entities until SoR exists / linked
Placement (site / room / rack / U) Often authoritative when modeled Syncs hierarchy Creates / corrects in field Queryable hierarchy for agents & apps
Telemetry hooks Often SoR Syncs references May attach field notes / photos Twin attributes + links
Tenant IT (clusters, VMs, pods) Out of scope Out of scope Does not write Bridge ids only — IT lives in FFO/Platform

Data flow

Same facade story as FFO/Facility Plane — DCIM SoRs enter through HyperSync DCIM adapters; Floor writes/annotates the Facility twin (not the SoR); Platform links only via boundary bridges (placement only; no IT graph merge).

flowchart TB subgraph Adapters["DCIM SoR adapters"] direction LR OD["Modius OpenData
adapter #1"] NL["Nlyte
future"] SB["Sunbird
future"] OTH["Other DCIM…
future"] end HS["HyperSync DCIM Scout
facade / projector"] FAC["FFO/Facility TypeDB
vendor-neutral twin"] Floor["Frontier Floor iPad"] Plat["FFO/Platform:<tenant>
placement only"] OD --> HS NL --> HS SB --> HS OTH -.-> HS HS -->|project / reconcile| FAC Floor -->|writes / annotates Facility
not SoR| FAC FAC -->|boundary bridges| Plat Floor -.->|optional P1/P2 proposals| OD style HS fill:#2b6cb0,stroke:#4299e1,color:#fff style FAC fill:#2c7a7b,stroke:#38b2ac,color:#e2e8f0 style Floor fill:#553c9a,stroke:#805ad5,color:#e2e8f0 style OD fill:#2d3748,stroke:#4299e1,color:#e2e8f0 style NL fill:#1a202c,stroke:#718096,color:#e2e8f0 style SB fill:#1a202c,stroke:#718096,color:#e2e8f0 style OTH fill:#1a202c,stroke:#718096,color:#e2e8f0 style Plat fill:#2d3748,stroke:#4299e1,color:#e2e8f0

Caption: HyperSync DCIM projects any DCIM SoR into FFO/Facility; OpenData HyperSync is the Modius job name only.

Optional later path: SoR proposals / write-back from Floor or twin workflows into the DCIM SoR via the same adapter (P1/P2 below). Until that ships, Floor must not pretend to update the SoR silently.

Design principles

  1. SoR stays SoR. The DCIM product remains authoritative for DCIM-managed objects; HyperSync DCIM does not replace it.
  2. Twin is for agents and field speed. Operators and agents query FFO/Facility.
  3. Complement, don’t race. HyperSync DCIM prevents long-term drift from the SoR. Floor fills gaps ahead of or beside the SoR.
  4. Provenance on every write. Required: external_id (@key), source, source_updated_at, commissioning_status (+ name). opendata_id is a Modius legacy alias only (may mirror external_id); new adapters must not require it.
  5. Boundary isolation. Links to tenant compute use opaque facility ids / projections — no cross-tenant IT in the facility graph.
  6. No vendor-specific Facility types. Adapters normalize to Facility-shaped DTOs; no schema fork per DCIM.

MVP phasing

Phase Focus
P0 — Twin-first Facility schema + HyperSync DCIM (OpenData HyperSync job) into FFO/Facility + Floor create/verify against the twin
P1 — SoR proposals Floor / twin workflows can propose SoR creates/updates via the adapter without assuming write-back success
P2 — Optional write-back Controlled SoR write-back where the operator enables it

Conflict policy (summary)

  • If the DCIM SoR and Floor disagree on a SoR-managed object, HyperSync DCIM / SoR wins for SoR-owned attributes after reconcile.
  • Field-only attributes (photos, aisle notes, commissioning checklist state) remain Floor-authored unless explicitly mapped into SoR.
  • Never delete Floor-only entities (source=frontier_floor without SoR link) unless tombstoned by policy.
  • Never merge Facility and Platform graphs; use boundary bridges only.