U.S. flag

An official website of the United States government

Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock () or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Acquisition of Services (AoS)
Title 10 Changes Summary Table
Software Acquisition Pathway (SWP)
Defense Business Systems (DBS)
Software Acquisition Pathway (SWP)

EVMS Application Requirements

Breadcrumb

  1. Home
  2. About AAFDID
  3. EVMS Application Requirements

EVMS Application Requirements

CONTRACT VALUE

APPLICABILITY

NOTES

SOURCE

< $20M

​EVMS not required; may be applied at PM discretion based on risk to the Government

​Requires business case analysis and MDA approval.

Part 7 of Office of Management and Budget Circular A-11

FAR 52.234-4, FAR subpart, 34.2

DFARS 234.201

DoDI 5000.85, Para. 3C.3.c.(3)

≥ $20M &<$100M

​EVMS Required; Contractor is required to have an EVMS that complies with the guidelines in EIA-748.*

​The Government reserves the right to review a contractor’s EVMS when deemed necessary to verify compliance.

Part 7 of Office of Management and Budget Circular A-11

FAR 52.234-4, FAR subpart, 34.2

DFARS 234.201

DoDI 5000.85, Para. 3C.3.c.(3)

≥ $100M

​EVMS Required; Contractor is required to have an EVMS that has been determined to be in compliance with the guidelines in EIA-748.*

​The Contractor will provide access to all pertinent records and data requested by the Contracting Officer or duly authorized representative as necessary to permit initial and ongoing Government compliance reviews to ensure that the EVMS complies, and continues to comply, with the guidelines in EIA-748.*

Part 7 of Office of Management and Budget Circular A-11

FAR 52.234-4, FAR subpart, 34.2

DFARS 234.201

DoDI 5000.85, Para. 3C.3.c.(3)

Table Notes:

While the DODI 5000.85 provides an overview for EVM, the application of EVM is not specific to any one acquisition pathway.  EVM should be applied per the contract type and thresholds described above.

For programs or contracts associated with programs where the OUSD(A&S) is the MDA, the  OUSD(A&S) Acquisition Data and Analytics, in coordination with the CAE or designee, will review proposed contract work scope for EVMS applicability and provide a recommendation to the DAE/MDA for a determination of EVMS applicability.  For all other ACAT levels, the CAE or designee, will review and determine EVMS applicability.  If EVMS is determined to apply, then threshold application in this table is utilized or a waiver from the CAE is required.  If, based on the nature of the work, EVMS is determined not to apply, then EVMS is not placed on contract.

The term "contracts" includes contracts, subcontracts, intra-government work agreements, and other agreements.

For indefinite delivery, indefinite quantity (IDIQ) contracts, inclusion of EVMS requirements is based on the estimated ceiling of the total IDIQ contract, and then is applied to the individual task/delivery orders, or group(s) of related task/delivery orders, that meet or are expected to meet the conditions of contract type, value, duration, and work scope.  The EVMS requirements should be placed on the base IDIQ contract and applied to the task/delivery orders, or group(s) of related task/delivery orders.  "Related" refers to dependent efforts that can be measured and scheduled across task/delivery orders.

The Integrated Baseline Review is required when EVMS is determined to be applicable.

The initiation of an over-target baseline or over-target schedule must be approved by the Government PM.

Application thresholds are in then-year dollars.

For more information regarding EVM Policy or the EVM Central Repository visit the OUSD(A&S) Acquisition Data and Analytics / Integrated Program Management website

* EIA-748 = Electronic Industries Alliance (EIA) 748-Current Version