II_QA_2032H325Q00063.xlsx
XLSX spreadsheet 15 KB Posted
- Attached to
- U. S. Department of Treasury_ Artificial Intelligence (AI) Tools Federal contract opportunity
- Solicitation number
- 2032H325Q00063
About this file
This document is a Questions and Answers (Q&A) spreadsheet for Request for Quote (RFQ) 2032H325Q00063 from the U.S. Department of Treasury for Artificial Intelligence (AI) tools. The solicitation is a small business set-aside seeking AI-powered coding assistants and chat functionality across Treasury and its bureaus, with a five-year period of performance (one base year and four option years). Key requirements include licensing 7,500 AI-Powered Coding Assistant tools, 15,000 AI-Powered Chat Functionality tools, and 15,000 AI Suite of Tools, with vendors able to propose flexible pricing models that meet those quantities.
Critical technical requirements include Section 508 accessibility compliance, compatibility with Treasury's primary programming languages (Python, Java, JavaScript, C#, Shell scripting), integration with existing IAM systems via SAML 2.0, and deployment in Kubernetes-based environments like ECS, FARGATE, or EKS. Vendors must provide validation datasets demonstrating performance metrics such as 200k token context window, 95% autocomplete relevance, and 1-second latency. The solicitation allows for potential no-cost pilot programs for emerging AI capabilities and requires vendors to submit Voluntary Product Accessibility Templates (VPATs) with their proposals. Vendors must be registered in the System for Award Management (SAM) to be eligible.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| 2032H325Q00063_Amendment 0004_.pdf | ||
| Amendment 0004_ 2032H325Q00063_Revised Terms and Conditions.pdf | ||
| II_01_2032H325Q00063_Attachment 2_Price Matrix_Amendment 0004.xlsx | XLSX spreadsheet | |
| Amendment 0003_Attachment 1_Tool Threshold Assessment.docx | DOCX document | |
| Amendment 0003_2032H325Q00063.pdf | ||
| 2032H325Q00063_Amendment 0002_Final.pdf | ||
| II_01_2032H325Q00063__Amendment 1.pdf | ||
| II_01_2032H325Q00063_Attachment 2_Price Matrix_Amend1_20250709.xlsx | XLSX spreadsheet | |
| II_01_2032H325Q00063_Attachment 1_SOW_Amend 1.pdf | ||
| DRAFT RFQ_Questions and Answers_AI Tools.xlsx | XLSX spreadsheet | |
| II_01_2032H325Q00063_Attachment 2_Price Matrix.xlsx | XLSX spreadsheet | |
| II_01_2032H325Q00063_TCs.pdf | ||
| II_01_2032H325Q00063_Attachment 1_SOW.pdf |
Show all 13
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| RFQ Question | Answer | |||
| 1 | The instructions tab within the price matrix spreadsheet states that quoters may not alter the specified quantities for each tool category: 7,500 for AI-Powered Coding Assistant, 15,000 for AI-Powered Chat Functionality, and 15,000 for the AI Suite of tools. What unit of measure is each of these quantities (per user, per token, per query, etc.)? | The unit of measure (e.g., per user, per query, per token) is not prescribed and may vary by vendor. However, quoters must ensure their proposed pricing model provides the government with access equivalent to the full quantity of licenses specified: 7,500 for AI-Powered Coding Assistant, 15,000 for AI-Powered Chat Functionality, and 15,000 for the AI Suite. Vendors may use any unit pricing basis, as long as it results in the government receiving the full functional access implied by those license quantities. | ||
| 2 | Do we need to be certified or qualified in any govt vehicle to respond to the notice? | The solicitation is open market, which means a company does not have to hold a specific vehicle. However, they do have to be registered in the System for Award Management (among other criteria stated in the solicitation) to be considered for an award. SAM can be accessed here: https://sam.gov/ | ||
| 3 | Treasury has requested software installable within their AWS account so we are quoting license costs for usage of our software. Software must necessarily be installed on a server or service, which within AWS will accrue charges for compute, storage, databases, network, AI API usage, and other services. | Acknowledged - the government understands the cost for using the cloud is separate and not included in the cost of the license that will be proposed by quoters under this RFQ. | ||
| 4 | The instructions for proposal formatting are as follows: "All text must use Arial 12-point font with 1-inch margins on all sides." Please let us know if the font size for Tables & Graphics can be Arial 10-point. | That is acceptable. | ||
| 5 | SF 1449 indicates a 1 year period of performance, while the Section 3. Period of Performance indicates a 5 year period of performance. Please confirm, pricing should be for full 5 year period of performance on the SF 1449 as per Section 3 and Attachment 2 Price Matrix | Yes, pricing provided should be for the full specified POP of five years (one base year and four one year options. The POP noted on the SF1449 is for the base year (and will be adjusted based upon the award date). | ||
| 6 | The evaluation criteria of LPTA allows foundational technology vendors to rig competition by providing preferential pricing to certain SB offerors thereby providing an unfair advantage in a LPTA bid. We request the government to evaluate price at the task order level. | This RFQ is a small business set-aside. And as such, quoters must comply with applicable small business regulations, including the Nonmanufacturer Rule (NMR). Under the NMR, small business resellers must supply at least 51% of the final product from one or more small business manufacturers (13 CFR § 121.406), unless a waiver has been granted by the SBA. The government does not believe foundational technology vendors can rig the competition based upon how the RFQ is structured. Task orders will also be competed via LPTA. | ||
| 7 | If the offeror bids a 'suite' of tools for the AI Suite classification, which tool category will the government classify that 'suite' under? | There is a separate section in the price template to propose a suite of tools - it is considered a third category. | ||
| 8 | On page 67 of 70, in the solicitation document, the government provides a note on AI Suite of Tools. What is the difference between an 'AI Suite of Tool' and the Coding Assistant and Chat Function? | The AI Suite of Tools refers to a bundled offering that must include, at a minimum, the full functionality of both the AI-Powered Coding Assistant and the AI-Powered Chat Functionality as defined in the RFQ. In addition, the suite may include any other AI-based capabilities the vendor offers—such as data analysis tools, summarization engines, content generation tools, or other LLM-enhanced functionalities. The intent of the “suite” category is to allow agencies to license a broader and more integrated set of AI capabilities through a single offering, while still meeting the core requirements outlined for the Coding Assistant and Chat Function categories. | ||
| 9 | Can the government please provide an extension for this solicitation. | The amendment to the RFQ reflects a revised response date. | ||
| 10 | What specific benchmarks or validation datasets does Treasury expect vendors to use or provide to demonstrate compliance with performance requirements such as: | |||
| o | 200k token context window | |||
| o | Autocomplete relevance ≥95% across specified languages | |||
| o | Latency ≤1 second on standard hardware | Treasury expects vendors to provide validation datasets that reflect real-world, diverse use cases, including large-scale documents and multi-language content. For the 200k token context window, datasets should include long-form texts and complex queries. Performance benchmarks should be validated using both synthetic and production-like environments to ensure consistent autocomplete relevance and latency. Proposed support tools, analysis, or integrations need to be compatible with the primary programming languages used at Treasury, including Python, Java, JavaScript, C#, and Shell scripting. | ||
| 11 | Beyond the 24-hour deletion requirement upon admin request, is there a mandated maximum retention period for logs, prompts, and metadata? | Yes, retention requirements can vary depending on the regulatory requirements, and the nature of the data. | ||
| 12 | Are there any requirements for immutable audit trails or WORM (Write Once Read Many) storage for compliance audits? | No, there are no such expected requirements. | ||
| 13 | Should data deletion support recovery windows or be immediate and irreversible? | No, this is not currently required. | ||
| 14 | For integration with Treasury’s existing IAM systems via SAML 2.0 / ADFS, will Treasury provide test environments or sandbox identity providers for pre-award integration testing? | No- pre-award there will be no testing environments provided. Vendors should assume typical SAML based authentication support for intergration into Treasury's existing system(s). | ||
| 15 | Are there preferred or mandatory APIs/standards for integrating usage analytics and license management dashboards with Treasury’s internal monitoring tools? | OpenAPI (REST) and JSON are preferred standards for integrating usage analytics and license management dashboards. It's also preferred for the tool(s) to be integrated with ServiceNow modules to track licenses and API usage with minimal custom coding. | ||
| 16 | What level of advance notice is required for model updates beyond the stated minimum 14 days? | The default is acceptable. | ||
| 17 | • | Will Treasury require the ability to approve or reject certain updates before deployment? | No, this is not currently required. | |
| 18 | Are rollback capabilities mandatory for all updates, including minor patches? | No, this is not currently required. | ||
| 19 | • | Are there accessibility standards (e.g., Section 508 compliance) that the AI chat and coding assistant tools must meet for UI and documentation? | Yes. All AI tools proposed under this solicitation must comply with Section 508 accessibility standards as defined in 36 CFR, Appendix C to Part 1194. This includes applicable technical standards for: |
software functionality and user interface accessibility, support documentation and services, functional performance criteria, interoperability with assistive technologies. Vendors are required to submit Voluntary Product Accessibility Templates (VPATs) or equivalent accessibility documentation for each tool proposed. If any accessibility gaps exist, vendors must identify those areas and provide: documented workarounds, planned remediation timelines, or applicable exceptions. Failure to provide this documentation may render a quote ineligible for award. These Section 508 requirements apply to a;; tool interfaces and all related documentation and support services. For detailed requirements, please refer to: RFQ Pages 15–20: Section 508 Compliance Clauses and RFQ Page 61: Submission instructions for accessibility documentation.
| 20 | • | Is there an expectation for multilingual UI or output support beyond English in future phases? | No, there is no such expectation. | |
| 21 | •Besides quarterly reporting, will Treasury require real-time or near-real-time dashboards for usage, adoption, and security metrics? | No, the Treasury does not currently have that as a requirement. | ||
| 22 | •Are there specific KPIs or SLAs tied to user satisfaction or error rates that vendors should monitor and report? | In accordance with industry standards, vendors should monitor and report KPIs such as user satisfaction scores and error rates (e.g., system downtime, failed transactions) to ensure compliance with service quality expectations. SLAs should include metrics for response time, uptime, and resolution time for reported issues, with a gold standard of 99.999% uptime and minimal errors. These metrics, along with quarterly reporting, should be tracked and provided regularly to align with Treasury's performance and compliance requirements. | ||
| 23 | •For containerized or VM deployments, are there preferred orchestration platforms (e.g., Kubernetes) or configuration management tools Treasury uses or requires compatibility with? | The must be provided in or compatible with a K8S based environment such as ECS, FARGATE, or EKS. | ||
| 24 | Is bare-metal deployment support truly optional, or might it become a requirement for certain bureaus? | This is optional. | ||
| 25 | •How frequently does Treasury anticipate reviewing vendor roadmaps, and what format or level of detail is expected? | Treasury anticipates reviewing them yearly. High-level timelines and major feature releases would be the format/level of detail expected. | ||
| 26 | •Will Treasury consider pilot programs or proof-of-concept evaluations for emerging AI capabilities during contract performance? | Treasury may consider no-cost pilot programs or proof-of-concept evaluations for emerging AI capabilities during contract performance, provided they do not interfere with the delivery of contractually required capabilities. However, vendors should note that modifying the awarded contract to incorporate new technologies not contemplated in the original solicitation is unlikely, due to scope and funding constraints. Any such pilot or evaluation would be considered separate from the awarded contract scope and would require prior coordination and approval through the appropriate contracting channels. | ||
| 27 | • | Can Treasury clarify the process and timeline for reallocating licenses from inactive users to other bureaus? | Treasury expects that license reallocation for inactive users can be conducted efficiently through either a vendor-managed administrative portal or by contacting a designated vendor point of contact (POC). Reallocation should be completed within 48 hours of request submission, enabling bureaus to maintain continuity of access. This expectation is consistent with standard commercial practices where flexible and timely user reassignment is supported. | |
| 28 | • | Are there any restrictions on license transfers between bureaus or conditions that would trigger reallocation? | License transfers or reallocations between bureaus are dependent on the structure and terms of the specific order. If an order is issued to support multiple bureaus, there are generally no restrictions on reallocating licenses across those bureaus. However, if multiple distinct orders are issued (e.g., one per bureau), and a license needs to be transferred from one order to another, such a transfer would be subject to the scope and funding of the receiving order. In those cases, Treasury will evaluate whether the license movement aligns with the funding authority, scope of work, and intended beneficiary of the destination order. Vendors should support such transfers in coordination with the contracting officer or task order manager as appropriate. | |
| 29 | 1. | Would the Treasury department provide us the COBOL / PeopleSoft / proprietary data to fine-tune the models, we fine-tune them and provide them in a dedicated manner hosted in the cloud for each user via API. | ||
| 2. | Would the Treasury department provide us the COBOL / PeopleSoft / proprietary data to fine-tune the models, we fine-tune them and provide them to be downloaded via API and ran locally on each user's laptop. | |||
| 3. | None of the models should run in the cloud, be fine-tuned in the cloud and should be available via API for download and the Treasury department requests for functionality to fine-tune each model locally. | Treasury can share PeopleSoft and COBOL code (but it is not expected there is much COBOL codebase). |
File details come from the government source that posted it. Updated .