3DASSOW23Jan19.docx

Statement of Work (SOW) For A-10 3-Dimensional Audio January 23, 2019 Prepared by:

A-10 Division Air Force Life Cycle Management Center (AFLCMC)/WWA A-10 Systems Program Office (SPO)

Hill AFB UT 84056

Acronym List

1.0 Introduction

1.1 Purpose

The purpose of this effort is to provide the existing A-10 aircraft with a 3DA System that will provide much needed spatial separation of multiple audio sources the war fighter is using for mission effectiveness and situational awareness capability. The 3 Dimensional Audio (3DA ) System will also provide true three dimensional cueing by interfacing with the Scorpion HMCS (Helmet Mounting Cueing System) system (previously installed in the aircraft), ALQ-213 threat warning system. The 3DA System shall also provide electronic and ambient noise reduction/cancellation characterized to the A-10.

The total 3DA System will be comprised of Non-Developmental Items (NDI) with minimal non-recurring-engineering (NRE) efforts, while still maintaining required performance. Aircraft installed 3DA components include necessary Line Replaceable Units (LRU) and all associated wiring, fixtures, connectors, and other components necessary to integrate 3DA into the A-10 aircraft. The 3DA functions of the system are defined in the System Requirements Document (SRD) and defined attachments.

The program description is to acquire a non-developmental 3DA System and accomplish the following: A-10 aircraft qualification test, 3DA Operational Flight Program/Operational Test Platform (OFP/OTP) integration with the A-10 software, delivery of engineering systems, aircraft integration, low rate initial production (LRIP), full rate production (FRP), Interim Contractor repair and support, and follow-on OFP sustainment.

1.2 Background

3DA capability increases the pilot's spatial, battlespace, and situational awareness while significantly enhancing critical safety items for impacted aircraft. The A-10 aircraft has a suite of visual information comprised of an Electronic Warfare displays, Situational Awareness Datalink (SADL) radio, communication radios, and a Helmet Mounted Integrated Targeting system. However, this suite is not fully integrated with aural components and lacks noise reduction/cancellation which is central to critical safety items, that are especially important on today's longer duration sorties. The 3DA System will provide noise reduction/cancellation, integrate the A-10 suite with aural capability and organize this aural capability in three dimensional space (3D) for enhanced pilot awareness.

1.3 Scope

This work effort will consist of all activities required for the Contractor to furnish, integrate, test, and install a 3DA System for the A-10 aircraft. This will include, but is not limited to: qualification test, delivery of test assets, full and complete aircraft integration, installation drawing updates, Technical Order (TO) updates, and any other applicable documents that the Government deems required, installation into the weapon system, and Interim Contractor Support and Repair (ICS).

1.3.1 Groups/Kits

The 3 Dimensional Audio System (3DA System) shall consist of Group A, Group B, Group C kits, and support equipment

· The Group A kits are defined as permanent aircraft wiring, brackets, clamps, and mounts for the 3DA System.

· Group B is defined as the computer/controller, or any other Line Replaceable Unit (LRU) or items that stay with the aircraft but are easily removed and replaced. Group B kits can be broken into two items:

· Enhanced Interphone Amplifier (EIA) – Computer LRU

· Audio Control Panel (ACP) – Pilot controller

· Group C is defined as the 3DA System assembly that leaves the aircraft with the pilot and is stored in life support. Group C kits can be defined as the headset assembly.

· Support equipment – ready room tester, headset testers, and any support equipment deemed required by the Government. Required support equipment could be identified through the Support Equipment Recommendation Data process.

1.3.2 Integration

The Contractor shall be responsible for recommending the routing path, clamp sizes, brackets, associated mounts (to Include, but not limited to, any cockpit mapping, harmonization, or alignment equipment of the 3DA System). The Contractor shall be responsible for aircraft integration tasks and products as identified in the System Requirement Document (SRD) and other supporting documents.

1.3.3 Milestone Entry/Exit

There will be entry and exit criteria established in the A-10 Systems Engineering Plan (SEP) for each engineering milestone (EG: PDR, CDR, FCA, PCA). The Government Program Manager, or designated representative, shall acknowledge and graduate the contractor once all the exit criteria for each milestone has been met. Every technical/engineering meeting will require an agenda 15 days prior to meeting, and post-meeting minutes within 10 days after the meeting has been completed. The Government has the right to require/wave the agenda and minutes requirement upon contractor request.

A003 - System Engineering Management Plan - DI-SESS-81785A A004 – Conference Agenda - DI-ADMN-81249B A005 – Conference Minutes - DI-ADMN-81250B

2.0 Applicable Documents

2.1 Compliance Documents

The 3DA System shall be in accordance with and meet the specifications listed in the SRD section 2.2, and any other applicable documents listed in either this SOW or the SRD.

2.2 Government Furnished Information

Government furnished information will be made available as required. Examples would be Interface Control Document, drawings, and TOs. If other Government furnished information is needed, the Contractor shall request that information through the Program Manager for approval. Approval of Request for Information will be on a “Need to know” basis.

3.0 Contractor Tasking/Requirements

3.1 Program Planning

The Contractor shall provide all program management and engineering services to support the USAF A-10 Integrated Product Team (IPT). The Government will require an Integrated Master Plan, Program Management Plan, and Risk Management Plan that will include technical performance measure.

3.1.1 Integrated Mater Plan (IMP) – Program Management Plan

This plan shall contain all of the planning documents and schedule as attachments of appendices, a process for tracking action items, resolving issues, a focal point for program management engineering. Documentation and reports deliverables shall be delivered in accordance with this SOW, unless otherwise specified by the Government Program Manager.

CDRL - A001 – Program Management Plan – DI-MGMT-81797

3.1.2 Integrated Master Schedule (IMS)

The Contractor shall provide an Integrated Master Plan (IMP) in Microsoft Project format, as part of the Request for Proposal (RFP) submission; the Contractor shall be held to an event driven schedule. The IMP shall include, but is not limited to, proposed dates and number of occurrences for the following: Aircraft Integration (both software and hardware), Engineering Milestones, Production Milestones, Qualification Processes, Ground and Flight Tests, Trial Vehicle Installation, kit proof support on model aircraft, System Requirements Review (SRR), Preliminary Design Review (PDR), Critical Design Review (CDR), Physical Configuration Audit (PCA), Functional Configuration Audit (FCA), Production Readiness Review (PRR), Initial Operational Capability (IOC), Full Operational Capability (FOC), Interface Control Working Group (ICWG), Technical Interchange Meetings (TIMs), Logistics, Source Data Deliveries, and Program Management Reviews (PMRs) as specified in the SOW. All reviews/meetings/audits shall be deemed “AS REQUIRED” by the Government .

The Government shall have the authority to remove/adjust/add any meetings/audits/reviews as the Government sees fit; only the USAF A-10 IPT can approve changes to the IMS for line items that do not change the overall deliveries to major event driven milestones. A Contractor-requested change to major milestones will be approved through the Procuring Contracting Officer (PCO). The SRR, PDR, CDR, and TRR are aircraft integration milestone reviews of the 3DA System and will be chaired by the System Program Office’s lead engineers or their designated representatives. If the Contractor recommends any other review/audit/meeting, please include in the IMS submission.

CDRL Sequence A001- Program Management Plan- DI-MGMT-81797

3.1.3 Monthly Status Reports

The contractor shall provide a monthly status report. This report shall contain: Updated milestone chart, Equipment/facilities chart (GFE), updated cost chart (in Government fiscal year, October-September), updated Purchase Charts, and updated Organizational Charts.

CDRL Sequence No. A002 Status Report- DI-MGMT-80368A

3.1.4 Systems Engineering Management Plan (SEMP)

The Contractor shall provide a Systems Engineering Management Plan (SEMP) in Government approved Contractor format at the SRR. At a minimum, the SEMP shall identify engineering milestones with associated entry and exit criteria and an outlined plan on how the contractor will comply with entry and exit criteria Safety plan in accordance with section 5.3.1 of this SOW. The entry and exit criteria will be provided by the A-10 System Engineering Plan (SEP) (starting at section 4.4.1) and will delegate the proper authority for approving all exit criteria in order to graduate to the next milestone entry.

CDRL Sequence No. A003 - System Engineering Management Plan - DI-SESS-81785A

3.1.5 Risk Management Status Report

The Contractor shall provide a Contractor’s Risk Management Status Report in Contractor format. Risk Assessments will be held regularly, but not limited to, at PMRs. Items requiring close monitoring will be reviewed as required by the Government. The contractor shall provide the Government a copy of the Contractor’s risk management plan shall be submitted 10 calendar days prior to SRR for the Government to review. The Contractor’s Risk Management Plan will be used to monitor management, cost and schedule of the contract efforts relative to a system and equipment. This information will provide the government with risk data for all risks associated with the system/equipment.

The Contractor shall support risk assessments via teleconference or during a face-to-face program review with the A-10 Integrated Product Team at the discretion of the Government. The Contractor shall provide and implement risk mitigation plans for all Contractor respective risks identified as yellow or red documented in the minutes of the risk assessment teleconferences or face-to-face meetings. The Risk Report will comply with MIL-STD-882E or most current revision.

CDRL Sequence No. A006 - Risk Management Status Report - DI-MGMT-81809

3.1.6 Test and Evaluation Program Plan

The Contractor shall provide a Test and Evaluation Program Plan TEPP. In addition, the TEPP shall identify and include all of the required test plans identified in section 3 of this SOW, all testing required for qualification of operational use on the A-10 aircraft, internal Contractor testing/requirements for all kits, equipment, integration of the 3DA system into the A-10. A draft TEPP shall be provided at PDR for evaluation by the Government. The Government shall require that contractor engineers will be present during the modification phase, and flight and ground testing phase of this program. Pre-production assets will be provided for safety of flight, qualification, TAAF, and miscellaneous testing.

CDRL Sequence No. A007 - Test and Evaluation Program Plan (TEPP) - DI-NDTI-81284

3.1.7 Configuration Management Plan (CMP)

The Contractor shall provide a Configuration Management Plan (CMP). The Contractor shall provide the processes and procedures used to track configuration of the A-10 3DA System. Contractor configuration management processes and procedures are acceptable along with tailoring as required to meet program requirements. The Government shall be provided with configuration data prior to all testing. Class II hardware changes shall require notification to the Government by the Contractor, but will not require formal approval. Class I hardware changes shall require formal approval through the Government configuration change control board process.

CDRL Sequence No. A008 Suppliers Configuration Management Plan - DI-SESS-80858C

3.1.8 Life Cycle Management Plan (LCMP)

The Contractor shall provide a Life Cycle Management Plan (LCMP). A draft LCMP shall be provided 30 days prior to CDR for evaluation by the Government. The Government will provide a sample LCMP in order for the Contractor to conform to the required Government format.

CDRL Sequence No. A009 - Life Cycle Management Plan (LCMP) - DI-MGMT-82215

3.1.9 Software Development Plan (SDP)

The Contractor shall provide a Software Development Plan (SDP). The SDP shall address implementation of the 3DA System software capabilities, the two cockpit review team meetings, and Interface Control Document.

CDRL Sequence No. A010 - Software Development Plan - DI-IPSC-82208

3.1.10 System Safety Hazard Analysis (SHA)

The Contractor shall provide a Safety Hazard Analysis (SSHA) in accordance with MIL-STD-882 or most current revision.

CDRL Sequence No. A011 - System Safety Hazard Analysis Report (SSHA) - DI-SAFT-80101C

3.1.11 Requirements Traceability Matrix

The Contractor shall provide, maintain, and update a system requirements traceability matrix.

CDRL Sequence No. A012 - Requirements Traceability Verification Matrix - DI-MGMT-82133

3.1.12 Airworthiness Support

The Contractor shall support the Government Program Office in preparation, validation, and substantiation of a Modified Airworthiness Certification Criteria (MACC) checklist per MIL-HDBK 516C. Substantiating documentation is anticipated to be comprised of multiple CDRL’s listed herein in other paragraphs of this document and the accompanying SRD. The Government Program Office will be responsible for preparing the MACC, and will rely on the Contractor’s expertise and technical, test, and verification documentation, as well as test plans and reports from the responsible test organization (AATC) to complete the MACC. Contractor shall participate in teleconferences and technical reviews as required to complete the air worthiness process; however, it is anticipated that most of these technical discussions will take place as part of other regularly scheduled teleconferences of program reviews. Therefore, no additional airworthiness-specific reviews or documentation should be anticipated.

3.2 3DA System Capability Requirements

3.2.1 Operational Capability

The Contractor shall provide a 3DA System that meets the operational capabilities identified in the SRD.

3.2.2 Technical Requirements

The Contractor shall provide a 3DA System that meets the technical requirements identified in the SRD.

3.2.3 Software Capability

The Contractor shall provide the baseline software capabilities for the 3DA System as defined in the Systems Requirement Document (SRD) and any other associated attachments.

3.2.4 Aircraft Data

The Contractor shall provide a 3DA System that receives aircraft data based on the Government Furnished Information and Property sections of the SOW.

3.3 Aircraft System Integration

3.3.1 Drawings

The Contractor shall provide a block diagram of the 3DA System, drawings of the 3DA System Group A, Group B, and Group C (to include the helmet module) exhibiting the space required for the aircraft design, and drawings of all components, to include but not limited to, the helmet-mounted equipment, computer, control panel, mounts, and wiring in order for the Government to repair 3DA system components at the field and depot level.

The Contractor shall supply a Top Level Drawing List that contains: new drawings, revised drawings, top level drawing, installation drawings, drawing tree and delivery schedule to be provided at PDR (draft) and CDR (final draft). This information will be used to determine what revised drawings will require only a drawing and EO to be delivered to the government and what revised drawings the contractor will update the drawing/model and supply the accompany EO. This process only applies to revised drawings/models. The other new drawings/models, drawing tree and accompany data will be delivered per the delivery schedule.

Drawings shall be delivered in Contractor format IAW ASMEs identified on the CDRL for this contract. The Contractor shall provide part numbers for Contractor provided parts that are part of the 3DAS as part of the drawing package.

The Contractor shall provide a list of parts that the Contractor may recommend as throw-away items that cost less than $5K per item. This list is subject to Government approval. The Contractor shall provide Level II (depot level maintenance) drawings for all 3DAS and Support Equipment components, including the Enhanced Interphone Amplifier (EIA) and Audio Control Panel (ACP). The drawings may be stamped proprietary but will have a distribution statement for “Government Purpose Rights” and will be used only for establishing an organic repair capability that will include Advisory and Assistance Service Contractors working on behalf of the Government. If the Contractor is unwilling to provide Government purpose rights under the FAR, the Contractor may assert limited rights statements to any components that are developed exclusively at Contractor expense; however, the Government must be provided detailed drawings to allow for provisioning and repair of these items, even if such drawings are labeled proprietary. This extends to top level assemblies and all related subassemblies of the 3DA System. Drawings shall be delivered in Contractor format IAW ASMEs identified on the CDRL for this contract. The Contractor shall provide part numbers for Contractor provided parts that are part of the 3DAS as part of the drawing package.

CDRL Sequence No. A014 - Product Drawing/Models and Associated Lists - DI-SESS-81000E

3.3.2 Technical Data Package

The Contractor shall provide a Technical Data Package (TDP) of the 3DA System and any required support equipment. The TDP will consist of Quality Assurance Provisions (QAP), applicable technical data such as models, drawings, associated lists, specifications, standards, performance requirements, software, and memory device documentation, packaging details for the 3DA System. The Contractor shall provide data as part of the technical data package that provides the Government the ability to stand-up a repair capability on parts identified as repairable items and the ability to provide the Government the ability to integrate the 3DAS, and any required support equipment.

The Contractor QAP shall address standard company manufacturing quality control practices and documented processes for the 3DAS Contractor. In addition, the QAP shall include all relevant company certifications like Computer Maturity Model Integration (CMMI) and International Standards Organization (ISO) by the 3DAS Contractor.

The Contractor shall abide by TMCR 86-01Q and the A-10 Technical Order Process Plan (TOPP) for Source Data Deliveries for entry and exit criteria for all Technical data/order process requirements. The following sections of the TOPP provide an outline for the required processes:

TOPP Section 3.3.7 – In-Process Review 1 (IPR 1) – 30-40% review.

TOPP Section 3.3.10 – In-Process Review 2 (IPR 2) – 70-80% review.

TOPP Section 3.3.12 – Validation/Certification TOPP Section 3.3.19 – Pre-Publication TOPP Section 3.3.20 – Final Delivery The TMCR 86-01Q supersedes any other documentation regarding Technical and Source Data. Reference CDRL No. A016 for the TMCR requirements.

CDRL Sequence No. A015 - Technical Data Package - DI-SESS-80776A CDRL Sequence No. A016 - TMCR 8601 - TM-86-01Q CDRL Sequence No. A017 Quality Assurance Provisions - DI-SESS-80789A

3.3.3 Interface Control Document (ICD)

The Contractor shall provide an Interface Control Document (ICD) for 3DA System and support equipment (hardware and software). The Contractor shall collaborate with the Government to create the above system-specific Interface Control Document for 3DA System hardware and software based on DI-SESS-81248B. The Government will provide updates for the ICD as required, as well as any other necessary information regarding aircraft electrical power or other relevant aircraft characteristics.

CDRL Sequence No. A018 - Interface Control Document - DI-SESS-81248

3.3.3.1 Physical Location of LRU

The 3DA System shall be installed in the A1C18 and SWPP cockpit locations. The Peak performance volume shall be controlled through the ACP. Minimal effect, movement, and relocating of current cockpit systems shall take place. A draft diagram shall be provided 30 days prior to PDR for Government approval.

CDRL Sequence No. A014 – Product Drawing Models and Associated Lists

3.3.4 System Performance Specifications

The Contractor shall provide a System Performance Specification. The Contractor shall use the SRD and any applicable sections in this SOW, as the baseline and template for the 3DA System Performance Specification.

CDRL Sequence No. A019 - System/Subsystem Performance Specification - DI-SDMP-81465A

3.3.5 Critical Component Analysis

The Contractor shall provide a Critical Component Analysis for the appropriate 3DA System.

CDRL Sequence No. A020 Technical Report–Study/Services - Critical Components Analysis - DI-MISC-80508B

3.3.6 Cyber Security

Security and Cyber security items dealing with threat warning, identification, location, or related items determined by the Government shall only be handled by U.S. citizens.

3.3.6.1 Critical Program Information

Critical Program Information (CPI) Identification/Protection: The contractor shall identify any CPI and Resident CPI that is added under this effort which needs to be protected. The CPI identified shall be approved by the USG Program Manager. The CPI identification shall include a review of the system, unique integration, support equipment and the Non-Resident design/process/material aspects of the program. All identified CPI shall be protected with appropriate countermeasures. In the case of Resident CPI, the use of Anti-Tamper shall be considered and documented in an Anti-Tamper Recommendation Report in accordance with DODI 5200.39. The contractor shall identify system security engineering requirements in the contractor’s Requirements Management Specification, write Test Plans and accomplish Verification Testing to mitigate protection risks to an appropriate level.

CDRL Sequence No. A022 - Technical Report–Study/Services - Critical Program Information assessment - DI-MISC-80508B

3.3.6.2 Criticality Analysis - Cyber

The contractor shall accomplish a Criticality Analysis. The criticality analysis shall show traceability from the mission threads to the supporting subsystems, critical functions/processes and ultimately identify Critical Components (CC). The CC shall subsequently be identified as level I through level IV critical. The contractor shall identify current risk and recommend supply chain countermeasures for all level I and II CC, to include alternate components as needed.

CDRL Sequence No. A023 - Technical Report–Study/Services – Criticality Analysis - DI-MISC-80508B

3.3.6.3 Supply Chain Risk Management (SCRM) - Cyber:

The contractor shall develop, implement and maintain a Supply Chain Risk Management Plan IAW the most current version of the Key Practices and Implementation Guide for the DoD Comprehensive National Cybersecurity Initiative 11 Supply Chain Risk Management Pilot Program, SP 800-161 (2nd Draft) Supply Chain Risk Management Practices for Federal Information Systems & Organizations and NISTIR 7622 Notional Supply Chain Risk Management Practices for Federal Information Systems and DoDI 5200.44. Major events within SCRM shall be reflected in the Integrated Master Schedule. Major events include, but are not limited to, Software Quality Audits, Software Configuration Audits, and Software Qualification Testing. SCRM shall be flowed to vendors and subcontractors that produce software products used in meeting program requirements. The contractor shall report all areas of non-compliance for all level I and level II critical components as identified in the criticality analysis to the Government and provide the Government solutions in an effort to move towards full compliance where appropriate.

CDRL Sequence No. A024 - Technical Report–Study/Services – Supply Chain Risk Management (SCRM) - DI-MISC-80508B

3.3.6.4 Hardware and Memory Architecture Analysis Report - Cyber The contractor shall complete the Hardware and Memory Architecture Analysis Report (report details and format to be provided by USG).

CDRL Sequence No. A025 - Technical Report–Study/Services – Hardware and Memory Architecture Analysis Report - DI-MISC-80508B

3.3.6.5 Software Assurance

The contractor shall develop secure, robust, and assured software through use of disciplined processes and procedures based on secure coding standards, practices, and guidelines (e.g. DISA STIGs, OWASP, SANS). The methodology to be used in performing security-related and software assurance activities for software shall be documented in the Software Development Plan (SDP) [CDRL A010] to include the regularly occurring frequency of assessment actions and procedures.

CDRL Sequence No. A026 - Technical Report–Study/Services – Software Assurance - DI-MISC-80508B

3.3.6.5.1 Software Assurance Testing and Evaluation

The contractor shall apply software vulnerability detection methods and automated internal code-level (static and dynamic), external penetration and fuzz testing, off-nominal/negative testing, and database scanning tools and the most current DISA STIGs/SRGs, specifically the Application and Database STIGs/SRGs and report results. The contractor shall conduct the software assurance evaluations leveraging: Common Vulnerability Enumeration ®; Common Attach Path Enumeration and Classification™; and Common Weakness Enumeration™. The contractor shall analyze the results of each penetration test, fuzz test, and off-nominal test and identify all anomalies that degrade confidentiality, integrity, or availability. The contractor shall eliminate, or otherwise mitigate these anomalies. Evidence of the software changes shall be provided to the Government for review. The contractor shall develop and provide written documentation in the Software Test Report (STR) [CDRL TBD, DI-IPSC-81440A] of the results of the scans and tests along with a mitigation plan.

[Note: This section uses the following definitions – 1) Penetration Testing: A test methodology in which assessors, typically working under specific constraints, attempt to circumvent or defeat the security features of an information system. 2) Fuzz testing: A software testing technique, often automated or semi-automated, that involves providing invalid, unexpected, or random data to the inputs of a computer program. The program is then monitored for exceptions, such as crashes, failing built-in code assertions, or potential memory leaks. 3) Off-Nominal Testing: (Also known as negative testing) consists of tests that examine system performance under conditions that are not covered by explicit system requirements. This includes tests where input data: is not strongly typed; has the incorrect syntax; is outside of length boundaries; contains unpermitted characters; or contains numbers that are incorrectly signed and outside range boundaries.] CDRL Sequence No. A027 - Software Test Report - DI-MISC-80508B CDRL Sequence No. A028 – Contractor Data Management Plan (CDMP) – DI-MGMT-82228

3.3.6.5.2 Malicious Code Certification

The contractor shall represent and certify that the delivered software shall be free from all computer viruses, worms, time bombs, back doors, and other harmful or malicious code intended to or which may damage, disrupt, or permit access to an unauthorized entity whether that is access to software, hardware, networks, data, or information. Certify all code delivered, including but not limited to Commercial off the Shelf (COTS), Free and Open Source Software (FOSS), and other developed code.

3.3.6.6 Contractor Cybersecurity Support

The Contractor shall support Government in fulfilling Cyber Security requirements needed to support the OFP/Software/Firmware or Hardware product. This includes but is not limited to: Supporting Cybersecurity Risk Assessment, Assistance in Conducting Criticality Analysis (CA) and Demonstration of visibility into supply chain and Software Assurance for critical components.

3.3.7 Operational Flight Program

The Contractor shall provide the 3DA Operational Flight Program (OFP) Version Description Document (VDD), Software Product Specification document, and a user manual.

CDRL Sequence No. A029 - Software Product Specification -DI-IPSC-81441A CDRL Sequence No. A030 - Software Version Description -DI-IPSC-81442 CDRL Sequence No. A031 - User Manual – OFP Manual - DI-IPSC-81443

3.3.8 Software Test Plan

The Contractor shall deliver a software test plan for the 3DA OFP. First submission shall be 60 days prior CDR and final at FCA/PCA.

CDRL Sequence No. A032 - Software Test Plan - DI-IPSC-81438

3.3.9 Hardware Test Plan

The Contractor shall provide a 3DA System Hardware Test Plan as an appendix or attachment as part of the overall TEPP. 3DA System Electro-Magnetic Interference (EMI) Procedures shall be delivered and include a section dedicated to the requirements for meeting A-10 aircraft qualifications. The Contractor shall provide the Hardware Test Plan based on the Air Force Military Standard 810 (or latest rev), Air Force Military Standard 461 (or latest rev), MIL-STD 810G, MIL-STD 461G, MIL-STD 464C, and MILSTD 704A, and Fairchild Source Document SA220R0307 (A-10 Vibration Profile).

CDRL Sequence No. A007 - Test and Evaluation Program Plan (TEPP) - DI-NDTI-81284

3.3.10 Software Requirements Specification

The Contractor shall deliver a Software Requirements Specification report at PDR.

CDRL Sequence No. A056 – Software Requirements Specification (SRS) - DI-IPSC-81433

3.3.11 Software and Firmware Source Code

The Contractor shall provide Software and Firmware Source Code, Board Support Package (BSP) Source Code, and maintenance support equipment source code on compact disc(s) and associated documentation in editable format in accordance with CDRL (DI-IPSC-80590B) and Software Design Description in accordance with CDRL (DI-IPSC-81435A) except on COTS, MOTS and GOTS equipment. This information will be classified as Government Purpose Rights and will be used for establishment of future repair capabilities on the chosen system. The Contractor shall also submit information required to certify the software product as secure for US Air Force Information Systems. The Government will provide a series of documents to be completed by the Contractor for the purpose of establishing Information Assurance certification.

CDRL Sequence No. A021 - Computer Program End Item Documentation - DI-IPSC-80590B CDRL Sequence No. A033 - Software Design Description - DI-IPSC-81435

3.3.12 Software End Items

The Contractor shall provide two copies of compiled 3DA OFP to the Government on compact disc(s). The Contractor shall provide compiled OFP compatible with existing aircraft loading tools (PATS-70, PATS-70-A, or CAPRE) on A-10 aircraft prior to the commencement of software integration (SIL) testing. The Contractor shall provide the ability to load the 3DA software via the Ethernet fill port.

CDRL Sequence No. A021 - Computer Program End Item Documentation - DI-IPSC-80590B

3.3.12.1 Listing Requirements for the 3DA System Code

The Contractor shall provide a list of all the tools, sub-contractors, and their respective source data required to modify, debug, troubleshoot, update, and compile both Operational Flight Program (OFP) Source Code and BSP Source Code for the 3DA System. The Contractor shall also submit information required to certify the software product as secure for US Air Force Information Systems. The Government will provide a series of documents to be completed by the Contractor for the purpose of establishing Information Assurance certification. First submission shall be not later than 10 working days prior to the commencement of software integration testing at Government facilities, and resubmission shall occur upon incorporation of changes throughout the program.

This IA certification process is required by the DOD, and will necessitate access to extremely detailed information regarding system, subsystem, and component level design and software code. Volatile and non-volatile memory, input/output, and functional allocated architectural information will be required. In order to defray costs normally associated with procuring such detailed information, the Government is willing to sign a non-disclosure agreement regarding this intellectual property that will assure the Contractor that this information shall be used only for the purposes of establishing information assurance certifications, and will be returned or destroyed once that purpose is accomplished. It is vital to note, however, that this process is now a hard and fast requirement for all current and future US Air Force acquisition programs, and if a Contractor is either unwilling or unable to comply with this requirement, that Contractor shall be considered non-responsive to this solicitation.

The Contractor shall not allow the 3DA System to store aircraft data remnants read from the aircraft in Non-Volatile memory when powering down on the ground (weight on wheels). The Contractor shall design the 3D Audio in such a manner as to ensure that classified or encrypted information will not remain in non-volatile memory on any component of the 3D Audio in the event of a crash or ejection. The Contractor shall accomplish tests witnessed by the Government that will support the claim for the 3DAS not being able to store aircraft data remnants. The Contractor shall provide the facilities to develop, test, and repair unclassified 3D Audio systems. The Government will provide the Contractor with data sheets required to certify the memory volatility for Information Assurance and security purposes; the Contractor will complete these data sheets and return them to the Government.

CDRL Sequence No. A021 - Computer Software Program End Item Documentation - DI-IPSC-80590B CDRL Sequence No. A022 - Technical Report–Study/Services - Critical Program Information assessment - DI-MISC-80508B

3.3.13 Test Verification Matrix

The Contractor shall provide a draft Test Verification Matrix at PDR and a final at TRR.

CDRL Sequence No. A034 - Test/Inspection Report - DI-NDTI-80809B

3.3.14 Bench Test

The Contractor shall provide functional bench test report.

CDRL Sequence No. A035 - Test Procedure (Functional Bench Test Procedure) - DI-NDTI-80603 CDRL Sequence No. A034 - Test/Inspection Report - DI-NDTI-80809B

3.3.15 Environmental Qualification Testing

The Contractor shall accomplish 3DA System hardware environmental qualification testing per SOW paragraph 3.1.6. The Contractor shall provide 3DA System hardware qualification test reports to include, but not limited to, environmental qualification, Electromagnetic Interference, and software test.

CDRL Sequence No. A007 Test and Evaluation Program Plan (TEPP) - DI-NDTI-81284 CDRL Sequence No. A034 Test/Inspection Report - DI-NDTI-80809B

3.3.16 Environmental Stress Screening

The Contractor shall submit an Environmental Stress Screening and Implementation Plan that meets MIL-STD-810G or latest revision. The plan shall focus on detection and prevention of workmanship and material defects, and shall take into account the cost of the tests and fixtures required when determining what components are subject to what levels of ESS. Upon Government approval of the ESS plan, the Contractor shall implement ESS procedures to ensure manufacturing quality and eliminate latent workmanship and material defects during the course of the production runs for this contract. Frequency of the environmental screenings shall be determined jointly by the Contractor and the Government, based on the approved system design. Each report shall contain a complete accounting of all ESS actions completed during the subject month, including resolution data for any failures detected.

CDRL Sequence No. A036 - Environmental Stress Screening Procedures and Plan - DI-ENVR-81014 CDRL Sequence No. A034 - Test/Inspection Report - DI-NDTI-80809B

3.3.17 Failure Modes, Effects, and Criticality Analysis (FMECA) The Contractor shall accomplish and provide reliability predictions, maintainability predictions, and Failure Modes, Effects, and Criticality Analysis (FMECA).

CDRL Sequence No. A037 - Failure Modes, Effects, and Criticality Analysis Report (FMECA) - DI-SESS-81495

3.3.18 Test Plan Acceptance

The Contractor shall provide an Acceptance Test Plan for 3DA System production at PRR and final at FCA/PCA. Acceptance of Test Procedures for the 3DA System production at PRR and final at FCA/PCA.

CDRL Sequence No. A038 - Acceptance Test Plan - DI-QCIC-80553A CDRL Sequence No. A039 - Test Procedure (Acceptance) - DI-NDTI-80603

3.3.19 Testing Anomalies

Anomalies discovered in ground or flight test related to the requirements in the 3DA, SRD, SOW, will be resolved as mutually agreed upon during technical interchange meetings in a timely manner. Anomalies may be documented as Watch Items (WITs), Software Program Anomaly Reports (SPARs), or Deficiency Reports (DRs) that arise out of lab, ground, and flight test. As part of the anomaly resolution process, the Contractor shall analyze data provided from Government testing, conduct engineering investigations, provide the Government recommended options for correction, and then implement those changes as determined by the Government Program Manager. Category 1 (showstopper) DRs shall be addressed within five working days after completion of ground testing and five working days after completion of flight test for integration phase.

CDRL Sequence No. A040 - Deficiency Report - DI-PSSS-81535A

3.3.20 Special Equipment

The Contractor shall provide all applicable technical data and operating instructions required for any special equipment pertaining to the 3DA System, and any 3DA System special equipment required in order for the Government to author technical orders, maintenance training curriculum, and pilot academics.

CDRL Sequence No. A016 - TMCR 86-01Q

3.3.21 Depot Stand-Up Support

The Contractor shall provide a White Paper that describes their approach to achieving a Depot Stand-Up solution for 3DA System components anticipated to be repaired in the first order period of this program. The components identified for repair shall include the EIA, ACP, and the 3DA System Support Equipment. The Contractor shall provide a Memorandum of Understanding (MOU) between the Contractor and the Government as to the effort and requirement to support a Depot Repair capability of the 3DA System. A Partnering Agreement shall be created between the Contractor and the Government as to the level-of-work, who will do the work and what is to be accomplished. An overall strategy/plan shall be created to support the Depot effort and include, but not limited to, identifying all technical data necessary to stand up an AF depot. Also, provide an estimated price associated with providing Government Purpose Rights with a required technical data and a list of tools required for repair. Provisioning requirements, and any Special Equipment requirements shall be provided by the Contractor in support of this effort.

CDRL Sequence No. A015 - Technical Data Package - DI-SESS-80776A

3.3.22 Part Numbers

The Contractor shall provide part numbers for Contractor provided parts that are part of the 3DA System as part of the drawing package referenced in paragraph 3.3.1. Aircraft wire harness part numbers and any other type aircraft part numbers will be provided by the A-10 IPT and Engineering.

3.3.23 Weight and Balance

The Contractor shall provide data required to accomplish a weight and balance update to the aircraft as part of the 3DA drawing package (reference SOW paragraph 3.3.1).

3.3.24 Built in Test

The Contractor shall provide Built-In-Test (BIT) functionality in the 3DA System; as well as a mechanism for users to access the results of the BIT, either in flight or during maintenance activities. See the SRD, starting in section 3.2.3.1.3, for all of the BIT requirements.

3.3.25 Engineering Support

The Contractor shall provide engineering support for studies and analysis for the duration of this program to address issues or questions that arise that are not directly addressed elsewhere in this SOW as determined by the Government. The Contractor shall fix any critical safety item anomalies at no additional cost to the Government found during the integration and production phase of this program. Any new requirements will be accomplished under section 3.4.

3.3.26 Trial Vehicle Installation (TVI)

The Contractor shall support a TVI of the 3DA System for both Guard/Reserve and ACC aircraft. These test events will be coordinated with the Contractor by the Government. The Government anticipates a minimum of one test vehicle install per mission designation series (MDS). The Contractor shall update any engineering data found to be in error during TVI within 30 calendar days of the completion of TVI.

3.3.27 Ground and Flight Test

The Contractor shall provide 3 functionally representative systems for aircraft software integration and 4 production representative 3DA Systems for aircraft ground and flight test. The extent of the testing required will be determined by the Government upon receipt of initial design specifications for the Contractor hardware design. As part of the general scope of the contract, requirements for additional data is required and will include the following: Head and Neck loads, Center of Gravity measurements, Compliance with established Knox Box criteria. For additional information regarding length of time required for Contractor support for qualification testing, refer to SOW paragraph 6.0.

Production Representative – 3DAS shall have passed all testing and be fully functional Functionally Representative – 3DA shall be fully functional but full testing not required

3.3.28 Data Storage

The Contractor shall not allow the 3DA System to store aircraft data remnants read from the aircraft in Non-Volatile memory when powering down on the ground (aircraft power off/engines shutdown and ground power removed). The 3DA may store information required for quick re-boot to support power cycle in the air. The Contractor shall design the 3DA in such a manner as to ensure that classified or encrypted information will not remain in non-volatile memory on any component of the 3DA System in the event of a crash or ejection. The Contractor shall accomplish tests witnessed by the Government that will support the claim for the 3DA System not being able to store aircraft data remnants. The Contractor shall provide the facilities to develop, test, and repair unclassified 3DA Systems and the ability to handle classified data per provided DD254 and section 5.1. The Government will provide the Contractor with data sheets required to certify the memory volatility for Information Assurance and security purposes; the Contractor will complete these data sheets and return them to the Government. First iteration is due at PDR, with subsequent iterations due upon the completion of system design changes.

3.3.29 Ejection Compatibility

If required, the Contractor shall support 3DA System ejection compatibility testing. This includes windblast, drop tower, and sled testing. If required, sled qualification testing will occur at a facility TBD by the Government for A-10. If required, the Contractor shall support this testing with both personnel and materiel, including an adequate number of structurally representative units to be consumed during testing.

3.3.30 Maintenance Support

The Contractor shall provide a 3DA System that is supported based on a two-level maintenance support concept. The Contractor shall provide training plans for the aircraft maintainers and pilots. These plans shall be reviewed and approved by the Government prior to fielding. The contractor will use the approved training plans to train maintainers and pilots at each base during the 3DA System fielding.

3.3.31.1 Obsolescence Assessment and a Parts Management Plan (DMSMS) As part of the DMSMS report, the Contractor shall provide an obsolescence assessment and a parts management plan.

CDRL Sequence No. A041 DMSMS Management Plan - DI-MGMT-81948

3.3.30.2 Maintenance Training Curriculum

The Contractor shall provide maintenance training curriculum to support flight test and fielding. The Contractor shall incorporate lessons learned and updates into the curriculum and provide final maintenance training curriculum concurrent with the first production hardware and software delivery for use by Air Education and Training Command, to familiarize maintenance personnel with the 3DA System.

CDRL Sequence No. A042 Presentation Material - Training Curriculum - DI-ADMN-81373

3.3.31 Cockpit Characterization Procedures

If the 3DA System requires cockpit characterization procedures and/or associated support equipment for any reason, then the 3DA System Contractor shall provide a cockpit characterization system that meets the SRD requirements.

3.4 Growth Capabilities

3.4.1 Engineering Change Proposal (ECP)

The Contractor shall incorporate ECPs that arise as part of the ongoing aircraft OFP development process or lessons learned to improve 3D Audio Integration. Changes required to any existing designs to meet the Interface Control Document (ICD) and aircraft software design documents, or claimed threshold or objective performance in the SRD, are the responsibility of the Contractor.

CDRL Sequence No. A043 Engineering Change Proposals (ECP) - DI-SESS-80639D

3.5 Production

3.5.1 Kit Proof Activities

The Contractor shall support kit proof activities of the 3DA System on the A-10 aircraft. The location of the kit proof will be accomplished at a location determined by the customer, but shall be located in the continental U.S. (CONUS).

3.5.2 Production Levels

The Production levels will be according to Group A, Group B, and Group C deliver requirements. Production levels for Group A items shall be based on a maximum deliver of sixteen (16) Group A kits per month for a maximum production level of (200) Group A Kits per year. Production levels for Group B items shall be based on a maximum delivery of sixteen (16) 3D Audio systems per month for a maximum production level of (200) 3D Audio systems per year, and a minimum of one (1) Group B 3D Audio system per month for a minimum production level of twelve (12) 3D Audio systems per year.