Understanding the DCMA 14-Point Schedule Assessment: A Guide for Primavera P6 Users

Introduction :

In complex projects, accurate and reliable scheduling is essential to ensure on-time and on-budget delivery. However, not all schedules are built according to best practices. This is where the 14-point schedule assessment comes in Defence Contract Management Agency.

The DCMA 14-Point Schedule Health Check is a widely recognised standard used to assess the quality and integrity of project schedules, particularly in government and defence contracts. If you are using Oracle Primavera P6, The application of DCMA standards ensures your schedule adheres to best practices, limits risks, and improves performance monitoring.

In this article, we will explain what the 14-point DCMA evaluation is, why it is essential, and how you can implement it in Primavera P6.

What is the DCMA 14-Point Schedule Assessment?

The DCMA 14-Point Assessment is a set of guidelines developed by the United States Department of Defense to evaluate the quality and reliability of project schedules. It helps to identify planning deficiencies that could lead to delays or cost overruns.

The evaluation checks for common errors, such as:

✔ Missing dependencies (open activities)
Excessive use of constraints
✔ High float (indicating an unrealistic schedule)
✔ A negative float (indicating already overdue deadlines)
✔ Invalid critical paths

The objective is to produce a structured, logical, and executable schedule, enabling reliable management and accurate forecasts.

The 14 DCMA Indicators Explained

The 14 DCMA indicators act as quality control checks for schedules in Primavera P6. Here are the main ones:

✅ 1. Logic test (no open activities)

Check that each activity has a predecessor and a successor (except for start and end milestones).
🔹 Threshold: a minimum of 90 % of activities must be correctly linked

🔹 Primavera P6 Best Practices:
✔ Use logical relationships (FS, SS, FF, SF)
Avoid missing dependencies

✅ 2. Advance testing (no negative lag)

Negative leads must not be used to artificially advance activities.
Utlisation : 0 %

🔹 Best practices:
Replace negative lags with correctly sequenced activities
✔ Use milestones to control early starts

✅ 3. Lag Testing (limited use of lags)

🔹 Excessive use of lags reduces schedule reliability
🔹 Threshold: maximum 5 % of relationships

🔹 Best practices:
Replace lags with explicit activities

✅ 4. Testing of strong constraints

🔹 Strict constraints (Must Finish On, Mandatory Start, etc.) disrupt the logic
🔹 Threshold: maximum 5 % of activities

🔹 Best practices:
Use constraints only if contractually necessary
Prefer flexible constraints (ALAP, Start On or After...)

✅ 5. Testing High Floats

A high float often indicates a schedule not driven by logic
🔹 Threshold: max 5 % activities with > 44 working days

🔹 Best practices:
✔ Check dependencies
✔ Link activities correctly

✅ 6. Negative float test

A negative float indicates a delay that has already occurred
🔹 Threshold: 0 %

🔹 Best practices:
✔ Quickly identify critical delays
Correct the logic rather than forcing with constraints

✅ 7. Critical path testing

🔹 Check that a continuous sequence of activities drives the end date

🔹 Best practices:
Perform regular critical path analyses (CPA)
Ensure the critical path is not artificially constrained

✅ 8. CPLI (Critical Path Length Index) Test

🔹 Measure the effectiveness of the remaining plan

Threshold: ≥ 0.95

🔹 Best practices:
✔ If CPLI < 0.95 → review the logic and reduce the float

✅ 9. BEI (Baseline Execution Index) Test

Measure execution performance against the baseline schedule

Threshold: ≥ 0.95

🔹 Best practices:
✔ Regularly compare with the baseline
Analyse delays and missed milestones

How to perform a DCMA check in Primavera P6?

1️⃣ Export data (reports or XER)
2️⃣ Use specialist tools (Acumen Fuse, ScheduleReader, XER Toolkit)
3️⃣ Manually check key indicators
4️⃣ Rectify risks (logic, constraints, resources)
5️⃣ Re-run analysis for validation

Conclusion: Why DCMA Compliance is Essential

The application of the DCMA standard allows for:

Improve the quality and credibility of the schedule.
Strengthen risk anticipation
Ensure contractual compliance (particularly EPC / defence)
✔ Increase stakeholder confidence

A good Primavera P6 schedule is more than just dates:
it must be Logical, robust, and defensible (Ready for claim).

Discussion

How do you ensure DCMA compliance in your planning?
Have you ever encountered planning quality issues on your projects?

Do you have any more questions?