PWS_T_38_RMS_Support_Final_24_Sep_18.pdf

PERFORMANCE WORK STATEMENT

For the:

T-38 Reliability, Maintainability, and Supportability (RM&S)

FY19B Contractor Support

24 September 2018

Prepared by:

Michael P. Blinn, T-38 ASIP Mgr.

AFLCMC/WLDE

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

AIR FORCE LIFE CYCLE MANAGEMENT CENTER

MATURE AND PROVEN AIRCRAFT DIVISION

ENGINEERING BRANCH

STRUCTURAL INTEGRITY AND ANALYSIS SECTION

HILL AIR FORCE BASE, UTAH 84056

mailto:michael.blinn@hill.af.mil i T-38 RM&S Support

Last Rev. Date: 24 Sep 18

TABLE OF CONTENTS

Page

LIST OF TABLES ........................................................................................................................ ii

RECORD OF REVISIONS ......................................................................................................... iii

1.0 DESCRIPTION OF SERVICES

1.1 Scope

1.2 Period of Performance

2.0 SERVICE SUMMARY

3.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES

3.1 Reports Provided

3.2 Security and Access to Government Facilities and Equipment

3.2.1 Security Clearance

3.2.2 Access to Government Facilities

3.2.3 Obtaining and Retrieving Base Identification:

3.2.4 Entry Procedures to Controlled or Restricted Areas:

3.2.5 Procedures and Controls

3.2.6 Cybersecurity

3.2.7 Network Security

3.2.8 Operational Security (OPSEC)

4.1 GENERAL INFORMATION

4.2 General Requirements

4.3 Specific Requirements

4.3.1 Contractor Services

4.3.2 Integrated Management Support

4.3.3 Management System Requirements

4.3.4 Contractor Task Order Management Requirements

5.1 APPENDICES AND ATTACHMENTS

5.2 Applicable Documents

5.2.1 Document Availability and Delivery

5.3 Applicable CDRLs

5.3.1 CDRL List

5.3.2 Contractor Reporting

ACRONYMS AND ABBREVIATIONS

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

ATTACHMENT TWO: TASK REQUEST FORM ................................................................. A2-1

ATTACHMENT THREE: APPLICABLE CDRLS................................................................. A3-1

ATTACHMENT FOUR: TM-86-01Q………………………………………………………..A4-1

2 T-38 RM&S Support

LIST OF TABLES

Page

Table 1 – Service Summary for T-38 RM&S Contractor Support

Table 2 – Task Categories

Table 3 – CDRL List for the RM&S Contractor Support......................................................... A3-1

3 T-38 RM&S Support

RECORD OF REVISIONS

REV DATE

PAGE(S)

AFFECTED

SECTION

AFFECTED

REASON FOR REVISION

- 24 Sep 18 n/a n/a Initial release of the PWS

1 T-38 RM&S Support

1.0 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 Mechanical Systems Integrity Program (MECSIP), T-38 Avionics

Integrity Program (AVIP), T-38 Mature and Proven Aircraft Branch (MAPA), T-38

System Program Office (SPO), Air Education and Training Command (AETC), and other T-38 related commands.

The T-38 SPO at Ogden ALC, UT, is responsible for the reliability, availability, safety, and mission readiness of the T-38 Talon trainer jet. The T-38 Talon is a twin engine, high altitude, supersonic jet trainer used in a variety of roles because of its design, economy of operations, ease of maintenance, high performance, and exceptional safety record. AETC is the primary user of the T-38 for missions such as: 1) Specialized

Undergraduate Pilot Training (SUPT), Introduction to Fighter Fundamentals (IFF), and

3) Euro-NATO Joint Jet Pilot Training (ENJJPT). Air Combat Command (ACC), Air

Force Materiel Command (AFMC), the National Aeronautics and Space

Administration (NASA), the U.S. Navy, and foreign militaries also use the T-38 in various roles. The T-38 requires multiple integrity programs to ensure the overall weapon system safety, suitability, and effectiveness (or OSS&E).

The T-38 aircraft is currently being managed with the benefit of both the experience and historical analyses available from the Northrop Grumman Corporation (NGC), the

Original Equipment Manufacturer (OEM). The T-38 SPO requires the ability to collect and analyze data from Global Combat Support System (GCSS) and other government database systems to identify potential systems and related key components that may require action to prevent negative impact on Mission Capability (MC) rates and Fleet

Availability (FA). The goal of this PWS is to propose continued OEM support to the

T-38 SPO for the Reliability, Maintainability and Supportability (RM&S) of the T-38.

The scope of RM&S includes support for sustainment of weapon system operational safety, suitability, and effectiveness. This proposed contract would allow the SPO to continue to contact the OEM by phone or email, cite the specific task order and task number, and receive rapid input from the OEM.

The T-38 weapon system RM&S is dependent upon multiple disciplines to ensure the weapon system’s viability for the future. This effort allows direct access to the

Northrop T-38 research engineers, design engineers, test and evaluation engineers, sustainment engineers, logisticians, OEM data research, and other technical capabilities found within NGC. The extensive RM&S analysis and engineering experience within

NGC as performed on other major weapon systems would provide critical and timely support for system analysis and sustainment of the T-38 and allow the SPO to re-establish a “cradle-to-grave” T-38 weapon system management approach. Analysis and support includes but is not limited to technology application evaluations, analysis of alternatives, requirements development, operational utility evaluations, proto-type design, design development, test and evaluation, configuration analysis and support, 2 T-38 RM&S Support durability, safety, reliability, supportability, failure modes and consequences, cost of ownership, sustainment improvements, deficiency and mishap evaluations, analytical condition inspections (ACIs), and maintenance support. This approach would maximize the T-38 SPO’s ability to ensure that the T-38 fleet meets availability, cost, and capability benchmarks required to satisfy its Air Force mission and remain viable to the end of the programmed life cycle.

1.1 Scope:

The contractor shall provide the appropriate level of engineering support to address all

CDRL deliverables as described in this PWS. Tasks will be assigned by either the government program manager (PM) or the engineering lead and may include, but are not limited to, the following activities:

Conduct engineering analysis, design, test, and sustainment activities as required by T-38 SPO.

Provide RM&S analyses and studies into areas impacting availability, maintainability, sustainability and cost as required by the SPO.

Provide engineering and RM&S support for Product Improvement Working Group

(PIWG) like activities as required.

Provide system integrity engineering analysis support as required by T-38 SPO and/or integrity manager and/or chief engineer.

Analysis and support of technology application evaluations, analysis of alternatives, requirements development, operational utility evaluations, proto-type design, design development, test and evaluation, configuration analysis and support, durability, safety, reliability, supportability, failure modes and consequences, cost of ownership, sustainment improvements, deficiency and mishap evaluations, analytical condition inspections, and maintenance support.

Any other engineering tasks that are either too small for an individual task orders or for which schedule constraints preclude establishing a new task order.

For tasks that require the contractor to provide written technical procedures, follow the instructions provided in Technical Manual Contract Requirements (TMCR)

TM-86-01Q. (Attachment Four)

Assist with mapping of T-38 airframe damage using NLign computer software program. (CDRL A0002, Attachment Three).

1.2 Period of Performance:

The period of performance for this PWS is 12 months.

2.0 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

3 T-38 RM&S Support management related.

4 T-38 RM&S Support

Table 1 – Service Summary (SS) for the T-38 RM&S Contractor Support

Performance Objectives

PWS

Reference

Performance Threshold

(Minimum Acceptable)

Engineering Technical

Activities: Contractor to provide support engineering analyses, assessments, and research towards accomplishment of this PWS.

4.2.1 through 4.2.4

For engineering analyses (or assessments or studies): All actions accomplished as required with no more than one disapproval by the government for technical discrepancies per technical report. Any necessary corrections must be made within 30 days of government notification" to the Performance

Threshold column/Engineering Technical Activities row of the Service Summary.

Technical Documentation:

Contractor to generate timely, error free technical, management, and all other reporting and documentation;

includes activities such as monthly financial reporting, meeting minutes, etc.

4.2.1.2 through

4.2.4, 5.2.1, 5.2.2

95% of revisions are error free in the final product.

Preliminary documentation of the reports to be 90% error free.

3.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES:

3.1 Reports Provided:

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

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

3.2 Security and Access to Government Facilities and Equipment:

3.2.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.2.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.

5 T-38 RM&S Support

3.2.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.2.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.2.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 unclassified information on personal information technology systems or via personal e-mail.

3.2.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.2.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

6 T-38 RM&S Support 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.2.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.0 GENERAL INFORMATION:

4.1 General Requirements:

The T-38 aircraft is currently being managed with the benefit of both the experience and historical analyses available from the Northrop Grumman Corporation (NGC), the

Original Equipment Manufacturer (OEM). The T-38 SPO requires the ability to collect and analyze data from Global Combat Support System (GCSS) and other government database systems to identify potential systems and related key components that may require action to prevent negative impact on mission capability (MC) rates and fleet availability (FA). The goal of this effort is to provide vital and timely OEM support to the Reliability, Maintainability, and Supportability (RM&S) of the T-38. Scope of

RM&S will include support for sustainment of weapon system operational safety, suitability, and effectiveness. Operational Safety, Suitability, and Effectiveness

(OSS&E) will benefit from the T-38 weapon system integrity analysis and support which is dependent upon multiple integrity disciplines to ensure weapon systems viability for the future. This PWS allows the government to contact the OEM by phone or e-mail, cite the specific task order, and receive rapid input from the OEM.

4.2 Specific Requirements:

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

4.2.1.1 Data Compatibility: All data will be presented in a format useable by government entities. For example, the government uses Microsoft Word, Adobe Acrobat, and similar word processing software.

4.2.1.2 Task Assignment:

4.2.1.2.1 Tasks shall be assigned by the a T-38 PM and engineers and accepted by the contractor using the Task Request Form (Attachment Two) with an individual WSMT number assigned to each task. The contractor shall not be required to accept tasks if the cost to execute them will result in exceeding the value of the contract.

7 T-38 RM&S Support

4.2.1.2.2 Following assignment of a WSMT number the contractor shall review and categorize each task according to the criteria in Table 2 (Task Categories). Task category designation shall be subject to approval by the T-38 PM.

4.2.1.2.3 Tasks categorized as Type I “minor tasks” shall be assigned under one “task” number and submitted to the contractor by either e-mail or telephone call.

4.2.1.2.4 Exceptions:

4.2.1.2.4.1 Any task requiring subcontractor support shall automatically be categorized as a Type

III task.

4.2.1.2.4.2 Any Type I task which, when evaluated, would require more than 90 days to complete shall be automatically categorized as a Type II task (subject to approval by the T-38

PM).

4.2.1.2.4.3 The contractor shall not proceed with any tasks submitted without a task number until written verification has been received from the T-38 PM.

4.2.1.3 Data Documentation: All data researched for this project will be provided in the individual task order reports. Details of the reporting are as follows:

For technical status reporting, the contractor shall provide quarterly informal status reports to the T-38 PM detailing how hours spent during the month were distributed among the assigned tasks. The status report shall identify the hours spent for each

Type II or Type III task during the reporting month versus the hours allocated for the task. Type I tasks shall be lumped into one Type III task for reporting purposes, with a table included in the report which lists all Type I tasks assigned to date and the status of each, but with hours spent reported in aggregate. Type II and Type III tasks shall be listed individually. Report shall include a table listing all Type II and

Type III tasks with a summary of hours spent to date. Report format shall be determined by the contractor.

For program management reporting, the contractor shall provide quarterly status reporting on their tasks. The status report shall include a brief technical description of individual tasks, program management issues, and financial information (CDRL

A005, Attachment Three).

For engineering dispositions (other than those defined as Type I), the contractor shall provide a final task report for individual dispositions, size to be commensurate with the amount of engineering activities involved, minimum to be completion of the task request form, Attachment Two. For larger efforts, a separate report might be required; this shall be determined on a case-by-case basis and coordinated with the T-38 PM and the responsible engineer. Format for separate reports shall be according to CDRL A007, Attachment Three.

At the conclusion of the Period of Performance (PoP) for this effort, a final report is required, including a summary of each of the task orders of this PWS. The

8 T-38 RM&S Support intention of this document is to catalogue the activities for the contract’s PoP

(CDRL A005, Attachment Three).

4.2.1.3.1 Task Specific Deliverables:

1) Project plan, which includes the problem definition, a proposed plan to investigate and resolve problem, identification of any travel required, details of the proposed final deliverable(s) for the task, and identification of entrance and exit criteria for each milestone, contractor format.

2) Rough-Order-of-Magnitude (ROM) estimate, contractor format.

3) Proposed task schedule, prepared using Microsoft Project (.mpp file format, contractor format).

4) Chart of proposed technical performance measures, contractor format.

4.2.1.4 Formal Evaluations: The following formal evaluations are to be supported by the contractor:

1) Preliminary Program Review: A preliminary program review for the contractor to present their refined “way ahead” for the RM&S support, and to 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 and meeting minutes as part of the first status report (CDRL A005, Attachment Three).

2) Final Program Review: A final program review for the contractor to present their results and discuss the outcomes of their RM&S support shall be held sometime during the last month of the contract PoP. The contractor shall provide a PPT document and meeting minutes as part of the last status report (CDRL A005, Attachment Three).

4.2.1.5 Contractor Travel: The following are the contractor travel requirements:

1) Miscellaneous Program Support Trips: The contractor is authorized five miscellaneous trips for a maximum two people each trip (minimum one engineer), for up to five days (each trip) to any of the following locations: 1) Hill AFB, UT;

2) Randolph AFB, TX; 3) El Segundo, CA; 4) St. Augustine, FL; or 5) Southwest

Research Institute (SwRI), San Antonio, TX. In addition, the contractor should consider travel to other locations within the continental US that would be required in support of this PWS.

2) These trips are intended to provide the contractor flexibility in supporting the

RM&S activities; as such, there are no firm requirements. Miscellaneous trips shall be reported in the quarterly reports (CDRL A005, Attachment Three).

3) Type II, III, and IV individual tasks may require more than the five (5) trips listed above. ROM estimates for those tasks shall clearly state the number of support trips required and cost for those trips. The requirement for additional support trips will be reviewed with the ROM estimate and approved or disapproved with the task. No additional funding will be provided for additional support trips.

Table 2 – Task Categories

Type Completion

Time

Examples Deliverables Delivery Schedule for

Deliverables

Authorization to

Proceed

I <50 hours Minor Tasks such as:

Requests for technical data

Drawing revisions for CSI designations

Preliminary investigations of problem reports

Planning documents (unless approved by the T-38 PM to move to a Type II category).

E-mail response directly to requestor, contractor format; cc to the T-38 PM.

Coordinated with requestor. Automatic upon receipt of task.

II 50-325 hours Intermediate Tasks such as:

Aft Canopy Study

Follow-on investigations of problem reports

Project Plan, other deliverables as described in the

Project Plan.

Project Plan to be delivered within 20 business days unless previously approved by the T-38 PM; other deliverables to be submitted as described in the Project Plan.

Automatic upon approval of Project Plan by the T-38 PM.

III 325-1,000 hours Major Tasks such as:

Flight Loads Data

Collection

PMP Baseline

Recovery

Aft Fuselage

Hydraulic Coupling

Analysis

Project Plan, ROM estimate, proposed task schedule, technical performance measures, and other deliverables as described in the

Project Plan.

Project Plan to be delivered within 30 business days unless previously approved by the T-38 PM; ROM estimate, proposed task schedule, and technical performance measures to be delivered 45-60 days following government approval of Project Plan;

other deliverables to be submitted as described in the Project Plan/task schedule.

Pending receipt of authorization to proceed letter from the T-38

Contracting Office following delivery and approval of

Project Plan, ROM estimate, proposed task schedule, and technical performance measures.

IV >1,000 hours To be processed similar to Type III tasks but only after written direction from the T-38 Contracting Office.

8 T-38 RM&S Support

9 T-38 RM&S Support

4.2.2 Integrated Management Support:

4.2.2.1 Contractor Program Manager: For all tasks required by this PWS, the contractor shall identify and maintain a program manager. The contractor PM 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 A005, Attachment Three).

4.2.2.2 Contractor Interim Reporting: The contractor shall submit interim reports as appropriate with the requirements of each individual sub-task (see Para. 4.2.1.2).

4.2.3 Management Systems Requirements:

Management systems requirements are to be provided by the contractor.

4.2.3.1 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.

4.2.4 Contractor Task Order Management Requirements: Task management by the contractor shall include but is not limited to:

4.2.4.1 Providing monthly informal status reports to the T-38 PM detailing how hours spent during the month were distributed among the assigned tasks.

4.2.4.2 Providing monthly cost-schedule-performance programmatic reports.

4.2.4.3 Participating in quarterly programmatic briefings.

4.2.4.4 All internal management reviews necessary for any deliverable required for Type II, Type III, or Type IV tasks.

4.2.4.5 Program management support.

4.2.4.6 Pricing for ROM estimates.

5.0 APPENDICES AND ATTACHMENTS:

5.1 Applicable Documents:

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

10 T-38 RM&S Support

5.2 Applicable CDRLs:

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

2 (CDRLs A002, A005 and A007, Attachment Three).

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 A002, A005 and A007, Attachment

Three) 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 electronically in both

Microsoft Word for Windows and Adobe Acrobat (.pdf) format to the T-38 Mechanical

Systems section at AFLCMC/WLDEB.

A1-1 T-38 RM&S Support Last

Rev. Date: 24 Sep 18

ACRONYMS AND ABBREVIATIONS

ACC - Air Combat Command

ACI - Analytical Condition Inspection

AETC - Air Education and Training Command

AFB - Air Force Base

AFMC - Air Force Materiel Command

AIS - Automated Information System

ALC - Air Logistics Center

ARO - After Receipt of Order

ASIP - Aircraft Structural Integrity Program

AVIP - Avionics Integrity Program

CCB - Configuration Control Board

CDRL - Contract Data Requirements List

CS - Cybersecurity

CUI - Controlled Unclassified Information

DoD - Department of Defense

ENJJPT - Euro-NATO Joint Jet Pilot Training

FA - Fleet Availability

GCSS - Global Combat Support System

IAW - In Accordance With

IFF - Introduction to Fighter Fundamentals

IMIS - Integrated Maintenance Information System

IT - Information Technology

MAPA - Mature and Proven Aircraft

MC - Mission Capability

MECSIP - Mechanical Systems Integrity Program

NGC - Northrop Grumman Corporation

OC-ALC - Oklahoma City Air Logistics Center

OEM - Original Equipment Manufacturer

OSS&E - Operational System Safety, Suitability and Effectiveness

PIWG - Product Improvement Working Group

PM - Program Manager

PoP - Period of Performance

PWS - Performance Work Statement

RM&S - Reliability, Maintainability and Supportability

ROM - Rough Order of Magnitude

SPO - System Program Office

SS - Service Summary

SUPT - Specialized Undergraduate Pilot Training

TO - Technical Order

TCTO - Time Compliance Technical Order

USAF - United States Air Force

WSMT - Weapon System Management Tool

A2-1 T-38 RM&S Support Last

ATTACHMENT ONE: LIST OF APPLICABLE DOCUMENTS

Department of Defense (DoD) Specifications:

1) Air Force Policy Directive 63-1, “Acquisition and Sustainment Life Cycle Management,”

3 April 2009.

2) Air Force Instruction 63-1001, “Aircraft Structural Integrity Program,” 18 April 2002.

Department of Defense (DoD) Standards:

3) MIL-STD-1530C, “Aircraft Structural Integrity Program,” 3 August 2010.

4) MIL-STD-1798, “Mechanical Equipment and Subsystem Integrity Program,” 24 January

2010.

5) MIL-HDBK-1783b(2), Engine Structural Integrity Program,” June 2009.

6) MIL-STD-1796A, “Avionics Integrity Program,” 13 October 2011.

Note: If the T-38 SPO/PM deems appropriate, the contractor may use other applicable documents.

A3-1 T-38 RM&S Support Last

ATTACHMENT TWO: TASK REQUEST FORM

Reliability, Maintainability &

Supportability Task Request Form

No.

Page:

Effective: 24 Sept 18

Revision:

Approved:

Authorized documents are published online only - verify any copy against the online system before use

Section I – To be completed by Government Program Manager

Task No.:

Title:

Date Originated: Date Response Requested By:

Govt. Program Manager: Telephone No.:

Requestor: Telephone No.:

Deliverable Requested (report (size and format), analysis, drawing, etc.):

Initial Problem Description:

Task Category: I II III IV

Are there attachments with this form? Yes No If yes, list:

Section II – To be completed by NGTS personnel

Expanded Problem Description:

Investigation/Analysis/Testing:

Solutions/Recommendations:

Section III – To be completed by NGC personnel

Project Engineer: Date:

NGTS Project Manager: Date:

Date returned to Government Program Manager:

Manhours Used:

ATTACHMENT THREE: APPLICABLE CDRLS

Table 3 – CDRL List for the T-38 RM&S FY19B Contractor Support

PWS Paragraph CDRL CDRL Description DID

1.1, 5.2.1, 5.2.2 A002 Computer Software Product End Item DI-AVCS-80700A

4.2.1.3, 4.2.1.4, 4.2.1.5, 4.2.2.1, 5.2.1, 5.2.2

A005 Status Reports DI-MGMT-80368A

4.2.1.3, 5.2.1, 5.2.2 A007 Scientific and Technical Reports:

- Individual Task Order Reports

DI-MISC-80508B

A3-1 T-38 RM&S Support