in 2005, us defense contract management agency implemented a 14-point schedule assessment to help the department of defense evaluate the enormous volume of contracts and schedules they were tasked with managing.
years later, the dcma’s 14-point schedule assessment has become a guideline that is widely used and has been incorporated into many software tools such as deltek acumen fuse and primavera p6 eppm.
but what exactly is the dcma 14-point schedule assessment checking?
well, essentially it’s evaluating whether a schedule is well-built – whether it adheres to a set of best practices considered important to the success and manageability of a project. these best practices are broken down into a list of 14 checks
1) checking the logic
are is the logic complete? are there missing links. we all know that a schedule is a network, and if that network is not complete because of missing logic, an accurate critical path is not possible.
2) looking for leads
negative lags are often referred to as “lead time”. negative lags can cause all sorts of problems. plus they can be confusing. here, the goal is to have no negative lags in your schedule
3) looking for lags
the dcma is a bit more forgiving when it comes to positive lags, but the goal here is to minimize their use in your schedule. the goal is no more than 5% of relationships should have a lag. here’s how you might find those lags.
4) the right relationship types
p6 and other software supports 4 relationships types, but that doesn’t mean you should build a schedule using only start-start relationships. finish-start is best. dcma says your schedule should use finish-start 90% of the time (or more).
5) how ’bout those hard constraints
hard constraints can really affect logic (as we’ve told you) and can disable a schedule from being logic-driven. i say you can do without hard constraints. dcma says don’t have hard constraints on more than 5% of all constrained activities.
6) rein-in your total float
44 days is all you get. high float activities may not be linked properly and can cause havoc on your critical path. this check looks for activities with total float values over 44 days. again, the goal is less than 5% of activities can have float values of 44 days or more.
7) negative float is never good
if you’re followup these checks up to here, you may not have a problem with negative float. ideally dcma says avoid having negative float in your schedule. if you do, make sure you’ve documented a plan to mitigate being late.
8) break down those long durations
when is an activity too long? when it’s longer than 2 months, says the folks at dcma. you’ll want to limit long duration activities to no more than 5% of all activities. or just break those long activities down into a series of shorter ones for more detail.
9) check for invalid dates
no actual dates in the future, beyond your data date; and no forecast dates in the past before your data date. primavera p6 may not allow some of these conditions, but remember these checks can be applied to a schedule built in any software package.
10) load it up with 世界杯时间比赛时间 and costs
dcma likes their schedules to be resource and cost-loaded. and if you are following this path as well, make sure not to leave out workable activities; milestones excluded.
11) subvert activity slippage
we all want to deliver on time. this check looks at how many activities have finished late as compared to the baseline. it’s a good generic check to see if your project will deliver on time or not.
12) critical path integrity
the 12th check is one that tests the integrity of your schedule’s critical path, looking for fluidity driven by good logic linking. here dmca checks that introducing a delay in the schedule results in the project’s finish date being equally delayed.
13) critical path length index (cpli)
this check is a bit difficult to explain. i’ve deferred to ron winter’s explanation who sums it up this way:
“the critical path length index (cpli) is one of the ‘trip wire checks’ that is supposed to gauge the realism of completing the project on time. most construction schedulers will find this test a little bizarre. we are to measure the ratio of the project critical path length plus the project total float to the project critical path length. the critical path length is the time in work days from the current status date to the “end of the program.” the target number is 1.0 with a value of less than 95% as a failure.”
thank you, ron.
14) baseline execution index (bei)
the baseline execution index is meant to help you understand how well you are performing against your project’s baseline. the bei sums up how many activities are ahead or behind schedule against the baseline. a bei of 1.0 means you are right on track. dcma says a bei of less than 0.95 puts you on notice.
you can get more information from dcma on the 14-point schedule check here.
so should you use these guidelines as outlined by the dcma?
well, there are different views on that question. most of these guidelines are accepted as best practices for practitioners in many industries. and most of them are easy to check manually within primavera p6, with the exception of the last 3 that are a bit more involved.
whether you think the dcma’s 14 checks result in a good schedule or not, i’m fairly certain we will be seeing more of them in the future as more and more tools start to implement them in the software.
originally published may 15, 2014. this articles has been reviewed and updated for consistency.
