Skip to main content
PrecisionDCOSPrecisionX CriticalPrecisionDCOS home

Technical search

Jump to any product, solution or page

Commercial

Configurations

Composition, not a license tier ladder.

PrecisionDCOS is scoped to your estate: a deployment model, a module set and an operating-authority tier. Start where the risk is and expand under one operating contract.

Request an Architecture ReviewConfigure a Reference Architecture

Build a configuration

Choose a commercial configuration, then set the operating-authority tier that matches how much your team wants to run.

Configuration

DCOS Foundation

Includes: PrecisionDCMS plus Network, CriticalOps Cloud and NOC

Best fit: Pilot or small production site

  • Pilot / small production
  • Core network + hosted plane
  • 24/7 NOC coverage
Operating authority

Shared workflows with defined customer approvals.

  • Shared workflows
  • PrecisionX coordinates incidents and vendors
  • Customer retains defined approvals
  • Joint reporting and improvement cadence
Scope this configuration

Deployment models

Where the runtime lives — from a single monitored site to a federated portfolio with a hosted operating plane.

ACloud: None

Field Standalone

Complete local monitoring runtime with no cloud dependency.

  • Field Lite or Standard
  • Optional IO and GMS
  • Complete local monitoring runtime

Best for: Small or moderate facility / packaged-equipment scope

BCloud: Authoritative

Field + NX-CloudPreferred

Preferred production pattern when traditional I/O exists and managed hosted scale is desired.

  • Field Connected Edge with PFC and physical acquisition
  • Edge Continuity runtime
  • Zabbix proxy and Site Connector

Best for: Traditional I/O present, managed hosted scale desired

CCloud: None

Field + NX Local

Full local facility and cluster monitoring with complete data residency.

  • Field acquisition package
  • Local NX Lite or Standard
  • Complete local facility and cluster monitoring

Best for: Sovereign, air-gapped or fully local requirements

DCloud: None

NX Local Only

Direct Ethernet-native acquisition with no base physical I/O.

  • NX Lite or Standard
  • Direct Ethernet-native acquisition
  • No base physical I/O

Best for: Ethernet-native sources; no hardwired I/O required

ECloud: Full

NX-Cloud Only

Hosted NX-Cloud with software proxies and collectors — no site appliance.

  • Hosted NX-Cloud
  • Private or outbound connectivity
  • Software proxies and collectors

Best for: Independently monitored facility systems; hosted operations

Operating authority is explicit

Every engagement names who monitors, who decides and who acts. Authority is delegated on purpose — never assumed.

Authority boundaries are engineered

Safety-critical functions — protection, gas, shutdown and life-safety — remain autonomous and local in every configuration. PrecisionDCOS observes and coordinates within engineered boundaries; it does not override protective controls.

How scoping works

A short, evidence-based path from estate to operating contract.

  1. 1Inventory the estate, standards, residency constraints and existing authoritative systems.
  2. 2Select a deployment model and the module set that covers the actual risk.
  3. 3Agree the operating-authority tier and the exclusions that stay with you or an OEM.
  4. 4Commit an operating contract with defined response, change cadence and evidence.

Scope your configuration

Bring your estate and constraints. We return a deployment model, module set, authority tier and an operating contract.

Request an Architecture ReviewSee Managed Services