When Assets Share Dependencies

Pipeline integrity portfolios are often reviewed asset by asset, yet real operating systems are rarely independent.

Different pipeline segments, facilities and integrity programmes can share the same physical corridors, crossings, power supplies, control rooms, communications infrastructure, contractors, inspection technologies, software workflows, material vintages, analytical assumptions, spare parts and specialist resources.

These shared dependencies can create common-mode exposure that is difficult to see when each asset is evaluated only through an individual risk score.

At the same time, the strength of engineering evidence is rarely uniform across a portfolio. One high-consequence asset may have current and well-validated inspection evidence, while another apparently lower-risk asset may depend on uncertain material properties, incomplete records, weak data alignment or poorly constrained assumptions.

This white paper presents a series-specific Portfolio Evidence-Dependency Review for making these cross-asset dependencies and differences in evidence confidence visible before portfolio prioritization and resource commitment.

The paper deliberately does not propose a replacement quantitative risk model, financial valuation method or universal prioritization score.

Instead, it places several distinct considerations side by side:

consequence — safety, environmental, service and regulatory significance;

evidence confidence — completeness, quality, recency and contextual fit of the engineering evidence;

shared dependency — common physical, digital, organizational or specialist-resource dependencies;

common-mode exposure — a single threat, assumption or weakness capable of affecting multiple nominally separate assets;

intervention lead time — how long inspection, repair, replacement or mitigation may require;

resource constraints — specialist capacity, outage windows, material availability and other competing needs; and

financial / non-financial alignment — how engineering need, value, cost, risk and organizational objectives interact without collapsing them into one opaque number.

A central proposition of the paper is that a portfolio is not merely a list of independent assets.

Two apparently separate assets may share a hillside, river crossing, power source, telecommunications path, control room, inspection vendor, engineering team, software model or material-vintage assumption. If that shared dependency fails—or the shared assumption is wrong—multiple integrity decisions may be affected simultaneously.

The paper therefore distinguishes asset risk from evidence confidence.

Evidence confidence does not replace consequence or likelihood. It asks a different question: how strongly does the available information support the estimate being used?

A high-consequence asset may be well understood because it has strong inspection coverage and current validated data. A lower-consequence asset may be much less certain because of missing records, weak historical alignment or uncertain material properties.

Making that distinction visible helps identify assets that require attention because they are high risk, poorly understood, or both.

The paper also emphasizes that common-mode exposure is not only physical.

Organizations can create common-mode vulnerability by relying across many assets on:

one software workflow;

one specialist engineering team;

one inspection technology;

one contractor;

one interpretation rule;

one data source; or

one organizational assumption.

If the shared dependency fails, several apparently independent portfolio decisions can be degraded at once.

The Portfolio Evidence-Dependency Review can be qualitative or semi-quantitative. Its purpose is to challenge portfolio assumptions before major prioritization or resource commitments are made.

It is especially useful where:

several asset priorities are close;

multiple assets depend on the same evidence source or assumption;

one shared threat may affect several assets;

intervention lead times differ materially;

specialist resources are scarce; or

one intervention could reduce a common-mode exposure across multiple assets.

The paper also separates engineering context from economic optimization.

Cost, outage impact, value, regulatory obligations and lead time are legitimate decision inputs. However, they should be considered after consequence, evidence confidence, dependency and common-mode exposure have been made explicit. This helps avoid false precision from a single composite score whose internal reasoning becomes difficult to review.

A four-stage maturity path is proposed:

Asset-by-Asset → Evidence-Aware → Dependency-Aware → Portfolio-Integrated

At Asset-by-Asset maturity, priorities rely mainly on individual asset scores and cross-asset dependencies may remain invisible.

At Evidence-Aware maturity, the confidence and quality of the supporting evidence are considered alongside risk.

At Dependency-Aware maturity, shared physical, digital and organizational dependencies are explicitly mapped and common-mode exposures influence prioritization.

At Portfolio-Integrated maturity, risk, evidence confidence, dependencies, lead times and resource constraints are reviewed together, making portfolio choices easier to explain, challenge and revisit.

The paper is grounded in publicly available work including ISO 55001:2024, ISO/TS 55010:2024, API RP 1160, ISO 55012:2024, DNV-RP-0670, PHMSA integrity-management material and API RP 1187.

These established standards and practices already address asset-management decision-making, risk, value, competence, information management, integrity management and financial/non-financial alignment.

Accordingly, this paper makes no claim to invent portfolio risk management, asset prioritization, common-mode analysis, asset management or financial optimization.

Its narrower contribution is the author-defined Portfolio Evidence-Dependency Review: a manufacturer-neutral organizational aid that exposes common-mode dependency and uneven evidence confidence before portfolio prioritization.

The review is not presented as an industry standard, certification scheme, trademarked method, quantitative replacement risk model or first invention.

Its output does not authorize expenditure or operational action. It provides structured engineering context for the accountable owner/operator process to make those decisions.

The scope remains limited to publicly discussable engineering evidence, assessment and human engineering decision support. It does not specify proprietary execution-control mechanisms, automated physical actuation logic or safety-instrumented functions.

This paper forms No. 31 of Phase IV — From Live Asset to Long-Horizon Accountability, extending the series from preservation and reuse of historical engineering evidence into a wider portfolio question: what changes when apparently separate assets share evidence, infrastructure, threats, assumptions and resources?

Author-written abstract, reproduced from the authoritative Zenodo DOI record.