Exhibit_A_CDRLs.pdf

For the best experience, open this PDF portfolio in

Acrobat X or Adobe Reader X, or later.

Get Adobe Reader Now!

http://www.adobe.com/go/reader

DD FORM 1423-1, FEB 2001

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:

TDP ________ TM _______ OTHER

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

G. PREPARED BY H. DATE I. APPROVED BY J. DATE

Page of Pages

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

INSTRUCTIONS FOR COMPLETING DD FORM 1423

(See DoD 5010.12-M for detailed instructions.)

FOR GOVERNMENT PERSONNEL

Item A. Self-explanatory.

Item B. Self-explanatory.

Item C. Mark (X) appropriate category: TDP - Technical Data Package;

TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.

Item D. Enter name of system/item being acquired that data will support.

Item E. Self-explanatory (to be filled in after contract award).

Item F. Self-explanatory (to be filled in after contract award).

Item G. Signature of preparer of CDRL.

Item H. Date CDRL was prepared.

Item I. Signature of CDRL approval authority.

Item J. Date CDRL was approved.

Item 1. See DoD FAR Supplement Subpart 4.71 for proper numbering.

Item 2. Enter title as it appears on data acquisition document cited in Item 4.

Item 3. Enter subtitle of data item for further definition of data item (optional entry).

Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.

Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).

Item 6. Enter technical office responsible for ensuring adequacy of the data item.

Item 7. Specify requirement for inspection/acceptance of the data item by the Government.

Item 8. Specify requirement for approval of a draft before preparation of the final data item.

Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).

Item 10. Specify number of times data items are to be delivered.

Item 11. Specify as-of date of data item, when applicable.

Item 12. Specify when first submittal is required.

Item 13. Specify when subsequent submittals are required, when applicable.

Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.

Item 15. Enter total number of draft/final copies to be delivered.

Item 16. Use for additional/clarifying information for Items 1 through 15.

Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14.; Desired medium for delivery of the data item.

FOR THE CONTRACTOR

Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.

a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.

Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.

b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.

Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.

c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.

Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and

d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.

Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.

Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.

These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data shall be governed by the pertinent provisions of the contract.

DD FORM 1423-1 (BACK), FEB 2001

data_item: A007 title: CONFERENCE AGENDA sub:

auth: DI-ADMN-81249B (see BLK 16) ref: SOW Para.C.3.4 req_ofc: NSWCCD, Code 808 dd250: N/A appcode: N/A dist: D* freq: ASREQ asof: N/A firstsub: See BLK 16 subsub: N/A addressee1: COR* draft1: 0 reg1: 1 repro1: 0 addressee2: Code 808, TA* draft2: 0 reg2: 1 repro2: 0 addressee3: PMS450 draft3: 0 reg3: 1 repro3: 0 addressee4: DCMA draft4: 0 reg4: 1 repro4: 0 addressee5:

draft5:

reg5:

repro5:

addressee6:

draft6:

reg6:

repro6:

addressee7:

draft7:

reg7:

repro7:

addressee8:

draft8:

reg8:

repro8:

addressee9:

draft9:

reg9:

repro9:

addressee10:

draft10:

reg10:

repro10:

addressee11:

draft11:

reg11:

repro11:

addressee12:

draft12:

reg12:

repro12:

addressee13:

draft13:

reg13:

repro13:

addressee14:

draft14:

reg14:

repro14:

addressee15:

draft15:

reg15:

repro15:

addressee16:

draft16:

reg16:

repro16:

addressee17:

draft17:

reg17:

repro17:

addressee18:

draft18:

reg18:

repro18:

addressee19:

draft19:

reg19:

repro19:

addressee20:

draft20:

reg20:

repro20:

addressee21:

draft21:

reg21:

repro21:

addressee22:

draft22:

reg22:

repro22:

addressee23:

draft23:

reg23:

repro23:

addressee24:

draft24:

reg24:

repro24:

addressee25:

draft25:

reg25:

repro25:

addressee26:

draft26:

reg26:

repro26:

addressee27:

draft27:

reg27:

repro27:

addressee28:

draft28:

reg28:

repro28:

addressee29:

draft29:

reg29:

repro29:

addressee30:

draft30:

reg30:

repro30:

addressee31:

draft31:

reg31:

repro31:

addressee32:

draft32:

reg32:

repro32:

addressee33:

draft33:

reg33:

repro33:

addressee34:

draft34:

reg34:

repro34:

addressee35:

draft35:

reg35:

repro35:

addressee36:

draft36:

reg36:

repro36:

addressee37:

draft37:

reg37:

repro37:

addressee38:

draft38:

reg38x:

repro38:

total_draft: 0 total_reg: 4 total_repro: 0 remarks: Blk 9: Distribution Statement D: Distribution authorized to Department of Defense and U.S. DoD contractors only ; Critical technology; (6/1/99). Other requests will be referred to NAVSEA Submarine Propulsor Technical Warrant Holder. Warning – This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. Sec. 2751, et seq.) or Executive Order 12470 as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate per the provisions of DOD Directive 5230.25. Destruction Notice – Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Blk 12: The first submission shall be made five working days prior to scheduled meeting date.

Blk 14: Distribution by electronic mail is preferred. Minutes shall be in electronic format using Microsoft Office product(s) or Portable Document Format (pdf) suitable for reproduction, with all fonts and images embedded within the document. Agenda shall be distributed via email to all parties identified in Block 14a.

group:

total_price:

prep_name: Michael Rubalsky, NSWCCD 808 line_item: TO BE DETERMINED exhibit: A xtdp: Off xtm: Off othercat: ADMIN system: VACL PROPULSOR TAILCONE ctr_no: N00167-20-R-0010 contr: TO BE DETERMINED remarksb:

Page2:

Reset:

2019-08-16T13:25:51-0400

RUBALSKY.MICHAEL.1286849381

prep_date: 08/16/2019 app_by: Yara Zidan, NSWCCD 808

2019-08-19T10:10:49-0400

ZIDAN.YARA.M.1543122412

app_date: 08/19/2019

Page: 7 of_pages: 9 app: Adobe Professional 8.0

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any data_item: A008 title: CONFERENCE MINUTES sub:

auth: DI-ADMN-81250B ref: SOW Para.C.3.4 req_ofc: NSWCCD,Code 808 dd250: N/A appcode: N/A dist: D* freq: ASREQ* asof: N/A firstsub: See BLK 16 subsub: N/A addressee1: COR* draft1: 0 reg1: 1 repro1: 0 addressee2: Code 808, TA* draft2: 0 reg2: 1 repro2: 0 addressee3: PMS450 draft3: 0 reg3: 1 repro3: 0 addressee4: DCMA draft4: 0 reg4: 1 repro4: 0 addressee5:

draft5:

reg5:

repro5:

addressee6:

draft6:

reg6:

repro6:

addressee7:

draft7:

reg7:

repro7:

addressee8:

draft8:

reg8:

repro8:

addressee9:

draft9:

reg9:

repro9:

addressee10:

draft10:

reg10:

repro10:

addressee11:

draft11:

reg11:

repro11:

addressee12:

draft12:

reg12:

repro12:

addressee13:

draft13:

reg13:

repro13:

addressee14:

draft14:

reg14:

repro14:

addressee15:

draft15:

reg15:

repro15:

addressee16:

draft16:

reg16:

repro16:

addressee17:

draft17:

reg17:

repro17:

addressee18:

draft18:

reg18:

repro18:

addressee19:

draft19:

reg19:

repro19:

addressee20:

draft20:

reg20:

repro20:

addressee21:

draft21:

reg21:

repro21:

addressee22:

draft22:

reg22:

repro22:

addressee23:

draft23:

reg23:

repro23:

addressee24:

draft24:

reg24:

repro24:

addressee25:

draft25:

reg25:

repro25:

addressee26:

draft26:

reg26:

repro26:

addressee27:

draft27:

reg27:

repro27:

addressee28:

draft28:

reg28:

repro28:

addressee29:

draft29:

reg29:

repro29:

addressee30:

draft30:

reg30:

repro30:

addressee31:

draft31:

reg31:

repro31:

addressee32:

draft32:

reg32:

repro32:

addressee33:

draft33:

reg33:

repro33:

addressee34:

draft34:

reg34:

repro34:

addressee35:

draft35:

reg35:

repro35:

addressee36:

draft36:

reg36:

repro36:

addressee37:

draft37:

reg37:

repro37:

addressee38:

draft38:

reg38x:

repro38:

total_draft: 0 total_reg: 4 total_repro: 0 remarks: Blk 9: Distribution Statement D: Distribution authorized to Department of Defense and U.S. DoD contractors only ; Critical technology; (6/1/99). Other requests will be referred to NAVSEA Submarine Propulsor Technical Warrant Holder. Warning – This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. Sec. 2751, et seq.) or Executive Order 12470 as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate per the provisions of DOD Directive 5230.25. Destruction Notice – Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Blk 12: The first submission shall be made five working days after completion of each meeting.

Blk 14: Distribution by electronic mail is preferred. Minutes shall be in electronic format using Microsoft Office product(s) or Portable Document Format (pdf) suitable for reproduction, with all fonts and images embedded within the document. Distributed via email to all parties identified in Block 14a.

group:

total_price:

prep_name: Michael Rubalsky, NSWCCD 808 line_item: TO BE DETERMINED exhibit: A xtdp: Off xtm: Off othercat: ADMIN system: VACL PROPULSOR TAILCONE ctr_no: N00167-20-R-0010 contr: TO BE DETERMINED remarksb:

Page2:

Reset:

2019-08-16T13:26:10-0400

RUBALSKY.MICHAEL.1286849381

prep_date: 08/16/2019 app_by: Yara Zidan, NSWCCD 808

2019-08-19T09:42:18-0400

ZIDAN.YARA.M.1543122412

app_date: 08/19/2019

Page: 8 of_pages: 9 app: Adobe Professional 8.0

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any data_item: A009 title: REQUEST FOR VARIANCE sub:

auth: DI-SESS-80640D* (see BLK 16) ref: SOW Para.C.3.5 req_ofc: NSWCCD, Code 808 dd250: SS appcode: A dist: D* freq: ASREQ* asof: N/A firstsub: See BLK 16 subsub: ASREQ* addressee1: VACCS* draft1: 1 reg1: 1 repro1: 0 addressee2:

draft2:

reg2:

repro2:

addressee3:

draft3:

reg3:

repro3:

addressee4:

draft4:

reg4:

repro4:

addressee5:

draft5:

reg5:

repro5:

addressee6:

draft6:

reg6:

repro6:

addressee7:

draft7:

reg7:

repro7:

addressee8:

draft8:

reg8:

repro8:

addressee9:

draft9:

reg9:

repro9:

addressee10:

draft10:

reg10:

repro10:

addressee11:

draft11:

reg11:

repro11:

addressee12:

draft12:

reg12:

repro12:

addressee13:

draft13:

reg13:

repro13:

addressee14:

draft14:

reg14:

repro14:

addressee15:

draft15:

reg15:

repro15:

addressee16:

draft16:

reg16:

repro16:

addressee17:

draft17:

reg17:

repro17:

addressee18:

draft18:

reg18:

repro18:

addressee19:

draft19:

reg19:

repro19:

addressee20:

draft20:

reg20:

repro20:

addressee21:

draft21:

reg21:

repro21:

addressee22:

draft22:

reg22:

repro22:

addressee23:

draft23:

reg23:

repro23:

addressee24:

draft24:

reg24:

repro24:

addressee25:

draft25:

reg25:

repro25:

addressee26:

draft26:

reg26:

repro26:

addressee27:

draft27:

reg27:

repro27:

addressee28:

draft28:

reg28:

repro28:

addressee29:

draft29:

reg29:

repro29:

addressee30:

draft30:

reg30:

repro30:

addressee31:

draft31:

reg31:

repro31:

addressee32:

draft32:

reg32:

repro32:

addressee33:

draft33:

reg33:

repro33:

addressee34:

draft34:

reg34:

repro34:

addressee35:

draft35:

reg35:

repro35:

addressee36:

draft36:

reg36:

repro36:

addressee37:

draft37:

reg37:

repro37:

addressee38:

draft38:

reg38x:

repro38:

total_draft: 1 total_reg: 1 total_repro: 0 remarks: Blk 4: A Request for Variance is used to obtain authorization to deliver non-conforming material which does not meet the prescribed configuration documentation but is suitable for use as-is or after repair (previously known as deviations or waivers). All variance requests shall specify operational, technical and fit-up impacts if product is delivered in in this configuration. All requests for variance shall be via the VIRGINIA Class Configuration Control System (VACCS).

Blk 8: Formal approval of content required. Draft to be submitted NLT 5 days after identification of issue. Allow 7 days for government review of each submittal (initial or after comments incorporated). Approval based upon meeting contractual drawing requirements and specifications. Approval by government shall be in writing. If comments are provided by the government, the contractor is allowed 7 days for comment adjudication.

Blk 9: This document contains information exempt from mandatory disclosure under the FOIA. Distribution Statement D: Distribution authorized to Department of Defense and U.S. DoD contractors only; Critical technology; (6/1/99). Other requests will be referred to NAVSEA Submarine Propulsor Technical Warrant Holder. Warning – This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. Sec. 2751, et seq.) or Executive Order 12470 as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate per the provisions of DOD Directive 5230.25. Destruction Notice – Destroy by any method that will prevent disclosure of contents or reconstruction of the document.

Blk 12: NLT 10 days after the need for a Deviation/Waiver is identified.

Blk14: Initial submission for approval shall be in accordance with Blk 14. A combined final report containing all approved Requests for Variances that are applicable to a CLIN shall be submitted NLT 30 days after completion of all deliveries under that CLIN being delivered.

group:

total_price:

prep_name: Michael Rubalsky, NSWCCD 808 line_item: TO BE DETERMINED exhibit: A xtdp: Off xtm: Off othercat: SESS system: VACL PROPULSOR TAILCONE ctr_no: N00167-20-R-0010 contr: TO BE DETERMINED remarksb:

Page2:

Reset:

2019-08-16T13:26:36-0400

RUBALSKY.MICHAEL.1286849381

prep_date: 08/16/2019 app_by: Yara Zidan, NSWCCD 808

2019-08-19T10:04:41-0400

ZIDAN.YARA.M.1543122412

app_date: 08/19/2019

Page: 9 of_pages: 9 app: Adobe Professional 8.0

DATA ITEM DESCRIPTION

Title: CONFERENCE AGENDA

Number: DI-ADMN-81249B Approved Date: 20160524

AMSC Number: F9658 Limitation:

DTIC Applicable: GIDEP Applicable:

Preparing Activity: 11 (AFLCMC/EZSC) Project Number: ADMN-2015-002

Applicable Forms: None

Use/Relationship: The Conference Agenda provides information concerning purpose, location, and schedule of conferences required to manage the acquisition of systems equipment, related items, and services.

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

b. This DID supersedes DI-ADMN-81249A.

Requirements:

1. Reference documents. None.

2. Format. Contractor format is acceptable.

3. Content. The agenda shall include the following, where applicable:

a. The purpose and objective of the conference.

b. The conference location, date, and duration.

c. A daily chronological listing of each major topic or subtopic to be discussed and the time to be devoted to each topic.

d. A list of activities to be represented and identification of their responsibilities.

e. A list of subcommittees to be established during the conference and the proposed activity representation for each subcommittee.

f. Reference to and brief description of the results of previous meetings, when relevant.

g. Location, schedule, and purpose or subject area to be covered by each subcommittee, when applicable.

h. Names of the conference chairperson, co-chair, and subcommittee chairs, when

i. Information on billeting, messing, transportation, and administrative services available to conference attendees.

j. Complete list of all documentation to be available for review.

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

Source: http://assist.dla.mil -- Downloaded: 2019-08-19T14:12Z Check the source to verify that this is the current version before use.

DI-ADMN-81249B

k. Brief description of progress on actions or problems identified at previous meetings, when

l. Other pertinent information such as Forms to be used, identification of any deviations or waivers, security classification, and clearance requirements.

End of DI- ADMN-81249B

Source: http://assist.dla.mil -- Downloaded: 2019-08-19T14:12Z

Title: CONFERENCE MINUTES

Number: DI-ADMN-81250B Approved Date: 20160524

AMSC Number: F9659 Limitation:

DTIC Applicable: GIDEP Applicable:

Preparing Activity: 11 (AFLCMC/EZSC) Project Number: ADMN-2015-001

Applicable Forms:

Use/Relationship: Conference minutes provide documentation of technical information provided and decisions and agreements reached at meetings.

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

b. This DID supersedes DI-ADMN-81250A.

Requirements:

1. Reference documents: None.

2. Format. Contractor format is acceptable.

3. Content. The minutes shall include the following information:

a. A title page containing the following:

(1) Title – type of meeting and date.

(2) Identification of the acquisition (system, equipment, contract number) for which the meeting was held.

(3) Space for signatures of the designated representatives of the contractor and acquisition activity.

(4) The name of the contractor and address to which the acquisition activity should acknowledge receipt of comments.

b. The purpose and objective of the conference.

c. The conference location.

d. A summary of the discussions, decisions, agreements reached, and directions of the conference or individual subcommittees thereof.

e. A list of attendees by name, rank, grade or position, activity represented, activity symbol/code, phone numbers, and emails, as appropriate.

f. Action items resulting from the conference.

g. Briefing charts, if presented, shall be attached to the minutes for information only.

End of DI- ADMN-81250B

DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.

Source: http://assist.dla.mil -- Downloaded: 2019-08-19T12:40Z

Source: http://assist.dla.mil -- Downloaded: 2019-08-19T15:08Z

Source: http://assist.dla.mil -- Downloaded: 2019-08-19T15:08Z

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: http://assist.dla.mil -- Downloaded: 2019-08-19T15:14Z

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.

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

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:

• 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 establish a PMB with budgets that exceed the CBB. This is called an OTB. Acceptance of the OTB values in excess of the CBB will be predicated on Government approval. This process is called formal reprogramming. The contractor and the Government shall agree on how the results of formal reprogramming shall be reported in the IPMR before it is initiated. Blocks 9.a and 9.b are used to reconcile the increased budget values to the CBB. Any pertinent details on the reporting of the formal reprogramming shall be included in Format 5.

3.2.5.2. Variance Adjustment. If the contractor uses a portion of the additional budget to adjust or eliminate variances applicable to completed work, the total adjustments made to the cost and schedule variances shall be shown in Columns (10) and (11) of Block 9.a.

• The total schedule variance adjustment entered in Column (10) of Block 9.a shall be the sum of the individual schedule variance adjustments shown in Column (12b) of Block 8.g.

• The total cost variance adjustment entered in Column (11) of Block 9.a shall be the sum of the individual cost variance adjustments shown in Column (12a) of Block 8.g.

Values identified in Block 9.a represent cumulative adjustment for all past reprogramming adjustments, including the most recent reprogramming.

3.2.5.3. Total Contract Variance. In Columns (10) and (11) of Block 9.b, enter the sum of the cost and schedule variances shown on the Total line (Block 8.g) and on the Variance Adjustment line (Block 9.a). In Column (14) enter the CBB from Block 6.c.2. In Column (15) enter the most likely management EAC from Block 6.c.1. In Column (16) of Block 9.b enter the difference between Columns (14) and (15) of Block 9.b.

3.2.6.

Performance Data Columns (2) through (16).

3.2.6.1.

Column (2) and Column (7) - Budgeted Cost - Work Scheduled.

For the report period noted, enter the BCWS in these columns.

3.2.6.2.

Column (3) and Column (8) - Budgeted Cost - Work Performed.

For the report period noted, enter the BCWP in these columns.

3.2.6.3.

Column (4) and Column (9) - Actual Cost - Work Performed. For the report period noted, enter the ACWP in these columns without regard to ceiling. In all cases, costs and budgets shall be reported on a comparable basis.

3.2.6.4.

Column (5) and Column (10) - Variance – Schedule. For the report period, these columns shall reflect the differences between BCWS and BCWP.

• For the current period column, Column (5) (Schedule Variance) is derived by subtracting Column (2) (BCWS) from Column (3) (BCWP).

• For the cumulative to date column, Column (10) (Schedule Variance) is derived by subtracting Column (7) (BCWS) from Column

(8) (BCWP).

A positive number in Column (5) and Column (10) indicates a favorable variance. A negative number indicates an unfavorable variance.

3.2.6.5. Column (6) and Column (11) - Variance - Cost. For the report period, these columns shall reflect the difference between BCWP and

ACWP.

• For the current period column, Column (6) (Cost Variance) is derived by subtracting Column (4) (ACWP) from Column (3) (BCWP).

• For the cumulative to date column, Column (11) (Cost Variance) is derived by subtracting Column (9) (ACWP) from Column (8) (BCWP).

A positive value indicates a favorable variance. A negative value indicates an unfavorable variance.

3.2.6.6. Column (12a) and Column (12b) Reprogramming Adjustments - Cost Variance and Schedule Variance. Formal reprogramming (OTB) can result in budget allocations in excess of the CBB and, in some instances, adjustments to previously reported variances. If previously reported variances are being adjusted, the adjustment applicable to each reporting line item affected shall be entered in Column (12a) for cost variances and Column (12b) for schedule variances. The total of Column (12a) and Column (12b) shall equal the amount shown on the Variance Adjustment line (Block 9.a) in Column (10) and Column (11).

3.2.6.7.

Column (13) Reprogramming Adjustments - Budget. Enter the total amounts added to the budget, for each reporting line item, as the result of formal reprogramming (OTB). The amounts shall consist of the sum of the budgets used to adjust cost variances (Column (12)) plus the additional budget added to the WBS element for remaining work. Enter the amount of budget added to MR in the space provided on the MR line (Block 8.f of Column (13)).