PWS_T_38_IATP_and_LESS_Phase_XX_Final_24_Sep_18.pdf

PERFORMANCE WORK STATEMENT (PWS)

For the:

T-38 Individual Aircraft Tracking Program (IATP) Sustainment

Phase XX: Continued T-38 IATP and L/ESS Development and

Implementation

24 September 2018

Prepared by:

Michael P. Blinn

AFLCMC/WLDE

(801) 777-0535 michael.blinn@hill.af.mil

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

MATURE AND PROVEN AIRCRAFT DIVISION

ENGINEERING BRANCH

HILL AIR FORCE BASE, UTAH 84056

mailto:michael.blinn@hill.af.mil i T-38 IATP and L/ESS – Phase XX

Last Rev. Date: 24 Sep18

PERFORMANCE WORK STATEMENT

TABLE OF CONTENTS

Page

LIST OF TABLES ............................................................................................................................. iii

RECORD OF REVISIONS ......................................................................................................... iv

1 DESCRIPTION OF SERVICES

1.1 Scope

1.2 Period of Performance

2 SERVICE SUMMARY

3 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.1 Aircraft Provided

3.2 Reports

3.3 Security and Access to Government Facilities and Equipment

3.3.1 Security Clearance

3.3.2 Access to Government Facilities

3.3.3 Obtaining and Retrieving Base Identification

3.3.4 Entry Procedures to Controlled or Restricted Areas

3.3.5 Procedures and Controls

3.3.6 Cybersecurity

3.3.7 Network Security

3.3.8 Operational Security (OPSEC)

4 GENERAL INFORMATION

4.1 General Requirements

4.2 Technical Objectives and Goals

4.3 Specific Requirements

4.3.1 Contractor Services

4.3.2 Integrated Management Support

4.3.3 Management Systems Requirements

4.3.4 Validation Program

4.3.5 Maintainability Program

5 APPENDICES AND ATTACHMENTS

5.1 Applicable Documents

5.1.1 Document Availability and Delivery

5.2 Applicable CDRLs

5.2.1 CDRL List

5.2.2 Contractor Reporting

ii T-38 IATP and L/ESS – Phase XX

Last Rev. Date: 24 Sep 18

ACRONYMS AND ABBREVIATIONS

ATTACHMENT ONE: LIST OF APPLICABLE DOCUMENTS.................................... A1-1

ATTACHMENT TWO: APPLICABLE CDRLS ................................................................ A2-1 iii T-38 IATP and L/ESS – Phase XX

LIST OF TABLES

Page Table 1: Service Summary for Phase XX of the T-38 IAT and L/ESS Program Table 2: Travel for the T-38 IAT and L/ESS Program – Phase XX Table 3: CDRL List for the T-38 IATP and L/ESS Program – Phase XX ................................... A2-1 iv T-38 IATP and L/ESS – Phase XX

RECORD OF REVISIONS

REV DATE

PAGE(S)

AFFECTED

SECTION(S)

AFFECTED

REASON FOR REVISION

- 24 Sep 18 n/a n/a Original PWS date of release

1 T-38 IATP and L/ESS – Phase XX

1 DESCRIPTION OF SERVICES

The following Performance Work Statement (PWS) provides a description of the required contractor services in support of the T-38 Aircraft Structural Integrity Program (ASIP), T-38

Program Office (PO), Air Education and Training Command (AETC), and other commands.

This contractual effort is limited to Phase XX of the T-38 Individual Aircraft Tracking (IAT) and

Loads/Environment Spectra Survey (L/ESS) program. The required engineering efforts are binding towards meeting the Phase XX requirements. Additional follow-on efforts are merely mentioned to depict the T-38 PO and ASIP Manager’s overall program scheme and to ensure current efforts are considered by the contractor to facilitate integration towards required follow-on efforts and options.

Phase XX, in and of itself, is of value to the T-38 ASIP’s IAT program for the purpose of continual improvement of the overall T-38 sustainment efforts, regardless of whatever future efforts are accomplished.

1.1 Scope

This PWS specifies the Phase XIX tasks towards sustaining and improving the T-38’s IAT and

L/ESS programs. The T-38 IATP and L/ESS revitalization and sustainment effort – including the earlier FLDR activities - is a continuation of a multi-phased approach as follows:

Phase I (FY04) – T-38C FLDR at Moody AFB and Preliminary T-38 IATP and L/ESS

Evaluation

Phase II (FY05) – T-38C FLDR and Preliminary T-38 IATP and L/ESS Development

Phase III (FY06) – T-38C FLDR and T-38 IATP and L/ESS Implementation and Final

Development Reporting

Phase IV (FY07) - T-38C FLDR Program at Four AETC Bases with Continued IATP and L/ESS Development and Implementation

Phase V and Va (FY08-10) - T-38C FLDR Program at Four AETC Bases with

Continued IATP and L/ESS Development and Implementation

Phase VII (FY11 and FY12) - Final T-38C FLDR Program at Four AETC Bases with

Continued IATP and L/ESS Development and Implementation

Phase X (FY13) - Continued T-38 IATP and L/ESS Development and Implementation

Phase XII (FY14) - Continued T-38 IATP and L/ESS Development and Implementation

Phase XIV (FY15) - Continued T-38 IATP and L/ESS Development and Implementation

Phase XV (FY16) - Continued T-38 IATP and L/ESS Development and Implementation

Phase XVI (FY17) - Continued T-38 IATP and L/ESS Development and Implementation

Phase XIX (FY18) - Continued T-38 IATP and L/ESS Development and Implementation

Note: Phases VI, VIII, IX, XI, XIII, XVII, and XVIII are by other contractors, so are not included in the previous list.

1.2 Period of Performance

The Period of Performance (PoP) for this task order is 12 months.

2 T-38 IATP and L/ESS – Phase XX

2 SERVICE SUMMARY

Table 1 describes the Service Summary (SS) for the tasks as outlined in this PWS. Most of the efforts as described in this PWS will be engineering services and program management related.

Table 1 - Service Summary for Phase XX of the T-38 IAT and L/ESS Program

Performance Objectives

PWS

Reference Performance Threshold

(Minimum Acceptable)

Engineering Technical Activities: 4.3.1.1 For engineering analyses (or assessments or

Contractor to provide engineering through studies): All actions accomplished as required analyses, assessments, and research 4.3.1.2.3 with no more than one disapproval by the towards supporting the T-38 IATP and government for technical discrepancies per

L/ESS development. technical document/report. Any necessary corrections must be made within 30 days of government notification; the flow of analysis must be logical, the analysis steps must be shown in sufficient detail such that an entry-level engineer can follow and a journeymen engineer can recreate; the input values/units to the model must be cited; the mathematics must be free from significant errors; the results/conclusions must be clearly identified; and the implications of the result/conclusion must be clearly stated.

Development Support for Tinker’s 4.3.1.1 T-38 IATP and L/ESS development, including the ASIMIS: To provide support during the through software and associated infrastructure, shall be development of the T-38 IATP and 4.3.1.2.3 95% error free in the final product.

L/ESS software and associated infrastructure and systems; to provide the required improvements to the software for Tinker’s ASIMIS; and to continue interfacing with Boeing’s

IMIS.

Technical Documentation: To 4.3.1.1.2 The T-38 IATP’s user’s manual shall be updated to generate high quality T-38 IATP and through be 100% complete. All actions accomplished are

L/ESS reporting and documentation; 4.3.1.1.5; to be delivered with no more than one disapproval includes activities as monthly reporting 5.2.1, 5.2.2 by the government for technical and financial and documentation, such as the IATP’s discrepancies per each technical, financial, and user’s manual. other documentation. Contractor shall submit all documentation as identified in the attached

CDRLs. Any necessary corrections must be made within 30 days of government notification.

3 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.1 Aircraft Provided

No instrumented aircraft are required for Phase XX.

3 T-38 IATP and L/ESS – Phase XX

3.2 Reports

The government will provide the contractor with all the necessary government Technical Orders

(TOs), Time Compliance Technical Orders (TCTOs), and contractor reports, required to accomplish the tasks as detailed in this PWS.

3.3 Security and Access to Government Facilities and Equipment

3.3.1 Security Clearance: The efforts required for this task are UNCLASSIFIED and will not require contractor personnel to obtain a security clearance. Contractor personnel shall abide by all Air Force rules, procedures, and standard of conduct. Contractors requiring access to

Air Force Automated Information Systems (AIS) shall have background investigations and security awareness training completed prior to the start of contract performance. When the period of performance is complete and/or the contractor personnel leave work on this project, they will return all access cards and base identification badges within five days.

3.3.2 Access to Government Facilities: Access to government facilities is limited. Therefore, the contractor shall coordinate the need, time, and personnel requiring access to government facilities with the PM, at least one week prior to need. The government PM or designated representative will coordinate between the contractor and base personnel as required.

3.3.3 Obtaining and Retrieving Base Identification: Contractors requiring access to government installations shall obtain the appropriate base identification for all contractor personnel who make frequent visits to or perform work at government sites. Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished identification badges while visiting or performing work on the installation(s).

During performance of the contract, the contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials for any employee who no longer requires access to the work site(s). Upon completion or termination of the contract or expiration of base identification, the contractor shall ensure that all base identification passes issued to contractor employees are returned to the appropriate issuing office.

3.3.4 Entry Procedures to Controlled or Restricted Areas: Contractor employees shall comply with local base procedures for entry into government controlled and restricted areas. If contractor employees require unescorted entry to controlled or restricted areas, the contractor shall comply with the Federal Installations Command Physical Security Plan and DoD Personnel

Security Program, DoD 5200.2-R.

3.3.5 Procedures and Controls: The contractor shall implement and maintain security procedures and controls to prevent unauthorized disclosure of controlled unclassified information and to control distribution of controlled unclassified information IAW DoD 5220.22-M, National Industrial Security Program Operating Manual. All contractor facilities shall provide appropriate means of storage for controlled unclassified information and materials.

All controlled unclassified information shall be appropriately identified and marked as For

Official Use Only IAW DoD 5200.01, DoD Information Security Program: Controlled

Unclassified Information Volume 4 (enclosure 3) and DoD 5400.7-R Freedom of

Information Act Regulation Chapter 3. The contractor shall not store or transmit controlled

4 T-38 IATP and L/ESS – Phase XX unclassified information on personal information technology systems or via personal e-mail.

3.3.6 Cybersecurity: Cybersecurity (CS) is the discipline that protects and defends information and information systems by ensuring their availability, integrity, authentication, confidentiality, and non-repudiation. These measures include providing for restoration of information systems by incorporating protection, detection, and reaction capabilities. DoD

Instruction 8500.01 establishes a DoD cybersecurity program to protect and defend DoD information and information technology. The contractor shall implement DoDI 8500.01 guidance for development of a cybersecurity strategy as defined below.

3.3.7 Network Security: The contractor shall take means (defense-in-depth measures) necessary to protect the availability, integrity, and confidentiality of government Controlled

Unclassified Information (CUI) in the same manner as the contractor would protect its own unclassified company proprietary information IAW DoD Instruction 8582.01. The contractor shall safeguard CUI stored on non-DoD information systems to prevent the loss, misuse, and unauthorized access to or modification of this information. The contractor shall ensure that contractor-owned and operated unclassified information technology (IT) network assets (including assets used for contractor teleworkers) used to process sensitive government CUI are managed and maintained IAW commercial best practices, vendor-specific, or other nationally or internationally-recognized IT configuration and management standards.

3.3.8 Operational Security (OPSEC): OPSEC requirements are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the contract. A critical information list will be provided by the government.

4 GENERAL INFORMATION

4.1 General Requirements

General requirements for the Aircraft Structural Integrity Program (ASIP) are given in Air Force

Policy Directive (AFPD) 63-1, Air Force Instruction 63-101, and AFI 63-140 (1-3)1. In addition, ASIP is detailed in MIL-STD-1530D (4).

4.2 Technical Objectives and Goals

The T-38 “Talon” has recently completed significant avionics modifications and is currently undergoing engine upgrades, with the intention of modernizing the fleet of over 420 AETC aircraft. The T-38A and A/T-38B models have been upgraded with the T-38C avionics; the

AETC fleet will be fully positioned to train the pilots of the future (e.g., those flying the F-16 and

F-22). As the T-38 fleet is now being programmed out to FY34 (and possibly beyond), the T-

38 ASIP needs to adapt to the changes in the aircraft, and collect the required flight loads data to ensure structural integrity. Following the NGC Phase XIX effort (FY18), the T-38 ASIP still

1 All references are found in Attachment One.

5 T-38 IATP and L/ESS – Phase XX needs to continue developing the long-term solution for the T-38 IATP and L/ESS. As such, both the IATP and L/ESS data collection and evaluation are ASIP requirements to be updated and supported, formally stated in MIL-STD-1530D.

4.3 Specific Requirements

4.3.1 Contractor Services: The contractor shall provide the appropriate engineering, program management, and technical services as required for this PWS. Travel will be required to meet the goals of this effort.

4.3.1.1 T-38 IATP and L/ESS Continued Development and Implementation:

4.3.1.1.1 General Discussion: The contractor shall continue to perform a comprehensive and coordinated effort to integrate the earlier and new flight loads data into a combined T-

38 IAT and L/ESS program. This effort will require coordination with the USAF and other contractors, as well as the Aircraft Structural Integrity Management Information

System (ASIMIS) out of Tinker AFB, OK, and is intended to be in concert with those similar efforts as performed in Phases I through XIX (with some phases performed by others – see Para. 1.1). A good source for evaluating the early requirements are the work statements (6-14).2

4.3.1.1.2 System Development (Includes IMIS and ASIMIS): The T-38 IATP and L/ESS development will continue to improve and refine their approach to determining some of the following: 1) control points to use for individual tracking (currently FCL B-12 for the fuselage and FCL A-10a for the wing); 2) calculation of a notional Damage

Index (DI) at these control points; 3) suggestions as to how to best capture other important aircraft parameters (e.g., airframe hours, longeron hours, wing hours, etc.);

4) integration of the on-aircraft flight loads data (FLD) from the AETC bases with the ASIMIS at Tinker; 5) coordination with Tinker (ASIMIS) as to how to best format final IAT and L/ESS reporting (on a quarterly basis); 6) methodologies to integrate and how to determine a FLD baseline for the fleet based on the T-38C data (as opposed to traditional FLDR programs). In short, a continuation of the shorter Phase XIX efforts are required.

Continuous, comprehensive, and detailed planning is vital to the success of the Phase

XX efforts, so the contractor shall plan accordingly for their reporting. The final IATP report is due 12 months ARO. For Phase XX, the deliverable document should be entitled, “T-38 IATP and L/ESS Development Report – Phase XX.” Additional requirements for the final documentation of the system development are described in

Para. 4.3.1.1.5 (CDRL A001, Attachment Two).

4.3.1.1.3 System Software: As part of the T-38 IATP and L/ESS development, software updates shall be provided for use at Tinker’s ASIMIS facilities. The software should be tailored, by the contractor, to the specific needs of the T-38 ASIP, but should employ as much “Commercial Off-the- Shelf” (COTS) technology as possible. In addition, data for use in the Northrop’s IATP and L/ESS system will come from

2 A listing of the various work statements can be found in Attachment One.

6 T-38 IATP and L/ESS – Phase XX

Boeing’s IMIS central facility, downloaded by ASIMIS technicians, and thus the software needs to be fully compatible with these inputs (CDRL A002, Attachment Two).

4.3.1.1.4 User’s Manual: In support of ASIMIS activities to run and troubleshoot the system software, and to detail the IAT and L/ESS program improvements for the earlier phases and beyond, the contractor shall update the user’s manual report that summarizes their assessment of the T-38 IATP and L/ESS situation, including all design, development, and implementation activities (through Phase XX). In addition, the contractor shall recommend an approach for Phase XXI and beyond (CDRL

A003, Attachment Two).

4.3.1.1.5 Reporting: At the conclusion of the system development for Phase XX, the contractor shall prepare a final report that summarizes their assessment of the T-38 IATP and L/ESS situation, including all design, development, and implementation activities

(through Phase XX). In addition, the contractor shall recommend an approach for later phases (CDRL A004, Attachment Two).

4.3.1.2 Formal Evaluations: The following formal evaluations are to be supported by the Contractor:

4.3.1.2.1 Preliminary Program Review: A preliminary program review for the contractor to present their refined “way ahead” for Phase XX, and further discuss the anticipated challenges with the tasks as described in this PWS, shall be held no later than two months ARO contract award. The contractor shall provide a PPT document as well as present minutes of the meeting in the most appropriate monthly report (CDRL A005, Attachment Two).

4.3.1.2.2 Mid-course Evaluations and Status updates: As a minimum, monthly status updates and information exchanges between the government and the contractor will be conducted. These can be accomplished via teleconferencing. Minutes will be maintained by the government. CDRL reporting is not required. Performance and cost reporting must be submitted monthly. The performance and cost reports shall provide current status and projected requirements of funds, man-hours, and work completion. (CDRL A005, Attachment Two).

4.3.1.2.3 Final Program Review: A final review to present the final results and discuss the outcomes of the T-38 FLDR and IATP (Phase XX) shall be held at the conclusion of the program (CDRL A005, Attachment Two).

4.3.1.3 Contractor Travel: The contractor travel requirements are limited to one maintenance trip and is related to support for the IAT program. Table 2 shows the anticipated contractor trip anticipated for IAT support.

7 T-38 IATP and L/ESS – Phase XX

Table 2 - Travel for the T-38C IATP and L/ESS Program – Phase XX

Number

Travelers

No. of

Days

Start

(CY)

Purpose From To Fly or

Drive

Rental

Car

1 5 2019 ASIMIS El

Segundo, CA

Tinker

AFB, OK

F Y

4.3.2 Integrated Management Support:

4.3.2.1 Contractor Program Manager: For all tasks required by this PWS, the contractor shall identify and maintain a program manager (PM). The program manager shall have a defined and direct line of authority and responsibility over all aspects of the work effort. The contractor’s work progress, status and any corrective action shall be documented (CDRL A006, Attachment Two).

4.3.2.2 Contractor Interim Reporting: The contractor shall submit monthly technical status reports on the T-38 IAT and L/ESS program’s progress (CDRL A006, Attachment Two). Reports shall be relatively error free and technically correct, as per the guidelines of Table 1.

4.3.2.3 Contractor Manpower Report: The contractor shall report ALL contractor labor hours

(including subcontractor labor hours) required for performance of services provided under this contract for the IATP via a secure data collection site. The contractor is required to completely fill in all required data fields at http://www.ecmra.mil.

Reporting inputs will be for the labor executed during the period of performance for each government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all data shall be reported no later than

31 October* of each calendar year. Contractors may direct questions to the CMRA help desk.

4.3.3 Management Systems Requirements: Management systems requirements are to be provided by the contractor.

4.3.4 Validation Program: The contractor shall work towards the T-38 IATP’s improved performance in terms of processing speed, documentation, and reporting as follows:

1) Examine ways to speed processing. First, determine the CPU time breakdown for each step in the prediction process (data retrieval, conversion to stress, rain-flow, AFGROW, etc.). Second, examine the steps which take the most time and see if there is a way to improve performance. Third, look at parallel processing. This would allow the contractor the flexibility to add more FCLs in the future without impacting the reporting process.

2) Document the process for system validation with the Southwest Research Institute http://www.ecmra.mil/

8 T-38 IATP and L/ESS – Phase XX

(SwRI) generated inspection intervals. Add the ability to run the specific blocks of flight data files used in the SwRI analyses without impacting the database. The intent here is to develop an organic process for system validation.

3) Continue to improve automated mission identification (primarily SUPT).

4) Continue to improve L/ESS reporting.

4.3.5 Maintainability Program:

4.3.5.1 T-38 IATP and L/ESS Maintainability: The contractor is responsible for developing, calibrating, and maintaining the IATP and L/ESS software support system for use at Tinker AFB’s ASIMIS facilities. As the program integrator, the contractor shall develop a plan to maintain the infrastructure of the IATP and L/ESS system, and provide seamless interfacing with Boeing’s IMIS.

4.3.5.2 Continuation of Essential DoD Contractor Services During Crisis: In accordance with DODI 1100.22 (Dated 12 April 2010), this requirement is not considered mission essential.

5 APPENDICES AND ATTACHMENTS

5.1 Applicable Documents

5.1.1 Document Availability and Delivery: If the government deems appropriate, the contractor may use other applicable documents. Also, the contractor shall request necessary documents from the government, as required. In turn, the government shall supply all required TOs and TCTOs for the contractor to perform the tasks of this PWS.

5.2 Applicable CDRLs

5.2.1 CDRL List: The deliverable products (CDRL list) for this PWS are presented in Table

3 (see Attachment Two).

Note: See DD Form 1423 for further details.

5.2.2 Contractor Reporting: The contractor shall submit reports in accordance with the DIDs specified in DD form 1423 (CDRLs A001, A004, A005 and A006, Attachment Two) with the following stipulations. Tables, figures, drawings, etc. shall be placed immediately following their reference in the main body of the text (i.e. same page if possible or on the next page). Reports shall be submitted in electronic format in both

Microsoft Word for Windows and Adobe Acrobat (.pdf) format to the T-38 ASIP Manager at AFLCMC/WLDE. Any necessary corrections shall be made within 30 days of government notification.

9 T-38 IATP and L/ESS – Phase XX

ACRONYMS AND ABBREVIATIONS

ACStrSeq - Aircraft Stress Sequence Program

AETC - Air Education and Training Command

AF - Air Force

AFB - Air Force Base

AFI - Air Force Instruction

AFPD - Air Force Policy Direction

AirStats - Flight Loads Post-processing Software

ARO - After Receipt of Order

ASIMIS - Aircraft Structural Integrity Monitoring Information System

(Tinker AFB, OK)

ASIP - Aircraft Structural Integrity Program

COTS - Commercial Off-the-Shelf

DoD - Department of the Defense

DTA - Damage Tolerance Analysis

FCL - Fatigue Critical Location

FEA - Finite Element Analysis

FEM - Finite Element Model

FLDR - Flight Loads Data Recorder

FS - Fuselage Station

IATP - Individual Aircraft Tracking Program

IAW - In Accordance With

IFF - Introduction to Fighter Fundamentals

IMIS - Integrated Maintenance Information System (Boeing, St. Louis)

ISIDR - Instrumentation System/Installation Description Report

Mgr. - Manager

MIL-STD - Military Standard

MSC/NASTRAN - Finite Element computer program maintained by the MacNeal-Schwendler Corporation

MSFT - Microsoft

NGC - Northrop Grumman Corporation

NGTS - Northrop Grumman Technical Services

NOR - Northrop

OEM - Original Equipment Manufacturer

OO-ALC - Ogden Air Logistics Center

Para. - Paragraph

PM - Project Manager

PMP - Propulsion Modernization Program

PO - Program Office

PoP - Period of Performance

PWS - Performance Work Statement

QA - Quality Assurance

Ref. - Reference

Sect. - Section

S/N - Serial Number

SPM - System Program Manager

10 T-38 IATP and L/ESS – Phase XX

ACRONYMS AND ABBREVIATIONS (CONT)

SS - Service Summary

SUPT - Specialized Undergraduate Pilot Training

SwRI - Southwest Research Institute

TBD - To Be Determined

TCTO - Time Compliant Technical Order

TO - Technical Order

USAF - United States Air Force

VGH - Velocity, Acceleration (G), and Altitude (H)

WS - Wing Station

A1-1 T-38 IATP and L/ESS – Phase XX

ATTACHMENT ONE: LIST OF APPLICABLE DOCUMENTS

Department of Defense (DoD) Specifications

1) Air Force Policy Directive (AFPD) 63-1, Integrated Life Cycle Management, 3 June 2016.

2) Air Force Instruction (AFI) 63-101, Integrated Life Cycle Management, 6 September 2016.

3) AFI 63-140, Aircraft Structural Integrity Program, 7 April 2014.

Department of Defense (DoD) Standards

4) MIL-STD-1530D, Aircraft Structural Integrity Program, 31 August 2016.

5) MIL-STD-1840C, Automated Interchange of Technical Information, 26 June 1997.

Other Publications and Work Statements

6) “T-38C Flight Loads Data Recorder (FLDR) and Individual Aircraft Tracking Program

(IATP) Evaluation – Phase I: T-38C FLDR Program at Moody AFB, Georgia, and

Preliminary FLDR and IATP Study,” USAF SOW, June 2004.

7) “T-38C Flight Loads Data Recorder (FLDR) and Individual Aircraft Tracking Program

(IATP) Evaluation – Phase II: T-38C FLDR Program at Moody AFB, Georgia, and

Preliminary FLDR and IATP Study,” USAF SOW, June 2005.

8) “T-38C Flight Loads Data Recorder (FLDR) and Individual Aircraft Tracking Program

(IATP) Evaluation – Phase III: T-38C FLDR Program at Moody AFB, Georgia, with

IATP and L/ESS Development and Preliminary Implementation,” USAF SOW, January

2006.

9) “T-38C Flight Loads Data Recorder (FLDR) and Individual Aircraft Tracking Program

(IATP) Revitalization – Phase IV: T-38C FLDR Program at Four AETC Bases with

Continued IATP and L/ESS Development and Implementation,” USAF SOW, June 2007.

10) T-38C Flight Loads Data Recorder (FLDR) and Individual Aircraft Tracking Program

(IATP) Revitalization - Phase V: T-38C FLDR Program at Four AETC Bases with

Continued IATP and L/ESS Development and Implementation USAF PWS, August 2008.

11) “T-38C Flight Loads Data Recorder (FLDR) and Individual Aircraft Tracking Program

(IATP) Revitalization – Phase VII: F i n a l T-38C FLDR Program at Four AETC

Bases with Continued IATP and L/ESS Development and Implementation,” USAF PWS, August 2011.

A1-2 T-38 IATP and L/ESS – Phase XX

12) “T-38C Flight Loads Data Recorder (FLDR) and Individual Aircraft Tracking Program

(IATP) Revitalization – Phase X: Continued T-38 IATP and L/ESS Development and

Implementation,” USAF PWS, June 2013.

13) “T-38C Flight Loads Data Recorder (FLDR) and Individual Aircraft Tracking Program

(IATP) Revitalization – Phase XII: Continued T-38 IATP and L/ESS Development and

Implementation,” USAF PWS, May 2014.

14) “T-38C Flight Loads Data Recorder (FLDR) and Individual Aircraft Tracking Program

(IATP) Revitalization – Phase XIV: Continued T-38 IATP and L/ESS Development and

Implementation, USAF PWS, February 2015.

15) NOR 04-101, “Instrumentation/System Installation Description Report for T-38C Flight

Loads Data Recorder Program (Moody AFB),” November 2004 (revised May 2005).

16) NG-0144 -T38-00010008-15-RPT, “T-38 IATP User’s Manual – Phase XII,” September

2015.

17) NG-0145 -T38-00010008-15-RPT, “T-38 IATP and L/ESS Development Report – Phase

XII,” September 2015.

18) “Edit/Pre-Analysis User’s Manual,” Alamo Technology, Inc. Report.

19) “AirStats User's Manual,” SwRI Report.

Note: If the government deems appropriate, the contractor may use other applicable documents.

A2-1 T-38 IATP and L/ESS – Phase XX

ATTACHMENT TWO: APPLICABLE CDRLS

Table 3 - CDRL List for the T-38C IATP and L/ESS Program – Phase XX

PWS Paragraph CDRL CDRL Description DID

4.3.1.1.2, 5.2.2 A001 Technical Report – Study/Services T-

38 IATP and L/ESS Development

Report – Phase XX

DI-IPSC-80508B

4.3.1.1.3 A002 Computer Software Product End Items

T-38 IATP Software – Ver. 10

DI-AVCS-80700A

4.3.1.1.4 A003 T-38 IATP and L/ESS Software

User Manual - Ver. 10

DI-IPSC-81443A

4.3.1.1.5, 5.2.2 A004 Technical Report - T-38 IATP and L/ESS Final Report

DI-MISC-80508B

4.3.1.2.1, 4.3.1.2.2, 4.3.1.2.3, 5.2.2

A005 Status Report DI-MGMT- 80368A

4.3.2.1, 4.3.2.2, 5.2.2 A006 Progress, Status and Management Report

DI-MISC-80227

http://assist.daps.dla.mil/online/parms/mainframe.cfm?ident_number=205530 http://assist.daps.dla.mil/online/parms/mainframe.cfm?ident_number=205921 http://assist.daps.dla.mil/online/parms/mainframe.cfm?ident_number=205922