One programme update, checked and ranked.

Send one Primavera P6 update and your three registers. You get back the DCMA results, the register gaps a board would find and each fix, ranked.

01 / What you send

Four files and one date.

01
A Primavera P6 export
The latest update as an .xer file, with the baseline if you have one.
02
The notice register
Each notice with its due date, the date it went out and the reply.
03
The variation register
Each variation with its instruction and its value.
04
The extension of time register
Each request with its delay event and its fragnet, where one exists.
05
The date that matters
A permit, a board hearing or completion. It sets the order we read in.

02 / What we run

01
The DCMA 14-point assessment
14 checks on logic, float, durations, constraints and dates, each against its published threshold.
02
The three registers
Notices against the notice period, variations against the programme, extensions of time against their fragnets.
03
A lead's review
A lead reads every finding before the report goes out.

03 / What comes back

01
The DCMA results
Each check with its threshold, what your programme measured and the count behind it.
02
The register findings
Notices late or unanswered, variations missing from the programme, extensions of time with no fragnet.
03
The ranked fixes
Each finding with its fix, ranked by impact, then by effort.

04 / A findings page from Falaj Tower

Falaj Tower, G+14 · Sample project

DCMA 14-point

4 pass · 9 fail · 1 not scored

Registers

Top fixes

Rank	Finding	Fix	Impact / effort
01	7 of 27 notices sent after the 28-day period	Check each against the notice clause and record why it went late. Add a reminder 7 days before each notice falls due.	high / low
02	4 variations valued in the cost report with no programme assessment	Assess time for each in the next update and link it to its register ID.	high / medium
03	9 tasks on negative float, completion 11 working days past contract completion	Write the recovery narrative and tie each negative-float path to a notice or a recovery action.	high / medium
04	1 of 4 extension of time requests with no fragnet	Build the fragnet and insert it into the update current when the event happened.	high / high
05	4 open-ended tasks	Add the missing successors so float on these tasks means something. Most of the high-float tasks are these open ends.	medium / low

5 of 11 fixes shown. The full list is in the worked example.

Start here

01
You send
a Primavera P6 export (.xer) and your notice, variation and extension of time registers.
02
We run
the 14 DCMA checks, then notices, variations and extensions of time.
03
You get back
the findings ranked, each with its fix.