Planning, P6 and 4D
Planning, P6 scheduling and 4D simulation
A programme your employer accepts, your team can run, and your claims can rely on. We build and review Primavera P6 schedules and link them to the model for 4D.
The problem we solve
Many programmes are submitted to meet a deadline, not to be used. Logic is missing, constraints force dates, and float means nothing. The employer's consultant returns comments, the baseline stays unapproved, and the contractor ends up without an agreed reference when delay or acceleration is discussed.
A schedule that is not accepted also cannot support an extension of time. When a delay event happens, you need a baseline that was reviewed, with logic that holds up when a delay is inserted. That work is far cheaper before the first update than during a dispute.
What we deliver
- Baseline programme in Primavera P6 with WBS, activity codes, calendars and resource or cost loading where the contract asks for it
- Schedule health check against the DCMA 14-point assessment, with a findings list and fixes
- Programme narrative covering sequence, assumptions, constraints and key dates
- Monthly updates with progress, float movement and a short variance report
- Recovery and look-ahead programmes for the next four to six weeks
- 4D simulation: activities linked to model elements, with a walkthrough video or a model-based review session
- Delay analysis inputs prepared from updated programmes, for the contract administrator
How we work
Read the contract and the brief
We start with the programme clauses, milestones, sectional completion and submission rules, then agree the level of detail with you.
Build the logic
Work breakdown, durations from quantities and productivity, and finish-to-start logic wherever possible. Constraints only where the contract imposes a date.
Check before you submit
We run the health check, fix what it flags and write the narrative, so the submission reads as a managed plan.
Update and report
Progress is recorded at the status date, float is tracked, and changes are shown against the baseline.
Link to the model (optional)
Where a BIM model exists, we tie activities to elements and produce the 4D review.
Articles on this topic
All articlesDCMA 14-point check: how to get a P6 baseline accepted
What the DCMA 14-point schedule check tests, the thresholds to aim for, and a pre-submission routine that helps a P6 baseline pass employer review.
Read the articleClash detection that gets fixed: a coordination workflow
A BIM coordination workflow for Saudi projects: set the rules, test the models, group clashes by cause, assign owners and close issues with evidence.
Read the articleFIDIC 2017 notices: the 28-day rule (Sub-Clause 20.2) explained
How the 28-day Notice of Claim in FIDIC 2017 Sub-Clause 20.2.1 works, what the Engineer's 14-day notice does, and a register routine to avoid a time bar.
Read the articleFrequently asked questions
Do you work in Primavera P6 only?
P6 is our main tool because most Saudi employers and consultants ask for XER files. We can also receive a Microsoft Project or Excel programme and convert it, then check the logic.
What is the DCMA 14-point check, and is it required in Saudi Arabia?
It is a set of 14 schedule quality tests published by the US Defense Contract Management Agency. It is not a Saudi requirement, but it is a clear benchmark, and some employers reference it. We use it as an internal quality gate unless your contract states another method.
Can you produce a 4D simulation without a BIM model?
4D needs model elements to link to. If there is no model, we can scope a light model for the areas that matter, or use a phased site plan animation instead.
Can you take over a late project's programme?
Yes. We review the current update, rebuild the logic where needed and set up a recovery programme. We would also note what the records can and cannot support for a time claim.
Talk to us about this service
Send us the contract programme clause and your latest programme file, and we will reply with a proposed scope.