Connectors
Protocol adapters that bridge PLCs, fieldbus networks, MES, and ERP into a single typed data model — one query surface across the stack.
§ Technical footprint
- Protocols
- OPC UA
- MQTT
- PROFINET
- EtherCAT
- REST · gRPC
- Deployment
- on-prem
- edge
- hybrid cloud
- air-gapped
- k8s · bare-metal
- Compliance
- TISAX*
- ISO 27001*
- GDPR-compliant
- Made in Germany
Versions · protocols · limits
- PLC
- Siemens S7
- Rockwell
- Beckhoff
- ABB
- FIELDBUS
- PROFIBUS
- Modbus RTU/TCP
- CANopen
- ETHERNET
- PROFINET
- EtherCAT
- EtherNet/IP
- ENTERPRISE
- SAP S/4HANA
- MES (Hydra · SIMATIC IT)
- KNIME · R · Power BI
- API
- REST (OpenAPI 3)
- gRPC
- Kafka topics
- signed webhooks
- SECURITY
- mTLS
- OAuth2 · OIDC
- per-connector audit log
What it does.
- P01
One data model, many protocols
Every connector maps its wire format into the same typed data model. A KPI defined once in the platform reads identically whether the source is a Siemens PLC, an S/4HANA order, or a KNIME workflow.
- P02
Typed, not lossy
Connectors carry units, timestamps, and quality flags end to end. A torque reading is never just a float — it has a unit, a sampling rate, and a provenance chain into the raw frame.
- P03
Back-pressure aware
Every adapter has a bounded queue, a retry policy, and a dead-letter sink. A downstream ERP outage does not corrupt shop-floor history; the platform replays on recovery.
- P04
Observable by default
Each connector emits Prometheus metrics on throughput, lag, and error rate. Operators see a broken SAP hand-off in the same console where they see an anomaly on the line.