Innervate was not built in a lab looking for a problem. It was built by an engineer who spent 18 years managing pipeline integrity across Southeast Asia, West Africa, and the North Sea — and kept hitting the same gap. The degradation models used during pipeline design did not account for what actually happened in operations: failed chemical injection pumps waiting months for parts, temporary separator bypasses becoming permanent, recalibration schedules that slipped because operations teams were managing ten other priorities simultaneously. When that engineer moved to managing a portfolio of 200 active pipelines — more than 40% of which could not be inspected with conventional ILI tools — the gap between what was known and what was happening became the founding problem of a company.
The Gap Between Design and Operations
Pipeline integrity models are built during design with assumptions about operating conditions — fluid composition, flow velocity, chemical injection rates, inspection intervals. In practice, operating conditions change continuously and the integrity model is rarely updated to reflect them.
This is not operator negligence. It is a structural disconnect between how pipelines are designed and how they are operated. The design phase assumes a steady-state that rarely exists in real operations.
Consider the practical realities: a chemical injection pump fails. The replacement part has a 3–6 month lead time. The pipeline continues operating without the corrosion inhibition that the integrity model assumes is in place. A temporary separator bypass installed during a maintenance shutdown becomes permanent because the modification to restore normal flow path keeps getting deferred. A dehydration unit catalyst replacement is postponed while waiting for a shutdown window that keeps moving.
Each of these events — routine in operations — creates a gap between the integrity model and the actual pipeline condition. The model says one thing. The pipeline experiences another. And unless someone reconciles these inputs, the assessment is wrong before it begins.
The 40% Problem — Unpiggable Pipelines
40% of global pipeline infrastructure cannot be inspected using conventional ILI tools (source: PHMSA). These pipelines lack pig traps, have tight bends, diameter restrictions, heavy wax buildup, or insufficient flow velocity to drive inspection tools through.
For these assets, "integrity management" is built on periodic, incomplete data — corrosion coupons, CP surveys, ECDA assessments — none of which provide continuous visibility of wall condition between inspection windows.
The operational reality is sobering: pipelines designed in the 1970s without pigging facilities, assets with heavy wax buildup that would trap any tool sent through, production rates too low to push tools through the line, or pigs stuck mid-run creating an operational crisis on top of the original inspection challenge.
From Consultancy to Monitoring-as-a-Service
Innervate operated as a corrosion engineering consultancy for three years before pivoting to Monitoring-as-a-Service. The catalyst: every consultancy engagement began with two weeks of chasing data before any engineering could start.
Shared folders. Spreadsheets that disagreed. PIMS that were only as current as the last person who updated them. Corrosion readings sitting in databases nobody had connected to anything useful.
The bottleneck was not the analysis. It was everything that had to happen before the analysis could start.
What Innervate Built
The response to this structural gap was a three-product stack designed to address each layer of the problem:
- Horizon — prediction analytics anchored to governing code equations, delivering confidence-rated assessments that engineers can defend to regulators and Technical Authorities
- Sync — data integration that reads from existing operator systems, normalises across formats and sampling rates, and delivers a single continuous data stream
- Node — continuous sensing hardware for assets with no existing monitoring, deployed non-intrusively without shutdown or pipeline access
Together, these components close the visibility gap — not by replacing what operators already have, but by connecting it and making it useful.