Start with a question, not a dashboard
A production discrepancy, an offshore water-cut change, a pipeline batch difference, a shore-tank quality exception and a refinery yield variance require different engineering judgments. The navigation should still answer the same questions: where did this result originate, what belongs to it, and which evidence supports it?
A Generalized Universal Lineage Architecture expresses this as a common contract. Each record carries an identity, workspace boundary, typed relationships and references to its source. An enterprise view can descend through those relationships without inventing a new investigation path for each data type.
Keep physical and contractual paths connected
A physical hierarchy might end at a reservoir zone, completion interval, delivery meter, process unit or product tank. A commercial investigation may end at a tract agreement, custody transfer condition or cargo quality clause. These are related records with different meanings; neither should be flattened into an unexplained total.
Preserve units, periods, measurement bases, effective dates and run versions as you descend. Access controls should apply at every workspace boundary. A roll-up must identify missing inputs and avoid counting the same movement twice.
Evaluate the deepest leaf
Choose one exception and ask a reviewer to reach the physical leaf and applicable agreement. Open the supporting reading, sample or event, reproduce the calculation and inspect the approval history. Repeat the exercise in another operating segment.
The homepage explorer uses illustrative examples to make this architecture tangible. During a pilot, establish supported data types, required relationships and the depth of traceability on your own hierarchy. A shared navigation pattern is valuable when the evidence survives every step.
The value to establish
A repeatable investigation path across workspaces, without losing the source or meaning of a result.
Editorial guide · Hydrocarbon Flow 360. Numerical examples are synthetic. Methods, agreements and operating constraints must be reviewed for the actual facility.