Connectivity
Connect the plant you have. Backfill the history you already paid for.
In-Sight reads from the control network, the historian, and the ERP through native connectors, backfills history so day one starts with context, and monitors every source for connection health and data gaps. Nothing is written to the control system, and nothing needs to be replaced.
Connector coverage
Each connector is a first-class source in the platform with its own health monitoring, gap tracking, and backfill. Tags are discovered from the source and given friendly labels, so the rest of the platform, from findings to the copilot, speaks the plant's language rather than node identifiers.
- OPC UA, including subscriptions at configurable publishing intervals and the Alarms and Conditions stream
- OPC DA classic servers, reached through a UA wrapper or an OpenOPC gateway on the DA host
- OSIsoft PI and PI Web API for historian access and backfill
- Modbus TCP for PLCs, drives, meters, and legacy equipment
- Siemens S7 for the S7-300, 400, 1200, and 1500 families
- Beckhoff ADS, Omron FINS, and Mitsubishi MELSEC for TwinCAT, Omron, and iQ-R, Q, and L series PLCs
- EtherNet/IP for Rockwell and Allen-Bradley controllers
- MQTT and MQTT Sparkplug B for IIoT gateways and edge devices
- DNP3, IEC 61850, and IEC 60870-5-104 for substations, protection relays, RTUs, and utility SCADA
- BACnet for HVAC and building systems, SNMP for network and power equipment
- Kafka topics, SQL databases (PostgreSQL, SQL Server, MySQL, Oracle), and InfluxDB as data-platform sources
- SAP OData for work orders, notifications, and master data
- REST APIs and CSV files for everything else, including LIMS exports and log sheets
High-rate capture for fast signals
Vibration, current, and pressure pulsation carry information that a one-second historian averages away. In-Sight can stream selected tags at up to 2 kHz per tag, losslessly, with momentary overshoot detection at ingest. Rates are configured from the app and the subscriber picks them up live. An engineer can zoom from months to milliseconds on the same signal.
Backfill, health, gaps, and store-and-forward
A new source is backfilled from the historian so baselines, models, and precedents start with real history. Every source reports its connection state and data gaps, and a gap is a finding in its own right, because an analytics system that silently loses data is worse than one that reports it. Reconnection and gap repair are automatic where the source supports it.
If the platform's own database becomes unreachable, readings are not dropped: every batch is spooled to local disk and replayed automatically, oldest first, once the database is back. The buffer survives a restart, its size is bounded, and its state is visible on the Sources page.
Operator rounds and documents are sources too
Manual log sheets are captured as structured operator rounds, and the readings join the same historian and detection pipeline as the sensors. Datasheets, SOPs, and manuals are ingested as documents and become the copilot's grounding and the source of proposed engineering limits. The plant's whole information estate, from the PLC to the filing cabinet, is one context.
Deployment
In-Sight runs as a set of containers on a single instance, either inside the plant network or in a dedicated cloud environment, with role-based access, workspace isolation, and an audit trail. The pre-connection checklist for OPC UA is short: endpoint, security policy, a read-only user, and the node set to subscribe. We provide the prerequisites document for OT and IT ahead of a pilot.
Connectivity capabilities
Twenty-four connector types
From OPC UA, OPC DA and PI to Modbus, S7, ADS, FINS, MELSEC, Sparkplug B, IEC 104, IEC 61850, SNMP, Kafka, SQL, InfluxDB, and SAP, plus REST and CSV.
Historical backfill
Day one starts with context: baselines, models, and precedents from real history.
Health and gap tracking
Connection state and data gaps on every source, with a gap treated as a finding.
Friendly tag labels
Node identifiers resolved to plant names everywhere in the product.
High-rate capture
Up to 2 kHz per tag with overshoot detection at ingest and zoom to milliseconds.
Read-only by design
Nothing is written to the control system. SAP write-back is limited to work orders and notifications.
Questions we are asked
- What do I need to connect an OPC UA server?
- The endpoint URL, the security policy and mode, a read-only user or certificate, and the node set to subscribe. We provide a short prerequisites document for OT and IT before a pilot.
- Can In-Sight read from OSIsoft PI?
- Yes, for both live values and historical backfill, so baselines and models start with real history.
- Does In-Sight write to the PLC or DCS?
- No. All control-network connectors are read-only. The only write-back is to SAP, for work orders and notifications, and it is optional.
- What happens when a connection drops?
- The source's health state changes, the gap is recorded and surfaced as a finding, and reconnection and gap repair are attempted automatically where the source supports it.
Tell us what is on the network.
Send the list of systems on one line and we will confirm the connectors and the prerequisites before the first call.