Advanced Project Controls

Member for

13 years

I think that shud b a part of schedule maagement system, that wud typically focus on what to check in the schedule while submitting;interfaces between planning & other departments and the standard reporting formats.

__________________________

production planning software

Member for

20 years 7 months

Hi, Bobo. Since I teach just such a graduate course, here are my views:

  1. EVMS is a control system for cost and resource usage. (EV schedule data could be helpful, but not the way it is usually implemented: on the ASAP baseline schedule which is distorted by float and thus raises the prospect of gaming the data and moral hazard.)
  2. Schedule monitoring is hugely important. Two crucial topics that typically are ignored, however, are critical path drag (and it's corollary, drag cost) and float burn index (FBI), which monitors in quantified terms the potential of a non-CP path migrating to the CP.
  3. Neither of the above, however, offers a control metric that monitors the project/program as an integrated effort combining time, cost and the investment value of the scope that is the raison d'etre of the entire project. That would be the DIPP (Expected Monetary Value (EMV) plus or minus acceleration premium or delay cost, all divided by Cost Estimate-to-complete) as the baseline and the DIPP Progress Index (DPI), which is just Actual DIPP divided by Planned DIPP at any data date. 

The DIPP data provide a single index that combines all three sides of the "Triple Constraint Model", with scope measured as the expected value of the investment, cost as future resource usage to complete the scope, and time monetized as the value/cost of schedule acceleration or delay around a completion target date. (This index also eliminates the artificial construct known as a "deadline", a generator of inefficiency and moral hazard on contract projects if ever there was one!) 

Fraternally in project management,

Steve the Bajan