Ganymede FPSO — Topside Modifications

Contents

01 Time effect on planned Completion

How the 9 days arise

The event adds 14 days to the flare knock-out drum tie-in chain. Five of those days are absorbed by the total float that path carried at the dividing date, and the remaining 9 days pass through to planned Completion. The float consumed belonged to the Contractor under the ECC; its consumption is reported here because it explains the difference between the event's duration and its effect, not because it is itself a matter for assessment.

02 Basis of assessment

The two programmes compared

The assessment compares AP-06, the Accepted Programme current at the dividing date of 3 October 2024, with that same programme impacted by CE-014 and re-run. No other change was made between the two: the calendars, the resource assignments, the constraint set and every activity unaffected by the event are identical. A difference in planned Completion between the two can therefore only be attributable to the event.

Why the movement of planned Completion is the measure

Under the ECC, the delay to the Completion Date is assessed as the delay to planned Completion shown on the Accepted Programme (clause 63.3 under NEC3). The measure is deliberately not "the delay on site" and not "the delay to the Completion Date as previously assessed": it is the movement of the Contractor's own planned Completion when the event is applied to the programme that was accepted. That is what has been measured here.

The dividing date and why it matters

The dividing date of 3 October 2024 is the date of the Project Manager's instruction giving rise to the event. Work before it is treated as fact; work after it is treated as forecast. Choosing a later programme revision would fold in delays that arose after the event and are not caused by it; choosing an earlier one would ignore accepted changes that were properly part of the plan when the event occurred. AP-06 is the revision in force on that date.

Both programmes were parsed on-device from the files listed at Appendix C. Neither file was uploaded and no copy is retained.

03 The driving path

The 9 days reach planned Completion along a single path. Six activities moved; each is listed in full at Appendix A.

Where the delay travels

The instructed redesign holds A-2140 KO drum tie-in detail design, which in turn holds fabrication, delivery to the module, installation and the commissioning sequence that follows it. The path was already the driving path to planned Completion before the event; CE-014 lengthened it rather than changing which path drives, which is the simpler and more defensible of the two cases.

Why the delta shrinks along the path

The event adds 14 days at A-2140 but only 9 arrive at Completion. The reduction happens twice and is visible in the table: 3 days are absorbed at A-2210, where the installation window had float against the commissioning sequence, and 2 further days at A-2340. No days are lost to rounding or to calendar differences — both programmes use the same offshore calendar, and the arithmetic closes exactly at 14 − 5 = 9.

04 What this does not decide

This report assesses one thing: the effect of CE-014 on planned Completion. Four questions that usually accompany it are outside its scope, and are listed here so that no reader has to infer the boundary.

Whether CE-014 is a compensation event

Not decided here. Whether the instruction falls within one of the events listed at clause 60.1, and whether it was notified in time under clause 61, are matters for the Project Manager and the Contractor under the contract. This report takes the event as given and measures its programme effect; if the event is later found not to be a compensation event, the measurement is simply not used.

The change to the Prices

Not assessed here. The change to Defined Cost plus Fee is a cost assessment requiring rates, resources and records that a programme file does not contain. The time effect established here is an input to that assessment — prolongation is priced against a period, and this is the period — but it is not itself a valuation. The quotation pack at SI-NQ-EX-008 carries the placeholder for the estimator.

Concurrency and other causes

Not allocated here. The comparison isolates CE-014 by holding everything else constant, which is the right way to measure one event but means the report is silent on whether another cause was operating over the same period. Where two events overlap, each will measure at its full effect in its own assessment and the two cannot simply be added. Resolving that is a matter for the Project Manager's assessment under clause 64.

Acceleration and mitigation

Not assumed. The impacted programme applies the event to the accepted logic without adding resource, re-sequencing or working additional shifts. If the Contractor is instructed to mitigate, or elects to, the effect changes and the assessment should be re-run on the mitigated programme rather than adjusted by judgement.

A Driving path — full register

Every activity on the driving path to planned Completion whose dates moved, in sequence. "Float at dividing date" is the total float each activity carried on AP-06 before the event was applied — it is what the reduction in delta along the path is spent from.

The driving path is identical in both programmes, so a single register serves for each. Where an event changes which path drives, both paths are listed and the activities present in one only are marked.

B Key Dates and milestones

Every Key Date and sectional milestone on the programme, with its movement under the event. Key Dates carry their own obligations under clause 30.3 and are assessed independently of Completion — a milestone can move without planned Completion moving, and the reverse.

KD-03 moves further than Completion. The flare system Key Date sits on the affected path with less float than the path to Completion, so it absorbs less of the event: 11 days against 9. A Key Date moving by more than planned Completion is not an inconsistency — it is the ordinary consequence of different float on different paths — but it is the item most often missed, and it carries its own consequences under clause 30.3 independently of the Completion Date.

C Programme provenance

The provenance of both programmes, recorded at the time of assessment so that the comparison can be reproduced exactly.

Difference between the two files

The impacted programme contains two activities not present in AP-06 — A-2141 revised detail design cycle and A-2142 Project Manager review of revised detail — both being the instructed work itself. No activity was deleted, no duration outside the event was altered, no constraint was added or removed, and no calendar was changed. That list is exhaustive: any other difference between the two files would invalidate the comparison, so it is stated rather than summarised.