UC-538
Improve Dig List to reduce cost, risk and delay
One board: ask what happened on a job like this one, and read the record it came from.
TBDBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
XXXXValue
The Challenge
The opportunity is to eliminate a dig no engineer can defend, an anomaly ranked by depth alone, and a re-run from a wrong call. The proposed workflow is source-linked, but the current operating baseline and financial value remain illustrative until validated with the client.
How It Works
- A dig list ranked by predicted failure pressure and failure pressure ratio under the new PHMSA tiers, with tool tolerance carried through, digs clustered by location, and a written rationale per dig for the operator's regulator file.
- The machine learning classifier used today only for mechanical damage is extended to SSWC, CSCC and pinholes on TDW's own adjudicated calls.
- Boundary: producing and validating the anomaly list is the Report Engine's.
What It Removes
- A dig no engineer can defend
- An anomaly ranked by depth alone
- A re-run from a wrong call
Input Data RequirementsRelevant operational records, contracts, transactions, schedules, documents and outcome history named in the source proposal
Output FormatOne board: ask what happened on a job like this one, and read the record it came from.
“Which anomalies must be dug this year, and how do I prove that call?”