Drydock Project Critical Path, Work Package & Schedule Overrun Tool
Drydock Project Critical Path, Work Package & Schedule Overrun Tool
Turn a docking specification into a dependency-based plan. Compare original work scope with current progress, yard workfront capacity, contractor availability, approved changes and downtime. See which work packages control redelivery and where realistic recovery measures can reduce cost exposure.
Docking Project Snapshot
Work Package & Dependency Register
Every active task requires a unique ID. List predecessor IDs separated by commas; cycles, unknown IDs and crew requirements exceeding trade capacity block Calculate. "Progress" represents physically completed work. Remaining work is simulated from the status day.
| Use | ID | Work package / scope | Trade | Duration days | Predecessor IDs | Crew teams | Complete % | Budget USD | Safety gate | Baseline end | Forecast end |
|---|
Contractor / Trade Capacity Register
Crews are simultaneous work teams, not headcount. Crew mobilization is measured from project day zero. The scheduler prevents competing tasks from using more teams than available.
| Use | Trade | Available teams | Mobilize day | Daily team cost USD | Owner / contractor |
|---|
Change Order & Discovery Register
Approved change order days and costs are applied only to the selected work package in the forecast. Pending rows are visible in the dispute/scope board but are not automatically added as committed costs.
| Use | Change / discovery | Work package ID | Extra days | Cost USD | Decision | Responsible |
|---|
Dock Closure, Hold & Verification Register
Closure rows suspend all active work during the entered absolute day window. Verification rows may be flagged critical, which creates a separate handover hold. An unverified safety item is never treated as authorization to proceed.
| Use | Hold / check | Type | From day | Duration days | Critical? | Status | Responsible |
|---|