The monitoring and management core
PrecisionDCMS is the detailed core of PrecisionDCOS — from field signal to verified evidence. It spans physical acquisition, local and hosted runtimes, point engineering, prime-power coordination and a deep connector library.
- Modules
- Field · NX · NX-Cloud · IO · GMS
- Deployment
- 5 models (A–E)
- Availability
- Lite · Standard
- Connectors
- 40+ protocols
Overview
Signal to verified evidence
PrecisionDCMS acquires physical and Ethernet-native signals, gives every point stable identity, time and quality, and carries it through history, operations and evidence — locally, hosted, or both.
Modules
Six modules, one core
Adopt the modules your site needs. They share the same identity, quality and authority models.
Field
AcquisitionPhysical acquisition, PFC and edge continuity — the deterministic base of the stack.
ExploreNX
Local runtimeLocal facility and cluster monitoring, history, users and operations.
ExploreNX-Cloud
Hosted runtimeHosted authoritative monitoring, workflow and multi-site scale.
ExploreIO
Points & I/OSignal engineering, point modeling, quality and command fencing.
ExploreGMS
Prime powerGenerator and prime-power monitoring and coordination.
ExploreConnectors
Integration40+ OT, BMS, EPMS and IT protocol connectors with normalized modeling.
ExploreSignal path
How a value becomes evidence
Every value travels the same governed path so operators trust what they act on.
Acquire
Field / connectors
Identify
stable IDs
Qualify
time + quality
Operate
history, alerts
Prove
linked evidence
Deployment models
Five patterns from standalone to hosted
The same core deploys five ways. Model B (Field + NX-Cloud) is the preferred production pattern when traditional I/O exists and managed hosted scale is desired.
Field Standalone
Cloud dependencyNoneComplete local monitoring runtime with no cloud dependency.
- Field Lite or Standard
- Optional IO and GMS
- Complete local monitoring runtime
- Local UI, history, users, alerts and permitted commands
- No cloud dependency
Best for: Small or moderate facility / packaged-equipment scope
Field + NX-Cloud
PreferredCloud dependencyAuthoritativePreferred 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
- Local queue and fallback view
- NX-Cloud authoritative monitoring and workflow
- Cluster collectors and bounded local continuity during WAN loss
Best for: Traditional I/O present, managed hosted scale desired
Field + NX Local
Cloud dependencyNoneFull local facility and cluster monitoring with complete data residency.
- Field acquisition package
- Local NX Lite or Standard
- Complete local facility and cluster monitoring
- Full local data and operations residency
Best for: Sovereign, air-gapped or fully local requirements
NX Local Only
Cloud dependencyNoneDirect Ethernet-native acquisition with no base physical I/O.
- NX Lite or Standard
- Direct Ethernet-native acquisition
- No base physical I/O
- Complete local monitoring, history and operations
- Add a bounded Field package only when physical or deterministic requirements exist
Best for: Ethernet-native sources; no hardwired I/O required
NX-Cloud Only
Cloud dependencyFullHosted NX-Cloud with software proxies and collectors — no site appliance.
- Hosted NX-Cloud
- Private or outbound connectivity
- Software proxies and collectors
- No PrecisionDCMS site appliance
- Allowed only where facility systems are independently monitored
- Not a substitute for required local BMS, fire, gas or protective systems
Best for: Independently monitored facility systems; hosted operations
Availability editions
Lite and Standard, defined precisely
Availability language is deliberately unambiguous, because in critical infrastructure the difference decides whether a single failure interrupts operations.
| Edition | Nodes | Definition |
|---|---|---|
| Lite | One Field Core or one NX Node | A complete deployment with an accepted single-node interruption and a defined backup, spare and recovery plan. |
| Standard | Two independently powered and networked matching nodes | Standard means two nodes — not two processors or two power supplies inside one server. Independent power and network failure domains, leader/follower or approved active/active collection, no shared-storage dependency in the base local architecture, tested failover, fenced singular actions. Point-level redundancy remains separately engineered. |
What Standard is not
Redundancy is engineered, not assumed
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.
CriticalOps Cloud
Identity, private access, monitoring, dashboards, CALS, evidence, APIs, backup and multi-site operations as a hosted plane.
Configure PrecisionDCMS for your facility
Bring your I/O inventory, protocols and availability targets. We will map them to a Field, NX and NX-Cloud configuration.