QA 01MAR-05MAR2021.pdf
PDF 133 KB Posted
- Attached to
- F-16 Brake Control System Redesign (BCSR) Federal contract opportunity
- Solicitation number
- SPRHA1-21-R-7000
- Issued by
- Defense Logistics Agency Aviation
About this file
This document contains questions and answers related to a solicitation for the F-16 Brake Control System Redesign program. The solicitation is seeking proposals to redesign the brake control system for the F-16 aircraft to support continued operations throughout its remaining service life. The Defense Logistics Agency Aviation is the contracting office listed in the solicitation. Offerors must submit a CSDR package with their proposal outlining their cost and software data reporting approach, and forecast CSDR reporting for the life of the contract. Examples of CSDR templates and guidance are available online from the CADE website. The solicitation number is listed as SPRHA1-21-R-7000 and is available for full details along with pre-solicitation information on SAM.gov.
View the file
Other files for this federal contract opportunity
Show all 50
F-16 Brake Control System Redesign (BCSR) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Questions & Answers: 01MAR-05MAR2021
Question:
C004 refers to the Excel file 1921-3. I downloaded that file from the cade.osf.mil website. Are we to fill out that file and include it in our response?
Answer:
To meet the requirement for CSDR submission at the time proposals are due a submission must adhere to one of the following options:
1. A package submission should provide concurrence that an Offeror will use the established CSDR documents/templates for submittals after award. To do this an Offeror may leave the CSDR documents/templates blank and submit them with their proposal package as a form of concurrence that they will be utilized, or generate a statement that confirms CSDR documents/templates will be utilized.
2. A package submission can also be done in accordance with the CSDR SOW Post-Award Conference (PAC) and Software Data Reporting Conference section, in that, the Offeror plans to satisfy the requirement using Contractor [Offeror] generated documents/templates in a format that:
“- Demonstrates [Describes] how it collects cost data in its accounting system and how that data will be utilized to provide actual cost transactions and minimize cost allocations when preparing CSDR data deliverables.
- Describes how recurring vs. nonrecurring costs are segregated in its accounting system and for the purpose of CSDR reporting.
- Demonstrates [Describes] how the data from its accounting system will be mapped into the CSDR reports required by Attachment 1 - CSDR Plan and associated CDRLs.
- Demonstrates [Describes] the methodologies used for mapping internal cost accounts to the WBS, specifically showing how individual WBS elements and functional element codes will be populated.
- Proposes [Identifies] any changes to Attachment 1 - CSDR Plan in order to tailor the plan to the Contractor [Offeror’s] accounting system, to include any Contractor [Offeror] recommended changes or additions to the WBS elements.
These changes may include adjustments to the submission events and/or submission timelines, particularly in the case of a direct-reporting subcontractor performing against a different delivery schedule than the associated prime contractor.”
The Contractor Generated submission can be actual/tangible alternative documents/templates, or a detailed statement of the systems in place that will provide information in accordance with the CSDR SOW Post-Award Conference (PAC) and Software Data Reporting Conference section as detailed above. Please keep in mind
Contractor [Offeror] generated alternative documents/templates and/or systems should, at a minimum, provide information that is equal to that required by the CSDR documents/templates.
3. Lastly, an Offeror may use a combination of option 1 and 2, in that they may use some CSDR templates in addition to existing Contractor [Offeror] generated alternative documents/templates and/or systems.
Question:
How many years in the future do we need to forecast the CSDR requirement?
Answer:
The CSDR Requirement will continue throughout the life of the Contract.
Question:
C003 and C002 refer to a FlexFile format; from the cade.osf.mil website there are certain data item descriptors, but they do not follow the flow of the associated DI (MI-MGMT-82164, DI-FNCL-82162). Is there an Excel file missing or some kind of front-end application that would present data in a human-readable form? How should an Offeror prepare C003 and C002 in light of the above?
Answer:
Example Cost and Hour Report (FlexFile) and Quantity Data Reports are available on the CADE website here: https://cade.osd.mil/tools/csdr-tools
Scroll to the bottom of the page you will find “For cPet demo files” link. Once downloaded, the example Cost and Hour Report (FlexFile) submission are found in folder “~\cPet Demo_Files_2019\FlexFile- Quantity Demo Files”. A set of Excel files with Part 1, 2, 3 in the title are called the “three part template” and are a human readable deliverable format. The file called “Sample File_FF.zip” has the same data as the Excel files but in the native JSON/FlexFile data model and may require additional software to read.
Empty three part templates (along with training) can be found and download from here:
https://cade.osd.mil/policy/flexfile-quantity
The DIDs for all the CSDR deliverable formats can be found here: https://cade.osd.mil/policy/dids
Please keep in mind, that while CSDR packages must be a part of the proposal, individual packages will not be a part of the evaluation process. CSDR is a new requirement for DLA requirements, such as the F- 16 BCSR; therefore, the CADE (CSDR) Office will work with the successful Offeror. The important factors regarding CSDR are that an Offeror has an individual CSDR package (plan), and it is forecasted in the proposal.
Question:
https://cade.osd.mil/tools/csdr-tools https://cade.osd.mil/policy/flexfile-quantity https://cade.osd.mil/policy/dids
The retrofit start date in the SOW schedule shows a retrofit start @ T0 + 53 months. The first delivery for Item 0005AA in the Contract is requested in Oct 2023. Could you please clarify the difference between these two dates?
Answer:
The intent is to exercise Option 2 on Oct 2023 per the solicitation; that is not the delivery date.
Question:
Please confirm that the DID content is intended to be identical for documents A002, A006 and A007? If so, where can we find more details about the Reviews expectations?
Answer:
The DID for those CDRLs is intentionally the same. The minimum review requirements are established per the contract, SOW, and CDRL/DIDs.
Question:
Please confirm that sections A to K of the SF1449 are pages 1 to 88 of the PDF document reference
“SPRHA121R7000”?
Answer:
Correct, pages 1-88 constitute A-K; the remaining pages are section “L” and “M,” which do stipulate important submittals, however they do not have the “fill-in” requirements seen in A-K.
File details come from the government source that posted it. Updated .