RFP CRM Questions and Answers 2 (28-Dec-2020).xlsx
XLSX spreadsheet 24 KB Posted
- Attached to
- Integration Support Contract (ISC) 2. 0
- Solicitation number
- FA8207-21-R-0001
About this file
This document contains questions and answers related to solicitation number FA8207-21-R-0001 for the Integration Support Contract (ISC) 2.0. The solicitation is seeking systems engineering and integration support services for the Minuteman III and Ground Based Strategic Deterrence weapon systems. Key details include questions from offerors about requirements for labor category pricing, cost estimating methodologies, subcontractor analyses, applicable compliance documents, and page limits for technical factors. The government provides responses to clarify requirements and makes changes to the solicitation terms through amendments.
View the file
Other files
Show all 49
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
Final RFP Questions
| Category | Document Referenced | Pg. No. | Para No. | Text Referenced in PWS (If applicable) | Issue/Comment | Question/Request | Government Response | Action Taken | |
| Cost | Amend. 0001 - Section L | 19 | 6.4 | The Offeror shall provide priced BOEs for each labor category by year to support | |||||
| the cost and COM amounts in the CEWs. | There appears to be a disconnect between Industry's interpretation of a BOE and the Government's interpretation. For Industry, a BOE is a document which details the justification and rational for how a specific task is estimated and substantiates the labor categories, hours per LCAT, and the skill mix (Sr., Mid, or Jr.) required to complete the task. A priced BOE takes this estimate or LCATs, hours and skill mix and applies the appropriate labor rates and burdens to come up with a price for the BOE. Industry doesn't know how to respond to the requirements of 6.4.1 and 6.4.2 because based on our understanding of BOEs, we did not create the BOEs and the BOE output is provided in the RFP. | ||||||||
| It appears the Government has a different interpretation of a BOE. | Based on Industry's understanding of BOEs, Section L paragraph 6.4 and all subparagraphs do not apply to this acquisition. Please remove the requirements in paragraph 6.4 including all subparagraphs or provide a detailed definition and example of the type of information the Government is seeking as the priced BOE. It is recommended that the government provide a standard template or format for BOEs to aid the government evaluation. | Section L paragraph 6.4 and subparagraphs have been written to clarify what the government is requiring in the BOE from industry for this portion. | Section L paragraph 6.4.1 and 6.4.2 have been updated and will be released in amendment to the solicitation. | ||||||
| Cost | Amend. 0001 - Section L | 20 & 21 | 6.8.3.1 and 6.8.3.3 | The Offeror shall explain the methodology used to estimate each cost |
element.
The Offeror shall provide the following information for each cost element:
| Past Experience-Based Estimates | There appears to be a disconnect between Industry's understanding of an estimating methodology and past experience-based estimates and the Government's request to provide this information. For Industry, the estimating methodology is the process followed to generate the estimates and is detailed in the BOE. The process can use parametric, past experience based estimates, Engineering or Subject Matter Expert opinion which generates the expected LCATs, hours per LCAT and skill mix required to perform the task. All of this information is provided in the RFP and offerors are directed to use the provided information as presented. Based on Industry's definition of estimating methodology, it is impossible for Industry to provide an explanation of the methodology used to generate the estimates provided in the RFP Attachment 3 - Labor Quantity Workbook and Attachment 4 - Labor Categories and Qualifications. | ||||
| It appears the Government has a different understanding of estimating methodology. | Based on Industry's understanding of estimating methodology, Section L paragraph 6.8.3.1 & 6.8.3.3 do not apply to this acquisition. Please remove the requirements in 6.8.3.1 and 6.8.3.3 or provide a detailed definition and example of the type of information the Government is seeking as the estimating methodology and past experience based estimates. | Section L paragraph 6.8 has been updated to reflect the Estimating Methodology to help industry better understand the governments request in this area. | Section L paragraph 6.8 has been updated and will be released in amendment to the solicitation. | ||
| Cost | Amend. 0001 - Section L | 21 | 6.8.3.4 | Labor Hour Skill Mix |
6.8.3.4.1. The Offeror shall explain how the proposed labor hour skill mix has been derived for each contract labor category.
6.8.3.4.2. The Offeror shall state if the Offeror’s normal estimating system
| uses a plant-wide average for proposal purposes. | There appears to be a disconnect between Industry's understanding of skill mix and the Government's request to explain how the skill mix was derived. Industry's definition of skill mix includes the various LCATs and grades necessary to complete a task. For example, a Jr. Software Engineer, a Sr. Mechanical Eng. and a Principal Documentation/Technical Writer would be Industry's understanding of the skill mix required to complete a task. It is impossible for Industry to explain how the skill mix found in RFP Attachment 3 - Labor Quantity Workbook was derived because it is provided as part of the RFP. | ||||
| It is apparent the Government has a different understanding of skill mix. | Based on Industry's understanding of skill mix, Section L paragraph 6.8.3.4 does not apply to this acquisition. Please remove the requirements in 6.8.3.4 or provide a detailed definition and example of the type of information the Government is seeking to explain how the skill mix was derived. | This has been removed from section L. | Updated Section L will be released with amendment to the solicitation. | ||
| Cost | Amend. 0001 - Section L | 20 | 6.7.2 | The Offeror shall conduct cost or price analyses of subcontracting costs and |
interdivisional units IAW FAR 15.404-3 and include those results in the Cost/Price
| Volume. | All other requirements within paragraph 6.7 reference major subcontractors but this paragraph does not. | Please confirm offerors are only to submit pricing analysis for major subcontractors. | Section L paragraph 6.7 has been revised to better clarify Subcontractor costs actions. | Updated Section L will be released with amendment to the solicitation. | |||||
| Contract | H004 JCITS | Clause H004 (JOINT CYBER INFORMATION TRACKING SYSTEMS (JCITS)) imposes cyber incident reporting requirements above and beyond those included in DFARS 252.204-7012 and the National Industrial Security Program Manual (NISPOM). Please confirm that these additional reporting requirements apply only to contractor equipment and information systems used to store or process information related to the ISC 2.0 contract.” | Please confirm that these additional reporting requirements apply only to contractor equipment and information systems used to store or process information related to the ISC 2.0 contract.” | Yes, this clause is for information systems and equipment used to store or process information for the ISC 2.0 contract. | Closed | ||||
| Cost | Amend. 0001 - Attachment 23 - Section L | 18 | 6.2.8: LRM-FFPRates Worksheet | The rates on this worksheet will be incorporated into the resulting contract. The Government will use the rates on this worksheet to price FFP CLINs on future contractual modifications/awards. | The RFP does not provide an details on how future FFP task orders will be awarded. | 1. Will all FFP task orders be issued via a bi-lateral modification? | |||
| 2. Will the ISC contractor have the opportunity to negotiate the hours and skill mix of all FFP task orders prior to award? | 1. It is anticipated that all future task orders will issued as bi-lateral orders. 2. By the nature of it being a bi-lateral order the hours and skill mix for the FFP tasks could be negotiated (however the rates are fixed). | Closed | |||||||
| Contract | Section L | 24 | 7.5.8, 7.5.8.1, 7.5.8.2 and 7.5.8.3 | 7.5.8 Applicable Documents |
7.5.8.1. The Offeror shall provide a list of any Offeror, industry, commercial, and tailored Government standards, specifications, processes, and/or practices selected as compliance documents.
7.5.8.2. The Offeror shall also provide a list of all Government compliance documents intended to be used as compliance documents during the course of this contract.
7.5.8.3. The Offeror shall submit a list of these documents, including any tailoring
| instructions, as an annex to the proposed PWS. | The intent of Section L, Paragraph 7.5.8. is unclear. Is it the Government’s intent that an offeror copy and paste the Bidders Library and Attachment 6 (CDRL Listing) as an annex to the PWS along with a statement that an offeror will abide by all Federal, State, Local Laws and Regulations? Or is it the intent of the Government for an offeror to highlight an offeror's internal Governance not currently listed in the Bidders Library or RFP, e.g. an offeror's ISO processes and internal work instructions? | This paragraph and the subparagraphs have been removed from section L. | Updated Section L will be released with amendment to the solicitation. | |||||
| Misc | CRM Q&A (from Government) | Line 63 | The ICBM digital environment continues to evolve. Offerors should suggest tools and processes necessary to illustrate their approach in this scenario. A non-exhaustive summary of commercial engineering software currently used by the MMIII and GBSD is provided and will be added to the Bidder's Library. The Document is identified as: "Commercial Software Tools.docs.docs. File" and it is located in the Bidder's Library. | With all due respect, we cannot find this document in the Bidders Library that we received from you. Can the Government please resend? | Posted document to the Bidders Library. | Reposted document to the Bidders Library. | ||
| L.3.2.4 |
L.3.4
L.4.1 5
9 3.2.4
3.4.4.2
| 4.1 | Will the Government increase the page count for Factor 1 Subfactor 1 Test Anomaly Root Cause from 15 to 20 pages in order to provide the Government with the level of detail against each requirement in Section L needed for a fully-informed decision, given the additional requirements to which offeror's must respond and the use of 1.15 line spacing? | The government will except this request for page increase and has updated section L accordingly. | Updated Section L will be released with amendment to the solicitation. | |
| L.3.2.4 |
L.3.4
L.4.2 5
10 3.2.4
3.4.4.2
| 4.2 | Will the Government increase the page count for Factor 1 Subfactor 2 System Engineering from 15 to 20 pages in order to provide the Government with the level of detail against each requirement in Section L needed for a fully-informed decision, given the additional requirements to which offeror's must respond and the use of 1.15 line spacing? | The government will except this request for page increase and has updated section L accordingly. | Updated Section L will be released with amendment to the solicitation. | |||||
| L.7.5.8 | 25 | 7.5.8 | Seeking guidnance on which specific compliance documents the Government requires. | This paragraph and the subparagraphs have been removed from section L. | Updated Section L will be released with amendment to the solicitation. | |||
| L.3.5.1 L.3.5.2 L.3.9.5 | 6 | A. If a “Volume” is a single document, all attached files need to be embedded in a single Word document as images (in the case of PDFs) or tables (in the case of Excel spreadsheets). That would preclude cross-referencing across files. Reference Section L 3.5.1 and 3.5.2. |
That would mean there would be one file per volume, all-up all-in, except the government-provided Excel spreadsheets would also be included on the CD as separate files in addition to that one file. For example, all the excel spreadsheets for the subcontractor price compare would be included in the Word document as regular tables.
B. If a “Volume” can consist of several files, the prints have to look exactly like the files, but we don’t have to reproduce all file content in the Word document. 3.9.5 appears to allow, or even encourage separate files.
That would mean:
• The all-electronic Cost Volume Word document can reference an Excel document by name but not have to reproduce its contents.
• In the Contract Volume, the PDF files We are seeking clarification regarding the file separation instructions. Is a Volume a single document (like a book) or can it be a number of files on a CD that all belong to that Volume? A volume contains the information for the section or portion of the proposal which can or should consist of several files. Both the print and electronic copies content and page size must be identical per section L paragraph 3.9 therefore content cannot be left out. Closed
File details come from the government source that posted it. Updated .