Is PrecisionDCOS a single product or a suite?

It is one operating contract expressed across seven planes. Each plane can be adopted independently, but they share identity, time, authority, event lifecycle, dependency and evidence models so they behave as one system rather than integrated silos.

Do we have to replace our existing BMS, DCIM or network?

No. PrecisionDCOS federates suitable existing systems through a managed overlay and replaces only what should be replaced. Authoritative systems and approved customer standards are preserved where they earn their place.

What makes authority different from access?

Read authority and command authority are declared separately. Visibility never implies the right to change a system. Every command path is fenced, logged and attributable, and protective functions remain local.

How is compliance evidence produced?

Evidence is generated continuously from linked operating records rather than reconstructed before an audit. Controls map to real events, work orders, changes and approvals across every plane.

Platform Architecture

One operating contract for critical digital infrastructure

PrecisionDCOS binds monitoring, networking, connectivity, security, operations, data and assurance under a single contract — so every domain shares the same truth about identity, time, authority, events, dependency and evidence.

Request an Architecture Review Configure a Reference Architecture

Planes: 7 integrated
Delivery: Software / Hardware / Managed
Adoption: Overlay, hybrid or full-stack
Portability: Config, data & evidence

Overview

Not a bundle of tools — a shared operating layer

Digital infrastructure is judged on uptime, security and provable control. The systems that deliver those outcomes rarely share identity, time, authority or evidence, and the gaps between them become operational risk. PrecisionDCOS closes those gaps with one contract.

Monitor broadly. Command narrowly. Keep protection local.

The operating contract

Seven guarantees every plane must honor

Whatever a domain measures or controls, it commits to the same seven guarantees. That is what turns integrated tools into an operating system.

Stable identity

Every organization, site, asset, point, event and service carries a stable identifier that survives reconfiguration and vendor change.

Time and quality

Source time, receipt time and canonical quality states travel with every value so that operators trust what they act on.

Authority

Read authority and command authority are declared separately. Visibility never implies the right to change.

Event lifecycle

A shared detect → validate → correlate → coordinate → restore → prove lifecycle links every domain to accountable closure.

Dependency

Assets, services and paths are related so that impact, blast radius and restoration order are explicit.

Evidence

Controls and operating effectiveness are demonstrable from linked records rather than reconstructed before an audit.

Portability

Configuration, data and evidence remain exportable so the customer is never locked out of their own operating history.

Seven planes

Each plane, one accountable owner

Every plane is a product you can adopt on its own — and a citizen of the same contract when adopted together.

DCMS

PrecisionDCMS

Facility, data-center and cluster monitoring and operations — the detailed core of PrecisionDCOS, from field signal to verified evidence.

Network

DCOS Network

Engineered building-management, OT, campus, security and management networks — new build, overlay, managed or mixed-vendor.

Connect

DCOS Connect

Waves, dark fiber, transit, remote hubs, cloud on-ramps and customer interconnects — procured, engineered, accepted and operated.

Secure

DCOS Secure

Perimeter, access control, video, intrusion, visitor management and dispatch — as a protective system and a governed data domain.

Operations

DCOS Operations

24/7 NOC, SOC, service desk, CALS event orchestration, ITSM/CMMS/DCIM and field services under an accountable operating model.

Data Fabric

DCOS Data Fabric

Normalized, contextualized operational data with governed APIs, streams and exports for analytics, AI/ML and digital twins.

Assurance

DCOS Assurance

ISO/IEC 27001, SOC 2 Type II, PCI DSS extensions and a unified control fabric with continuous evidence operations.

DCOS Cloud

CriticalOps Cloud

Identity, private access, monitoring, dashboards, CALS, evidence, APIs, backup and multi-site operations as a hosted plane.

Reference architecture

From field signal to verified evidence

Signals rise from physical acquisition through edge continuity and site operations into hosted planes and governed data — while authority and protection stay where they belong.

Field & acquisitionPhysical / OT

BMS / EPMS / sensors

hardwired I/O

PFC & edge runtime

continuity

Protective systems

local, fenced

Field standard nodes

N+1

Network & connectivityTransport

Campus & OT fabric

Out-of-band mgmt

Carrier & transport

Cloud on-ramps

Operating planeNX / NX-Cloud

Monitoring & history

CALS event lifecycle

ITSM / CMMS / DCIM

Dashboards & UI

Data & assuranceGoverned

Normalized data fabric

Governed APIs & streams

Continuous evidence

Customer access

Reference flow. Actual topology, redundancy and residency are engineered per site and configuration.

Protection stays local

Monitoring and coordination can be broad and hosted, but protective functions — fire, gas, electrical protection and life-safety interlocks — remain local and independent of the operating plane.

Operated outcomes

Eight measurable states

PrecisionDCOS exists to move a site into these states and hold it there under change.

Operated outcome states and what each guarantees.
State	What it guarantees
Observable	Every in-scope system, path and service has defined coverage, data quality, source health, stale behavior and ownership.
Operable	Operators have controlled interfaces, authority matrices, procedures, escalation paths and field-response models.
Connected	Campus, OT, OOB, transport, Internet, cloud and customer interconnections are engineered, accepted, monitored and managed.
Secure	Physical, cyber and OT boundaries are designed together with strong identity, least privilege and converged incident context.
Maintainable	Assets, PMs, work orders, vendors, spares, warranties, inspections, changes and evidence are governed through the lifecycle.
Customer-ready	Customers receive controlled access, health, incidents, maintenance, reports, data and assurance without ambiguous authority.
Auditable	Controls and operating effectiveness are demonstrated from linked records rather than reconstructed manually.
Data-enabled	External analytics, AI/ML, reporting and digital-twin systems consume normalized operational data through governed endpoints.

Operated outcome states and what each guarantees.

Authority model

Monitor broadly. Command narrowly.

The authority model is the backbone of the platform. It separates what a role can see from what a role can change, everywhere.

Read authority

Broad visibility across planes, sites and customers, scoped by tenancy and role — without any implied right to act.

Command authority

Explicitly granted, fenced and attributable. Singular and destructive actions require confirmation and leave an evidentiary trail.

Local protection

Life-safety and protective functions are never dependent on the operating plane, the network or the cloud to remain effective.

Separate declaration of read and command authority per role
Tenancy-scoped visibility for owners, operators and customers
Fenced singular actions with confirmation and logging
Every command attributable to an identity and a reason

Technical FAQs

Frequently asked questions

See how the operating contract maps to your sites

Bring your current systems, standards and portfolio. We will show where PrecisionDCOS federates, where it replaces, and what it makes provable.

Request an Architecture Review Review Configuration Options