Skip to main content
PrecisionDCOS — PrecisionX CriticalPrecisionDCOS home

Technical search

Jump to any product, solution or page

PrecisionDCMS componentDCMS-FIELD

PrecisionDCMS Field

Physical acquisition & bounded local operation

Industrial x86 services plus a PFC300-class field controller, modular I/O, protected power and optional IO/GMS interfaces. Field may operate as a complete local product, a connected Edge for NX-Cloud or a bounded acquisition package for local NX.

Field is the boundary between physical plant and the operating contract — industrial x86 services with a PFC300-class controller, modular I/O, protected power and optional IO and GMS interfaces. It normalizes raw signal into identified, time-stamped, quality-tagged values and holds bounded local operation during isolation. It can run as a complete local product, a connected Edge for NX-Cloud, or a bounded acquisition package for local NX.

Role in the platform

Acquire at source

Polls and subscribes to controllers, meters, sensors and gateways across the site and stamps values with source time on capture.

Normalize signal

Maps vendor points to the shared point model with stable identifiers, engineering units and canonical quality states.

Hold the edge

Buffers, evaluates local rules and preserves the local picture when the path to the core is degraded or severed.

Capabilities

Protocol acquisition

Native drivers for BACnet/IP, Modbus TCP/RTU, SNMP, OPC UA, MQTT and IPMI/Redfish with per-device polling and subscription profiles.

Source timestamping

Captures source time and receipt time independently so downstream systems can reason about latency and staleness.

Quality tagging

Every value carries good / uncertain / bad / stale states derived from device response, range checks and freshness windows.

Store-and-forward

Local durable buffer replays gap-free history to the core after a disruption, preserving order and quality.

Edge rules

Deterministic local rules raise alarms, debounce noise and drive safe local responses without waiting for the core.

Secure transport

Mutually authenticated, encrypted outbound sessions to NX with no inbound management plane exposed to plant networks.

Local autonomy

How this component upholds the shared operating contract.

Operating contract

Field is the boundary between physical plant and the operating contract — industrial x86 services with a PFC300-class controller, modular I/O, protected power and optional IO and GMS interfaces. It normalizes raw signal into identified, time-stamped, quality-tagged values and holds bounded local operation during isolation. It can run as a complete local product, a connected Edge for NX-Cloud, or a bounded acquisition package for local NX. Identity, time, quality, authority and evidence travel with every value this component handles, so the behavior stays predictable across the estate.

Acquire at source

Polls and subscribes to controllers, meters, sensors and gateways across the site and stamps values with source time on capture.

Normalize signal

Maps vendor points to the shared point model with stable identifiers, engineering units and canonical quality states.

Hold the edge

Buffers, evaluates local rules and preserves the local picture when the path to the core is degraded or severed.

Runtime characteristics

Deployment
Hardened appliance, VM or container at the site or zone
Protocols
BACnet, Modbus, SNMP, OPC UA, MQTT, IPMI/Redfish
Timestamping
Source + receipt time, sub-second where the source allows
Buffering
Durable local store with gap-free forward on reconnect
Autonomy
Local rule evaluation and alarming during core isolation
Transport
Outbound mTLS to NX; no inbound plant-side management
Indicative runtime characteristics; exact profiles are set per site during engineering.

Scope & boundaries

What this component is — and deliberately is not — responsible for.

  • Field acquires, normalizes and holds bounded local operation; the authoritative monitoring record lives in local NX or NX-Cloud depending on the deployment model.
  • Command authority is declared separately from read authority; Field enforces the authority matrix issued by the platform.
  • Field does not replace safety instrumented systems, vendor safety interlocks, or the autonomous GMS life-safety package.

Technical FAQs

Frequently asked questions

Explore the family

Related products

See where this fits in your reference architecture

We map PrecisionDCMS components to your sites, existing systems and assurance obligations.