Fix the SPI & CPI Indexes

[#1]

Currently the SPI Index does not function properly for tasks that start later than intended.

For example, if I have a Baselined task of 1 week duration (40 Planned Hours) that was supposed to start 2 weeks ago but hasn't started (0% Complete and 0 Actual Hours). The SPI=0 (correct).

But if I change the Start Date to today or greater (which is what a PM should do for tasks that didn't start on time) the SPI changes to 1, indicating the task is on time (it's really 2 weeks late already). It should be 0 until a % Complete is entered and then be calculated on the original start date.

It appears the SPI doesn't use the Baseline when calculating Planned Hours Scheduled to Date. It is using the current (new) Planned Hours Scheduled, which is technically incorrect.

From your Help Screen:

SPI = (Total Planned Hours x % Complete) / Planned Hours Scheduled to Date*

*If Planned Hours Scheduled to Date = 0, SPI = 1.

[#2]

CPI also does not use baseline, which will again be misleading and incorrect.

If I baseline a task with 40 Planned Hours and half way through I change the Planned Hours to 80 hours (we under estimated), WF calculates CPI based on the new number, so my budget indicator now looks good as opposed to over budget.

Essentially both are only useful if you never change your project plan dates and estimates (which happens.... never :))

[#3]

I agree with Victor! We are currently facing the same issue when we baseline projects. We either have to record manually the original planned hours or true up the numbers every time we baseline. Having the CPI and SPI use baseline will greatly improve reporting.

[#4]

Agree!

[#5]

agreed. Especially as the resource planner only shows planned hours and not projected. there start dates always need to be updated

[#6]

Totally agree. Can't believe it is not there already.

[#7]

CPI and SPI are foundational metrics that any organization adhering to PMI standards will expect from a project management system. Please fix this issue.