UC-612
Improve ROV Idle Day Recovery to increase output and recover lost value
Fills the Fleet Day page: idle days by reason, base and class, and where the next days are.
TBDBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
XXXXValue
The Challenge
The opportunity is to eliminate Idle days no public report ranks, a shop return no one has booked, and two bases chasing one system. 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 the spine: every system, its base, its class, its last contract, the days since, the floating rigs coming up for tender and the vessel schedule.
- It ranks idle systems against the work that could take them, including shop returns and resident placements, and puts a move in front of a named approver with the days and the value attached.
- It measures against the days available figure Oceaneering publishes.
What It Removes
- Idle days no public report ranks
- A shop return no one has booked
- Two bases chasing one system
Input Data RequirementsRelevant operational records, contracts, transactions, schedules, documents and outcome history named in the source proposal
Output FormatDashboard showing idle days by reason, base and class, and where the next days are.
“I know which system is free, where it sits, and what it could be on next week.”