Order Description - Interim Link-16 on HC-130J.docx

AIR FORCE LIFE CYCLE MANAGEMENT CENTER ROBINS AIR FORCE BASE, GEORGIA 31098-1670

Order Description for Interim Link-16 Capability for HC-130J T-1 modification

DISTRIBUTION STATEMENT D: Distribution authorized to Department of Defense and U.S. DoD Contractors only. Other requests for this document shall be referred to AFLCMC/WIUAB Robins AFB, GA 31098.

1.0 Description of Services: The purpose of this subject task order description is to define the requirements for the integration of a Line of Sight (LOS) Data Link 16 radio on up to twenty two (22) HC-130J aircraft using portions of the Airborne Mission Networking (AbMN) system developed for the MC-130J and EC-130J to ensure compatibility between the SACU, LOS data Link16, and AbMN software on the HC-130J aircraft.

1.1 Objectives:

1.1.1 Contractor shall integrate a government furnished Multifunctional Information Distribution System – Joint Tactical Radio System (MIDS-JTRS) LOS data Link 16 radio on up to twenty two (22) HC-130J aircraft using portions of the Airborne Mission Networking (AbMN) system developed for the MC-130J and EC-130J to ensure compatibility between the SACU, LOS data Link16, and AbMN software on the HC-130J aircraft.

· Contractor shall perform one (1) Trial Kit, one (1) Kit Proof, and up to Twenty (20) Production installations.

· There shall be no degradation of current HC-130J systems (i.e. Vortex, SADL, AFTRS-R, PRC-117G, etc.).

2.0 Services Summary: This section is TBD.

3.0 Government Property: The Government will provide the MIDS-JTRS radios as GFE.

4.0 Technical Requirements: The contractor shall perform all design, installation, and testing required of this HC-130J LOS data Link 16 effort. The contractors’ structural, electrical design, and installation shall meet the requirements of the HC-130J platform and shall be documented in a Level III drawing package. The contractor shall support Government test activities and provide support to the Link 16 system, as required. The contractor shall support program and technical reviews, as required.

4.1 Period and Place of Performance

4.1.1 Period of Performance (PoP): The PoP for this order shall be 14 Months from date of task order award.

4.1.2 Place of Performance: These services shall be performed as follows. The Contractor shall perform a Trial Kit Installation (TKI), Proof Kit Installation (PKI), and all Production (Prod) Installations. The TKI and PKI will be conducted at the contractor’s modification facility or the USAF bases, as agreed upon by the contractor and government. The production installations will be completed at the USAF bases by at least three separate Contractor Field Teams (CFTs) working concurrently at the same or different bases, as required by USAF aircraft availability.

4.1.3 Schedule of Support: Trial Install April 2023; Kit Proof June 2023; Production July 2023 The contractor shall identify any kit part shortages that are due to long-lead times and provide the delivery dates for each item.

4.3 Contract Data Requirements Lists (CDRLs): This section is TBD.

4.4 Travel: This section is TBD.

4.5 Program Management

4.5.1 Contractor’s Progress and Management Report: This section is TBD.

4.9 Program and Design Reviews: The contractor shall participate in, support, and conduct reviews and periodic meetings with Government, vendor, and subcontractor representatives, and associated contractors. At these meetings, the contractor shall provide risk identification, risk assessment, risk handling, and risk monitoring status. The contractor shall develop and deliver agendas and minutes.

4.9.1 Kickoff Meeting: A kickoff meeting shall be hosted no later than 30 calendar days after contract award. The purpose of the meeting is to review and evaluate the contractor’s interpretation of the basic contractual requirements and to provide necessary direction and guidance.

4.9.2 Engineering Data Guidance Conference (Engineering Data Post Award Integrated Program Team (IPT) Meeting): Not applicable (T-1 modification).

4.9.3 In-Process Review (IPR) of the TDP: Not applicable (T-1 modification).

4.9.4 Preliminary Design Review (PDR): The contractor shall host and conduct a PDR after completion of all technical research and development of a preliminary design approach. The PDR shall be held before the contractor begins the detailed engineering process. During the PDR, the contractor shall present the design analysis and preliminary design for Government review.

4.9.5 Critical Design Review (CDR): The contractor shall perform detailed design and shall present the detailed design, including loads/stress analysis and any other supporting analyses at a CDR. The contractor shall perform the effort required to achieve the CDR entrance and exit criteria defined in paragraphs 4.9.5.1 and 4.9.5.2 below. The contractor shall prepare an approved information copy of all data to be covered in the CDR at least 10 work days prior to the design review.

4.9.5.1 CDR Entrance Criteria:

4.9.5.1.1 Manufacturing Processes: Identification and description of the manufacturing processes needed to produce the designs.

4.9.5.1.2 Materials or Manufacturing Obsolescence: Identification and description of the time until materials or manufacturing obsolescence of the designs.

4.9.5.1.3 Corrosion and Production Issues: Detailed analysis or test data that supports the insusceptibility of the designs to corrosion, stress corrosion cracking, and production issues that may cause premature failure.

4.9.5.1.4 Producibility/Manufacturability Issues: Identify any Producibility/Manufacturability Issues.

4.9.5.1.5 Test Plan: Provide Acceptance Test Procedure and support development of a Qualification Test Plan.

4.9.5.2 CDR Exit Criteria:

4.9.5.2.1 Product Document Approval: Government approval of supporting analysis and documents.

4.9.5.2.2 Design Approval: Government approval of the design concept

4.9.5.2.3 Acceptance Test Plan and Procedures Approval: Government approval of acceptance test plan and procedures.

4.9.5.2.4 Deliverables: The contractor shall provide all data documented as part of this CDR in MS-Word, MS Excel, or PDF format.

4.11 Airworthiness Management: The contractor shall develop, implement, provide the compliance artifacts and maintain the compliance report per the HC-130J LOS Data Link 16 system certification basis.

4.11.1 Airworthiness Certification Basis: The Contractor shall develop/produce/maintain and deliver an Airworthiness Certification Basis/criteria that will accurately depict the final product. The most current Modification Airworthiness Compliance Criteria (MACC) template shall be used to identify all applicable criteria pertinent to this effort. Title page and description shall be filled out as accurately as possible. Criteria will be identified as applicable by selecting “Y” or “N” respectively utilizing the guidance/descriptions provided in MIL-HDBK-516C expanded. If “N” is selected a rationale must be provided for each non-applicable criteria. This document is not considered approved until it has been completely signed at the appropriate level by the Government.

4.11.2 Airworthiness Compliance Summary Matrix/Data: The contractor shall develop/produce/maintain and deliver an Airworthiness Compliance Summary matrix, and all accompanying engineering data, that accurately depicts the final product. The compliance summary matrix shall utilize the Government approved certification basis as the baseline/starting point for the compliance summary. Each applicable criterion shall clearly identify the standard being used, method of compliance, supporting data artifacts, and whether or not compliance has been met. If compliance is not met a risk assessment must be conducted /written. Each data artifact/document/analysis/drawing/report used to show compliance must have a unique identifying number and title. All artifacts used to show compliance shall be listed on the document summary tab of the matrix reflecting where it is applied along with document title and file name. All airworthiness/engineering products/ data created as a result of this contract shall be shall be delivered to the Government with unlimited rights.

RFI: TBD

Distribution Statement D Rev 0

5.11 Cybersecurity

5.11.1 Cybersecurity/Information Assurance (IA): The Contractor shall identify, design, manage, implement, and verify cybersecurity requirements. The contractor shall ensure that the development environment and processes support cybersecurity implementation. The Contractor shall perform analyses and verifications and deliver necessary artifacts, source data, and verification results to the Government in order to obtain Authorization for the system to operate IAW DoDI 8500.01 and 8510.01.

The Contractor shall ensure security requirements are traced to specifications and architectures that comprise the functional and allocated baselines. The Contractor shall integrate cybersecurity considerations into program systems engineering processes, especially risk management. The Contractor shall integrate cybersecurity into all Software Integration Lab (SIL) testing. The Contractor shall consider Cyber resiliency (Anticipate, Withstand, Recover, and Adapt) into the system design, development, and integration of system components as to deny adversaries the ability to degrade, modify, or destroy Link 16 functionality and capability.

5.11.2 Cybersecurity In Technical Data: The contractor shall ensure that training materials, technical manuals, and other technical data developed for the program address any cybersecurity controls (e.g., administrative, procedural, inherited) or requirements that affect system operation, maintenance, repair, or other support activities.

5.11.3 Cybersecurity Requirements: The Contractor shall identify, manage, and verify cybersecurity requirements in the same manner as all other system requirements. The Contractor shall refine the system specifications by translating and deriving cybersecurity specifications from the system cybersecurity requirements, both explicitly specified and implicitly derived. The Contractor shall map and allocate cybersecurity requirements to the hardware and software design for the system. See Committee on National Security Systems Instruction (CNSSI) No. 1253. Refined specifications, with mapped requirements, due as a draft 30 calendar days prior to PDR and final at CDR.

5.11.4 System Architecture Analysis Report (AAR): The Contractor shall prepare a system-level architecture analysis detailing system architecture, data types, hardware, software, interfaces, peripherals, networks, access, and incident handling capabilities. Analysis shall include:

(1) System Authorization Boundary system-level authorization boundary report describing the PIT boundary, interconnections, data types, and data transfers.

(2) Interconnection diagrams, data type descriptions, data flow diagrams, hardware and software lists.

(3) Identification of internal configuration management, quality assurance, security, and systems engineering processes applied during system design, build, test, and manufacture.

Analysis shall be in a format complementary to the aircraft Architecture Analysis Report (AAR) which is currently being written by Raytheon. The Contractor is responsible for writing an AAR covering the Link 16 integration. It is permissible to submit the AAR as an attachment to the System Security Plan (SSP).

5.11.5 System Security Plan (SSP): The System Security Plan (SSP) document shall provide an overview of the security requirements of the system, general security controls and describe the controls in place and (or) planned controls for meeting those requirements. The system security plan should be viewed as documentation of the structured process of planning adequate, cost- effective security protection for the system. The system security plan shall delineate responsibilities and expected behavior of all individuals who access the system. Finally the SSP will also include a compiled list of system characteristics system interconnection agreements, contingency plan, security configurations, configuration management plan, software lists, and hardware list. The SSP shall be delivered as a draft 30 days prior to SRR, 30 days prior to PDR, and as final 10 days after PDR.

5.11.6 Security Controls Traceability Matrix (SCTM): The Security Controls Traceability Matrix (SCTM) specifies the details of each control introduced in the SSP. The SCTM is the detailed analysis of the applicable security controls. The Aircraft-related SCTM usually combines the Aircraft-specific overlays, the Ground Support Equipment overlays, and tailored security controls used to meet the security requirements specified in the SSP. The SCTM covers all the security controls, not just the non-compliant ones implied by the DoD Risk Management Framework (RMF) process guides. The SCTM shall be delivered as draft 30 days prior to CDR and as final 30 days after TRR. Government provided templates shall be used.

5.11.7 Security Assessment Plan: The contractor shall develop a Security Assessment Plan (SAP) in support of an Interim Authority to Test (IATT). The SAP shall identify means to assess the system against the cybersecurity requirements, determining the extent to which the controls are effecting, operating as intended, and producing the desired outcome. In addition, SAP shall specify test platforms, equipment, and interfaces. To the extent possible, the contractor shall integrate test and evaluation (T&E) of cybersecurity requirements into the overall T&E process, to include component level testing performed by suppliers.

5.11.8 Security Assessment Report (SAR): The Contractor shall verify the implementation of cybersecurity controls and submit the verification results in a Security Assessment Report (SAR). SAR shall map to procedures outlined in SAP. The SAR shall be delivered as draft 30 days prior to TRR and as final at TRR. This document may contain sensitive or classified information and must be delivered using proper procedures.

5.11.9 Risk Assessment Report (RAR): The focus of a risk assessment is to determine if there is residual risk associated with the security controls found to be non-compliant during the contractor’s assessment, leaving vulnerability. The Risk Assessment Report (RAR) is used to capture any findings that will not be corrected prior to the control assessment in the Assess Phase and to communicate the contractor’s risk assessment results to the Government to inform the final air system RMF authorization. The RAR shall be delivered at TRR.

5.11.10 Cybersecurity Incident Reporting: IAW with DFARS 252.204-7012 (c), Upon discovery of a cybersecurity incident affecting covered contractor information systems, covered defense information within those systems, or a cybersecurity incident that affects the contractor’s ability to perform the contractor’s requirements, the contractor shall conduct a review for evidence of compromise. The contractor shall report the incident to the affected DOD systems’ Authorizing Official’s Office beginning with the Aircraft/System’s Information System Security Manager and the system’s program manager within 24 hours of the discovery of the incident.

5.12 Interface Design, Control, and Documentation: The contractor shall ensure that the Link 16 will interface with the existing HC-130J radios. The LOS data Link 16 shall respond to operator stimuli using AbMN software interfaces in the same manner as the SAMS-ESA system as defined by appropriate legacy interface and software documentation. The contractor shall deliver the hardware and software interfaces in an Interface Control Document for each separate aircraft to the Government for approval, and upon notice of any deficiencies, the corrected ICD will be resubmitted within 10 business days.

5.13 Engineering Data: The contractor shall develop/produce/maintain a Technical Data Package (TDP) that accurately depicts the final product. The TDP shall provide the necessary design, engineering, manufacturing, testing and quality assurance requirements information necessary to enable the procurement or manufacture of an interchangeable item that duplicates the physical and performance characteristics of the original product, without additional design engineering effort or recourse to the original design activity. Product data shall reflect the approved, tested, and accepted configuration of the defined delivered item. All engineering product definition data created as a result of this contract shall be considered a part of the TDP. This data includes, but is not limited to CAD data, models and model based definition data sets, and Gerber data.

5.14 Safety of Flight: The Contractor shall support the Government Military Flight Release (MFR) and safety review board processes with requested data and participation in person or via teleconference, if requested.

5.15 Engineering

5.15.1 Weight and Balance: The Contractor shall evaluate any changes to the HC-130J configuration for effects to weight and balance and provide a delta weight and balance report documenting this data in accordance with T.O. 1-1B-50. The Government will provide baseline data, available.

5.15.2 Electrical Power Distribution: The Contractor shall conduct a delta electrical load analysis and submit a written report. The Government will provide baseline data, as available.

5.15.3 Aircraft Structural Integrity: The Contractor shall use MIL-STD-1530 to perform the following tasks:

1) Load Analysis for any Group A/B structural modifications deviating from the baseline HC-130J configuration.

2) Stress Analysis for any Group A/B structural modifications.

5.15.4 Radio Frequency (RF)/Spectrum Management Analysis: The Contractor shall perform an analysis to document the radio frequency systems are physically and functionally non-interfering to themselves and each other when (1) operating independently, and (2) simultaneously transmitting and receiving radiated energy. The analysis shall be of sufficient detail to support Spectrum Management certification. The Contractor shall submit a Stage 3 DD 1494 to support frequency allocation approvals and a Stage 4 for production.

5.15.5 Electromagnetic Interference/Compliance (EMI/EMC): The contractor shall ensure that the system integration is designed to achieve electromagnetic system compatibility. EMI and susceptibility shall be controlled by adequate design provisions to eliminate undesired responses, and emissions from other electronic and electrical system operating within the aircraft environment. EMC at the aircraft system level will be evaluated by the Government with Contractor support during ground and flight tests.

5.15.6 Human Factors: The principles, criteria and procedures of human factors engineering shall be applied to the design of the system IAW the guidelines established in MIL-STD-1472G, Human Engineering. The system shall not affect crew egress or survivor insertion/extraction operations.

5.16 Maintainability: The contractor shall ensure the design of the aircraft integration modifications are repairable by the maintenance personnel (to include minor battle damage IAW T.O. 1-1H-39) at the organizational level. The aircraft integrations modifications shall use Air Force 2-2levels of maintenance – organizational and depot level concepts. Support Equipment requiring external electrical power shall use government common equipment.

5.16.1 The contractor will provide Interim Contractor Support (ICS) during the Qualification Test & Evaluation and Operational Test & Evaluation periods. ICS includes Program Management, Labor, Material, Other Direct Costs, Operational Support Services, Spares, Repair Support, Software Sustainment, Travel, and Routine Data (i.e Status reports, Engineering Change Proposals, etc.).

5.17 Marking Requirement: Unique Item Identification (IUID) is required for all items to be delivered to the Department of Defense (DoD) that meet the criteria established by the FAR.

5.17.1 Reporting in IUID Registry:

4.18.1.1 : Transmission of Government property must be recorded in the IUID Registry. The Government is required to record the transfer of Government Furnished Property (GFP) to the Contractor. The Contractor is required to record the receipt of GFP from the Government. The Contractor is required to record the return of GFP to the Government.

4.18.1.2 : The Government or contractor/subcontractor personnel responsible for causing a “life cycle event” (i.e., abandoned, consumed, destroyed by accident, destroyed by combat, donated, exchanged – repair, exchanged – sold, exchanged – warranty, expended – experimental/target, expended – normal use, leased, loaned, lost, reintroduced, retired, scrapped, sold – foreign government, sold – historic, sold – nongovernment, sold – other federal, sold – state/local, and stolen) will update the item record in the IUID Registry.

5.18 Diminishing Manufacturing Sources and Material Shortages (DMSMS): Not applicable (T-1 modification).

5.19 Systems Orientation/Familiarization: The Contractor shall develop or obtain Type-1 training for the modification and provide it (on disc) to the Government Program Office and each base receiving the modification. Additionally, the Contractor will provide at least one week of hands-on training to Government maintenance and aircrew personnel at each base receiving the modification.

5.20 Technical Data – Operator/Maintenance Manuals: Not Applicable.

5.0 General Information: This section is TBD.

6.0 Appendices

6.1 Appendix A, Special Contract Requirements 18-01 Sexual Harassment/Assault Response and Prevention (Sharp): This section is TBD.

6.2 Appendix B, Reference(s): This section is TBD.

6.3 Appendix C, Acronyms