ATTACHMENT_03_CDRLs_R01.pdf

PDF 416 KB Posted Mar 30, 2017

Attached to: T-38A/B and A-10 Automatic Dependent Surveillance-Broadcast (ADS-B) Federal contract opportunity
Solicitation number: FA822017R0001
Issued by: Department of the Air Force Materiel Command Lifecycle Management Center Hill Air Force Base

About this file

From the source

Contract Data Requirements List

View the file

Other files for this federal contract opportunity

Other files attached to T-38A/B and A-10 Automatic Dependent Surveillance-Broadcast (ADS-B), newest first.
File	Type	Posted
FA822017R0001_______0001.pdf	PDF	Mar 30, 2017
ATTACHMENT_10_AFMAN_63-119.xls	XLS spreadsheet	Mar 30, 2017
ATTACHMENT_08_A-10_DD254.pdf	PDF	Mar 30, 2017
ATTACHMENT_15_Source_of_Repair.pdf	PDF	Mar 30, 2017
ATTACHMENT_02_T-38_A-10_APX-119_GPS_PWS_R01.pdf	PDF	Mar 30, 2017
ATTACHMENT_02_T-38_A-10_APX-119_GPS_PWS.pdf	PDF	Mar 30, 2017
ATTACHMENT_06_AFMC_Form_158.pdf	PDF	Mar 30, 2017
ATTACHMENT_07_DD_Form_1653.pdf	PDF	Mar 30, 2017
Narrative_of_Electrical_Loads_Spreadsheets.docx	DOCX document	Mar 30, 2017
ATTACHMENT_11_Florida_Wage_Determination.pdf	PDF	Mar 30, 2017
FA822017R0001.pdf	PDF	Mar 30, 2017
FA822017R0001_______0002.pdf	PDF	Mar 30, 2017
Materiel_Fielding_Plan_Template.docx	DOCX document	Mar 30, 2017
Item__20_ELA-AT-38B_DC_load_Analysis_ECM_Pod.xlsx	XLSX spreadsheet	Mar 30, 2017
ATTACHMENT_12_Indiana_Wage_Determination.pdf	PDF	Mar 30, 2017
Item__20_ELA-T-38_AC_Loading_TO_data-ECM_Pod.xlsx	XLSX spreadsheet	Mar 30, 2017
ATTACHMENT_03_CDRLs.pdf	PDF	Mar 30, 2017
ATTACHMENT_01_Pricing_Matrix_R01.xlsx	XLSX spreadsheet	Mar 30, 2017
ATTACHMENT_09_Reserved.pdf	PDF	Mar 30, 2017
ATTACHMENT_13_Maryland_Wage_Determination.pdf	PDF	Mar 30, 2017
T-38_A_and_B_Fleet_12_7_16.xlsx	XLSX spreadsheet	Mar 30, 2017
Electrical_Loads.xlsx	XLSX spreadsheet	Mar 30, 2017
ATTACHMENT_05_Technical_Manual_Contract_Requirements.pdf	PDF	Mar 30, 2017
ATTACHMENT_04_GFP_List.pdf	PDF	Mar 30, 2017
ATTACHMENT_14_Warranty_Information.pdf	PDF	Mar 30, 2017
Synopsis_of_FA8220-17-R-0001_ADS-B_-_Presolicitation.docx	DOCX document	Mar 15, 2017

Show all 26

On GovTribe

Work with this file on GovTribe

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

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

DD FORM 1423-1, FEB 2001

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

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

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of PagesDD

0001-0017 A

MGMT

T-38A/B ADS-B FA8220-17-R-0001

A001 Integrated Program Management Report (IPMR) IMS

DI-MGMT-81861A BLK 16 AFLCML/WLDMA

BLK 16

AFLCML/WLDMA 1

6064 Dogwood Ave Bldg 1254 Hill AFB, UT 84056-5816 Attn: Edward Waghorn

0 1 0

Contractor format is acceptable using Microsoft Office Products.

BLK 5: PWS Paragraph: 3.2.6

Block 9: Distribution Statement D: Distribution authorized to Department of Defense and U.S. DoD contractors for administrative or operational use, determined 12 September 2014. Other requests for a copy of this document shall be referred to AFLCMC/WLDMA T-38 Program Office.

Warning: This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751 et seq.) or Executive Order 12470. Violations of these export laws are subject to severe criminal penalties.

DESTRUCTION NOTICE – For classified documents, follow the procedures in DoD 5220.22-M, Industrial Security Manual, Section 11 -19 or DoD 5200.01, DoD Information Security Program. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

The above Distribution Statement, Warning Notice, and Destruction Notice shall be displayed or affixed to the data in a conspicuous position.

Block's 10, 11, 12, and 13: The Integrated Program Management Report shall be delivered to the Government within 60 days of contract award. The IMS will be updated and submitted 10 days before PDR, 10 days before CDR and at any point where a major milestone date changes by more than 2 weeks from the last reported IMS. At a minimum the IMS shall be delivered to the Government every 6-months.

01 Dec 2016 01 Dec 2016

1 3

OTTESON.JACOB.P.1

395210706

Digitally signed by OTTESON.JACOB.P.1395210706 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=OTTESON.JACOB.P.1395210706 Date: 2016.12.01 15:17:41 -07'00'

BROWNING.DEANNE.

1231545642

Digitally signed by BROWNING.DEANNE.1231545642 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=BROWNING.DEANNE.1231545642 Date: 2016.12.01 15:14:55 -07'00'

(1 Data Item)

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

TDP ________ TM _______ OTHER

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

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

0001-0017 A MGMT

T-38A/B ADS-B FA8220-16-R-0004

Remove Section 1.0 through 3.6 of DI MGMT 81861 and tailor section 3.7 so only the following applies:

3.7. Format 6 – Integrated Master Schedule (IMS).

3.7.1. IMS Requirements.

3.7.1.1.

Content Required. The IMS shall include, at a minimum, discrete tasks/activities, consistent with all authorized work, and relationships necessary for successful contract completion. Subcontractor discrete work shall be incorporated as tasks within the prime IMS at a level necessary for a realistic critical path. The IMS is a single integrated network that also contains significant external interfaces, Government furnished equipment/information/property and relationship dependencies for the entire contractual effort.

3.7.1.1.1. Production Contract IMS. Production contracts utilizing a Manufacturing Requirements Planning (MRP) or an Enterprise Requirements Planning (ERP) system may include a representation of the discrete effort contained in the MRP/ERP in the contract IMS.

The MRP/ERP information in the IMS shall be at a sufficient level of detail to ensure that the contract IMS status reflects the status of manufacturing progress in MRP/ERP system. Vertical traceability shall be maintained between the IMS and MRP/ERP system.

3.7.1.1.2.Subcontractor Flowdown.If specified in the CDRL, the contractor may be required to submit subcontractor IMS reports.

3.7.1.2.IMS Status The IMS shall be statused according to the contractor’s accounting month and aligned with Format 1 reporting month, as applicable.

3.7.1.3.IMS Content Elements The IMS shall contain the contract milestones, accomplishments, criteria, discrete tasks/activities, work packages and planning packages, as applicable, from contract award to contract completion.

• The IMS shall be an integrated, logically driven network-based schedule that is vertically and horizontally traceable.

• The IMS shall contain contractual milestones and descriptions and shall display summary, intermediate, and detailed schedules.

• The IMS shall include fields and data that enable access to the information by product and organizational lines.

• The IMS shall contain all calendars that define working and nonworking time periods or other information that may impact the schedule.

3.7.1.3.1. Contract Milestones. Key programmatic events which represent progress and completion of the contract.

3.7.1.3.4. Detailed Schedules. The lowest level of contract tasks/activities that form the network. The detailed schedules shall contain horizontal and vertical integration, as a minimum, at the work package and planning package level. The detailed schedules shall include all discrete tasks/activities, work packages and planning packages necessary to create a networked schedule capable of identifying a valid critical path.

3.7.1.3.5. IMS Detailed Elements. The IMS, at a minimum, shall include the following:

3.7.1.3.5.1. Task/Activity. An element of work with duration.

3.7.1.3.5.2. Milestone. A specific definable accomplishment in the contract network, recognizable at a particular point in time.

Milestones have zero duration and do not consume resources.

3.7.1.3.5.3. Duration. The length of time estimated or realized to accomplish a task/activity.

3.7.1.3.5.4. Schedule Percent Complete. Schedule percent complete is a time-based status calculated by the schedule tool without regard to task scope accomplishment. Schedule percent complete shall not be used to status BCWP.

3.7.1.3.5.5. Task/Activity and Milestone Descriptions. These are descriptive titles that are concise, complete, and clearly identify the work effort being accomplished. The task/activity title shall reflect the scope, its output (i.e., deliverable) and its place within the IMS architecture so that the content can be understood without the subproject task structure, if applicable. Abbreviations may be used to shorten the descriptive titles. The title for a task shall be unique in respect to other titles in the same IMS.

3.7.1.3.5.6. Relationships/Dependencies. Identify how predecessor and successor tasks/activities and milestones are logically linked. All non-constrained discrete tasks/activities/milestones, except the start and end of the contract or interim delivery, shall have at least one predecessor and successor.

3.7.1.3.5.7. Total Float/Slack. The amount of time a task/activity or milestone forecast finish date can slip before delaying contract completion or constraint date.

3.7.1.3.5.8. Driving Path. The longest sequence of discrete tasks/activities from time-now to a selected interim contract milestone.

Discrete tasks/activities on the driving path have the least amount of total float/slack to the interim contract milestone. If a task on a driving path slips, the interim contract milestone will slip. Driving path may not be part of the contract critical path. The Government may specify which driving path is currently reportable. Without Government direction, the contractor reports the driving path to the next major event, at a minimum.

3.7.1.3.5.9. Critical Path. A sequence of discrete tasks/activities in the network that has the longest total duration through the contract or project. Discrete tasks/activities along the critical path have the least amount of float/slack. Activities that contain “0” or negative total float are not by default the critical path. The critical path calculation is based on relationships, lead/lag times, durations, constraints, and status. Excessive constraints and incomplete, incorrect, or overly constrained logic shall be avoided because they can skew the critical path.

3.7.1.3.5.10. Current Schedule. The IMS shall reflect status and forecast discrete activities. Forecast start and forecast finish dates, shall not be earlier than the status date.

2 3

(1 Data Item)

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

TDP ________ TM _______ OTHER

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

16. REMARKS (Continued)

DD FORM 1423-1, FEB 2001 Page of Pages

0001-0017 A MGMT

T-38A/B ADS-B FA8220-16-R-0004

3.7.1.3.5.11. Baseline Schedule. The IMS shall have baseline dates for all tasks within the PMB and those dates shall be consistent with the start and finish of the cost baseline. The baseline is typically set equal to the current schedule early dates at the time of the baseline establishment when change control is initiated.

3.7.1.3.5.12. Baseline Schedule Changes. Changes to the baseline schedule shall be made in accordance with the contractor’s EVM process when applicable. In the event that the IMS is implemented without an EVM requirement, the change shall be made in accordance with the contractor’s schedule change management process. Any movement of contractual milestones in the baseline schedule shall be derived only from either authorized contract changes or an approved over target schedule.

3.7.1.3.5.13. Schedule Progress. The IMS shall reflect actual progress and maintain accurate start and finish dates for all tasks/activities and milestones. The requirements for reflecting schedule progress are as follows:

1) Actual start and actual finish dates shall be recorded in the IMS. The Actual start and actual finish dates shall not be later than the status date.

2) The progress line is the date on which the schedule is statused, also known as “time-now,” “data date,” or “status date.” All tasks/activities shall be progressed to the status date of the IMS.

3) Forecast start and forecast finish dates shall not be earlier than the status date.

3.7.1.3.5.14. Free Float/Slack. The amount of time a task/activity or milestone can slip before it delays any of its successor tasks/ activities or milestones.

3.7.1.3.5.15. External Dependencies. As agreed to by the Government and contractor, the IMS shall identify significant external dependencies that involve a relationship or interface with external organizations, including Government-furnished items (e.g., decisions, facilities, equipment, information, data) as defined in the contract. The required or expected delivery dates shall also be identified in the IMS. External dependencies shall be logically linked in the schedule to the appropriate IMS tasks.

3.7.1.3.7. Required Fields and Traceability Requirements.

3.7.1.3.7.1. General. The use of the term “field” is not intended to restrict the contractor. Most tools employ a mixture of user defined fields, notes fields, or flag fields. A required field referenced in this section can be satisfied by any means that allows for filtering and sorting of its information to obtain the results required. Also every task does not need to identify or be represented in every field, but only as applicable for the item required; e.g. planning packages are identified only for the tasks that represent planning packages.

3.7.1.3.7.2. Required traceability. The Statement of Work and OBS must be traceable for all discrete work in the IMS. Traceability may be met with a field in the IMS or via other means as long as discrete work reconciles.

3.7.1.3.7.3. Required IMS Fields. The following fields shall be identified as applicable and described in the Data Dictionary (see 3.7.3).

The purpose is for Government understanding or usability of the IMS as an effective tool.

2) Subcontractor. Identify the tasks that are unique to the scope of a major supplier, if any.

3) Justification of Lead, Lag, Constraint. Provide a field that contains a summary justification of lead, Lag, or constraint. This requirement may be met with a code defined in the definition table or by individual notes on each applicable task.

5) Risk Mitigation Tasks. Items that came from the risk register and include authorized risk mitigation activities shall be identified, as applicable.

6) Critical Path and Driving Paths. The Critical Path and Driving Path shall be identified. These identifiers are either automatically created by the scheduling software or custom fields that indicate/flag each task on a driving or critical path.

3.7.1.3.9. Retention of Historical Performance. Historical performance on completed tasks/activities shall be maintained electronically for analytical use. Historical performance shall be maintained at the time of key contract events (e.g., Integrated Baseline Review, Critical Design Review) for all tasks/activities. Data to be retained includes logic, actual and baseline durations, actual and baseline start and finish dates, and the three-point estimates that were used before the task/activity started.

3.7.1.4. Monthly Analysis. Format 6 monthly analysis requirements are defined in 3.6.7.

3.7.2.2. Lead/Lag. An interval of time that must occur between a predecessor and successor task/activity or milestone. Documenting the purpose of each lead/lag within the IMS (i.e. in a user defined field) to facilitate the ease of IMS status and analysis is required. Since negative time is not demonstrable, leads are discouraged. Lead/lag shall not be used to manipulate float/slack or to artificially constrain the tasks/activities. If a coding field is used for justification of leads/lags, the terms shall be defined in the data dictionary (see 3.7.3).

3.7.2.3 Constraints. Constraints are limits applied to network start and finish dates (e.g., “Finish No Later Than,” “Finish On or Before”).

Constraints shall be minimized if they affect “late” dates or both “late and early” dates. The constraints that require justification include:

1) All constraints that affect “late” dates or both “late and early” dates as defined by the schedule tool.

2) All constraints that affect “early” dates beyond 20 working days from the current status period.

Constraints requiring justification shall be justified in an associated notes field provided within the scheduling software application. If a coding field is used for justification of constraints the definitions shall be defined in the data dictionary (see 3.7.3).

3.7.3. Task/Activity Codes and Data Dictionary. This is a list of all contractor defined fields, definitions, and code Structures in the IMS.

This list shall define all of the required fields in section 3.7.1.3.7.3. The list shall be provided to the procuring activity upon initial submission of the IMS and any subsequent change to the dictionary.

3 3

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

0001-0017 A

MGMT

T-38A/B ADS-B FA8220-17-R-0001

A002 Contractor's Risk Management Plan

DI-MGMT-81808 BLK 16 AFLCMC/WLDMA

BLK 16

AFLCMC/WLDMA 1

6064 Dogwood Ave Bldg. 1254 Hill AFB, UT 84056-5816 Attn: Edward Waghorn

0 1 0

Contractor format is acceptable using Microsoft Office Products.

BLK 5: PWS Paragraph: 3.6.1, 3.6.2

DESTRUCTION NOTICE – For classified documents, follow the procedures in DoD 5220.22-M, Industrial Security Manual, Section 11-19 or DoD 5200.01, DoD Information Security Program. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document.

The above Distribution Statement, Warning Notice, and Destruction Notice shall be displayed or affixed to the data in a conspicuous position.

Block's 10, 11, 12, and 13: First submission of the Risk Management Plan shall be provided within 60 calendar days from contract award and subsequent submittals shall be provided when changes are made to the plan.

19 Oct 16 19 Oct 16

1 1

OTTESON.JACOB.P.1

395210706

Digitally signed by OTTESON.JACOB.P.1395210706 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=OTTESON.JACOB.P.1395210706 Date: 2016.10.19 10:50:16 -06'00'

ALAWNEH.DEBORA

H.I.1161171324

Digitally signed by

ALAWNEH.DEBORAH.I.1161171324

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=ALAWNEH.DEBORAH.I.1161171324 Date: 2016.10.19 09:38:58 -06'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

0001-0017 A

MGMT

T-38A/B ADS-B FA8220-17-R-0001

A003 Contractor's Progress, Status and Management Report

DI-MGMT-80227 BLK 16 AFLCMC/WLDMA

BLK 16

AFLCMC/WLDMA 1

6064 Dogwood Ave Bldg 1254 Hill AFB, UT 84056-5816 Attn: Edward Waghorn

0 1 0

Contractor format is acceptable using Microsoft Office Products.

BLK 5: PWS Paragraph: 3.2.5, 3.2.7

Block 9: Distribution Statement D: Distribution authorized to Department of Defense (DoD) and U.S. DoD contractors for administrative or operational use, determined 12 September 2014. Other requests for a copy of this document shall be referred to AFLCMC/WLDMA T-38 Program Office.

The above Distribution Statement, Warning Notice, and Destruction Notice shall be displayed or affixed to the data in a conspicuous position.

Block's 10, 11, 12, and 13: The Contractor's Progress, Status and Management Report shall be delivered As Required.

19 Oct 16 19 Oct 16

1 1

OTTESON.JACOB.P.

1395210706

Digitally signed by OTTESON.JACOB.P.1395210706 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=OTTESON.JACOB.P.1395210706 Date: 2016.10.19 10:50:49 -06'00'

ALAWNEH.DEBOR

AH.I.1161171324

Digitally signed by ALAWNEH.DEBORAH.I.1161171324 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=ALAWNEH.DEBORAH.I.1161171324 Date: 2016.10.19 09:39:35 -06'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

0001,0002,0006 A

SESS

T-38A/B ADS-B FA8220-17-R-0001

A004 Baseline Description Document

DI-SESS-81121A BLK 16 AFLCMC/WLDMA

BLK 16

AFLCMC/WLDMA 1

6064 Dogwood Ave Bldg 1254 Hill AFB, UT 84056-5816 Attn: Edward Waghorn

0 1 0

Contractor format is acceptable using Microsoft Office Products.

BLK 5: PWS Paragraph: 3.2.9

The above Distribution Statement, Warning Notice, and Destruction Notice shall be displayed or affixed to the data in a conspicuous position.

Block's 10, 11, 12, and 13: The Baseline Description Document shall be delivered upon request.

19 Oct 16 19 Oct 16

1 1

OTTESON.JACOB.P.

1395210706

Digitally signed by OTTESON.JACOB.P.1395210706 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=OTTESON.JACOB.P.1395210706 Date: 2016.10.19 11:03:28 -06'00'

ALAWNEH.DEBORA

H.I.1161171324

Digitally signed by

ALAWNEH.DEBORAH.I.1161171324

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, Date: 2016.10.19 09:40:12 -06'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

0002, 0007, 0006, 0008 A

MISC

T-38A/B ADS-B FA8220-17-R-0001

A005 Technical Report-Study/Services Technical Evaluation

DI-MISC-80508B BLK 16 AFLCMC/WLDMA

BLK 16

BLK16

AFLCMC/WLDMA 1

6064 Dogwood Ave Bldg 1254 Hill AFB, UT 84056-5816 Attn: Edward Waghorn

0 1 0

Contractor format is acceptable using Microsoft Office Products.

BLK 5: PWS Paragraph: 6.1.6, 6.1.7, 6.1.10, 6.1.11, 6.2.4, 7.2.1, 8.1.1, 9.1.1, 9.3.1

Warning: This document contains technical data whose export is restricted by the Export Control Act (Title 22, V.S.C., Sec 2751 et seq.) or Executive Order 12470.

Violations of these export laws are subject to severe criminal penalties.

The above Distribution Statement, Warning Notice, and Destruction Notice shall be displayed or affixed to the data in a conspicuous position.

Block's 10, 11, 12, and 13: The Technical Evaluation shall be delivered as required.

19 Oct 16 19 Oct 16

1 1

OTTESON.JACOB.P.1

395210706

Digitally signed by OTTESON.JACOB.P.1395210706 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=OTTESON.JACOB.P.1395210706 Date: 2016.10.19 11:05:19 -06'00'

ALAWNEH.DEBORAH.

I.1161171324

Digitally signed by ALAWNEH.DEBORAH.I.1161171324 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, Date: 2016.10.19 09:52:55 -06'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

0001-0017 A

ADMN

T-38A/B ADS-B FA8220-17-R-0001

A006 Report, Record of Meeting/Minutes Meeting Minutes and Action Items

DI-ADMN-81505 BLK 16 AFLCMC/WLDMA

BLK 16

BLK16

AFLCMC/WLDMA 1

6064 Dogwood Ave Bldg 1254 Hill AFB, UT 84056-5816 Attn: Edward Waghorn

0 1 0

Contractor format is acceptable using Microsoft Office Products.

BLK 5: PWS Paragraph: 3.2.3, 3.2.4, 4.1.2

Warning: This document contains technical data whose export is restricted by the Export Control Act (Title 22, V.S.C., Sec 2751 et seq.) or Executive Order 12470.

Violations of these export laws are subject to severe criminal penalties.

The above Distribution Statement, Warning Notice, and Destruction Notice shall be displayed or affixed to the data in a conspicuous position.

Block's 10, 11, 12, and 13: The Meeting Minutes and Action Items shall be provided within 5 business days following the meeting being reported.

19 Oct 16 19 Oct 16

1 1

OTTESON.JACOB.P.13

95210706

Digitally signed by OTTESON.JACOB.P.1395210706 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=OTTESON.JACOB.P.1395210706 Date: 2016.10.19 11:05:55 -06'00'

ALAWNEH.DEBORAH.

I.1161171324

Digitally signed by ALAWNEH.DEBORAH.I.1161171324 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, Date: 2016.10.19 09:53:27 -06'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

0002 A

SESS

T-38A/B ADS-B

A007 Engineering Release Record (ERR)

DI-SESS-80463D BLK 16 AFLCMC/WLDMA

BLK 16

BLK16

AFLCMC/WLDMA 1

6064 Dogwood Ave Bldg 1254 Hill AFB, UT 84056-5816 Attn: Edward Waghorn

0 1 0

Contractor format is acceptable using Microsoft Office Products.

BLK 5: PWS Paragraph: 6.3.1, 6.3.8, 6.4.1

Warning: This document contains technical data whose export is restricted by the Export Control Act (Title 22, V.S.C., Sec 2751 et seq.) or Executive Order 12470.

Violations of these export laws are subject to severe criminal penalties.

The above Distribution Statement, Warning Notice, and Destruction Notice shall be displayed or affixed to the data in a conspicuous position.

Block's 10, 11, 12, and 13: The Engineering Release Record shall be provided as required.

19 Oct 16 19 Oct 16

1 1

OTTESON.JACOB.P.1

395210706

Digitally signed by OTTESON.JACOB.P.1395210706 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=OTTESON.JACOB.P.1395210706 Date: 2016.10.19 11:54:47 -06'00'

ALAWNEH.DEBORA

H.I.1161171324

Digitally signed by

ALAWNEH.DEBORAH.I.1161171324

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=ALAWNEH.DEBORAH.I.1161171324 Date: 2016.10.19 09:54:02 -06'00'

FA8220-17-R-0001

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

0002, 0006 A

ADMN

T-38A/B ADS-B FA8220-17-R-0001

A008 Revisions to Existing Government Documents

DI-ADMN-80925 AFLCMC/WLDMA

BLK 16

BLK16

AFLCMC/WLDMA 1

6064 Dogwood Ave Bldg 1254 Hill AFB, UT 84056-5816 Attn: Mr. Edward Waghorn

0 1 0

Contractor format is acceptable using Microsoft Office Products.

BLK 5: PWS Paragraph: 6.1.3, 6.1.9.A, 6.1.9.C, 6.2.5, 6.4.2, 6.4.3

Warning: This document contains technical data whose export is restricted by the Export Control Act (Title 22, V.S.C., Sec 2751 et seq.) or Executive Order 12470.

Violations of these export laws are subject to severe criminal penalties.

The above Distribution Statement and Warning Notice shall be displayed or affixed to the data in a conspicuous position.

The above Distribution Statement, Warning Notice, and Destruction Notice shall be displayed or affixed to the data in a conspicuous position.

Block's 10, 11, 12, and 13: The Document Changes shall be submitted as required.

19 Oct 16 19 Oct 16

1 1

OTTESON.JACOB.P.13

95210706

Digitally signed by OTTESON.JACOB.P.1395210706 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=OTTESON.JACOB.P.1395210706 Date: 2016.10.19 11:55:18 -06'00'

ALAWNEH.DEBORA

H.I.1161171324

Digitally signed by

ALAWNEH.DEBORAH.I.1161171324

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, Date: 2016.10.19 10:16:45 -06'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

0001, 0002, 0006 A

SESS

T-38A/B ADS-B FA8220-17-R-0001

A009 Specification Change Notice (SCN)

DI-SESS-80643D BLK 16 AFLCMC/WLDMA

BLK 16

BLK16

AFLCMC/WLDMA 1

6064 Dogwood Ave Bldg 1254 Hill AFB, UT 84056-5816 Attn: Mr. Edward Waghorn

0 1 0

Contractor format is acceptable using Microsoft Office Products.

BLK 5: PWS Paragraph: 4.2.2, 6.4.2

Warning: This document contains technical data whose export is restricted by the Export Control Act (Title 22, V.S.C., Sec 2751 et seq.) or Executive Order 12470.

Violations of these export laws are subject to severe criminal penalties.

The above Distribution Statement and Warning Notice shall be displayed or affixed to the data in a conspicuous position.

The above Distribution Statement, Warning Notice, and Destruction Notice shall be displayed or affixed to the data in a conspicuous position.

Block's 10, 11, 12, and 13: The Specification Change Notices shall be submitted as required.

19 Oct 16 19 Oct 16

1 1

OTTESON.JACOB.P.1

395210706

Digitally signed by OTTESON.JACOB.P.1395210706 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=OTTESON.JACOB.P.1395210706 Date: 2016.10.19 12:50:19 -06'00'

ALAWNEH.DEBOR

AH.I.1161171324

Digitally signed by ALAWNEH.DEBORAH.I.1161171324 DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, Date: 2016.10.19 12:49:01 -06'00'

(1 Data Item)

PREVIOUS EDITION MAY BE USED.

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302. 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 address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No.

listed in Block E.

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

TDP ________ TM _______ OTHER

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

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

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

7. DD 250 REQ

8. APP CODE

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

11. AS OF DATE

12. DATE OF FIRST SUBMISSION

13. DATE OF SUBSEQUENT

SUBMISSION

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

Draft Final

Reg Repro

15. TOTAL

16. REMARKS

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

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

Page of Pages

0001, 0002, 0006 A

T-38A/B ADS-B FA8220-17-R-0001

A010 Product Drawings/Models & Associated Lists APX-119 Transponder with Embedded GPS Development

DI-SESS-81000E 6.4.2 AFLCMC/WLDMA

WAWF

A D

BLK 16

WAWF 1 1

DoDAAC FA8213

AFLCMC/WLDMA

6064 Dogwood Ave Bldg 1254 Hill AFB, UT 8405 Attn: Edward Wagh

AFLCMC/WLDEA 1 1

6057 Box Elder Ln Bldg 1285 Hill AFB, UT 8405

AFLCMC/LZPEM 1 1

6020 Gum Ln Bldg 1218 Hill AFB, UT 8405 Attn: EDMS

2 3 0

Drawings shall be IAW ASME Y14.100-2013 (including Appendices B,C,D,E)

ASME Y14.24, ASME Y14.3, ASME Y14.34, ASME Y14.35, ASME Y14.41,

and ASME Y14.5.

Blk E. Contract Number: All Drawings, Models, Specifications and Associated Lists shall have the contract number identified on sheet one of each drawing.

Blk 4. Tailoring of DI-SESS-81000E per information in this document and attached MIL-DTL-31000C. Technical data package option Selection Worksheet forms a part of this contract data requirements list.

Blk. 7 Electronic receiving report required via INTERNET Side Area Workflow (WAWF) (WAWF at: HTTPS://WAWF.EB.MIL). DoDAAC FA8213.

The electronic receiving report shall be used only for this data item: Do not combine other data item submittals with this requirement.

All Proprietary Data shall be identified with Distribution Statement B:

Distribution authorized to U.S. Government Agencies only Proprietary Information 18 October 2016. Other requests for this document shall be referred to AFLCMC/WLDEA, Hill AFB, UT 84056-5811.

Proprietary Stamp shall be on the first sheet of each drawing.

All non-proprietary shall be Distribution Statement D:

Blk 9. Distribution Statement D: Distribution authorized to Department of Defense and U.S DoD contractors only for Administrative or Operational Use 18 October 2016. Other requests shall be referred to AFLCMC/WLDEA, Hill AFB, UT 84056-5811.

Warning - This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. 2751 et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., APP. 2401, et seq.

Violation of these export laws are subject to severe criminal penalties.

Dissemination of this document is controlled under DOD Directive 5230.25.

HANDLING AND DESTRUCTION NOTICE: Comply with distribution statement and destroy by any method that will prevent disclosure of the contents or reconstruction of document

Distribution Statement, Export Control and Destruction Notice shall be on the first sheet of each drawing and associated lists.

Wendy Heugly 19 Oct 2016 Jacob Otteson 19 Oct 2016

1 4

HEUGLY.WEN

DY.T.1231478

Digitally signed by

HEUGLY.WENDY.T.1231478198

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=HEUGLY.WENDY.T.123147819 Date: 2016.10.19 12:39:45 -06'00'

OTTESON.JACO

B.P.1395210706

Digitally signed by

OTTESON.JACOB.P.1395210706

DN: c=US, o=U.S. Government, ou=DoD, ou=PKI, ou=USAF, cn=OTTESON.JACOB.P.1395210706 Date: 2016.10.19 12:43:30 -06'00'

(1 Data Item)

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

TDP ________ TM _______ OTHER

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

16. REMARKS (Continued)

Page of Pages

0001, 0002, 0006 A

T-38A/B ADS-B FA8220-17-R-0001

Blk 10 A shipping list shall be provided with each shipment of engineering data. This shipping list shall identify, in alphanumeric document number order, each document furnished in the package. Media shall be paper copies.

Blk 11 As required by Government

Blk 12 and 13.

a. Drawing Preliminary/Draft Copies: The contractor shall submit a digital data sample. preliminary drawings to block 14 addressees for review of format, content and accuracy of drawings 45 calendar days prior to final delivery. AFLCMC/WLDEA requires 15 working days to review drawings and provide comments to AFLCMC/WLDMA for return to the contractor. Subsequent to receipt of government comments, the contractor shall then within 30 days submit corrected digital data preliminary to the block 14 addressees for confirmation of acceptability prior to final delivery. Contractor shall deliver 2-D assembly engineering drawings in PDF and associated list media PDF. Contractor shall deliver CAD model in native file format Unigraphics NX.

9. Tailoring to ASME’s as follows:

ASSME Y14.100-2004

(1). (Application Data) para 4.6 - Application Data is required on firsts sheet of each Drawing and Associated List. General use or multi-use notations is allowed.

(2) (Drawing Notes) para 4.26 - Drawing Notes shall be on first sheet of each drawing.

(3) (Language) para 4.26.1 - Drawings and Associated Lists shall be in the English language.

(4) (Drawing Notes-Contents) para 4.26.6 (f) - Flag note symbol used shall be consistent throughout the entire TDP.

(5) (Drawing Verification and Approval) para 4.27 - For newly created Drawings and Associated Lists…

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. Updated Nov 14, 2017.