Industrial Edition
PrecisionDCMS Industrial Edition Overview
The same accountable operating contract as core PrecisionDCMS, engineered for OT-first environments — substations, water and wastewater, energy and process plants — where protection is local and segmentation is not optional.
- Access
- Open access
- Resource type
- Product and architecture overview
- Primary audience
- Owners, controls and OT engineers, plant operators, integrators and owner’s engineering teams
- Product scope
- PrecisionDCMS Industrial Edition, Field Edition, IO and GMS
Same contract, OT-first engineering
Industrial Edition is a deployment discipline, not a different product.
Industrial Edition runs the same PrecisionDCMS components and the same operating contract as a data-hall deployment. What changes is the engineering: environments are harsher, protection is unambiguously local, and network segmentation follows a zone-and-conduit model rather than a flat management VLAN.
It is intended for switchgear rooms, plant floors, substations, pump stations and process areas where the authoritative systems are relays, PLCs, RTUs and safety controllers — and where the operating system supervises and coordinates without ever becoming the protective device.
One operating contract across a mixed estate
A single engagement can run core PrecisionDCMS in the data hall and Industrial Edition on the plant floor under one authority model, one evidence chain and one governance cadence.
Design from the process outward
The estate is modeled as zones, conduits and assets — not as a rack list.
Asset ownership is explicit
Every monitored asset names its owner, its authoritative controller and whether PrecisionDCOS may read only, coordinate or issue a separately engineered command.
Environment drives hardware
Enclosure rating, mounting, cabling and cooling are engineered for temperature, vibration, dust and any hazardous-area classification the site carries.
Signal quality is first-class
Every point carries quality — GOOD, UNCERTAIN, BAD, STALE, OUT_OF_SERVICE or SIMULATED — so operations never act on values they cannot trust.
Zone-and-conduit, IEC 62443-informed
Segmentation is engineered around real flows, not a template.
OT segmentation is designed around the plant's actual zones and the conduits between them. The reference model is informed by IEC 62443 rather than treated as a certification claim — PrecisionX engineers the segmentation and coordinates any required assessment with the appropriate qualified parties.
- Zones defined by function, criticality and ownership
- Conduits with explicit allowed flows, protocols and direction
- Independent out-of-band and console reachability under fault
- Read-oriented data paths by default; command paths separately engineered and disabled unless authorized
- Evidence capture and change control designed into the segmentation, not bolted on
The eight components in an OT context
How the operating model maps onto Industrial Edition.
Scroll horizontally to see the full table.
| Component | Industrial-context role |
|---|---|
| Field Edition | Acquisition at the plant edge in enclosures rated for the environment |
| IO | Physical termination and signal conditioning to relays, PLCs and RTUs |
| GMS | Autonomous gas sensing, annunciation and shutdown-interface boundaries |
| NX / NX-Cloud | Aggregation, workflow and evidence — local NX authoritative where deployed |
| DCOS Network | Zone-and-conduit segmentation, out-of-band and structured cabling |
| DCOS Secure | Physical security and access as a governed protective domain |
| DCOS Operations | CriticalOps monitoring and coordination within engineered boundaries |
| DCOS Assurance | Control records and evidence for OT-relevant frameworks |
Protection survives loss of the platform
The consequence-limiting function stays local and independent.
Relay trips, gas emergency shutdown, fire release, interlocks and equipment safeties act within their engineered envelope even when the network, NX-Cloud, central identity or the NOC is unavailable. PrecisionDCOS observes, correlates, notifies, dispatches and preserves evidence around these systems — it does not become them.
Monitor broadly. Command narrowly. Keep protection local.
No required protective function is made to depend on the operating system, the WAN or the cloud.
Frequently asked
Questions and answers
- Is Industrial Edition IEC 62443 certified?
- The segmentation and engineering are IEC 62443-informed. PrecisionX engineers to the model and coordinates any formal assessment with the appropriate qualified assessor; the overview does not claim a certification on your behalf.
- Can it run alongside core PrecisionDCMS?
- Yes. A mixed estate runs core and Industrial Edition under one authority model, evidence chain and governance cadence — typically core in the data hall and Industrial Edition on the plant floor or in the switchgear room.
- Does the operating system control protection?
- No. Protective relays, gas shutdown, fire release and equipment safeties remain local and autonomous. The operating system supervises and coordinates within fenced boundaries and never overrides a protective action.
- What do you need to scope an Industrial deployment?
- Environment and hazardous-area classification, the protection systems present, existing controllers and networks, and your acceptance criteria. The Basis of Design Questionnaire captures this in a structured intake.
Related resources
Industrial Edition Basis of Design Questionnaire
Capture the environment, protection and acceptance criteria for a scoped design.
Read resourceHardware and ConfigurationIO and GMS Overview
See the Field interface and independent gas-safety boundaries in detail.
Read resourcePrecisionDCMSPrecisionDCMS Technical Manual
Read the controlled requirements for the components referenced here.
Read resourceScope an OT deployment
Bring your plant, its protection systems and its constraints.
We return a zone-and-conduit design, a hardware and segmentation plan and an acceptance path engineered for your environment.