CDRLs A046 thru A081 15 May 2020.pdf

5/15/2020 7:21:51 AM CDT CDRL Table of Contents

CONTRACT #:

CONTRACTOR:

SET NAME: B-52 CERP/Engine SS SYSTEM ITEM: B-52 Commercial Engine Replacement Program

PROGRAM: B-52 CERP

DATA ITEM REQUIRING OFFICE AUTHORITY/TITLE/SUBTITLE SOW PARAGRAPH

A046 AFLCMC/WWDC DI-SESS-81521B/T BLK 16

Training Program Structure Document

A047 AFLCMC/WWDC DI-ILSS-80872/T BLK16

Training Materials

A048 AFLCMC/WWDC DI-MISC-80508B/T BLK16

Technical Report-Study/Services

Engineering Studies

A049 AFLCMC/WWDC DI-MISC-80508B/T BLK16

Technical Report-Study/Services

Shop Visit Report

A051 AFLCMC/WWDC DI-MISC-80508B/T BLK16

Technical Report-Study/Services

Long Term Commercial Repair Supportability Report

A054 AFLCMC/LPA DI-IPSC-81427B/T SOW PARA 4.4.18

Software Development Plan

Software Development Integrity Master Plan

A056 AFLCMC/LPA DI-MSSM-81966A/T SOW PARA 4.4.8

Gas Turbine Engine Steady State and Transient Performance Presentation for Computer Programs

A057 AFLCMC/LPA DI-MGMT-80934C SOW PARA 4.13

Operation Security (OPSEC) Plan

A059 AFLCMC/WWDC DI-MGMT-81453B BLK16

Data Accession List (DAL)

A060 AFLCMC/WWDC DI-MGMT-81808 BLK16

Contractor's Risk Management Plan

A061 AFLCMC/WWDC DI-MGMT-81809 BLK16

Risk Management Status Report

CERP Risk Management Status Report

A066 AFLCMC/LPA DI-MISC-80508B/T BLK16

Technical Report-Study/Services

Verification Matrix Development

5/15/2020 7:21:51 AM CDT CDRL Table of Contents

A072 AFLCMC/LPA DI-NDTI-80566A/T SOW Paragraph 4.4.10

Test Plan

Engine and Subsystem Test Plans

A073 AFLCMC/LPA DI-NDTI-80809B/T SOW PARA 4.4.11

Test/Inspection Report

A074 AFLCMC/LPA DI-SAFT-80101C SOW PARA 4.9.7

System Safety Hazard Analysis Report (SSHA)

A075 AFLCMC/WWDC DI-SAFT-80102C BLK16

Safety Assessment Report (SAR)

A077 AFLCMC/LPA DI-ADMN-81306 SOW Paragraph 4.15

Program Protection Implementation Plan (PPIP)

Program Security Plan

A081 AFLCMC/LPA DI-IPSC-81433A BLK16

Software Requirements Specification (SRS)

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.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement Program

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A046

2. TITLE OF DATA ITEM

Training Program Structure Document

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-SESS-81521B/T

5. CONTRACT REFERENCE

BLK 16

6. REQUIRING OFFICE

AFLCMC/WWDC

7. DD 250 REQ

DD

9. DIST STATEMENT

REQUIRED

BLK16

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

Block 4: This DID is tailored as follows: Delete 2.2.1 c, c1,c2,c3,c4,d, 2.2.4, 2.2.5, 2.3.1 l, m, o, q, r, t, u, v, w, x and

y. 2.3.2c and d. 2.3.4 b. 2.3.8 l, m, and n. 2.3.9 i, 2.3.13a, b, c, d, e, f, g, h, i, j, k, l, m, n, q, s, t, u, and v.

Block 5: The contract reference is stated in SOW paragraph 8.

Block 9: Distribution Statement D: Distribution authorized to the Department of Defense and US contractors only, operational use, 6 January 2020. Other requests shall be referred to AFLCMC/WWD.

Export Control Warning Notice: Warning- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, USC Section 2571 Et Seq) or the Export Administration Act of 1979 (Title 50, USC, App 2401 Et Seq), as amended. Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with provisions of DOD directives 5230.25.

Destruction Notice for Unclassified Documents: Destroyed by any method that will prevent disclosure of contents or reconstruction of the document.

Destruction Notice for Classified Documents: Follow the procedures in DOD 5220.22-M, National Industry Security Program Operating Manual (NISPOM), Section 5-705, or DOD 5200.01M, Information Security Program, Volume 3, Protection of Classified Information.

Block 10: The contractor shall submit the data NLT 90 calendar days of Government request.

Block 11: The as of date shall be accurate as of the date of submittal.

Block 12: The date of the first submission shall be NLT 90 calendar days of Government request.

Block 13: The date of the subsequent submission shall be for a second maintenance training class with 20 attendees covering the same material (with applicable updates) within 90 calendar days of the Government request.

Block 14: Deliverable shall be made to the B-52 CERP Configuration Management Office, Tinker AFB, OK. Contractors shall use the specified Configuration Management/Data Management (CM/DM) System in accordance with the Statement of Work.

AFLCMC/WWDC 1

15. TOTAL 0 1 0

G. PREPARED BY

shepherd.debra.1044063553 Debby Shepherd

H. DATE

2020/05/14

I. APPROVED BY

crowder.celia.dyanne.1162383848

J. DATE

2020/05/14

Contract Nr:

Mod#:

Exhibit:

Appendix B

18. ESTIMATED

TOTAL PRICE

17. PRICE GROUP

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED Page 1 of 2 Pages

A. CONTRACT LINE ITEM NO.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER SESS

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement Program

E. CONTRACT/PR NO.

F. CONTRACTOR

16. REMARKS (Continued) Format shall be compatible with the latest Adobe Acrobat Reader version in Portable Document Format (PDF) or the latest Microsoft Office file type. The contractor shall use US DOD PKI compliant encryption mechanism when submitting sensitive but unclassified data as attachments to emails. All CDRLs will be submitted in an editable (PDF) format.

Documents are to be clearly marked and NO CLASSIFIED data is ever sent or uploaded via the (CM/DM) System or normal e-mail channels.

Note: Government CDRL monitor will ensure personnel assigned to the following organizations have been granted access to MEARS or the current system the government is using: WWDC, DCMA, LPS and LPA as required.

DD FORM 1423-1, FEB 2001 Page 2 of 2 Pages

Contract Nr:

Exhibit:

Source: http://assist.dla.mil -- Downloaded: 2019-06-25T13:59Z Check the source to verify that this is the current version before use.

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

XX

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

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.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER ILSS

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement Program

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A047

2. TITLE OF DATA ITEM

Training Materials

3. SUBTITLE

4. AUTHORITY (Data Acquisition Document No.)

DI-ILSS-80872/T

5. CONTRACT REFERENCE

BLK16

6. REQUIRING OFFICE

AFLCMC/WWDC

7. DD 250 REQ

DD

9. DIST STATEMENT

REQUIRED

BLK16

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

Block 4: This DID is tailored as follows: Delete all the requirements for audio visual instructions and material and paragraph 10.2.1.2 in its entirety.

Block 5: The contract reference is stated in SOW paragraph 8.

Block 9: Distribution Statement D: Distribution authorized to the Department of Defense and US contractors only, operational use, 6 January 2020. Other requests shall be referred to AFLCMC/WWD.

Export Control Warning Notice: Warning- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, USC Section 2571 Et Seq) or the Export Administration Act of 1979 (Title 50, USC, App 2401 Et Seq), as amended. Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with provisions of DOD directives 5230.25.

Destruction Notice for Unclassified Documents: Destroyed by any method that will prevent disclosure of contents or reconstruction of the document.

Destruction Notice for Classified Documents: Follow the procedures in DOD 5220.22-M, National Industry Security Program Operating Manual (NISPOM), Section 5-705, or DOD 5200.01M, Information Security Program, Volume 3, Protection of Classified Information.

Block 10: The contractor shall submit the data NLT 30 calendar days after the contract is awarded.

Block 11: The as of date shall be accurate as of the date of submittal.

Block 12: The date of the first submission shall be prepared and ready to be able to train personnel at least 45 calendar prior to the delivery of the first fully mission capable aircraft.

Block 13: The date of subsequent submission shall be when changes occur to the engine which will affect how maintenance actions are completed and training materials need to be changed.

Block 14: Deliverable shall be made to the B-52 CERP Configuration Management Office, Tinker AFB, OK. Contractors shall use the specified Configuration Management/Data Management (CM/DM) System in accordance with the Statement of Work.

AFLCMC/WWDC 1

15. TOTAL 0 1 0

G. PREPARED BY

shepherd.debra.1044063553 Debby Shepherd

H. DATE

2020/05/14

I. APPROVED BY

crowder.celia.dyanne.1162383848

J. DATE

2020/05/14

18. ESTIMATED

TOTAL PRICE

A. CONTRACT LINE ITEM NO.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER ILSS

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement

Format shall be compatible with the latest Adobe Acrobat Reader version in Portable Document Format (PDF) or the latest Microsoft Office file type. The contractor shall use US DOD PKI compliant encryption mechanism when submitting sensitive but unclassified data as attachments to emails. All CDRLs will be submitted in an editable (PDF) format.

Documents are to be clearly marked and NO CLASSIFIED data is ever sent or uploaded via the (CM/DM) System or normal e-mail channels.

Note: Government CDRL monitor will ensure personnel assigned to the following organizations have been granted access to MEARS or the current system the government is using: WWDC, DCMA, LPS and LPA as required.

DD FORM 1423-1, FEB 2001 Page 2 of 2 Pages

Contract Nr:

Exhibit:

Source: http://assist.dla.mil -- Downloaded: 2019-06-13T20:09Z

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.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER MISC

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement Program

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A048

2. TITLE OF DATA ITEM

Technical Report-Study/Services

3. SUBTITLE

Engineering Studies

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508B/T

5. CONTRACT REFERENCE

BLK16

6. REQUIRING OFFICE

AFLCMC/WWDC

7. DD 250 REQ

DD

9. DIST STATEMENT

REQUIRED

BLK16

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

Block 4: This DID is tailored as follows: 3.d. Section II - delete.

Block 5: The contract reference is stated in SOW paragraph 4.4.5.

Block 9: Distribution Statement D: Distribution authorized to the Department of Defense and US contractors only, operational use, 6 January 2020. Other requests shall be referred to AFLCMC/WWD.

Export Control Warning Notice: Warning- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, USC Section 2571 Et Seq) or the Export Administration Act of 1979 (Title 50, USC, App 2401 Et Seq), as amended. Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with provisions of DOD directives 5230.25.

Destruction Notice for Unclassified Documents: Destroyed by any method that will prevent disclosure of contents or reconstruction of the document.

Destruction Notice for Classified Documents: Follow the procedures in DOD 5220.22-M, National Industry Security Program Operating Manual (NISPOM), Section 5-705, or DOD 5200.01M, Information Security Program, Volume 3, Protection of Classified Information.

Block 10: The contractor shall submit the data as requested.

Block 11: The as of date shall be accurate as of the date of submittal.

Block 12: The date of the first submission shall be as requested.

Block 13: The date of subsequent submission shall be as requested.

Block 14: Deliverable shall be made to the B-52 CERP Configuration Management Office, Tinker AFB, OK. Contractors shall use the specified Configuration Management/Data Management (CM/DM) System in accordance with the Statement of Work.

Format shall be compatible with the latest Adobe Acrobat Reader version in Portable Document Format (PDF) or the latest Microsoft Office file type. The contractor shall use US DOD PKI compliant encryption mechanism when submitting sensitive but unclassified data as attachments to emails. All CDRLs will be submitted in an editable (PDF) format.

Documents are to be clearly marked and NO CLASSIFIED data is ever sent or uploaded via the (CM/DM) System or normal e-mail channels.

AFLCMC/WWDC 1

15. TOTAL 0 1 0

G. PREPARED BY

shepherd.debra.1044063553 Debby Shepherd

H. DATE

2020/05/14

I. APPROVED BY

crowder.celia.dyanne.1162383848

J. DATE

2020/05/14

18. ESTIMATED

TOTAL PRICE

A. CONTRACT LINE ITEM NO.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER MISC

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement

Note: Government CDRL monitor will ensure personnel assigned to the following organizations have been granted access to MEARS or the current system the government is using: WWDC, DCMA, LPS and LPA as required.

DD FORM 1423-1, FEB 2001 Page 2 of 2 Pages

Contract Nr:

Exhibit:

DATA ITEM DESCRIPTION

Title: Technical Report–Study/Services

Number: DI-MISC-80508B Approval Date: 14 Nov 2006 AMSC Number: 7633 Limitation: N/A DTIC Applicable: Yes Defense Technical Information Center (DTIC), 8725 John J. Kingman Rd.

Suite. 0944, Fort Belvoir, VA 22060-6218 GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: A technical report provides fully documented results of studies or analysis performed.

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

This DID supersede DI-MISC-80508A

Requirements:

1. Reference documents. None.

2. Format.

(a) The report and all attachments shall be typewritten, or otherwise clearly lettered, and shall be duplicated using non-fading ink.

(b) Text shall be prepared on standard letter size paper (8 ½ x 11”) .

(c) When attachments are included, they shall be fully identified, referenced in the text, and folded to conform to the size paper used in the report.

(d) Security classification and distribution markings shall conform to the requirements of the contract, purchase description and security requirements checklist, as applicable.

Source: http://assist.dla.mil -- Downloaded: 2019-03-15T19:38Z

DI-MISC-80508B

3. Contents.

(a) Title Page – Identifies the report by providing contract number, project name or purchase description title, task number, and reporting period.

(b) Table of Contents.

(c) Section I – Includes the following:

(1) Introduction

(2) Summary – A brief statement of results obtained for the analytic effort.

(3) Conclusions and their condensed technical substantiation’s.

(d) Section II – A complete and detailed description of the analytic results which led to the conclusions stated in Section I above.

4. END OF DI-MISC-80508B

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.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER MISC

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement Program

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A049

2. TITLE OF DATA ITEM

Technical Report-Study/Services

3. SUBTITLE

Shop Visit Report

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508B/T

5. CONTRACT REFERENCE

BLK16

6. REQUIRING OFFICE

AFLCMC/WWDC

7. DD 250 REQ

DD

9. DIST STATEMENT

REQUIRED

BLK16

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

Block 4: This DID is tailored as follows: Delete-Section II, Add- SOW Attachment N, Shop Visit Report.

Block 5: The contract reference is stated in SOW paragraph 7, 7.2.1, 7.2.2d and 7.2.4.

Block 9: Distribution Statement D: Distribution authorized to the Department of Defense and US contractors only, operational use, 6 January 2020. Other requests shall be referred to AFLCMC/WWD.

Export Control Warning Notice: Warning- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, USC Section 2571 Et Seq) or the Export Administration Act of 1979 (Title 50, USC, App 2401 Et Seq), as amended. Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with provisions of DOD directives 5230.25.

Destruction Notice for Unclassified Documents: Destroyed by any method that will prevent disclosure of contents or reconstruction of the document.

Destruction Notice for Classified Documents: Follow the procedures in DOD 5220.22-M, National Industry Security Program Operating Manual (NISPOM), Section 5-705, or DOD 5200.01M, Information Security Program, Volume 3, Protection of Classified Information.

Block 10: The contractor shall submit the data within five (5) working days of completion of maintenance actions.

Block 11: The as of date shall be accurate as of the date of submittal.

Block 12: The date of the first submission shall be within five (5) working days of completion of maintenance actions to return engine/LRU to serviceable condition.

Block 13: The date of subsequent submission shall be within five (5) working days of completion of maintenance actions to return engine/LRU to serviceable condition.

Block 14: Deliverable shall be made to the B-52 CERP Configuration Management Office, Tinker AFB, OK. Contractors shall use the specified Configuration Management/Data Management (CM/DM) System in accordance with the Statement of Work.

AFLCMC/WWDC 1

15. TOTAL 0 1 0

G. PREPARED BY

shepherd.debra.1044063553 Debby Shepherd

H. DATE

2020/05/14

I. APPROVED BY

crowder.celia.dyanne.1162383848

J. DATE

2020/05/14

18. ESTIMATED

TOTAL PRICE

A. CONTRACT LINE ITEM NO.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER MISC

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement

Format shall be compatible with the latest Adobe Acrobat Reader version in Portable Document Format (PDF) or the latest Microsoft Office file type. The contractor shall use US DOD PKI compliant encryption mechanism when submitting sensitive but unclassified data as attachments to emails. All CDRLs will be submitted in an editable (PDF) format.

Documents are to be clearly marked and NO CLASSIFIED data is ever sent or uploaded via the (CM/DM) System or normal e-mail channels.

Note: Government CDRL monitor will ensure personnel assigned to the following organizations have been granted access to MEARS or the current system the government is using: WWDC, DCMA, LPS and LPA as required.

DD FORM 1423-1, FEB 2001 Page 2 of 2 Pages

Contract Nr:

Exhibit:

Number: DI-MISC-80508B Approval Date: 14 Nov 2006 AMSC Number: 7633 Limitation: N/A DTIC Applicable: Yes Defense Technical Information Center (DTIC), 8725 John J. Kingman Rd.

Suite. 0944, Fort Belvoir, VA 22060-6218 GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: A technical report provides fully documented results of studies or analysis performed.

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

This DID supersede DI-MISC-80508A

Requirements:

1. Reference documents. None.

2. Format.

(a) The report and all attachments shall be typewritten, or otherwise clearly lettered, and shall be duplicated using non-fading ink.

(b) Text shall be prepared on standard letter size paper (8 ½ x 11”) .

(c) When attachments are included, they shall be fully identified, referenced in the text, and folded to conform to the size paper used in the report.

(d) Security classification and distribution markings shall conform to the requirements purchase description title, task number, and reporting period.

(b) Table of Contents.

(c) Section I – Includes the following:

(1) Introduction

(2) Summary – A brief statement of results obtained for the analytic effort.

(3) Conclusions and their condensed technical substantiation’s.

(d) Section II – A complete and detailed description of the analytic results which led to the conclusions stated in Section I above.

4. END OF DI-MISC-80508B

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.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER MISC

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement Program

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A051

2. TITLE OF DATA ITEM

Technical Report-Study/Services

3. SUBTITLE

Long Term Commercial Repair Supportability Report

4. AUTHORITY (Data Acquisition Document No.)

DI-MISC-80508B/T

5. CONTRACT REFERENCE

BLK16

6. REQUIRING OFFICE

AFLCMC/WWDC

7. DD 250 REQ

DD

9. DIST STATEMENT

REQUIRED

BLK16

10. FREQUENCY

BLK16

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

Block 4: This DID is tailored as follows: Delete 3(a)-3(d).

Block 5: The contract reference is stated in SOW paragraph 5.5.

Block 9: Distribution Statement D: Distribution authorized to the Department of Defense and US DOD contractors only, operational use, 6 January 2020. Other requests shall be referred to AFLCMC/WWD.

Export Control Warning Notice: Warning- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, USC Section 2571 Et Seq) or the Export Administration Act of 1979 (Title 50, USC, App 2401 Et Seq), as amended. Violations of these export laws are subject to severe criminal penalties.

Disseminate in accordance with provisions of DOD directives 5230.25.

Destruction Notice for Unclassified Documents: Destroyed by any method that will prevent disclosure of contents or reconstruction of the document.

Destruction Notice for Classified Documents: Follow the procedures in DOD 5220.22-M, National Industry Security Program Operating Manual (NISPOM), Section 5-705, or DOD 5200.01M, Information Security Program, Volume 3, Protection of Classified Information.

Block 10: The contractor shall submit the data NLT 30 calendar days after the government request.

Block 11: The as of date shall be accurate as of the date of submittal.

Block 12: The date of the first submission shall be at the time of the first Production Engine delivery.

Block 13: The date of subsequent submission shall be at the End of Contract.

Block 14: Deliverable shall be made to the B-52 CERP Configuration Management Office, Tinker AFB, OK. Contractors shall use the specified Configuration Management/Data Management (CM/DM) System in accordance with the Statement of Work.

Format shall be compatible with the latest Adobe Acrobat Reader version in Portable Document Format (PDF) or the latest Microsoft Office file type. The contractor shall use US DOD PKI compliant encryption mechanism when submitting sensitive but unclassified data as attachments to emails. All CDRLs will be submitted in an editable (PDF) format.

AFLCMC/WWDC 1

15. TOTAL 0 1 0

G. PREPARED BY

shepherd.debra.1044063553 Debby Shepherd

H. DATE

2020/05/14

I. APPROVED BY

crowder.celia.dyanne.1162383848

J. DATE

2020/05/14

18. ESTIMATED

TOTAL PRICE

A. CONTRACT LINE ITEM NO.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER MISC

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement

Documents are to be clearly marked and NO CLASSIFIED data is ever sent or uploaded via the (CM/DM) System or normal e-mail channels.

Note: Government CDRL monitor will ensure personnel assigned to the following organizations have been granted access to MEARS or the current system the government is using: WWDC, DCMA, LPS and LPA as required.

DD FORM 1423-1, FEB 2001 Page 2 of 2 Pages

Contract Nr:

Exhibit:

Number: DI-MISC-80508B Approval Date: 14 Nov 2006 AMSC Number: 7633 Limitation: N/A DTIC Applicable: Yes Defense Technical Information Center (DTIC), 8725 John J. Kingman Rd.

Suite. 0944, Fort Belvoir, VA 22060-6218 GIDEP Applicable: No Office of Primary Responsibility: NS/DA02 Applicable Forms: N/A

Use/relationship: A technical report provides fully documented results of studies or analysis performed.

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

This DID supersede DI-MISC-80508A

Requirements:

1. Reference documents. None.

2. Format.

(a) The report and all attachments shall be typewritten, or otherwise clearly lettered, and shall be duplicated using non-fading ink.

(b) Text shall be prepared on standard letter size paper (8 ½ x 11”) .

(c) When attachments are included, they shall be fully identified, referenced in the text, and folded to conform to the size paper used in the report.

(d) Security classification and distribution markings shall conform to the requirements purchase description title, task number, and reporting period.

(b) Table of Contents.

(c) Section I – Includes the following:

(1) Introduction

(2) Summary – A brief statement of results obtained for the analytic effort.

(3) Conclusions and their condensed technical substantiation’s.

(d) Section II – A complete and detailed description of the analytic results which led to the conclusions stated in Section I above.

4. END OF DI-MISC-80508B

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.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER IPSC

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement Program

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

A054

2. TITLE OF DATA ITEM

Software Development Plan

3. SUBTITLE

Software Development Integrity Master Plan

4. AUTHORITY (Data Acquisition Document No.)

DI-IPSC-81427B/T

5. CONTRACT REFERENCE

SOW PARA 4.4.18

6. REQUIRING OFFICE

AFLCMC/LPA

7. DD 250 REQ

DD

9. DIST STATEMENT

REQUIRED

BLK16

10. FREQUENCY

ONE/R

12. DATE OF FIRST SUBMISSION

BLK16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE

A

11. AS OF DATE

BLK16

13. DATE OF SUBSEQUENT

SUBMISSION

BLK16

Draft

Final

Reg Repro

16. REMARKS

Block 4: The DID is tailored as follows:

Paragraph 3.8.b.1 is replaced with:

3.8.b.1 Software Engineering Environment. This section shall be divided into the following paragraphs to describe the software engineering environment. Each paragraph shall describe the purpose of each item, and identify any classified processing or other security or privacy issues associated with the items.

3.8.b.1.1 Software Items. This paragraph shall identify by name, number, and version, as applicable, the software items (e.g., operating systems, languages, graphical development environments, compilers, communications software, related application software, databases, input files, code auditors, dynamic path analyzers, test drivers, preprocessors, test data generators, test control software, other special test software, post-processors) necessary to perform the planned development or engineering activities.

3.8.b.1.2 Hardware and Firmware items. This paragraph shall identify by name, number, and version, as applicable, the computer hardware, interfacing equipment, communications equipment, test data reduction equipment, apparatus such as extra peripherals, test message generators, test timing devices, test event records, etc., and firmware items that will be used in the software engineering environment.

Paragraph 3.8.b.2 is replaced with:

3.8.b.2 Software Test Environment. This section shall be divided into the following paragraphs to describe the software test environment at each intended test site. Each paragraph shall describe the purpose of each item, state the period of usage and the number of each item needed, identify those that are expected to be supplied by the site, and identify any classified processing or other security or privacy issues associated with the items.

3.8.b.2.1 Software Items. This paragraph shall identify by name, number, and version, as applicable, the software items (e.g., operating systems, compilers, communications software, related application software, databases, input files, code auditors, dynamic path analyzers, test drivers, preprocessors, test data generators, test control software, other special test software, post-processors) necessary to perform the planned testing activities at the test site(s).

3.8.b.2.2 Hardware and Firmware items. This paragraph shall identify by name, number, and version, as applicable, the computer hardware, interfacing equipment, communications equipment, test data reduction equipment, apparatus such as extra peripherals, test message generators, test timing devices, test event records, etc., and firmware items that will be used in the software test environment at the test site(s).

3.8.b.2.3 Installation, Testing, and Control. This paragraph shall identify the plans for performing each of the following at the test site(s):

a. Acquiring or developing each element of the software test environment

AFLCMC/WWDC 1

15. TOTAL 0 1 0

G. PREPARED BY

shepherd.debra.1044063553 Debby Shepherd

H. DATE

2020/05/14

I. APPROVED BY

crowder.celia.dyanne.1162383848

J. DATE

2020/05/14

18. ESTIMATED

TOTAL PRICE

A. CONTRACT LINE ITEM NO.

XX21

B. EXHIBIT

Appendix B

C. CATEGORY:

TDP TM OTHER IPSC

D. SYSTEM/ITEM

B-52 Commercial Engine Replacement

b. Installing and testing each item of the software test environment prior to its use

c. Controlling and maintaining each item of the software test environment

Block 9: Distribution Statement D: Distribution authorized to the Department of Defense and US contractors only, operational use, 6 January 2020. Other requests shall be referred to AFLCMC/WWD.

Export Control Warning Notice: Warning- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, USC Section 2571 Et Seq) or the Export Administration Act of 1979 (Title 50, USC, App 2401 Et Seq), as amended. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DOD directives 5230.25.

Destruction Notice for Unclassified Documents: Destroyed by any method that will prevent disclosure of contents or reconstruction of the document.

Destruction Notice for Classified Documents: Follow the procedures in DOD 5220.22-M, National Industry Security Program Operating Manual (NISPOM), Section 5-705, or DOD 5200.01M, Information Security Program, Volume 3, Protection of Classified Information.

Block 11: The as of date shall be accurate as of the date of submittal.

Block 12: The date of the first submission shall be 90 DAC.

Block 13: An update of the entire SDIMP shall be delivered 90 days prior to the First Engine to Test

(FETT).

Block 14: Contractor format is acceptable. The contract number, document name, CDRL number, date of submission and document number shall appear on the first page of the deliverable. Deliverable shall be made to the B-52 CERP Configuration Management Office, Tinker AFB, OK. Contractor shall use the specified Configuration Management/Data Management (CM/DM) System in accordance with the Statement of Work.

Format shall be compatible with the latest Adobe Acrobat Reader version in Portable Document Format (PDF) or the latest Microsoft Office file type. The contractor shall use US DOD PKI compliant encryption mechanism when submitting sensitive but unclassified data as attachments to emails. All CDRLs will be submitted in an editable (PDF) format.

Documents are to be clearly marked and NO CLASSIFIED data is ever sent or uploaded via the (CM/DM) System or normal e-mail channels.

Note: Government CDRL monitor will ensure personnel assigned to the following organizations have been granted access to MEARS or the current system the government is using: WWDC, DCMA, LPS and LPA as required.

DD FORM 1423-1, FEB 2001 Page 2 of 2 Pages

Contract Nr:

Exhibit:

Title: Software Development Plan (SDP)

Number: DI-IPSC-81427B Approval Date: 20170313

AMSC Number: N9775 Limitation: N/A

DTIC Applicable: No GIDEP Applicable: No

Preparing Activity: EC Project Number: IPSC-2017-001

Applicable Forms: N/A

Use/relationship: The Software Development Plan (SDP) with Agile, Cyber Security and Safety

Assurance contains the format, content, and delivery timeframes for the SDP. The SDP provides the acquirer insight into, and a tool for monitoring, the processes to be followed for software development, the methods to be used, the approach to be followed for each activity, and project schedules, organization, and resources. This DID is useful for new development, modification, reuse, reengineering, maintenance, and other activities resulting in software products.

This Data Item Description contains the format, content, and intended use information for the data product resulting from the work task described by the contract.

This DID supersedes DI-IPSC-81427A.

Requirements:

1. Referenced documents. This section shall list the number, title, revision, and date of all documents referenced in this plan. This section shall also identify the source for all documents not available through normal Government stocking activities. The complete address or website or other conditions for availability will be described.

2. Format. The SDP shall adhere to the format described under Content.

3. Content:

3.1. Identification. This paragraph shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).

3.2. System overview. This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance; identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents.

Source: http://assist.dla.mil -- Downloaded: 2019-03-15T19:18Z

DI-IPSC-81427B

3.3. Document overview. This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.

3.4. Relationship to other plans. This paragraph shall describe the relationship, if any, of the

SDP to other project management plans.

3.5. Overview of required work. This section shall be divided into paragraphs as needed to establish the context for the planning described in later sections. It shall include, as applicable, an overview of:

a. Requirements and constraints on the system and software to be developed

b. Requirements and constraints on project documentation

c. Position of the project in the system life cycle

d. The selected program/acquisition strategy or any requirements or constraints on it

e. Requirements and constraints on project schedules and resources

f. Other requirements and constraints, such as on project security, privacy, methods, standards, interdependencies in hardware and software development, etc.

3.6. Plans for performing general software development activities. This section shall be divided into the following paragraphs. Provisions corresponding to non-required activities may be satisfied by the words "Not applicable." If different builds or different software on the project require different planning, these differences shall be noted in the paragraphs. In addition to the content specified below, each paragraph shall identify applicable risks/uncertainties and plans for dealing with them.

a. Software development process. This paragraph shall describe the software development process to be used. The planning shall cover all contractual clauses concerning this topic, identifying planned builds, if applicable, their objectives, and the software development activities to be performed in each build. This paragraph shall include why the approach was chosen and provide a description of previous experience in developing software of the same nature as being acquired.

b. If the software development process is an Agile process, the following must be addressed within this section or subsection(s):

1. Cite the Agile technique(s) being employed (Scrum, pair programming, extreme programming, etc.).

2. For each Agile technique employed, describe your approach.

3. Describe the approach for release planning.

4. For Scrum, identify the sprint length and how it was determined.

5. Describe how the backlog is initially established, and the process for modifying and re-prioritizing it.

6. For Scrum, describe the typical sprint activities, and what happens during each iteration.

7. Identify the Product Owner and his/her roles/responsibilities.

8. Describe the acquirer’s role in the sprints if the customer is not also the

Product Owner.

9. Describe the mechanism for getting acquirer ( or end user) feedback for each sprint.

10. Describe how the product (working, useful piece of software) will be demonstrated to the Product Owner after each sprint (e.g., live demo on real equipment, in the lab with sim/stim, PowerPoint slides, etc.).

11. Describe the handling of incomplete user stories, unsatisfactory user stories, and bugs, and how they are factored back into the backlog.

12. Describe your Configuration Management process for keeping track of which user stories passed without any rework needed, which require rework, and which failed.

13. Describe your approach to artifact delivery; when documents such as the SRS, SDD, Software Test Plan and System Integration Plan will be available.

14. Discuss your approach to refactoring.

15. List and describe the software metrics to be used.

16. Discuss your approach to paying off technical debt.

17. Describe how you will determine story points for the velocity metric.

18. Describe your Integrated Requirements Toolset (IRT) that traces user stories to mission threads and KPPs, and whether this is a commercial tool or a tool developed by your organization.

19. Describe how software development activities will be coordinated with the

Integration and Test (I&T) team, and how it will be assured that the I&T team can keep up with testing all the software releases.

20. Describe how sprint-to-sprint dependencies (related to product and development resources) will be resolved and factored into the Sprint/Release

Plan.

21. Describe your strategy/mechanism for keep multiple sprint teams in sync.

22. Describe how the integrity of the baseline is maintained for use in the development of the next sprint.

23. Describe how regression testing will be conducted for each sprint release for all previous functions released.

24. Describe how automated testing techniques will be used for sprint and/or regression testing.

25. Describe how the software development effort will be synchronized and coordinated with systems engineering activities and reviews.

3.7. General plans for software development. This paragraph shall be divided into the following subparagraphs.

a. Software development methods. This paragraph shall describe or reference the software development methods to be used. Included shall be descriptions of the manual and automated tools and procedures to be used in support of these methods. The methods shall cover all contractual clauses concerning this topic. Reference may be made to other paragraphs in this plan if the methods are better described in context with the activities to which they will be applied.

b. Standards for software products. This paragraph shall describe or reference the standards to be followed for representing requirements, design, code, test cases, test procedures, and test results. The standards shall cover all contractual clauses concerning this topic. Reference may be made to other paragraphs in this plan if the standards are better described in context with the activities to which they will be applied. Standards for code shall be provided for each programming language to be used. They shall include at a minimum:

1. Standards for format (such as indentation, spacing, capitalization, and order of information)

2. Standards for header comments (requiring, for example, name/identifier of the code; version identification; modification history; purpose; requirements and design decisions implemented; notes on the processing (such as algorithms used, assumptions, constraints, limitations, and side effects); and notes on the data (inputs, outputs, variables, data structures, etc.)

3. Standards for other comments (such as required number and content expectations)

4. Naming conventions for variables, parameters, packages, procedures, files, etc.

5. Restrictions, if any, on the use of programming language constructs or features

6. Restrictions, if any, on the complexity of code aggregates

c. Reusable software products. This paragraph shall be divided into the following subparagraphs.

1. Incorporating reusable software products. This paragraph shall describe the approach to be followed for identifying, evaluating, and incorporating reusable software products, including the scope of the search for such products and the criteria to be used for their evaluation. It shall cover all contractual clauses concerning this topic. Candidate or selected reusable software products known at the time this plan is prepared or updated shall be identified and described, together with benefits, drawbacks, and restrictions, as applicable, associated with their use.

2. Developing reusable software products. This paragraph shall describe the approach to be followed for identifying, evaluating, and reporting opportunities for developing reusable software products. It shall cover all contractual clauses concerning this topic.

d. Handling of critical requirements. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for handling requirements designated critical. The planning in each subparagraph shall cover all contractual clauses concerning the identified topic.

1. Safety Assurance

a. Software Requirements

b. System Software Architecture and Software Preliminary Design

c. Software Detailed Design

d. Software Coding and Unit Test

e. Computer Software Component (CSC) Integration and Test

f. Computer Software Configuration Item (CSCI) Formal Qualification

Test (FQT)

g. Subsystem Integration and Test

h. System Qualification Test

2. Cyber-Security / Software Assurance

a. Software Requirements

b. System Software Architecture and Software Preliminary Design

c. Software Detailed Design

d. Software Coding and Unit Test

e. CSC Integration and Test

f. CSCI FQT

g. Subsystem Integration and Test

h. System Qualification Test

i. Describe the mechanism to address constant emerging cyber-security requirements.

1. Assurance of other critical requirements

f. Computer hardware resource utilization. This paragraph shall describe the approach to be followed for allocating computer hardware resources and monitoring their utilization. It shall cover all contractual clauses concerning this topic.

g. Recording rationale. This paragraph shall describe the approach to be followed for recording rationale that will be useful to the support agency for key decisions made on the project. It shall interpret the term "key decisions" for the project and state where the rationales are to be recorded. It shall cover all contractual clauses concerning this topic.

h. Access for acquirer review. This paragraph shall describe the approach to be followed for providing the acquirer or its authorized representative access to developer and subcontractor facilities for review of software products and activities. It shall cover all contractual clauses concerning this topic.

3.8. Plans for performing detailed software development activities. This section shall be divided into the following paragraphs. Provisions corresponding to non-required activities may be satisfied by the words "Not applicable." If different builds or different software on the project require different planning, these differences shall be noted in the paragraphs. The discussion of each activity shall include the approach (methods/procedures/tools) to be applied to: 1) the analysis or other technical tasks involved; 2) the recording of results; and, 3) the preparation of associated deliverables, if applicable. The discussion shall also identify applicable risks/uncertainties and plans for dealing with them.

a. Project planning and oversight. This paragraph shall be divided into the following subparagraphs to describe the approach to be followed for project planning and oversight. The planning in each subparagraph shall cover all contractual clauses regarding the identified topic.

1. Software development planning (covering updates to this plan)

2. CSCI test planning

3. System test planning

4. Software installation planning

5. Software transition planning

6. Following and updating plans, including the…