Every update is checked the moment it is imported, in six families: DCMA's 14 points, GAO's critical path checks, update integrity, logic quality, NDIA's execution indices and P6's own scheduling options. Seventy checks, each against a named threshold, with the activities behind every count, kept for every update so the trend shows itself.
The update on one slide, with its lights.
···×
Nitrova Green AmmoniaFinishProgressHoursManpowerFloatStatsData Date: 10-Jul-26Delay ▼ 30 wd
▼ Against Baseline (Data Date: 11-May-26): finish 30 wd later, 15-Feb-29 → 29-Mar-29. ▼ Against Previous (Data Date: 26-Jun-26): finish 20 wd later, 1-Mar-29 → 29-Mar-29. The delay since Previous starts at CO-CIV-1094. 15.9 % of the time has passed and 1.0 % of the work is earned. The plan needs 893,388 hours now, 4,033 fewer than the Baseline.
DATES
BASELINEPREVIOUSCURRENTMOVE
Project start1-Jan-261-Jan-261-Jan-26
Data date11-May-2626-Jun-2610-Jul-26
Project finish15-Feb-291-Mar-2929-Mar-29▼ 30 wd
3 Month LAH Milestones (Top 5)
90 Piperacks - Access date for steel and equipments9-Sep-2628-Sep-2628-Sep-26▼ 13 wd
Budget 898,036 · 4,648 under, ▲ 1,110 fewer since Previous
Durationworking days · passed + remaining = total
BASELINEAT COMPLETION
Baseline87 passed694 remaining781
Previous119 passed672 remaining791
Current129 passed682 remaining811
Time passed15.9 %
Earned progress1.0 %
Against time ▼ 14.9 pts behind · against the plan (1.7 %) ▼ 0.7 pts behind
ManpowerFTE per month
BaselinePreviousCurrentPeak ▲ 36 fewer since Previous
Delay by partythe driving path's delay · every slip, by where it started
Client20 wd
Contractor10 wd
CO-CIV-1094 Additional Piling, Re-Work (SI-011) · CO-CIV-1000 Piling works
FloatCurrent · since Previous
Critical109▼ 40 more
Near critical2739 fewer
Negative float44▼ 18 more
Median total float72.9 d
Late start already passed3▼ 2 more
HealthCurrent · since Previous
Earned against planned0.59
Hours per day, needed1,31021 lower
Open ends101▲ 1 fewer
Hard constraints1
Start / Finish Statssince each data date
ACT. / PLN.Δ
Starts in Previous9 of 10▼ 10 %
Finishes in Previous4 of 8▼ 50 %
Starts in Baseline21 of 39▼ 46 %
Finishes in Baseline22 of 57▼ 61 %
DCMA's fourteen points, on DCMA's own thresholds.
···×
Nitrova Green AmmoniaDCMA 14-Point AssessmentTilesTableData Date: 10-Jul-26
PLT01-260511-Demo-Ammonia-Baseline-Rev0.xer → PLT01-260710-Demo-Ammonia-Live.xer · 5 updates · DCMA 14-Point Assessment (09NOV09) · open activities, Level of Effort left out
4within8over2not judgedNo light changed since Previous.
1Logic23 %line ≤ 5 %100 of 435 open activitiessame as PreviousOpen activities without a predecessor or a successor (the project's first and last excepted)
2Leads0 %line 0 %0 of 615 linkssame as PreviousLinks into open work with a negative lag
3Lags15 %line ≤ 5 %91 of 615 links▼ 0.1 pts higher than PreviousLinks into open work with a positive lag
4Relationship types72 %line ≥ 90 %442 of 615 links▼ 0.1 pts lower than PreviousThe finish-to-start share of the links into open work
5Hard constraints0.2 %line ≤ 5 %1 of 435 open activitiessame as PreviousStart or finish on, start or finish no later than, mandatory
6High float62 %line ≤ 5 %268 of 435 open activities▲ 0.8 pts lower than PreviousTotal float above 44 wd
7Negative float10 %line 0 %44 of 435 open activities▼ 4.2 pts higher than PreviousTotal float below zero
8High duration19 %line ≤ 5 %72 of 390 open tasks▼ 0.2 pts higher than PreviousOpen tasks whose Baseline duration is above 44 wd
9Invalid dates0line 00 of 487 activitiessame as PreviousAn actual after the data date, or a forecast before it
10Resources41 %to read159 of 390 open tasks0.6 pts lower than PreviousOpen tasks with no hours or units
11Missed tasks75 %line ≤ 5 %119 of 158 due▲ 1.7 pts lower than PreviousDue before the data date, and finished after that date or not at all
12Critical Path Testneeds a recalculationA long delay on a critical task moves the finish by as much
13CPLI0.96line ≥ 0.95▼ 0.02 lower than Previous(critical path length + its float) ÷ the length
14BEI0.33line ≥ 0.95▼ 0.01 lower than PreviousActivities finished ÷ planned to finish before the data date
9Invalid datesAn actual after the data date, or a forecast before it000000
10ResourcesOpen tasks with no hours or unitsto read43 %42 %42 %41 %41 %
11Missed tasksDue before the data date, and finished after that date or not at all≤ 5 %—82 %82 %77 %75 %
12Critical Path TestA long delay on a critical task moves the finish by as much—needs a recalculation
13CPLI(critical path length + its float) ÷ the length≥ 0.951.001.000.990.980.96
14BEIActivities finished ÷ planned to finish before the data date≥ 0.95—0.290.320.340.33
Was the update statused and scheduled cleanly?
···×
Nitrova Green AmmoniaUpdate integrityTilesTableData Date: 10-Jul-26
PLT01-260511-Demo-Ammonia-Baseline-Rev0.xer → PLT01-260710-Demo-Ammonia-Live.xer · 5 updates · AACE 53R-06 update review · DECM · SCL Protocol · ploteer's own red flags, each update against the one before
15within4red flagsSince Previous: Logic changed on a critical activity turned a red flag
This update on its own
Forecast start before the data date0line 00 of 487 activitiessame as Previous
Forecast finish before the data date0line 00 of 487 activitiessame as Previous
Actual after the data date0line 00 of 487 activitiessame as Previous
Started with 0 %2line 02 of 487 activitiessame as Previous
100 % without an actual finish0line 00 of 487 activitiessame as Previous
In progress without an actual start0line 00 of 487 activitiessame as Previous
Actual finish before actual start0line 00 of 487 activitiessame as Previous
Against the update before
Backdated actuals0line 00 of 487 activitiessame as Previous
Riding the data date0 %line ≤ 1 %0 of 322 not startedsame as Previous
Actual dates changed after reported0 %line ≤ 10 %0 of 156 reportedsame as Previous
Days since the update before14 dline ≤ 31 d▲ 7 d less than Previous
ploteer's own red flags
Remaining duration grew, original unchanged21a red flag▼ 9 more than Previous
% complete up with no actual hours4a red flagsame as Previous
Original duration cut on a critical activity0a red flagsame as Previous
Logic changed on a critical activity1a red flag▼ 1 more than Previous
Actual date withdrawn0a red flagsame as Previous
Finished inside a shorter window0a red flagsame as Previous
Constraint added on a milestone0a red flagsame as Previous
Budget cut while in progress0a red flagsame as Previous
Is the critical path valid, as GAO asks?
···×
Nitrova Green AmmoniaGAO critical path validityTilesTableData Date: 10-Jul-26
PLT01-260511-Demo-Ammonia-Baseline-Rev0.xer → PLT01-260710-Demo-Ammonia-Live.xer · 5 updates · GAO Schedule Assessment Guide (GAO-16-89G), best practice 6 · critical = the schedule's own critical marks
3within2over1not judgedNo light changed since Previous.
The driving path starts at the data dateyesyesThe first open activity on the driving path is in progress, or starts on the data date
A critical activity in progress6line ≥ 1▲ 4 more than PreviousSomething on the critical path is under way
Level of effort on the critical path0line 0same as PreviousAn LOE that is critical drives nothing real
Lags on the critical path16line 0▼ 2 more than PreviousA critical activity driven by a critical predecessor through a lag
Hard constraints on the critical path1line 0same as PreviousA hard constraint holds a critical date instead of the logic
Critical share25 %to read109 of 435 open activities9.4 pts higher than PreviousCritical activities among the open ones; GAO asks why when it is high
The logic, check by check.
···×
Nitrova Green AmmoniaLogic qualityTilesTableData Date: 10-Jul-26
PLT01-260511-Demo-Ammonia-Baseline-Rev0.xer → PLT01-260710-Demo-Ammonia-Live.xer · 5 updates · NASA · DOE · DECM · CIOB · the review tools · redundant links read one step ahead
6within5red flagsNo light changed since Previous.
Links per open activity2.83line ≤ 4▼ 0.02 higher than PreviousLogic density: each link counts at both ends
Redundant links32a red flag▼ 1 more than PreviousAn FS link that a one-step FS chain already holds
Two links on one pair12a red flagsame as PreviousThe same two activities tied twice (FS and FF ...)
SS + FF ladders0a red flagsame as PreviousPairs tied start-to-start and finish-to-finish
Soft constraints1.8 %line ≤ 15 %8 of 435 open activitiessame as PreviousStart or finish on or after, as late as possible ...
Level of effort driving work0line 0same as PreviousAn LOE with a real activity after it
Milestones with a duration0line 0same as PreviousA milestone that takes time
Ready to start, not started1a red flag▲ 1 fewer than PreviousEvery predecessor done, still not started
Duplicate activity names6a red flagsame as PreviousActivities that share a name with another
Long lags22a red flagsame as PreviousLinks with a lag above 22 wd of the project calendar
Merge points0 %line ≤ 5 %0 of 435 open activitiessame as PreviousOpen activities with more than 15 predecessors
Is the work finishing as forecast?
···×
Nitrova Green AmmoniaExecutionTilesTableData Date: 10-Jul-26
PLT01-260511-Demo-Ammonia-Baseline-Rev0.xer → PLT01-260710-Demo-Ammonia-Live.xer · 5 updates · NDIA PASEG v6 and the Predictive Measures Guide · Earned Schedule on every activity, the first schedule as the plan
2within5over1near the line2not judgedNo light changed since Previous.
CEICurrent Execution Index50 %line ≥ 75 %4 of the 8 forecast to finish▼ 8.0 pts lower than PreviousOf the activities the update before forecast to finish by now, the ones that did
Hit task %37 %to read7 of the 19 the Baseline had due18.8 pts lower than PreviousOf the activities the Baseline had finishing this period, the ones that finished on or before that date
BEIBaseline Execution Index0.33NDIA bands52 finished of 158 due▼ 0.01 lower than PreviousActivities finished ÷ planned to finish by now
CPLICritical Path Length Index0.96NDIA bandsthe path 670 wd from the data date▼ 0.02 lower than Previous(critical path length + its float) ÷ the length
SPI(t)Schedule Performance Index, time0.76NDIA bands▼ 0.07 lower than PreviousThe time earned ÷ the time spent since the first schedule, on every activity
TSPITo-complete Schedule Performance Index1.02line ≤ 1.10966 days of work in 951 days▼ 0.01 higher than PreviousThe pace the rest of the work needs to make the plan's finish
TSPI − SPI(t)0.26line < 0.10TSPI 1.02 against SPI(t) 0.76▼ 0.08 higher than PreviousHow much faster the plan expects the rest to go than the project has gone so far
IEAC(t)Independent Estimate at Completion, time6-Jan-30to readthe schedule: 29-Mar-29The finish at the pace so far: the plan's duration ÷ SPI(t)
TFCITotal Float Consumption Index0.77line ≥ 1.00129 wd spent▼ 0.14 lower than Previous(time spent + the critical path's float) ÷ time spent
Forward compression1.00line ≥ 0.859,749 d now, 9,750 in the Baselinesame as PreviousThe durations of the work not started yet, now ÷ in the Baseline
The scheduling options of every update, side by side.
···×
Nitrova Green AmmoniaP6 scheduling optionsTilesTableData Date: 10-Jul-26
2as the spec asks2to look at6to readNo light changed since Previous.
Progressed activitiesWhen scheduling progressed activities useRetained logicUFGS: retained logicthe same in all 5How an activity started out of sequence is scheduled: progress override lets it ignore its open predecessors, and a switch moves dates with no change in the work
Critical activitiesDefine critical activities asTotal float ≤ 15 dUFGS: longest path120 h, as P6 keeps itthe same in all 5What P6 marks critical. The Review reads critical by the project's own rule
% complete typePercent complete type (the project's default)PhysicalUFGS: physicalthe same in all 5What % complete means for a new activity: physical progress, the duration passed, or the units spent
Total float asCompute Total Float asFinish floatto readthe same in all 5Late finish − early finish (P6's default), the start float, or the smaller of the two: the same schedule shows a different float
Relationship lag calendarCalendar for scheduling Relationship LagPredecessor's calendarto readthe same in all 5Which calendar counts a lag's days: the predecessor's (P6's default), the successor's, 24 hours or the project's
Expected finish datesUse Expected Finish DatesOnto look at when used113 open activities carry onethe same in all 5An activity with an expected finish takes that date: its remaining duration is set to meet it, not worked out from the work left
Open ends criticalMake open-ended activities criticalNoto readthe same in all 5Whether an activity without a successor counts as critical whatever its float
Start-to-start lag fromCalculate start-to-start lag fromEarly startto readthe same in all 5Whether an SS lag counts from the predecessor's early start (P6's default) or its actual start once it has begun
Float to the finish ofCalculate float based on finish date ofEach projectto readthe same in all 5Each project's own finish, or the latest finish among the projects opened together
Multiple float pathsCalculate multiple float pathsOffto readthe same in all 5Whether P6 numbers the float paths (1 = the driving path to the end activity)
The situation
Is this update fit to accept, or should it go back for revision?
Was it scheduled to its data date before it was sent, or are forecast dates left in the past?
Were actuals backdated, or changed after they were reported?
Did a scheduling option change since the last update, such as retained logic to progress override?
How does it read on DCMA's 14 points, and which activities sit behind each count?
Is the work finishing as forecast, and where does the finish land at this pace?
What turned red since the last update, and where?
Did the resubmission fix what went back with comments?
What you do
1
Import the update. All seventy checks run the moment the file lands, on the update alone and against the one before. Nothing to run, nothing to set up. ploteer reads the XER and never writes back to P6; a resubmission with the same data date is kept as a revision of that update.
2
Read the lights. One window, a tab per family of checks: each check's light, its reading against its threshold, its trend over the updates and its move since the last one, in tiles or as a table with every update a column. A click shows the activities behind a count, on the schedule.
3
Set, then send. Where the scheduling specification has thresholds of its own, set them; each names whose it is. Filter the schedule to a check and export the grid for the review comments, activity by activity. Or ask Fogg how the update reads: Fogg answers from the lights and the counts.
The checks of an update review, run the same way on every update, from every submitter.
What you get
A reading against its threshold for every check, and the activities behind every count.
Each family reads the update as its source sets out: DCMA's 14 points on the incomplete activities, Level of Effort left out; GAO's critical path checks from best practice 6; the update review of AACE 53R-06 against the update before; NDIA's execution indices in NDIA's bands. Every reading sits against its threshold, and the threshold names whose it is: DCMA's, GAO's, NDIA's, DOE's or NASA's, or ploteer's own where no published figure exists, with the source one click away. A threshold the project changed is marked wherever it shows.
Because every update is read on import and kept, a check is never one number. It has a trend: the remaining durations that keep growing, the float that keeps draining, the key milestones slipping again. The questions of an update review are asked every time: forecast dates left in the past, backdated actuals, a scheduling option changed since the last update.
ploteer counts and points; the reviewer judges. There is no single number for the schedule: a red light is a question to ask, and the answer is the reviewer's. The Critical Path Test needs a recalculation, and its tile says so rather than guess; the basis of schedule, the durations and the risk stay with the reviewer. Beside the checks, ploteer walks the longest path itself from the file's logic and holds it against P6's own critical flag.
What is seen goes out: the tables to Excel, a sheet per family, the tabs to PDF or PowerPoint, a page each, ready for the review report and the board.
An extension of time is measured on the updates. Checked as each one arrived, and kept, they show which updates hold up and which come with a caveat.
