RFI for KC-46 Systems Integration Lab Operations _Sustainment.pdf

CUI

REQUEST FOR INFORMATION (RFI)

RFI for KC-46 Software Integration Laboratory Operations and Sustainment (O&S)

Requestor: USAF AFLCMC/WLC (KC-46A Program Office)

Description

United States Air Force (USAF) KC-46A Tanker Program Office (PO) seeks information from qualified contractors interested in providing support for KC-46A Systems Integration Laboratory (SIL) Operations & Sustainment (O&S) (K-SIL O&S).

THIS IS A REQUEST FOR INFORMATION ONLY. This RFI is solely for information and planning purposes – it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit to contract for supply or service. The PO is not seeking quotes at this time and will not accept unsolicited quotes. Additionally, the PO will not fund responding to this RFI; cost to respond is at respondent’s expense.

Finally, not responding does not preclude/prevent respondent participation/consideration if future RFP is issued.

Background

The KC-46A Tanker is derivative of the Boeing 767-2C, finished to meet unique USAF Tanker requirements. It provides worldwide, day, night, and adverse weather aerial refueling to receiver-capable US, allied, and coalition military aircraft, including unoccupied. The K-SIL will be built to serve as a high-fidelity testing center to verify software, avionics, and hardware interactions. The projected completion date for the K-SIL is 30 April 2030.

Under the original Interim Contracted Support (ICS) contract (FA8625-11-C-6600), which concluded its Period of Performance (PoP) in June 2022, requirements nor provisions were established for stand-alone software sustainment. This lack of coverage created a critical gap, leaving the Program Office without a contract vehicle to execute software sustainment including regression testing in the SIL when SW updates are released by common item program offices like MAGR2K, LAIRCM, KG-245). Consequently, the burden of software "care and feeding" shifted to the initial KOSS contract. To resolve severe gaps in software sustainment the USAF is investigating the ability to consolidate SW sustainment into integrator led contracts; in this instance for the KC-46 SIL via KC-46 SIL O&S.

There are two similar but different RFIs that are being released by AFLCMC/WLC. The first one entitled “RFI for KC-46 SW Integration Sustainment & Support (K-SWISS)” is intended to provide system integrator capability for KC-46 aircraft. An integrator will perform the duties of creating a relationship (contract) with all the systems within the aircraft to perform integration, test, certification, design and development.

The second one entitled “RFI for KC-46 Software (SW) Operations and Sustainment (O&S)” is intended to provide regular maintenance for the individual systems within the KSIL environment, such are hardware and software modifications.

It will be up to each vendor to decide if their response to these RFIs will be one consolidated RFI or a standalone RFI.

Scope

The PO seeks Industry perspective for establishing and providing integrated organic SW Operations and Sustainment (O&S) capability for the KC-46 SIL. Parties responding must provide information and/or documentation validating technical ability to provide system integration services to create agreements with suppliers, manage software sustainment efforts and guide development of organic SW O&S for the KC-46 SIL performed by organic sustainment and Public Private Partnerships (P3). Please respond to the following:

1. Does your company currently have appropriate manpower with technical expertise and skill set, and does the company have required capability to provide the full level of system integrator support required to develop and maintain the K-SIL? Agile SW development is structured to increase flexibility, collaboration and user satisfaction stemming from user feedback and interaction thus scope and performance requirements will vary.

a. Please explain your current agile software development process, how it aligns with DoD 5000.87 and how it can be applied to K-SIL O&S in detail.

2. The SIL comprises many systems including (Wing Aerial Refueling Pod (WARP), Remote Vison System (RVS), Actuator Control Unit (ACU), AROS Flight Control Stick Electronic Unit (AR_FCSEU), Avionics Flight Management Computer (AFMC), Ariel Refueling Management System (ARMS), Aerial Refueling Operator Control and Display Unit (AROCDU), Multifunction Control and Display Unit (MCDU), Military Data Network (MDN), Centerline Drogue System (CDS), Tactical Situation Awareness System (TSAS) and Radar Warning Receiver (RWR) Most of these systems/subsystems are specific to KC-46 refueling capability. All systems/subsystems contain software that was modified for the KC-46 program.

a. Does your company possess technical and fundamental awareness of these systems? Does your company have system integration experience with these system/subsystems, with similar aircraft system/subsystems? Please explain in detail.

3. The following companies correlate to the above systems: WARP (Eaton), RVS (Collins), ACU (Boeing), AF_FCSEU (Woodward), AFMC (GE), ARMS (Boeing), AROCDU (Boeing), MCDU (GE), MDN (Boeing), CDS (Eaton), TSAS (Boeing) and RWR (Raytheon).

a. Does your company have business relations with any of the above vendors of the listed systems/sub-systems? Please explain in detail.

4. Technical aspects

a. The KOSS SW service contract prevents gaps in critical operational support.

1. Scope encompasses Software Maintenance, and System Integrator capability and currently relies on continued Original Equipment Manufacturer (OEM) support to facilitate use of a dedicated contractor owned and operated software development environment.

b. SSOCS establishes the permanent organic software sustainment (KC-46 SIL) at Tinker AFB operated by organic and P3 services

1. Requires technical ability to integrate and sustain Computer Software Configuration Items (CSCIs) and military-unique CSCIs within the Software Development Environment (SDE) and KC-46A Systems Integration Laboratory (KSIL) to include CDS, AFMC, RWR, AR_FCSEU, WARP, and MCDU.

c. Systems Integrator Requirement

1. Sustain KC-46 Major Modernization & Software baseline enhancements, overlapping post-production modernization programs such as:

a. Block 1 PACS (Post-Production Modernization) integrates four (4) critical mission capabilities: Mobile User Objective System (MUOS) for BLOS UHF satellite comms, Second-generation Anti-jam Tactical UHF Radio for NATO (SATURN) waveform, MIDS-JTRS Link-16, and Airspace Control Order (ACO) overlays in the Tactical Situational Awareness System (TSAS).

b. Remote Vision System (RVS 2.0) replaces the single Video Graphics System (VGS) with a revised design including Video Processing Unit (VPU), Video Routing and Communication Unit (VRCU), and updated Boom Sensor LRU utilizing 4K and Full HD LWIR cameras with 3D displays. Mitigations are currently managed through Enhanced RVS

(eRVS) updates across Aerial Refueling Management System (ARMS) and ARO Control and Display Unit (AROCDU).

c. Boom Telescope Actuator Redesign (BTAR) redesigns telescoping actuator to use active hydraulic flow control with a pressure feedback valve (PQ-valve), delivering smooth, continuous "spring-like" resistive force. Introduces flight control stick shaker to provide tactile force queuing to the ARO/AROI under high radial loads. This alters control laws and built-in tests (BIT) within the Actuator Control Unit (ACU), ARMS, and Central Maintenance Computing Function (CMCF).

d. Contractor must show qualified comprehensive technical ability and compliance for the following core requirements required for this SW O&S program:

1. Providing system integrator capability for annual/Multi-Year SW releases consisting of maintenance, patching, integration and lifecycle support:

a. Managing and maintaining specialized military flight software and providing COTS software oversight and support.

b. Perform software operating system patching (e.g., Windows Embedded Standard 7, Red Hat Enterprise Linux 6.5) and Java environment updates across distributed and multi-workstation architectures without impacting certified avionics baselines.

c. Manage and deploy cybersecurity tools and configurations (e.g., McAfee VirusScan, Cisco Intrusion Prevention Systems [IPS]).

2. P3 Co-habitation & K-SIL O&S:

a. Establish, operate, and co-habitat in a secure Government facility (Building 9001, Tinker AFB) alongside 76th SWEG personnel.

b. Proposed processes for shared use of development servers, configuration databases, and joint execution of software modifications within a collaborative, unified organizational structure.

3. Hardware-in-the-Loop (HIL) Lab Topologies & Simulation Environments:

a. Replicate, scale, and maintain complex HIL and wrap-around simulation environments (using tools like Integrated Aircraft Configuration [IAC] and Parallel Simulation System [PSIM]).

b. Establishing and operating the following laboratory topologies:

1. Software Development Environment (SDE): Secure development workstations, network-attached storage (NAS) servers, and tools (e.g., IBM Rational ClearCase/ClearQuest, DOORS requirements management, and VectorCAST/Sherlock code coverage tools).

2. Government Software Development Lab 1 (GSDL-1):

Classified testing environment with integration test benches, an AROS console, and geolocation stimulation software for RWR, TSAS, and MDN software validation.

3. Government Software Development Lab 2 (GSDL-2):

Unclassified environment featuring the Avionics Integration Cabin (IntegCab), AROS, and a specialized "4-Box" testing setup (incorporating ARCC, SDCN, OBIGGS, BTC, and FQIS).

4. Aerial Refueling Software Development Lab (AR-SDL):

Closed-loop dry simulation environment for boom flight control laws, actuator timing, and telescoping rate controls.

4. Federated Multi-Bus Avionics Integration & Software Partitioning:

a. Extensive technical experience working with tightly integrated, federated avionics suites and diverse data bus protocols.

b. Required interfaces include ARINC-429, MIL-STD-1553B, ARINC- 664 (AFDX Ethernet), ARINC-739 (MCDU), ARINC-708 (Weather Radar), and serial standards (RS-422, RS-485, USB).

c. Demonstrated experience managing ARINC 653 Integrated Modular Avionics (IMA) partitioning, implementing robust software boundaries to segregate unclassified data (e.g., civil Aircraft Communication Addressing and Reporting System (ACARS), unclassified crew apps) from classified mission networks (e.g., TSAS, Secret Internet Protocol Router Network (SIPRNet)).

5. FAA Airworthiness Compliance & Military Cert Merge Strategy:

a. Experience executing software verification and validation under RTCA DO-178B/C (Design Assurance Levels [DAL] A through D) and RTCA DO-254 guidelines.

b. Proven ability to support FAA's 4 Stages of Involvement (SOI 1-4) process, update the Plan for the Software Aspects of Certification (PSAC), and perform safety hazard analyses.

c. Proven capability to manage FAA Amended Type Certificate (ATC) and Supplemental Type Certificate (STC) compliance, while aligning with Military Type Certification (MTC) and Military Sovereignty of Flight (SoF) requirements.

d. Demonstrated methodology executing continuous "Cert Merge," systematically merging divergent, highly complex developmental branches (e.g., RVS 2.0 ARMS 2.x and BTAR ARMS 3.x/ACU 3.x) into a unified, certified release baseline.

6. RMF & Cyber Survivability Attributes (CSAs 1-10) Implementation:

a. Experience ensuring compliance with DoDI 8500.01, DoDI 8520.02, DoDI 5200.39 (Critical Program Information Protection), and the Risk Management Framework (RMF).

b. Ability implementing and maintaining the 10 Cyber Survivability Attributes (CSAs) at the software/firmware layer, including:

1) CAS-01: Control Access

2) CAS-02: Reduce System’s Cyber Detectability

3) CAS-03: Secure Transmissions and Communications

4) CAS-04: Protect System’s Information from Exploitataion

5) CAS-05: Partition and Ensure Critical Functions at Mission

Completion Performance Levels

6) CSA-06: Minimize and Harden Attack Surfaces

7) CSA-07: Baseline & Monitor Systems and Detect Anomalies

8) CSA-08: Manage System Performance if Degraded by Cyber

Events

9) CSA-09: Recover System Capabilities

10) CSA-10: Actively Manage System’s Configurations to Achieve and

Maintain an Operationally Relevant Cyber Survivability Risk Posture (CSRP)

7. Software Configuration & Database Management:

a. Manage complex Computer Program Identification Number (CPIN) labeling, indexing software packages in ETIMS library, and coordinating distributions through the Software Control Center (SCC).

b. Manage aircraft-specific General Software Manuals (TO 1C-46(K)A- 8-1) and Software Version Description (SVD) database parameters.

c. Provide a rigid step-by-step process detailing Software Deficiency Report resolution via Root Cause Analysis, regression testing and RMF validation prior to fielding ensuring flight safety and cybersecurity postures are appropriate

d. Identify and document the vendor-specific Agile and DevSecOps continuous integration/continuous development (CI/CD) strategy supporting the program, to include the processes, tools, environments, pipelines, governance, security controls, testing approach, release procedures, and roles and responsibilities required to develop, integrate, secure, test, and deliver software capabilities.

e. Identify and document a data rights strategy for the KC-46 aircraft program that ensures all Intellectual Property (IP), technical data, computer software, computer software documentation, and other contract-developed or contract-used deliverables are assessed and structured to provide the Government with Government Purpose Rights, Limited Rights, or other appropriate license rights sufficient to enable the United States Air Force to organically operate, maintain, sustain, repair, modify, upgrade, and support the entire KC-46 aircraft, as required.

8. Type-1 Training Transition & Organic Training Curricula:

a. Proven ability designing, establishing, and executing Type-1 technical training courses in accordance with DAFH 36-2675 (Information for Designers of Instructional Systems) and AFI 36-2670 (Total Force Development).

b. Providing curriculum that qualifies software personnel to independently operate SDE/SIL environments, troubleshoot faults, and perform depot-level software maintenance.

9. The K-SWISS operation will contract with a System Integrator that will create subcontracts with suppliers and manage the development, testing, and certification of KC-46 software. The KC-46 SIL O&S contract will provide regular maintenance for the K-SIL environment including managing modifications as required with aircraft updates, managing DMS issues, updating software versions as required, system patches and firmware updates, hardware preventative maintenance, rack and server inspections, switches, cabling and maintain core lab network service. Assess and explain whether K-SWISS operations should be combined with KC-46 SIL O&S as a single support construct, or whether they should remain two distinct efforts.

The response shall provide the rationale for the recommended approach and address the operational, technical, cybersecurity, cost, schedule, staffing, governance, and risk implications associated with each option.

e. Information Requested / Instructions for Response

1. Page size shall be 8.5 x 11 inches; foldouts are permitted and will be included in total page count.

2. Pages shall be single-spaced, Arial font 10-12 point, 1-inch top and bottom margins, ¾ inch side margins.

3. Capability package with cover letter documenting ability to meet the stated requirements with sufficiently qualified personnel.

a. Qualification – relevant type and duration of employee experience.

b. Level of involvement - prime or subcontractor.

c. Time/Years providing similar support and oversight.

d. Other relevant details or information.

4. Capability Package should include the following elements:

a. 10-page maximum not including cover page describing the items listed above. The responses should be formatted as follows:

1. Level of contractor interest, likelihood of submitting a proposal as a prime contractor: not likely, somewhat not likely, likely, somewhat likely, highly likely.

b. Potential teaming arrangements (if likely to submit a proposal).

c. If considering a teaming arrangement, describe the tasks the prime would perform versus tasks the subcontractor would perform.

5. Prospective Business Identification

a. Company Name, Address, Phone Number, E-mail, Point of Contact Information, website address.

b. Highest security clearance your company currently holds.

c. Business status - Small, Small Disadvantaged, Woman- Owned, 8(a) Certified, Service-Disabled, Veteran-Owned Business, etc.

d. Previous contract numbers with descriptions of services.

e. Contracting Officers’ and Program Managers’ contact information.

f. Cage Code, Unique Entity Identifier (UEI) Number, size/socio-economic status (large, small, 8(a), etc.) for NAICS 336413 and other information the US Air Force should consider reviewing responses.

5. Please deliver the completed response to this RFI electronically to Mr. Michael Crane via email at michael.crane.11@us.af.mil No Later Than (NLT) 11 Dec 2026 5pm EST.

END

mailto:michael.crane.11@us.af.mil