Pinnacle Insights

In Part 2 of this series, Schedule Analysis, Part 2: Why Should I Do It?, it was stated that schedule analysis increases confidence in the schedule and its results. It provides information as to where the schedule needs to be improved and how it needs to be improved. 

In Part 1 of this series, Schedule Analysis, Part 1: What Is It?, provided a brief introduction to schedule analysis. This article discusses why a schedule analysis should be performed. But first, a point of clarification. Schedule analysis and Schedule Risk Analysis (SRA) are two different things. 

Update: August 26, 2024.
Please note that the article below refers to the implementation of a DFAR deviation implemented in 2017 that effectively changed the EVMS validation threshold for DOD cost-plus development contracts to $100M, while keeping EVMS reporting threshold at $20M. The 2024 NDAA directs the Dept of Defense to update the DFAR to raise the reporting threshold to $50M, and officially change the validation threshold to $100M. DFARs changes take a long time, and we will post additional information when changes are made.

At the most recent NDIA Integrated Program Management (IPM) Division Meeting, John McGregor, Director of Earned Value Management for OSD Performance Assessment & Root Cause Analysis (PARCA) took the stage to discuss the latest updates related to EVM threshold requirements for DoD contracts. During the presentation, John clarified that DoD Instruction 5000.02 is finalized, signed and in full affect, even though the document looks like it may be in draft form.

A schedule is a time-model of how you as the supplier or manager plan on executing your project. It represents the project scope, resources, assumptions and constraints of the project. Like a cost model, the time model or schedule should respond to changes.

Many of our clients are looking to implement an Earned Value Management System (EVMS) to satisfy reporting requirements for EVM on US federal contracts (FAR 52.234-4, DFAR 252.234-7001, or equivalent), whether they have an existing requirement, or potential future requirement.

For many years, Deltek's Micro-Frame Program Manager (MPM) has been the backbone of many Earned Value Management systems.  It provided a simplistic cost engine for a single program environment that could be integrated with scheduling data to meet the needs of even government programs.  

INTRODUCTION:

In 2012, OSD Performance Assessments and Root Cause Analysis (PARCA) introduced the Integrated Program Management Report (IPMR) Data Item Description (DID) DI-MGHT-81861.

For many years, Deltek's Micro-Frame Program Manager (MPM) has been the backbone of many Earned Value Management Systems.  It provided a simplistic cost engine for a single program environment that could be integrated with scheduling data to meet the needs of even government programs.