Jacket design delivery.

Level 1 shows design phases; Level 2 adds work packages; Level 3 adds activities and milestones. Expand a summary to explore its children. Summary durations span the earliest start to latest completion, not the sum of activity durations. Dependencies connect activity IDs, not WBS codes or summary rows.

Use the organise button beside an activity to change its phase or work package, or create a new group. The Lead column identifies the foundation designer, turbine OEM, joint team or reviewer. CSV retains these fields and supports older flat activity files.

Light ILA uses a reduced Design Load Case (DLC) table; Full ILA 1 and Full ILA 2 each use a complete DLC table. Each cycle includes model acceptance, OEM load delivery, designer assessment and joint closure. Full ILA 2 acceptance gates final verification and fabrication release. Material changes after the final run require a joint decision on further analysis.

Activities start as early as their dependencies allow. Enter one or more predecessor IDs separated by commas (for example L01, I04). The selected logic and lag apply to every predecessor on that row. Positive lag adds a delay; negative lag allows overlap.

Durations and lag use whole working days. A duration of zero is a milestone. Activities finish at the end of their last working day; a finish-to-start successor starts on the next working day. Milestones mark a start-of-day boundary. All activities are constrained to start on or after the project start.

The weekday calendar excludes Saturdays and Sundays; holidays and weather allowances are not included. This version calculates earliest dates, without resource levelling or critical-path analysis.

Your entries stay in this open tab. Export a CSV before leaving to keep your activity table. CSV files contain activities and logic; set the project name, start date and working calendar separately when importing.