Attachment 0002 - Data Item Description Index - Contains 28 DIDS.pdf

DATA ITEM DESCRIPTION

Title: Ammunition Data Card (ADC)

Number: DI-MISC-80043B Approved Date: 20090623

AMSC Number: A9073 Limitation:

DTIC Applicable: GIDEP Application:

Office of Primary Responsibility: A/AR

Applicable Forms:

Use/relationship: The Ammunition Data Card is a record that documents essential historical information pertaining to the build of a production component lot or an end item lot of ammunition, explosive material or a serially numbered guided missile which contains all required data pertaining to each lot of the item. The Ammunition Data Card is used to provide traceability of explosive and non explosive end items, assemblies, sub-assemblies and component parts as mandated by contract requirements.

a. The data contained in this DID is required by MIL-STD-1168

‘Ammunition Lot Numbering and Ammunition Data Card’.

b. This DID supersedes DI-MISC-80043A which is no longer applicable.

Requirements:

1. Reference documents. The applicable issue of documents cited herein, including their approval dates, and dates of any applicable amendments, notices and revisions shall be as cited in the current issue of the DODISS at the time of the solicitation; or, for non DODISS-listed documents, as stated herein.

2. Preparation and Format. Manufacturer’s Identification

Symbols used in lot numbering must be registered per MIL-HDBK-

1461 ‘Ammunition Manufacturers and Their Symbols’. Ammunition

Data Cards shall be prepared in the World-Wide Ammunition Data

Repository Program (WARP) in accordance with the requirements of

MIL-STD-1168 and the on-line WARP User’s Manual.

3. End of DI-MISC-80043B.

DISTRIBUTION STATEMENT A. Approved for Public Release;

Distribution is Unlimited.

Source: http://assist.dla.mil -- Downloaded: 2021-06-16T21:04Z Check the source to verify that this is the current version before use.

Title: Contract Summary Report

Number: DI-ADMN-80447A Approval Date: 08 NOV 2006 AMSC Number: 7625 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship:

This report summaries all work performed under the contract.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

This DID supersedes DI-ADMN-80447.

Requirements:

1. Reference documents. None.

2. Format. The report shall be prepared in contractor’s format.

2.1 It shall be typewritten and is to be duplicated in non-fading ink.

2.2 The data indicated below shall be contained on the title page:

2.2.1 Type of Report, Final

2.2.2 Purchase Description Title

2.2.3 Contract Number

2.2.4 Dates of the Reporting Period

2.3 Security classification and distribution limitation markings shall be included on all pages.

3. Content.

Source: http://assist.dla.mil -- Downloaded: 2021-06-16T20:19Z

DI-ADMN-80447A

3.1 Table on Contents.

3.2 Brief summary of all work accomplished, to include both negative and positive results. All information shall be referenced to the appropriate Progress Report, or section of the Final Report, where the subject is discussed in detail.

3.3 The body of the report shall describe all work accomplished, including as applicable, theoretical studies, experimental work mechanical design, theory of operation, test procedures, test results, and those drawings, charts, graphs, illustrations, or other material needed to clarify the presentation.

3.4 When test equipment has been designed and constructed for use on this contract, a listing of all such equipment is to be included. This listing shall include all related drawings and associated lists. It shall be referenced in the report and included as an appendix.

3.5 Conclusions, recommendations, and proposals.

3.6 Appendixes for any necessary tables, references, photographs, charts, and illustrations.

4. END OF DI-ADMN-80447A

Source: http://assist.dla.mil -- Downloaded: 2021-06-16T20:19Z

Source: http://assist.dla.mil -- Downloaded: 2021-06-16T20:28Z

Title: Management Plan

Number: DI-MGMT-80004A Approval Date: 30 OCT 2006 AMSC Number: 7621 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: The management plan describes the contractor’s organization, assignment of functions, duties, and responsibilities, management procedures and policies, and reporting requirements for the conduct of contractually-imposed tasks, projects, or programs.

This Data Item Description (DID) contains format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.

This DID may be applied in any contract or program phase where the contract management is under the direction and control of the contractor.

Requirements:

1. Reference documents. None.

2. Format. The plan shall be in a format that the contractor devises and conforms to the following:

a. Identification. The plan shall be identified with the preparing office or contractors title, the identifying numbers or designation of the Contract/Procurement Request, the identify and/or nomenclature of the system/component/program/project, the security classification and the Government activity issuing the controlling contract.

b. Descriptive material. As may be needed to clarify or explain matters in the text, the plan may include descriptive material, sketches, drawings, photographs, tables, forms, graphs, worksheets, charts, etc.

c. Page size. The plan may be typewritten or printed on standard size paper, e.g., 8 ½ x 11 inches or metric A4. The pages shall be sequentially numbered and security bound together. As necessary, graphic material may be one-way fold-outs. All attachments shall be identified and referenced in the text. Each section and paragraph shall be numbered.

d. Table of contents and index. Plans of more than 30 pages in length shall contain a

Source: http://assist.dla.mil -- Downloaded: 2021-06-16T20:09Z

h. delivery procedures

DI-MGMT-80004A

table of contents. Plans more than 120 pages in length shall also include an Index.

e. Legibility. The document shall be legible and reproducible.

3.1 General. The Management Plan shall consist of the organizational structure, the assignment of functions, duties, and responsibilities, the procedures and policies and the reporting requirements that are established for the initiation, monitoring, control, completion, test and verification, and reporting of contractual tasks, projects, and programs.

3.2 Specific contents. The Management Plan shall cover the organizational structure, program management methodology, personnel, security, and the reports as described herein. Other subjects to be included are as follows:

a. design control

b. reliability

c. configuration control

d. standardization

e. quality assurance

f. provisioning

g. control of Government property

i. tests

j. certifications

k. packaging

l. shipping

m. other

3.3 Organizational structure. The plan shall present an organizational chart and supporting narrative portraying the contractor’s business (corporate) structure. It shall describe the functional relationships and responsibilities among the organizational elements that will participate in the accomplishment of the contractual commitments.

DI-MGMT-80004A

3.4 Program management. The plan shall present an organizational chart and supporting narrative describing the management office the contractor establishes to manage the contractual commitments. The plan shall define the direct lines of control, responsibilities, functional relationships, and authority between the management office and the contractor’s other organizational elements. The plan shall also describe all interfaces between the contractor and the Government and between the contractor and other contractors which are necessary and pertinent to the accomplishment of contractual tasks, projects and programs.

3.5 Methodology.

a. The plan include a narrative description of the technical approach or methods the contractor will employ to accomplish contractual tasks, projects, and programs, including, as applicable, development, tests, manufacture, construction, formulation, installation, logistics support, training, maintenance documentation, and configuration controls.

b. The plan shall include a milestone chart graphically depicting the schedule of events associated with accomplishing each contractual commitment.

3.6 Personnel.

a. The plan shall list the personnel staffing of the contractor’s management office that directs the contractual tasks, projects, and programs and assist in completing the contract. The listing shall include the education, training, skills, experience, and security clearance that personnel require to fill each such position and shall state the identity, background, and work experience of the personnel assigned to fill these positions.

b. The plan shall also describe the staffing required for proper accomplishment of each contractual task by skill type, skill level, number of personnel, and security clearance. When submitted as part of a proposal, the plan shall state how many such personnel are currently available and how many new hires are required to staff fully to accomplish each task as scheduled.

3.7 Security.

a. Provide a Standard Practice Procedure (SPP) which fully describes the security program, safeguards emergency procedures to be established to the protection of Government-furnished and contractor-developed classified materials prepared In conjunction with the project. The SPP shall be prepared in accordance with guidelines contained in the Industrial Security Manual, Purchase Description, and such additional requirements as may be stipulated by the cognizant security compliance organization. The SPP shall require approval by the Government.

DI-MGMT-80004A

b. Develop a comprehensive security accreditation plan to demonstrate how the computer security requirements stipulated in the PD, as applicable, have been accounted for in the system design, and how satisfaction of each requirement will be explicitly demonstrated in the test program. This plan shall also identify any specific support equipment or software to be provided for demonstration of design compliance and/or system compliance with the planned security requirements. The plan shall require approval by the Government prior to implementation.

c. Reports. The plan shall describe the management methods the contractor will employ to ensure meeting all preparations, format, and submittal requirements established by the CDRL (DD Form 1423) for data to be delivered to the Government.

4. END OF DI-MGMT-80004A

Source: http://assist.dla.mil -- Downloaded: 2021-06-16T21:21Z

Title: OPERATIONS SECURITY (OPSEC) PLAN

Number: DI-MGMT-80934C Approval Date: 20101213 AMSC Number: 9178 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: NS/I925 Applicable forms: N/A

Use/Relationship: The OPSEC Plan is used to identify and monitor a contractor’s OPSEC activities during the performance of a contract. It is intended to be a living document that will require periodic updates throughout the life of the contract. The OPSEC plan; (1) Describes the OPSEC environment to include identification of critical information, the OPSEC threat and vulnerabilities an adversary might exploit to acquire critical information, (2) Documents the OPSEC risk analysis, (3) Identifies proposed and actual OPSEC measures, (4) Defines and assigns specific OPSEC responsibilities and ties the OPSEC Plan to the contractor’s corporate OPSEC Program, and (5) Serves as a repository of the OPSEC history of the contract.

a. This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirements delineated in the contract.

b. This DID is applicable only when the contracting activity determines that the sensitivity of the contracted effort warrants OPSEC protections.

c. The contractor’s implementation of the OPSEC Plan, approved by the contracting activity, is subject to joint audit and/or inspection by the Defense Security Service and the contracting activity.

d. This DID supersedes DI-MGMT 80934B.

Requirements:

1. Reference documents: The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices and revisions, shall be as specified in the contract.

a. “Applying OPSEC to U.S. Government Acquisitions and Contracts”. This document is available from the Interagency OPSEC Support Staff (IOSS) at the following web address:

www.ioss.gov.

b. Department of Defense Manual (DODM) 5205.02M, DOD Operations Security (OPSEC) Program Manual, dated November 3, 2008.

Source: http://assist.dla.mil -- Downloaded: 2021-06-16T20:31Z http://www.ioss.gov/

DI-MGMT-80934C

c. Department of Defense Contract Security Classification Specification (DD 254). This document is included as a part of all Request for Proposals (RFP) and Contracts involving classified data.

d. Contract Data Requirements List (CDRL). This document is included as a part of all RFP and contracts containing data deliverable requirements.

e. National Industrial Security Program Operating Manual (NISPOM) 5220.22M, dated February 28. 2006.

2. Format: The OPSEC Plans shall be submitted in contractor determined format and, at a minimum, consist of the following sections listed in the Content Section below.

3. Content:

3.1 COVER PAGE

The cover page for an OPSEC Plan shall clearly present, at a minimum, the following information:

1. Title of the Acquisition Program

2. Title of the Document (i.e. “Operations Security Plan”)

3. Reference to the government contract number

4. Date of latest revision

5. Name, signature and title of the preparer of the OPSEC Plan

6. Name, signature and title of the approver of the OPSEC Plan.

7. Reference for whom the document was prepared (Contracting activity)

8. Reference by whom the document was prepared (Corporation)

9. All appropriate distribution or classification statements

3.2 TABLE OF CONTENTS PAGE

The Table of Contents for an OPSEC Plan shall outline each section contained in the OPSEC Plan.

3.3 PREFACE PAGE

The purpose of the Preface is to provide a brief, unclassified, overview of the program and the need for OPSEC measures. The specific objectives of the contracted effort shall be introduced with reference to all strategic participants and partnerships required to make the program a success. The anticipated development of any innovative concepts or technologies shall also be introduced in the Preface.

The Preface shall reference all links between the OPSEC Plan and any corporate OPSEC Program(s). The Preface may conclude by referencing requirement documents such as the contract number, Contract Security Classification Specification (DD254), Contract Data

Requirements List (DD1423) and any other pertinent guidance provided by the contracting activity. It shall also provide an OPSEC point of contact, with contact information, for additional guidance or assistance such as the OPSEC program manager or contractor program manager.

3.4 OPSEC PLAN INTRODUCTION

3.4.1 Purpose and Scope: The purpose of the OPSEC Plan shall be effectively communicated in this section and include a description of the scope of the OPSEC Plan (unique physical locations, subcontractors, suppliers, period of performance, etc.).

3.4.2 Authorities: The requirement to protect critical information shall be documented within this section. Documenting the requirement can be achieved by referencing the Corporate OPSEC Program (Policy) and Plan, DODM 5205.-2M, specific contract documents including the DD254 for contracts involving classified data, or other contracting activity specific guidance.

3.4.3 OPSEC Plan Major Activity Timeline: This section shall include a list of all major OPSEC Plan activities such as quarterly OPSEC Working Group Meetings, Annual Assessments, scheduled OPSEC awareness training, Sub-contractor OPSEC Assessments and Surveys, Threat and Vulnerability Reviews, etc. This section shall also include scheduled OPSEC Plan reviews.

3.4.4 Responsibilities: The OPSEC Plan shall identify whom is responsible for the major activities described in the Plan. For example (not intended as an inclusive list):

The OPSEC Manager shall be identified by name and include a list of duties that may include:

1. Coordinate all OPSEC policy responsibilities/ procedures within the program.

2. Revise the Program OPSEC Plan as necessary.

3. Convene and coordinate the annual Program OPSEC Assessment.

4. Disseminate updated threat information to program personnel.

5. Assist in the review of contract requirements for OPSEC considerations.

6. Conduct OPSEC briefing(s) upon customer approval of the plan.

7. Principal advisor to the Contractor Program Manager on all OPSEC matters.

8. Develop/Disseminate Program Critical Information List (CIL).

9. Promote OPSEC awareness within the program.

The Contractor Program Manager shall be identified by name and include a list of duties that may include:

1. Responsible for the overall implementation of the program/contract.

2. Ensure proper OPSEC procedures are implemented by program personnel.

3. Ensure all subcontractors and suppliers supporting the program develop and implement procedures in compliance with the Program OPSEC Plan.

4. Remain cognizant of emerging OPSEC threats and vulnerabilities that may adversely impact upon the success of the program.

5. Actively participate in periodic Program OPSEC assessments.

6. Remain cognizant of any changes in critical information and communicate them to the Program OPSEC Manager.

7. Promote OPSEC awareness within the program.

A short description of the expectations and responsibilities of all program personnel (including subcontractors and suppliers) shall be provided and may typically include:

1. Remain compliant with all applicable OPSEC Plans.

2. Maintain an awareness of all applicable CIL.

3. Attend all OPSEC program briefings.

4. Timely reporting of any OPSEC concerns to the Contractor Program Manager and/or the Program OPSEC Manager.

5. Generation of OPSEC Plans (sub-contractors or suppliers only).

3.4.5 Organizational OPSEC Communications and Interfaces: A description as to how the OPSEC Plan will be communicated to all personnel supporting the program (hardcopy, via a webpage, briefings, etc.).

3.4.5.1 Internal: In this section the OPSEC Plan shall identify all anticipated OPSEC interfaces internal to the corporation such as the senior corporate leadership, corporate OPSEC Working Group, OPSEC coordinators, program personnel, etc.

3.4.5.2 External: In this section the OPSEC Plan shall identify all anticipated external points of contact such as the contracting activity, Defense Contract Management Agency (DCMA), The Defense Security Service (DSS), Federal Bureau of Investigation (FBI) and local law enforcement and their primary role within the OPSEC program (i.e. DCMA audits acquisition management practices, DSS provides security oversight, FBI and law enforcement may provide threat data). Subcontractor and supplier OPSEC points of contact shall be similarly identified.

3.4.6 Marking, Handling and Distribution of Documents: This section shall provide a description of marking, handling, storage, access and transmission authorizations and procedures for any critical information provided to, or generated by, the contractor.

Reference to the program classification guide, Freedom of Information Act and any additional guidance provided by the contracting activity may be cited as applicable.

3.5 THREAT

3.5.1 General Threat: This section shall identify and demonstrate an understanding of the overall threat to program critical information throughout the anticipated duration of the contract/program. For example, an information systems program might note the following:

DSS analysis of 2008 threat data shows, “Information systems, especially C4ISR related systems remained the primary sought-after technology for East Asia and Pacific Region countries. Direct requests (often via the Internet) and other suspicious Internet activity continued to be the preferred method of collection. Information systems are primary targets for Near East adversaries of the United States. Near East commercial entity activity indicates a growing collusion between commercial entities and government associated entities such as universities, public agencies and research and development centers. Adversaries using HUMINT and OSINT collection methods represent a significant threat to program critical information. i

The section shall conclude with a brief description of all identified intelligence collection methods that may be expected to be used by an adversary to acquire critical information.

Note: A general description of intelligence collection methods may be found in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov.

3.5.2 Program Detailed Threat: This section shall be similar to section 3.5.1 above referencing any known direct threats to acquisition specific elements of critical information within the program/contract. As complete a description of each threat as possible shall be provided while maintaining the overall plan classification at the unclassified level. Since detailed threat information may derive from classified sources, reference to source documents as provided by the government contracting activity or other reputable source is permitted.

3.5.3 Threat Analysis: Each threat identified in sections 3.5.1 and 3.5.2 shall be analyzed to determine the level of threat to the corresponding critical information. The results of this analysis shall be presented in this section. A description of the specific threat analysis method used by the contractor to quantify each threat shall be included in this section.

Note: For additional guidance and a sample threat analysis methodology see, “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov and DODM 5205.02.

3.5.4 Changes Within Threat Environment: The Threat section shall conclude with a statement that addresses how new threat data is to be received and incorporated into the OPSEC Plan to ensure OPSEC risk remains in compliance with all applicable guidance.

3.6 CRITICAL INFORMATION

3.6.1 General: Critical information shall be identified within this section of the plan and a comprehensive program Critical Information List (CIL) shall be included.

3.6.2 Critical Information List: Guidance on the creation of a CIL is contained within “Applying OPSEC to Government Acquisitions and Contracts,” available at www.ioss.gov, DODM 5205.02M, or may be provided by the contracting activity. Ideally the CIL shall remain unclassified to facilitate wide internal distribution, but may provide reference to classified information as applicable.

http://www.ioss.gov/

3.7 VULNERABILITY

3.7.1 General: The Vulnerability section of the OPSEC Plan shall describe the analysis of activities (indicators) that point to OPSEC vulnerabilities an adversary can exploit to acquire critical information. This section shall contain a list of all identified OPSEC vulnerabilities.

3.7.2 List of OPSEC Vulnerabilities: Each vulnerability shall be described in sufficient detail as to communicate to the contracting activity the extent of the vulnerability. The Vulnerability List shall remain unclassified, but may provide reference to classified information if applicable. Reference to classified reports and other information shall include an unclassified description of the documentation (report title, number, etc.) and the source responsible for publication of the information.

Note: A list of typical OPSEC vulnerabilities which may require OPSEC measures may be found within “Applying OPSEC to Government Acquisitions and Contracts”, available at www.ioss.gov or may be provided by the contracting activity. These sample vulnerabilities are not all inclusive and the submitted vulnerability list shall be tailored to the specific acquisition or contract.

3.7.3 Vulnerability Analysis: Once potential program vulnerabilities have been identified, the magnitude of each vulnerability shall be determined using a consistent methodology identified and documented in this section of the OPSEC Plan. The results of this analysis shall also be described in this section.

Note: For additional guidance and a sample vulnerability methodology see, “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov and DODM 5205.0-2M.

3.8 RISK ASSESSMENT

3.8.1 General: The OPSEC risk of a program represents the probability of compromise of critical information and the impact to the program/contract taking into account the threat and vulnerabilities. The acceptable level of OPSEC risk (as determined by senior leadership, or the contracting activity) shall be described in this section in terms consistent with the selected OPSEC methodology.

3.8.2 Risk Assessment: The specific OPSEC risk shall be described in terms consistent with the OPSEC methodology selected for determining OPSEC threat and vulnerability.

The method, and the results of the assessment, shall be presented in this section. The conclusion of the risk assessment shall result in an ordinal ranking of OPSEC risk (highest to lowest).

Note: Additional guidance and a sample risk methodology are available in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov and DODM 5205.0-2M.

3.9 OPSEC MEASURES

3.9.1 General: This section of the OPSEC Plan shall identify specific OPSEC

Source: http://assist.dla.mil -- Downloaded: 2021-06-16T20:31Z Check the source to verify that this is the current version before use.

http://www.ioss.gov/

Measures proposed for mitigating OPSEC risk to acceptable levels including the cost to implement each measure. A sampling of common OPSEC measures is available in “Applying OPSEC to Government Acquisitions and Contracts” at www.ioss.gov . This list is not to be considered exhaustive and is provided as guidance for the development of the program/contract specific list of potential OPSEC measures.

3.9.2 Residual Risk: This section shall contain an analysis of residual OPSEC risk, in terms consistent with the OPSEC methodology selected, as a result of implementation of each OPSEC measure presented in section 3.9.1. This section shall identify which OPSEC measures will be implemented and the rationale for those that will not.

3.10 OPSEC Program Chronology: This section shall document significant program OSPEC events throughout the lifecycle of the program. Significant events may include changes to the CIL, changes in program leadership or results of program assessments and surveys (including subcontractors). At a minimum, this section shall include a brief description of the event, date of occurrence, actions taken by the contractor and final disposition. A known compromise of critical information need only be referenced in keeping with the intended classification of this document.

Note: The history contained herein may be used by the government as a part of an OPSEC or security audit conducted by the contracting activity, DSS or other authorized agency.

3.11 ACRONYMS: This section shall include a complete list of acronyms used in the Program OPSEC Plan (i.e., CDRL – Contract Data Requirements List, DID – Data Item Description, etc.).

3.12 REFERENCES: This section shall include a complete list of all references cited in the Program OPSEC Plan (i.e. DoD Manual 5205.02-M, dated November 3, 2008, Contract Number, Corporate OPSEC Plan(s)/Program(s), etc.).

i The specific example provided derives from annual documentation produced by the Defense Security Service, Counterintelligence Office in 2009. Current assessments may be found at https://www.dss.mil/isp/count_intell/count_intell.html.

4. END OF DI-MGMT-80934C.

Source: http://assist.dla.mil -- Downloaded: 2021-06-16T20:12Z

Source: http://assist.dla.mil -- Downloaded: 2021-06-16T19:29Z

Title: Integrated Program Management Report (IPMR) Number: DI-MGMT-81861A Approval Date: 20150916 AMSC Number: D9583 Limitation:

DTIC Applicable: No GIDEP Applicable: No Preparing Activity: OUSD (AT&L) PARCA Project Number: MGMT-2015-033 Applicable Forms: Forms are available to be used to submit required formats as follows:

IPMR Format Form Number Format No.

Work Breakdown Structure 2734/1 1 Organizational Categories 2734/2 2 Baseline 2734/3 3 Staffing 2734/4 4 Explanations and Problem Analyses N/A 5 Integrated Master Schedule N/A 6 Electronic History and Forecast File N/A 7

1.0. USE/RELATIONSHIP:

1.1. The IPMR contains data for measuring cost and schedule

performance on Department of Defense (DoD) acquisition contracts. It is structured around seven formats that contain the content and relationships required for the electronic submissions.

1.1.1. Format 1 defines cost and schedule performance data by product-oriented Work Breakdown Structure (WBS).

1.1.2. Format 2 defines cost and schedule performance data by the contractor's organizational structure (e.g., Functional or Integrated Product Team (IPT)).

1.1.3. Format 3 defines changes to the Performance Measurement Baseline (PMB).

1.1.4. Format 4 defines staffing forecasts.

1.1.5. Format 5 is a narrative report used to provide the required analysis of data contained in Formats 1-4 and 6.

1.1.6. Format 6 defines and contains the contractor’s Integrated Master Schedule (IMS).

1.1.7. Format 7 defines the time-phased historical & forecast cost submission.

1.2. The IPMR's primary value to the Government is its utility in reflecting current contract status and projecting future contract performance. It will be used by the DoD component staff, including program managers, engineers, cost estimators, and financial management personnel, as a basis for communicating performance status with the contractor. DoD will also use the IPMR data for the following purposes:

1.2.1. Integrate cost and schedule performance data with objective technical measures of performance.

Source: https://assist.dla.mil -- Downloaded: 2016-10-25T20:56Z

DI-MGMT-81861A

1.2.2. Identify the magnitude and impact of realized and potential performance problem areas that may cause significant cost and schedule variances.

1.2.3. Provide valid, timely, and accurate contract status information to Government leadership.

1.3. The IPMR data must be consistent with the contractor’s actual contract status.

1.4. The IPMR is used to obtain cost and schedule performance information on contracts requiring compliance with the American National Standards Institute/Electronic Industries Alliance Standard 748 (ANSI/EIA-748), Earned Value Management Systems (EVMS) (current version in effect at time of contract award; refer to the Defense Federal Acquisition Regulation Supplement (DFARS) clause on the contract). The IPMR data elements must reflect the output of the contractor's ANSI/EIA-748 compliant system, where applicable.

1.5. Requiring more information in a Contract Data Requirements List (CDRL) for the IPMR than is specified in this DID is contrary to DoD policy. All negotiated reporting provisions will be specified in the contract. Refer to the Performance Assessments and Root Cause Analyses (PARCA) EVM Web site (http://www.acq.osd.mil/evm/) for guidance on CDRL tailoring.

1.6. This DID contains the format, content, and intended use

information for the data deliverable resulting from the work task described in the solicitation.

1.7 This DID supersedes DI-MGMT-81861, 81650 and 81466A.

2.0. COMMON IPMR REQUIREMENTS:

2.1. Electronic Submittal Formats.

Formats 1-4 and 6-7.

The following requirements apply to

2.1.1.

Electronic Submission of Data. All formats shall be submitted electronically in accordance with the DOD-approved XML schemas located in the EVM Central Repository (EVM-CR). Refer to the PARCA EVM Website for a link to the EVM-CR (http://www.acq.osd.mil/evm/).

2.1.1.1.

Cost XML Guidelines. Formats 1-4 shall be submitted using the DoD-approved Cost XML guideline and schema. Formats 1-4 shall be submitted in whole units (no decimals) in the XML. Format 1 data in XML shall be provided at the reporting level per the guidance in section 2.2.2. unless specified at a lower level, such as to the control account level, in the CDRL.

2.1.1.2.

IMS XML Guidelines. Format 6 shall be submitted using the DoD-approved IMS XML guideline and schema.

2.1.1.3.

Time-phased Cost XML Guideline. Format 7 shall be submitted using the DoD-approved Time-Phased Cost XML Guideline and schema.

Format 7 shall be submitted in whole dollar units (no decimals) in the

XML.

http://www.acq.osd.mil/evm/)

2.2 Additional Submittal Formats. The following additional submittal requirements apply to formats 1-7.

2.2.1. Hours. The Government may, in the CDRL, require the contractor to provide Formats 1-4 and 7 by hours as additional, separate submissions. The CDRL will define the basis for Format 5 variance analysis (hours or dollars).

2.2.2.

Reporting Level. The reporting level is defined as the WBS level established by tailoring the appropriate MIL-STD-881 (current version in use at time of contract award) appendix by the Program Office and approved by an office(s) designated by OSD policy.

2.2.3.

Human Readable. The Government may, in the CDRL, require Formats 1-4 in human readable format down to the reporting level as additional, separate submissions.

2.2.4.

Native Variance Analysis Format. Format 5 shall be submitted in the contractor’s native electronic file format.

2.2.5.

Native Schedule Format. Format 6 shall be submitted in the contractor’s native IMS schedule electronic file format unless otherwise specified in the CDRL.

2.2.6.

Time-phased Control Account Data. Format 7 shall contain time-phased and historical monthly performance data provided at the same level as Format 1 unless otherwise specified in the CDRL.

2.2.6.1.

BCWS Reporting Period. Budgeted Cost for Work Scheduled (BCWS) shall be reported from contract award through contract completion.

2.2.6.2.

BCWP Reporting Period. Budgeted Cost for Work Performed (BCWP) shall be reported from contract award through the current reporting month.

2.2.6.3.

ACWP Reporting Period. Actual Cost of Work Performed (ACWP) shall be reported from contract award through the current reporting month.

2.2.6.4.

Time-phased Cost Projection. Time-phased cost projection shall consist of historical, time-phased actual costs (ACWP) plus future time-phased Estimate To Complete (ETC) values for all the reported WBS elements. The total of the time-phased costs must reconcile with Format 1 Block 8 Column (15) (Estimate At Completion (EAC)) for the same reporting month.

2.3.

Security Requirements. Security requirements may affect IPMR marking and/or delivery requirements.

2.4.

Subcontractor Requirement. The Government may require separate submission(s) of subcontractor IPMRs.

2.5.

Reporting Frequency.

2.5.1.

Monthly Submission Requirement. The IPMR Formats 1-6 shall be required at least monthly. The reporting frequency shall be identified in the CDRL.

2.5.2. Annual Submission Requirement. Format 7 shall be required at least annually, but may be specified in the CDRL if more frequent deliverables are required.

2.6.

Submission Requirements.

2.6.1. Formats 1-6 shall be submitted to the procuring activity no later than 12 working days following the contractor’s accounting period cutoff date. This requirement may be tailored through contract negotiations to allow submission as late as 17 working days, provided the contractor and Government agree that contract complexity and/or integration of subcontractor and vendor performance data warrant additional time and will yield more accurate performance. All the Formats shall reflect the same reporting period.

2.6.2. Format 7 shall be provided with the associated Formats 1-6 in the month(s) it is due and shall reflect information as of the same reporting period as Formats 1-6.

2.7. Scope of Reporting. Unless otherwise specified in the CDRL, data reported in the IPMR shall reflect all negotiated contract work and include the total scope of authorized unpriced work efforts as of the period specified in the IPMR.

2.8.

Applicability.

2.8.1.

When EVM DFARS is Applicable. Formats 1-7 are required whenever DFARS 252.234-7002 is applicable.

2.8.2.

When EVM DFARS is Not Applicable. Format 6 may be applied separately where DFARS 252.234-7002 is not applicable. Format 6 applies to all development, major modification, and low rate initial production efforts. Where Format 6 is applied separately, the following sections of the IPMR DID are applicable (omitting references to Formats 1-5 or 7): 1.3, 1.4, 1.5, 2.1.1, 2.1.1.2, 2.2.5, 2.3, 2.4, 2.5.1, 2.6.1, 2.7, 3.6.7 and 3.7.

2.8.3.

EVM Tailoring. Rules for appropriate tailoring are located on the PARCA EVM Web site at http://www.acq.osd.mil/evm/.

3.0. IPMR FORMAT CONTENT REQUIREMENTS.

The IPMR content shall be consistent with the contractor’s ANSI/EIA- 748 documented system, where applicable, and shall contain the following:

3.1. Common Heading Information. Preparation instructions for the common heading information apply only to Formats 1-4 and 7. The common heading information relates to Blocks 1-4 on the Formats. The instructions also apply to Format 5, but the information may be provided in contractor format.

3.1.1.

Contractor. Enter in Block 1.a the contractor's name and division (if applicable). Enter in Block 1.b the facility location and mailing address of the reporting contractor.

Source: https://assist.dla.mil -- Downloaded: 2016-10-25T20:56Z http://www.acq.osd.mil/evm/

3.1.2. Contract. Enter the contract information in Block 2.

1) Enter the contract name in Block 2.a;

2) Enter the contract number and the applicable Contract Line Item Number(s) (CLIN(s) in Block 2.b;

3) Enter the contract type in Block 2.c;

4) Enter the contract share ratio, if applicable, in Block 2.d.

3.1.3. Program. Enter in the program information in Block 3.

1) Enter in Block 3.a the contractor’s program name, number, acronym, type, model, series, or other designation of the prime item(s) purchased under the contract;

2) Enter the program phase (e.g., development, production) in Block 3.b.;

3) Use “Yes” or “No” to indicate whether the contractor’s EVMS has been approved or disapproved by the Cognizant Federal Agency (CFA) and the date of the approval/disapproval in Block 3.c.

[Note: The contractor may have several approving CFAs that may apply to different levels of the contractor’s organization.] o A “Yes” indicates system approval and “No” indicates no system approval.

o All “No” answers must be discussed in Format 5 and categorized by either “Withdrawn,” “Not Assessed,” or “Not Applicable.”

o This block shall be completed as it relates to the particular contract/site.

o The date shall be the date of the Advance Agreement, if applicable, or the date of the letter of acceptance from the CFA.

o Enter “N/A” if neither an Advance Agreement nor agency acceptance letter is applicable to the contract/site.

3.1.4. Report Period. Enter the beginning date in Block 4.a and the ending date in Block 4.b of the time period covered by the report.

3.1.5.

Security. All electronic file deliverables shall include the appropriate security designations.

3.1.6.

Dollars In. If reported dollar amounts are not in whole dollars, enter the units used (e.g. $K, $M, $B) at the top of each page. This applies only to human readable submissions.

3.2.

Format 1 - Work Breakdown Structure.

The submission of Format 1 data shall utilize a product-oriented WBS at the level established by tailoring the appropriate MIL-STD-881 (current version in use at time of contract award) appendix by the Program Office and approved by an office(s) designated by OSD policy.

WBS levels below MIL-STD-881 are defined by the contractor and reported in accordance with the DoD Cost XML Guideline.

3.2.1. Contract Data.

3.2.1.1.

Quantity. Enter in Block 5.a the number of principal hardware delivery items to be procured on this contract. Non-hardware type contracts (e.g., software or services) shall place a “0” in this block.

3.2.1.2.

Negotiated Cost. Enter in Block 5.b the dollar value (excluding fee or profit) on which contractual agreement was reached as of the reflected reporting period.

3.2.1.2.1. For an incentive contract, enter the definitized contract target cost.

3.2.1.2.2. For a cost plus fixed fee or award fee contract, enter the estimated negotiated cost. The estimated cost shall consist only of estimated amounts for changes in the contract scope of work, not for cost growth (overrun) above the original estimated cost.

3.2.1.2.3. Amounts for changes shall not be included until they have been definitized in the contract.

3.2.1.3. Estimated Cost of Authorized, Unpriced Work (AUW).

Authorized, Unpriced Work is approved work scope that has not been definitized. The total dollar value (excluding fee or profit) of AUW shall be entered in Block 5.c.

3.2.1.3.1. The value of AUW is the value of the scope that was coordinated between the contractor and the Program Office, and authorized by the Procuring Contracting Officer (PCO).

3.2.1.3.2. AUW can never be a negative value. For effort de-scoped and not yet reflected in the Contract Budget Base (CBB), report the estimated value in Format 5 (see 3.6.11.3).

3.2.1.4. Target Profit/Fee. Enter in Block 5.d the applicable fee that applies to the negotiated cost of the contract.

3.2.1.5.

Target Price. Enter in Block 5.e the target price (negotiated contract cost plus profit/fee) applicable to the definitized contract effort.

3.2.1.6.

Estimated Price. Based on the contractor’s most likely estimate of cost at completion for all authorized work, including the appropriate profit/fee, incentive, and cost sharing provisions, enter in Block 5.f the estimated final contract price (total estimated cost to the Government). This number shall be based on the contractor’s most likely management EAC in Block 6.c.1 and normally will change when the EAC is updated and/or when the contract is revised. This number shall reconcile with the estimated price in the Contract Funds Status Report (CFSR), as applicable.

3.2.1.7.

Contract Ceiling. Enter in Block 5.g the contract ceiling price applicable to the definitized effort. This is only applicable to contracts with the ceiling clause.

3.2.1.8. Estimated Contract Ceiling. Enter in Block 5.h the estimated ceiling price applicable to all authorized contractual efforts including both definitized and undefinitized efforts. This is only applicable to contracts with the ceiling clause.

3.2.1.9.

Over Target Baseline (OTB)/Over Target Schedule (OTS). Enter in Block 5.i the date the last OTB or OTS was implemented, if applicable.

3.2.2.

Estimated Cost at Completion. These blocks shall present the contractor's range of estimated costs (EACs) of the authorized contractual scope. The required range of estimates is intended to allow contractor management flexibility to express multiple, justifiable final cost outcome positions. Contractors shall provide the most accurate EACs possible that include:

• Contract-level assessments of factors that may affect the cost, schedule, and/or technical outcome of the contractual effort;

• Consideration of known and anticipated risk areas;

• Planned risk reductions;

• Cost containment measures.

EACs shall be reported without limitation of the contract ceiling value.

3.2.2.1. Management Estimate at Completion - Best Case. Enter in Block 6.a.1 the contractor's best case EAC. The best case EAC reflects the lowest potential cost to the Government. This estimate shall be based on the outcome of the most favorable set of circumstances. If this estimate is different from the most likely management EAC (Block 6.c.1), the assumptions, conditions, and methodology underlying the estimate shall be explained in Format 5. This estimate is for informational purposes only; it is not an official company estimate.

3.2.2.2. Management Estimate at Completion - Worst Case. Enter in Block 6.b.1 the contractor's worst case EAC. The worst case EAC reflects the highest expected cost to the Government. This estimate shall be based on the outcome of the least favorable set of circumstances. If this estimate is different from the most likely EAC (Block 6.c.1), the assumptions, conditions, and methodology underlying the estimate shall be explained in Format 5. This estimate is for informational purposes only; it is not an official company estimate.

3.2.2.3. Management Estimate at Completion - Most Likely. Enter in Block 6.c.1 the contractor's most likely EAC. This EAC is the contractor's official contract EAC and takes precedence over the estimates presented in Column (15) of Formats 1 and 2, and Blocks 6.a.1 and 6.b.1. The most likely EAC is the value that the contractor's management believes is the most possible outcome based on a knowledgeable estimation of all authorized work, known factored risks, and probable future conditions.

3.2.2.3.1. This value may not agree with the total of Column (15) (Block 8.e). Any difference shall be explained in Format 5 in terms of risk and opportunities and senior management knowledge of current or future contract conditions.

3.2.2.3.2. The most likely EAC need not agree with EACs contained in the contractor's internal data, but must be reconcilable to them. This EAC shall also be reconcilable to the contractor's latest statement of funds required as reported in the CFSR or its equivalent.

3.2.2.4. Contract Budget Base (CBB). Enter in Block 6.c.2 the total of negotiated cost (Block 5.b) and estimated cost of authorized, unpriced work (Block 5.c).

3.2.2.5.

Estimated Cost at Completion Variance. Enter in Block 6.c.3 the CBB (Block 6.c.2) minus the most likely management EAC (Block 6.c.1). This difference, if any, shall be explained in Format 5.

3.2.3.

Authorized Contractor Representative. Enter in Block 7.a the name of the authorized person (program manager or designee) approving the report. Enter that person's title in Block 7.b. The authorized IPMR signature approval shall be provided in Block 7.c. Enter the date of approval in Block 7.d. Digital signatures are required for the XML submission. Guidance for digital signatures are the PARCA EVM Web site at http://www.acq.osd.mil/evm/.

3.2.4.

Performance Data.

3.2.4.1.

Column (1) - Work Breakdown Structure Element. Enter in Column (1) of Block 8.a the description of the Work Breakdown Structure (WBS) elements against which cost information is being reported.

3.2.4.2.

Cost of Money (COM). Enter in Columns (2) through (16) of Block 8.b the Facilities Capital COM allocated to the contract.

Identify in Format 5 whether the value(s) entered for COM are add or non-add to the WBS elements. Add would mean the costs are not included in Block 8.a. Non-add would mean that costs have been included in Block 8.a. The Government may specify in the CDRL if the WBSs shall exclude COM.

3.2.4.3.

General and Administrative (G&A). Enter in Columns (2) through (16) of Block 8.c the appropriate G&A costs. Identify in Format 5 whether the value(s) entered for G&A are add or non-add to the WBS elements. Add would mean the costs are not included in Block 8.a. Non-add would mean that costs have been included in Block 8.a.

The Government may specify in the CDRL if the WBSs shall exclude G&A.

3.2.4.4.

Undistributed Budget (UB). Enter the amount of budget applicable to contract effort that has not yet been distributed to WBS elements at or below the reporting level. Budgets that have been distributed to WBS elements at or below the specified reporting level shall be included in the total budgets shown for the WBS elements in Block 8.a and shall not be shown as UB. UB characteristics:

Source: https://assist.dla.mil -- Downloaded: 2016-10-25T20:56Z Check the source to verify that this is the current version before use.

• UB is used to accommodate temporary situations where time constraints prevent adequate budget planning or where contract effort can only be defined in very general terms.

• UB shall not be used as a substitute for adequate contract planning. Budgets shall be allocated within the PMB to responsible organizations at the earliest possible time, preferably within the next reporting period.

• UB can never be negative. If a contractual de-scope change occurs and the effort has not been removed from time-phased PMB, the amount shall be discussed in Format 5. Discuss when the de-scope will be removed from the PMB and placed into UB.

Enter in Column (15) of Block 8.d the EAC for the scope of work represented by the UB in Column (14) of Block 8.d. Enter in Column

(16) of Block 8.d any variance. The content of UB and changes in the period shall be described in Format 5.

3.2.4.5. Subtotal (PMB). In Columns (2) through (16) of Blocks 8.a through 8.d, enter the sum of the costs and budgets for direct, indirect, COM, and G&A. This subtotal represents the dollars in the allocated budget (less management reserve (MR)), which is the PMB against which performance is measured.

3.2.4.6.

Management Reserve (MR). MR is an amount of the overall contract budget held for management control purposes and for unplanned events. MR characteristics:

• MR shall not be used to offset cost variances.

• MR shall never be a negative value (Column (14) of Block 8.f).

• If MR includes the contractor and subcontractor amounts together, the breakout shall be discussed in Format 5.

Enter in Column (14) of Block 8.f, the total amount of budget identified as MR as of the end of the current reporting period. The value shown as MR in Formats 1, 2, and 3 shall agree. Amounts from MR applied to WBS elements during the reporting period shall be listed in Block 6.b of Format 3 and explained in Format 5.

3.2.4.7. Total. Enter the sum of all direct, indirect, COM, G&A, UB and MR costs (as applicable) in Columns (2) through (14) of Block 8.g.

The Total lines of Format 1 (Block 8.g) and Format 2 (Block 5.g) shall agree. The total of Column (14), Block 8.g, shall equal the Total Allocated Budget (TAB) shown in Block 5.f on Format 3.

3.2.5.

Reconciliation to CBB.

3.2.5.1.

Formal Reprogramming. In exceptional cases, the contractor may…