PrecisionDCMS NX
Site operating node
The on-site node that consolidates Field runtimes into a coherent site picture — historian, alarm engine, dependency model and operator interfaces running within the customer boundary.
Role in the platform
Consolidate the site
Aggregates all Field runtimes into one coherent, identified model of the site with a single authoritative historian.
Run the lifecycle
Detects, validates, correlates and coordinates events across domains and drives them toward accountable closure.
Serve operators
Presents dashboards, alarm consoles, dependency views and controlled actions within the customer trust boundary.
Capabilities
Site historian
High-resolution, quality-aware time-series store with retention tiers and gap-free ingestion from Field.
Correlation engine
Relates alarms, state changes and dependencies to suppress noise and surface probable cause and blast radius.
Dependency model
Assets, services and paths are related so impact and restoration order are explicit during an incident.
Operator interfaces
Role-scoped dashboards, alarm consoles and controlled actions bound to the platform authority matrix.
Local resilience
Continues site operations and evidence capture if the connection to NX-Cloud or the hosted plane is lost.
Governed integration
Publishes to the data fabric and federates approved BMS, DCIM, CMMS and ITSM systems without rip-and-replace.
Event lifecycle
How this component upholds the shared operating contract.
Operating contract
NX is where a site becomes operable. It aggregates every Field runtime, maintains the authoritative site historian and dependency model, runs correlation and the event lifecycle, and presents governed operator interfaces — all inside the customer trust boundary. Identity, time, quality, authority and evidence travel with every value this component handles, so the behavior stays predictable across the estate.
Consolidate the site
Aggregates all Field runtimes into one coherent, identified model of the site with a single authoritative historian.
Run the lifecycle
Detects, validates, correlates and coordinates events across domains and drives them toward accountable closure.
Serve operators
Presents dashboards, alarm consoles, dependency views and controlled actions within the customer trust boundary.
Runtime characteristics
- Deployment
- Redundant VMs or appliances within the customer boundary
- Historian
- Quality-aware time-series with tiered retention
- Availability
- Active/standby or clustered per availability edition
- Upstream
- mTLS ingestion from Field with gap-free replay
- Interfaces
- Web operator consoles, governed APIs, streams
- Isolation
- Full site operation during core/cloud disconnection
Scope & boundaries
What this component is — and deliberately is not — responsible for.
- NX is the authoritative site operating node; multi-site federation and hosted services are provided by NX-Cloud and CriticalOps Cloud.
- NX enforces, but does not unilaterally define, the authority matrix governing read and command rights.
- NX federates approved external systems; it does not silently override their systems of record.
Technical FAQs
Frequently asked questions
Explore the family
Related products
DCOS Network
Engineered building-management, OT, campus, security and management networks — new build, overlay, managed or mixed-vendor.
DCOS Operations
24/7 NOC, SOC, service desk, CALS event orchestration, ITSM/CMMS/DCIM and field services under an accountable operating model.
DCOS Data Fabric
Normalized, contextualized operational data with governed APIs, streams and exports for analytics, AI/ML and digital twins.
DCOS Assurance
ISO/IEC 27001, SOC 2 Type II, PCI DSS extensions and a unified control fabric with continuous evidence operations.
See where this fits in your reference architecture
We map PrecisionDCMS components to your sites, existing systems and assurance obligations.