REQUEST FOR INFORMATION_SAM.pdf

REQUEST FOR INFORMATION (RFI) QUESTIONNAIRE

MISHAP ANALYSIS & ANIMATION FACILITY (MAAF)

FLIGHT RECORDER DOWNLOAD SOLUTIONS ACQUISITION AND SUSTAINMENT

Section 1: Corporate & Business Profile

• 1.1 Company Information: Provide your organization’s legal name, CAGE code, UEI, address, primary point of contact (name, phone, email), and web address.

• 1.2 Business Size & Socioeconomic Status: Specify your business size under NAICS Code 541330 (Engineering Services) or 541511 (Custom Computer Programming Services). Indicate all applicable small business designations (e.g., Small Business, 8(a), HUBZone, SDVOSB, WOSB).

• 1.3 Contracting Vehicles: List any current GSA Multiple Award Schedules (MAS), IDIQs, GWACs, or DoD-wide contract vehicles (e.g., NASA SEWP) through which your services can be procured

Section 2: Technical & Engineering Capabilities

• 2.1 Raw Flash & CCA Extraction Methodologies: Describe industry-standard commercial methodologies, tooling, and hardware interface standards for conducting bench-level Circuit Card Assembly (CCA) memory extractions.

Specifically address practices involving desoldered flash memory chips, 3V/5V NOR/NAND flash arrays, and damaged solid-state Crash Survival Memory Units (CSMUs).

• 2.2 Flight Recorder Interface Experience: Describe your organization's experience interfacing with and processing raw binary data from flight recorder systems.

Please indicate your level of familiarity with systems from the following OEMs:

• General Electric (GE): KVADR, DAU/ECSMU, IDAR / Refreshed IDAR, legacy

CSFDR/SFDR/SAU/CSMU.

• L3Harris / Acron: SRVIVR, F-22 CSMU, F-35 CSMU, FA2100 series, FA2300

MADRAS, FA5003 CVR.

• Curtiss-Wright: CVFDR, CSR.

• Mercury Mission Systems: HH-60W FDR.

• Honeywell / Allied Signal: SSFDR, SSCVR 30/120.

• Universal Avionics: CVR-120, FDR.

• Fairchild: F1000, A200S.

• 2.3 Decompression, Transcription & Data Integrity: Explain how commercial download solutions typically ensure bit-exact raw extractions. How does industry ensure these extractions map seamlessly to OEM-native transcription and decompression software tools without data corruption?

Section 3: Software, System Architecture & Data Rights

• 3.1 Operating Systems & Licensing Verification: What operating systems (e.g., Red Hat Enterprise Linux, Windows) do your existing tools and drivers natively support? How does your software handle license verification and updates in a strictly air-gapped, standalone network environment?

• 3.2 Commercial Licensing & Data Rights Practices: Describe your standard commercial licensing and data rights practices for custom software, APIs, firmware drivers, and technical schematics. How does your firm typically balance proprietary code modules with a customer's need for long-term sustainment data?

• 3.3 OEM Technical Data Access & Facilitation: How does your firm typically obtain the proprietary OEM technical data (such as signal specifications, pinouts, or data decompression algorithms) necessary to perform these extractions?

Specifically, what Non-Disclosure Agreements (NDAs), Associate Contractor Agreements (ACAs), or Government-Furnished Information (GFI) would the Air Force need to facilitate or provide under a future contract to enable your performance?

Section 4: Sustainment & Operational Support

• 4.1 Support Tiers & Obsolescence Management: Describe your typical commercial lead times, support tiers, and service level agreements (SLAs) for hardware repairs, driver updates, and hardware/component obsolescence management.

• 4.2 Installation, Calibration & Remote Support: What elements of software installation, technical system calibration, and hardware maintenance can be performed remotely versus requiring on-site facility access?

• 4.3 Training Delivery Models: Describe the training delivery models (e.g., on-site, virtual, classroom, train-the-trainer) your firm standardly provides to support newly fielded equipment and software interfaces.