CAISI would benefit from more resources, OSTP director tells lawmakers

TL;DR

Bipartisan legislation (H.R. 9363) to codify the Center for AI Standards and Innovation (CAISI) into law is advancing through Congress, and lawmakers are discussing increasing CAISI’s funding from the current $20 million annually to as much as $100 million. CAISI — formerly the AI Safety Institute — is responsible for testing and evaluating AI models and setting standards that affect government contractors using AI technologies. If enacted with expanded resources and statutory authority, CAISI’s scope for testing, validation, and standards-setting is likely to grow, increasing compliance and technical verification demands on contractors. Immediate implications: contractors in AI, ML, IT, cybersecurity, cloud, and related R&D should assume heightened scrutiny of AI systems used in government work, reassess capture and compliance plans, and prepare for more rigorous testing requirements. Monitor H.R. 9363’s progress and configure opportunity pipelines to surface CAISI-related requirements; align proposal and technical teams to close likely gaps in security, testing, and documentation.

Key Points

• What happened: Bipartisan legislation (H.R. 9363) to codify CAISI into law is advancing, with discussions to raise funding from $20 million annually toward $100 million.
• Who is affected: NAICS codes 541512, 541511, 541715, 541330, 541690, 518210, 334111, 541713; agencies NIST, DOD, DHS (Department of Homeland Security), GSA (General Services Administration), DOE, HHS, VA, DOJ; contract vehicles OASIS+, CIO-SP4, SEWP, 8(a) STARS III, Alliant 3, GSA MAS; market segments include Artificial Intelligence, Machine Learning, AI Safety and Testing, IT Services, Cybersecurity, Data Science, Software Development, Cloud Computing, Research and Development; compliance surfaces include NIST AI Risk Management Framework, FedRAMP (Federal Risk and Authorization Management Program), NIST 800-53, CMMC (Cybersecurity Maturity Model Certification), FISMA, NIST 800-171 (NIST Special Publication 800-171), OMB AI Guidance.
• Timeline: Timeline TBD pending source review.
• What contractors should do NOW: inventory AI systems and data flows used on government work, begin gap analysis against the listed compliance surfaces, prioritize capture opportunities that touch CAISI-relevant capabilities, and stand up monitoring and proposal readiness processes to respond quickly to CAISI-driven solicitations.

Who Is Affected

Contractors delivering AI, machine learning, IT services, cybersecurity, cloud, and R&D support to the federal government are the primary audience. Specific NAICS codes, agencies, and contract vehicles listed in the segmentation are likely to see the most direct impact: 541512; 541511; 541715; 541330; 541690; 518210; 334111; 541713; NIST; DOD; DHS; GSA; DOE; HHS; VA; DOJ; and contract vehicles OASIS+, CIO-SP4, SEWP, 8(a) STARS III, Alliant 3, GSA MAS. Compliance regimes named in the segmentation (NIST AI RMF, FedRAMP, NIST 800-53, CMMC, FISMA, NIST 800-171, OMB AI Guidance) should be treated as relevant surfaces for readiness activities.

Frequently Asked Questions

Q: What is H.R. 9363 and what does it do?

A: H.R. 9363 is bipartisan legislation to codify the Center for AI Standards and Innovation (CAISI) into law. The bill is advancing through Congress and aims to formalize CAISI’s statutory authority. Further legislative details and statutory language are pending source review.

Q: Will CAISI get more funding?

A: According to the reporting summarized here, lawmakers are discussing increasing CAISI’s funding from the current $20 million annually to potentially $100 million. Final appropriations and statutory funding levels are pending source review.

Q: How will this affect contractor obligations and procurement processes?

A: The Summary indicates that increased resources and formal statutory authority will likely expand CAISI’s regulatory reach and testing requirements for AI systems used in government contracting. Specific new compliance requirements, timelines, or testing protocols are pending source review.

Definitions

• CAISI: Center for AI Standards and Innovation — an entity responsible for testing and evaluating AI models and setting standards; formerly the AI Safety Institute.
• H.R. 9363: Bipartisan legislation referenced in the Summary that would codify CAISI into law.
• AI Safety Institute: The former name for CAISI as noted in the Summary.
• OSTP director: The Director of the Office of Science and Technology Policy, referenced in the Title as speaking to lawmakers about CAISI’s resourcing.

Intelligence Response

• Cabrillo products to leverage:
• Cabrillo Signals War Room — Already detected this event and delivered this briefing. Use it to maintain continuous monitoring of H.R. 9363 progress, congressional activity, and policy signals that affect CAISI’s mandate.
• Cabrillo Signals Match Engine — Rescore pipelines and opportunities that involve AI, ML, and testing services to reflect increased CAISI influence and potential funding shifts.
• Cabrillo Signals Intelligence Hub — Configure saved searches to track solicitations and notices from the agencies listed in the segmentation; alerts will surface follow-on solicitations and RFI/RFQ activity.
• Proposal Studio (Proposal OS) — Update compliance matrices and win themes to reflect likely CAISI testing and standards requirements; use the proposal automation to accelerate responses.
• Proposal Studio Workflow Tracker — Activate the 9-gate capture process for high-priority opportunities and ensure automated compliance routing and audit-ready documentation.
• Who to notify:
• Capture Manager — immediate bid/no-bid and resourcing decisions.
• BD Director/Business Development — adjust pipeline priorities and pursue CAISI-relevant opportunities.
• CTO/Technical Lead — lead technical gap analyses on AI/ML systems and testing readiness.
• Security/Compliance Officer — validate alignment with NIST AI RMF, NIST 800-series, FedRAMP, CMMC, and OMB AI Guidance.
• Proposal Lead — update proposal artifacts and compliance matrices.
• First 48-hour playbook:
• Hour 0–4: Triage and notify the capture and executive team; declare a watch on opportunities touching AI/ML and CAISI-relevant work. Confirm Signals War Room alert subscription.
• Hour 4–12: Run an automated rescore of current pipeline with the Signals Match Engine to reprioritize opportunities; push high-priority hits to Proposal Studio.
• Hour 12–24: CTO and Security/Compliance Officer begin a focused gap analysis against NIST AI RMF and the other compliance surfaces listed; document gaps in Proposal Studio compliance matrices.
• Hour 24–48: Convene capture stand-up for top-priority opportunities via Proposal Studio Workflow Tracker; assign owners for remediation tasks and schedule follow-on monitoring via Signals Intelligence Hub saved searches. Reference the Winning Federal Contracts Guide for capture best practices and the CMMC Compliance Guide (/insights/cmmc-compliance-guide) and CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide) for compliance and CRM handling of controlled information.

Primary hub: Winning Federal Contracts Guide (/insights/winning-federal-contracts)