2032L2-26-X-0001 AIMAS SOO RFI Attachment 1.docx

2032L2-26-X-0001 Attachment 1 DRAFT Department of the Treasury - Treasury Common Services Center (TCSC) AI Model Access Services (AIMAS) Statement of Objectives (SOO)

1 BACKGROUND

1.1 Purpose. The Department of the Treasury requires direct access to frontier large language model (LLM) artificial intelligence capabilities. This contract will provide scalable, secure, API-based access to AI models for authorized government users to support mission objectives including software development, data analysis, research, and operational efficiency.

1.2 Scope. This resulting award will be available Treasury wide and to other federal agencies.

1.3 Primary Use Case. The primary use case is software development augmentation, encompassing code generation and completion, code review, analysis, and debugging, test case generation, documentation generation, and security vulnerability identification, while secondary use cases include document analysis and summarization, data extraction and transformation, research assistance, natural language processing, and content generation and editing.

1.4 Key Terms.

· Tokens: Units used to measure model processing and generation for consumption metering.

· Model version: Identifier for a specific deployed model release or build.

· Government data: Government-provided or Government-generated prompts, context, files, and outputs.

2 OBJECTIVES

2.1 Primary Objective. Provide authorized government users with scalable, secure, programmatic (API) access to Frontier AI language models that meet or exceed qualification benchmarks for capability, reliability, and security.

2.2 Performance Objectives. The Contractor shall provide AI model access services that achieve:

Note: For purposes of latency measurement, a "standard request" is an interactive API call within Government-defined input and output size thresholds (for example, up to a specified prompt plus context size and a specified maximum response size). The Contractor shall propose measurement assumptions and capture methodology in the initial benchmarking report.

2.3 Capability Objectives. The Contractor shall provide AI models with demonstrated capability in:

Software Engineering: The capabilities include multi-language code generation across Python, JavaScript, Java, C++, Go, Rust, and other languages, along with code completion and intelligent suggestions, bug detection and remediation recommendations, security vulnerability identification, unit test generation, documentation generation from code, and code refactoring and optimization suggestions.

General Intelligence: The system supports natural language understanding and generation, document analysis, summarization, and extraction, advanced reasoning and problem-solving, multi-turn conversational interaction, context retention across extended sessions, and task decomposition and planning.

2.4 Security Objectives. The Contractor shall provide services that meet FedRAMP Moderate authorization requirements, or an equivalent Agency Authority to Operate, process and store all data exclusively within the Continental United States, and ensure that government data is not retained beyond immediate processing needs. The services shall not use government input or output data for model training or improvement without explicit written consent, shall comply fully with the requirements of Executive Order 14110, and shall support robust continuous monitoring, logging, and incident response capabilities to promptly detect, report, and remediate security incidents.

2.5 Integration Objectives. The Contractor shall provide RESTful API access that adheres to industry standards, supported by comprehensive and well-maintained API documentation, and offer SDKs for common programming languages to facilitate rapid integration. The services shall support secure authentication mechanisms, including API keys and OAuth 2.0, provide detailed usage metering and reporting capabilities for monitoring and governance, and include integration support tailored to government development environments and tooling.

3 MANDATORY PERFORMANCE REQUIREMENTS

3.1 Security Requirements

3.2 Compliance Requirements

3.3 Data Handling Requirements

· Government retains all rights to input data and generated outputs

· Contractor shall not retain government data beyond immediate session processing

· Contractor shall not use government data for model training, fine-tuning, or improvement without explicit written consent at the task order level

· Contractor shall provide data extraction capabilities upon request

· Contractor shall securely delete all government data upon contract or task order termination

3.4 Operational Requirements

· Services shall be accessible from government networks (including VPN)

· API rate limits shall accommodate government usage patterns

· Service maintenance windows shall be scheduled outside core business hours when possible

· Emergency maintenance permitted with immediate notification

· Exportable token consumption reports

· Service maintenance windows shall be scheduled outside core business hours when possible

· Emergency maintenance permitted with immediate notification

· Exportable token consumption reports

4 DELIVERABLES

4.1 Initial Deliverables (within 30 days of contract award)

4.2 Ongoing Deliverables (may be provided through a customer portal)

4.3 Transition Deliverables (upon contract conclusion)

5 PERIOD OF PERFORMANCE

5.1 Ordering Period

· Base Period: One (1) year from date of award

· Option Period 1: One (1) year

· Option Period 2: One (1) year

· Option Period 3: One (1) year

· Option Period 4: One (1) year

· Total Potential Period: Five (5) years

5.2 Order Performance

· Orders may be issued throughout the contract ordering period

· Order periods of performance will be specified in each order

· Orders will address token carry over/expiration

· Orders issued prior during the active ordering period of the contract remain valid through their specified performance period, even after contract expiration

5.3 Transition Period

· 180-day transition period required upon contract conclusion or off-ramp

· Contractor shall support transition to successor provider(s)

· Full cooperation required for data migration and knowledge transfer

6 PLACE OF PERFORMANCE

6.1 General. All performance under the contract is expected to be undertaken at the contractor’s place of business.

6.2 Service Delivery. Services shall be delivered via cloud-based infrastructure from Contractor facilities. All data processing and storage shall occur within the continental United States.

6.3 Support Services. As permissible under the contract, support services may be required. Services will likely be provided remotely but on-site support may be requested for specific orders.

7 GOVERNMENT-FURNISHED ITEMS

7.1 Government-Furnished Information. The Government will provide, as necessary, access to Government networks and environments to support API integration, testing, and validation activities associated with token-based access.

7.2 Government-Furnished Equipment. No government-furnished equipment is anticipated to be needed/provided under this contract.

8 CONTRACTOR RESPONSIBILITIES

8.1 Service Delivery

· Maintain API availability per SLA requirements

· Provide adequate capacity for contracted usage levels

· Implement security controls per FedRAMP/authorization requirements

· Respond to and resolve service incidents promptly

· Maintain model performance at or above benchmark qualification levels

8.2 Communication

· Provide 24/7 emergency direct human contact for critical issues

· Respond to routine inquiries within 1 business day

· Notify Government of planned maintenance 72 hours in advance

· Notify Government immediately of security incidents

8.3 Continuous Improvement

· Provide access to model updates and improvements

· Maintain competitive pricing aligned with market trends

· Implement security enhancements as threats evolve

· Support Government adoption of new capabilities

9 QUALITY ASSURANCE

9.1 Performance Standards

9.2 Performance Remediation

· Contractor shall provide root cause analysis for SLA failures.

· Contractor shall implement corrective actions within agreed timeframes.

· Persistent failures may result in contract off-ramp or other contractual remedies.

10 APPLICABLE DOCUMENTS

The following documents are incorporated by reference:

11 COMMUNICATIONS

Effective communication between the contractor and the Government is essential to the success of this IDIQ. The contractor shall maintain regular coordination with the Contracting Officer’s Representative (COR), the Program Office, and other designated officials to ensure transparency and timely resolution of issues. Meetings may be conducted virtually or in person as specified in each Task Order.

The contractor shall provide timely responses to all Government inquiries, normally within two business days, and ensure that all required participants attend scheduled meetings. All virtual meetings shall include video participation unless otherwise approved by the COR. The contractor shall maintain open lines of communication throughout all phases of performance to support collaboration, accountability, and mission success.

12 SECURITY

TBD

13 CONTRACT ADMINISTRATION

TBD