The Relynk Platform

Sensor ingestion, anomaly detection, and CMMS integration. Three layers that work together without replacing anything you already run.

Relynk platform architecture
LAYER 1

Sensor Data Ingestion

Relynk accepts data from industrial sensors and control systems without custom middleware development. The ingestion layer handles protocol translation, time-series normalization, and backfill for intermittent connections.

OPC-UA

Native OPC-UA client for direct server connection. Supports certificate-based auth and encrypted sessions.

Modbus TCP/RTU

Polling-based Modbus collection for legacy PLCs and RTUs. Configurable scan rates from 100ms.

MQTT Broker

Built-in MQTT broker supports IIoT edge devices and Sparkplug B payloads. TLS 1.3 required.

REST / Webhook

Inbound REST API and webhook receiver for custom sensors, ERP data feeds, and manual entry systems.

Sensor data ingestion
LAYER 2

Anomaly Detection

Relynk builds a statistical baseline for each sensor using 14-90 days of historical data. When a sensor drifts outside its tolerance band, the system generates an alert with the sensor ID, deviation magnitude, and historical context.

No rule-writing required. Baselines update automatically as equipment behavior shifts seasonally or after maintenance.

  • Z-score deviation with configurable sigma thresholds (default: 2.5)
  • Rate-of-change detection for rapid event escalation
  • Correlated anomaly grouping across related sensors
  • Alert de-duplication with 15-minute suppression window
  • Severity classification: warning / critical / emergency
Anomaly detection
LAYER 3

SCADA Integration

Relynk reads from existing SCADA systems via read-only API connections. No modification to your control architecture. No new hardware. Your OT security team reviews one outbound read connection.

Ignition by Inductive AutomationRead-only REST API
Siemens WinCC / TIA PortalOPC-UA or S7 connector
AVEVA System PlatformHistorian REST API
Rockwell FactoryTalkLive Data API
Custom / other SCADAVia OPC-UA or REST
SCADA integration

Work order integration

Relynk alerts mean nothing if they don't reach the person who can act on them. Every alert creates a structured work order in your CMMS with the sensor context attached.

SAP Plant Maintenance

Relynk creates notifications and PM orders via SAP RFC. Equipment number, functional location, and sensor readings are mapped automatically.

IBM Maximo

Work orders created via Maximo REST API with asset ID and location pre-filled. Supports both on-premise and Maximo Application Suite cloud.

eMaint / Fluke

eMaint CMMS integration via webhook. Work request created with custom fields for Relynk anomaly score and sensor reading trend.

How a typical deployment goes

From first sensor connected to production alert routing in under a week, for most facilities.

1

Connect your sources

Point Relynk at your OPC-UA server, SCADA API, or direct sensors. No agent installation on your control systems. Read-only credentials only.

2

Baseline runs automatically

Relynk ingests 30-90 days of historical data and builds statistical baselines for each tag. You review the sensor list, flag anything that looks wrong.

3

Alerts route to your team

Configure which alerts go where: email, SMS, Slack, or directly into your CMMS. Technicians get structured work orders with full sensor context.

Security and compliance

Industrial data is sensitive. Relynk is built with OT security requirements in mind from the start.

ISO 27001

Certified

TLS 1.3

All data in transit

AES-256

Data at rest

Pen Tested

Annual third-party

See it on your own data

Bring a data export from your current SCADA or historian. We'll run the baseline analysis on it during the demo and show you what Relynk would have flagged.

Request a Demo