DCMA 14-point schedule check for P6 XER files (Beta)

Upload one XER and get the DCMA 14-point style health check with the activities behind every finding: logic, leads, lags, constraints, float, durations, CPLI and BEI.

Opens: XER, ZIP
Saves: HTML, XLSX, CSV

Compare

Earlier update (or the only schedule)
Choose a file… or drop it here
.xer, .zip · up to 200 MB
    Replace file

    The previous update or the baseline, as exported from P6 (.xer, or a .zip of it). Upload only this file to get a schedule health check instead of a comparison.

    Later update (optional)
    Choose a file… or drop it here
    .xer, .zip · up to 200 MB
      Replace file

      The newer update of the same project (.xer, or a .zip of it). Activities are matched by Activity ID.

      Options
      More options

      Only needed when an XER holds several projects. Empty: the projects whose Activity IDs match each other are used.

      Which activities count as critical in the report.

      For showing durations and float in days. 0 uses the hours per day of each activity's calendar, as P6 does.

      Your files are deleted after processing.

      The DCMA 14-point assessment is a common way to judge whether a CPM schedule is built well enough to rely on. Upload one Primavera P6 XER here and every check is run on it, with the activities behind each finding listed so they can be found and fixed in P6.

      The checks

      No.CheckThreshold
      1Logic: incomplete tasks without a predecessor or successor5% or less
      2Leads: relationships with a negative lagnone
      3Lags: relationships with a positive lag5% or less
      4Relationship types: finish-to-start share90% or more
      5Hard constraints (Start/Finish On, On or Before, Mandatory)5% or less
      6High float: more than 44 working days5% or less
      7Negative floatnone
      8High duration: more than 44 working days5% or less
      9Invalid dates: actuals after or forecasts before the data datenone
      10Resources: tasks without a resource assignmentinformation
      11Missed tasks: due by the data date, finished late or not at all5% or less
      12Critical path testpass
      13CPLI: critical path length index0.95 or more
      14BEI: baseline execution index0.95 or more

      Counts are of incomplete tasks, leaving out milestones, level-of-effort and WBS summary activities. Dangling activities (a start nothing drives, or a finish that drives nothing) are listed as an extra check.

      How some checks are worked out

      • Durations and float are in working days of each activity's calendar.
      • Missed tasks and BEI use the baseline project when the XER holds one, otherwise the planned finish dates stored with each activity.
      • The critical path test checks that a chain of critical activities leads back from the last activity to work at the data date. The DCMA version adds a delay and recalculates; this tool reads the dates P6 stored and does not reschedule.

      Beyond the 14 points

      The report also lists the critical and longest path activities, out-of-sequence progress, the float distribution and every calendar in use with its work week and holidays. Everything comes as an HTML report, an Excel workbook and a CSV list of findings.

      With two XER files of the same project the page compares the updates instead, and shows the health checks of both side by side: see comparing P6 schedule updates.

      More about what this tool reads and writes: P6 Schedule Update Comparison (XER).