Pre Solicitation RFI Matrix 2026.xlsx
XLSX spreadsheet 80 KB Posted
- Attached to
- UPDATE ** DRAFT Solicitation for COMET Defense Intelligence Agency Missile and Space Intelligence Center
- Solicitation number
- HHM40225RCOMET
- Issued by
-
Defense Intelligence Agency
About this file
This is a Pre-Solicitation RFI Matrix containing questions and answers addressing the Draft Request for Proposal (RFP) for the Contract Operations for Missile Evaluation and Testing (COMET) program. The Defense Intelligence Agency's Missile and Space Intelligence Center (MSIC) anticipates releasing a final RFP in December 2025 for a multiple award Indefinite Delivery/Indefinite Quantity (IDIQ) contract with a ten-year potential ordering period (five-year base plus one five-year option). The estimated ceiling for the entire ten-year ordering period is $14,088,291,226. The contract will support research, development, and sustainment of hardware, systems, and software capabilities across multiple functional areas including Scientific & Technical Intelligence, Foreign Materiel Exploitation, IT Operations, and Modeling & Simulation. Supporting task orders may utilize various contract types (Time and Materials, Cost-Plus Fixed Fee, and Firm-Fixed Price) determined on a case-by-case basis.
The Q&A matrix addresses critical requirements across security, personnel, facilities, proposal formatting, and evaluation criteria. Key qualification requirements include: Other Than Small Business (OTSB) contractors must maintain at least 50 SCIF workstations with facility clearance (25 within 180 miles of Redstone Arsenal), while Small Business contractors require a minimum of five accredited SCIF workstations. Joint ventures must meet full SCIF requirements under either the small business or OTSB track. The Government intends to award IDIQs to all "Qualifying Offerors" meeting minimum requirements, with 20 percent of total awards reserved for small businesses. Small business subcontractors must perform a minimum of 30 percent of total contract value (with specific percentages for disadvantaged, women-owned, service-disabled veteran-owned, and HUBZone categories). The solicitation employs a streamlined evaluation approach with no cost realism analysis at the IDIQ level; price will not be an evaluation factor, though fair and reasonable pricing must be demonstrated. High Bay facility specifications were removed and will be defined at the task order level. Proposals must comply with strict formatting requirements (30-page limit for technical volume, 12-point Times New Roman font throughout) and include separate submission volumes for administrative, security, technical/management capability, past performance, and small business participation information.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| COMET DRAFT Solicitation Part 1.pdf | ||
| COMET DRAFT Solicitation Part 2.pdf | ||
| RFI Matrix.xlsx | XLSX spreadsheet | |
| COMET DRAFT Solicitaion.pdf | ||
| Opportunity for Small Business Participation in COMET.pdf | ||
| Response Letter Industry COMET.pdf | ||
| UPDATED Sources Sought.pdf | ||
| UPDATED-COMET Sources Sought RFI.pdf | ||
| COMET Sources Sought RFI.pdf | ||
| DRAFT Section L.pdf | ||
| RFI Matrix28MAY2025.xlsx | XLSX spreadsheet | |
| DRAFT Section M.pdf | ||
| DRAFT PWS-COMET.pdf |
Show all 13
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
All Questions
| Type | Paragraph / Section | Responsible Office | Question / Comment | Response | Document |
| Select from drop down | If applicable | For Response | Adjudication | ||
| General | 6.4 | PM/Contracting | Section 6.4 pertaining to joint ventures states "The Offeror must demonstrate that the Offeror's team has at least one SCIF." This seems less rigorous than SB requirements in section 5.2.1.2. Are JV's required to comply with section 5.2.1.2 or are SB requirements changing? | The Government clarifies that there is an inconsistency in the cited language, and Joint Ventures (JVs) ARE required to meet the full SCIF requirements of Section 5.2.1.2 (if small business JV) or Section 5.2.1.1 (if other than small business JV). |
| The Offeror must demonstrate that the Offeror's team has at least one SCIF meeting the requirements of PWS Section 5.2.1.1 (for OTSB) or PWS Section 5.2.1.2 (for Small Business). | Section M 6.4 corrected | |||||
| General | 5.2.1.1 | PM | Will any credit be given to small business teams that have applicable high bay facilities? | High Bay specifications were removed and specific requirements willl be defined as needed at the TO level | No Change | |
| General | J.5 | SST | The security questionnaire J.5 specifies that a high-bay should have 10,000 square feet of high bay space and 2,000 square-feet of office space. Is it necessary that these be attached, or is co-located, or within reasonable driving distance acceptable? | High Bay specification were removed and specific requirements willl be defined as needed at the TO level | PWS Edited | |
| PWS | Appendix 1: Labor Categories and Qualifications, section 1.3 Mid. | SST | For the Mid-level, is there a specified additional (total years) experience in a specific labor category that may substitute for a bachelor’s degree? |
For a junior, the SOW states, “An additional four years of experience in the specific labor category, for a total of seven years of experience in the specific labor category, may be a substitute for a bachelor’s degree.” For a senior, the SOW states, “…or have bachelor’s degree related to the labor category from a college or university accredited by an agency recognized by the U.S. Department of Education and an additional five years of related senior experience, for a total of 17 years, as a substitute to the master’s degree.”
There are no similar criteria for a Mid-Level analyst.
| The LCAT Level was revised and the below was added to the description: | |||||
| An additional four years of experience in the specific labor category, for a total of 12 years of experience in the specific labor category, may be a substitute for a bachelor’s degree. | SOW revised | ||||
| Section M | Section L, page 7/22 and Section M in total. | SST/PM | Section 3.6.1 states, “A program manager is the only "Key Personnel” Identified at the IDIQ level.” Section L, page 7/22, has the Key Personnel (KP) Resume as part of the Administrative Volume. The KP Resume is not listed in Section M of the evaluation factors. Will the KP Resume be evaluated and if so, by what factor(s)? | The Key Personnel resume IS evaluated. |
| Offerors must ensure their proposed Program Manager clearly meets or exceeds Senior Program Manager qualifications and provides a strong commitment to serve for the contract period. | No Change | |||||
| Section L | Budget | Contracting | Are there specific cost elements that must be detailed in the pricing proposal? | At the IDIQ level, Offerors are NOT required to submit detailed pricing proposals. Per Section M, Paragraph 1.1.4, "price will not be an evaluation factor for this solicitation." However, Volume 0 must include pricing-related information for Step 2 (Fair and Reasonable Pricing determination) | No Change | |
| Section M | Budget | Contracting | What level of cost realism analysis will be conducted during evaluation? | No cost realism analysis will be conducted at the IDIQ level. Per Section M, Paragraph 1.4, "price will not be an evaluation factor for this solicitation." The Government will only determine whether there is reason to believe the Offeror would likely offer other than fair and reasonable pricing (Step 2 evaluation) | No Change | |
| Section L | Budget | Contracting | Is there a target budget or ceiling for this solicitation? | Estimated ceiling for the 10 year ordering period is $14,088,291,226 | No Change | |
| Section L | Communication | PM/Contracting | Will there be a debriefing process for unsuccessful bidders? | See Section L Para. 2.2 | No Change | |
| Section L | Communication | PM/Contracting | How will the agency communicate updates or changes to the solicitation? | See Para 2.1.8 | No Change | |
| Section L | Contract Structure | PM | What is the anticipated contract type (e.g., fixed-price, cost-plus, time-and-materials)? | The IDIQ base contract establishes multiple contract types that may be used at the task order level. Individual task orders will be issued using the contract type most appropriate for the specific requirements of that task order. | No Change | |
| Section L | Contract Structure | PM | What is the expected period of performance and are there options for renewal? | The anticipated period of performance is: |
Base Ordering Period: 5 years Option Ordering Period: 1 additional 5-year period Total Potential: 10 years
| These are ordering periods during which the Government may issue task orders. Individual task orders will have their own performance periods as specified in each task order solicitation. Task order performance may extend beyond the IDIQ ordering period for task orders issued before the ordering period expires. | No Change | ||||||
| Section L | Contract Structure | SST/PM | Are there any specific reporting or deliverable submission requirements during the contract period? | Yes. Reporting and deliverable requirements are defined at two levels: (1) IDIQ-level reports required for contract administration, and (2) Task Order-level deliverables that will be specified in individual TO Performance Work Statements. | No Change | ||
| Section M | Evaluation Criteria | SST/PM | What level of detail is expected in the technical approach section? | The technical approach in Volume II - Technical/Management Capability is limited to 30 pages and must provide sufficient detail to demonstrate that the Offeror clearly understands and has the depth and breadth of expertise to perform COMET requirements. | No Change | ||
| Section M | Evaluation Criteria | SST/PM | What are the primary evaluation criteria for this solicitation (e.g., technical merit, past performance, cost)? | See Section M | No Change | ||
| Section M | Evaluation Criteria | SST/PM | How will proposals be scored or weighted across the different criteria? | See Section M 2.1.4 | No Change | ||
| Section M | Evaluation Criteria | SST/PM | Are there specific differentiators the agency is looking for in a winning proposal? | This is a qualification-based procurement where the Government intends to award IDIQ contracts to ALL "Qualifying Offerors" who meet the minimum criteria—there is no competitive "winning" proposal selection at the IDIQ level. | No Change | ||
| PWS | Geographic Scope | DIV REPS | What are the expectations for worldwide deployment or rapid response capabilities? | SEE PWS Para. 2.1 | Geographic Scope | No Change | |
| PWS | Geographic Scope | DIV REPS | Are there specific geographic locations or operational environments where services will be required? | See PWS Section 2.1: |
| No Change | ||||||
| Section M | Past Performance | Contracting | Can past performance from subcontractors or teaming partners be included? | Yes | No Change | |
| Section M | Past Performance | SST/PM | What types of past performance examples are most relevant to this solicitation? | The most relevant past performance examples demonstrate experience delivering services similar in scope, scale, and complexity to COMET requirements in multi-level security, multi-customer intelligence environments. | No Change | |
| Section M | Past Performance | SST/PM | Are there specific formats or templates for submitting past performance information? | See Section L4.4 | No Change | |
| Section L | Personnel | DIV REPS | Are there specific qualifications or certifications required for key personnel? | Per PWS Section 3.6.1.1, the IDIQ Program Manager shall, at a minimum, possess the qualifications of a Senior Program Manager as outlined in PWS Appendix 1. | No Change | |
| Section L | Personnel | SST/PM | What is the agency’s expectation for staffing levels and surge capacity? | This will be defined at the Task Order Level | No Change | |
| Section L | Personnel | SST/PM | Are there any restrictions on hiring or onboarding personnel for this contract? | Yes, there are several restrictions and requirements that affect hiring and onboarding of personnel for COMET. These restrictions relate to security clearances, labor category qualifications, Key Personnel Requirements, organizational conflicts of interest, Government employee hiring limitations, and facility access requirements. | No Change | |
| Section M | Post-Award | PM | Are there opportunities for follow-on work or additional task orders? | Yes | No Change | |
| Section M | Post-Award | PM/Contracting | What is the process for contract modifications or scope changes? | Contract modifications and scope changes follow different processes depending on whether changes affect the IDIQ base contract or individual Task Orders. Only the Contracting Officer has authority to modify the contract. | No Change | |
| Section M | Post-Award | SST/PM | What are the key performance indicators (KPIs) or metrics for success during contract execution? | Key Performance Indicators (KPIs) and metrics for success will be established at both the IDIQ level and Task Order level, with IDIQ-level metrics focusing on overall contract management and TO-level metrics focusing on specific technical performance and deliverables. | No Change | |
| Section L | Risk | PM | What are the biggest risks or challenges the agency foresees in executing this contract? | This IDIQ spans diverse functional areas—Scientific & Technical Intelligence (S&TI), Foreign Materiel Exploitation (FME), IT Operations, and Modeling & Simulation (M&S)—that require different expertise, facilities, and approaches. | ||
| Our requirements are unpredictable and time-sensitive. | No Change | |||||
| Section L | Risk | SST/PM | Are there specific risk mitigation strategies the agency expects to see in the proposal? | Yes, while the IDIQ-level proposal does not require a formal risk management plan, the Government expects offerors to demonstrate understanding of key risks and articulate credible mitigation approaches across multiple areas. Risk considerations are embedded throughout the evaluation factors, particularly in Factor II: Technical/Management Capability and the OCI Management approach. | No Change | |
| PWS | Scope | SST/PM | Are there specific deliverables or milestones that must be included in the proposal? | The Government does not dictate specific deliverables or milestones that must be included in the proposal. Instead, we encourage offerors to tailor their proposals to meet the evaluation criteria as they see fit. This allows for flexibility and creativity in addressing the project requirements while ensuring alignment with the Government's objectives. Offerors should consider their unique capabilities and insights when defining the deliverables and milestones that they believe will best meet the needs of the project. | No Change | |
| PWS | Scope | SST/PM | What are the most critical technical capabilities or areas of expertise the agency is prioritizing? | The agency values a balanced approach to technical capabilities and areas of expertise, as all evaluation criteria are weighted equally. This means that while there are no single critical areas prioritized over others, we appreciate a comprehensive proposal that demonstrates proficiency across all relevant technical domains. Offerors should focus on showcasing their strengths in each criterion, providing a well-rounded perspective that aligns with the agency's objectives. | No Change | |
| PWS | Scope | SST | Are there any specific tools, methodologies, or technologies the agency prefers or requires? | For the IDIQ, MSIC welcomes vendors to present their expertise using various tools, methodologies, and technologies that could help meet the PWS requirements across MSIC Missions, Domains, and Disciplines. Individual Task Orders may require use of specific tools, methodologies, and/or technologies. | No Change | |
| Section L | Security | PM/Contracting | Are there any restrictions on subcontracting or teaming arrangements? | Yes, there are several mandatory requirements and restrictions listed in the RFP. | No Change | |
| Section L | Security | Security | What security clearance levels are required for personnel working on this contract? | See SOW Para. 5.2 | No Change | |
| Section L | Security | Security | Are there specific compliance requirements (e.g., DoD Directive 8570.1, COMSEC, IA) that must be addressed? | See Appendix 4 of the SOW | ||
| Section L | Submission | PM/Contracting | What is the deadline for submission, and are there any extensions possible? | This will be Identified when the Final RFP is released. | No Change | |
| Section L | Submission | PM/Contracting | What is the process for submitting questions or clarifications during the solicitation period? | See Section L Para. 2.1 | No Change | |
| Section L | Submission | SST/PM | Are there specific formatting requirements (e.g., page limits, font size, file types)? | See Section L Para. 3.4 | Section 3.4 was edited to allow different font in certain circumstances | |
| Section L | Submission | SST/PM | Are there specific templates or forms that must be used for the proposal? | Yes. Templates and forms will be attached the the RFP | ||
| MSIC Missions | 1 | SST | Which COTS and GOTS software will require IT operations management? | There are numerous COTS and GOTS software applications across multiple networks that require IT operations management. Offerers should refer to the PWS as well as Section M of the RFP to articulate their expertise with software administration that will meet MSIC mission objectives. | No Change | |
| MSIC Missions | 1 | SST | Will MSIC require cross-domain or cross-program data-integration support for T&E, Modeling, Intelligence, Hardware evaluation, and legacy data? | Yes | No Change | |
| MSIC Missions | 1 | SST | Does MSIC encourage or require use of “digital twin” or “digital thread” workflows for modeling & simulation tasks under COMET task orders, consistent with 2025 GAO recommendations? | MSIC is currently formulating its approach to addressing digital engineering and model-based systems engineering (MBSE) initiatives within the DoW. | No Change | |
| MSIC Missions | 1 | SST | Will MSIC clarify whether it favors extensible modern modeling workflows (Python, AFSIM, STK, OpenFOAM) versus legacy or Government-furnished toolchains? | MSIC will utilize a "best of breed" approach to meeting its mission requirements, whether that is legacy tools or recent developments. Offerors should address their unique expertise of tools and methodologies to address the MSIC Missions, Domains, and Disciplines. | No Change | |
| MSIC Missions | 1 | SST | Will MSIC provide guidance on COOP requirements for contractor-supported mission activities, including expectations COOP testing, failover access, or redundancy requirements? | Yes, this will be completed at the TO level. | No Change | |
| MSIC Missions | 1 | SST | Does MSIC currently use any Government-approved LLMs or AI models (such as Ask Sage, NIPR GPT, SIPR/JWICS-deployed models), and will contractors be expected to only utilize those models? If so, what restrictions apply regarding prompt content, data retention, model training boundaries, and external network access? | This will be determined at the Task Order level depending on specific requirements and current technical capabilitiies and access restrictions. In general, as users of Government networks, contractors will have access to all services provided by those networks, including LLM services, if they have approval based on mission needs. There is no general expectation that a contractor use a specific service, at this time. However, it is possible that a Task Order could specify a specific service to use. | No Change | |
| Section M | 1.5 | PM | Can more details please be provided about the definition of "discretion"? | In the context of this solicitation, "discretion" means the Government's judgment and authority to make determinations based on what is in the best interest of the Government. This may include, but is not limited to: |
Compliance issues: Eliminating proposals that fail to meet mandatory requirements or submission instructions Competitive range determinations: Advancing only those offerors whose proposals have a reasonable chance of being selected for award Technical capability concerns: Removing offerors who demonstrate insufficient understanding, qualifications, or approach
| All discretionary decisions will be made in accordance with applicable procurement regulations (e.g., FAR Part 15) and the evaluation criteria stated in this solicitation. Offerors will not be eliminated arbitrarily; decisions will be based on documented evaluation findings and the Government's assessment of which proposals are qualified. | No Change | |||||
| Section M | 1.7 | Contracting | Please describe the process for requesting to be readmitted, and is it an automatic award? | Section 1.7 will be revised to expand on the Government 10 Day correction period | ||
| General | 3.6 | PM/Contracting | Is there likely to be other Key Personnel than the program manager? | Not at the IDIQ level | No Change | |
| PWS | 5.2 | Security | What security requirements or provisions are required as flow downs to subcontractors? | Security requirements that apply to the prime contractor generally flow down to subcontractors performing on classified Task Orders. The prime contractor is responsible for ensuring subcontractors meet applicable security requirements and for providing DD Form 254s to subcontractors. | No Change | |
| PWS | 1.1.2 | SST | What compute resources (GPU/CPU clusters, storage) will be available for high-fidelity radar/EW simulations? | This will be determined at the Task Order level depending on specific requirements. In some cases, the contractor may have access to the MSIC HPCS and other MSIC networks/labs, or may be required to utilize computing resources on external Government networks as well as contractor facilities. | No Change | |
| PWS | 1.3.1 | SST | Is MSIC expecting industry to develop new seeker-tracking models (e.g., advanced Kalman filters, AI-based trackers) or only analyze foreign implementations? | The two are not mutually exclusive. Foreign threats are developing new advanced tracking models. Since the MSIC mission is to assess foreign system capabilities, the primary focus is on potential R&D for those systems. | No Change | |
| PWS | 1.3.10 | SST | What is the required accuracy and confidence level for emitter parameter extraction used in MIDB/MARS updates? | MSIC uses a wide variety on intelligence sources to make these assessments. The confidence level and accuracy will vary greatly depending upon the sources used to make the assessment. | No Change | |
| PWS | 1.3.10 | SST | Will contractors receive access to raw OpELINT, ISR, GEOINT, and TECHINT used to validate radar order-of-battle entries? | The intent is for the Government to provide all of the available intelligence data that we can to support high-fidelity modeling. In some cases, raw data will not be provided; however, reports describing the raw data will be made available. | No Change | |
| PWS | 1.3.13 | SST | Which radar/EW problem areas does MSIC view as highest priority for ML innovation—classification, fusion, anomaly detection, or waveform optimization? | All of these areas are important and need to be individually addressed. | No Change | |
| PWS | 1.3.2 | SST | What raw radar data (I/Q, waveform captures, etc..) will be government-furnished to support high-fidelity modeling of foreign air defense radars? | The intent is for the Government to provide all of the available intelligence data that we can to support high-fidelity modeling. In some cases, raw data will not be provided; however, reports describing the raw data will be made available. | No Change | |
| PWS | 1.3.2 | SST | What level of fidelity is expected for modeling digital beamforming, advanced signal processing, and conventional/unconventional radar waveforms used by foreign GBADS? | For high fidelity applications, the modeling of digital beamforming, advanced signal processing, and conventional/unconventional radar waveforms will need to be performed at a detailed level to ensure the radar can respond to electronic attack in a threat faithful manner. For lower-fidelity applications, a more coarse representation can be taken to capture the “effects” of jamming. | No Change | |
| PWS | 1.3.2 | SST | Does MSIC expect contractors to propose novel EP/EA techniques, or is the scope limited to characterizing foreign-system capabilities? | MSIC’s goal is accurately characterize threat weapon systems consistent with the design philosophies of the foreign developer. Therefore, any novel EP techniques need to be consistent with the foreign designer’s philosophy on counter jamming. | No Change | |
| PWS | 1.3.2 | SST | Are cross-domain models (e.g., radar to seeker guidance to EO/IR cues) desired for tasks under 1.3.2: Ground-Based Air Defense Systems? | To accurately represent a ground-based threat, any weapon system model must properly represent the sensors employed with the system regardless of domain they operate in (i.e. RF, EO/IR, laser, ..) and be consistent with the concept of operations. | No Change | |
| PWS | 1.3.3 | SST | What specific gaps does the Government see in discrimination, multi-spectral fusion, or complex target deconfliction that industry should address? | MSIC’s goal is to define the specific techniques foreign weapon systems use to address each of these techniques in a threat-faithful manner and consistent with foreign design concepts. | No Change | |
| PWS | 1.3.3 | SST | Will existing government BMD threat models be provided, or must contractors develop new physics-based models? | This will be determined at the Task Order level depending on specific requirements and model availability. Government-owned BMD threat models may be provided to vendors selected to perform BMD analysis on individual Task Orders. However, vendors should also be prepared to develop new models as required to meet potential Task Order requirements. | No Change | |
| PWS | 1.3.3 | SST | Does MSIC want contractor-developed algorithms for aim-point optimization, or strictly characterization of foreign capabilities? | MSIC’s goal is accurately characterize threat weapon systems consistent with the design philosophies of the foreign developer. Therefore, any contract-developed algorithms need to be consistent with the foreign designer’s philosophy on these topics. | No Change | |
| Section L | 4.1.1.1.1.6 | PM/Contracting | Please detail what is required to to be included in the Key Personnel commitment letters. | This is standard commercial practice. Any offeror with Government contracting experience knows how to produce a commitment letter. Providing templates for routine business documents would be unnecessary and potentially restrictive. |
| The solicitation appropriately assumes offerors possess basic proposal preparation competency, including the ability to generate standard commitment letters without Government-prescribed formats. | No Change | |||||
| PWS | 5.2.1.1 | SST/PM | Would the government consider widening the radius to 400 miles? | No | No Change | |
| PWS | 5.2.1.2 | Security | Please detail what is required to prove that the Prime owns 5 SCIF workstations. | See L 4.2 Security for the requirements | Section 4.2 edited | |
| PWS | Appendix 1 | PM | Appendix 1 outlines personnel with 5 levels of experience. Will the government consider multiple personnel at the same level of experience? | Appendix 1 defines five experience levels to establish minimum qualifications and provide a framework for labor categories that will be utilized at the Task Order Level. These levels do not limit the number of personnel an Offeror may propose at any given experience level. | No Change | |
| Section L | Attachment 1, Past Performance Information | Contracting | Would the government be amenable to offering a fillable version of the form? | The Government will provide fillable versions of the form as necessary. | No Change | |
| Section L | Attachment 2, Past Performance Questionnaire | Contracting | Would the government be amenable to offering fillable versions of the forms for our previous customers for their ease? | The Government will provide fillable versions of the form as necessary. | No Change | |
| Section L | Attachment 3, Subcontractor Consent Letter | Contracting | Would the government be amenable to offering a fillable version of the form? | The Government will provide fillable versions of the form as necessary. | No Change | |
| Section L | Attachment 4, Client Authorization Letter | Contracting | Would the government be amenable to offering a fillable version of the form? | The Government will provide fillable versions of the form as necessary. | No Change | |
| Section L | Attachment 5, Security Questionnaire | Contracting | Would the government be amenable to offering a fillable version of the form? | The Government will provide fillable versions of the form as necessary. | No Change | |
| Section L | Attachment 6, Question Format, L 2.1.7, 2.1.4 | Contracting | 2.1.7 references that Questions should be submitted on Attachment 6. Please consider releasing draft of Attachment 6, or explaining in detail how we will submit questions for the Final RFP. | Instructions will follow in Final RFP. | ||
| SOW revised | ||||||
| Section L | L 3.2; 5.1 | PM/Contracting | Please explain in detail the proposal submission process. | These instructions are in Section L. | No Change | |
| Section L | L 3.2; L 4.5 | PM/Contracting | Under Table L-1, it says the SBPC does not include "Commitment Letters," but there is no guidance in L 4.5 that says "Commitment Letters." Please advise whether the Commitment Letter is the same as the SBPC, or, if a different document, what is required to be in the SBPC Commitment Letters. | The Government has already removed "Commitment Letters" from the Table L-1 note for Volume IV, confirming that: |
No commitment letters are required for Volume IV (SBPC) The reference was an error
| Table L-1 has been corrected | Section L-1 has been Heavily edited for corrections | |||||
| Section L | L 3.8 | PM/Contracting | What is the purpose of the sanitized Copy version of the Proposal? | The sanitized/redacted copy of Volume II serves to enable unbiased technical evaluation by preventing evaluator identification of the offeror during technical assessments. | No Change | |
| Section L | L 4.2.2 | Security | Please consider breaking up the table to account for differences between Prime Offeror and Teammates Facility and SCIF Capabilities. | The prime must provide their SCIF capability to meet the Prime's requirement listed in the SOW. They may also provide the Subcontractors SCIF capability to meet the overall COMET requirement. | ||
| Section L | L 4.3 / 4.3.1.5 | SST/PM | Please confirm if there is further guidance on the organization, formatting, or content requirements for Volume II Factor II: IDIQ Technical/ Management Capability. | No | No Change | |
| Section L | L 4.4.1 | PM/Contracting | Will the Government accept CUI submissions in Past Performance? | Yes. The Government will accept Controlled Unclassified Information (CUI) in Past Performance submissions (Volume III). | No Change | |
| Section L | L 4.4.3 | Contracting | Is there a required number of past performance examples from the Prime? | No. There is no specific minimum number of past performance examples required from the Prime Offeror. | No Change | |
| Section L | L 4.4.4 | Contracting | Will the government accept CPARS in place of PPQs? | The Government will acccept CPARs and PPQs. CPARS will not replace PPQs. | No Change | |
| General | PM/Contracting | Will there be a ceiling on the number of awardees? If yes, how many does the Government anticipate? Will there be separate pools for small and large businesses? If yes, please provide the anticipated number of awardees for both small and large businesses. | No | No Change | ||
| PWS | 5.1 | Contracting | Please confirm that OCONUS Other Direct Costs (ODCs) reimbursement will cover common OCONUS cost reimbursable allowances such as Living Quarters/Housing Allowance, Cost of Living Allowance, Education Allowance, Defense Base Act, Repatriation, Danger Pay, and/or Hardship Pay? Including this language at the IDIQ level will facilitate reimbursement for overseas performance delivery on specific task orders, dependant on location. | The Government cannot provide a blanket confirmation at the IDIQ level regarding specific OCONUS ODC reimbursements, as allowability will be determined at the Task Order level based on specific requirements, locations, and applicable regulations. | No Change | |
| PWS | 3.6.2.2 & Appendix 1 | PM | PWS Section 3.6.2.2 states that the COMET IDIQ requires contractor personnel with four (4) levels of experience, while Appendix 1 lists five (5) experience levels. Can you please clarify this discrepancy? | PWS Section 3.6.2.2 was changed from "4" Levels to "5" levels to agree with the listed number of experience Levels. | PWS Section 3.6.2.2 was edited | |
| Section L | 4.1.1.2.4 | PM | Can the Government please confirm that Section 4.1.1.2.4 "The same information is required for each subcontractor," is referring to 4.1.1.2.2.3 Contact Information, only? | No. Section L 4.1.1.2.4 requires "the same information" as required under Section 4.1.1.2 for the prime Offeror, which includes: |
OCI Statement (per 4.1.1.2.1) - Each subcontractor must provide a statement certifying they have reviewed the SOW/RFP and either identified no OCI or identified an OCI with proposed mitigation
OCI Mitigation Plan (per 4.1.1.2.2) - Only if the subcontractor identifies a potential, actual, or apparent OCI (maximum 5 pages per subcontractor)
Contact Information (per 4.1.1.2.2.3) - All subcontractors must provide the minimum required contact information
Clarification:
All subcontractors must provide an OCI Statement and Contact Information Only subcontractors that identify an OCI need to provide a Mitigation Plan Section 4.1.1.2.2.3.1 already states contact information is required "for the Offeror and each subcontractor (if applicable)" The phrase "same information" in 4.1.1.2.4 refers back to the entire OCI documentation package under 4.1.1.2, applied to each subcontractor at any tier.
| 4.1.1.2.4 was revised for clarity to state: "Subcontractor OCI Documentation: The prime Offeror must provide OCI Statements (per 4.1.1.2.1) for all subcontractors at any tier. If a subcontractor identifies a potential, actual, or apparent OCI, the prime must also include that subcontractor's OCI Mitigation Plan (per 4.1.1.2.2). Contact Information per 4.1.1.2.2.3 is required for all subcontractors." | Section L 4.1.1.2.2.3 and 4.1.1.2.4 was edited for clarification | ||||
| PWS | 5.2.2.2 Existing SCIF | Security | Will our subcontractors need to supply a current SCIF accreditation letter or certificate when they are part of our SCIF or High Bay plan? | Yes, if your subcontractor's SCIF is being used to meet the Prime Offeror's minimum workstation or facility requirements, that subcontractor must provide a current SCIF accreditation letter or certificate. The documentation requirements specified in PWS Section 5.2.2.2 and Section L, Volume I apply to ALL facilities being used to demonstrate compliance with the IDIQ-level security requirements, regardless of whether they are Prime-owned or subcontractor-owned. |
| High Bay specifications were removed and specific requirements willl be defined as needed at the TO level | No Change | |||||
| Section J | Attachment 1 | PM/Contracting | Attachment 1 Past Performance Information asks for any key individuals listed who might be supporting this acquisition to be named. However there is only 1 required KP for the IDIQ (Program Manager) and offerors do not know which TOs will be bid under this IDIQ or which MSIC missions will be covered, and would be unable to name specific personnel at this point. Would the Government consider removing item I? | The Government acknowledges the concern but will NOT remove Item I from Attachment 1. However, the Government will issue clarifying guidance that Item I is OPTIONAL, not mandatory. The actual language in Attachment 1, Item I states: "Specify, by name, any key individual(s) who participated in this program and are proposed to support this acquisition." The use of "any" indicates this is permissive rather than mandatory. Offerors may provide this information if personnel from past performance examples are available and proposed for COMET, but it is not required. | No Change | |
| Section J | Attachment 1 | PM/Contracting | Item M asks for the nature or portion of the work described to be performed by the business entity listed in the qual. As offerors do not yet know which TOs will be bid under this IDIQ, they are unable to identify which portions of future work will be performed by the Prime or its partners for this effort. Would the Government consider clarifying item M or removing it? | The Government will clarify Attachment 1, Item M to make clear that Offerors should describe the nature and portion of work performed by the business entity ON THE PAST PERFORMANCE EXAMPLE being cited, and then explain how that entity's role on the past performance example relates to their anticipated role on COMET. Complete removal of Item M is not happening as it serves critical evaluation purposes for understanding team composition, subcontractor relevance, and organizational relationships. | No Change | |
| Section L | L 1.1.1.2 | PM | Can the Government confirm the highest level of classification that can be accepted for vendor proposal classified Annex? For example, SCI to include ORCON, GAMMA, HCS-P, etc.? | Section L.1.1.1.2 States: | ||
| "Classification: The Government anticipates the receipt of UNCLASSIFIED proposals in response to this solicitation; however, if the Offeror believes any other classification is necessary to present a contractor's past performance and/or approach, a written request must be presented to the Contracting Officer five business days BEFORE proposal due date. If approved by the Contracting Officer, a separate written classified annex may be included in the proposal. This annex may not exceed the classification of TOP SECRET/SCI, and must be delivered appropriately. Failure to adhere to any of the labeling, classification marking, packaging, or other general proposal instructions may cause the Government to reject the Offeror's proposal in its entirety." | No Change | |||||
| Section L | L 4.4.3.2 | Contracting | Will the Government please clarify if there is a specified time prior to the overall submission deadline when the Past Performance questionnaires that will be completed by Government POCs, must be submitted to the Contract Officer? Or, is the deadline expected to be the due date for the overall proposal submission? | The Government clarifies that there is no separate deadline for Past Performance Questionnaire (PPQ) submissions by Government reference POCs. | No Change | |
| Section M & J | M 6.7.2 & Attachment 5 | Security | Attachment 5 does not include a way to provide verification of the High Bay workstation requirements as listed in PWS 5.2.2.1.6. as it only includes the table (Y/N). Will the Government please identify the specific information needed to provide verification of a High Bay SCIF facility, such as CAGE code, floor plans, or self-attestation? Or, will filling out the Security Certification Questionairre for the SCIF portion of the High Bay requirement provide the Government with sufficient information to verify that the High Bay does meet the capability requirements? | High Bay specifications were removed and specific requirements willl be defined as needed at the TO level | SOW Revised | |
| PWS | PWS 4.1.2 | PM | Does the Government intend for Status Reporting to be only applicable to Task Orders? | Status reporting requirements exist at both the IDIQ and task order levels, but serve different purposes: |
IDIQ-Level Reporting (Administrative):
The following reports are required at the IDIQ contract level covering all task order activity:
Small Business Participation Reporting (Deliverable A007) - semi-annually Individual Subcontracting Reports (OTSB only, via eSRS per FAR 52.219-9) - semi-annually and annually [Any other IDIQ-level reports in your deliverables list] These reports cover the IDIQ contract as a whole, not individual task order technical performance.
Task Order-Level Reporting (Technical Performance):
| Status reporting on technical progress, schedule, deliverables, risks, and issues will be specified at the task order level. | No Change | |||
| PWS | PWS 5.2.2.2 | Security | Will the Government please clarify in which Volume offerors should include the required SCIF verification documentation listed in PWS 5.2.2.2 - 5.2.2.2.4.3 (Existing SCIF)? These requirements are not captured in Table L-2, the Security Certification Questionairre, or in the Page Requirements listed in L-1 (ex: security audits can be > 20 pages). |
| If the Government includes the above referenced response requirement in the Security Volume, will the page count be increased accordingly, or will the docuementation not count towards the stated page count for Factor I: Security? | The Government clarifies that all SCIF verification documentation required by PWS 5.2.2.2 through 5.2.2.2.4.4 shall be included in Volume I - Factor I: Security, and this supporting documentation does NOT count against the 3-page Security Volume limit. | Section L-1 has been edited for corrections | ||||
| Section J | Section J Attachment 1 and Section L 3.2 | PM/Contracting | Attachment 1 is limited to 4 pages per example. However the Attachment itself is already 3 pages before any information is provided. Can the Government provide clarity on how the page count is determined, or increase the page count to 5 accommodate complete answers to the questions? | The Government will NOT increase the page limit for Attachment 1 from 4 pages to 5 (or 6) pages per example. | No Change | |
| Section L | Section L 1.1.1.2 | PM/Contracting | Would the Government please clarify, if the Contracting Officer approves submission of a classified annex, how the classified annex counts against the page count requirements? | The solicitation does NOT establish a separate, additional page limit for classified annexes. Classified content must fit within the existing page limits for each volume. Section L.3.10.1 states: 'Volumes I-III may include classified information up to the TOP SECRET Sensitive Compartmented Information (SCI) level.' This means classified content is PART OF Volumes I-III, not separate from them. | No Change | |
| Section L | Section L 2.0 | Contracting | Would the Government please clarify what coordination for proposal delivery and submission of abstract entails? In addition, will the Government provide requirements or a template for the Abstract? | Delivery Coordination- See Para. 5.2. Abstract attachment and Format will be provided with the Final RFP. | No Change | |
| Section L | Section L 3.5 | PM | Section L.3.5 does not include font size or style. Will the Government please clarify if there are further formatting requirements for graphics regarding font size, font type, and other characteristics? Or, if vendors are allowed to use any font size or style so long as it's clearly legible and easily interpretable on standard screen resolutions? | The font is rquirement is specified and does not change. | No Change | |
| Section L | Section L 4.5.2.1.1 | Contracting | Section 4.5.2.1 states that Offerors shall clearly articulate how they will meet the following mandatory requirements. 4.5.2.1.1 states "30% of total proposed contract or subcontracted value shall be performed by small business firms" There is no total proposed contract value listed in the solicitation. Can the Government please confirm the requirement? | Estimated ceiling for the 10 year ordering period is $14,088,291,226 | No Change | |
| Section L | 3.11 | Contracting | Are hyperlinks allowed? | Hyperlinks will be provided in the solicitation, specifically for referencing external documents, clauses, government websites, providing access to specific information etc. Proposals shall not have hyperlinks, information form the hyperlink will not be evaluated. | No Change | |
| Section L | 3.13 | PM/Contracting | What is the definition for "index" so that all bidders will be providing consistent responses for consistent evaluation and to ensure compliance with the intended requirement? An example would be appreciated to remove any ambiguity regarding interpretation. | Index refers to a detailed table of contents that must be included in each proposal volume. | No Change | |
| Section L | 3.13 | PM/Contracting | Is indexing a true link or does this requirement just relate to the TOC? | The solicitation uses the term "indexing" to describe a detailed table of contents with page numbers, not interactive hyperlinks or embedded navigation features | No Change | |
| Section L | 3.17 | PM/Contracting | If content is only unclassified or CUI, is portion marking required at the paragraph level? In order for these paragraph headings to be captured in the TOC, formatting will result in tremendous loss of page space. | Section L, Para 3.17 (Classification Markings): |
"All material submitted for evaluation by the Government, including electronic media, must be appropriately classified and marked per Government security classification guidance."
"Portion marking is required for all materials."
| This applies to all submissions, including unclassified and CUI content. | No Change | |||||
| Section L | 5.2 | Contracting | Paragraph 5.2 indicates a copy of the Abstract was included as a Section J RFP attachments. However, the Abstract is not one of the 5 Section J attachments. Please provide an editable Abstract attachment. | It will be an attachment when final is released. | No Change | |
| Section L | 3.2 Table L-1 and 4.1.1.1.6 | PM | Table L-1 has double asterisk (**) notation for Commitment Letters that is associated with Volume IV Factor IV Small Business Participation Plan Commitment. The only other reference for Commitment Letters in the solicitation is in Section L 4.1.1.1.6 Volume 0 Administrative Volume which is for key personnel. These two references to Commitment Letters appear to be different from one another. Please clarify the definition of commitment letters as required for Volume IV, and the definition of commitment letters as required for Volume 0. | Section L was revised to limit confusion. |
| Section L-1 has been edited for corrections | |||||
| Section L | 1.1.2.2 and 2.3.3, and Section M 2.1.4 | PM | There is a discrepancy regarding whether all proposals that meet the minimum qualifications will receive an award (Section L, 1.1.2.2 and 2.2.3.3) or whether there will there be a comparative analysis of bidder proposals as described in Section M 2.1.4. Please clarify. [For reference: Section L, 1.1.2.2 "As the evaluation does not involve comparative judgements ...". Section L, 2.2.3.3 "No Comparative Analysis. ... IDIQ awards were based solely on meeting minimum qualifications ...". Section M 2.1.4, "When considering the relative merit of each proposal, comparisons will be made...". | M2.1.4 was revised to state: | |
| The evaluation of proposals will consider two groups of Offerors: Other Than Small Business (OTSB) and Small Business (SB). Proposals within each group will be evaluated independently against the stated evaluation criteria. Proposals from OTSB offerors will not be evaluated against proposals from SB offerors, and vice-versa. | Section M 2.1.4 was edited | ||||
| Section L | 1.1.2.2, 2.2.3.3, 4.5.2.1.2 | PM/Contracting | If all qualifying offerors will receive an award, how will 20% of awards be reserved for small business (Section L 4.5.2.1.2.)? This implies that trade-offs , rankings, and/or comparisons will be made across Offerors, but the solicitation states that comparisons will not be made (Section L 1.1.2.2 and 2.2.3.3). | The Government clarifies that there is no conflict between the qualifying offeror approach and the 20% small business set-aside. The two work together through separate evaluation groups rather than through trade-offs or comparisons. | |
| The 20% set-aside is achieved through SEPARATE EVALUATION, not through trade-offs or comparisons. | No Change | ||||
| PWS | 1.3/ Appendix 1 | SST | For mid-level experience and expert-level experience, are there additional years of experience that can be substituted for the desired education as is the case for junior and senior level positions? | The LCAT Level was revised and the below was added to the description: | |
| An additional four years of experience in the specific labor category, for a total of 12 years of experience in the specific labor category, may be a substitute for a bachelor’s degree. | SOW revised | ||||
| Section M | 2.1.3 | PM | Please verify the reference to subfactors is no longer relevant in accordance with the current draft RFP. | There are not any subfactors- Section M 2.1.3 was revised and the word "Subfactor" was removed to eliminate confusion. |
Section L 4.1.1.4.2 "Subfactors" was removed to eliminate confusion.
| Section L 4.3.1.3 "evaluation element" was put in place of "Subfactor" | Section L and M was edited to remove Subfactor language | |||||
| Section L | 3.10.4 | Contracting | The time on the SF33 does not match Section L 3.10.4. Please clarify. | This will be corrected when the Final RFP is released | No Change | |
| Section L | 3.13.2 | Contracting | Are tabs blank pages that are not counted in page limits? | Tab Pages / Divider Pages are: |
Separator pages used to organize proposal sections Contain only a section title/identifier Used to help evaluators navigate between major sections Visual dividers (in electronic proposals)
| Improve proposal organization and readability | No Change | |||||
| Section L | 3.13.2 | Contracting | Are tabs considered level one sections with the next page starting on a new section? Request clarification of where tabs are requested. | The solicitation does NOT prescribe where tabs/dividers must be placed or require them at specific organizational levels. The use of tabs/dividers is at the offeror's discretion to organize their proposal for clarity and ease of navigation. | No Change | |
| Section L | 3.13.2 | Contracting | If tabs are blank pages, do tab pages get a page number? | The solicitation does NOT prescribe whether tab/divider pages must be numbered or left unnumbered. This is at the offeror's discretion as part of their overall page numbering scheme. | No Change | |
| Section L | 3.14.1 | PM | Is it accurate that the Section 3.14 request for "explanations" is the same as providing the acronym definition? | No, this is not accurate. The request for "explanations" goes beyond providing acronym definitions. |
| While a definition provides the spelled-out term that an acronym represents, an explanation may include additional context to ensure the evaluators understand how the term applies to your proposal. | No Change | ||||
| Section L | 3.14.2 | PM | Glossaries do not count for the page limit but the table L-1 does not include glossaries in the ** excluded items. Please add glossaries to the ** note in the table. | Section L was revised to limit confusion. |
| Section L-1 has been edited for corrections | ||||||
| Section L | 3.2 Table L-1 | PM | In Table L-1 for Factor IV: Small Business Participation Commitment**, the two asterisks are defined below the table stating, "Page limit does not include Commitment Letters and Subcontracting Plan." Please clarify what is meant by “Commitment Letters” in the context of Factor IV: Small Business Participation Commitment. The only commitment letter in the draft is for the program manager key personnel position resume. | Notes on Table L-1 changed. | ||
| Commtiment Letters was deleted from the Note. | Section L-1 has been edited for corrections | |||||
| Section L | 3.2 Table L-1 | SST | With the additional requirements added to Vol II (e.g., Section M 7.2.1.1; 7.2.2.1, 7.2.3.1, 7.2.4.1, 7.2.5.1), we respectfully request 10 more pages to provide the requested technical examples/plans, subcontactor management plan, and additional requested details. | The Governement has decided to deny this request for additional pages in the proposal. The current page limits are firm and necessary to ensure a focused and equitable evaluation process. Please prioritize the most critical information within the allocated space. If you have questions about the requirements, feel free to clarify. | ||
| No Change | ||||||
| Section L | 3.2 Table L-1 | SST | In the previous draft there were 6 additional pages for graphics outside of the Vol II page limit. We request the 6 additional graphics pages be added back and remain outside of page limits. | No, the Government will not add back a separate 6-page allowance for graphics in Volume II, as this was intentionally removed in the current draft to streamline proposal preparation and ensure focus on substantive content | No Change | |
| Section L | 3.2 Table L-1 and 4.1.1.1.6 | PM | Please confirm commitment letters for both Section L 3.2 Table L-1 and 4.1.1.1.6 are outside of page limits. | Table L-1 was edited to reflect "* Page limit does not include Key Personnel Commitment Letters." | Section L-1 has been edited for corrections | |
| Section L | 3.2 Table L-1 and 4.1.1.2.2 | PM | If Offerors provide an OCI Statement affirming there is no OCI, is a 5-page mitgation plan still required to be submitted with the proposal? Section L 3.2 Table L-1, states "if necessary", however, Section L 4.1.2.2 Documentation Requirements requires a 5-page OCI Mitigation Plan. We request that an OCI Mitigation Plan only be required if the Offeror cannot provide the OCI Statement. | An OCI Mitigation Plan is only required if the Offeror identifies a potential, actual, or apparent OCI. | Section L 4.1.1.2.2 and 4.1.2.2 was edited | |
| Section L | 3.2 Table L-1, 4.1.1.3, and 4.1.1.4, | PM | Will the Government allow the Executive Summary and Narrative Summary to be one page each to accommodate meaningful information for the five required sections? | No | No Change | |
| Section L | 3.3.2 | PM | Please confirm cover pages denoting classification are outside of page count. | Section L was revised to limit confusion. |
| Section L-1 has been edited for corrections | |||||
| Section L | 3.4.2 | PM | Would the Government allow 10-pt Times New Roman font in graphics? | No | No Change |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .