QA 11JAN thru 15JAN2021.pdf

PDF 104 KB Posted

Attached to
F-16 Brake Control System Redesign (BCSR)
Solicitation number
SPRHA1-21-R-7000
Issued by

About this file

This document contains questions and answers pertaining to solicitation SPRHA1-21-R-7000 for the F-16 Brake Control System Redesign program. The solicitation seeks proposals to redesign the brake control system for the F-16 aircraft to enable continued safe operations throughout the remaining lifespan of the fleet. Offerors must submit all documentation required under Section L of the solicitation, including the RDT, CHR-FF, QDR, CBDR and associated attachments with their initial proposals. The CSDR process requires registration on the CADE website and tailored reporting templates may be proposed post-award. The Performance Specification is currently in clearance and the final version will be distributed to all parties. In total there are 64 documents associated with this solicitation.

View the file

Other files

File Type Posted
Section L_REV04232021.pdf PDF
SPRHA1-21-R-7000-0004.pdf PDF
QA 19APR-23APR2021.pdf PDF
SPRHA1-21-R-7000-0003.pdf PDF
QA 12APR-16APR2021.pdf PDF
Section M_REV04162021.pdf PDF
Section L_REV04162021.pdf PDF
SPRHA1-21-R-7000-0002.pdf PDF
Section L.pdf PDF
F-16_BCSR_(TRD-SOW)_20210329_RevB.pdf PDF
Section M.pdf PDF
SPRHA121R7000_______0001.pdf PDF
QA 01MAR-05MAR2021.pdf PDF
22FEB-26FEB2021.pdf PDF
QA 16JAN thru 11FEB2021.docx DOCX document
CSDR_SOW_20201123.pdf PDF
A001_DID_IMS_BCSR.pdf PDF
A011_CDRL_CDMAL.pdf PDF
C004_CBDR_CDRL_signed.pdf PDF
A011_TDP_CDMAL.pdf PDF
Subcont_Consent.pdf PDF
B001_TDP_PDMAL_AD.pdf PDF
A006_CDRL_PDR.pdf PDF
A005_DID_TP.pdf PDF
F16_BCSR_TRDSOW_20201028_RevA.pdf PDF
A007_DID_CDR_AWS.pdf PDF
A004_DID_ContractorCMP.pdf PDF
A012_DID_SIE_EDDAL.pdf PDF
B001_DID_PDM_DMAL.PDF PDF
C003_CDRL_QDR_signed.pdf PDF
PPISSample.pdf PDF
ClientLtr.pdf PDF
A016_DID_TIR_VACR.pdf PDF
A016_CDRL_TIR_VACR.pdf PDF
B001_DID_CGEP_CSPEI.pdf PDF
A017_CDRL_SSR.pdf PDF
A006_DID_PDR_AWS.pdf PDF
A013_DID_ST_EDDAL.pdf PDF
A010_CDRL_TIR_QTR.pdf PDF
A005_CDRL_TP.pdf PDF
A009_CDRL_TRR.pdf PDF
A003_DID_ConfAgenda.pdf PDF
A012_TDP_SIE_DMAL.pdf PDF
Nongovernmental.pdf PDF
Attachment_0002_ResourceDistributionTable.xlsx XLSX spreadsheet
A010_DID_TIR_QTR.pdf PDF
B001_CDRL_PDMAL_AD.pdf PDF
A011_DID_CDMAL_CEDDAL.pdf PDF
SPRHA121R7000.pdf PDF
Attachment_0001_DD2794_CSDR_Plan.xls XLS spreadsheet
Show 40 more

Latest 50 of 78 listed here. See the rest on GovTribe.

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

Questions & Answers: 11JAN2021-15JAN2021 (13:30 MST)

Question:

To clarify, CDRL A015, does not have a corresponding DID?

Answer:

Correct. Please note block 4 of CDRL A015 lists the DID as “N/A.”

Question:

The addition of CSDR is the main differentiation from the draft RFP. Do all of the documents (RDT, CHR- FF, QDR, CBDR, and attachments) need to be submitted at the time of proposal?

Answer:

Yes. All documents, as indicated in Section L are due with the proposal. Additionally, some important take-away(s) from the documents provided are:

1) As indicated in the CDRLs; registering with the CADE website (https://cade.osd.mil/support/events) is part of the CSDR process. This site also has contact information that may be useful in developing the required documentation:

CADE Help Desk:

(253) 564-1979 Ex. 2 CADESupport@Tecolote.com

2) As indicated in the CSDR SOW; tailored reports may be submitted; however, approval takes place at the post-award conference. Hence, Section L statement “individual packages will not be a part of the evaluation process.” I would refer you to the above website if you would like additional information regarding completing/tailoring CSDR documents, or details that are specific to CSDR outside of this requirement.

3) Lastly, we are more than happy to help with any questions, however, we may not be able to directly answer questions regarding CSDR. This means, we may need to include the CADE Support team on specific CSDR question(s) outside of our expertise. CADE Support consists of DoD personnel, however, information given to us by Offerors will not be shared with the CADE Support Office. If a contractor chooses to share information with the CADE Support Office, they are more than welcome to do so. Please email ryan.peacock@us.af.mil and cc michelle.leschke@us.af.mil.

Question:

When will the updated Performance Specification (PS) be delivered? Should we wait for the PS to be updated before we request a copy?

Answer:

https://cade.osd.mil/support/events mailto:CADESupport@Tecolote.com mailto:ryan.peacock@us.af.mil mailto:michelle.leschke@us.af.mil

Please do NOT wait for the updated Performance Specification (PS) to request your copy. The note on the bottom of the “PS_RFP” document is solely to address the fact that “the PS is in the clearance process… The cleared version will be released to all parties, however, the release of this document does not constitute new/updated information.”

Question:

How many documents, in total, are there?

Answer:

There are 64 documents with the Solicitation and all of the controlled and uncontrolled documents/attachments.

Question:

Do we need to request access to historical controlled documentation on RFI(s) or the draft RFP? Would the information be helpful in generating a proposal? Can they be made available?

Answer:

Controlled documents posted with historical RFI(s) & the draft RFP have been updated and incorporated into the controlled Performance Specification (PS). We do not believe the information would be of use in generating a proposal, and might actually be misleading as some of the information is outdated.

Question:

Is there a form, or formal method for asking questions?

Answer:

Please email all questions to ryan.peacock@us.af.mil and cc michelle.leschke@us.af.mil. It is our objective to post questions and answers weekly (as needed) to Beta.Sam. I will also be sending questions, directly via email to those that responded to the RFP. Questions pertaining to individual proposals, that may be considered proprietary information or specific to an individual Offeror/proposal, will not be posted. If an Offeror feels a question contains such information, they are encouraged to notify the Contracting Officer Michelle Leschke, and the Contracting Specialist Ryan Peacock in their email correspondence; however, questions will be screened for this type of information.

mailto:ryan.peacock@us.af.mil mailto:michelle.leschke@us.af.mil

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