AVEVA PI System
AVEVA (formerly OSIsoft)
Typical setup time
2–4 hours
Historian & monitoring system integrations
Your historian already has the data. We read it.
Six native integrations covering the historian and vibration monitoring systems deployed across oil and gas midstream. Read-only API access — no SCADA modifications, no new sensors.
Supported systems
Six integrations. Zero rip-and-replace.
All connections use read-only historian or condition monitoring APIs. No active polling of PLC or DCS systems.
GE Digital Cimplicity
GE Digital (Vernova)
Typical setup time
3–6 hours
AVEVA Wonderware
AVEVA (Schneider Electric)
Typical setup time
3–5 hours
Bently Nevada System 1
Baker Hughes (Bently Nevada)
Typical setup time
4–8 hours
Emerson AMS Machinery Manager
Emerson Electric
Typical setup time
4–6 hours
SKF @ptitude
SKF Group
Typical setup time
3–5 hours
Connection specifications
Technical requirements per integration
Expand each integration for API version, required permissions, firewall requirements, and configuration notes.
Requires PI Data Archive 2019+ and PI AF 2.10+. The Midstreamly collector authenticates via Kerberos or NT LAN Manager against the PI server. Read-only access to the target AF database is required; no write permissions needed.
# Firewall — outbound only from collector host PI Web API endpoint: TCP 443 (HTTPS) → pi-srv-01.corp.local PI Data Archive: TCP 5450 (PI SDK) → pi-srv-01.corp.local [optional fallback] Midstreamly ingest: TCP 443 (HTTPS) → ingest.midstreamly.com # Required PI security permissions PI Identity: Midstreamly_ReadOnly PI Mapping: PI Identity → AD Group (e.g., MSL-PI-Readers) AF Security: Read access to target AF database + template elements
System 1 Enterprise 6.x+ includes a built-in OPC-UA server that exposes raw vibration waveform data. Full waveforms (up to 25,600 samples/channel) are accessible via OPC-UA NodeId subscription. The collector requests waveforms at configurable intervals; overall vibration values (RMS, 1×, 2×) are polled continuously at 1 Hz.
# Bently Nevada System 1 OPC-UA server_url: opc.tcp://bn-srv-01.corp.local:4840 security_mode: SignAndEncrypt auth_type: username # or certificate channel_nodes: - ns=2;s=COMPR04.BRG-DE.VIB_X_RAW_WAVEFORM - ns=2;s=COMPR04.BRG-DE.VIB_Y_RAW_WAVEFORM - ns=2;s=COMPR04.BRG-DE.OVERALL_RMS - ns=2;s=COMPR04.BRG-DE.PHASE_1X waveform_request_interval_s: 600 # 10-minute waveform capture overall_poll_interval_ms: 1000 # 1 Hz continuous
AMS Machinery Manager 5.x+ exposes route-based and online vibration data through OPC-DA. For continuous online monitor integration (AMS 6500 online unit), waveform data is accessible at 5–30 minute intervals depending on monitoring channel configuration.
Alternatively, AMS can be configured to export measurement data as scheduled XML files to a shared folder, which the Midstreamly collector watches via file-based ingestion — useful when OPC-DA access is restricted by IT policy.
Wonderware Historian 2020+ exposes a REST API at /api/v1/ for tag value retrieval. Midstreamly authenticates with an application account granted read-only tag access. Tag browsing uses the tagname search endpoint; historical data is requested in configurable time windows.
GET /api/v1/tags/values?tagNames=COMPR04_VIB_X,COMPR04_BRG_T
&startTime=2026-01-01T00:00:00Z
&endTime=2026-01-01T01:00:00Z
&count=3600
Authorization: Bearer {token}
# Response sample
{
"tags": [
{ "tagName": "COMPR04_VIB_X", "values": [...] }
]
}
OT network security
Read-only. Outbound-only. No SCADA writes.
Every integration in the Midstreamly stack is read-only at the API level. The on-premise collector agent initiates all connections — there are no inbound network connections from the cloud platform to your facility network.
No PLC or DCS access
Historian-only. We never poll PLCs directly. All data comes from time-series historian or vibration monitor APIs — Level 2/3 systems only.
Outbound HTTPS only
Port 443 outbound from collector to
ingest.midstreamly.com. No inbound rules required. No VPN tunnel to plant DMZ.Purdue Model compatible
Collector runs at Level 3.5 (DMZ). Reads from Level 3 historian. Compatible with ISA-95 and IEC 62443 network segmentation requirements.
Tag name tokenization
Raw SCADA tag names are replaced by opaque tokens before leaving the collector. Asset identifiers and tag paths are not stored in the cloud platform.
Don't see your system? We've connected to 12+ historian configurations.
Most midstream facilities run a combination of historians and monitoring systems not covered by our standard integrations. Share your configuration and we'll assess feasibility within 48 hours.
Discuss Your Configuration