Facility Ownership & Data Flow

Ownership matrix and data flow for OpenData, HyperSync, Frontier Floor, and FFO/Facility — including MVP phasing and conflict rules.

Facility Ownership & Data Flow

This page is the operational contract for who writes what into FFO/Facility, and how that relates to Modius OpenData (DCIM SoR).

Ownership matrix

Concern OpenData (SoR) HyperSync Frontier Floor FFO/Facility
DCIM-managed inventory already in OpenData Authoritative Projects / reconciles into twin Reads / annotates; does not silently overwrite SoR truth Live twin copy + provenance
New aisle discoveries (not yet in OpenData) Catch-up target May later ingest if SoR gains them Creates in twin Holds field-created entities until SoR exists
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

Modius OpenData (DCIM SoR)
        │
        │  HyperSync Scout (cron / event)
        ▼
   FFO/Facility (TypeDB)  ◄──── Frontier Floor (iPad field client)
        │
        │  boundary bridges
        ▼
   FFO/Platform:<tenant> (IT twins)

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

Design principles

  1. SoR stays SoR. OpenData remains authoritative for DCIM-managed objects.
  2. Twin is for agents and field speed. Operators and agents query FFO/Facility.
  3. Complement, don’t race. HyperSync prevents long-term drift from OpenData. Floor fills gaps ahead of or beside OpenData.
  4. Provenance on every write. Carry source, external / OpenData ids when known, and timestamps.
  5. Boundary isolation. Links to tenant compute use opaque facility ids / projections — no cross-tenant IT in the facility graph.

MVP phasing

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

Conflict policy (summary)

  • If OpenData and Floor disagree on an OpenData-managed object, HyperSync / 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 merge Facility and Platform graphs; use boundary bridges only.