Early and late dates come from the forward and backward pass over the working calendar. Total float is the slack before the activity delays completion; the critical path is every activity with none. Value share is optional and feeds the cost projection.
Programme checks
The Protocol asks for a properly logic-linked, resourced programme, updated as the works proceed, so that delay can be measured against it (Core Principles 1 and 2). A programme that cannot pass these checks will struggle to carry a claim.
What Sub-Clause 8.3 asks for
Tick what the programme submission includes. The 2017 forms list these in Sub-Clause 8.3; the 1999 forms and the MDB editions ask for the order, the timing, the periods for reviews, the inspections and tests, and a supporting report on methods and resources.
Each event is inserted as a fragnet against the activity it affects: either it delays the start of the activity or it prolongs the work. The programme is then re-scheduled and completion read off, which is the Time Impact Analysis the Protocol prefers for a prospective assessment (Core Principle 4). Employer and Contractor events are impacted separately so concurrency can be seen.
The MS Project file carries the activities, durations, dates and links; Primavera P6 opens it through File › Import › Microsoft Project XML.
The cost projection reads the programme as phases by section: the value share you entered, spread over each section's dates. The delay check and the claim builder read the impacted completion.