Attachment_G_Consolidated_DIDs.pdf

r DATA ITEM DESCRIPTION I Fom @/mwcd Ohm No. 07rMQlse

COnlerentx Agenda

I DI-ADMN-81249A

1.eescmlmm JRrwms -.

3.1 The cmferencs agan& provides infofn=Iion concerning Purposel ~mn. @ *edule of ~nfewr= -uired to manage the acqukidion of systems equipment. related items, and services.

1. APPfo/u OATS 6. OFFCE w PRWARY RSS~ (OW Q OTC APPUCMU

-D)

a. GUEP APPLC4US

931001 F/ESC/Ef44

r. APPUCATKW I !NTERREuTKNSH[P

7.1 Thii Data Item Description (DID) contains the format and content preparation instructions for the data product’= ~.

generated by fhe specific and dscrete sssk requirement as detiieafed m the contract.

7.2 Thii DID supersedes DI-ADMN-81249.

B. AmRubJM LMIATtJN *. Ausc NL?Am

I I L PREPARATlffl MSTRUCKWS

0.1 &IL@ Contractor format is acceptable.

0.2-. The agenda shall include the following, where applicable:

a. The purpose and objective of the conference.

b. The mnlerence Iocatiin, da!e, and duration.

c. A daiiy ctrmnobgiil listing of ea& major topic or subtopic to be dkussed and the time to be devoted to eati ppic.

d A list of acf”tiea to be represented and irfen!ikation of their responsbiINas.

e. A fist of sibcomrniitees to be established during the corrferenoe and the proposed ad-w”~ representation for each

Suboornrniltaa.

f. Reference to and brief descrfpdon of the resutk of previous meafi~s, wt&3n felevam.

(Continued on Page 2)

Il. Dlsrma.rrrm

DISTRIBUTION STATEMENT A; Approved for publii release: distribution is unlimited. I

I ~Ml&rm 1S64, APR 89 (EF) Prwi015editm am 0t6c+We. P*LIX2P%WSource: https://assist.dla.mil -- Downloaded: 2015-12-01T17:38Z

Check the source to verify that this is the current version before use.

D1-ADW’-8 1249A

I Ekxk 10. Preparation Instructions (Conlinued)

I

g. bs.afion, Sdwduk, and pwpoae or subject area to be covered,,w each sufxmmm”me, when appGcabl& ‘ h, Names Of the mntererwe chahpemn, m-chair, and submmistee chairs, w~n aPPfi*le.

i. htformafiin on billeting, messing, trarsporlation, and administratkfe semices available to confwerm aftemleea.

. j. Canpfete list of ati documanSation to be avaiife for Mew.

k. Brief description of progress on actions or problems identifistd at previous meetings, when @plicable.

I 1.Olhar pertinent inforrnat”mn such as forms to be used, identification of any deviations or waivers, sacwfly classification, @ olearance requirwnersta.

Page 2012 Pages

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T17:38Z

I

I

DATA ITEM DESCRIPTION I FumAmm@OMaNo.o@Rm3e

Zanfererce Mhules I DI-ADMW31Z50A

. D=c%mmtl~

APmovu OATE rmacwl

FTeiwm~ (Om 6?,.DTc APFtWSU 6brx3EP~

APPIBxl’8x/NrERwA~ .-.

‘.1This Da!a Item -M @[D) ~ he fo~ @ ~eti prepation instr@ons for the data pfodud leneratedby fhe apeoim and diswta ask requirarnen!as deliiakd in fhe czmlrad.

~AL LMTATC+l c8.AwJaaLE~ m. AJ6cMAraER

1. PREPAPAlct4 NsTRlsTctts

0.1 m. Comtaaor formal is accqabk.

02 Ql&D1. Themirwesa f@inoMef JwMowinghfom@on:

a Atitlipage mnfainingfhefm

(1) Tii-fypeofmaeting anddde.

(2) Wm=tbn of the amu:pition(syatarrbaMxnam omaa number)for whichthe meeongwaa held

(3) Spaoe for a@atums of fhe dasigmt~ repreaantdivesof fhe canhuor and acqistbn acfiviiy.

(4) The mm of fhe omfmUorard~fowhkh fheacquisilion activityahoukie&mwMge reoe@4of

Omrnants.

b. Thapmposaand objecfiveoftheoonferanoe.

o. meC&k3ranceboabn.

d Aaurnmryoflhedsaskma, deckbns, agreemam reached,anddiredoneoffhe oonknmaorhdiid Uboomrniueesthereof.

(Confiied OnPa@ 2)

1, Dlslumlnw

DISTRIBLMON STATEMENT A Appmvadfor publicralease;d&ibuOin is unliied.

D&mm w&-I, APRW (E!=) ~-m&sO&m. pqre~d~~ Source: https://assist.dla.mil -- Downloaded: 2015-12-01T17:39Z

DI-ADMN-812jOA

Bbck 10, PreparationInstrudions(Cantitwd)

e. A ES of atferd~ & name, mnk, tafe, graie or position,activiiy represenkd, activityoode, and phone .4

Nmbefs as expropriate.

f. Win items resuhing“komIhe conference.

L

I

I Paoe20f2F+age5

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T17:39Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-03T14:09Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-03T14:09Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T17:41Z

DATA ITEM DESCRIPTION

Title: CONTRACT CHANGE PROPOSALS (CCPs)

Number: DI-ADMN-81401B Approved Date: 20080814 AMSC Number: F9019 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: 11 (ASC/ENS) Applicable Forms: N/A Use/Relationship: The CCP DID will be used to provide the data necessary to propose, control, and approve nonbaseline changes to contracts. A CCP must not be used for making changes to specifications, drawings, or other baseline documentation. In the event changes to both baseline and nonbaseline documents are made, all changes should be included in an Engineering Change Proposal (ECP).

a. This Data Item Description (DID) may be used on any type contract for which a vehicle for control and processing of contract changes is needed.

b. This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation

c. DI-ADMN-81401B supersedes DI-ADMN-81401A

Requirements:

1. Requirements. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as cited in the contract at the time of solicitation.

2. Format. The Contract Change Proposal shall be in the contractor’s format.

3. Content. The CCP shall contain the following:

3.1. Control number and date of preparation. A CCP number shall be assigned. The date of preparation shall also be included.

3.2. Title. A descriptive title shall be assigned.

3.3. Items affected. Identifies the part or parts of the contract which are affected by the proposed changes (e.g. contract data requirements list, statement of work paragraph, plan, or contract section).

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

Source: https://assist.dla.mil -- Downloaded: 2015-12-08T15:06Z

DI-ADMN-81401B

3.4. Statement of justification and alternatives. Identifies reason for change. Presents viable alternatives which may exist. Includes impact statement to address effect of not making the change.

3.5. Description of proposed change. Provides a detailed description of the proposed change.

3.6. Schedule. Identifies working schedule for implementation of the CCP, including target date for implementation via contract modification. If conditions exist which make implementation urgent, a brief explanation should be included.

3.7. Estimated cost. Presents estimated cost (or estimated savings) expected as a result of implementing the change.

4. End of DI-ADMN-81401B.

Source: https://assist.dla.mil -- Downloaded: 2015-12-08T15:06Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-16T20:24Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T17:44Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T17:44Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:06Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:08Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:09Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:10Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:11Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:12Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:13Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:14Z

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:15Z

Title: Status Report

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

Use/relationship:

The Status Report documents the status of contractor effort towards achieving contract objectives. It identifies accomplishments to date and difficulties encountered, and compare the status achieved to planned goals and the resources expended. It is used by the Government to monitor and evaluate contractor performance.

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

It is not intended that all requirements herein should be applied to every program.

Portions of the DID are subject to tailoring by deletion depending on the specific status reporting requirements of the project.

This DID is related to DI-FNCL-80331, Funds and Man-Hour Expenditure Report which can be used in conjunction with this report if paragraph 3.2.3 below is deleted.

This DID supersede DI-MGMT-80368.

1. Reference documents. None.

2. Format. The Status Report shall be in contractor format.

2.1 Identification. The data indicated below shall be contained on a title page or on the first page of the report.

a. Title/identification of the system/component/program/project.

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:16Z

DI-MGMT-80368A

b. Type of report (e.g., monthly, interim, final).

c. Period covered by the report.

d. Contract number.

e. Preparing activity or contractor’s title.

f. Security classification, when required.

g. Distribution Statement.

2.2 Page size. The report shall be on 8 ½ by 11 inch (metric A4) paper.

3. Content. The report shall contain the following:

3.1 Summary. The summary shall include a brief statement of the overall project status , covering the accomplished technical activities and development, objectives of efforts, summary results of efforts, identification of major problems/deficiencies with impact, and recommended solutions.

3.2 Body of report. The Status Report shall contain the following items, where applicable:

3.2.1 Milestone/task status. The status of each milestone/task as defined by the statement of work or contract, as applicable:

a. A statement as to whether or not the program/project/task is on schedule; if not, the effort planned to meet the schedule shall be indicated. Include an overall status of each milestone, task, or unit of work. Include update schedule sheets, milestone charts, or task synopsis sheets identifying phase of task and percentage of completion of each task, technical instruction, or order.

b. A comparison of achieved end-product performance capabilities projected against contract baseline values, requirements, or allocations.

c. Effort expended on each task to date, and a brief description of technical developments and accomplishments.

d. Key dates in any testing program and description of tests performed and significant test results. If applicable, a description of the amount and type of down time on the equipment or system under test.

e. A list of all designs completed and a brief description of each item. For designs in process, provide estimated dates for design and drawing completion.

f. A narrative of outstanding problems existing as of the previous status report, and their resolution status. 2

DI-MGMT-80368A

g. New problem areas encountered or anticipated, their effect on the overall work effort/project and steps being taken to remedy problem situations.

h. Significant results of conferences, trips, or directives for the Contracting officer’s representatives.

i. Any other information which may cause significant changes in the program schedule.

3.2.2 Future plans. Summary of future plans, recommendations and proposals both for the next reporting period and for any long term plans.

3.2.3 Itemized man-hours and costs. Itemized man-hour and cost expenditure incurred for the reporting period by category and task, total contractual expenditures, and funds remaining as of the reporting date.

3.2.4 Contract deliveries status. The status of each deliverable end item, including data deliverables, as required by the contract. Provide item and contract identification, shipping/transmittal data, acceptance status, security classification, and schedule due date information.

3.2.5 Report preparer. Name of person(s) preparing report and telephone number(s).

3.3 Appendices. Appendices where applicable, for tables, references, charts, or other descriptive material. Each appendix shall be identified and referenced in the appropriate area of the report.

4. END OF DI-MGMT-80368A

Title: DATA ACCESSION LIST (DAL)

Number: DI-MGMT-81453A Approved Date: 20070927 AMSC Number: F9020 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Office of Primary Responsibility: 11 (ASC/ENS) Applicable Forms: N/A Use/Relationship: The purpose of the Data Accession List (DAL) is to provide a medium for identifying contractor internal data which has been generated by the contractor in compliance with the work effort described in the Statement of Work (SOW). The DAL is an index of the generated data that is made available upon request.

a. This data item is not a substitute for standard data requirements that are contractually applied.

b. This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in the solicitation.

c. This DID supersedes DI-MGMT-81453.

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

2. Format. The Data Accession List shall be in the contractor’s format.

3. Content. The DAL shall specify internally generated data and computer software used by the contractor to develop, test, and manage the program. The format and content of the data listed on the DAL shall be as prepared by the contractor to document compliance with the SOW Task requirements.

3.1. The list shall include the identification number, title which shall describe content, security classification, and in-house release date.

3.2. The list shall also identify the Government Rights to the data using the following codes:

“GPR” – Government Purpose Rights “UR” = Unlimited Rights “LR” = Limited Rights

“RR” = Restricted Rights (Computer Software only)

4. End of DI-MGMT-81453A.

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

Source: https://assist.dla.mil -- Downloaded: 2015-12-01T18:17Z

Title: WEIGHT AND BALANCE REPORT FOR AIRCRAFT

Number: DI-MGMT-81501A Approval Date: 20070927 AMSC Number: F9014 Limitation: N/A DTIC Applicable: Yes GIDEP Applicable: No DTIC Northwestern Regional Office at Boston, ATTN: DTIC_BRNB Building 1103, 5 Wright Street Hanscom AFB, MA 01731-3012 Office of Primary Responsibility: 11 (ASC/ENFS) Applicable Forms: N/A Use/relationship: The Weight and Balance Report for Aircraft provides up-to-date information required to maintain cognizance of deleterious trends which may require program office action, provide data for use by various engineering activities, and provide safety of flight information to the field. Aircraft weight, balance, and inertia properties officially affect system performance.

a. This Data Item Description (DID) interrelates with DI-MGMT-81452, Mass Properties Control and Management Process Report; DI-MGMT-81504, Inertia Report for Aircraft;

DI-MGMT-81503, Post-Design Weight Analysis Report; and DI-MGMT-81502, Sample Chart A and Chart E Report for Aircraft.

b. This DID contains the format, content and intended use information for the data deliverable resulting from the work task described in the contract.

c. DI-MGMT-81501A supersedes DI-MGMT-81501.

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

2. Format. The format shall be The Society of Allied Weight Engineers (SAWE) Recommended Practice number 8 (RP-8), Weight and Balance Data Reporting for Aircraft.

3. Content. Depending on project phase, the following weight and balance information shall be included:

a. Estimated

b. Calculated

c. Status

d. Actual

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

DI-MGMT-81501A

2of 4

3.1 The following shall be included in the report (except for status updates).

a. Contract number, aircraft designation, acquiring activity, and contract identification or serial numbers, as appropriate, of the aircraft for which the data in the report is considered to be representative.

b. A table summarizing the weight, center of gravity (c.g.), and moments of inertia for weight empty, maximum gross weight, structural design weights, most forward, most aft, and all weight conditions covered in the design mission description and specification.

Dimensional data suitably illustrated, locating the longitudinal, vertical, lateral, and radii of gyration axes, and mean aerodynamic chord (MAC) or main rotor centerline. The recommended c.g. limits shall be provided.

c. Group Weight Statement. The useful load page shall detail the summary values in b.

above.

d. Detail Weight Statement

e. Material breakdown by weight group for Structure Weight and Airframe Unit Weight.

f. Longitude, vertical, and lateral balance calculations for values in b. above.

g. List of government supplied equipment in weight empty and associated weight.

h. Welted areas of fuselage, wings, empennage, and all external items included in takeoff configurations (pylons, tanks, and weapons).

i. Volumes of the fuselage, wings, empennage, and all external items included in mission takeoff configurations. The volumes shall be calculated with flaps, gears, and air brakes retracted.

j. Scalable dimensional three-view drawings locating and identifying the following:

(1) The major dimensional data including major structural stations of the wing, rotor, tails, fuselage, alighting gear, nacelles, and inlets.

(2) Reference data for longitudinal, lateral, and vertical moment arms and Mean Aerodynamic Chord (MAC).

(3) Major structural members, cutouts, control surfaces, and other structural features.

(4) Major items of equipment, fuel, or propellant

(5) Types of construction and materials used in each major structural component section and tank.

k. Outline sketch of the main propulsion power transmission system showing gearboxes, shafting, rated horsepower, and torque reduction ratio.

l. Schematic diagram for major subsystems.

m. Center of gravity (c.g.) diagrams showing plots of weight vs. c.g. for all specification missions, most forward loadings, and most aft loadings. Label all applicable limits.

n. Oil and unusable fuel data.

o. Derivation of the moment change owing to retracting the alighting gear.

p. Tip back calculations.

3of 4

3.2 The following additional data are required on actual weight reports:

a. Weight empty weighting form.

b. A detailed list of items, weights, arms, and moments to be added to or subtracted from the as-weighed condition to arrive at the weight empty.

c. All weight and balance calculations for the final Estimated or Calculated Weight Report, corrected to agree with the actual weight and c.g. data.

d. A tabulation of specified and actual weights of all Government Furnished Aerospace Equipment (GFAE) included in the weight empty, based on weighing of the items prior to installation, and determination of the net underweight or overweight of this equipment

e. Tabulations of authorized and pending changes included in the reported weight empty and useful load, the weights, and the groups to which the weights are allocated and associated engineering change proposals (ECPs) or corresponding numbers.

f. A tabulation deriving the contractor responsibility for weight empty under or overweight, as follows:

(1) The original weight empty guarantee or specification weight empty.

(2) The weight empty increases or decreases owing to the weights of authorized changes, pending changes, and the net underweight or overweight of GFAE.

(3) The aircraft actual weight empty.

(4) The contractor responsible weight.

g. Oil, unusable fuel, drainable fuel, and trapped fuel weight and c.g. data including description of how values were determined.

h. Brief summary of internal loads and points of load concentration. If information is presented by drawings, it is desired, but is not necessary, that the cross-section of the related structure be included. Reduced size drawings and copies are acceptable.

These data are required on first and last aircraft only.

3.3 The following shall be included in Status Updates. Reports reflect the changes from the previous weight report (estimated, status, or calculated) as the design and fabrication proceeds.

As individual components become defined, the status reports shall represent a mixture of estimated, calculated, and actual weight. Each report shall represent the status as determined by the contractor’s weight control records at the end of the reporting period noted by the date on the form. The report shall include separate sections listing all possible and planned changes not yet included in the weight control records. Additional data will be required by the acquiring activity if weight or c.g. are considered to show an undesirable trend. The following general instructions shall apply:

a. The values in the original specification or the original guarantee column shall be the same as in the original specification or approved Estimated Weight Report and shall not be changed.

b. The initial issues of the status report shall include reference to the source or the recommended c.g. limits, brief indication of the critical flying qualities or structural considerations which dictated these limits, and reasons for any tapered or special c.g.

restrictions. Similar data shall be furnished whenever limits are revised.

4of 4

c. A brief discussion of each major government responsible weight change.

d. A brief discussion describing the reason for each major contractor responsibility weight variation and c.g. shift, including any remedial measures being investigated or applied.

e. At the times when the current weight status and c.g. are brought into agreement with the Calculated Weight Report or the results of the actual weighing of the completed aircraft, appropriate note to this effect shall be made and the calculated or actual weight report shall be referenced by number, date, and title.

f. During the flight test phase, if changes in the current weight status in a status report period are less than 0.25 percent of the weight empty and the weight empty c.g. shift is less than 0.5 percent MAC for aircraft or 2 percent of allowable c.g. range for rotor craft, the status report for that period may be omitted and the acquiring activity notified by letter.

g. If a major modification is to be incorporated in one or a group of aircraft on the contract, information on the weight and c.g. status of the modified aircraft shall be included as an appendix to the status report. Status information furnished may be in the form of differences over the basic model and shall continue as a separate report, if necessary, until the modified aircraft is delivered to the acquiring activity.

4. End of DI-MGMT-81501A.

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

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

IPMR Format Form Number Format No.

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

1.0. USE/RELATIONSHIP:

1.1. The IPMR contains data for measuring cost and schedule

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

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

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

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

1.1.4. Format 4 defines staffing forecasts.

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

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

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

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

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

Source: https://assist.dla.mil -- Downloaded: 2016-06-10T15:01Z

DI-MGMT-81861A

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

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

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

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

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

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

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

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

2.0. COMMON IPMR REQUIREMENTS:

2.1. Electronic Submittal Formats.

Formats 1-4 and 6-7.

The following requirements apply to

2.1.1.

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

2.1.1.1.

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

2.1.1.2.

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

2.1.1.3.

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

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

XML.

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

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

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

2.2.2.

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

2.2.3.

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

2.2.4.

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

2.2.5.

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

2.2.6.

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

2.2.6.1.

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

2.2.6.2.

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

2.2.6.3.

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

2.2.6.4.

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

2.3.

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

2.4.

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

2.5.

Reporting Frequency.

2.5.1.

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

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

2.6.

Submission Requirements.

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

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

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

2.8.

Applicability.

2.8.1.

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

2.8.2.

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

2.8.3.

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

3.0. IPMR FORMAT CONTENT REQUIREMENTS.

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

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

3.1.1.

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

Source: https://assist.dla.mil -- Downloaded: 2016-06-10T15:01Z http://www.acq.osd.mil/evm/

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

3.1.5.

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

3.1.6.

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

3.2.

Format 1 - Work Breakdown Structure.

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

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

3.2.1. Contract Data.

3.2.1.1.

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

3.2.1.2.

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

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

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

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

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

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

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

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

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

3.2.1.5.

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

3.2.1.6.

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

3.2.1.7.

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

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

3.2.1.9.

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

3.2.2.

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

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

• Consideration of known and anticipated risk areas;

• Planned risk reductions;

• Cost containment measures.

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

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

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

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

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

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

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

3.2.2.5.

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

3.2.3.

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

3.2.4.

Performance Data.

3.2.4.1.

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

3.2.4.2.

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

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

3.2.4.3.

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

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

3.2.4.4.

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

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

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

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

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

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

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

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

3.2.4.6.

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

• MR shall not be used to offset cost variances.

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

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

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

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

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

3.2.5.

Reconciliation to CBB.

3.2.5.1.

Formal Reprogramming. In exceptional cases, the contractor may 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)). The total of Column (13) shall equal the budget amount by which the TAB exceeds the CBB as shown in Block 5.g of Format 3. An explanation of the reprogramming shall be provided in Format 5.

3.2.6.7.1.

Formal Reprogramming Reporting. Columns (12) and (13) are intended for use only in situations involving formal reprogramming (OTB). Internal replanning actions within the CBB do not require entries in these columns.

3.2.6.7.2.

Formal Reprogramming Timeliness. Formal reprogramming (OTB) may require more than one month to implement and may necessitate a temporary reporting hiatus. In those cases, before the initiation of formal reprogramming, the contractor and the Government shall agree on the date, the duration, and the scope of the hiatus along with any specific interim reporting…