QA - W91QEX26R0001 - J2 EDA IDIQ - KO Review_ RS Input.xlsx
XLSX spreadsheet 165 KB Posted
- Attached to
- USSOUTHCOM J2 EDA IDIQ
- Solicitation number
- W91QEX26R0001
About this file
This document is a comprehensive Questions and Answers (Q&A) file related to a multiple-award Indefinite Delivery/Indefinite Quantity (IDIQ) contract for the USSOUTHCOM J2 Enhanced Domain Awareness (EDA) Program. The solicitation (W91QEX26R0001) seeks a contractor to provide strategic and technical support services across 16 distinct Work Orders, including cloud infrastructure, knowledge graph development, data engineering, geospatial systems, cybersecurity, and program management. The contract will be unrestricted, with a performance period of approximately 41 months (including a 30-day phase-in period) starting January 23, 2026, and will involve supporting USSOUTHCOM's mission partners across various operational domains.
Key details include a requirement for Top Secret Facility Clearance at proposal submission, with contractors responsible for developing cloud-agnostic, containerized solutions supporting IL-2, IL-4, and IL-5 environments. The incumbent is Quiet Professionals LLC, and the contract will involve inheriting existing security artifacts and cloud environments, potentially spanning AWS GovCloud and Azure Government platforms. Pricing will be primarily Firm-Fixed-Price with cost-reimbursable elements for Other Direct Costs, and the Government anticipates awarding multiple contracts based on proposals meeting specific evaluation criteria. Contractors must be prepared to support complex data integration, knowledge graph development (targeting one billion graph edges), and mission-critical web services with stringent performance requirements.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| W91QEX26R0001 - Solicitation EDA IDIQ -Amendment - 22Dec2025.pdf | ||
| Performance Assessment Questionnaire.docx | DOCX document | |
| W91QEX26R0001 - Solicitation EDA IDIQ - 4DEC2025.pdf | ||
| Surge Price Sheet.xlsx | XLSX spreadsheet | |
| DD FORM 254 - DRAFT.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
Q&A
| 1 | 52.212-1 – Instructions to Offerors – Commercial Items, Subfactor 1: Experience and Volume 2/ Factor 2 – Past Performance, Page # 386, Would the Government please consider accepting non-DoD projects for Experience and Past Performance? | The requirement wil be remain as is for this | |
| 2 | 52.212-1 – Instructions to Offerors – Commercial Items, Volume 2 / Factor 2 – Past Performance, Page # 386, Would the Government please consider accepting CPARS in lieu of PPQs? | CPARS will be acceptable as well along with PPQ's | |
| 3 | Could you kindly confirm whether this requirement represents a new effort, or if there is an incumbent currently performing these services? If an incumbent exists, we request the incumbent contract details, including any available information on the current contractor and ongoing performance arrangements. | This is a follow on requirement. Quiet Professionals LLC is the incumbent (2701 N Rocky Point Dr. Ste 175 Tampa, FL. 33607) | |
| 4 | Could you please provide the anticipated or historical contract value associated with this requirement, if available? | Not at this time | |
| 5 | Page 382, Question and Answer Period: The solicitation indicates that questions will not be answered until Monday December 22nd. Given that the answers to the questions submitted below will materially affect proposal response preparation, will the Government consider an extension if answers to questions cannot be provided until 12/22? | There will be no extension at this time | |
| 6 | Page 1, SF1449, Block 10 and Page 372, FAR 52.219-32: Block 10 of the SF1449 indicates this solicitation is a 100% Unrestricted procurement. However, the solicitation includes FAR 52.219-32 for Orders Issued Directly Under Small Business Reserves. Please confirm this solicitation's status is Unrestricted. If this is a fully unrestricted procurement with no small business reserves, please confirm that clause 52.219-32 will be removed via amendment. | Clause 52.219-32 was removed | |
| 7 | Page 388, Solicitation, Section M, Evaluation Factors for Award: The solicitation states "This is a competitive Trade Off best value source selection conducted in accordance with Federal Acquisition Regulation (FAR) 8, Required Sources of Supplies and Service. . . " Given that this is an unrestricted, open-market solicitation posted on SAM.gov for commercial items/services, please confirm that the correct governing authority for competitive trade-off source selection is FAR Part 15 and/or FAR 16.505 for the ordering of individual Work Orders under the IDIQ, and not FAR Part 8. | This has been updated to reflect FAR Part 16.5 - Indefinite Delivery Contracts | |
| 8 | Page N/A, Solicitation: The Solicitation implies the Government will make multiple awards in support of this IDIQ solicitation. Under this solicitation, the Government envisions up to 16 Work Orders that may be awarded. The Solicitation does not indicate how the Government will compete or award individual Work Orders among Multiple IDIQ Awardees. Can the Government confirm and amend the Solicitation if the Government intends to compete Work Orders among the IDIQ Multiple Awardees after IDIQ award using FAR 16.505 and provide the Fair Opportunity Procedures planned for Work Order Competitions? | The Government intends to compete each Task Order amongst the IDIQ awardees | |
| 9 | Page 388, Solicitation, Section M, Evaluation Factors for Award, Paragraph 2: Paragraph 2 states "The Government intends to award multiple award IDIQ contracts under this solicitation." | ||
| Page 388, Solicitation, Section M, Evaluation Factors for Award, Section Factors and SubFactors to be Evaluated: This section states "Award will be made to the offeror [singular] whose proposal is most advantageous . . .".Can the Government confirm this is a multi-award IDIQ? | Yes, multiple award IDIQ | ||
| 10 | Page 388, Solicitation, Section M, Evaluation Factors for Award: Paragraph 2 states "The Government intends to award multiple award IDIQ contracts under this solicitation." Can the Government share the minimum and maximum number of awards it intends to issue? | There is no minimum or maximum | |
| 11 | Page 131, Section C, PWS, Part 5, Section 5.6: Two Work Orders, WO-011 Program of Record and WO-015 Cross Domain Support are established as contract structure placeholders to support future requirements, are not part of this solicitation, and are not priced or proposed at this time. What is the Government's activation processes for these two Work Orders under a multi-award IDIQ? Does the Government envision future Fair Opportunity Proposal Requests from IDIQ awardees if these orders are executed? | The solicitation requirement remains as written. These Work Orders are inactive placeholders and will only be activated if future Government requirements materialize. Should the Government decide to execute WO-011 or WO-015 under the multi-award IDIQ, activation would occur through a separate Fair Opportunity Proposal Request (FOPR) issued to all eligible IDIQ awardees in accordance with FAR 16.505. No pricing or proposals are requested at this time, and any future execution would follow a new competitive task-order process. | |
| 12 | Page 21, Section B, CLIN Structure; Pages: Multiple, PWS, Attachments 1-16: Nearly all Work Orders contain requirements for purchasing via ODCs. The IDIQ only contains a single ODC CLIN per contract year (0045, 1045, 2045, 3045). As the IDIQ is a multi-award contract, is this single, annual ODC CLIN envisioned as shared capacity across all awarded Work Orders and awarded Offerors? Will ODCs be obligated at the individual work order level when each work order is awarded? | The solicitation requirement remains as written. The single annual ODC CLIN (0045/1045/2045/3045) is not a shared or pooled capacity across all IDIQ awardees. ODCs will be obligated at the individual Work Order level, consistent with FAR 16.505. Each Work Order will specify its own ODC requirements and associated funding, and only the contractor receiving that Work Order will have ODC funds obligated. Other awardees will not access or draw from these CLINs unless awarded a separate Work Order that includes ODC obligations. | |
| 13 | Page 81, Section C, PWS Part 1, Section 1.5 and Page 369, Solicitation, Section I, Contract Clauses: The Period of Performance identifies a provision for an optional FAR 52.217-8 extension. | ||
| Please confirm the potential extension should NOT be priced as part of the CLIN pricing structure, as the CLIN pricing structure does not contain entries for a 52.217-8 extension.Should a FAR 52.217-8 be authorized in execution, does the Government intend on awarding a pro rata value using a continuation of Option Year 3 pricing? | Correct - 52.217-8 shall NOT be priced - if 52.217-8 is utilized pricing from last Option Period will be utilized | ||
| 14 | Page 89, Section C, PWS, Part 1, Section 1.6.10: States "Key Personnel: The Contractor shall provide key personnel as specified in the Work Order Requirements." |
Page 116, Section C, PWS, Part 2, Section 2.1.7: States "Key Personnel: Contractor Personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal."
| Please clarify if there is a requirement to provide any type of firm commitment evidence for the 2 Key Personnel - i.e., evidence of employment, contingent offers, etc.? | Senior Program Specialist (SPS) & Senior Software Developer (SSD) have been removed from the solicitation. Resumes will not be evaluated and has been removed from the solicitation. Key Personnel will be identified at the Task Order level once IDIQ holders have been established. Thus resumes will be required and evaluated at the Task Order level once the requirement is submitted and competed amongst awarded IDIQ holders | |
| 15 | Page 104, Section C, PWS, Part 2, Full-Time Equivalent Definition: For consistency in pricing across all Offerors, can the Government confirm the following Full-Time Equivalent (FTE) definitions in terms of person-labor hours: |
- 1.0 (100%) FTE = 1920 hours, annually.
- 0.5 (50%) FTE = 960 hours, annually.
| - 0.25 (25%) FTE = 480 hours, annually. | Confirm | ||
| 16 | Page N/A; Solicitation: Please confirm that this unrestricted solicitation includes no mandatory requirements for small business participation or subcontracting plans that require coverage in our proposal submission. Please verify that there are no associated evaluation criteria regarding small business participation. If small business participation and/or subcontracting plans are required, please provide the required small business participation commitments or target percentages applicable to this effort. | There is no mandatory requirement for Small Business participation or subcontracting plans | |
| 17 | Page N/A; Solicitation: If the Government updates the solicitation to include small business participation requirements, will the requirements be assessed at the overall IDIQ level, or will the requirements be assessed at the individual Work Order level? | See answers to Question 16 | |
| 18 | Page N/A, Solicitation: There is currently nowhere in the solicitation allocated for Offerors to introduce our teaming partners/subcontractors. Can an introduction to our subcontractors and our team's collective capabilities be included in Volume 1 - Technical before we begin to discuss our contract references? | There is no requirement for subcontracting. The awards for IDIQ will be based on Prime Contractor. It's up to Prime Contractor how they submit proposal if they consider subcontracting | |
| 19 | Page N/A, Solicitation: If the Government will allow an introduction to our subcontractors and our team's collective capabilities within Volume 1 - Technical before we begin to discuss our contract references, please confirm that the team introduction section can contain company logos, names, or other identifying information. | Please see Section L pertaining to company logos, name and other idenifying ifnormation in proposal submittal | |
| 20 | Page 383, Page Limitations and Format: Please confirm that font requirements do not apply to cover pages, headers/footers, or any pre-existing forms requiring completion (e.g., Performance Assessment Questionnaires, SF1449, Overtime Support Pricing Sheet, Representations and Certifications) | Confirm - correct | |
| 21 | Page 383, Page Limitations and Format: Please confirm that font requirements do not apply to cover pages, headers/footers, or any pre-existing forms requiring completion (e.g., Performance Assessment Questionnaires, SF1449, Overtime Support Pricing Sheet, Representations and Certifications) | PPQ submission and CPARS are acceptable as well for Volume 2 | |
| 22 | Page 383, Volume 3, Price: Given a potential for discrepancies within the SF1449 CLIN Pricing Structure, would the Government consider providing a separate Volume 3 Pricing Template in Microsoft Spreadsheet format for completing the Volume 3 Pricing Submission? A separate template spreadsheet would allow both the Government and industry to validate all priced CLIN level labor is present, mapped and correctly aligned to the PWS. It will also provide the Government a consistent and standardized pricing format from all Offerors for easier and more accurate evaluation. | The requirement will remain as is - all vendors will submit pricing in accordance to solicitation instructions | |
| 23 | Page 384, Volume 1/Sub-Factor 1 - Experience, Relevancy: The solicitation states: "A relevant contract reference can be a competitive or noncompetitive single contract purchase order, or a standalone task order." One of our relevant ongoing projects was split, due to contracting technicalities, across multiple task orders but is all considered to be a standalone, continuous work product/project. Would it be possible to consider this project a single contract for the purposes of this solicitation? | Yes | |
| 24 | Page 384, Note on Ostensible Subcontracting Rules: Please confirm that ONLY Past Performance from the Prime Offeror will be considered as recent and relevant Past Performance. Past Performance from teaming partners or subcontractors CANNOT be used in lieu of Prime Offeror Past Performance. | This requirement was removed from the solicitation and no longer applies | |
| 25 | Page 384, Volume 1 - Technical, Sub-factor 1 - Experience, Recency: The recency requirements for Volume I state: "To be considered recent, the contract reference must have been awarded within the last five (5) years". |
Page 386, Volume 2 / Factor 2 - Past Performance, Recency & Relevancy: The recency requirements for Volume II state: "A recent contract reference will be considered an active contract within the last five (5) years at the time of proposal submission."
| Can the Government please confirm that contracts that were active within the last 5 years at the time of proposal submission, regardless of award date, would meet recency requirements for both Volume 1 and Volume 2? | Confirm | |
| 26 | Page 384, Solicitation, Section L, Volume 1, Sub-Factor 1, Experience: States "The contracts must have been similar in size and scope in support of U.S. Government." |
Page 386, Solicitation, Section L, Volume 2, Past Performance: States "Contracts identified in the PPQ must be contracts completed for the Department of Defense."
Page 386, Solicitation, Section L, Volume 2, Past Performance, Recency & Relevancy: States " A relevant contract is a contract . . . for the US Government."
Page 388, Solicitation, Section M, Volume 1, Sub-Factor 1, Experience: States "The contracts must have been similar in size and scope in support of U.S. Government."
Page 391, Solicitation, Section M, Volume 2, Past Assessment: States "Contracts identified in the PPQ must be contracts completed for the Department of Defense."
| Section L and Section M and Volume 1 Experience/Volume 2 Past Performance use slightly different terminology for Experience and PPQ requirements. Can the Government confirm that Past Performance Experience References and PPQs only for the more specific US Department of Defense will be compliant vs the more general US Government? | Confirm | ||
| 27 | Page 385, Solicitation, Section L, Volume 1, Sub-Factor 2 - Resumes: Sub-Factor 2 identifies two (2) Key Personnel Resume Position Descriptions that will be evaluated as part of proposal response. These include 1 Senior Program Specialist (SPS) and 1 Senior Software Developer (SDS). Neither of these Position Descriptions/Titles are part of the current PWS. Can the Government please confirm these are the correct Key Personnel resume LCATs for proposal evaluation purposes? If not, can the Government please update this table with the Key Personnel Position Description/Title, Knowledge/Skills/Abilities, and Experience aligned to the PWS? | Senior Program Specialist (SPS) & Senior Software Developer (SSD) have been removed from the solicitation. Resumes will not be evaluated and has been removed from the solicitation. Key Personnel will be identified at the Task Order level once IDIQ holders have been established. Thus resumes will be required and evaluated at the Task Order level once the requirement is submitted and competed amongst awarded IDIQ holders | |
| 28 | Page 385, Solicitation, Section L, Volume 1, Sub-Factor 2 - Resumes: Sub-Factor 2 identifies two (2) Key Personnel Resume Position Descriptions that will be evaluated as part of proposal response. These include 1 Senior Program Specialist (SPS) and 1 Senior Software Developer (SDS). Neither of these Position Descriptions/Titles are part of the current PWS. Can the Government please confirm these are the correct Key Personnel resume LCATs for proposal evaluation purposes? If not, can the Government please update this table with the Key Personnel Position Description/Title, Knowledge/Skills/Abilities, and Experience aligned to the PWS? | Senior Program Specialist (SPS) & Senior Software Developer (SSD) have been removed from the solicitation. Resumes will not be evaluated and has been removed from the solicitation. Key Personnel will be identified at the Task Order level once IDIQ holders have been established. Thus resumes will be required and evaluated at the Task Order level once the requirement is submitted and competed amongst awarded IDIQ holders | |
| 29 | Page 386, Volume 2/Factor 2 - Past Performance: The solicitation states: "It is the offeror’s responsibility to assure all identified contract reference PPQ’s are filled out entirely and are submitted to the Contract Specialist / Contracting Officer before the deadline to submit proposals under the subject solicitation." Is the expectation that vendors include completed PPQs, evaluated and signed by our relevant customer POCs as part of Volume 2? | Yes | |
| 30 | Page 386, Solicitation, Section L, Volume 2, Past Performance - Other Sources of Past Performance Information: This section states "Other sources may include, but are not limited to, past performance information retrieved through the Past Performance Information Retrieval System (PIRS) using all CAGE/DUNS numbers of team members (partnership, joint venture, teaming arrangement, or parent company/subsidiary/affiliate) identified in the Offeror's proposal . . . ". There is currently no section or volume of the proposal where an Offeror may be able to supply the CAGE/DUNS of its team members. Would the Government allow a section of the proposal to introduce the Offeror's team members? | Not required | |
| 31 | Page 386, Solicitation, Section L, Volume 3, Price: The instructions state "The Offeror shall submit a completed SF1449 CLIN structure indicating a unit price and total proposed price for all Contract Line-Item Numbers (CLINS) for the base period accordingly." The CLIN structure contains a structure for the Base period, as well as Option 1, Option 2, and Option 3. Should the evaluation criteria be revised to include pricing for the entire current CLIN structure, inclusive of the Base, Option 1, Option 2, and Option 3? | This language has been updated to include base + all option periods | |
| 32 | Page 388, Section M, Evaluation Factors for Award: Paragraph 2 states "To be eligible for award, the Offerors must meet all requirements of the solicitation for all CLIN's, including options . . .". | ||
| Please confirm that Volume 1, Sub-Factor 1 - Experience and Volume 2 - Past Performance evaluations will evaluate the similarity of size and scope to the IDIQ PWS versus any individual Work Order. | Confirm | ||
| 33 | Page 395, Solicitation, Section M, Volume 3, Price: Section M does not describe how the Government will evaluate the completed SF1449 CLIN Pricing Structure for Volume 3. Will the Government evaluate 1) The Total Price inclusive of all contract years and CLINs; 2) Pricing at the individual CLIN/LCAT level; or 3) At the Work Order Level? What techniques will the Government use? | 1) | |
| 34 | Page 395, Solicitation, Section M, Volume 3, Price: It is unclear how the Government will award the multi-award IDIQ and the subsequent Work Orders. Pricing for all CLINs, covering each of the currently envisioned Work Orders, is being requested during the IDIQ proposal submission. How will IDIQ pricing be used or applied for future Work Order competition? | Task Orders will be completed amongst IDIQ awardees | |
| 35 | Draft DD254, Page 1: On the Draft DD254, Box 1.b. is marked to require Top Secret Safeguarding for classified information at the contractor facility. |
Draft DD254, Page 2: On the Draft DD254, only Box 11.a (access to classified information at a Government Activity), 11.j. (Have operations security OPSEC requirements), and 11.m. (additional guidance will be provided) are checked. Box 11.b. to receive and store classified documents and Box 11.c. to receive, store, and generate classified information are not checked.
| Can the Government confirm that Awardees will only have access to Top Secret information at the Government site and will have no requirement to safeguard Top Secret information at a contractor's facility? | Top Secret Facility Clearance required for all vendors in order to acceptable | ||
| 36 | Is there an existing set of security artifacts, SSP/SAR/POA&M and ATO boundary documentation that the awardee will inherit from the incumbent? If so, please provide the current SSP and SARs or describe how they will be shared with the selected contractor (the PWS mentions inheriting artifacts from incumbent). | The solicitation requirement remains as written. Security boundary documentation and associated artifacts (e.g., SSP, SAR, POA&M, ATO materials) will be provided only to the awardee after contract award in accordance with DoD cybersecurity policies and need-to-know restrictions. These materials contain sensitive information and will not be released during the solicitation phase. As stated in the PWS, the awardee will inherit the necessary security artifacts and deployment documentation from the incumbent as part of the post-award transition process. | |
| 37 | Which specific cloud tenancy(s) and GovCloud accounts will be available (Azure Government / AWS GovCloud) and what level of shared resources (e.g., Databricks workspace, Kubernetes cluster images, secrets vaults) will the contractor be provided vs. required to provision? The PWS references Databricks and GovCloud but allows alternatives if government-approved. | The solicitation requirement remains as written. The Government will provide access to the existing accredited cloud environments and associated GovCloud accounts required to perform the tasks in the awarded Work Orders. These environments currently operate within DoD-authorized cloud tenancies (e.g., AWS GovCloud (IL4/IL5) and Azure Government), and the specific accounts, access levels, and shared platform components (such as Databricks workspaces, Kubernetes clusters, secrets management services, or similar shared resources) will be made available to the awardee post-award in accordance with security and need-to-know requirements. Contractors will not be expected to provision new cloud accounts unless directed by the Government; however, contractors may propose alternative technologies or services where permitted by the PWS, subject to Government review and approval. Detailed configuration information and access credentials will only be shared with the awardee during transition and onboarding. | |
| 38 | Are there existing IaC repositories (Terraform/ARM/Bicep) and container images (Helm charts, base images) that the contractor must use, or must the contractor design and deliver these artifacts from scratch? The PWS requires containerized, IaC-based deployables and portability. | The solicitation requirement remains as written. The Government will provide the awardee with all authorized technical artifacts necessary to perform the requirements of the awarded Work Orders. Specific details regarding existing infrastructure-as-code templates, container images, or deployment artifacts will be shared only after award in accordance with DoD security and need-to-know restrictions. Regardless of what artifacts are provided during transition, the contractor is responsible for developing, maintaining, and updating IaC- and container-based deployment solutions that meet the PWS requirements for portability, cloud agnosticism, and DoD security compliance. |
No further information about current system configurations or repositories can be released during the solicitation phase.
39 For data ingestion and ETL: what are the expected average and peak ingestion rates (records/sec and data volume/day) for typical mission datasets (and expected retention classes across raw/processed/enriched tiers)? KPIs reference transfer latencies; we need volumes to size Databricks, Kafka/EventHub, and storage tiers. The solicitation requirement remains as written. Mission data ingestion rates, peak throughput profiles, and retention tier specifications constitute operationally sensitive information and will not be released during the solicitation phase. The awardee will receive the required dataset profiles, throughput expectations, and retention parameters during post-award onboarding in accordance with DoD security and need-to-know requirements.
Contractors should propose scalable, cloud-agnostic ingestion and processing architectures capable of supporting variable, high-volume data pipelines consistent with the PWS requirements for elasticity, containerized deployment, and portable IaC. KPIs listed in the solicitation define performance objectives; detailed volume estimates will be provided to the awardee to enable final system sizing and configuration.
| 40 | For geospatial processing: what are the expected map tile rendering load, typical layer sizes, coordinate/accuracy standards, and whether vector or raster outputs are preferred? The PWS requires 95% data-layer accuracy and ESRI licensing; practical sizing depends on expected layer scale and refresh rate. | The solicitation requirements remain as written. Geospatial layer scales, map tile rendering loads, coordinate accuracy thresholds beyond those stated in the PWS, and preferred output formats are operationally sensitive and will not be released during the solicitation phase. These parameters will be provided to the awardee during post-award onboarding in accordance with DoD security, OPSEC, and need-to-know requirements. Contractors should propose scalable, standards-compliant geospatial processing architectures capable of supporting both raster and vector workflows, elastic tile rendering, and high-volume geospatial analytics in alignment with the PWS requirements for 95% data-layer accuracy, ESRI Enterprise licensing, Kubernetes-based geospatial workloads, and cloud-agnostic deployment. Final sizing and configuration will be refined post-award when authoritative dataset profiles and refresh expectations are furnished to the awardee. |
| 41 | What authentication/identity integration specifics are required: will the contractor integrate with an existing Microsoft Entra ID tenant and CAC/PKI federation, and will the contractor receive delegated service accounts and roles ahead of onboarding? PWS references Entra (Azure AD) and CAC integration, but we need technical details for SSO/role mapping and SCIM/provisioning. | The solicitation requirements remain as written. The Government will provide the awardee with the necessary identity, authentication, and access-control information during post-award onboarding in accordance with DoD security and need-to-know requirements. The program uses DoD-approved identity services, including Microsoft Entra ID (Azure AD) with CAC/PKI-based authentication, but specific configurations, federation details, role mappings, SCIM provisioning workflows, and service-account structures will not be released during the solicitation phase. The awardee will receive the required access, roles, and service accounts as part of the transition process, consistent with RMF, zero-trust principles, and Government identity governance policies. Contractors should propose solutions capable of integrating with DoD identity services and supporting CAC/PKI authentication, role-based access control, and standards-aligned provisioning workflows, as required by the PWS. |
| 42 | What telemetry, logging and SIEM ingestion endpoints are mandatory (e.g., Microsoft Sentinel, Splunk, AWS Security Hub), and are there retention/forwarding requirements for logs across IL4/IL5 enclaves? The PWS requires SIEM and policy management tooling and quarterly log audit compliance. | The solicitation requirements remain as written. Specific telemetry endpoints, log forwarding targets, SIEM platforms, and enclave-level retention or cross-domain log-movement requirements will be provided to the awardee after contract award in accordance with DoD security, RMF, and need-to-know restrictions. These details are part of the accredited security boundary and will not be released during the solicitation phase. Contractors should propose solutions capable of integrating with DoD-approved logging, telemetry, and SIEM environments; supporting IL4/IL5 log collection and retention requirements; and meeting the PWS obligations for quarterly audit readiness, policy compliance, and centralized log management. Final configuration—including required ingestion endpoints, retention periods, and forwarding rules—will be provided during transition to ensure alignment with the existing ATO and Government security architecture. |
| 43 | For knowledge graph tooling—are there licensing constraints or an existing shared Stardog/Neo4j instance available, and are federated queries required across the shared knowledge-graph environment? The PWS mentions shared Stardog license under TO-007 and governance via TO-014. | The solicitation requirements remain as written. Licensing details and specific configurations for any existing knowledge-graph platforms (e.g., Stardog, Neo4j) will be provided to the awardee after contract award in accordance with DoD security, RMF, and need-to-know restrictions. The PWS identifies that Work Order 007 includes support for a Government-furnished knowledge-graph capability and that Work Order 014 governs associated data-management, licensing, and shared-service coordination; however, no additional information regarding current instances, license allocations, or federation requirements will be released during the solicitation phase. |
Contractors should propose solutions capable of integrating with Government-furnished knowledge-graph technologies, supporting federated and non-federated query patterns, and enabling schema governance, ontology management, and scalable ingestion in alignment with the PWS. Final determinations regarding available shared services, licensing structures, and any required federated query configurations will be provided to the awardee during transition.
| 44 | Are there hard constraints on allowable third-party or commercial libraries (e.g., specific ESRI modules, paid geospatial libraries) versus open-source replacements for portability and ATO acceptance? The PWS emphasizes avoiding proprietary configurations that inhibit migration. | The solicitation requirements remain as written. The Government does not provide additional pre-award constraints on specific third-party or commercial libraries beyond those stated in the PWS. As outlined in the solicitation, solutions must avoid proprietary configurations that inhibit portability, migration, or reuse across cloud environments and Work Orders. The awardee may use commercial or open-source components as appropriate, provided they comply with DoD cybersecurity, licensing, ATO, and data-portability requirements. Final approval of any third-party libraries, commercial modules, or managed services—whether ESRI or other platforms—will occur post-award during architecture review and ATO alignment. The Government will identify any prohibited components, required modules, or licensing conditions during transition and onboarding in accordance with RMF and need-to-know restrictions. |
| 45 | What are the expected SLAs for roll-forward/rollback and incident response windows for production updates in IL4/IL5 environments (the PWS gives targets for deployment efficiency and rollback rates — need exact acceptance criteria and maintenance windows). | The solicitation requirements remain as written. The solicitation does not specify additional SLAs or maintenance-window requirements for roll-forward or rollback procedures beyond what is provided in the PWS. As outlined in Section 5.3 and 5.5, the contractor must meet the stated performance thresholds for production deployments, including: high-severity incident notification within 15 minutes, system-failure notification within 30 minutes, and ensuring no more than two hours of downtime per Kubernetes-based transformation service during deployment. Detailed operational parameters such as environment-specific maintenance windows, approved production-update schedules, and any additional acceptance criteria for roll-forward or rollback activities in IL4/IL5 environments will be provided to the awardee after contract award in accordance with DoD operational security and need-to-know restrictions. Contractors should propose deployment and incident-response processes capable of meeting the PWS-defined SLAs and KPIs, with final configuration and timing coordinated during post-award onboarding. |
| 46 | Who will be the designated Contracting Officer (KO), COR and EDA Government Program Manager (name and contact) for pre-award coordination and, if available, will they provide a schedule of regular governance meetings? The PWS notes COR will be designated by separate letter but does not supply names in the draft . | This information will be provided after IDIQ award |
| 47 | What are the acceptance criteria and Government review timelines for deliverables (e.g., how many business days for Government review/acceptance of each deliverable)? The PWS requires certain deliverable schedules but typically governments define review windows — we need those windows to schedule activities. | A Post Award Kickoff Meeting will be held and this will be dicussed then |
| 48 | How will change requests to Task Order scope, funding, or deliverable dates be handled and approved (formal change control process)? The PWS indicates only the KO can authorize modifications; please confirm required documentation and expected decision timelines for task-order modifications. | A Post Award Kickoff Meeting will be held and this will be dicussed then |
| 49 | What are the invoice submission requirements and the expected payment schedule for FFP labor CLINs and cost-reimbursable ODCs (supporting documentation, timelines for approval, and contact for invoice questions)? The PWS references CLIN types and cost approval processes but not invoicing templates or cadence. | A Post Award Kickoff Meeting will be held and this will be dicussed then |
| 50 | Are there mandatory program management tooling or templates the Government requires (e.g., a specific PM tool, format for sprint dashboards, or a required government dashboard format)? The PWS requires a Government-approved format for sprint dashboards and monthly Program Status Report integration. | A Post Award Kickoff Meeting will be held and this will be dicussed then |
| 51 | What collaboration / meeting cadence does the Government expect (e.g., weekly working sessions, monthly program reviews, quarterly executive reviews) and which stakeholders must attend? The PWS prescribes monthly program reviews and numerous sprint coordination items; confirm governance meeting frequency and participants. | A Post Award Kickoff Meeting will be held and this will be dicussed then |
| 52 | Are there specific performance remedies or withholding policies tied to KPI noncompliance; if so, what is the process for cure and remediation? The PWS notes remedies and withholding are possible for noncompliance — we need thresholds and cure periods to model program risk. | A Post Award Kickoff Meeting will be held and this will be dicussed then |
| 53 | For on-site personnel: what are the exact facility access/badging processes, lead time, and any restrictions on foreign nationals or third-country national (TCN) staff? The PWS describes USSOUTHCOM badging requirements and facility access rules but not operational timelines for issuing badges. | A Post Award Kickoff Meeting will be held and this will be dicussed then |
| 54 | What is the expected ramp timeline for staffing after award (clearance validation windows and target in-place FTE dates for critical roles)? The PWS defines minimum/scalable FTE caps and clearance requirements — need target staffing schedule to plan recruiting and clearance transfer/relocation windows. | This will be done during the Phase In Period |
| 55 | Are there standard reporting templates / acceptance checklists for QCP (Quality Control Plan) acceptance; QCP must be submitted within 15 days of award — confirm whether an initial QCP draft will be acceptable and whether iterative updates are expected. |
| 56 | For outward-facing dashboards and the data catalog, what level of public or partner-facing access is required (completely public internet, protected web portal, or partner-only authenticated view), and are there branding/UX standards to follow (DoD templates, accessibility policy) for outward-facing interfaces? The PWS references an outward customer-facing data catalog and required attributes for each dataset. | The solicitation requirements remain as written. The solicitation does not authorize the release of additional information regarding public or partner-facing access levels beyond what is defined in the PWS. As stated in Section 2.5, the contractor must develop an outward customer-facing data catalog and make it available as a web-based interface for searching, filtering, and rendering geospatial datasets and research products. Required attributes such as Information Level Sensitivity, handling instructions, and PII/HPI/USPI indicators must be included for all catalog entries. The PWS does not specify whether the catalog or dashboards will be publicly accessible, restricted to authenticated partners, or hosted on a protected portal. Final access posture—including authentication requirements and external user eligibility—will be provided to the awardee post-award in accordance with DoD security and information-governance requirements. The PWS also does not mandate a specific branding or UX template but requires the catalog to provide intuitive navigation and an interactive interface for dataset search and rendering. Contractors are expected to follow applicable DoD accessibility and usability standards for outward-facing interfaces, with any additional branding or design requirements identified during post-award coordination with the Government. |
| 57 | Are Spanish and Portuguese language localizations required for user interfaces, or are those skills only “highly desirable” for the contractor team? The PWS notes Spanish and Portuguese are highly desirable but not mandatory; confirm whether UI localization is required for outward-facing components. | The solicitation requirements remain as written. The solicitation identifies Spanish and Portuguese language skills as highly desirable for personnel supporting the program, but it does not require language localization of user interfaces. The PWS does not mandate translation or multilingual support for dashboards, the outward-facing data catalog, or any other UI components. Accordingly, UI localization into Spanish or Portuguese is not a requirement under this solicitation. Any multilingual features may be proposed by the contractor if they enhance usability for mission partners, but they are not required for compliance. |
| 58 | Are there existing UX/UI style guides, color palettes, and DoD branding requirements or must the contractor propose a design system that conforms to DoD/USSOUTHCOM standards? The PWS instructs products be produced using Government-prescribed standard formats; clarify graphic standards and accessibility/508 requirements. | The solicitation requirements remain as written. The solicitation does not provide additional UX/UI style guides, branding packages, or color palettes beyond the requirement that all products conform to Government-prescribed standard formats. The PWS does not specify a design system for dashboards or outward-facing components. Contractors should propose a design approach that aligns with DoD and USSOUTHCOM expectations for professional presentation and complies with all applicable federal accessibility regulations, including Section 508 of the Rehabilitation Act, which requires electronic and information technology used by the Government to be accessible to individuals with disabilities. Any additional branding, graphic standards, or templated formats required by the Government will be provided to the awardee during post-award coordination. |
| 59 | What performance targets are required for map rendering and dashboard responsiveness (e.g., page load time target referenced in KPIs) and are synthetic monitoring tools and thresholds prescribed (Lighthouse or equivalent)? The PWS includes page load time KPIs and suggests a monitoring tool but asks for specification — confirm tool or standard to measure against. | The solicitation requirements remain as written. The solicitation already defines the required performance targets and monitoring standards for webpage and dashboard responsiveness. Section 5.7.1 requires all user-accessible content to load in ≤ 3.5 seconds under normal operating conditions, measured through synthetic performance testing conducted in a Government-approved controlled environment within an IL4/IL5 enclave or FedRAMP High tenant. The PWS does not mandate a specific commercial tool such as Lighthouse. Instead, it specifies that contractors must implement **synthetic probes using approved tools—such as Azure Application Insights or an equivalent—**and that all measurements must conform to W3C Navigation Timing standards. Contractors must also document the testing scope, regional distribution, performance metrics, and test frequency, and provide sufficient technical detail to allow the Government to independently verify and validate results. No additional page-rendering or dashboard-specific responsiveness standards are included in the solicitation, and no other monitoring tools are prescribed. |
| 60 | Will the Government provide example user stories, personas, or prioritized dashboard feature lists for each user type (analyst, commander, partner) or must the contractor lead user research and requirements elicitation? The PWS references structured customer engagement and feedback-driven sprint planning; clarify the level of Government-provided detail up-front. | The solicitation requirements remain as written. The solicitation does not provide example user stories, personas, or prioritized dashboard feature lists by user type. As described in the PWS, the contractor is responsible for conducting structured customer engagement, user research, and requirements elicitation to inform backlog development and feedback-driven sprint planning. The Government will identify stakeholder groups and participate in requirements refinement, but detailed user stories, personas, and feature prioritization will be developed collaboratively after award as part of the agile delivery process. |
Accordingly, the contractor should expect to lead the discovery and requirements-definition activities, with Government input and validation provided throughout the execution of the awarded Work Orders.
| 61 | For outward-facing data catalog UI: what minimum metadata and handling attributes must be visible to users (the PWS lists required attributes such as sensitivity, handling instructions and USPI flags) — confirm display requirements and filtering/search expectations . | The solicitation requirements remain as written. The solicitation already defines the minimum metadata and handling attributes that must be displayed in the outward-facing data catalog. As outlined in the PWS, each dataset entry must include required fields such as information-level sensitivity, handling instructions, PII/HPI/USPI indicators, data provenance, update frequency, and other catalog attributes specified in Section 2.5. These attributes must be visible to users and support filtering and search functions within the catalog interface. The PWS does not prescribe additional display rules or mandate specific UI layouts beyond these required metadata elements. Contractors should therefore ensure the catalog supports intuitive navigation, attribute-based filtering, and search across all required metadata fields, with final display and interaction patterns refined collaboratively with the Government after award. |
| 62 | Section 1.6.7.3 of the PWS references the attached DD Form 254, which indicates a Top Secret security requirement for FCL and for Safeguarding For Classified Information/Material Required at Contractor Facility, while Section 4.2 of the PWS states that cleared access is only required where the Work Order requires access to classified information. Please confirm that a Top Secret Facility clearance is not required to submit a proposal to this RFP and will be required as specified in Section 4.2. | Top Secret Facility Clearance required for all vendors in order to acceptable |
| 63 | Section M / Factor 2 (Past Performance) / Subfactor 2 (Resumes) Volume 2 (Past Assessment) states that “Contracts identified in the PPQ must be contracts completed for the Department of Defense” while the Technical Subfactor 1 (Experience) discusses experience in support of the “U.S. Government." To ensure offerors with highly relevant federal performance are not unfairly limited, please confirm whether the Government will accept PPQs for recent and relevant prime/sub/JV efforts performed for other federal agencies (non-DoD). If specific DoD PPQs are required, would USSOUTHCOM consider accepting PPQs from subcontractors? | PPQ submissions are required from Prime Contractor |
| 64 | 384 of 395 Subfactor 1- Experience Will the Government consider removing the minimum three (3) years of experience requirement—or revising it to six (6) months of experience on a five-year contract for recent and relevant services? As a new company with past performance of similar size, scope, and complexity, this requirement would preclude us from competing and disproportionately advantage incumbents and long-standing DoD contractors. Given the Government’s stated goal of promoting innovation and expanding competition, we respectfully request that this requirement be reconsidered or removed. | The requirement will remain as is |
| 65 | General Will the government provide the incumbent contract number? | Contract No: 47QTCA 18D006F Task Order: W91QEX-23-F-0043 |
| 66 | 388 of 395 Evaluation How many awards will be made? | This will be a multiple award IDIQ and depending on proposals accepted after Source Selection Evaluation conducted |
| 67 | 386 of 395 Volume 2/ Factor - Past Performance … for the Department of Defense. Is the government only accepting DoD Past Performance? | Correct |
| 68 | 388 of 395 What is the expected contract value for this contract? | Can't provide this information during current acquisition period |
| 69 | 391 of 395 B. Volume 2 - Past Assessment If we intend to leverage subcontractor experience, should the PPQs be completed by the government customer or by the prime contractor for whom the work was performed? Please note that some prime contractors do not permit direct communication between subcontractors and the government customer for these types of requests. | Prime contractor performed |
| 70 | Page 1 SF1449 Will the government consider extending the due date 2 weeks to provide offerors adequate time to analyze the question responses the government will provide on 22 December and adjust their proposals to provide the best offer possible? | There will be no extension at this time |
| 71 | Page 3 Section B , Item NO 0047, asks for the net price for the Phase-In 1 Month period. Will the government clarify what the offerors shall price for the one month Phase-In period? | This should include administrative cost such as travel, coordination of resources in preparation for full contract performance following month etc |
| 72 | Page 385 Section L Subfactor 2, Key Personnel (Resumes) states: "The Offeror shall submit the resumes of “Key Personnel” as defined in the PWS Paragraph 1.6.10 through 1.6.10.3.2. The resumes shall identify the title of each key personnel listed in accordance with the PWS as it pertains to the following personnel: [Senior Program Specialist and Senior Software Developer]". And PWS 1.6.10 states: "Key Personnel: The contractor shall provide key personnel as specified in the Work Order requirements." Will the government confirm that the offerors shall submit resumes for only the Senior Program Specialist and Senior Software Developer identified in Section L page 385? | Senior Program Specialist (SPS) & Senior Software Developer (SSD) have been removed from the solicitation. Resumes will not be evaluated and has been removed from the solicitation. Key Personnel will be identified at the Task Order level once IDIQ holders have been established. Thus resumes will be required and evaluated at the Task Order level once the requirement is submitted and competed amongst awarded IDIQ holders |
| 73 | Page 385 Section L Subfactor 2, Key Personnel (Resumes) states: "The Offeror shall submit the resumes of “Key Personnel” as defined in PWS Paragraph 1.6.10 through 1.6.10.3.2. " Section 1.6.10.3.2 does not exist. Is there another paragraph reference regarding this requirement? | Senior Program Specialist (SPS) & Senior Software Developer (SSD) have been removed from the solicitation. Resumes will not be evaluated and has been removed from the solicitation. Key Personnel will be identified at the Task Order level once IDIQ holders have been established. Thus resumes will be required and evaluated at the Task Order level once the requirement is submitted and competed amongst awarded IDIQ holders |
| 74 | Page 385 Section L Subfactor 2, Key Personnel (Resumes) states: "The Offeror shall submit the resumes of “Key Personnel” as defined in PWS Paragraph 1.6.10 through 1.6.10.3.2. The resumes shall identify the title of each key personnel listed in accordance with the PWS as it pertains to the following personnel: [Senior Program Specialist and Senior Software Developer]". The two positions, Senior Program Specialist and Senior Software Developer, are not included as key personnel in the Work Orders. Will the government please clarify which CLIN(s) and Work Order(s) they fall under? |
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 .