What changed?
Define the observation precisely. Is it a new alarm, trend, inspection finding, performance shift, field observation, test result, or recurring condition?
CONDITION & CONTEXT
Condition information becomes useful when the organization understands what changed, can trust the evidence, considers the operating context, examines supporting or contradictory information, and determines what the combined evidence means for the asset and the decision ahead.
SOUBEL PERSPECTIVE
An alarm, trend, inspection finding, test result, field observation, or model output may be important. It may also be incomplete, misleading, poorly timed, or disconnected from the conditions under which the asset was operating. A defensible decision brings detection together with evidence that can withstand context, contradiction, consequence, and follow-through.
10 QUESTIONS FOR A DEFENSIBLE DECISION
The questions below draw on established asset-management, integrity, reliability, condition-monitoring, and risk principles. They are deliberately broader than a maintenance decision tree because the right response may be to monitor, investigate, change operations, escalate, mitigate, repair, defer, replace, redesign, or invoke a specialist methodology.
Define the observation precisely. Is it a new alarm, trend, inspection finding, performance shift, field observation, test result, or recurring condition?
Check source, quality, completeness, calibration, timing, lineage, assumptions, and whether the apparent change could be noise, instrumentation error, or a data-quality problem.
Establish operating mode, load, pressure, temperature, throughput, environment, recent maintenance, process changes, and other conditions that may change the meaning of the signal.
Integrate inspection, integrity, maintenance, process, field, laboratory or metallurgical, historical, and comparable-asset information where it is relevant.
Connect the condition to asset duty, criticality, degradation or failure context, reliability, availability, operating limits, and the function the asset must continue to perform.
Challenge the potential safety, environmental, regulatory, production, reliability, financial, and other material consequences of both action and inaction.
Consider continued operation, monitoring, additional evidence, inspection, changed operating conditions, escalation, mitigation, repair, deferral, replacement, redesign, or specialist analysis.
Compare risk, cost, performance, timing, uncertainty, downtime, resource constraints, remaining life, reversibility, and the consequence of waiting.
State the assumptions, contradictory evidence, information gaps, thresholds, triggers, and escalation conditions that would justify a different course.
Define ownership, follow-up evidence, effectiveness measures, verification, record updates, and what the organization should learn for the next decision.
A concise meeting-ready guide and decision record for operations, integrity, reliability, maintenance, asset-management, and leadership teams.
Use it to: challenge the evidence, capture context, compare options, document the decision basis, and define how the outcome will be verified.
BASIS & USE
This guide is informed by recognized asset-management, integrity-management, reliability, condition-monitoring, and risk practice. It is designed as a leadership decision aid, not as a replacement for applicable regulations, engineering standards, company procedures, qualified technical judgment, RCM, RBI, FMEA/FMECA, integrity assessment, or other specialist methodologies.
Why this matters: PHMSA pipeline-integrity requirements explicitly emphasize data integration, risk analysis, preventive and mitigative measures, qualified review, effectiveness measurement, and records supporting analyses and decisions. ISO's asset-management work likewise treats decision-making and the usefulness of asset data as formal management concerns. The SOUBEL guide organizes these established ideas into a concise set of leadership questions centered on Operational Trust.
THE DECISION TEST
Operational Trust requires a clear line from what changed, to what was known, to why the organization acted, to whether the action produced the intended result.