DID

Earned Value Management Implementation Guide (EVMIG) Rescinded

, , , , , , , ,

Earned Value Management Implementation Guide (EVMIG) Rescinded | DFARSThe DoD EVM Implementation Guide (EVMIG, Oct 2006) was rescinded on September 15, 2015 by the Office of Performance Assessments and Root Cause Analysis (PARCA). The EVMIG had provided guidance for understanding Earned Value Management System (EVMS) concepts; detailed procedures for implementing the EIA-748 EVMS Standard, Earned Value Management Systems (EVMS), on government contracts; tailoring guidance for EVMS application and reporting; and post award procedures. Most of the details contained in the EVMIG are also available in other, more recent, publications and the EVMIG is replaced with these other references. EVM System information can be found in the DoD EVM System Interpretation Guide (EVMSIG) which provides overarching DoD interpretation of the 32 EIA-748 EVMS guidelines. Additional information can be found in multiple Defense Contract Management Agency (DCMA) compliance instruction documents.

PARCA identified the following references to replace the contents and guidance found in the EVMIG:

EVM Concepts and Guidelines
EVM Concepts TBD EVM Analysis Guide
Defense Acquisition University (DAU) EVM Community of Practice
PARCA EVM Website
EVM System (EVMS) Concepts EVMSIG
DCMA Surveillance Guide

 

Procedures For Government Use of EVM
Organizational Roles and Responsibilities TBD EVM Application Guide
PARCA EVM Website
Defense Acquisition Guide (DAG)
WBS Development and Use MIL-STD-881C
TBD EVM Application Guide
EVM/EVMS Policy and Application TBD EVM Application Guide
PARCA EVM Website
Cost and Schedule Reporting Integrated Program Management Report (IPMR) Data Item Description (DID) and IPMR Guide
TBD EVM Application Guide
EVMS System Compliance EVMSIG
DCMA Surveillance Guide
Integrated Baseline Review (IBR) Program Manager’s Guide to the Integrated Baseline Review (IBR)
TBD EVM Application Guide
Reprogramming Formal Reprogramming Over Target Baseline (OTB)/Over Target Schedule (OTS) Guide
EVMSIG
Training Defense Acquisition University Website
PARCA EVM Website

Earned Value Management Implementation Guide (EVMIG) Rescinded Read Post »

Management Reserve; Comparing Earned Value Management (EVM) and Financial Management Views of “Reserves”

, , , , , , , , , ,
Management Reserve & Earned Value ManagementPerhaps you have witnessed the collision of earned value management’s views on “management reserve” with the Chief Financial Officer (CFO) and the finance department’s views on “balance sheet reserves.” Most companies tend to organize EVM, the function, reporting to either the programs’ organization or to the finance organization. Either will work but either can fail if the two organizations do not understand the interest of the other.

In this article we will outline three areas. The first will be EVM and Management Reserve (MR). The second will be finance and balance sheet “contingencies, loss provisions, or reserves.” The third will compare the two views and identify where they are similar and where they differ.

We will use two terms for both EVM and Financial Management; “in play” and “on the sideline.” “In play” for EVM means that it is in your Performance Measurement Baseline (PMB) and Budget at Completion (BAC). “On the sideline” for EVM means “not in scope” therefore in MR. “In play” for financial management means recorded on the balance sheet (e.g.: current liability; an accrued liability). “On the sideline” for financial management means not recorded on the balance sheet, because it is more likely than not that a liability has been incurred.   If material, however, it will likely be disclosed in the notes to the financial statements, even if it is not recorded on the balance sheet.

 

Earned Value Management and Management Reserve

A program manager and his or her team must deal with – mitigate – risk or be consumed by those risks as they become issues. There are two types of risks, known and unknown. The known risks are entered into a risk register, and their likelihood and consequence are determined. Mitigation for those known risks is done at the activity level in a program’s Integrated Master Schedule (IMS) (Planning and Scheduling Excellence Guide — PASEG page 141, ¶ 10.3.1). Mitigation of known risks is part of the PMB (in the BAC) and is therefore “in play.”

The second type of risk – unknown or unknowable risks – are covered by management reserve if within the Scope of Work (SOW) of the existing contract. If contractor and customer conclude that the realized risk is outside the existing contract, then an Engineering Change Proposal (ECP) would likely be created by the contractor; and a contract modification would be issued by the authorized customer contracting officer if they agreed.   The program manager should ask this question of his team: what work is “at risk” and what work is not “at risk?” Does labor or material present more risk? Management reserve “is an amount of the overall contract budget held for management control purposes and for unplanned events” (Integrated Program Management Report–IPMR DI-MGMT-81861 page 9, ¶ 3.2.4.6). Management reserve is “on the sidelines.” MR has no scope. MR is not earmarked. MR stands in waiting.

 

Earned Value Management Reserve (MR) Compared To Financial Management “Contingency”

Because the audience reading this blog is most likely from the EVM community, I’ll offer a Financial Management example of a company that faces many risks and must manage those risks or be consumed by them. Altria Group, Inc. and Subsidiaries (stock symbol: MO) are in the tobacco, e-Vapor and wine business. Altria’s history clearly shows that the company measures and successfully mitigates the risks they face. Altria faces a blizzard of litigation each year and must protect its shareholders from that risk. So how does Altria manage known risks (mostly from litigation) and how does Altria handle unknown risks?

Altria is a publicly traded company and its annual report (10K) is available on-line to the public. This data is from their 2014 annual report.

I am an MBA, not a CPA, so I’ll stick to Altria’s 2014 balance sheet. For those not familiar with financial statements, a balance sheet has on its left hand side all of a company’s assets – what the company owns and uses in its business (current assets = cash, accounts receivable, inventory; long term assets = property, plant and equipment). The right hand side of a company’s balance sheet shows current and non-current liabilities and shareholders’ equity. The top right hand side of the balance sheet includes current and non-current liabilities (accounts payable, customer advances, current and long-term debt, and accrued liabilities like income taxes, accrued payroll and employee benefits, accrued pension benefits and accrued litigation settlement costs) and the bottom of the right hand side of the balance sheet includes shareholders’ equity consisting of common and preferred stock, paid in capital and retained earnings.

Altria’s 2014 annual report shows under current liabilities; accrued liabilities; settlement charges (for pending litigation Contingency note # 18) a value of $3.5 billion dollars. The 2013 amount was $3.391 billion dollars.

So Altria has “in play” $3.5B for litigation for 2014. In financial terms, Altria has recorded $3.5 billion in expense related to the litigation, probably over several years as it became more likely than not that a liability had been incurred and was reasonably estimable. In EVM terms Altria has $3.5B in their baseline, or earmarked, or in scope for litigation (court cases).

What happens if Altria ultimately has more than $3.5B in litigation settlement costs? What does Altria have waiting on the “sidelines” to cover the unknown risks? Essentially Altria has on its balance sheet waiting “on the sidelines” $3.321 billion in cash and the ability to borrow additional funds or perhaps to sell additional shares of stock to fund the settlement costs. In EVM terms Altria has $3.5B in its baseline (on its balance sheet) to manage the risks associated with litigation. Altria’s market capitalization at the market close on May 17, 2015 was $52.82 billion and its 2014 net revenues were $24.522 billion. It is reasonable to understand that Altria has more than enough MR.

 

Differences Between EVM MR and Financial Management Balance Sheet Reserves

In EVM, MR is only released to cover unplanned or unknown events that are in scope to the contract but out-of-scope to any control account. A cost under-run is never reversed to MR, and a cost over-run is never erased with the release of MR into scope.

In industry in general, and Altria in particular, if the “in play” current liability for settlement charges of $3.5B are not needed (an under-run), then Altria will reverse a portion of the existing accrued liability into income, thereby improving profitability. If Altria’s balance sheet reserve of $3.5B is insufficient, then Altria’s future profits will be reduced as an additional provision will be expensed to increase the existing reserve (an over-run).

[Humphreys & Associates wishes to thank Robert “Too Tall” Kenney for authoring this article.]

Management Reserve; Comparing Earned Value Management (EVM) and Financial Management Views of “Reserves” Read Post »

Variance Analysis, Corrective Action Plans, Root Cause Analysis

, , , , , , , , ,

Variance Analysis “provides EVMS contract management with early insight into the extent of problems and allows corrective actions to be implemented in time to affect the future course of the program.” [NDIA ANSI EIA 748 Intent Guide] Department of Defense Data Item Descriptions: DI-MGMT-81861, Integrated Program Management Report (IPMR) paragraphs 3.6.10xx; DI-MGMT-81466A, Contract Performance Report, paragraph 2.6.3; and DI-MGMT-81650, Integrated Master Schedule (IMS) — paragraph 2.5 — all require analysis for significant variances including cause, impact and corrective action plans.  By comparing the performance against the plan, it is possible to make mid-course corrections which assist completion of the project on time and within the approved budget. The Variance Analysis Report (VAR) is a “living, working document to communicate cause, impact and corrective action”. [See: Chapter 35 Variance Analysis and Corrective Action, Project Management Using Earned Value, Humphreys & Associates, page 707.] Well-written variance analyses should answer the basic questions of why, what and how.

Cause is also known as root cause, nature of the problem, problem statement, issue, or problem definition. Root cause is the fundamental reason for the problem. Root cause is required in order to take preventative corrective action. The explanation of the variance is broken down into each of its components: discuss schedule variances separately from cost variances; discuss labor separately from non-labor; discuss which portion of the variance was caused by efficiency (hours) and which portion was because of dollars (rates) or if the variance was driven by material discuss how much was because of price and how much was because of usage. For more information refer to Humphreys & Associates blog Variance Analysis-Getting Specific.

Once the root cause of the problem has been identified and described, the impact(s) on the project should be addressed. Identify impacts to customers, technical capability, cost, schedule (including when the schedule variance will become zero), other control accounts, program milestones, subcontractors, and the Estimate at Completion, including rationale.

A corrective action (CA) plan should be developed that describes the specific actions being taken, or to be taken, which includes the individual or organization responsible for the action(s). The corrective actions should be directly derived from root cause analysis and related to each identified root cause.   Results from previous corrective action plans should be included.  Occasionally, a successful plan will include interim modifications or fixes in the short term, with long term changes identified as well. When no corrective action for an overrun is possible, an explanation and EAC rationale should be included.  A corrective action log should be used that tracks the actions taken and the status of the corrective plan for each variance analysis cycle.  As was stated in the Humphreys & Associates article:  Corrective Action Response: Planning and Closure – Part 2 of 2  “It is critical that verification methods, objective measures, metrics, artifacts, and evidential products are identified that will verify that the corrective actions are effective.”  Corrective action plans based on clearly a defined root cause facilitates time management action and avoids the occurrence of repetitive problems.

Variance Analysis, Corrective Action Plans, Root Cause Analysis Read Post »

Earned Value Management | Integrated Program Management Report (IPMR) XML Electronic Submittals

, , , , , , ,

One of the major changes in the 2012 IPMR Data Item Description (DID) was the requirement to use the DoD-approved XML schemas and guidelines to electronically submit formats 1 through 4, 6, and 7. The DoD-approved XML schemas were developed under the auspices of the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT), a formal international organization for establishing electronic business standards.  The DoD-approved XML guidelines are the Data Exchange Instructions (DEIs) or business rules for using the UN/CEFACT XML schemas to support the data requirements in the IPMR DID.  This XML electronic submittal format replaces the ANSI X12 Electronic Data Interchange (EDI) transaction sets 839 and 806 found in the previous reporting DIDs, the 2005, DI-MGMT-81466A, Contract Performance Report (CPR) and the 2005, DI-MGMT-81650, Integrated Master Schedule (IMS).

The purpose of using a software vendor neutral international standard to submit data to the DoD was to eliminate the need for any specific toolset or proprietary database at either end.  Contractors can use their toolset of choice or internally developed applications to produce the XML instance files and electronically submit the data. For the various DoD end-users, they can use their toolset of choice or internally developed applications to read the XML data for their use and analyses.

The business owner for the DoD IPMR Data Exchange Instructions is the OSD Office of Performance Assessments and Root Cause Analyses (PARCA), Earned Value Management (EVM) Division (https://www.acq.osd.mil/evm). The electronic submittals are designed to support the OSD EVM Central Repository (https://dcarc.cape.osd.mil/EVM/EVMOverview.aspx), a joint effort between the Defense Cost and Resource Center (DCARC) and OUSD/AT&L, managed by PARCA.  The EVM Central Repository provides a secure centralized reporting, data collection and distribution of EVM data environment for the DoD acquisition community.

There are a number of UN/CEFACT XML related resources available to contractors, software vendors, and government users on the DCARC EVM Central Repository web site.

  • Select the UN/CEFACT XML navigation option to download the base UN/CEFACT XML schemas as well as the Data Exchange Instructions for the IPMR formats. There are three primary DEIs. One for Formats 1 through 4 (can include Format 5 data as an option), one for Format 6 (the IMS), and one for Format 7 (time phased historical data). Also on this web page is a link for a digital file signing tool; this works as an outer envelope that contractors can use to digitally sign and secure an XML instance file submission to the EVM Central Repository.
  • Select the EVM Tools navigation option to download the XML instance file IPMR Schema/DEI Checker or XML instance file viewers. The schema/DEI checker can be used to verify a given XML instance file conforms to the basic XML schema requirements as well as the business rules defined in the DEIs.  The XML instance files viewers can be used to read and display the XML data content in a more human friendly format.

A number of the commercial off the shelf (COTS) software vendors have submitted their IPMR outputs for testing to the EVM Central Repository to verify their XML outputs can pass the Central Repository data submission validation process. A number of contractors also tested outputs produced from their internal application systems (no COTS tool was used). This testing was part of the implementation verification process for completing the Data Exchange Instructions. To confirm a software vendor has successfully completed the process to verify their tool-set outputs can be successfully read and uploaded to the Central Repository, send an email to the EVM Contact for PARCA listed on the DCARC EVM Central Repository web site (Contact Us navigation link).

PARCA has also recently taken ownership of the XML schema and DEI Change Control Board (CCB) and related process. The intent is to use the PARCA Issue Resolution process (https://www.acq.osd.mil/evm/ir/index.shtml) for software vendors, contractors, or other end users to submit change requests for the base UN/CEFACT XML schemas or IPMR Data Exchange Instructions.

Earned Value Management | Integrated Program Management Report (IPMR) XML Electronic Submittals Read Post »

IPMR DID Change – Office of Secretary of Defense Publishes New Procedure

Office of Secretary of Defense (OSD) Publishes the Integrated Program Management Report (IPMR) Data Item Description (DID)

This is important, new information for companies with U.S. Department of Defense EVMS contractual requirements.

The Department of Defense Integrated Program Management Report (IPMR), Data Item Description (DID), DI-MGMT-81861, replaces the Contract Performance Report (CPR) DID, DI-MGMT-81466A, and the Integrated Master Schedule (IMS) DID, DI-MGMT-81650.

The IPMR DID can be downloaded from the ASSIST database:  IPMR ASSIST document

The IPMR DID will apply to new contracts and may be applied to follow on contracts, subject to negotiation with the government customer.

In summary:

  • The IPMR DID combines the CPR and IMS DIDs into one.  The intent is to emphasize the integration of the schedule and cost data for performance reporting.
  • CPR Formats 1 to 5 are now the IPMR Formats 1 to 5.  There are a few content changes for Formats 1 to 5 which are mostly confined to Format 3.  The Baseline Changes (Block 6.b.) row columns have been opened up for change detail content.
  • The Integrated Master Schedule (IMS) becomes IPMR Format 6.  There are additional schedule data elements that are required including specific data coding details.
  • A new Format 7 has been added for time phased cost data (historical and future time periods).  Format 7 is an annual submission.
  • The electronic data delivery format for the OSD EVM Central Repository is changing from the ANSI X12 standard to the UN/CEFACT XML standard.  Additional information about the XML data submittal instructions is available on the OSD EVM Central Repository website.

We highly recommend being prepared to support the new IPMR DID as it will impact existing EVM Systems.  It will be necessary to reference the old and new terms and forms.  Existing contracts will be against older DID requirements (unless otherwise negotiated with the client) and new contracts will be against the IPMR DID.

Be prepared to update:

  • Training materials to reflect the updated cost Formats 1 to 5 as well as discuss the new Format 6 and 7.
  • System Description and Storyboard text as well as example formats and/or artifacts.
  • Procedures or project directives that specify schedule data coding requirements and related details necessary to produce the required IMS data for submission to the OSD EVM Central Repository.
  • Desktop instructions for producing the cost IPMR Formats 1 to 5 as well as the new Format 7.
  • Software toolset outputs and electronic deliverables.
  • Contractor self-surveillance and subcontractor surveillance materials.

Most cost and schedule software vendors are aware of the IPMR data requirements.  You may want to check with your toolset vendor of choice to see when they plan to have software updates available to support the IPMR DID and the UN/CEFACT XML data submissions to the OSD EVM Central Repository.

Humphreys & Associates is available for consulting on this topic.  Contact us for more information.

IPMR DID Change – Office of Secretary of Defense Publishes New Procedure Read Post »

New Integrated Program Management Report (IPMR) DID

, , ,

This coming change, likely to take effect in May 2012, applies to government contractual requirements (CDRLs) on contracts that require Earned Value Management (EVM) by most federal agencies. This is of particular importance to program and project managers, corporate EVM focal points and other staff that maintain a corporate EVM System Description or training materials. In some cases it applies to IT resources responsible for maintaining the schedule and cost toolsets used on projects.

A new Data Item Description (DID) for contract performance reporting and integrated master schedules was recently circulated for public comment.  The new DID, Integrated Program Management Report (IPMR), DI-MGMT-81466B, will replace the current Contract Performance Report (CPR) DID, DI-MGMT-81466A, and the Integrated Master Schedule (IMS) DID, DI-MGMT-81650.

A copy of the draft IPMR DID can be found on the PARCA (Performance Assessments and Root Cause Analyses) website. PARCA is part of the Office of the Assistant Secretary of Defense for Acquisition.  The Earned Value Management Division of PARCA is the DOD focal point for all policy, guidance, and competency relating to EVM.

In summary:

  • The IPMR DID combines the CPR and IMS DIDs into one
  • CPR Formats 1 to 5 become the IPMR Formats 1 to 5
  • The IMS becomes IPMR Format 6
  • There are a few content changes mostly confined to Format 3, which opens up the Baseline Changes (Block 6.b.) row columns
  • It adds a new Format 7, time phased historical data (an annual submission)
  • The electronic data delivery format is changing from the ANSI X12 standard to the UN/CEFACT XML standard

The initial comment period for the IPMR DID closed on January 31, 2012, followed with additional discussions with industry through the NDIA Program Management Systems Committee (PMSC). The likely publication date is early May 2012 but this is dependent on the final formal coordination process within OSD. The new DID will begin being applied on new contracts once the DID is approved.

The new DID does impact current EVM Systems as it will be necessary to reference the old and new terms and forms.  As a result, it may be necessary to update:

  • Training materials
  • System Description and Storyboard text, example formats and/or artifacts
  • Desktop instructions for producing specified formats
  • Software toolset outputs and electronic deliverables
  • Self-surveillance and subcontractor surveillance materials

Most cost and schedule software vendors are aware of the pending changes.  You may want to check with your toolset vendor of choice to see when they plan to have software updates available to support the new DID requirements.

Humphreys & Associates is available to provide resources, consulting and information on this topic. Click here to contact us.

New Integrated Program Management Report (IPMR) DID Read Post »

Scroll to Top