UC-592
Improve Transfer Spread Recovery to increase output and recover lost value
Fills the Spreads page: every transfer spread and hauling asset, where it is, what it earns.
TBDBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
XXXXValue
The Challenge
The opportunity is to eliminate Spreads idle between two nearby jobs, rig-up days no published report shows, and hauling moves priced below their cost. 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 builds one record of every transfer spread, pump, layflat string and hauling asset: where it is, what job it is on, what it earned and how long it has stood.
- It reads the completion schedules Select already works to and proposes the next job for each spread by drive time, crew hours and the margin the job carries.
- Rig-up days are shown as days, not as a note.
What It Removes
- Spreads idle between two nearby jobs
- Rig-up days no published report shows
- Hauling moves priced below their cost
Input Data RequirementsRelevant operational records, contracts, transactions, schedules, documents and outcome history named in the source proposal
Output FormatDashboard showing every transfer spread and hauling asset, where it is, what it earns.
“I can see which spread is standing and what the nearest job would pay it to move.”