UC-574
Improve Spread and Jack-Up Utilisation to reduce cost, risk and delay
This IS the screen. Every vessel-day and spread-day, with the cause code on the day.
TBDBuild Duration
XXXXIndicative ROI
XXXXBuild Cost
XXXXValue
The Challenge
The opportunity is to eliminate a spread-day with no cause code, a move nobody priced, and a hire above our last done. The proposed workflow is source-linked, but the current operating baseline and financial value remain illustrative until validated with the client.
How It Works
- One ledger of every vessel-day and spread-day, classified on-hire, waiting on weather, waiting on client, waiting on parts, in transit or technically off-hire, with the reason code captured as the day is lost.
- Over it: a deployment balancer, a jack-up move planner holding weather, tug and preload constraints, and a charter-in screen benchmarked against our own last done.
- Boundary: Engine 05 takes the technical off-hire day, Engine 03 takes the cargo.
What It Removes
- A spread-day with no cause code
- A move nobody priced
- A hire above our last done
Input Data RequirementsRelevant operational records, contracts, transactions, schedules, documents and outcome history named in the source proposal
Output FormatThis IS the screen. Every vessel-day and spread-day, with the cause code on the day.
“How many spread-days did we lose last month, and which of them could we have booked?”