From documents to a connected procedure

Everything a pipeline project produces is already stored and findable: route plans in GIS, P&IDs and isometrics in the engineering vault, soil surveys as PDFs, environmental permits, welding procedure specifications, hydrotest protocols, as-built dossiers. What no system holds is how those pieces relate to one another, or to the construction and operating procedure that is actually being executed — so process compliance gets reconstructed by hand, usually at audit time.

The answer is a model written in the operator's own terms rather than another document index. A pipeline section has segments, each with a design pressure, material spec and coating. A construction procedure is a flow of steps: route clearance, trenching, stringing, welding, NDT, coating, hydrotest, backfill, commissioning. Each step requires certain documents, is governed by certain standards such as NBN EN 1594 and ATEX zoning, is performed by certain roles, and must complete before the next step starts.

That last relation is what makes the process flow a first-class object with gates. NDT cannot begin until the welding procedure is qualified. The hydrotest cannot be scheduled while the permit is invalid for that date. Commissioning cannot be signed off until the as-built dossier is complete. Each gate is a rule on the graph, and each rule points at the documents that satisfy it.

Once the assets are mapped onto the model, "which documents must be approved before NDT starts on segment 14 of the coastal section, and are any out of date?" is a query rather than a search. Because the platform knows where each segment sits in the flow, it can flag today that a permit expires before the planned hydrotest, draft the step completion report from the underlying records, or show an auditor the evidence chain from the as-built weld map back to the design pressure.

The point is that procedures and documents stop being two things linked afterwards. The ontology models the process, its gates and its evidence as one structure, so compliance becomes something the platform checks continuously rather than something reconstructed at audit time.

Nothing about the model is specific to gas. Any linear asset built under a governed procedure — fibre and duct networks, rail, water mains — accumulates the same pile of documents against the same staged, gated process, and gains the same thing from connecting them.

Pipeline routing, pressure data, permit status and weld records are all critical-infrastructure information. The platform runs on the operator's own infrastructure, so none of it leaves their perimeter.