How One Operator Automated Their Hydraulic Model Builds
From P&IDs and alignment sheets to a living model: the Golden Record, versioned studies, and simulation-file management.
A midstream operator’s hydraulic model is usually a heroic one-time artifact: weeks of document hunting and transcription, calibrated once, stale within months. This paper tells the anonymized story of one operator that changed the cost structure of knowing its own system: models built from the documents it already had, a versioned Golden Record as the single substrate, studies under version control, and reconciliation that makes staying current the default. Agents do the reading and the typing, within boundaries and with citations; engineers do the judging.
What is inside
- The anatomy of a 200-hour manual model build, and why almost none of it is engineering.
- The Golden Record: a versioned, queryable, provenance-bearing data type for pipeline assets.
- Building the record from the P&IDs, alignment sheets, GIS, and datasheets you already have.
- The verify-not-transcribe contract: agents propose with citations, engineers commit.
- Version control for studies: branches, diffs, merges, and provenance that survives personnel.
- Managed simulation artifacts: results that are never duplicated, orphaned, or silently re-run.
- Continuous reconciliation between GIS, documents, and live operating data, with drift as a work queue.
- The acquisition test, the compliance dividend, and a five-step adoption path with the four metrics to watch.
What changed for the operator
Reported from one North American midstream deployment, anonymized at the operator’s request. The numbers below are the two quantitative claims approved for publication, plus the structural change behind them.
One operator’s outcomes, from one document set and one team’s operating discipline. What transfers is the architecture: extraction plus reconciliation makes staying current cheap, and version control makes study work accumulate.
Your drawings already know the answer.
The paper is the story. FlowSync is the system: Model Builder reads your P&IDs and GIS, the Golden Record stays current, and Taylor answers against it with cited sources.


