UC-602
Improve Pumping Hour Recovery to increase output and recover lost value
Fills the hours page: every fleet, every hour of the day, pumping or not, and the named reason.
TBDBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
XXXXValue
The Challenge
The opportunity is to eliminate Lost hours no report names, a sand wait with no named cause, and a slow day with no explanation. The proposed workflow is source-linked, but the current operating baseline and financial value remain illustrative until validated with the client.
How It Works
- The engine reads StimCommander, Forge and the fleet clock and builds one timeline per fleet day: pumping, wireline, pad move, sand wait, fuel wait, weather, repair.
- It names the constraint on each day, ranks fleets by hours recoverable, and tells the crew before the shift what will stop them.
- It compares fleets on the same basin and the same job design, so a slow day is explained rather than excused.
What It Removes
- Lost hours no report names
- A sand wait with no named cause
- A slow day with no explanation
Input Data RequirementsRelevant operational records, contracts, transactions, schedules, documents and outcome history named in the source proposal
Output FormatDashboard showing every fleet, every hour of the day, pumping or not, and the named reason.
“Before the shift starts I know what will stop us, and who has to move to prevent it.”