C-17 Data Recorder
Overview
Buyer
Place of Performance
NAICS
PSC
Set Aside
Original Source
Timeline
Qualification Details
Fit reasons
- NAICS alignment with historical contract wins in similar service areas.
- Scope strongly matches core technical capabilities and delivery model.
Risks
- Past performance thresholds may require one additional teaming partner.
- Potential clarification needed on staffing minimums before bid/no-bid.
Next steps
Validate eligibility requirements, assign capture owner, and schedule partner outreach to confirm teaming strategy before submission planning.
Quick Summary
The Department of the Air Force has issued a Special Notice for a Draft Request for Proposal (RFP) for the C-17 Data Recorder (DBRS) system. This effort seeks industry input on requirements for a system to capture all data from C-17 aircraft data buses and fuel quantity computers, retrofitting the USAF C-17 fleet. This acquisition is a Total Small Business Set-Aside.
The Air Force is exploring a potential shift to a Commercial Solution Opening (CSO) approach, pending approval of a Class Deviation. If approved, the draft RFP will be revised to align with CSO principles, potentially limiting proposal requirements.
Purpose & Scope
The C-17 System Program Office (SPO) requires a Database Recording System (DBRS) to comprehensively record, transfer, and retain all databus traffic on the C-17 aircraft. This involves procuring Line Replaceable Units (LRUs) and spares for the entire 222-aircraft USAF C-17 fleet, plus 12 testing articles and 3 for NATO, totaling 257 LRUs. The system must capture all installed 1553/429 bus and fuel quantity computer data.
Key Clarifications & Requirements (from Vendor Q&A)
- Data Bus Protocols: Government will provide wiring harness design data and interface control documents. Specific protocols (MIL-STD-1553, ARINC 429, Ethernet) and capture rates are detailed in Attachment 10.
- Flight Certification: Military Flight Release (MFR) approval is mandatory prior to delivery acceptance of production LRUs.
- Cybersecurity: DBRS must handle Controlled Unclassified Information (CUI) per NIST SP 800-53, requiring secure boot and trusted computing. Encryption for stored/transferred data is not required.
- Past Performance: Commercial aerospace data system integration experience is not acceptable. Focus is on manufacturing databus recorders or similar solutions for fleet aircraft.
- Production Timelines: Anticipated production ramp: Lot 1 (Aug 2027), Lot 2 (Mar 2028), Lot 3 (Dec 2028), Lot 4 (Aug 2029).
- Connectors: Specific 6-pin and 128-pin connectors are required to mate with aircraft harnesses; alternate connectors are not satisfactory.
Draft Contract Details & Evaluation
- Contract Type: Requirements-type Indefinite Delivery Contract with a 5-year ordering period.
- Pricing: Firm Fixed Price for most Contract Line Item Numbers (CLINs).
- NAICS Code: 334511 (Size Standard: 1350 employees).
- Set-Aside: 100% Small Business.
- Evaluation: Tradeoff source selection, with Technical (most important), followed by Past Performance, then Price.
Submission & Deadlines
- Comments/Questions on Draft RFP: Due by May 1, 2026, 5:00 PM ET.
- RFP Release/Proposal Due Date: Currently To Be Determined (TBD).
- Submit written comments and questions to the provided contacts.
- Email contacts to receive the list of attachments for this draft RFP.
Contacts
- Primary: Robert Rollins (robert.rollins.2@us.af.mil)
- Secondary: Jasmine Jordan (jasmine.jordan.4@us.af.mil)