Commercial

Configurations

Composition, not a license tier ladder.

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

Request an Architecture Review Configure a Reference Architecture

Build a configuration

Choose a commercial configuration, set the operating-authority tier, pick a hardware form and edition. The result is an indicative, non-binding reference architecture — a starting point, not a quote.

Step 1 · Commercial 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

Step 2 · Operating authority

Shared workflows with defined customer approvals.

Shared workflows
PrecisionX coordinates incidents and vendors
Customer retains defined approvals
Joint reporting and improvement cadence

Step 3 · Hardware form

Step 4 · Edition

Reference architecture

Indicative starting point — not a quote or commitment

Non-binding

Configuration: DCOS Foundation — PrecisionDCMS plus Network, CriticalOps Cloud and NOC
Operating authority: Co-Managed — Shared workflows with defined customer approvals.
Hardware form: 1U–2U enterprise NX node(s) in a controlled room or rack.
Edition: Data centers, campuses, colocation and enterprise critical facilities.
Reference NX node: NX Standard Capacity (S32) — 2U dual-socket enterprise server

Assumptions

Final component set, node count and sizing follow discovery, active-item counts, event rates, history, users and order-specific benchmark results.
Reference hardware shown is an indicative baseline; approved customer-standard or existing platforms may be substituted where they meet the required architecture.
Safety-critical protection, shutdown and life-safety functions remain autonomous and local in every configuration.
Operating authority, exclusions and OEM/customer-retained scope are confirmed during the Architecture Review.

Request an Architecture Review

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.

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

Frequently asked questions

How configurations, editions and the reference architecture work.

Is the configurator a quote?: No. It produces an indicative, non-binding reference architecture — a starting point for discussion. Final component set, node count, sizing, authority and commercial terms are confirmed during an Architecture Review.
Are these fixed license tiers?: No. PrecisionDCOS is composed from eight governed components against your estate, not sold as a fixed tier ladder. The four commercial configurations are common compositions you can start from and expand under one operating contract.
Can I change the hardware form later?: Yes. The hardware form (NX rackmount, Field enclosure, rack-adjacent or mixed) is an engineering choice that can evolve as sites are added. Approved customer-standard or existing platforms may be substituted where they meet the required architecture.
What does the Industrial Edition change?: The Industrial Edition applies zone-and-conduit segmentation and IEC 62443-informed engineering for substations, water/wastewater, energy and process plants. It maps the same eight components onto an OT-first control and segmentation model.

Scope your configuration

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

Request an Architecture Review See Managed Services