About this file

CDRL's A&B

View the file

Other files

Show all 15

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

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

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

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

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

TDP TM OTHER

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

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

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

7. DD 250 REQ

9. DIST STATEMENT

REQUIRED

10. FREQUENCY 12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION Draft

Draft Final Final

Reg. Repro Reg. Repro

16. REMARKS

15. TOTAL

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

17. PRICE GROUP 18. ESTIMATED TOTAL PRICE

FOR OFFICIAL USE ONLY

Page _______ of _______ Pages USAPPC v3.00

DD FORM 1423-1, JUN 90

A CONTRACT LINE ITEM NO: 0002

B EXHIBIT: B

TDP:

TM:

OTHER: Misc

D SYSTEMITEM:

E CONTRACTPR NO: FA-8903-18-R-0065

F CONTRACTOR: TBD

1 DATA ITEM NO: B001

2 TITLE OF DATA ITEM: Conference Agenda

3 SUBTITLE:

4 AUTHORITY Data Acquisition Document No: DI-ADMN-81249A

5 CONTRACT REFERENCE: PSW Para - - 4.1.1, 4.2

6 REQUIRING OFFICE: AFCEC/CZRX

7 DD 250 REQ: LT

10 FREQUENCY: As Required

12 DATE OF FIRST SUBMISSION: Block 16

8 APP CODE: A

11 AS OF DATE: N/A

13 DATE OF SUBSEQUENT SUBMISSION: Block 16 a ADDRESSEE16 REMARKS: AFCEC/CZRX

Draft16 REMARKS: 1

Reg16 REMARKS: 0

Repro16 REMARKS: 0

Reg16 REMARKS_2: 1

Repro16 REMARKS_2: 0 a ADDRESSEE16 REMARKS_2: Base POC

Draft16 REMARKS_2: 1

Reg16 REMARKS_3: 0

Repro16 REMARKS_3: 0

Reg16 REMARKS_4: 1

Repro16 REMARKS_4: 0 a ADDRESSEE16 REMARKS_3: 772 ESS/PKB

Draft16 REMARKS_3: 1

Reg16 REMARKS_5: 0

Repro16 REMARKS_5: 0

Reg16 REMARKS_6: 1

Repro16 REMARKS_6: 0 a ADDRESSEE16 REMARKS_4: Other Stakeholders

Draft16 REMARKS_4: 0

Reg16 REMARKS_7: 0

Repro16 REMARKS_7: 0

Reg16 REMARKS_8: 1

Repro16 REMARKS_8: 0 a ADDRESSEE16 REMARKS_5:

Draft16 REMARKS_5:

Reg16 REMARKS_9:

Repro16 REMARKS_9:

Reg16 REMARKS_10:

Repro16 REMARKS_10:

a ADDRESSEE16 REMARKS_6:

Draft16 REMARKS_6:

Reg16 REMARKS_11:

Repro16 REMARKS_11:

Reg16 REMARKS_12:

Repro16 REMARKS_12:

a ADDRESSEE16 REMARKS_7:

Draft16 REMARKS_7:

Reg16 REMARKS_13:

Repro16 REMARKS_13:

Reg16 REMARKS_14:

Repro16 REMARKS_14:

a ADDRESSEE16 REMARKS_8:

Draft16 REMARKS_8:

Reg16 REMARKS_15:

Repro16 REMARKS_15:

Reg16 REMARKS_16:

Repro16 REMARKS_16:

a ADDRESSEE16 REMARKS_9:

Draft16 REMARKS_9:

Reg16 REMARKS_17:

Repro16 REMARKS_17:

Reg16 REMARKS_18:

Repro16 REMARKS_18:

a ADDRESSEE16 REMARKS_10:

Draft16 REMARKS_10:

Reg16 REMARKS_19:

Repro16 REMARKS_19:

Reg16 REMARKS_20:

Repro16 REMARKS_20:

a ADDRESSEE16 REMARKS_11:

Draft16 REMARKS_11:

Reg16 REMARKS_21:

Repro16 REMARKS_21:

Reg16 REMARKS_22:

Repro16 REMARKS_22:

a ADDRESSEE16 REMARKS_12:

Draft16 REMARKS_12:

Reg16 REMARKS_23:

Repro16 REMARKS_23:

Reg16 REMARKS_24:

Repro16 REMARKS_24:

a ADDRESSEE16 REMARKS_13:

Draft16 REMARKS_13:

Reg16 REMARKS_25:

Repro16 REMARKS_25:

Reg16 REMARKS_26:

Repro16 REMARKS_26:

a ADDRESSEE16 REMARKS_14:

Draft16 REMARKS_14:

Reg16 REMARKS_27:

Repro16 REMARKS_27:

Reg16 REMARKS_28:

Repro16 REMARKS_28:

a ADDRESSEE16 REMARKS_15:

Draft16 REMARKS_15:

Reg16 REMARKS_29:

Repro16 REMARKS_29:

Reg16 REMARKS_30:

Repro16 REMARKS_30:

a ADDRESSEE16 REMARKS_16:

Draft16 REMARKS_16:

Reg16 REMARKS_31:

Repro16 REMARKS_31:

Reg16 REMARKS_32:

Repro16 REMARKS_32:

a ADDRESSEE16 REMARKS_17:

Draft16 REMARKS_17:

Reg16 REMARKS_33:

Repro16 REMARKS_33:

Reg16 REMARKS_34:

Repro16 REMARKS_34:

a ADDRESSEE16 REMARKS_18:

Draft16 REMARKS_18:

Reg16 REMARKS_35:

Repro16 REMARKS_35:

Reg16 REMARKS_36:

Repro16 REMARKS_36:

a ADDRESSEE16 REMARKS_19:

Draft16 REMARKS_19:

Reg16 REMARKS_37:

Repro16 REMARKS_37:

Reg16 REMARKS_38:

Repro16 REMARKS_38:

a ADDRESSEE16 REMARKS_20:

Draft16 REMARKS_20:

Reg16 REMARKS_39:

Repro16 REMARKS_39:

Reg16 REMARKS_40:

Repro16 REMARKS_40:

a ADDRESSEE16 REMARKS_21:

Draft16 REMARKS_21:

Reg16 REMARKS_41:

Repro16 REMARKS_41:

Reg16 REMARKS_42:

Repro16 REMARKS_42:

a ADDRESSEE16 REMARKS_22:

Draft16 REMARKS_22:

Reg16 REMARKS_43:

Repro16 REMARKS_43:

Reg16 REMARKS_44:

Repro16 REMARKS_44:

a ADDRESSEE16 REMARKS_23:

Draft16 REMARKS_23:

Reg16 REMARKS_45:

Repro16 REMARKS_45:

Reg16 REMARKS_46:

Repro16 REMARKS_46:

a ADDRESSEE16 REMARKS_24:

Draft16 REMARKS_24:

Reg16 REMARKS_47:

Repro16 REMARKS_47:

Reg16 REMARKS_48:

Repro16 REMARKS_48:

a ADDRESSEE16 REMARKS_25:

Draft16 REMARKS_25:

Reg16 REMARKS_49:

Repro16 REMARKS_49:

Reg16 REMARKS_50:

Repro16 REMARKS_50:

a ADDRESSEE16 REMARKS_26:

Draft16 REMARKS_26:

Reg16 REMARKS_51:

Repro16 REMARKS_51:

Reg16 REMARKS_52:

Repro16 REMARKS_52:

a ADDRESSEE16 REMARKS_27:

Draft16 REMARKS_27:

Reg16 REMARKS_53:

Repro16 REMARKS_53:

Reg16 REMARKS_54:

Repro16 REMARKS_54:

a ADDRESSEE16 REMARKS_28:

Draft16 REMARKS_28:

Reg16 REMARKS_55:

Repro16 REMARKS_55:

Reg16 REMARKS_56:

Repro16 REMARKS_56:

a ADDRESSEE16 REMARKS_29:

Draft16 REMARKS_29:

Reg16 REMARKS_57:

Repro16 REMARKS_57:

Reg16 REMARKS_58:

Repro16 REMARKS_58:

a ADDRESSEE16 REMARKS_30:

Draft16 REMARKS_30:

Reg16 REMARKS_59:

Repro16 REMARKS_59:

Reg16 REMARKS_60:

Repro16 REMARKS_60:

a ADDRESSEE16 REMARKS_31:

Draft16 REMARKS_31:

Reg16 REMARKS_61:

Repro16 REMARKS_61:

Reg16 REMARKS_62:

Repro16 REMARKS_62:

a ADDRESSEE16 REMARKS_32:

Draft16 REMARKS_32:

Reg16 REMARKS_63:

Repro16 REMARKS_63:

Reg16 REMARKS_64:

Repro16 REMARKS_64:

a ADDRESSEE16 REMARKS_33:

Draft16 REMARKS_33:

Reg16 REMARKS_65:

Repro16 REMARKS_65:

Reg16 REMARKS_66:

Repro16 REMARKS_66:

a ADDRESSEE16 REMARKS_34:

Draft16 REMARKS_34:

Reg16 REMARKS_67:

Repro16 REMARKS_67:

Reg16 REMARKS_68:

Repro16 REMARKS_68:

a ADDRESSEE16 REMARKS_35:

Draft16 REMARKS_35:

Reg16 REMARKS_69:

Repro16 REMARKS_69:

Reg16 REMARKS_70:

Repro16 REMARKS_70:

Draft15 TOTAL: 0

Reg15 TOTAL: 0

Repro15 TOTAL: 0

Reg15 TOTAL_2: 0

Repro15 TOTAL_2: 0

G PREPARED BY: Cindy Cash

H DATE: 6/8/18

I APPROVED BY: Arthur Hatfield

J DATE: 6/8/18

18 ESTIMATED TOTAL PRICE:

Page: 1 of: 1

Remarks: Block 12 & 13: Submit draft 7 calendar days prior to the scheduled meeting. The government will require up to 3 calendar days for review of draft. The contractor shall make all required changes and have final available 2 calendar days prior to the scheduled meeting.

Block 14: All deliverables shall be submitted by email. List of additional stakeholders and all E-mail addresses will be provided by the COR.

17 PRICE GROUP:

9:

DIST STATEMENT: B

DATA ITEM DESCRIPTION

I 3.1 The conference agenda provides information conuMlinp purpose, Wnn, and schedule of conferences required to m a g e the acquisiition of system equipmenl, related items. and services. I

I

P ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ , ~ ~ - ~ . ~ ~ I ~ ~ ~ ~ ~ I O M L - . P Y ) ~ ~ ~ I D I ~ N ~ L L I ( I I I YMIN.F-.OYLI

-ad--- narw.",,a - w ~ m - 1 D l l l l l C D l - - ~ . ~ ~ u . I l b . Y I * ~ - d ~ V I S ~ - ' D I -, b . 1 ~ -m ~ A ~ ~ . ~ ~ D L ~ ~ ~ - ~ O ~ ~ P . D I I R . ~ P ~ ~ ~ I D X Y Q ~ Y I W Y * ~ Q I I I ~ -d I 112

Conlerence Agenda

-- 7.1 This Data Item Description (DID) mntains the format and m e n f preparation instructions lor the data produd I Qenerated by the Specific and dime task requirement as delmeaed in me contract.

2 I D E N ? Y a T I O H W E R

DI-ADMK-8 1249A

7.2 Th~s DID supersedes Dl-ADMN-81249.

& . G l D E P * P P L w .

r

7. APPULXTlOr t NERRELATDNSHIP

&DTCAPPLY;ABLE 4. APPROVAL DATE

V ~ O ) 931001

I 10.2 m. The agenda shall indude the Wowmg, where applitable: I

5. OFFICE OF P W R Y RESPWIBlim (OPR)

F/ESC/ENd

8. Af'f'RWKUIRIATION r

I a The plrpae am objective OI me cantereme. I I b. The wnlerertce location. date. and &ration. I

10. Pwwuncw H~RUCTYHS

10.1 F_brmat. Contractor tormat is scceptabk.

O AP- FOrPlhi

I c. A h i l y chmnolDpul liainp of each mpr topic or subtopic to be dscussed and the time to be devoted to each topic. I

a. Ab6C M I s E R

F6968

I d. A list of activiiies lo be representad and i d e n t i f i n of their respanslbiiai.

I e. A CIst 01 subcommittees to be establshcd dmbg the eantersnce and the pnqmed adiviy rqnesentabn lor each submmmmee. I I i. Refereme to and brif desu@tm of the resub of previous meetings, when relevant. I

(Cuatinud rn Page 2)

11 DISTRILIUTON

I DISTRIBUTION STATEMENT A. Apptoved tor plMic rdease: diiribulion is unlimited.

L DD Form 1664, APR 89 (EF) J

~ r & l m . n c l g d . e .

I m T J -1d2-0-

FA8903-17-R-0064

Exhibit B

g. Locallon, sheduk, and purpose or subject area to be covered by each su!xommmee, when appkcable.

h. Names of the conference chairperron, =hair, and subcornmiltee chairs, when applicable.

i . Inlormation on billeting, messing, transportation, and administrative services available to conference anend-.

j. Complete list at all documentation to be available for reuiew.

k. Brief description of pmgress on actions or problems identified m previous meetings, when applicable.

I. Other pertinent intormation arch as tom to be used, identification of any deviatians or waivers. security classification, and clearance requirements.

Page 2 ot 2 Pages

FA8903-17-R-0064

Exhibit B

FA8903-17-R-0064 Exhibit B.pdf

DI-MGMT-81334D - Contract Work Breakdown.pdf

a. UCWBS CodeU. Enter the code, if applicable. The CWBS codes used in the CWBS Index and Dictionary must be identical to those in the OSD DDCA-approved contract CSDR Plan. The preferred convention is to use a numeric structure starting with 1.0 for...

b. UCWBS Element LevelU. Enter the level of the CWBS element. Level 1 is the total contract. Levels 2, 3, and so on, are successively lower levels of the contract.

c. UCWBS Element NameU. Enter the title of the CWBS element using the specific name or nomenclature. The CWBS element names used in the CWBS Index and Dictionary must be identical to those in the OSD DDCA-approved contract CSDR Plan.

a. UCWBS CodeU. Enter the same codes used in the Index.

b. UCWBS Element NameU. Enter the same element names used in the Index.

c. UCWBS DefinitionU. Enter a complete description of the technical, cost, and work content of each CWBS element. For the technical content, the dictionary must include a general system level description (i.e., highest level WBS element) of the milit...

The CWBS dictionary must also include a description of the cost and work content for each element. Cost content definitions must include explanations of recurring versus nonrecurring efforts, functional cost element inclusion or exclusion, and purcha...

CWBS dictionaries must reflect only the work being done on the contract for which the document is being submitted. If work is not expected to occur for a given WBS element, the CWBS dictionary definition must indicate that this element is not applica...

Figure 1. CWBS Index Example (based on MIL-HDBK-881 Missile Systems)

Figure 2. CWBS Dictionary Example

Figure 2. CWBS Dictionary Example (Continued)

Figure 2. CWBS Dictionary Example (Continued)

END OF DI-MGMT-81334D

DI-MGMT-80507C - Project Planning Chart.pdf

DATA ITEM DESCRIPTION

Requirements:

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

A CONTRACT LINE ITEM NO: 0002

B EXHIBIT: B

TDP:

TM:

OTHER: Misc

D SYSTEMITEM:

E CONTRACTPR NO: FA-8903-18-R-0065

F CONTRACTOR: TBD

1 DATA ITEM NO: B002

2 TITLE OF DATA ITEM: Conference Minutes

3 SUBTITLE: N/A

4 AUTHORITY Data Acquisition Document No: DI-ADMN-81250B

5 CONTRACT REFERENCE: PSW Para - 4.1.1, 4.2

6 REQUIRING OFFICE: AFCEC/CZRX

7 DD 250 REQ: LT

10 FREQUENCY: As Required

12 DATE OF FIRST SUBMISSION: Block 16

8 APP CODE: A

11 AS OF DATE: N/A

13 DATE OF SUBSEQUENT SUBMISSION: Block 16 a ADDRESSEE16 REMARKS: AFCEC/CZRX

Draft16 REMARKS: 1

Reg16 REMARKS: 0

Repro16 REMARKS: 0

Reg16 REMARKS_2: 1

Repro16 REMARKS_2: 0 a ADDRESSEE16 REMARKS_2: Base POC

Draft16 REMARKS_2: 1

Reg16 REMARKS_3: 0

Repro16 REMARKS_3: 0

Reg16 REMARKS_4: 1

Repro16 REMARKS_4: 0 a ADDRESSEE16 REMARKS_3: 772 ESS/PKB

Draft16 REMARKS_3: 1

Reg16 REMARKS_5: 0

Repro16 REMARKS_5: 0

Reg16 REMARKS_6: 1

Repro16 REMARKS_6: 0 a ADDRESSEE16 REMARKS_4: Other Stakeholders

Draft16 REMARKS_4: 0

Reg16 REMARKS_7: 0

Repro16 REMARKS_7: 0

Reg16 REMARKS_8: 1

Repro16 REMARKS_8: 0 a ADDRESSEE16 REMARKS_5:

Draft16 REMARKS_5:

Reg16 REMARKS_9:

Repro16 REMARKS_9:

Reg16 REMARKS_10:

Repro16 REMARKS_10:

a ADDRESSEE16 REMARKS_6:

Draft16 REMARKS_6:

Reg16 REMARKS_11:

Repro16 REMARKS_11:

Reg16 REMARKS_12:

Repro16 REMARKS_12:

a ADDRESSEE16 REMARKS_7:

Draft16 REMARKS_7:

Reg16 REMARKS_13:

Repro16 REMARKS_13:

Reg16 REMARKS_14:

Repro16 REMARKS_14:

a ADDRESSEE16 REMARKS_8:

Draft16 REMARKS_8:

Reg16 REMARKS_15:

Repro16 REMARKS_15:

Reg16 REMARKS_16:

Repro16 REMARKS_16:

a ADDRESSEE16 REMARKS_9:

Draft16 REMARKS_9:

Reg16 REMARKS_17:

Repro16 REMARKS_17:

Reg16 REMARKS_18:

Repro16 REMARKS_18:

a ADDRESSEE16 REMARKS_10:

Draft16 REMARKS_10:

Reg16 REMARKS_19:

Repro16 REMARKS_19:

Reg16 REMARKS_20:

Repro16 REMARKS_20:

a ADDRESSEE16 REMARKS_11:

Draft16 REMARKS_11:

Reg16 REMARKS_21:

Repro16 REMARKS_21:

Reg16 REMARKS_22:

Repro16 REMARKS_22:

a ADDRESSEE16 REMARKS_12:

Draft16 REMARKS_12:

Reg16 REMARKS_23:

Repro16 REMARKS_23:

Reg16 REMARKS_24:

Repro16 REMARKS_24:

a ADDRESSEE16 REMARKS_13:

Draft16 REMARKS_13:

Reg16 REMARKS_25:

Repro16 REMARKS_25:

Reg16 REMARKS_26:

Repro16 REMARKS_26:

a ADDRESSEE16 REMARKS_14:

Draft16 REMARKS_14:

Reg16 REMARKS_27:

Repro16 REMARKS_27:

Reg16 REMARKS_28:

Repro16 REMARKS_28:

a ADDRESSEE16 REMARKS_15:

Draft16 REMARKS_15:

Reg16 REMARKS_29:

Repro16 REMARKS_29:

Reg16 REMARKS_30:

Repro16 REMARKS_30:

a ADDRESSEE16 REMARKS_16:

Draft16 REMARKS_16:

Reg16 REMARKS_31:

Repro16 REMARKS_31:

Reg16 REMARKS_32:

Repro16 REMARKS_32:

a ADDRESSEE16 REMARKS_17:

Draft16 REMARKS_17:

Reg16 REMARKS_33:

Repro16 REMARKS_33:

Reg16 REMARKS_34:

Repro16 REMARKS_34:

a ADDRESSEE16 REMARKS_18:

Draft16 REMARKS_18:

Reg16 REMARKS_35:

Repro16 REMARKS_35:

Reg16 REMARKS_36:

Repro16 REMARKS_36:

a ADDRESSEE16 REMARKS_19:

Draft16 REMARKS_19:

Reg16 REMARKS_37:

Repro16 REMARKS_37:

Reg16 REMARKS_38:

Repro16 REMARKS_38:

a ADDRESSEE16 REMARKS_20:

Draft16 REMARKS_20:

Reg16 REMARKS_39:

Repro16 REMARKS_39:

Reg16 REMARKS_40:

Repro16 REMARKS_40:

a ADDRESSEE16 REMARKS_21:

Draft16 REMARKS_21:

Reg16 REMARKS_41:

Repro16 REMARKS_41:

Reg16 REMARKS_42:

Repro16 REMARKS_42:

a ADDRESSEE16 REMARKS_22:

Draft16 REMARKS_22:

Reg16 REMARKS_43:

Repro16 REMARKS_43:

Reg16 REMARKS_44:

Repro16 REMARKS_44:

a ADDRESSEE16 REMARKS_23:

Draft16 REMARKS_23:

Reg16 REMARKS_45:

Repro16 REMARKS_45:

Reg16 REMARKS_46:

Repro16 REMARKS_46:

a ADDRESSEE16 REMARKS_24:

Draft16 REMARKS_24:

Reg16 REMARKS_47:

Repro16 REMARKS_47:

Reg16 REMARKS_48:

Repro16 REMARKS_48:

a ADDRESSEE16 REMARKS_25:

Draft16 REMARKS_25:

Reg16 REMARKS_49:

Repro16 REMARKS_49:

Reg16 REMARKS_50:

Repro16 REMARKS_50:

a ADDRESSEE16 REMARKS_26:

Draft16 REMARKS_26:

Reg16 REMARKS_51:

Repro16 REMARKS_51:

Reg16 REMARKS_52:

Repro16 REMARKS_52:

a ADDRESSEE16 REMARKS_27:

Draft16 REMARKS_27:

Reg16 REMARKS_53:

Repro16 REMARKS_53:

Reg16 REMARKS_54:

Repro16 REMARKS_54:

a ADDRESSEE16 REMARKS_28:

Draft16 REMARKS_28:

Reg16 REMARKS_55:

Repro16 REMARKS_55:

Reg16 REMARKS_56:

Repro16 REMARKS_56:

a ADDRESSEE16 REMARKS_29:

Draft16 REMARKS_29:

Reg16 REMARKS_57:

Repro16 REMARKS_57:

Reg16 REMARKS_58:

Repro16 REMARKS_58:

a ADDRESSEE16 REMARKS_30:

Draft16 REMARKS_30:

Reg16 REMARKS_59:

Repro16 REMARKS_59:

Reg16 REMARKS_60:

Repro16 REMARKS_60:

a ADDRESSEE16 REMARKS_31:

Draft16 REMARKS_31:

Reg16 REMARKS_61:

Repro16 REMARKS_61:

Reg16 REMARKS_62:

Repro16 REMARKS_62:

a ADDRESSEE16 REMARKS_32:

Draft16 REMARKS_32:

Reg16 REMARKS_63:

Repro16 REMARKS_63:

Reg16 REMARKS_64:

Repro16 REMARKS_64:

a ADDRESSEE16 REMARKS_33:

Draft16 REMARKS_33:

Reg16 REMARKS_65:

Repro16 REMARKS_65:

Reg16 REMARKS_66:

Repro16 REMARKS_66:

a ADDRESSEE16 REMARKS_34:

Draft16 REMARKS_34:

Reg16 REMARKS_67:

Repro16 REMARKS_67:

Reg16 REMARKS_68:

Repro16 REMARKS_68:

a ADDRESSEE16 REMARKS_35:

Draft16 REMARKS_35:

Reg16 REMARKS_69:

Repro16 REMARKS_69:

Reg16 REMARKS_70:

Repro16 REMARKS_70:

Draft15 TOTAL: 0

Reg15 TOTAL: 0

Repro15 TOTAL: 0

Reg15 TOTAL_2: 0

Repro15 TOTAL_2: 0

G PREPARED BY: Cindy Cash

H DATE: 6/8/18

I APPROVED BY: Arthur Hatfield

J DATE: 6/8/18

18 ESTIMATED TOTAL PRICE:

Page: 1 of: 1

Remarks: Block 12 & 13: Submit draft 7 calendar days following meeting. The Government will require up to 3 calendar days for review of draft. The Contractor shall make all required changes and have final available 2 calendar days after receipt of comments from the Government.

Block 14: All deliverables shall be submitted by email. The Government uses Microsoft Office Suite. List of additional stakeholders and all e-mail address will be provided by the COR.

17 PRICE GROUP:

9:

DIST STATEMENT: B

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: 2018-06-01T17:59Z Check the source to verify that this is the current version before use.

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

A CONTRACT LINE ITEM NO: 0002

B EXHIBIT: B

TDP:

TM:

OTHER: Misc

D SYSTEMITEM:

E CONTRACTPR NO: FA-8903-18-R-0064

F CONTRACTOR: TBD

1 DATA ITEM NO: B003

2 TITLE OF DATA ITEM: Presentation Material

3 SUBTITLE: N/A

4 AUTHORITY Data Acquisition Document No: DI-ADMN-81373

5 CONTRACT REFERENCE: PSW Para - 4.1.1, 4.2, 4.3

6 REQUIRING OFFICE: AFCEC/CZRx

7 DD 250 REQ: LT

10 FREQUENCY: As Required

12 DATE OF FIRST SUBMISSION: Block 16

8 APP CODE: A

11 AS OF DATE: N/A

13 DATE OF SUBSEQUENT SUBMISSION: Block 16 a ADDRESSEE16 REMARKS: AFCEC/CZRX

Draft16 REMARKS: 1

Reg16 REMARKS: 0

Repro16 REMARKS: 0

Reg16 REMARKS_2: 1

Repro16 REMARKS_2: 0 a ADDRESSEE16 REMARKS_2: Base POC

Draft16 REMARKS_2: 1

Reg16 REMARKS_3: 0

Repro16 REMARKS_3: 0

Reg16 REMARKS_4: 1

Repro16 REMARKS_4: 0 a ADDRESSEE16 REMARKS_3: 772 ESS/PKB

Draft16 REMARKS_3: 1

Reg16 REMARKS_5: 0

Repro16 REMARKS_5: 0

Reg16 REMARKS_6: 1

Repro16 REMARKS_6: 0 a ADDRESSEE16 REMARKS_4: Other Stakeholders

Draft16 REMARKS_4: 0

Reg16 REMARKS_7: 0

Repro16 REMARKS_7: 0

Reg16 REMARKS_8: 1

Repro16 REMARKS_8: 0 a ADDRESSEE16 REMARKS_5:

Draft16 REMARKS_5:

Reg16 REMARKS_9:

Repro16 REMARKS_9:

Reg16 REMARKS_10:

Repro16 REMARKS_10:

a ADDRESSEE16 REMARKS_6:

Draft16 REMARKS_6:

Reg16 REMARKS_11:

Repro16 REMARKS_11:

Reg16 REMARKS_12:

Repro16 REMARKS_12:

a ADDRESSEE16 REMARKS_7:

Draft16 REMARKS_7:

Reg16 REMARKS_13:

Repro16 REMARKS_13:

Reg16 REMARKS_14:

Repro16 REMARKS_14:

a ADDRESSEE16 REMARKS_8:

Draft16 REMARKS_8:

Reg16 REMARKS_15:

Repro16 REMARKS_15:

Reg16 REMARKS_16:

Repro16 REMARKS_16:

a ADDRESSEE16 REMARKS_9:

Draft16 REMARKS_9:

Reg16 REMARKS_17:

Repro16 REMARKS_17:

Reg16 REMARKS_18:

Repro16 REMARKS_18:

a ADDRESSEE16 REMARKS_10:

Draft16 REMARKS_10:

Reg16 REMARKS_19:

Repro16 REMARKS_19:

Reg16 REMARKS_20:

Repro16 REMARKS_20:

a ADDRESSEE16 REMARKS_11:

Draft16 REMARKS_11:

Reg16 REMARKS_21:

Repro16 REMARKS_21:

Reg16 REMARKS_22:

Repro16 REMARKS_22:

a ADDRESSEE16 REMARKS_12:

Draft16 REMARKS_12:

Reg16 REMARKS_23:

Repro16 REMARKS_23:

Reg16 REMARKS_24:

Repro16 REMARKS_24:

a ADDRESSEE16 REMARKS_13:

Draft16 REMARKS_13:

Reg16 REMARKS_25:

Repro16 REMARKS_25:

Reg16 REMARKS_26:

Repro16 REMARKS_26:

a ADDRESSEE16 REMARKS_14:

Draft16 REMARKS_14:

Reg16 REMARKS_27:

Repro16 REMARKS_27:

Reg16 REMARKS_28:

Repro16 REMARKS_28:

a ADDRESSEE16 REMARKS_15:

Draft16 REMARKS_15:

Reg16 REMARKS_29:

Repro16 REMARKS_29:

Reg16 REMARKS_30:

Repro16 REMARKS_30:

a ADDRESSEE16 REMARKS_16:

Draft16 REMARKS_16:

Reg16 REMARKS_31:

Repro16 REMARKS_31:

Reg16 REMARKS_32:

Repro16 REMARKS_32:

a ADDRESSEE16 REMARKS_17:

Draft16 REMARKS_17:

Reg16 REMARKS_33:

Repro16 REMARKS_33:

Reg16 REMARKS_34:

Repro16 REMARKS_34:

a ADDRESSEE16 REMARKS_18:

Draft16 REMARKS_18:

Reg16 REMARKS_35:

Repro16 REMARKS_35:

Reg16 REMARKS_36:

Repro16 REMARKS_36:

a ADDRESSEE16 REMARKS_19:

Draft16 REMARKS_19:

Reg16 REMARKS_37:

Repro16 REMARKS_37:

Reg16 REMARKS_38:

Repro16 REMARKS_38:

a ADDRESSEE16 REMARKS_20:

Draft16 REMARKS_20:

Reg16 REMARKS_39:

Repro16 REMARKS_39:

Reg16 REMARKS_40:

Repro16 REMARKS_40:

a ADDRESSEE16 REMARKS_21:

Draft16 REMARKS_21:

Reg16 REMARKS_41:

Repro16 REMARKS_41:

Reg16 REMARKS_42:

Repro16 REMARKS_42:

a ADDRESSEE16 REMARKS_22:

Draft16 REMARKS_22:

Reg16 REMARKS_43:

Repro16 REMARKS_43:

Reg16 REMARKS_44:

Repro16 REMARKS_44:

a ADDRESSEE16 REMARKS_23:

Draft16 REMARKS_23:

Reg16 REMARKS_45:

Repro16 REMARKS_45:

Reg16 REMARKS_46:

Repro16 REMARKS_46:

a ADDRESSEE16 REMARKS_24:

Draft16 REMARKS_24:

Reg16 REMARKS_47:

Repro16 REMARKS_47:

Reg16 REMARKS_48:

Repro16 REMARKS_48:

a ADDRESSEE16 REMARKS_25:

Draft16 REMARKS_25:

Reg16 REMARKS_49:

Repro16 REMARKS_49:

Reg16 REMARKS_50:

Repro16 REMARKS_50:

a ADDRESSEE16 REMARKS_26:

Draft16 REMARKS_26:

Reg16 REMARKS_51:

Repro16 REMARKS_51:

Reg16 REMARKS_52:

Repro16 REMARKS_52:

a ADDRESSEE16 REMARKS_27:

Draft16 REMARKS_27:

Reg16 REMARKS_53:

Repro16 REMARKS_53:

Reg16 REMARKS_54:

Repro16 REMARKS_54:

a ADDRESSEE16 REMARKS_28:

Draft16 REMARKS_28:

Reg16 REMARKS_55:

Repro16 REMARKS_55:

Reg16 REMARKS_56:

Repro16 REMARKS_56:

a ADDRESSEE16 REMARKS_29:

Draft16 REMARKS_29:

Reg16 REMARKS_57:

Repro16 REMARKS_57:

Reg16 REMARKS_58:

Repro16 REMARKS_58:

a ADDRESSEE16 REMARKS_30:

Draft16 REMARKS_30:

Reg16 REMARKS_59:

Repro16 REMARKS_59:

Reg16 REMARKS_60:

Repro16 REMARKS_60:

a ADDRESSEE16 REMARKS_31:

Draft16 REMARKS_31:

Reg16 REMARKS_61:

Repro16 REMARKS_61:

Reg16 REMARKS_62:

Repro16 REMARKS_62:

a ADDRESSEE16 REMARKS_32:

Draft16 REMARKS_32:

Reg16 REMARKS_63:

Repro16 REMARKS_63:

Reg16 REMARKS_64:

Repro16 REMARKS_64:

a ADDRESSEE16 REMARKS_33:

Draft16 REMARKS_33:

Reg16 REMARKS_65:

Repro16 REMARKS_65:

Reg16 REMARKS_66:

Repro16 REMARKS_66:

a ADDRESSEE16 REMARKS_34:

Draft16 REMARKS_34:

Reg16 REMARKS_67:

Repro16 REMARKS_67:

Reg16 REMARKS_68:

Repro16 REMARKS_68:

a ADDRESSEE16 REMARKS_35:

Draft16 REMARKS_35:

Reg16 REMARKS_69:

Repro16 REMARKS_69:

Reg16 REMARKS_70:

Repro16 REMARKS_70:

Draft15 TOTAL: 0

Reg15 TOTAL: 0

Repro15 TOTAL: 0

Reg15 TOTAL_2: 0

Repro15 TOTAL_2: 0

G PREPARED BY: Cindy Cash

H DATE: 6/8/18

I APPROVED BY: Arthur Hatfield

J DATE: 6/8/18

18 ESTIMATED TOTAL PRICE:

Page: 1 of: 1

Remarks: Block 12 & 13: Submit draft 7 calendar days prior to the scheduled meeting. The government will require up to 3 calendar days for review of draft. The contractor shall make all required changes and have final available 2 calendar days prior to the scheduled meeting.

Block 14: All deliverables shall be submitted by email. List of additional stakeholders and all E-mail addresses will be provided by the COR.

17 PRICE GROUP:

9:

DIST STATEMENT: B

Source: https://assist.dla.mil -- Downloaded: 2018-06-01T18:02Z

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

A CONTRACT LINE ITEM NO: 0002

B EXHIBIT: B

TDP:

TM:

OTHER: Misc

D SYSTEMITEM:

E CONTRACTPR NO: FA-8903-18-R-0065

F CONTRACTOR: TBD

1 DATA ITEM NO: B004

2 TITLE OF DATA ITEM: Contract Work Breakdown Structure

3 SUBTITLE: N/A

4 AUTHORITY Data Acquisition Document No: DI-MGMT-81334D

5 CONTRACT REFERENCE: PSW Para - 4.5

6 REQUIRING OFFICE: AFCEC/CZRX

7 DD 250 REQ: LT

10 FREQUENCY: As Required

12 DATE OF FIRST SUBMISSION: Block 16

8 APP CODE: A

11 AS OF DATE: N/A

13 DATE OF SUBSEQUENT SUBMISSION: Block 16 a ADDRESSEE16 REMARKS: AFCEC/CZRX

Draft16 REMARKS: 0

Reg16 REMARKS: 0

Repro16 REMARKS: 0

Reg16 REMARKS_2: 1

Repro16 REMARKS_2: 0 a ADDRESSEE16 REMARKS_2: Base POC

Draft16 REMARKS_2: 0

Reg16 REMARKS_3: 0

Repro16 REMARKS_3: 0

Reg16 REMARKS_4: 1

Repro16 REMARKS_4: 0 a ADDRESSEE16 REMARKS_3: 772 ESS/PKB

Draft16 REMARKS_3: 0

Reg16 REMARKS_5: 0

Repro16 REMARKS_5: 0

Reg16 REMARKS_6: 1

Repro16 REMARKS_6: 0 a ADDRESSEE16 REMARKS_4:

Draft16 REMARKS_4:

Reg16 REMARKS_7:

Repro16 REMARKS_7:

Reg16 REMARKS_8:

Repro16 REMARKS_8:

a ADDRESSEE16 REMARKS_5:

Draft16 REMARKS_5:

Reg16 REMARKS_9:

Repro16 REMARKS_9:

Reg16 REMARKS_10:

Repro16 REMARKS_10:

a ADDRESSEE16 REMARKS_6:

Draft16 REMARKS_6:

Reg16 REMARKS_11:

Repro16 REMARKS_11:

Reg16 REMARKS_12:

Repro16 REMARKS_12:

a ADDRESSEE16 REMARKS_7:

Draft16 REMARKS_7:

Reg16 REMARKS_13:

Repro16 REMARKS_13:

Reg16 REMARKS_14:

Repro16 REMARKS_14:

a ADDRESSEE16 REMARKS_8:

Draft16 REMARKS_8:

Reg16 REMARKS_15:

Repro16 REMARKS_15:

Reg16 REMARKS_16:

Repro16 REMARKS_16:

a ADDRESSEE16 REMARKS_9:

Draft16 REMARKS_9:

Reg16 REMARKS_17:

Repro16 REMARKS_17:

Reg16 REMARKS_18:

Repro16 REMARKS_18:

a ADDRESSEE16 REMARKS_10:

Draft16 REMARKS_10:

Reg16 REMARKS_19:

Repro16 REMARKS_19:

Reg16 REMARKS_20:

Repro16 REMARKS_20:

a ADDRESSEE16 REMARKS_11:

Draft16 REMARKS_11:

Reg16 REMARKS_21:

Repro16 REMARKS_21:

Reg16 REMARKS_22:

Repro16 REMARKS_22:

a ADDRESSEE16 REMARKS_12:

Draft16 REMARKS_12:

Reg16 REMARKS_23:

Repro16 REMARKS_23:

Reg16 REMARKS_24:

Repro16 REMARKS_24:

a ADDRESSEE16 REMARKS_13:

Draft16 REMARKS_13:

Reg16 REMARKS_25:

Repro16 REMARKS_25:

Reg16 REMARKS_26:

Repro16 REMARKS_26:

a ADDRESSEE16 REMARKS_14:

Draft16 REMARKS_14:

Reg16 REMARKS_27:

Repro16 REMARKS_27:

Reg16 REMARKS_28:

Repro16 REMARKS_28:

a ADDRESSEE16 REMARKS_15:

Draft16 REMARKS_15:

Reg16 REMARKS_29:

Repro16 REMARKS_29:

Reg16 REMARKS_30:

Repro16 REMARKS_30:

a ADDRESSEE16 REMARKS_16:

Draft16 REMARKS_16:

Reg16 REMARKS_31:

Repro16 REMARKS_31:

Reg16 REMARKS_32:

Repro16 REMARKS_32:

a ADDRESSEE16 REMARKS_17:

Draft16 REMARKS_17:

Reg16 REMARKS_33:

Repro16 REMARKS_33:

Reg16 REMARKS_34:

Repro16 REMARKS_34:

a ADDRESSEE16 REMARKS_18:

Draft16 REMARKS_18:

Reg16 REMARKS_35:

Repro16 REMARKS_35:

Reg16 REMARKS_36:

Repro16 REMARKS_36:

a ADDRESSEE16 REMARKS_19:

Draft16 REMARKS_19:

Reg16 REMARKS_37:

Repro16 REMARKS_37:

Reg16 REMARKS_38:

Repro16 REMARKS_38:

a ADDRESSEE16 REMARKS_20:

Draft16 REMARKS_20:

Reg16 REMARKS_39:

Repro16 REMARKS_39:

Reg16 REMARKS_40:

Repro16 REMARKS_40:

a ADDRESSEE16 REMARKS_21:

Draft16 REMARKS_21:

Reg16 REMARKS_41:

Repro16 REMARKS_41:

Reg16 REMARKS_42:

Repro16 REMARKS_42:

a ADDRESSEE16 REMARKS_22:

Draft16 REMARKS_22:

Reg16 REMARKS_43:

Repro16 REMARKS_43:

Reg16 REMARKS_44:

Repro16 REMARKS_44:

a ADDRESSEE16 REMARKS_23:

Draft16 REMARKS_23:

Reg16 REMARKS_45:

Repro16 REMARKS_45:

Reg16 REMARKS_46:

Repro16 REMARKS_46:

a ADDRESSEE16 REMARKS_24:

Draft16 REMARKS_24:

Reg16 REMARKS_47:

Repro16 REMARKS_47:

Reg16 REMARKS_48:

Repro16 REMARKS_48:

a ADDRESSEE16 REMARKS_25:

Draft16 REMARKS_25:

Reg16 REMARKS_49:

Repro16 REMARKS_49:

Reg16 REMARKS_50:

Repro16 REMARKS_50:

a ADDRESSEE16 REMARKS_26:

Draft16 REMARKS_26:

Reg16 REMARKS_51:

Repro16 REMARKS_51:

Reg16 REMARKS_52:

Repro16 REMARKS_52:

a ADDRESSEE16 REMARKS_27:

Draft16 REMARKS_27:

Reg16 REMARKS_53:

Repro16 REMARKS_53:

Reg16 REMARKS_54:

Repro16 REMARKS_54:

a ADDRESSEE16 REMARKS_28:

Draft16 REMARKS_28:

Reg16 REMARKS_55:

Repro16 REMARKS_55:

Reg16 REMARKS_56:

Repro16 REMARKS_56:

a ADDRESSEE16 REMARKS_29:

Draft16 REMARKS_29:

Reg16 REMARKS_57:

Repro16 REMARKS_57:

Reg16 REMARKS_58:

Repro16 REMARKS_58:

a ADDRESSEE16 REMARKS_30:

Draft16 REMARKS_30:

Reg16 REMARKS_59:

Repro16 REMARKS_59:

Reg16 REMARKS_60:

Repro16 REMARKS_60:

a ADDRESSEE16 REMARKS_31:

Draft16 REMARKS_31:

Reg16 REMARKS_61:

Repro16 REMARKS_61:

Reg16 REMARKS_62:

Repro16 REMARKS_62:

a ADDRESSEE16 REMARKS_32:

Draft16 REMARKS_32:

Reg16 REMARKS_63:

Repro16 REMARKS_63:

Reg16 REMARKS_64:

Repro16 REMARKS_64:

a ADDRESSEE16 REMARKS_33:

Draft16 REMARKS_33:

Reg16 REMARKS_65:

Repro16 REMARKS_65:

Reg16 REMARKS_66:

Repro16 REMARKS_66:

a ADDRESSEE16 REMARKS_34:

Draft16 REMARKS_34:

Reg16 REMARKS_67:

Repro16 REMARKS_67:

Reg16 REMARKS_68:

Repro16 REMARKS_68:

a ADDRESSEE16 REMARKS_35:

Draft16 REMARKS_35:

Reg16 REMARKS_69:

Repro16 REMARKS_69:

Reg16 REMARKS_70:

Repro16 REMARKS_70:

Draft15 TOTAL: 0

Reg15 TOTAL: 0

Repro15 TOTAL: 0

Reg15 TOTAL_2: 0

Repro15 TOTAL_2: 0

G PREPARED BY: Cindy Cash

H DATE: 6/8/18

I APPROVED BY: Arthur Hatfield

J DATE: 6/8/18

18 ESTIMATED TOTAL PRICE:

Page: 1 of: 1

Remarks: Block 12 & 13: Initial submittal is 15 calendar days after Contract award. Subsequent submissions shall be upon any changes to the WBS and shall be submitted within 10 days of the changes.

Block 14: All deliverables shall be submitted by e-mail. E-mail addresses will be provided by the COR.

17 PRICE GROUP:

9:

DIST STATEMENT: B

Title: Contract Work Breakdown Structure Number: DI-MGMT-81334D Approval Date: 20110518 AMSC Number: D9199 Limitation:

DTIC Applicable: GIDEP Applicable:

Preparing Activity: CAPE Applicable Forms: Not Applicable

Use/relationship: This documents the Contract Work Breakdown Structure (CWBS) and its extension by the contractor using terminology and definitions, as applicable, in MIL-

HDBK-881.

This DID summarizes the format for the CWBS and provides preparation instructions to support the data and frequency requirements specified in the contract. This DID applies to all contracts that require a Work Breakdown Structure (WBS). It is related to the four Contractor Cost Data Reporting (CCDR) formats: DD Form 1921, “Cost Data Summary Report” (DI-FNCL-81565); DD Form 1921-1, “Functional Cost-Hour Report” (DI-FNCL-81566); and DD Form 1921-2, “Progress Curve Report” (DI-FNCL-81567);

This DID is also related to the “Contract Performance Report” (DI-MGMT-81466) and DD Form 1586, “Contract Funds Status Report” (DI-MGMT-81468).

For those contracts with Cost and Software Data Reporting (CSDR) requirements, the CWBS must agree with the contract CSDR Plan approved by the Office of the Secretary of Defense (OSD) Deputy Director, Cost Assessment (DDCA).

The purpose and intent of the CWBS and CWBS dictionary is to document the contractor’s deliverable products and planned approach to performing the contract scope of work. It also contains the technical description of the military end item being developed/procured by the contract. The technical definitions and descriptions of each product-oriented (i.e., hardware) WBS element should be derived from the contractor’s systems engineering Integrated Product Team (IPT) or related technical department. The cost content of each WBS element definition should be produced by the contractor’s finance department.

MIL-HDBK-881 serves as the basis for developing the CWBS. Routine reporting shall be at CWBS level 3 for all contractors. Extensions of the CWBS can be tailored to the specific program but will be consistent with MIL-HDBK-881. More detailed reporting of the CWBS shall be required only for those lower-level elements that address high-risk, high-value, or high-technical-interest areas of a program. Identifying these additional elements for inclusion in the CWBS is a critical early assignment for the Cost Working- Group Integrated Product Team (CWIPT) for inclusion in the CWBS.

The reporting contractor must prepare and submit, using the CSDR Submit-Review System, the first contract CWBS Index and Dictionary at the same time the first Interim Report is due or, when the Initial Report, if required, is due. However, contractors also have the option to submit the Index and Dictionary earlier to facilitate report planning.

The reporting contractor must also maintain and update the Dictionary throughout the life of the contract. If changes to the CWBS occur, the contractor must submit an updated CWBS Index and Dictionary with the next affected CSD Reports. The contractor is not

Source: https://assist.dla.mil -- Downloaded: 2018-06-01T18:03Z

DI-MGMT-81334D

required to submit the updated CWBS Index and Dictionary more frequently than its CSDR submissions.

This DID supersedes DI-MGMT-81334C.

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 ASSIST at the time of the solicitation; or, for non-ASSIST documents, as stated herein.

2. References.

a. MIL-HDBK-881, “Work Breakdown Structures for Defense Materiel Items,” available at http://dcarc.pae.osd.mil.

b. DoD 5000.4-M, “Cost Analysis Guidance and Procedures,” [current version], available at http://www.dtic.mil/whs/directives/.

c. DoD 5000.04-M-1, “Cost and Software Data Reporting (CSDR) Manual,” [current version], available at http://www.dtic.mil/whs/directives/.

d. DD Form 2794, “Cost and Software Data Reporting Plan,” [current version], available at http://www.dtic.mil/whs/directives/. Commonly referred to as the CSDR Plan, a completed DD Form 2794 must be approved by the OSD DDCA.

3. Formats. The CWBS shall be reflected in an electronic report that consists of two parts. The first part, the CWBS Index, lists the individual elements by their CWBS Codes and Levels. The second part, the CWBS Dictionary, describes the effort and tasks associated with every CWBS element shown in the CWBS Index. Examples of the CWBS Index and CWBS Dictionary are shown in Figures 1 and 2, respectively. These are examples only, and are not intended to be a set format. If a contractor wishes to use an existing WBS internal to its organization, the contractor must first map their internal elements and definitions to the OSD DDCA-approved CSDR plan, and then develop a CWBS that conforms to the guidance in this DID.

The CWBS Dictionary must be submitted as a stand-alone Word-compatible file to the Defense Cost and Resource Center (DCARC) secure Web site using the CSDR Submit- Review System. Uploading requires the use of a DoD Common Access Card (CAC) or a DoD-approved External Certificate Authority (ECA) certificate. See the DCARC Web site for certificate instructions.

Preparation Instructions:

1. Contract Work Breakdown Structure Index:

a. CWBS Code. Enter the code, if applicable. The CWBS codes used in the CWBS Index and Dictionary must be identical to those in the OSD DDCA-approved contract CSDR Plan. The preferred convention is to use a numeric structure starting with 1.0 for the level 1 CWBS element (as displayed in Figure 1. CWBS Index Example). Every element on the OSD DDCA-approved CSDR Plan must be included in the Index, regardless of applicability on the contract. The http://dcarc.pae.osd.mil/� http://www.dtic.mil/whs/directives/� contractor must not include any elements that are not on the OSD DDCA-approved CSDR plan.

b. CWBS Element Level c.

. Enter the level of the CWBS element. Level 1 is the total contract. Levels 2, 3, and so on, are successively lower levels of the contract.

CWBS Element Name

2. Contract Work Breakdown Structure Dictionary:

. Enter the title of the CWBS element using the specific name or nomenclature. The CWBS element names used in the CWBS Index and Dictionary must be identical to those in the OSD DDCA-approved contract CSDR Plan.

a. CWBS Code b.

. Enter the same codes used in the Index.

CWBS Element Name c.

. Enter the same element names used in the Index.

CWBS Definition

The CWBS dictionary must also include a description of the cost and work content for each element. Cost content definitions must include explanations of recurring versus nonrecurring efforts, functional cost element inclusion or exclusion, and purchased versus made in-house decisions. The description of the cost content must also include characterizations by functional category (i.e., engineering, tooling, quality control, and manufacturing) as appropriate. The cost content portion of the definition for each element should be tied to the contractor’s control account, work package, and work scope definitions. The work content definition must include a short description of the process used to design, produce or sustain the end item or service. The description must address the types of activities (e.g., design, production, analysis, or management) included within the WBS element. These descriptions must include information on whether the reporting contractor or a supplier/subcontractor is performing the work being described.

. Enter a complete description of the technical, cost, and work content of each CWBS element. For the technical content, the dictionary must include a general system level description (i.e., highest level WBS element) of the military end item that captures top-level attributes of the system. If the system has a known official military designation (e.g., AN/ S L Q -32A (V)2), this designation should be included in the top-level description. The contractor must provide general descriptions of the physical characteristics of each individual element below the system level. It is important that the contractor specify all hardware and software equipment that are associated with each WBS element.

Each WBS element definition must provide the end user with the means to determine what the item is, what it does within the system, and how the item is physically defined.

CWBS dictionaries must reflect only the work being done on the contract for which the document is being submitted. If work is not expected to occur for a given WBS element, the CWBS dictionary definition must indicate that this element is not applicable. If work at some elements is being performed by a supplier/subcontractor, the dictionary must state this. Similarly, if the CWBS is for a subcontract/supplier, the work defined for each element must be specific to the subcontractor/supplier’s scope of effort, and must not include the prime contractor’s work. Definitions of a generic nature are acceptable for some parent level elements provided that more detailed definitions are given for the lower level elements. If there are GFE items being integrated into the end item, it is not expected that a detailed description of those items be provided, however, all GFE items being integrated into the system as part of the contract must be labeled as such in the CWBS dictionary under the appropriate elements.

Figure 1. CWBS Index Example (based on MIL-HDBK-881 Missile Systems)

Program: Vector Surface to Air Interceptor RFP NO: XXXXX Contract Plan No: A-10-X-C1 Contract No: DAAE07-XX-E-0001

DATE: 6/14/2010

CWBS CODE

1 2 3 4 5

1.0 X Vector Surface to Air Interceptor Missile System

1.1 X Air Vehicle

1.1.1 X Propulsion (Stages I...n,]

1.1.2 X Payload

1.1.3 X Airframe

1.1.4 X Reentry System

1.1.5 X Post Boost System

1.1.6 X Guidance and Control

1.1.6.1 X Guidance Section

1.1.6.1.1 X RF Active Seeker

1.1.6.1.2 X IF Receiver

1.1.6.1.3 X Digital Signal Processor

1.1.6.1.4 X Integration, Assembly, Test and Checkout

1.1.6.2 X Control Section

1.1.6.2.1 X Tail Fin Control Section

1.1.6.2.2 X Canards

1.1.6.2.3 X Integration, Assembly, Test and Checkout

1.1.7 X Ordnance Initiation Set

1.1.8 X Airborne Test Equipment

1.1.9 X Airborne Training Equipment

1.1.10 X Auxiliary Equipment

1.1.11 X Integration, Assembly, Test and Checkout

1.2 X Command and Launch

1.2.1 X Surveillance, Identification and Tracking Sensors

1.2.2 X Launch and Guidance Control

1.2.3 X Communications

1.2.4 X Command and Launch Applications Software

1.2.5 X Command and Launch System Software

1.2.6 X Launcher Equipment

1.2.7 X Auxiliary Equipment

1.2.8 X Booster Adapter

1.3 X System Engineering/Program Management

1.4 X System Test and Evaluation

1.4.1 X Development Test and Evaluation

1.4.2 X Operational Test and Evaluation

1.4.3 X Mock-ups / System Integration Labs (SILs)

1.4.4 X Test and Evaluation Support

1.4.5 X Test Facilities

1.5 X Training

1.5.1 X Equipment

1.5.2 X Services

1.5.3 X Facilities

1.6 X Data

1.6.1 X Technical Publications

1.6.2 X Engineering Data

1.6.3 X Management Data

1.6.4 X Support Data

1.6.5 X Data Depository

1.7 X Peculiar Support Equipment

1.7.1 X Test and Measurement Equipment

1.7.2 X Support and Handling Equipment

1.8 X Common Support Equipment

1.8.1 X Test and Measurement Equipment

1.8.2 X Support and Handling Equipment

1.9 X Operational/Site Activation

1.9.1 X System Assembly, Installation and Checkout on Site

1.9.2 X Contractor Technical Support

1.9.3 X Site Construction

1.9.4 X Site/Ship/Vehicle Conversion

1.10 X Industrial Facilities

1.10.1 X Construction/Conversion/Expansion

1.10.2 X Equipment Acquisition or Modernization

1.10.3 X Maintenance (Industrial Facilities)

1.11 X Initial Spares and Repair Parts

CWBS ELEMENT NAMECWBS ELEMENT

LEVEL

Contract Work Breakdown Structure Index

Figure 2. CWBS Dictionary Example

1.0 Vector Surface to Air Interceptor Missile System

1.1 Air Vehicle

1.1.1 Propulsion (Stages I...n,]

1.1.2 Payload

1.1.3 Airframe

1.1.4 Reentry System

1.1.5 Post Boost System

1.1.6 Guidance and Control

1.1.6.1 Guidance Section

1.1.6.1.1 RF Active Seeker

1.1.6.1.2 IF Receiver

1.1.6.1.3 Digital Signal Processor

1.1.6.1.4 Integration, Assembly, Test and Checkout

1.1.6.2 Control Section

1.1.6.2.1 Tail Fin Control Section

1.1.6.2.2 Canards

1.1.6.2.3 Integration, Assembly, Test and Checkout

This WBS element includes the cost of the Mk51 control surface tail f in control set.

This WBS element includes the cost of procurement, fabrication, assembly and test of the canard devices utilized to provide directional control to the missile in f light.

This WBS element includes the cost of all direct and indirect labor costs associated w ith integrating, assembling, testing and perform checkout procedures on the Control Section subassemblies in order to build up the complete Vector missile control section.

This element includes the cost of the Vector Missile Guidance Section. Cost for this element represent touch labor costs for the inspection, quality assurance, testing, recurring engineering design, and f inal assembly of all subassemblies into the completed Guidance set. Costs for purchased parts of children WBS elements are rolled up into and reported for this WBS element. There are no direct reporting CSDR requirements from any supplier or vendor for any component w ithin this WBS element.

This WBS element includes the cost of the Radio Frequency (RF) missile seeker that provides an all w eather capability. The RF active seeker is designed and manufactured at the prime contractors integration facility in Dallas, TX. The cost for this element includes the material cost for the subassemblies and direct and indirect labor associated w ith the IAT&C fo the subassemblies into the RF Active Seeker end-item.

This WBS element includes the cost of all the electronic circuitry and RF w aveguide.

This WBS element includes the cost of the tw o Texas Instruments TMS320C6414T/15T/16T DSPs that provide the signal processing capabilities for discrimination of the target from clutter and jammer returns in the received signal.

This WBS element includes the cost of all direct and indirect labor costs associated w ith integrating, assembling, testing and perform checkout procedures on the Guidance Section subassemblies in order to build up the complete Vector missile Guidance section.

This WBS element includes the cost of the Vector missile control section. The tail f in controls are equipment designed and manufactured in-house by the prime. Cost for the tail f in controls include engineering, tooling, quality control and manufacturing direct and indirect costs. The canard is a purchased item and its cost reflects the primes costs for direct and indirect labor for IAT&C of the canards into the control section of the missile.

This WBS element includes the cost of the Vector missile's rocket motor and labor required to integrate and assemble the propulsion system into the AUR. The single Thiokol TX-486-1 solid-fueled rocket motor is a subcontracted item but the cost falls under the threshold for "direct reporting" by the supplier. This WBS element captures the cost of the purchased solid rocket motor and IAT&C costs necessary to install, test and checkout the rocket motor inside the airframe. There is one TX-486-1 rocket motor per AUR.

This WBS element includes the cost of the Mk125 w arhead and labor required to integrate and assemble the w arhead into the AUR. The Vector payload consists of the Mk 125 Warhead and its support assemblies.

This element is a subcontracted item by the prime contractor. The dollar amount for this item is exceeds the dollar threshold for CSDR reporting and consequently the prime contractor has f low ed dow n CSDR reporting requirements to the supplier and provided the subcontractor w ith their CA-approved CSDR Subcontract plan.

Prime contractor recurring and non-recurring costs w ill capture the price paid for the Mk125 w arhead in addition to the prime's direct and indirect costs for integration, assembly, test and checkout of the Mk125 w arhead into the payload section of the missle. There is one Mk125 w arhead per AUR.

This element refers to labor and material costs associated w ith the components that comprise the airframe.

This WBS element is not applicable to the Vector Missile contract.

This WBS element includes the cost for the 1.1.6.1 Guidance Section and 1.1.6.2 Control Section. This parent element includes the cost of labor and material for the prime contractor and any subassembly manfactured and procured by outside vendors.

CWBS ELEMENT NAME CWBS DEFINITION

This WBS element includes the cost of the Vector missile All Up Round (AUR) in addition to the cost of the common WBS elements. The Vector missile is an Army Surface-to-Air interceptor missile providing 360 degree coverage for the air defense mission of forw ard deployed forces. It is a Single-stage, short-range, low -to high-altitude theater missile defense system that utilizes advanced guidance and control technologies including an advanced active RF seeker to extend the range of engagement beyond current and projected threats. This WBS element reports the total development or production cost, w hichever is applicable to the instant contract, of the All Up Round (AUR) through the cost for the common WBS elements. WBS elements

1.1 Air Vehicle and 1.2 Command and Launch are the tw o child WBS elements that capture the cost of the product, w hile WBS elements 1.3 through 1.1.1 capture the cost of the "common elements".

This element refers to the means for delivering the destructive effect to the target, including the capability to generate or receive intelligence to navigate and penetrate to the target area and to detonate the w arhead. This element includes the design, development, and production of complete units (prototype and operationally configured units, w hich satisfy the requirement of their applicable specif ications) regardless of their use. This WBS element has eleven children WBS elements.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it.