In our thirteenth article looking at the 14 point check we described how we checked the Critical Path Length Index, in this post we are going to take a look at the Baseline Execution Index.

The DCMA criteria states that the ratio between the number of tasks completed to the number of tasks that should have been completed should be 0.95 or greater.

Baseline Execution Index Check

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

Step 1. Open up the required project for analysis in Primavera P6.

Step 2. Create a new report through the Report Wizard by selecting Activities in the subject area as this is the data we wish to see in the output report. Click past the additional subject area screen as we do not require any additional subjects for this report.

Step 3. Add the BL Project Finish and Actual Finish columns then click next.

Step 4. Add the report title and click Run Report.

Step 5. As we want the report in Excel select ASCII and ensure that the Text Qualifier is set to “. The Report will open in Microsoft Excel.

Step 6. Filter on all the completed activities and make a note of the count. Now filter on Not Started and In Progress and filter on the current month for progress update in the BL Project Finish Column.

Step 7. Now the Baseline Execution Index calculation can be used – BEI = Tasks with Actual Finish Date / (# of Baseline Tasks Scheduled to Finish Prior to Status Date +Tasks Missing Baseline Start or Finish Date).

If the ratio is 0.95 or greater than the criteria has been met, if lower then the schedule would require a review.

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

In our twelfth article looking at the 14 point check we described how we used the Critical Path Test, in this post we are going to take a look at the Critical Path Length Index.

The DCMA criteria states that a Critical Path Index of 1 or above in favourable and below 1 is unfavorable.

Critical Path Length Index Check

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

Step 1. Open the required project for analysis in Primavera P6 and make a note of the Total Float

Step 2. Select Group and Sort, select <None> in the grouping and filter on critical activities only.

Step 3. Go back into Grouping & Sort and select show grand totals. The Duration for the Critical Path is shown, document this down.

Step 4. Now we have the data we can apply the formula – CPLI = (Critical Path Length +/- Total Float ) / Critical Path Length

If the index is 1 or above then the criteria has been met, if below one then the schedule may require a review.

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

In our eleventh article looking at the 14 point check we described how we at checked Missed Activities, in this post we are going to take a look at the Critical Path Test.

The DCMA criteria states that the critical path should be grossly extended and this should impact on the completion date of the project.

Critical Path Test

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

Step 1. Open up the project for analysis in Primavera P6.

Step 2. Select a critical activity that sits towards the front end of the critical path.

Step 3. Extend this activity by a large quantity and schedule the project.

Step 4. Analyse if the end date changes on the project.

If the completion date of the project extends then the critical path and the logic of the schedule is fit for purpose.

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

In our tenth article looking at the 14 point check we described how we at checked Resources, in this post we are going to take a look at Missed Activities.

The DCMA criteria states that the number of activities that have slipped from their baseline should not exceed 5% of the total number of activities in the project.

Missed Activities Check

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

Step 1. Open the project you wish to analyse in Primavera P6.

Step 2. Now add the Total Activities column and make a note of the Total Activities in the schedule.

Step 3. Create a new report using the Report Wizard, selecting Activities as it is activity data we require in the report.

Step 4. Add the BL Project Finish, BL Project Start, Finish and Start columns as we are looking to see if these differ on any activities. Click through until you are required to type in the report name.

Step 5.  As we want the report in Excel select ASCII and ensure that the Text Qualifier is set to “.

Step 6.  Now the report has opened in Excel insert columns between both the BL Project Finish and Start column.  Subtract the Start date from the BL Project Start Date in the column added and format the cells to a number. Repeat for the BL Project Finish and Finish column.

Step 7. Add auto filter onto the column descriptions and filter on the difference between the two start dates, note down the result. Apply the same logic on the difference between the two finish dates and make a note of the total number.

Step 8. Divide the total number of differences between the start dates and the finish dates by the total number of activities.

If the percentage is 5% or below then the criteria has been met, if higher than 5% then the schedule may need a review.

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