Draft DBRS RFP Vendor Questions Final V2.docx

DOCX document 53 KB Posted

Attached to
C-17 Data Recorder
Solicitation number
FA8526-26-R-B007
Issued by

About this file

This is a vendor questions and answers document for a draft Request for Proposal addressing technical clarifications, contract and evaluation questions, and programmatic details for the C-17 Data Recorder System (DBRS).

The DBRS is a comprehensive aircraft data collection system designed to retrofit the USAF C-17 fleet (222 aircraft) with Line Replaceable Units (LRUs) that record data bus traffic across all data buses and fuel quantity computers. The procurement strategy includes 222 LRUs for the USAF fleet, 7 testing articles and 5 spares for Boeing Avionics Integration Support Facility (AISF) and USAF flight tests, 3 units for NATO Airlift Management Program (NAMP), and 27 additional spares, totaling 257 units. This is a Small Business Set Aside with an anticipated IDIQ contract award. The RFP will follow a Commercial Solution Opening (CSO) approach with Technical White Papers due 14 days after RFP release (anticipated end of May), Phase 2 invitations 30 days after RFP, Phase 2 proposals due 14 days after invitation, pitch days within 2 weeks, and award anticipated within one month (approximately 90 days from RFP release). Production lots are scheduled for August 2027, March 2028, December 2028, and August 2029 with quantities to be determined; all production will be FOB Destination with FOB Origin applicable only for select CLINs. Key technical requirements include capturing data from MIL-STD-1553, ARINC 429, EIA-422, and Ethernet buses; supporting approximately 1000 hours of continuous flight data recording on removable SSDs with hot-swap capability; meeting DO-160, MIL-STD-810, and MIL-STD-461 environmental standards; implementing cybersecurity controls for Controlled Unclassified Information (CUI) including secure boot and trusted computing; and providing technical data packages and obsolescence management plans post-award. Evaluation will prioritize Technical factors (highest), followed by Past Performance and Price, with credit given for DoD aircraft modification experience, DoD cyber analysis, and DoD testing experience.

View the file

Other files

File Type Posted
SPECIAL NOTICE - 16 Jun 26.pdf PDF
Draft DBRS RFP Vendor Questions Final.docx DOCX document
Solicitation - FA852626RB007 Draft.pdf PDF

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Draft DBRS RFP Vendor Questions

1. Technical Clarifications

1. Please confirm the specific data bus protocols installed across the C-17 fleet (e.g., MIL-STD-1553, ARINC 429, Ethernet-based systems) that the DBRS must capture.

Review attachment 10

1. What are the required data capture rates, storage capacity thresholds, and retention duration requirements?

Review attachment 10

1. Are there defined environmental qualification standards required (e.g., DO-160, MIL-STD-810, EMI/EMC thresholds)?

Review attachment 10

1. Will Government Furnished Information (GFI) include wiring harness design data packages and interface control documents?

Yes, the pinout and interface tray engineering drawings will be provided.

1. Is flight certification required prior to delivery of production LRUs?

Military Flight Release (MFR) should be approved prior to delivery acceptance of production LRUs

1. What are the cybersecurity requirements for the DBRS (e.g., RMF package, NIST SP 800-53 controls, Platform IT vs. PIT determination)?

Review SOW para 2.4.1

1. Will Boeing AISF integration documentation and lab interface specifications be made available to offerors?

Integration engineering drawings (i.e pinout and interface tray) will be provided to offerors. ASIP integration will be executed by Boeing, with support from the selected vendor (SOW para 2.5.1).

2. Contract & Evaluation Questions

1. Please clarify the relative weighting of Technical, Past Performance, and Price factors.

CSO will weight Technical highest followed by Past Performance and then Price.

1. Will relevant commercial aerospace data system integration experience be considered acceptable past performance?

The USG would be unable to determine the relevancy of this experience until submission. Commercial experience will be evaluated but additional credit will be applied for experience with DoD Aircraft modifications, DoD Cyber Analysis, and other DoD Tests.

1. Is First Article Testing anticipated beyond the preproduction test units identified in CLINs 0001–0003?

There are no initial testing requirements past the acceptance of CLIN 0001-0003. Production acceptance testing is required.

1. Can the Government provide anticipated production ramp timelines across the ordering periods?

Lot 1 (Aug 27), Lot 2 (Mar 28), Lot 3 (Dec 28), Lot 4 (Aug 29) – Quantities are unknown at this time. An IDIQ contract will be awarded to provided ordering flexibilities. The USG would be interested if economic order quantities exist.

Q1 – Aircraft Data Buses

· Which specific data buses must be recorded (MIL-STD-1553, ARINC-429, EIA-422, Ethernet)?

Review attachment 10 Internal Detail: SRD 1-1

· How many bus channels will be recorded at the same time?

Review attachment 10 Internal Detail: SRD 1-1

· Will the Government provide Interface Control Documents (ICDs) for all buses?

Review attachment 10 Internal Detail: SRD 2.3 publications

· Should the recorder capture raw bus traffic or only decoded parameters?

Review attachment 10 Internal Detail: SRD 1-2

· What is the minimum required data rate per bus?

Review attachment 10 Internal Detail: SRD MIL-STD Documentation

Q2 – Storage Requirements

· How many hours of flight data must the recorder store?

Review attachment 10 Internal Detail: SRD 1-6

· Is continuous recording required, or can it be event-based?

Review attachment 10 Internal Detail: SRD 1-1, 1-2,

· What is the total expected data rate across all buses?

Review attachment 10 Internal Detail: SRD MIL-STD Documentation

· Are there encryption requirements for stored data?

SRD (ATTACHMENT 10) will be updated to remove SRD 5-10 requirement. No encryption is required for data.

Internal Detail: SRD 5-10 DELETED

· Do the removable SSDs need any military qualifications?

The SSD must meet all requirements outlined in the SRD (Attachment 10) Q3 – Installation and Aircraft Interfaces

· Will the Government provide wiring harness pinouts and connector definitions?

Yes. They will shared once they are made available to the USG.

· What are the power input requirements (voltage, transients, MIL-STD-704)?

Review attachment 10 Internal Detail: SRD 2-1 through 2-7

· What is the available mounting space for the LRU?

Review attachment 10 Internal Detail: SRD 6-6 through 6-8

· Are there cooling or temperature limitations for the recorder?

Review attachment 10 Internal Detail: SRD Section 3.3 Environmental Requirements

· Does the vendor supply mounting hardware and installation kits?

The vendor will have the ability to use the existing mounting tray or provide their own. Reference the SRD.

Q4 – Environmental Qualification

· Which environmental standards must the recorder meet (DO-160, MIL-STD-810)?

Review attachment 10 Internal Detail: SRD Section 3.3 Environmental Requirements

· What vibration and shock profiles apply?

Review attachment 10 Internal Detail: SRD Section 3.3 Environmental Requirements, and MIL-STD document table

· Are EMI/EMC tests required (MIL-STD-461)?

Review attachment 10 Internal Detail: SRD MIL-STD document table

· Are lightning or HIRF requirements applicable?

Review attachment 10 Internal Detail: SRD MIL-STD document table Q5 – Data Retrieval and Ground Systems

· Can data be retrieved via Ethernet/USB, or only via removable SSD?

Review attachment 10 Internal Detail: SRD 8-1

· Is in-flight data access required, or only post-flight?

Review attachment 10 Internal Detail: SRD 6-3

· Will the Government provide ground software for data analysis?

No, however data format must meet SRD requirements Internal Detail: SRD 1-8

· Should the vendor provide data conversion or visualization tools?

No, however data format must meet SRD requirements Internal Detail: SRD 1-8

Q6 – Cybersecurity

· Are there NIST 800-171, RMF, or other cybersecurity requirements?

Yes, DBRS will be dealing with Controlled Unclassified Information (CUI) data and must be protected appropriately as well as the various DFARS clauses related to protecting CUI information

· Must stored or transferred data be encrypted?

No, not necessary. If we encrypt the data, it will require something to decrypt it.

· Is secure boot or trusted computing required?

Yes, both will be required. DBRS will be dealing with CUI data and must be protected.

Q7 – Test and Integration

· What level of vendor support is expected at Boeing AISF and flight testing?

Reference SOW para. 2.5.1 and 2.5.2

· Will the Government provide bus simulation tools or test datasets?

No, simulation tools or test datasets will not be provided. The AISF will serve as verification testing before flight test.

· What verification testing is required before flight test installation?

The AISF will serve as verification testing before USG flight test. The primary integrator will be tasked with verifying the selected DBRS meets all requirements in SRD.

· Must the vendor provide integration documentation and test procedures?

Vendor must meet integration and testing requirements outlined in SRD (see attachment 10)

Q8 – Production and Logistics

· What is the expected delivery schedule for fleet LRUs?

Vendors will be required to provide an IMS for production. That will be subfactor two of your written technical proposal. The IMS will be primarily considered in the evaluation process.

· What reliability (MTBF) is required?

Review attachment 10 Internal Detail: SRD section 2.2.1 and SRD 1-2

· Must vendors provide technical data packages or source data?

Yes, the USG intent is to have a Technical Data Package delivered after contract award and finalizing system configuration.

SOW will be updated to reflect this intent.

· Are obsolescence management plans required?

Yes. Reference SOW para. 2.3.9 Q9 – Evaluation Criteria

· Will the Government evaluate technical maturity or existing fielded solutions?

Yes. That information should be provided in your written proposal.

· Are modular or scalable architectures preferred?

USG requires further clarification on intent of question.

· Will COTS recorder architectures be considered acceptable?

Yes, if it meets all SRD requirements.

Q10 – Program Schedule

· When will the final RFP be released? What is the expected award timeline?

Q 26- Please provide the Government’s anticipated acquisition timeline, including the expected proposal due date, anticipated contract award date, and planned timing of the lead-time event referenced in the delivery schedule.

Under new CSO policy, we are looking to release an official RFP at end of May.

· Technical White Papers will be due 14 days after RFP.

· Invitations into Phase 2 would be expected 30 days after RFP.

· Phase 2 Proposal would be due 14 days after invitation.

· Pitch Days would be within 2 weeks of phase 2 proposal

· Award within month.

90 days from RFP to Award ~10 months after RFP release

· When will first article testing and flight integration begin?

First article testing will begin once performance review units are received by the USG. Flight integration will begin at the conclusion of the AISF. The USG will accept some risk and initiate production procurement once the selected DBRS is validated via the AISF prior to completing USG flight test.

Q11 – Red/Black Data Separation

· Does the DBRS need to physically or logically separate classified (Red) and unclassified (Black) data?

Only unclassified data will be stored on the DBRS/SSD.

· Are there specific DoD or Air Force information security standards that must be followed (e.g.,DoDI 8500, DoDI 8510, or ICD 705/705A)?

Review attachment 10 Internal Detail: SRD Sections 2.2.1 and 2.2.2

· Should separate storage devices or partitions be used for Red vs Black data?

Only unclassified data will be stored on the DBRS/SSD.

· Will the system require cross-domain solutions or encryption mechanisms for Red data handling?

Only unclassified data will be stored on the DBRS/SSD.

· Is data sanitization or controlled media removal required before SSDs are removed or reused?

Review attachment 10 Internal Detail: SRD 5-11 Q12 – C-17 Style Guide

· Should we assume that this data recorder development will adopt an MBSE approach and leverage the existing C-17 style guide?

USG requires further clarification on intent of question.

Q13 – Strict Form-Fit-Function Replacement

· Should we assume a strict form-fit-function replacement? If not, where is there room for deviations from existing mechanical and electrical interfaces?

Review attachment 10 Internal Detail: SRD 6-2 through 6-8 Q14 – Functional and Non-Functional Legacy Units

· Will functional and non-functional legacy units be available for comparative testing and form factor evaluations during the development phase?

As of date, the USG have not procured a databus recorder for their fleet. Therefore, there will be no legacy unit to reference for comparative testing.

Q15 – Preferred Vendors and/or Components

· Are there preferred vendors and/or components that would help reduce risk or impact to certifications?

No preferred vendors and/or components to reduce risk

Q 16 - Can the Government please clarify whether "flight hours" should also include operational hours on ground?

· For this requirement, flight hours includes any period that there is power to the DBRS Q 17 - This implies that the DBRS will stop writing data if storage capacity is reached. Is that the desired behavior?

· Yes, this is the desired behavior.

Q 18 - Does this imply that the DBRS shall have 2 power inputs? Or will the DBRS be installed on a bus with emergency power?

· The DBRS will have only one power input which shall abide by SRD 2-1.

Q 19 - Will alternate 6 pin connectors that appropriately mate with the power connector be satisfactory?

· No.

Q 20 - Does "shut-off" mean power off of the LRU or stopping data recording?

· Power off of the LRU Q 21 - Can the Government clarify the encryption requirements?

· Encryption requirements outlined in Documents, Drawings and Publications, SRD 2.2.2 Q 22 - Can the Government clarify if "volatile memory" should be "non-volatile memory"?

· Volatile memory storage should be sanitized IAW NIST SP 800-53 rev 5 Q 23 - Will alternate 128 pin connectors that appropriately mate with the aircraft harnesses be satisfactory?

· No.

Q 24 - Can the government clarify this requirement and identify where the data will be transferred to?

· Data transfer requirements shall meet SRD requirements (SRD 8-1).

Q 27- Can the Government specify inspection and acceptance provisions for production deliveries? CLINs X004-X006 are production CLINs and will be inspected and accepted by awardee's DCMA office. The specific DCMA location will be provided once contract is awarded. The inspection and acceptance are guided by RFO 52.212-4(b).

Q 28- Will the Government consider FOB Origin for all CLINs? FOB Origin is more in line with commercial organization practices and allows for small businesses to more easily recognize revenue. If not, how should potential offerors address the cost of transportation included in the pricing spreadsheets? No, FOB cannot be Origin for all CLINs. There will be no evaluation of transportation costs for FOB Origin. FOB Destination costs shall be included in the FFP. All production will be FOB Origin and the bulk of shipping costs.

Q 29- Several of the Special Clauses have “Deviation” listed but no actual deviation number next to them. Can the Government provide the specific deviations to be used? This is due to the Revolutionary FAR Overhaul (RFO) as part of the President’s Executive Order. Currently all RFO clauses are deviations for now. See link for more information: https://www.acquisition.gov/far-overhaul and https://www.acq.osd.mil/dpap/dars/dfars_far_overhaul_class_deviations.html

Further, will the Government consider tailoring FAR 52.212-4 to be more in line with commercial practices and so they align/do not conflict with the specifications and requirements. Specifically, tailoring should pertain to inspection/acceptance, indemnities, risk of loss, title, and warranty areas. Yes, clauses could be tailored to align commercial practices and specific requirements. The USG would need specific instances as we are unaware of any conflict with specification of requirements. The other areas that are not dealing with requirement or specification are written to be so broad at RFO level as to no conflict with commercial requirements.

Q 30- Will Contractors be required to respond to a USG RFQ or RFP before issuance of delivery or task orders, due to fluctuating quantities?

The purpose of the RFP is to award a single FFP IDIQ contract for the pre-production units and the production unit. All prices will be established at award. Orders will be placed against this IDIQ contract.

Further, can a Contractor “no-bid” or turn down an order in accordance with 52.216-19 during the period of performance? A contractor may decline an order under FAR 52.216-19 ONLY IF the order exceeds the maximum order limitations specified in the contract. The contractor must return the order within a specified number of days (usually 5–7 days) with written notice stating their intent not to ship the items and the reasons for declination. In most cases, this would allow the Contractor to negotiated additional lead time for quantities in excess of limitations rather than rejection.

Q 31- What will the IDIQ minimum? Will it be the base amounts described in the pricing sheet? The minimum order is defined clause RFO 52.216-19

(a) Minimum order. When the Government requires supplies or services covered by this contract in an amount of less than __1LO of ASIF- CLIN 0001__, the Government is not obligated to purchase, nor is the Contractor obligated to furnish, those supplies or services under the contract.

CLIN 0001 Lot is defined as “9 LRU, 5 Spare SSD, 2 SSD Adapter” Q 32- Will PIEE have the ability to accept both a .pdf and a Word copy? Or does the Government expect just a Word copy of the technical proposal to be transmitted? Yes, the Procurement Integrated Enterprise Environment (PIEE) application supports both PDF and Microsoft Word document formats.

In what format does the Government wish to receive the Subfactor Two Integrated Master Schedule - can it be screenshots of MS Project or other graphical views included within the MS Word copy?

· It is anticipated that at least PDFs of schedule will be required at minimum.

Q 33- Given that subcontractors may perform significant portions of the technical scope, will the Government consider allowing relevant past performance information for key subcontractors to be submitted to demonstrate overall team capability?

· Under draft CSO procedures past performance proposal and analysis is much less defined that Source Selection. Additional credit will be applied for experience with DoD Aircraft modifications, DoD Cyber Analysis, and other DoD Tests. The CSO will be limited to 3 efforts which will be left to offers to determine the appropriate submissions and support how it is relevant.

Q 34- Can the Government provide more information on the reserve pool- specifically: (1) approximately how many backup offerors will be entered into the pool and (2) how the Government will evaluate schedule or cost increases during the Final Proposal Request.

· The reserve pool will include all offerors which are invited into Phase 2. Schedule would need to be maintained from original proposal. The only update that will be requested would be for pricing to enable quickest award possible. Evaluation will be redone with only reconsidering price. If unable to maintain schedule proposed, offeror will be un-awardable.

Q 35- If an offeror is successful in making the competitive range for discussions, but then excluded due to the KO and SSA limitations, when does the Government expect that the debriefing time limits start? The debriefing time limits typically start within 3 days of receiving the notice of exclusion, if a pre-award debriefing is requested.

Further, do the same debriefing time limits occur to unsuccessful offerors that are placed in the reserve pool? They are entitled to a post-award debriefing within 3 days of receiving notice of the award. Being placed in Reserve Pool will not affect debriefing.

Q 36- Is the award letter a notification letter sent to unsuccessful offerors, in addition to the initially successful offeror, as well? A written notification is sent to unsuccessful offerors, but it is not the same as the award letter that will be sent to the successful offeror.

Will the rest of the Reserve Pool know who else is in the pool with them? No Q 37- If this is a small business set aside, why are there compliance clauses and requirements for identifying as a large business?

· USG is unaware of Large Business only applicable clause or provisions. Please identify clause or provisions of concern.

Q 38- What certification level is being addressed in these general requirements?

· The contractor must meet all requirements and standards outlined in Attachment 10 Q 39- How will limited, restricted, government purpose, or specifically negotiated license rights markings that are authorized by the contract clauses be handled? Solicitation Clause 252.227-7015 has form/fit/function data or operation/maintenance/training data normally given to the public being required; but the CDRLs and other deliverables ask for further technical data beyond these where the Government would normally have unlimited rights.

· R-DFARS 252.227-7990, Technical Data—Commercial Products and Commercial Services will replace DFARS 252.227-7015

· “limited, restricted, government purpose, or specifically negotiated license” We are not sure of this question. The USG has no intention to negotiation additional license rights under para (d).

· Delivery does not equal to license

· “Except as provided in paragraph (c)(1) of this clause, the Government may use, modify, reproduce, release, perform, display, or disclose technical data within the Government only. “

Q 40- SRD 1-1 What is the transmission speed and data packet size for the 422? We are trying to determine the bandwidth needs. Does the recorder just log the raw packets?

Bandwidth shall be appropriate to cover not just log raw packets but also processing into a compressed format.

Q 41- SRD1-3 Synchronized to what? All signals into the recorder will be synchronized to each other. Is there another source to synchronize the recorder? IRIG?

The intent of this requirement is that all signals into the recorder are synchronized to each other and time stamped. No synchronization to an external source is required.

Q 42- SRD 1-6, 1-9 What happens after 1000 hrs?

When the SSD is full after approximately 1000 hours of recording, the system will stop recording to prevent data loss and will have already indicated that it was approaching its storage limit.

Q 43 - SRD1-7 Are you asking for hot swap while recording?

Yes. SRD 1-7 explicitly states, "The DBRS shall support the removal and replacement of the SSD while powered on without interruption to operations." This defines a hot-swap capability.

Q 44- SRD 5-9 So use SSL FIPS 140-3 level 2 encryption for the data on the SSD as well as data out the front port?

Yes, the SRD requires FIPS 140-3 Level 2 compliance for data transferred via the front panel output.

Q 45- SRD 5-13 What kind of command? HW switch or SW command?

Either method would meet the intent of SRD 5-13 requirement.

Q 46- SRD 6-3 What electrical connection for output interface? Ethernet? USB 3.0?

USB 3.0

Q 47- Attach11 SOW –2.2.5 Support Equipment – ATS – do you need test equipment? If so, how many?

The contractor shall identify, design, or procure and Support Equipment required to operate the DBRS system. The contractor is directed to generate a Support Equipment Recommendation Data (SERD) form for any SE items.

Q 50- What are there CMMC requirements for this effort?

Q 51- Who will be performing the Cyber Security Testing? Gov or Contractor?

The contractor will be required to perform the cyber security testing. The test report shall be delivered via CDRL D016 DI-MGMT-82001A/T Q 52- Will the BOM need to be evaluated for CPI / CT components? Who will perform this activity?

Q 53- Are there any requirements for Single Event Effects while airborne or any references to ARP4761A failure rates regarding Neutron Single Event Upset (NSEU)?

The system shall include resistance to radiation effects covered under MIL-STD-461G Q 48- What is the minimum percentage of work the Small Business must perform?

RFO Clause 52.219-14 Limitations on Subcontracting defines these requirements.

Q 49- Data package rights – does government expect 100% data rights?

R-DFARS 252.227-7990, Technical Data—Commercial Products and Commercial Services defines data rights. USG will take unrestricted license for data that falls within those categories. Most applicable are form fit function data and operations data. The clause also states what the USG will not do. The USG does not need additional license rights outside of what is given in clause.

File details come from the government source that posted it. Updated .