T-6A_ADS_B_Out_SOW_Final_Draft_5_Nov_15.docx

FOR OFFICIAL USE ONLY

JOINT PRIMARY AIRCRAFT TRAINING SYSTEMS (JPATS)

STATEMENT

OF WORK

FOR AUTOMATIC DEPENDENT SURVEILLANCE–BROADCAST (OUT)

FOR THE T-6A AIRCRAFT

Prepared for:

Mobility Directorate, Training Aircraft Division Wright-Patterson AFB, OH JPATS T-6A Programs

Prepared by:

T-6A Integrated Product Team JPATS Program Office Wright-Patterson AFB, OH and

PMA273

Patuxent River, MD

2 Nov 2015

TABLE OF CONTENTS

1 SCOPE

This Statement of Work (SOW) defines the efforts required to design, develop, integrate, test, certify, and install the Automatic Dependent Surveillance–Broadcast (ADSB) (Out) capability into the T-6A aircraft and the T-6A Aircrew Training Devices (ATDs). A technical data package will be required for updating the associated technical data and to support the operations and maintenance of the ADS-B (Out) solution in the air vehicle and the ATDs. In addition, aircrew and maintenance training will be required to operate and maintain the ADS-B (Out) technical solution. This contract will cover the Technology Development Phase, the Engineering, Manufacturing and Development Phase, and the Production Phase of the program.

1.1 Background

ADS-B (Out) is a requirement mandated by the Federal Aviation Administration (FAA) for aircraft operating within the National Airspace System as specified by Title 14 Code of Federal Regulations Part 91.225. This mandate directs a nationwide transition to ADS-B (Out) technology by 2020. ADS-B (Out) is a system by which aircraft repeatedly broadcast current position, altitude, airspeed, identification, and other information over a common data link. The functionality of ADS-B (Out) is intended to replace or augment ground based radar and enhance traffic flow. To meet this mandate it will be necessary to configure the T-6A aircraft with specific components that provide this capability and integrate in a fashion consistent with requirements set forth herein and that focus on minimizing impacts to training of ground crew and aircrew.

2 APPLICABLE DOCUMENTS

2.1 Government Documents

2.1.1 Specifications and Standards

The following Government specifications and standards form a part of this SOW to the extent specified herein. If a newer version of any the specifications or standards identified below have been published then they shall be used to execute the ADS-B (Out) tasks as stated in this SOW. The latest revision at the time of contract award shall be used.

Military Standard (MIL-STD)-882E, DOD Standard Practice: System Safety

MIL-STD-1472G, DOD Design Criteria Standard: Human Engineering

Military Standard (MIL-E)-7016, Military Specification: Electric Load and Power Source Capacity, Aircraft, Analysis of

MIL-STD-130M, DOD Standard Practice: Identification Marking of US Military Property

2.1.2 Other Government Documents, Drawings, and Publications

The following Government documents, drawings, and publications form a part of this SOW to the extent specified herein. The latest revision at the time of contract award shall be used.

Technical Order (T.O.) 00-35d-54, USAF Deficiency Reporting, Investigation, and Resolution

Title 14 Code of Federal Regulations (CFR) Part 91.225, Automatic Dependent Surveillance-Broadcast Out Equipment and Use

Advisory Circular (AC) 20-165A, Airworthiness Approval of Automatic Dependent Surveillance-Broadcast Out Systems

FAA Order 8110.101, Type Certification Procedures for Military Commercial Derivative Aircraft

FAA FAR Part 23, Airworthiness Standards: Normal, Utility, Acrobatic and Commuter Category Airplanes

Military Handbook (MIL-HDBK)-516C, DOD Handbook: Airworthiness Certification Criteria

Air Force Integrated Baseline Review Process Guide, Version 3

Department of Defense Manual (DOD 5000.04-M-1), Cost and Software Data Reporting Manual

Air Force Instruction (AFI) 63-101, Integrated Management – Acquisition/Logistics

Air Force Pamphlet (AFPAM) 63-128, Integrated Life Cycle Management

DoDI 5000.02, Operation of the Defense Acquisition System

AFI 63-1201, Implementing Operational Safety Suitability and Effectiveness and Life Cycle Systems Engineering

System Safety/Environmental Management Plan for Joint Primary Aircraft Training System

MIL-HDBK-61A, Configuration Management Handbook

Manufacturing Readiness Level (MRL) Deskbook

AFI 63-112, Cockpit Working Groups

Defense Federal Acquisition Regulation Supplement (DFARS) Clause 252.211-7003, Item Identification and Valuation

Ground-Based Training System (GBTS) Program Unique Specifications Document, BC 25301 Rev B

JPATS Aircrew Training Device Operator Manual

JPATS Aircrew Training Device Maintenance Manual

MIL-PRF-32216, Performance Specification: Evaluation of Commercial Off the Shelf Manuals and Preparation of Supplemental Data

DOD 5220.22-M, National Industrial Security Program Operating Manual

DOD 5400.7-R, Directive: DOD Freedom of Information Act Program

DOD 5200.01, DOD Information Security Program Manual: Overview, Classification, and Declassification

DOD 5200.2-R, Personnel Security Program

DODI 8500.01, Cybersecurity

DODI 8582.01, Security of Unclassified DoD Information on Non-DoD Information Systems

Systems Requirements Document – Automatic Dependent Surveillance Broadcast (Out) Capability for the T-6A

T-6A ADS-B (Out) Test and Evaluation Master Plan

JPATS Prime Item Product Function Specification (PIPFS), Rev I, dated 13 Dec 2012 (Beechcraft Defense Company BS24806)

2.2 Non-Government Documents

The following non-Government documents, drawings, and specifications form a part of this SOW for reference herein. Applications for copies should be addressed to the originator of each subject document.

American Society of Mechanical Engineers (ASME) Standard Y14.38M, Abbreviations and Acronyms for Use on Drawings and Related Documents 2013

American National Standards Institute (ANSI)/Electronic Industries Association (EIA) Standard 632, Processes for Engineering a System

ANSI/Government Electronics Information Technology Association (ANSI/GEIA) Standard 0009, Reliability Program Standard for Systems Design, Development, and Manufacturing

International Organization for Standards (ISO)/American Society of Quality (ASQ) ANSI/ISO/ASQ Standard 9001-2008, Quality Management Systems and Requirements

National Institute of Standards and Technology (NIST) Special Publication (SP) 800-60 Vol 2 Rev 1, D.11.3 Air Transportation and Information Type

NIST SP 800-30 Rev 1, Guide for Conducting Risk Assessments

NIST SP 800-53 Rev 4, Appendix E (Table E-1)

SAE International Standard AS5553, Counterfeit Electronic Parts; Avoidance, Detection, Mitigation, and Disposition

Society of Allied Weight Engineers (SAWE) RP7, Mass Properties Management and Control for Military Aircraft, Revision D

2.3 Availability of Government Specifications and Standards

Unless otherwise indicated, copies of the specifications, handbooks, and standards cited in 2.1.1 are available from the Standardization Document Order Desk, 700 Robbins Avenue, Building 4D, Philadelphia PA 19111-5094 or the ASSIST Internet site at http://quicksearch.dla.mil/.

2.4 Availability of Other Government Documents, Drawings, and Publications

Requests for copies of those documents listed in paragraph 2.1.2 should be submitted to the Government contracting officer and include the reason the document is needed and how long the document will be needed. The Government will review all request and provide written notification of approval or disapproval. If approved, the Government will provide documents to the T-6A ADS-B (Out) Contractor on contract if the distribution statement associated with that document allows it to be released.

3 REQUIREMENTS

3.1 General

For the T-6A to satisfy FAA AC 20-165A, the ADS-B equipment (transponder and antennas) will need to be integrated with an aircraft position source, a barometric altitude source, an air-ground status source, all associated controls and displays, and, for surface operations, it shall be able to transmit either a heading or ground track. The T-6A is not Traffic Collision Avoidance System (TCAS) II equipped, therefore there is no requirement for the ADS-B equipment to integrate with a TCAS II. The Contractor shall plan, manage, and integrate all program activities to ensure compliance with the contract requirements and timely delivery and completion of tasks detailed in this SOW for the nonrecurring engineering, testing, FAA certification, military airworthiness certification, and installation to integrate ADS-B (Out) capability into the T-6A aircraft and the ATDs. The Contractor shall coordinate with the JPATS program office to perform and document the efforts detailed in the SOW.

3.2 Systems Engineering

The Contractor shall define and implement a rigorous systems engineering approach to ensure that the design criteria, design data, and supportability approach are traceable to the technical requirements for design, development, test, integration, and certification. The Contractor shall deliver a T-6A ADS-B (Out) System Engineering Management Plan (SEMP) in accordance with (IAW) Contract Data Requirements List (CDRL) A017.

3.2.1 Requirements Traceability and Verification

The Contractor shall establish flow-down requirements from the JPATS PIPFS to the ADS-B (Out) Interface Control Document (ICD) as well as lower level ADS-B (Out) Subsystem Performance Specifications and ICDs. The Contractor shall provide ADS-B (Out) Subsystem Performance Specifications to include allocation of system-level functions and performance IAW CDRL A015. The Contractor shall deliver the ICDs IAW CDRL A008. The Contractor shall develop, deliver and maintain a Specification Requirements Verification Matrix (SRVM) IAW CDRL A009. The SRVM shall ensure that all ADS-B (Out) performance specification requirements are met by the Contractor developed design documentation. The SRVM shall demonstrate traceability between these requirements, the associated design documentation, and system functional qualification test documentation. The SRVM shall list the method of verification that will be used to demonstrate that the system requirements in all ADS-B (Out) performance specifications and this SOW have been achieved. Once developed, the SRVM shall be managed in preparation for the ADS-B (Out) Functional Configuration Audit (FCA) to verify compliance with all ADS-B (Out) performance specifications derived from the System Requirement Document (SRD). In the event that changes to the ADS-B (Out) performance specifications are required, the Contractor shall submit a revision to the specification IAW CDRL A015.

3.2.2 Installation and Airworthiness Approval

3.2.2.1 Federal Aviation Administration Certification

The Contractor shall utilize FAA Advisory Circular Number 20-165A in the development process for installation and FAA airworthiness approval of the new system. The Contractor shall provide a Supplemental Type Certificate (STC) per FAA Order 8110.101 IAW CDRL A028. The Contractor shall develop and submit all appropriate data to the FAA and obtain, sustain and retain ownership of the STC for the modification. The certification shall conform to FAA Federal Aviation Regulation (FAR) Part 23. The Contractor shall provide any Airworthiness Directives, Service Bulletins, and Advisory Data applicable to the ADS-B (Out) modification IAW CDRL A007.

3.2.2.2 Military Airworthiness

The Contractor shall develop, implement, and maintain an airworthiness program for the ADS-B (Out) modification, documented in an Airworthiness Plan, which successfully achieves military airworthiness certification for the modification. The plan and program shall comply with USAF policy on airworthiness certification and the JPATS certification basis for the ADS-B (Out) modification IAW CDRL A040. For the ADS-B (Out) modification, the Contractor shall update and maintain a military certification basis document provided by the United States Government (USG) IAW MIL-HDBK-516C. The contactor shall populate column G “substantiating data references” for all criterion marked as applicable in the military certification basis document. This action will document compliance to the defined military certification basis. This document shall become part of the functional baseline for the system IAW CDRL A043. The Government shall have final approval authority over the compliance means identified in the MACC. The Contractor shall establish provisions for accessing and providing the Government all substantiating data and verification artifacts required to support the determination of airworthiness in accordance with the MIL-HDBK-516C.

3.2.3 Spectrum Supportability

The Contractor shall obtain authorization for radio frequencies required in support of this contract. Any experimental, developmental, or operational equipment for which the appropriate frequency allocation has not been made, the Contractor shall provide the technical operating characteristics of the proposed electromagnetic radiating device to the Contracting Officer during the initial planning, experimental, and developmental phase of contract performance. The Contractor shall use DD Form 1494, Application for Equipment Frequency Allocation, and the Equipment Location-Certification Information Database formats to obtain radio frequency authorization. The Contractor shall provide spectrum-supportable data and periodic updates in the stated formats throughout the contracted period IAW CDRL A045. The Contractor shall include this requirement in all subcontracts requiring the development, production, construction, testing, or operation of a device for which a radio frequency authorization is required.

3.2.4 Failure Mode Effects and Criticality Analysis

The Contractor shall create a Failure Mode, Effects, and Criticality Analysis (FMECA) IAW CDRL A014 to include all of the ADS-B (Out) hardware and software delivered under this contract, using ASME Standard Y14.38M as a guide. The Contractor shall maintain the currency of the FMECA as each new Class I Engineering Change Proposal (ECP) is submitted and as warranted by changes in specific anomaly probabilities.

3.2.5 Hazardous Materials Management

The Contractor shall comply with all federal, state, and local environmental laws, regulations and policies for all activities defined in this SOW, whether conducted at government or contractor facilities. Upon request, the Contractor shall make available to the government applicable environmental permits and documentation.

The Contractor shall include a letter of compliance to section 3.3.3 of the SRD, Prohibited Hazardous Materials, IAW CDRL A025. Class I Ozone Depleting Substances (ODS) shall not be required to operate, repair, or maintain the delivered ADS-B (Out) solution or ATD systems. Class II ODS used under this contract shall be documented in the letter of compliance.

3.2.6 Counterfeit Prevention Plan

The Contractor shall develop and implement a Counterfeit Prevention Plan (CPP) (CDRL A003, Counterfeit Prevention Plan, DI-MISC-81832) in compliance with SAE Standard AS5553 to prevent the inclusion of counterfeit parts or parts embedded with malicious logic into products intended for sale to the Government. As part of the CPP, the Contractor shall provide Certificates of Conformance (CoC) as well as acquisition traceability for Original Component Manufacturers (OCMs) and franchises/distributors in the supply chain.

The Contractor shall require their vendors, suppliers, and subcontractors to participate in the counterfeit prevention and supply chain risk mitigation activities.

3.2.7 Validation/Verification (VAL/VER) Kits

The Contractor shall develop kits consisting of the necessary ADS-B (Out) system components for installation into the T-6A aircraft and Aircrew Training Devices (ATDs). Two kits shall be assembled for the aircraft, one kit shall be developed for the Operational Flight Trainer (OFT)/Unit Training Device (UTD), one kit shall be developed for the Instrument Flight Trainer (IFT) for test, and one kit shall be developed for the Egress Procedures Trainer (EPT).

3.3 Program Management

The Contractor shall manage the efforts under this SOW to ensure cost, schedule, and technical content are met. The Contractor shall execute the program in accordance with the Contractor’s own established management techniques. The Contractor 's efforts shall encompass the overall planning, directing, integrating, and controlling of the modification, production, fabrication, and delivery of the ADS-B (Out) kits including program, financial, configuration, subcontractor, risk, and data management needed to accomplish the tasks in this SOW. The Contractor shall establish and implement a program management office function to manage all technical performance, including reliability, maintainability, logistics, and data delivery requirements of the contract. The Contractor shall prepare and submit Contractor Progress, Status, and Management Reports IAW CDRL A001. The Contractor shall prepare and submit an agenda, briefing slides, minutes and action items for each formal, technical, or programmatic meeting as specified in this SOW IAW CDRL A018.

3.3.1 Program Manager

The Contractor shall appoint a knowledgeable individual who will be the single point of contact for all work related to this contract. The Contractor shall identify the formal organizational responsibility for accomplishing the contractual effort, including an outline of the program authority that exists between all Contractor organizational elements.

3.3.2 Contractor Integrated Performance Management

The Contractor shall establish, maintain, and use an integrated performance management system. The correlation and integration of the Integrated Master Schedule (IMS) and Integrated Program Management Report (IPMR) provide for early indication of cost and schedule problems, and their relation to technical achievement IAW CDRL A022.

3.3.2.1 Integrated Master Schedule

The Contractor shall develop and maintain a resource loaded master IMS (including subcontractor’s IMS) by logically networking detailed program activities, to include subcontractor activities. The schedule shall contain the planned events and milestones, accomplishments, exit criterion, and activities, as well as highlight the critical path from contract award to completion of the contract. The Contractor shall quantify risk in hours, days, or weeks of delay and provide optimistic, pessimistic, and most likely duration for each IMS activity and event an IMS IAW CDRL A022.

3.3.2.2 Integrated Program Management Report

The Contractor shall prepare and submit IPMR updates IAW CDRL A022 in order to:

a) Integrate development cost and schedule performance data with objective technical measures of performance

b) Identify the magnitude and impact of realized and potential performance problem areas that may cause significant cost and schedule variances

c) Provide valid, timely, and accurate contract status information to the Government’s program manager

3.3.3 Subcontract Cost/Schedule Management and Reporting

The Contractor shall manage all subcontracts, to include the timely award of the subcontract, the integration of the subcontractor’s plans into IMS, and the monitoring of the subcontractor’s staffing plans, to include the execution of those staffing plans to the required levels with the required skills.

3.3.4 Weekly Program Status Meetings

The Contractor shall prepare and conduct a weekly program status meeting via telecom to include overall program status to include cost, schedule, and performance of all phases of the effort. The purpose of these meetings shall be to review overall program status, to discuss and mutually resolve technical issues, and to resolve issues associated with production, integration, test, and installation efforts.

3.3.5 Over Target Schedule/Restructure

The Contractor may conclude the baseline no longer represents a realistic plan in terms of schedule execution. In the event the Contractor determines an Over Target Schedule (OTS)/restructuring action is necessary, the Contractor shall obtain Government approval prior to implementing an OTS/restructuring action. The request shall also include detailed implementation procedures as well as an implementation timeframe. The Contractor shall not implement the OTS/restructuring prior to receiving written approval from the Contracting Officer.

3.3.6 Risk Management Program

The Contractor shall maintain an overall risk management program to identify potential sources of technical performance, cost, and schedule risks and to determine risk levels. The Contractor shall ensure that risk is factored into decisions on integration design and solution alternatives. The Contractor’s risk management plan shall define the process to identify the risks to cost, schedule, and technical performance as they relate to the IMS and overall objectives of the program. The Contractor’s risk management plan shall be provided IAW CDRL A020 and use the risk management related sections of AFI 63-101 (Acquisitions and Sustainment Life Cycle Management) and AFPAM 63-128 (Guide to Acquisition and Sustainment Life Cycle Management) as guides. An initial risk assessment shall be conducted between the Government and Contractor at Wright-Patterson Air Force Base prior to the creation of the initial risk management report. For each moderate and high-level risk, the Contractor shall coordinate with the Government to develop a mitigation strategy to minimize the impact on overall program cost, schedule, and performance. The Contractor shall provide Government access to the Contractor-maintained risk tool used to develop and track risks. The Government and the Contractor shall conduct a monthly integrated risk management board. The risk management report shall be provided IAW CDRL A039.

3.3.7 Program Management Review

The Contractor shall conduct the first Program Management Review (PMR) six months after the Post Award Conference (PAC) and every six months thereafter. During these reviews, the Contractor shall present integrated cost, schedule, and technical performance status of all phases of the effort. The PMR shall include cost information in discussions of schedule status, technical performance, and risk. The Contractor shall provide the agenda and meeting minutes per CDRL A018.

3.3.8 Post Award Conference

The Contractor shall conduct a PAC within 45 days of contract award. The purpose of the PAC is to establish the framework of the Contractor and Government interaction during the performance period of the contract. The PAC shall address the following subjects:

a) Introduction and contract overview

b) SOW review

c) System requirements overview

d) Software requirements overview

e) Initial risk plan

f) Review of test and evaluation requirements

g) Review of data requirements/CDRL requirements

h) Review of configuration management procedures

i) Review of Integrated Logistic Support (ILS) requirements

j) Review of IMS (milestones and deliverables)

k) Review of delivery schedules

l) Review of configuration management processes and procedures as documented in the Configuration Management Plan

m) Review of quality control processes and procedures

n) Systems engineering overview

As part of the review of configuration management processes and procedures, the Contractor shall present their approach to tracking the status of all FAA-issued Airworthiness Directives, Service Bulletins, and Advisory Data in accordance with CDRL A007.

3.3.9 Associate Contractor Agreements

The Contractor shall use its best efforts to establish Associate Contractor Agreements to ensure a close working relationship with other Contractors who support the T-6A aircraft and ATDs. The Contractor shall establish agreements with:

a) Beechcraft Defense Company, LLC (Aircraft Original Equipment Manufacturer)

b) FlightSafety Services Corporation (ATD Original Equipment Manufacturer)

c) DynCorp International (Contractor Logistics Support Contractor)

3.4 Technical Meetings and Reviews

The Contractor shall conduct, with Government participation, formal technical meetings and reviews as listed below.

3.4.1 Technical Interchange Meetings

The Contractor shall conduct three Technical Interchange Meetings (TIMs) with the Government and other designated companies to: review the Analysis of Alternatives (AoA), demonstrate and discuss design implementations, identify and resolve any issues that result from those discussions and to review technical progress on this effort. These meetings shall be conducted at the Contractor’s facility.

3.4.2 Air Vehicle System Requirements Review/System Functional Review

The Contractor shall conduct a combined System Requirements Review (SRR)/System Functional Review (SFR) at the Contractor’s facility IAW Department of Defense Instruction (DoDI) 5000.02, to include a Government Chairman and a Government-appointed technical review team. The SRR/SFR shall be scheduled for two days. Copies of all presentation material (charts, graphs, etc.) shall be available at the review and shall become part of the minutes. The purpose of the SRR is to ensure that the understanding of the top-level system requirements is adequate to support further requirements analysis and design activities. The purpose of the SFR is to establish a functional baseline that fully satisfies performance requirements and ensures the system’s functions are decomposed and defined to lower levels in order to start preliminary design. At the SRR/SFR, the Contractor will present a requirements tree, analysis and synthesis approach, block diagrams, flow diagrams, proposed interfaces documentation and other such documentation as necessary to allow full assessment of the system requirements.

The Contractor shall analyze the system requirements and derive requirements as necessary to ensure a proper design for the T-6A ADS-B (Out) modification in accordance with the T-6A ADS-B (Out) SEMP, CDRL A017. The Contractor shall also analyze design risks and the steps needed to mitigate those risks. The Contractor shall document its risk analysis and mitigation efforts in the applicable section of Risk Management Report in accordance with CDRL A039 and in this review. The SRR/SFR must answer the following questions:

a) Can the system requirements satisfy the Government’s System Requirement Document and the Statement of Work?

b) Are the system requirements sufficiently detailed and understood to enable the start of the preliminary system design?

c) Are adequate processes and metrics in place for the program to succeed?

d) Are the risks known and manageable for development?

The SRR/SFR shall be held within 90 days after the PAC, or as mutually agreed upon by the Government and Contractor. The Contractor shall coordinate with the Government and hold two preparation telecom meetings in advance of the review, to include a final briefing dry-run.

Entry criteria for the SRR/SFR shall consist of:

a) Conference Agenda

b) Draft SRVM

c) Updated draft ADS-B (Out) System Performance Specification

d) Contractor’s IMS

e) Risk Management Report

f) Draft PIPFS compliance matrix

Exit criteria for the SRR/SFR shall consist of:

a) Government concurrence of the draft SRVM

b) Government acceptance of SRR/SFR Minutes

c) Government concurrence of risk management report

d) Government concurrence of resolution and closure of SRR/SFR critical action items assigned to the Contractor

e) Government concurrence that requirements are adequately defined and understood in order to advance into the preliminary design phase

f) Government concurrence that functional baseline has been established and is under formal configuration control

g) Government concurrence of final ADS-B (Out) System Performance Specification

h) A preliminary allocation of system requirements to hardware and software subsystems

i) An approved T-6A ADS-B (Out) SEMP that addresses critical risk drivers

j) Government concurrence of the draft PIPFS compliance matrix

3.4.3 Air Vehicle Preliminary Design Review

The Contractor shall conduct a Preliminary Design Review (PDR) at the Contractor’s facility IAW DoDI 5000.02, to include a Government Chairman and a Government-appointed technical review team. The PDR shall be scheduled for 2 days. Copies of all presentation material (charts, graphs, etc.) shall be available at the review and shall become part of the minutes.

The purpose of the PDR is to establish the allocated baseline and ensure it fully satisfies the requirements such that detailed design can begin. The Contractor shall present and describe the preliminary system design, changes to the functional baseline, and program status for the ADS-B (Out) capability. Prior to the Contractor proceeding with detailed design, the Contractor must answer all questions, comments, and critiques presented by the Government at the PDR. Indication of successful completion of the PDR shall be given by the Government in writing, indicating to the Contractor that it may proceed with the detailed design.

The Contractor shall separate the PDR into sections for hardware, software, and interfaces. The Contractor shall present detailed block diagrams, proposed fabrication sketches, interface documentation, weight and balance documentation, and any other such documentation as is necessary to allow full assessment of the proposed design validity for release to detailed design.

The Contractor shall develop the preliminary design for the T-6A ADS-B (Out) modifications in accordance with the T-6A ADS-B (Out) SEMP, CDRL A017.

The Contractor shall also update the analysis of design risks presented at the SRR/SFR and describe any modifications made to the plans and steps taken to mitigate those risks.

The Contractor shall update the applicable section of the Risk Management Report IAW CDRL A039, as appropriate.

The preliminary Mechanical and Electrical Design and the integration of components into the aircraft, including details of system mounting, wire runs, and interfaces with existing aircraft systems, shall be presented at PDR. The design shall ensure optimized sustainment and reliability in addition to minimal maintenance burden. Interfaces between software modules and different physical systems installed or affected by the T-6A ADS-B (Out) modifications will be documented in the draft Interface Control Document (ICD), CDRL A008.

The Contractor shall present the IMS, CDRL A022, at the PDR. Changes to the IMS since the previous review shall be identified, and the IMS shall be statused to reflect current progress on each task. The review of the IMS shall cover all specified program milestones, conferences, reviews, critical data submittals, contract critical path, and deliveries to present a clear picture of the progress made on the program.

The Contractor shall present the approach to Materiel Improvement Project Reporting. These reports shall be prepared and submitted IAW CDRL A044.

The system safety program shall use MIL-STD-882E (Systems Safety), AFI 63-1201 (Life Cycle Systems Engineering), and the JPATS System Safety/Environmental Management Plan (SSEMP) for Joint Primary Aircraft Training System as guidance in implementation of the system safety policies, process, and procedures.

The Data Accession List (DAL), CDRL A041, shall be presented at the PDR and at all subsequent reviews to document Contractor internal data generated during the development process.

The Contractor shall develop the program acceptance test plan, with descriptions of tests to be performed in the Systems Integration Lab (SIL), on the ground, in the aircraft, and in flight, IAW CDRL A052. The test plan shall adhere to the Government test strategy and processes as outlined in the Test and Evaluation Master Plan.

The test plan will be presented at PDR.

The Contractor shall provide a formal status update for ADS-B (Out) MACC criteria in support of USAF Airworthiness process. For suggested changes to the USG-provided MACC, the Contractor may present rationale for sub-elements that are deemed "Non-Applicable" or “Applicable” with supporting data.

The PDR is expected to occur approximately 90 days after SRR/SFR, or at another mutually agreed time, but not before the Contractor-allocated baseline meets PDR entry criteria and the SRR/SFR has been closed. The Contractor shall coordinate with the Government to hold two preparation meetings via telecom in advance of the review. Draft copies of all review presentation material (charts, graphs, etc.) will be presented to the Government two working days prior to each preparation meeting.

The PDR shall address:

a) Program overview, processes, risk areas, recommended mitigation plans, and evaluation of alternatives

b) Hardware and software design

c) Airframe modification and design

d) Maintenance support equipment requirements

e) Flight test equipment requirements

f) Logistics considerations (maintenance concepts, technical publications, spares, assets, training, and academics)

g) Verification and test approach

h) MACC Criteria Update

i) Civil certification plan review and status

Entry criteria for the PDR shall consist of:

a) Successful completion and closure of the SRR/SFR

b) Submittal of all CDRL items scheduled to be delivered prior to PDR including IMS, DAL, Acceptance Test Procedures (ATP), draft ICD

c) Submittal and acceptance of the SRVM

d) Submittal of draft ADS-B (Out) Subsystem Performance Specifications

e) Presentation of risk management report

f) Safety assessment report

g) Submittal and acceptance of Conference Agenda

h) Updated draft PIPFS compliance matrix

Exit criteria for the PDR shall consist of:

a) Government concurrence of the CDRL items required as PDR entry criteria

b) Government concurrence of the SRVM

c) Government concurrence of risk assessments and risk mitigation plans

d) Government concurrence of resolution and closure of critical PDR action items assigned to the Contractor

e) Government concurrence of draft ADS-B (Out) Subsystem Performance Specifications

f) Submittal and Government acceptance of PDR minutes

g) Government concurrence that allocated baseline has been established and is under formal configuration control

h) Government concurrence that the preliminary design as disclosed provides a satisfactory basis for proceeding into detailed design and test procedure development

i) Government concurrence of the updated draft PIPFS compliance matrix

3.4.4 Air Vehicle Critical Design Review

The Contractor shall conduct a Critical Design Review (CDR) at the Contractor’s facility IAW DoDI 5000.02 and shall include a Government Chairman and a Government-appointed technical review team. The CDR shall be scheduled for 2 days. Copies of all presentation material (charts, graphs, etc.) shall be made available at the review and shall become part of the minutes.

The purpose of the CDR is to ensure the product design is stable and to establish the initial product baseline. At the CDR, the Contractor shall formally present a comprehensive detailed review of the finalized design, test plan, and logistics support plan for the ADS-B (Out) capability. The Government shall provide indication of successful completion of the CDR in writing. The accepted CDR design shall establish the Contractor’s authority to implement and produce the proposed design and establish the basis for performance verification. Changes to the allocated baseline for ADS-B (Out) shall be captured in detailed documentation. Prior to Contractor proceeding with fabrication, installation, software coding, and other activities related to realizing the T-6A ADS-B (Out) modification design, the Contractor must answer all questions, comments, and critiques presented by the Government at the CDR.

The Contractor shall separate the CDR into sections for hardware, software, and interfaces. The Contractor shall highlight changes from the design presented at PDR and present block diagrams, fabrication drawings, schematics, weight and balance documentation, interface documentation, and any other such documentation as is necessary to allow full assessment of the design validity for release to production.

The Contractor shall develop the detailed design of the T-6A ADS-B (Out) modification IAW the T-6A ADS-B (Out) SEMP, CDRL A017. The Contractor shall also update the analysis of design risks presented at the PDR and describe any modifications made to the plans and steps taken to mitigate those risks.

The Contractor shall update the applicable section of Risk Management Report IAW CDRL A039.

The detailed Mechanical and Electrical Design and the integration of components into the aircraft, including details of system mounting, wire runs, and interfaces with existing aircraft systems, shall be presented at CDR. The CDR presentation shall highlight changes and updates to the design. Any such updates or changes shall be documented in updates to the Technical Manuals CDRL A016. Interfaces between software modules and different physical systems installed or affected by the T-6A ADS-B (Out) modifications will be documented in the final Interface Control Document (ICD), CDRL A008.

The Contractor shall present the IMS IAW CDRL A022 at the CDR. Changes to the IMS since the previous review shall be identified and the IMS shall be updated to reflect current progress on each task. The review of the IMS shall cover all specified program milestones, conferences, reviews, critical data submittals, contract critical path, and deliveries to present a clear picture of the progress made on the program.

The Contractor shall provide a formal status update for ADS-B (Out) MACC criteria in support of USAF Airworthiness process. For suggested changes to the USG-provided MACC, the Contractor may present rationale for sub-elements that are deemed "Non-Applicable" or “Applicable” with supporting data.

The CDR is expected to occur approximately 90 days after PDR, or at another mutually agreed time, but not before the Contractor-detailed designs meet CDR entry criteria and the PDR has been closed. The Contractor shall coordinate with the Government to hold two preparation meetings via telecom in advance of the review. Draft copies of all review presentation material (charts, graphs, etc.) will be presented to the Government two working days prior to each preparation meeting.

The CDR shall address:

a) Program risk areas, recommended mitigation plans

b) Hardware and software design

c) Airframe modification and design

d) Maintenance support equipment requirements

e) Flight test equipment requirements

f) Logistics considerations

g) Verification and test approach

h) Draft drawings

i) Recommended design changes as a result of developmental testing including trade-off impacts

j) MACC Criteria Update

Entry criteria for the CDR shall consist of:

a) Successful completion and closure of the PDR

b) Submittal of all CDRL items scheduled to be delivered prior to CDR including IMS, T-6A ADS-B (Out) SEMP, Risk Management Report, Safety Assessment Report (SAR), technical manual updates, and final ICD

c) Submittal of final ADS-B (Out) Subsystem Performance Specifications

d) Draft drawings 98% complete

e) Presentation of an updated risk management report

f) Submittal and acceptance of the CDR agenda

g) Submittal and acceptance of the updated SRVM

h) Complete detailed design description of the T-6A ADS-B (Out) modification

i) Final PIPFS compliance matrix

Exit criteria for the CDR shall consist of:

a) Government concurrence on CDRL items required for the CDR entry criteria

b) Government concurrence on updated risk management report

c) Submittal and Government acceptance of the updated SRVM

d) Government concurrence on resolution and closure of all critical CDR action items assigned to the Contractor

e) Submittal and Government acceptance of the CDR minutes

f) Government concurrence that product baseline has been established and is under formal configuration control

g) Government concurrence on final ADS-B (Out) Subsystem Performance Specifications

h) Government concurrence that the detailed design as disclosed is stable and shall satisfy the requirements of the ADS-B (Out) performance specifications

i) Government acceptance of Human Engineering Design Approach Document- Operator (HEDAD-O)

j) Government acceptance of Human Engineering Design Approach Document- Maintainer (HEDAD-M)

k) Government acceptance of the final PIPFS compliance matrix

3.4.5 Configuration Audits

Prior to final acceptance of the T-6A ADS-B (Out) modification aircraft, a Functional Configuration Audit (FCA) and a Physical Configuration Audit (PCA) shall be conducted on both the air vehicle and ATDs. Successful completion of the FCA and PCA shall result in the issuance of an initial DD250 by the Government. The FCA/PCA shall be conducted using MIL-HDBK-61A [1] (Section 8) (Appendix E) and EIA-632 as guides.

3.4.5.1 Functional Configuration Audit

The Contractor shall successfully pass a Government-conducted FCA to show the design meets all the requirements identified in the ADS-B (Out) performance specifications IAW CDRL A015 and this Statement of Work. The Contractor shall provide an FCA plan IAW CDRL A033. The Contractor shall develop and deliver a Government approved T-6A Prime Item Product Functional Specification (PIPFS) compliance matrix IAW CDRL A015. Once approved, the PIPFS compliance matrix shall be used in the execution of the FCA to ensure the ADS-B (Out) technical solution complies with the PIPFS or deviations from the PIPFS are Government approved. The Contractor shall maintain and update the PIPFS compliance matrix through the completion of the FCA. The Contractor shall make available analysis data, test results, drawings, demonstration results and documentation to validate that the intended function or performance criteria are met and that the documents are complete and satisfactory. The Contractor shall prepare and submit Verification Test Data and Results to support the FCA at least 20 working days in advance of the FCA.

3.4.5.2 Physical Configuration Audit

The Contractor shall successfully pass a Government-conducted PCA at the base location of the first production installation. The PCA shall be a formal examination of the "as-built" physical configuration of the T-6A ADS-B (Out) installation to ensure the modification conforms to the design and technical documentation that defines it. The PCA shall verify that the related design documentation matches the design of the delivered aircraft and ATD. The PCA formalizes the product baseline so that future changes can be made only through the formal configuration change control procedures IAW ADS-B (Out) performance specifications in CDRL A015. The Contractor will provide a PCA plan IAW CDRL A033.

3.4.6 Manufacturing Readiness Levels

The Contractor shall conduct Manufacturing Readiness Assessments (MRA) to determine the Manufacturing Readiness Level (MRL) of any newly developed or COTS avionics units/systems. The Contractor shall use the definitions, criteria, and processes defined in the MRL Deskbook as a guide. The assessment will be led by the Government program office at the prime Contractor’s facilities. The prime Contractor shall lead the assessments of suppliers and include Government participants. The selection of suppliers to be reviewed will be made using the MRL Deskbook, section 4.3, as a guide. The Contractor shall develop and implement manufacturing maturation plans or their equivalent for areas in which the MRL is lower than MRL of 8. The Contractor shall monitor and provide status at the First Flight Readiness Review (FFRR). The Contractor shall provide documentation showing that all newly developed or COTS avionics units/systems have reached MRL 8 prior to Government developmental testing and MRL 10 prior to Government operational testing. The successful completion of the MRA will be approved by the Government in writing. The Contractor shall re-assess MRLs in areas for which design, process, source of supply, or facility location changes have occurred that could impact the MRL.

3.5 Quality Assurance

The Contractor shall provide and maintain a Quality Assurance program that satisfies program objectives and meets the requirements of AS9100, ANSI/ISO/ASQ 9001, or an equivalent quality management system (QMS). If the Contractor is not AS9100 compliant they shall submit a gap analysis detailing the gaps between their QMS and AS9100C as well as plans to close the gaps. The quality system procedures, planning, and all other documentation and data that comprise the quality system shall be made available to the Government for review upon request. The Government may perform any necessary inspections, verifications, and evaluations to ascertain conformance to requirements and adequacy of the implementation procedures.

3.6 Human Engineering Program

The Contractor shall develop, implement, and maintain a human engineering program, documented in a Human Engineering Program Plan, for the ADS-B (Out) capability IAW CDRL A046.

3.6.1 Air Vehicle and ATD Human Engineering Design Approach Document – Operator (HEDAD-O)

The Contractor shall develop, implement, and maintain a HEDAD-O, describing the new or modified equipment impacted by the ADS-B (Out) design and its interfaces with operators, IAW MIL-STD-1472G and CDRL A005.

3.6.2 Air Vehicle Human Engineering Design Approach Document – Maintainer (HEDAD-M)

The Contractor shall develop, implement, and maintain a HEDAD-M, describing the new or modified equipment impacted by the ADS-B (Out) design and its interfaces with maintainers, IAW MIL-STD-1472G and CDRL A006.

3.6.3 Cockpit Working Group (CWG)

The Contractor shall co-chair and participate technically and administratively in the CWG, IAW AFI 63-112, to include providing technical briefings, working…