Skip to main content
PrecisionDCOSPrecisionX CriticalPrecisionDCOS home

Technical search

Jump to any product, solution or page

PrecisionDCMS · Connectors

40+ protocols, one normalized model

Connectors bridge OT, BMS, EPMS, IT and telemetry sources into a single governed model — with read-only defaults, scoped credentials and stable identity for every point.

Protocols
40+ supported
Default
Read-only
Security
TLS · scoped creds
Modeling
Normalized identity

Overview

Bridge every source into one truth

Critical sites run dozens of vendor systems. Connectors normalize them so a Modbus register and a Redfish sensor become first-class points with the same identity, time and quality guarantees.

Connector library

Explore supported protocols

Filter by category to see transport and integration notes.

Supported connectors. Read-only by default; command paths are separately commissioned.
ProtocolCategoryTransportNotes
SNMP v1/v2c/v3IT / ServerUDPSNMPv3 authPriv preferred; read-only by default.
Modbus TCPIndustrial / OTTCPScoped register maps; read-only unless commissioned.
Modbus RTUIndustrial / OTRS-485Serial acquisition via Field-family hardware.
BACnet/IPIndustrial / OTUDPBMS and mechanical systems integration.
OPC UAIndustrial / OTTCPCertificate-secured sessions; browse and subscribe.
RedfishIT / ServerHTTPSServer and BMC health; scoped credentials.
HTTP/RESTIT / ServerHTTPSAPI polling with explicit endpoint allowlists.
MQTT / SparkplugTelemetryTCP/TLSStructured device telemetry with birth/death context.
SyslogLoggingUDP/TCP/TLSStructured intake with tenant and source context.
ICMP / TCP service checksTelemetryIPReachability and synthetic service verification.
Prometheus-compatible exportersTelemetryHTTPSScrape with label and cardinality controls.
OpenTelemetryTelemetrygRPC/HTTPStructured telemetry and traces.
Scheduler / orchestrator APIsClusterHTTPSSlurm, Kubernetes and shared-service state.
OEM-specific profilesIT / ServerVariesCurated, tested adapters for vendor equipment.
Supported connectors. Read-only by default; command paths are separately commissioned.

Security defaults

Secure by default, everywhere

Integration inherits the platform's security posture rather than bolting it on afterward.

  • SNMPv3 authPriv preferred
  • Read-only by default
  • TLS and certificate validation
  • Scoped credentials
  • Explicit namespace and API allowlists
  • Rate and cardinality controls
  • No direct public management exposure

No direct public management exposure

Management interfaces are never exposed directly to the public Internet. Acquisition runs over private or out-of-band paths with certificate validation.

Normalized modeling

From raw register to governed point

Every acquired value is mapped to a stable identifier, given source and receipt time, assigned a canonical quality state, and related to its asset and dependency context.

  • Stable point identity that survives reconfiguration
  • Source time and receipt time preserved separately
  • Canonical quality states travel with every value
  • Asset and dependency relationships attached at ingest
  • Engineering units and scaling normalized
  • Tenant and site context enforced on every point

Technical FAQs

Frequently asked questions

Explore the family

Related products

Map your protocols to a normalized model

Share your device and system inventory. We will confirm connector coverage and modeling for each source.