Data EngineeringSeptember 29, 2026
Two Ways Out of SCADA, and the Vendor Picks
By John Wassilak
Every SCADA source falls into one of two access archetypes, decided by who administers the endpoint. The ingestion pattern follows from that.
Read moreInsights
From the field.
Perspectives on upstream data infrastructure, A&D readiness, and what it actually takes to build a clean data asset in oil and gas.
Category
Data Engineering
Sort Posts
Data EngineeringSeptember 22, 2026
Your MQTT Broker Is Not a Historian
By John Wassilak
A broker holds days, not years. Sparkplug birth certificates and report-by-exception change what silence means for your pipeline.
Read moreData EngineeringSeptember 17, 2026
Alarm Data Is Not Time Series Data
By John Wassilak
An alarm is an event with a lifecycle, not a sampled signal. Store it as time series and short alarms vanish and counts stop being true.
Read moreData EngineeringSeptember 10, 2026Who Controls Your SCADA Data · Part 3
Who Controls Your SCADA Data: When Your Historian Becomes Your Data Model
By John Wassilak
An asset framework is a normalization layer. Build it inside a vendor product and it is normalization you cannot take with you.
Read moreData EngineeringSeptember 8, 2026Who Controls Your SCADA Data · Part 2
Who Controls Your SCADA Data: You Probably Don't Need a Central Historian
By John Wassilak
Process historians were built for one homogeneous plant. An acquisition-assembled upstream estate is the case they handle worst.
Read more