DCMA 14 point schedule check – Lag

In article two looking at the 14 point check we described how we at checked Negative Lag, in this post we are going to take a look at Lag, to be honest the steps almost mirror those described in the previous post, nevertheless here we go.

Lag Check This check looks at the  Lag between activities. The criteria states that there should be no more than 5% of Negative Lag in a schedule. To check this is Primavera P6 we used the following steps:

Step 1. Check the Project activity totals, which can be found in the Project View in the ‘Total Activities’ column. Make a note of this number.

Step 2. Create a report in Primavera P6 that filters out activities that have zero or negative lag, we just want the positive Lag values.

Step 3. Run the report making sure to save as an ASCII Text File, the report should open in Microsoft Excel.

Step 4. Highlight the positive Lag values which will give you a count, make a note of this number.

Step 5. Divide the count of activities by the total number of activities (the number from Step 1 and this will give you a %. If the percentage is 5% or lower, then the criteria has been met, if not then a review of the schedule lags may need to take place.

There are a further 13 checks prescribed by the DCMA which along with the Logic Check will be detailed out in further supporting documentation and video tutorials at http://www.myxacom.com where knowledge is no weight to carry.

DCMA 14 Point Schedule Check – Negative Lag (Leads)

Article 2 of 14

Slightly earlier than promised.

In our first article looking at the 14 point check we described how we checked Logic, in this post we are going to take a look at Negative Lag, or Leads if you prefer. Again this approach was used for the same client as in the previous post.

Negative Lag Check

This check looks at the Negative Lag between activities.The criteria states that there should be 0% of Negative Lag in a schedule.

To check this in Primavera P6 we used the following steps:

Step 1. Check the Project activity totals, which can be found in the Project View in the ‘Total Activities’ column. Make a note of this number.

Step 2. Create a report in Primavera P6 that filters out activities that have zero or positive lag, we just want the Negative Lag values.

Step 3. Run the report making sure to save as an ASCII Text File, the report should open in Microsoft Excel.

Step 4. Highlight the Negative Lag values which will give you a count, make a note of this number.

Step 5. Divide the count of activities by the total number of activities (the number from Step 1) and this will give you a %. If the percentage is 0% or lower, then the criteria has been met, if not then a review of the schedule lags may need to take place.

There are a further 13 checks prescribed by the DCMA which along with the Logic Check will be detailed out in further supporting documentation and video tutorials at http://www.myxacom.com where knowledge is no weight to carry.

DCMA 14 point schedule check – Logic

Article 1 of 14

This is the first article of a series of 14 planned to be run, each will be published on a Monday evening. On completion of the series a set of documents and video tutorials will also be published on myxacom.com.

Has anybody applied the DCMA (Defence Contract Management Agency) 14 point check to their schedules and if so what software did you use?

We were recently supporting a client who had a requirement to assess their contractor schedules for some level of accuracy. The DCMA 14 point check was chosen, yet we didn’t have any specific software to run the analysis.

We opted for developing reports to be run from Primavera P6 and saved them as .csv files, from here we could sort and filter to assess the schedule data against elements of the 14 point check.

Below is an example of just one of the reports that we developed and how we utilised the data to assess against the 14 point check criteria.

The example we will use here is the Logic check.

Logic Check

This check looks at the links between activities. The criteria states that the number of activities in the schedule missing a predecessor, sucessor or both should not exceed 5% of the total activities in the schedule.

To check this is Primavera P6 we used the following steps:

Step 1. Check the Project activity totals, which can be found in the Project View in the ‘Total Activities’ column. Make a note of this number.

Step 2. Create a report in Primavera P6 that filters out activities that have predecessors and/or sucessors.

Step 3. Run the report making sure to save as an ASCII Text File, the report should open in Microsoft Excel.

Step 4. Sort on Column A and then delete any row with an Activity ID as a description or any Activity ID’s with a description.

Step 5. Highlight the remaining Activity ID’s which will give you a count (number of activities left).

Step 6. Divide the remaining count of activities by the total number of activities (the number from Step 1) and this will give you a %.

If the percentage is 5% or lower then the logic is within tolerance, if not then a review of the schedule logic may need to take place.

There are a futher 13 checks prescribed by the DCMA which along with the Logic Check will be detailed out in further supporting documentation and video tutorials at http://www.myxacom.com where knowledge is no weight to carry.

Create a website or blog at WordPress.com

Up ↑