ATTACHMENT_1-DATA_ITEM_DESCPRIPTIONS.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

DATA ITEM DESCRIPTION

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: https://assist.dla.mil -- Downloaded: 2016-06-13T19:02Z Check the source to verify that this is the current version before use.

Title: ENVIRONMENTAL STRESS SCREENING (ESS) REPORT

Number: DI-ENVR-81663 Approval Date: 20060511 AMSC Number: N7565 Limitation:

DTIC Applicable: GIDEP Applicable:

Office of Primary Responsibility: N/PEO IWS 1.0 Applicable Forms: N/A

Use/Relationship: The Environmental Stress Screening (ESS) Report is a formal record of the contractor’s environmental stress screening results. This report is used by the procuring activity to evaluate the effectiveness of the contractor’s ESS program and monitor ESS results.

This Data Item Description (DID) contains the format, content, and preparation instructions for the data product resulting from the work task specified in the contract.

1.0 Format. The ESS report shall be in contractor’s format.

2.0 Content. The ESS report shall contain the following sections:

2.1 Random Vibration. This section shall contain the following:

a. Report period.

b. Equipment nomenclature.

c. Equipment part number.

d. Subassembly part number (if ESS is performed at the subassembly level).

e. Date of the vibration screen.

f. Serial number of the unit(s) subjected to vibration screen.

g. Axis of vibration.

h. Time at the start of vibration.

i. Time when vibration stopped.

j. Duration of the vibration screen.

k. Elapsed time from the start of the vibration screen to each failure (if applicable).

l. Failed component (circuit card, module or assembly).

m. Part number or name of failed part.

n. Reference designation of failed part.

o. Failure mode of failed part.

p. Cause of failure of part.

q. Corrective action required, taken or planned.

r. Analysis of results to determine screening effectiveness.

s. Any recommended changes to the ESS procedures or program.

Source: http://assist.dla.mil -- Downloaded: 2020-11-17T16:50Z

DI-ENVR- 81663 (Continued)

Temperature Cycling. This section shall contain the following:

a. Report period.

b. Equipment nomenclature.

c. Equipment part number.

d. Subassembly part number (if ESS is performed at the subassembly level).

e. Date and time of temperature cycling (at the start of each cycle).

f. Serial number of the unit(s) subjected to temperature cycling.

g. Elapsed time from start of temperature cycling to each failure (if applicable).

h. Number of the cycle during which each failure occurred.

i. Indication of point in cycle when failure occurred (hot or cold).

j. Failed component (circuit card, module or assembly).

k. Part number or name of failed part.

l. Reference designation of failed part.

m. Failure mode of failed part.

n. Cause of failure of part.

o. Corrective action required, taken or planned.

p. Analysis of results to determine screening effectiveness.

q. Any recommended changes to the ESS procedures or program.

2.2 Laboratory Equipment Data. This section shall contain the following:

a. Random Vibration Equipment:

1) Identification by model number and manufacturer of equipment in the vibration system.

2) Photographs of mounting fixture and mounting arrangement for each item to be vibrated. The photographs must include enough detail to show mounting arrangements and accelerometer locations.

3) A plot of the actual random vibration spectrum recorded during vibration and used for control purposes, identifying frequencies, power and spectral density, and degrees of freedom (or actual filter bandwidths used in the analyses of the spectrum).

4) Description of procedure used to perform the vibration.

b. Temperature Cycling Equipment:

1) Identification by model number and manufacturer of the temperature chamber.

2) Maximum and minimum temperatures.

3) Maximum and minimum rate of change of temperature.

4) Description of procedure used to perform the temperature cycling.

3.0 End of DI-ENVR-81663.

Source: http://assist.dla.mil -- Downloaded: 2020-11-17T16:50Z

Source: https://assist.dla.mil -- Downloaded: 2018-02-06T15:31Z

Source: https://assist.dla.mil -- Downloaded: 2018-02-06T15:31Z

Title: CONFERENCE AGENDA

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

AMSC Number: F9658 Limitation:

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.

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

1. Reference documents. None.

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 applicable.

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

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

Source: https://assist.dla.mil -- Downloaded: 2016-06-13T19:01Z

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: https://assist.dla.mil -- Downloaded: 2016-06-13T19:01Z

Title: CONFERENCE MINUTES

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

AMSC Number: F9659 Limitation:

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.

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

1. Reference documents: None.

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

Source: https://assist.dla.mil -- Downloaded: 2016-06-13T19:02Z

DATA ITEM DESCRIPTION I Form Approved OMB No.0704.0188

1.nTLE 2.IOENTIFICATIONNUMBER

TEST/ INSPECTION REPORT DI-NM’I-80809B

L OESCRIPTlOtVPURPOSE

3.1 The testl inspection report is used to document testl inspection results, findings, and analyses that will enable the government or contracting agency to evaluate compliance with system requirements, performance objectives, specifications, and test linspection plans.

1.APPROVALDATE 5.OFFICEOFPRIMARYRESPONSIBILITY(OPB) Ea.DTICAPPLICABLE 6b.CWIEP AppliCable

(YVMMOD)

F/AFMC-DCJP

970124

,.APPLlCAT\0NflNTER7iElAT10NSH1P

7.1 This data item description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement

I as delineated in the contract.

I

7.2 This DID is applicable to engineering (developmental ), preliminary qualification, qualification, and acceptance testing.

7.3 This DID supersedes DI-NDTI-80809A and DI-MISC-80653

1.APPROVALLIMITATION 9a.APPLICABLEFORMS 9b.AMSCNUMBER

F7231

10,PREPARATIONlNSTRUCnONS

10.1 Format. Contractor format is acceptable.

paragraph 10.2 and its subparagraphs in a manner understanding

10.2 CQnL!aL. The test/inspection report shall

Organize the information required by that facilitates presentation and contain the following information, as

10. 2.1 Cove. and tile uaae. The following information shall appear on the outside front :over and title page:

a. Report date.

b. Report number (contractor or government)

Contractor’ s name, address, and commercia 1 and government entity code.

Contract number and contract line item number or sequence number (if applicable)

e. ‘fvpe of test/inspection (for example. first article acceptance test, aualitv con formanc-e-inspection, d-evelopmental test-, qualification test, f Identification of item tested/inspected.

9. Date or period of test/inspection.

h. Name and address of requiring government activity.

i. Security classification, downgrading and declassifying environmental Lest) .“ information, if applicable.

(Continued on page 2 )

1.DIS77UBUTIONSTATEMEW

DISTRIBUTION STATEMRNT A : APPROVED FOR PUBLIC RELBASE; DISTRIBUTION IS UNLIMITED.

ID Form 1664,APR 89 PreviOLIsedtliomwe obsdem. Page 1 of & Pages 39123

DI-NDTI-80809B

Block 10, Preparation Instructions (continued)

10.2.2 ~. The table of contents shall identify the following:

a. The title and starting page of each major section, paragraph, and apPendix of the report.

b. The page, identifying number, and title of each illustration (for example; figure, table, photograph, chart, and drawing)

10 .2.3 -ductim. The introduction shall include the following information:

10.2 .3.1 obyectlve W. The specific test/ inspection objective (s) as specified in the contract tasking document.

10. 2.3.2 L.temls) tes~. Complete identification of the item(s) testedl inspected including the following:

a. Nomenclature.

b. National stock number.

Model number, part number t and serial number :: Type of item (for example, prototype, production item, laboratory model )

e. Serial or lot number.

f. Applicable engineering changes

9. Production item specification, if applicable.

h. Date of manufacture.

10.2 .3.3 Complete inspection requirements correlated to contractual

Required testl inspection parameters :: Performance requirements, acceptance or environmental criteria.

10.2.4 ~. Complete test/inspection report identification of the testl requirements including the compliance limits, and summary including the

a. A brief discussion of the significant test/inspection results, ObSerVati Qns, conclusions, and recommendations covered in greater detail elsewhere in the report.

b. Proposed corrective actions and schedules for failures or problems encountered.

c. Identification of deviations, departures, or limitations encountered, referenced to the contract requirements.

d. Tables, graphs, illustrations, or charts as appropriate to simplify the summary data.

10.2.5 ~. Complete identification of all documents referenced in the test finspection report including the following, as applicable:

a. Prior testf inspection reports on the same item.

b. Test /inspection plans and procedure documents

c. Prior certifications of compliance.

d. Contractor’ s file designation where test/ inspection records are maintained.

e. Input parameters used.

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

Page 2 of 4 Pages

10.2.6 ~. The body of the testlinspection report shall be as follows :

10 .2.6.1 KzZL_ + de.tlflca~.

Complete identification of each item of test equipment used in the testlinspection including the following:

a.

b.

c.

d.

e.

f.

9.

10. 2.6.2

Nomenclature.

Model number.

Serial number.

Manufacturer.

Calibration status.

Accuracy data.

Comments, if applicable.

Testlinmection kuhtv mstd.b&mn and set–w. Complete description of the physical set-up used in conducting the test/inspection to include the following:

a. Location or orientation of the item.

b. Location. orientation, or settinm of test equipment and instrumentation.

c. Location, orientation, or settings of sensors and probes

d. Location or orientation of interconnections, cables, and hoop-ups.

e. Electrical power, pneumatic, fluidic, and hydraulic requirements.

Drawings, illustrations, and photographs maY be used for clarification.

10 .2.6.3 wrocedur~. Complete description of the procedures used in conducting the test/inspection to include the following:

a. Item selection and inspection that verified suitability for test/ inspection.

b. Summarized sequence of testing/inspection steps, including a description of how the item was operated during the test/inspection, and any control conditions imposed.

10 .2.6.4 A copy of all testlinspection results and analysis to include the following:

10.2.6 .4.1 ~. The actual recorded data (for example, log book entries, oscillographs, instrument readings, plotter graphs) If the recorded data is extensive, provide it in an appendix.

10. 2.6.4.2 Test/ insQec!iion resu. Identification of all testlinspection results to include the following:

a. Matrices comparing results achieved against test/inspection objectives or requirements

b. A discussion of these matrices as to their significance, and how they compare to any prior testlinspections.

Calculation examples.

;; Discussion of anomalies, deviations, discrepancies, or failures, including their impact, causes, and proposed corrective actions The discussion shall address discrepancies between design requirements and the tested/inspected Configuration.

10. 2.6.5 Conclusicxls Test/ inspection conclusions distinguished between objective and subjective to include the following:

a. The effectiveness of the testlinspection procedures in measuring item performance.

Page 3 of 4 Pages

b. The success or failure of the item to meet required test/inspection objectives.

c. The need for repeat, additional, or alternative tests linspections.

d. The need for item redesign or further development.

e. The need for improved test/inspection procedures, techniques, or facilities.

f. The adequacy and completeness of the test/inspection requirements.

10.2 .6.6 Recommendations appropriate to the test/inspection results and conclusions including the following:

a b.

c.

d.

e.

f.

9.

h.

Acceptability of the item tested/inspected (pass or fail) Additional testing/inspection required. ,.

Redesign required.

Problem resolution.

Test/inspection procedure or facility improvements Disposition of items tested/inspected.

Documentation changes required.

Testing/ inspection improvements

10.2.7 The following certifications shall be included, .as

applicable:

10.2 .7.1 A statement that the testlinspection was performed in accordance with applicable testlinspection plans and procedures, and that the results are true and accurate. The authentication shall include the signature of the contractor personnel that performed the test(s) /inspection(s) , a contractor representative authorized to make such certification, and any government witnesses

10.2 .7.2 A statement identifying those requirements not tested/inspected or measured that were previously validated.

Include identification of the data and method employed for such validation (for example, prior test/inspection, analytical verification, equivalent item, and so on) The authentication shall include the signature of a contractor representative authorized to make such authentication and any government witness.

10.2 .7.3 A statement that the item tested/ inspected either passed or failed item acceptability requirements This authentication shall include the signature of a contractor representative authorized to make such authentication and any government witness

10.2.8 Appendices shall be used to append detailed

test/inspection daia, drawings, photographs , or other documentation too voluminous to include in the main body of the report This includes referenced documentation not previously provided by the government, and test/ inspection reports from any associated test/inspection activity that may have performed some of the testing/inspecting requirements.

Page 4 of 4 Pages

Title: Integrated Program Management Data and Analysis Report (IPMDAR) Number: DI-MGMT-81861B Approval Date: 20200312 AMSC Number: 10165 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: OUSD (A&S) AAP (PARCA) Project Number: MGMT-2019-032

APPLICABLE FORMS: N/A

1. USE/RELATIONSHIP:

1.1 The Integrated Program Management Data and Analysis Report (IPMDAR) contains data for measuring contract execution progress on Department of Defense (DoD) acquisition contracts.

The IPMDAR's primary purpose to the Government is to reflect current contract performance status and the forecast of future contract performance. This Data Item Description (DID) contains the format, content requirements, and intended use of information for the data deliverable resulting from the work task described in the solicitation.

1.2 The IPMDAR consists of the following three components:

1.2.1 Contract Performance Dataset (CPD). Provides performance/execution data from the contractor’s existing management systems.

1.2.2 Schedule (Comprised of both the Native Schedule File and the Schedule Performance Dataset

(SPD)). Provides data from the contractor’s Integrated Master Schedule (IMS).

1.2.3 Performance Narrative Report (Comprised of both the Executive Summary and the Detailed

Analysis Report). Provides narrative analysis of data provided in the CPD and the Schedule.

1.3 IPMDAR Outline.

1.3.1 Data reported shall reflect all negotiated contract work and include the total scope of

Authorized Unpriced Work (AUW) efforts.

1.3.2 Data reported shall reflect the output of the contractor's Earned Value Management System

(EVMS).

1.3.3 Data reported in the CPD, Schedule, and Performance Narrative Report shall be as of the same reporting period.

1.4 Direct Reporting Contractor Role.

1.4.1 A Direct Reporting Contractor is any contractor required to provide the IPMDAR directly to the

Government. This includes prime contractors, subcontractors, intra-government work agreements, and other agreements, based on the contract type, value, duration, nature of the work scope, and the criticality of the information. In this document, instances of “Contractor” are synonymous with “Direct Reporting Contractor.” 1

1 In the event that the Direct Reporting Contractor is a contractor other than the prime, the Direct Reporting Contractor will additionally report to the prime. Subcontractor data shall be provided to the prime in a manner that supports the contractor’s submission to the Government.

Source: http://assist.dla.mil -- Downloaded: 2020-11-18T15:55Z

DI-MGMT-81861B

1.5 Data Repository. The Office of the Under Secretary of Defense (OUSD) Acquisition, Analytics and Policy (AAP) Earned Value Management (EVM) Division maintains a secure website, the Earned Value Management Central Repository (EVM-CR)2, for all unclassified, proprietary and non-proprietary data from programs and contracts that have EVM reporting requirements, regardless of a program’s Acquisition Category (ACAT) designation or a contract’s value. The EVM-CR is housed on an unclassified computer system designed to control sensitive and proprietary contractor data. The system will accept only unclassified data including contracts with EVM data that are marked as For Official Use Only (FOUO), Business Sensitive, and/or Proprietary. No classified material shall be provided to the EVM-CR. Refer to DoD Manual 5200.01 Volume 4 for information regarding designation and marking of Controlled Unclassified Information (CUI).

1.6 Electronic Submission and Files. Refer to the AAP EVM Website and the IPMDAR Implementation Guide for information about electronic data submission format requirements as defined in the File Format Specifications (FFS) and Data Exchange Instructions (DEI).3

1.6.1 The CPD shall be formatted in accordance with the applicable DoD-approved FFS and DEI.4

1.6.1.1 Historical Contract Performance Data. This refers to a CPD delivery with time phased historical data from contract award. The Government may request Historical Contract Performance Data in place of the normally provided CPD, typically no more than annually (specific encoding definitions of Historical Contract Performance Data can be found in the FFS and DEI).

1.6.2 The Schedule shall be provided electronically as follows:

1.6.2.1 The Schedule Performance Dataset (SPD) in accordance with the applicable DoD-approved FFS and DEI.

1.6.2.2 The Native Schedule File consistent with the contractor’s schedule tool (e.g., MPP, XER). The

Data Dictionary shall be included as part of the contractor’s Native Schedule File, or in a human-readable file format (e.g., PDF, XLSX, DOCX), containing searchable text, in accordance with the contractor’s internal system description.

1.6.3 The Performance Narrative Report (Executive Summary and Detailed Analysis) shall be provided electronically in the contractor’s human-readable file structure (e.g., DOCX, PDF), containing searchable text.

1.7 Signatures. The contractor’s program manager or designee shall sign the final Performance Narrative Report or a separate signature page to note the completion of the data submission. This signature confirms the information reported in all of the provided components is authoritative and used by the contractor to manage the program. Electronic signatures are acceptable.

1.7.1 Proprietary Disclosure Statement. A company proprietary disclosure statement is required and shall be provided as part of the Performance Narrative Report submission or separate signature page and shall be notated in the CPD and SPD files. (Refer to CPD FFS 2.2.2 and SPD FFS 2.2.1)

1.8 Delivery Timing.

1.8.1 Monthly Submission Requirement. IPMDAR data shall be required at least monthly. The reporting frequency shall be specified in the Contract Data Requirements List (CDRL). All reports shall reflect data from the same accounting period and shall be provided at any time after the

2 https://www.acq.osd.mil/evm/ 3 Conversion utilities and tools can be found at: https://www.acq.osd.mil/evm/ 4 https://www.acq.osd.mil/evm/ close of the contractor’s accounting period, but no later than sixteen (16) business days after the contractor’s accounting period end date.

1.8.1.1 Incremental Delivery. Reports may be provided incrementally, including preliminary data, with the number of days for delivery of each submittal tailored in the CDRL. Data delivered is not considered authoritative until the final submission and signature. The recommended incremental delivery process is the Schedule, followed by the CPD and the Executive Summary, Government review of submittals, Government directed Detailed Analysis, Contractor Detailed Analysis delivery and all final data.5

1.9 This DID supersedes DI-MGMT-81861A.

2. DOCUMENT REQUIREMENTS:

2.1 Data Submission. The IPMDAR shall be provided to the OUSD AAP EVM Division EVM-CR. The

EVM-CR will only accept unclassified, proprietary and non-proprietary data from programs and contracts that have EVM reporting requirements, regardless of a program’s Acquisition Category (ACAT) designation or a contract’s value.

2.2 Common Heading Information. This section shall provide information for metadata fields that are common across the datasets. (Refer to CPD FFS 2.2.2 and SPD FFS 2.2.1)

2.2.1 Contractor. Provide the reporting contractor’s name, division (if applicable), facility location, mailing address, and Commercial and Government Entity (CAGE) or Data Universal Numbering System (DUNS) code.

2.2.2 Contract. Provide the contract name (e.g., Low Rate Initial Production (LRIP) Lots 1-4), contract number, contract type, and applicable effort name (e.g., LRIP 1, Contract Line Item Number 1, Task 1). Effort name shall refer to the subdivision of reporting below the contract level.

2.2.3 Program. Provide the program name, or enter the type, model, and series or other military designation of the prime item or items purchased on the contract. The program phase (e.g., development, production) shall also be provided.

2.2.4 Report Period. Identify the current period covered by the reported data.

2.3 Contract Performance Dataset (CPD). This section shall include the following:

2.3.1 Heading Information. This section shall provide information for metadata fields that are resident in the CPD. All values provided in the Heading Information shall be reported in dollars, and shall include the following: (Refer to CPD FFS 2.2.4)

2.3.1.1 Negotiated Contract Cost (NCC). Provide the NCC, which is defined as the cost negotiated in a cost-plus-fixed-fee contract or the negotiated contract target cost in either a fixed-price-incentive contract or a cost-plus-incentive-fee contract. The NCC shall not contain profit or fee, the estimated value of undefinitized change orders (known as AUW), or cost growth (overrun) above the original estimated cost.

2.3.1.2 Estimated Cost of AUW. Provide the total dollar value (excluding fee or profit) of the approved work scope associated with AUW, which is a contract scope change that is directed by the Government contracting officer, but has not yet been fully negotiated/definitized.

2.3.1.3 Target Fee. Provide the applicable fee that applies to the NCC.

5 Reference the IPMDAR Implementation Guide for an example of the incremental delivery timeline.

2.3.1.4 Target Price. Provide the target price (NCC plus target fee) applicable to the definitized contract effort.

2.3.1.5 Estimated Price. Provide the estimated final contract price. The estimated price shall be based on the contractor’s Most Likely Estimate at Completion (EAC) for all authorized work, including: the appropriate fee, incentive, and cost sharing provisions.6

2.3.1.6 Contract Ceiling. Provide the contract ceiling price applicable to the definitized effort. This is only applicable to contracts with a ceiling.

2.3.1.7 Estimated Contract Ceiling. Provide the estimated ceiling price applicable to all authorized contractual efforts including both definitized and undefinitized efforts. This is only applicable to contracts with a ceiling.

2.3.1.8 Program Management EACs. These values represent the contractor program manager's EACs that may differ from Performance Measurement Baseline (PMB) EAC provided in 2.2.2.2.4.1 due to timing and executive insight.

2.3.1.8.1 Best Case EAC. Provide the contractor program manager’s Best Case EAC, defined as the best case scenario for the estimate of costs to complete all work from a point in time to the end of the program.

2.3.1.8.2 Worst Case EAC. Provide the contractor program manager’s Worst Case EAC, defined as the worst case scenario for the estimate of costs to complete all work from a point in time to the end of the program.

2.3.1.8.3 Most Likely EAC. Provide the contractor program manager’s Most Likely EAC, defined as the value that the contractor’s management believes is the most possible outcome based upon the estimate of costs to complete all work from a point in time to the end of the program.

2.3.1.9 Original NCC. Provide the dollar value (excluding fee) negotiated in the original contract.

2.3.1.10 Contract Budget Base (CBB). Provide the CBB. The CBB shall be defined as the total amount of performance measurement budget that is allocated to contract work and is the sum of 2.2.1.1, NCC, and 2.2.1.2, Estimated Cost of AUW.

2.3.1.11 Total Allocated Budget (TAB). Provide the sum of all budgets allocated to the performance of the contractual effort (includes direct, indirect, undistributed budget (UB), management reserve (MR), and over target baseline (OTB)).

2.3.1.12 Contract Start Date. Provide the date the contractor was authorized to start work on the contract, regardless of the date of contract definitization.

2.3.1.13 Contract Definitization Date. Provide the date the contract was originally definitized. If the contract is not definitized, the contract definitization date shall be left blank.

2.3.1.14 Baseline Completion Date (previously known as Planned Completion Date). Provide the completion date for which the budgets allocated in the Performance Measurement Baseline (PMB) have been planned. This date represents the planned completion of all efforts on the contract and shall reflect the time to complete the work scope.

2.3.1.15 Contract Completion Date. Provide the contract completion date in accordance with the latest contract modification.

6 This number shall reconcile with the estimated price in the Contract Funds Status Report (CFSR), as applicable.

2.3.1.16 Forecast Completion Date (previously known as Estimated Completion Date). Provide the contractor program manager’s latest forecast completion date. This date represents the projected completion of all effort on the contract, consistent with the Schedule forecast completion date. This date shall be consistent with the Most Likely EAC.

2.3.1.17 Over Target Baseline/Over Target Schedule (OTB/OTS) Date. Provide the date that all reprogramming adjustments were completed, if applicable.

2.3.1.18 Calculated Values. The following values are calculated and are not reported separately.

2.3.1.18.1 Negotiated Contract Changes. Provide the total cost (excluding fee) of all definitized contract changes which shall be defined as changes that have occurred since definitization of the original contract and is the difference between 2.2.1.1 (NCC) and 2.2.1.9 (Original NCC).

2.3.2 Performance Data. The data provided in the CPD shall be reported in both dollars and hours.

2.3.2.1 Structures. The following items shall be represented in the CPD structures. These structures are encoded as tables as described in the DEI.

2.3.2.1.1 Work Breakdown Structure (WBS). Provide the contractor’s WBS. (Refer to CPD FFS 2.2.10)

2.3.2.1.2 Organizational Structure. Provide the organizational categories that reflect the contractor’s internal management structure. Organizational categories can reflect different organization types, such as functional or Integrated Product Team (IPT), and can be arranged in a hierarchical structure. (Refer to CPD FFS 2.2.11)

2.3.2.1.3 Control Accounts.

2.3.2.1.3.1 Provide the list of control accounts established at the intersection of the WBS and organizational structure. Control accounts shall be traceable to the WBS and organizational structure, such that each control account is associated with a single WBS element and a single organizational structure element. (Refer to CPD FFS 2.2.12)

2.3.2.1.4 Work Packages. If work package data is required by the CDRL, work packages shall be traceable to the associated control accounts. A work package is the point at which work is planned, progress is measured, and earned value is computed. (Refer to CPD FFS 2.2.15)

2.3.2.1.5 Subcontractors. Efforts being conducted by major subcontractors shall be clearly marked as such in the organizational structure. Subcontractors with an EVM flow down requirement shall be considered major subcontractors. (Refer to CPD FFS 2.2.9)

2.3.2.1.6 Reporting Calendar. Provide the list of reporting periods that detail data is reported against.

The reporting calendar shall span the entire contractual period of performance (PoP).

Accounting period start and end dates and working hours shall be included. (Refer to CPD FFS 2.2.18)

2.3.2.1.7 Planning Packages. If planning package data is required by the CDRL, it shall be identified separately from work packages in the appropriate structure. A planning package is a logical aggregation of future work within a control account that cannot yet be planned in detail at the work package or task level. (Refer to CPD FFS 2.2.15)

2.3.2.1.8 Summary Level Planning Packages (SLPP). If applicable, identify summary level planning packages separately from control accounts in the appropriate structure. SLPPs are aggregations of work for far-term efforts that are not able to be identified at the control account level, but are traceable to WBS and organizational structure elements. (Refer to CPD

FFS 2.2.12)

2.3.2.2 Summary Data. The following items shall be represented in the CPD at a summary level.

2.3.2.2.1 Indirect Costs are costs that cannot be identified specifically against a particular program or activity, and must be controlled and budgeted at a functional or organizational level. Indirect Costs shall be reported as both cumulative-to-date and time phased non-cumulative-to-complete data. (Refer to CPD FFS 2.2.5, 2.2.7, and 2.2.8)

2.3.2.2.1.1 Cost of Money (COM). Provide summary-level performance data for the Facilities Capital COM allocated to the contract. Indicate “add” or “non-add” status of summary-level values.

“Non-add” means detail dollar values include burdening for COM; “add” means detail dollar values do not include burdening for COM.

2.3.2.2.1.2 General and Administrative (G&A). Provide summary-level performance data for the applicable G&A costs. Indicate “add” or “non-add” status of summary-level values. “Non-add” status means detail dollar values include burdening for G&A; “add” status means detail dollar values do not include burdening for G&A.

2.3.2.2.1.3 Overhead (OH). Provide summary-level performance data for the sum of all indirect costs, excluding COM and G&A. Indicate “add” or “non-add” status of summary-level values.

“Non-add” status means detail dollar values include burdening for OH; “add” status means detail dollar values do not include burdening for OH.

2.3.2.2.2 Undistributed Budget (UB). (Refer to CPD FFS 2.2.5)

2.3.2.2.2.1 Provide the amount of budget applicable to contract work scope that has not yet been distributed in the baseline per the contractor’s EVM system description.

2.3.2.2.2.2 Provide the EAC for the scope of work associated with UB.

2.3.2.2.3 Management Reserve (MR). Provide the value of the contractual budget held for management control purposes, risks, and for in-scope, but unplanned effort. (Refer to CPD

FFS 2.2.5)

2.3.2.2.4 Summary Cross-Check Data. Non-calculated, hard encoded (manually entered) summed values used as a validation reference for calculated values. (Refer to CPD FFS 2.2.5)

2.3.2.2.4.1 Provide the PMB subtotals of cumulative-to-date values for Budgeted Cost of Work Scheduled (BCWS), Budgeted Cost of Work Performed (BCWP), Actual Cost of Work Performed (ACWP), and Reprogramming Adjustments (Cost Variance, Schedule Variance, and Budget), as well as total values for EAC and Budget at Complete (BAC). The values provided shall be inclusive of the cumulative totals for UB, OH, G&A, and COM. All values shall be provided in both dollars and hours, as appropriate.

2.3.2.3 Detail Data. Detail data shall be comprised of the BCWS, BCWP, ACWP, and Estimate to Complete (ETC), reported by control account unless reporting by work package level is specified in the CDRL. Detail Data shall be identified by Element of Cost (EOC), and shall consist of Labor, Material, Other Direct, and Subcontractor costs. Detail Data is reported as both cumulative-to-date and time-phased-to-complete data.

2.3.2.3.1 Cumulative-To-Date Data. Cumulative-to-date values shall be provided for BCWS, BCWP, and ACWP. (Refer to CPD FFS 2.2.19, 2.2.20, and 2.2.21)

2.3.2.3.2 Time-Phased-To-Complete Data. To-complete data shall be provided for both BCWS and ETC as time-phased non-cumulative values. BCWS values shall be time-phased by reporting period starting with the next consecutive reporting period and continue through the end of the Baseline Completion Date. ETC values shall be time-phased by reporting period starting with the next consecutive reporting period and continuing through the end of the Forecast Completion Date. (Refer to CPD FFS 2.2.22 and 2.2.23)

2.3.2.4 Calculated Values. The following values are calculated.

2.3.2.4.1 Cost Variances. The cost variances are calculated by subtracting ACWP from BCWP values.

2.3.2.4.2 Schedule Variances. The schedule variances are calculated by subtracting BCWS from BCWP values.

2.3.2.4.3 Budget at Completion (BAC). In addition to the manually entered summary cross check value, the BAC values are calculated by summing the BCWS values.

2.3.2.4.4 Estimate at Completion (EAC). In addition to the manually entered summary cross check value, the EAC values are calculated by summing the ACWP and ETC values.

2.3.2.4.5 Variance at Completion (VAC). The VAC values are calculated by subtracting the EAC from the

BAC values.

2.3.2.4.6 Hierarchical Totals. The values associated with the WBS and organizational structure are calculated by summing the data provided at the control account or work package level (if applicable).

2.3.2.5 Contract Performance Over Target Baseline (OTB) and/or Over Target Schedule (OTS) Data Elements. (Refer to CPD FFS 2.2.24)

2.3.2.5.1 Cost Variance Adjustments. If the contractor adjusts or eliminates variances applicable to completed work, the adjustments made to the cost variances shall be provided by control account. Note: adjustments made shall be reported as amounts added to the old variances to reach the new variances (or to eliminate the variances, as applicable).

2.3.2.5.2 Schedule Variance Adjustments. If the contractor adjusts the schedule variances for completed work, the adjustments made to the schedule variances shall be provided by control account. Note: adjustments made shall be reported as amounts added to the old variances to reach the new variances (or to eliminate the variances, as applicable).

2.3.2.5.3 Budget Adjustments. Provide the total amounts added to the budget, consisting of the sum of the budgets used to adjust variances applicable to completed work, plus the additional budget added for remaining work.

2.3.2.5.4 Reporting Adjustments. The values provided shall represent cumulative adjustments for all previous and current reprogramming adjustments, in hours or dollars or both. If a reprogramming adjustment has occurred, it must be reported in all future reports.

2.3.2.5.5 Formal Reprogramming Timeliness. Formal reprogramming can require more than one month to implement. During formal reprogramming, reporting shall continue, at a minimum, to include ACWP, and the latest reported cumulative BCWS and BCWP will be maintained until the OTB/OTS is implemented.

2.4 Schedule (Native Schedule File and Schedule Performance Dataset (SPD)). Unless otherwise specified, all items below pertain to both the Native Schedule File and SPD.

2.4.1 Requirements.

2.4.1.1 Content. The Schedule consists of horizontally and vertically integrated discrete tasks/activities, consistent with all authorized work, and relationships necessary for successful contract completion. The Schedule is a single integrated network that also contains significant external interfaces, subcontractor discrete work, Government furnished equipment/ information/property and relationship dependencies for the entire contractual effort.

2.4.1.1.1 Production Contract Schedule. Production contracts utilizing a Manufacturing Requirements Planning (MRP) or an Enterprise Requirements Planning (ERP) system will include a representation of the discrete effort contained in the MRP/ERP in the Production Contract Schedule.

2.4.1.2 External Interfaces. The Schedule shall contain and identify significant external dependencies that involve a relationship or interface with external organizations, including Government-furnished items (e.g., decisions, facilities, equipment, information, and data). The required and projected delivery dates shall also be identified.

2.4.1.3 Calendars. The Schedule shall contain all calendars that define working and nonworking time periods. (Refer to SPD FFS 2.2.6, 2.2.7, and 2.2.8)

2.4.1.4 Schedule Progress. Schedule shall reflect accurate remaining durations, start dates, and finish dates for all tasks/activities and milestones in respect to the status date.

2.4.2 Required Content. The following items shall be represented in the Schedule:

2.4.2.1 If a Statement of Work (SOW) or Integrated Master Plan (IMP) are used for vertical schedule integration, those references shall be provided in both the SPD and native schedule. (Refer to

SPD FFS 2.2.9)

2.4.2.2 Milestones. Provide zero duration schedule events marking the due date for accomplishment of a specified work scope or objective. Milestone may mark the start, an interim step, or the end of one or more activities. (Refer to SPD FFS 2.2.9)

2.4.2.3 Tasks/Activities. Provide elements of work with duration, cost, logical relationships/dependencies, and resource requirements. Task/activity names shall be concise and unique in respect to other names within the Schedule. The name of each task/activity shall clearly reflect the scope, output (e.g. deliverable), and place within the Schedule architecture so that the content can be understood without the subproject task structure, if applicable.

(Refer to SPD FFS 2.2.9)

2.4.2.4 Duration. Provide the length of time estimated, realized, and/or remaining to accomplish a task/activity. (Refer to SPD FFS 2.2.10)

2.4.2.5 Baseline Dates and Information. Provide baseline dates for all items within the PMB. (Refer to SPD FFS 2.2.3 and 2.2.10)

2.4.2.6 Control Account/Work Package Identification. (Refer to SPD FFS 2.2.9)

2.4.2.6.1 Every discrete task/activity, work package, and planning package shall be traceable to a control account.

2.4.2.6.2 Control accounts and, if applicable, work packages shall tie to the CPD.

2.4.2.7 Level of Effort (LOE) Identification. If included in the Schedule, clearly identify any LOE control accounts, work packages, or planning packages. (Refer to SPD FFS 2.2.9, field EarnedValueTechniqueID)

2.4.2.8 Schedule Percent Complete. Provide the calculated and if applicable, physical schedule percent complete values. (Refer to SPD FFS 2.2.10)

2.4.2.8.1 The calculated schedule percent complete is a time-based status calculated by the schedule tool without regard to task/activity scope accomplishment. This is not used to status BCWP (i.e., depicts the “time” percent complete based on the forecast completion date, not earned value percent complete based on work accomplished).

2.4.2.8.2 The schedule physical percent complete is based on actual task/activity scope accomplishment.

2.4.2.9 Earned Value Technique (EVT). Identify the EVT (e.g., apportioned effort, level of effort, milestone). (Refer to SPD FFS 2.2.9)

2.4.2.10 Total Float/Slack. Provide the amount of time a task/activity or milestone forecast finish date can slip before delaying contract completion or constraint date. (Refer to SPD FFS 2.2.10)

2.4.2.11 Free Float/Slack. Provide the amount of time a task/activity or milestone can slip before it delays any of its successor tasks/activities or milestones. (Refer to SPD FFS 2.2.10)

2.4.2.12 Driving Path(s). Shall be clearly identified in both the Native Schedule and the SPD deliveries.

(Refer to SPD FFS 2.2.10)

2.4.2.12.1 The Government may specify which interim contract milestone is the destination for the driving path.

2.4.2.12.2 Without Government direction, the contractor will report the driving path to the next contractor identified event.

2.4.2.13 Critical Path(s). Shall be clearly identified in both the Native Schedule and the SPD deliveries.

(Refer to SPD FFS 2.2.10)

2.4.2.14 Subcontractor Tasks. Identify the tasks that are unique to the scope of a major subcontractor, if any. (Refer to SPD FFS 2.2.9)

2.4.2.15 Risk Mitigation Tasks. Both the Native Schedule and the SPD delivery shall identify items that came from the Risk/Opportunity Management System and include authorized risk mitigation activities, as applicable. (Refer to SPD FFS 2.2.9, field TaskSubtypeID)

2.4.2.16 Schedule Visibility Tasks (SVT). If SVTs are used, clearly and consistently identify all SVTs.

(Refer to SPD FFS 2.2.9, field TaskSubtypeID)

2.4.2.17 Lead/Lag. Provide the durations of leads or lags between predecessor and successor tasks.

Justification for each lead/lag shall be included in both the Native Schedule and the SPD.

(Refer to SPD FFS 2.2.13)

2.4.2.18 Constraints. Identify the constraints applied to tasks. Justification for each constraint shall be included in the Native Schedule and SPD submissions. (Refer to SPD FFS 2.2.13)

2.4.2.19 Schedule Margin. If Schedule Margin is used, clearly and consistently identify all schedule margin tasks. (Refer to SPD FFS 2.2.9, field TaskSubtypeID)

2.4.2.19.1 Use schedule margin only as the last task before key contractual events, significant logical integration/test milestones, end item deliverables, or contract completion.

2.4.2.19.2 Explain changes to the status of schedule margin tasks that impact the program’s primary critical path in the Detailed Analysis section of the Performance Narrative Report. See the Detailed Analysis table in Section 2.4.3 for additional information.

2.4.2.20 Data Dictionary for Native Schedule File. Provide a list of all contractor defined fields, definitions, and code structures used within the Native Schedule File. The Data Dictionary shall be delivered with the initial submission of the Native Schedule File, and resubmitted with subsequent submissions if changes occur to the Data Dictionary.

2.4.2.21 Schedule Risk Assessment (SRA). SRAs are required prior to an IBR, implementation of an OTB or OTS, as specified in the contract. The inputs (e.g., three-point estimates) from the most recent SRA shall be provided in the Native Schedule File submission. Results of the SRA shall be discussed in the Performance Narrative Report.

2.4.3 Optional Content. If required by the CDRL, the following items shall be represented in the Schedule.

2.4.3.1 Custom/User-Defined Fields. Custom/user-defined fields may be required for specific information not otherwise included in the Schedule. (Refer to SPD FFS 2.2.4, 2.2.5, 2.2.11, and 2.2.12)

2.4.3.2 Resources. Resource loading may be required as part of the Schedule in either the Native Schedule File, or both the SPD and Native Schedule File. (Refer to SPD FFS 2.2.16, 2.2.17, 2.2.18, and 2.2.19)

2.5 Performance Narrative Report. The Performance Narrative Report is comprised of the Executive Summary and the Detailed Analysis. The Executive Summary and the Detailed Analysis shall reflect both dollars and hours where applicable or as specified in the CDRL. The Government may request additional specific and/or clarifying information in the following month’s report.

2.5.1 Delivery Options. Delivery of the Performance Narrative Report is either Incremental Delivery or Single Delivery.

2.5.1.1 Incremental Delivery. The Performance Narrative Report is delivered in the increments as defined in Section 1.8.1.1. The Executive Summary will be delivered with the CPD file. The Detailed Analysis shall be delivered no later than the final delivery date as specified in the

CDRL.

2.5.1.2 Single Delivery. The Executive Summary and Detailed Analysis report are delivered as defined in Section 1.8.1 against a standard agreed-upon set of criteria or as specified in the CDRL.

2.5.2 Executive Summary. The Executive Summary shall address items listed below. The Executive Summary of the Performance Narrative Report is required regardless of monthly variance reporting selection direction.

2.5.2.1 Program/Contract Overview. A brief paragraph containing the program/contract description, PoP, contract value, and contract type (including share ratio, if applicable, and estimated price).

2.5.2.2 Contract Performance Overview. Overview of contract performance to include an integrated schedule, cost, and technical performance summary. Significant differences in the CPD and the SPD shall be reconciled and explained in the Executive Summary section of the Performance Narrative Report. Include potential impacts and drivers to the Most Likely EAC, contract objectives, and/or PoP, as well as any corrective actions underway, and provide the following as applicable:

2.5.2.2.1 Contract Modifications. Summary of major contract modifications since last report.

2.5.2.2.2 Integrated Baseline Review. The date the most recent IBR was completed along with a statement of achievability/executability, and the dates of upcoming IBRs if…