ICE IT shop looks to build ‘agentic software factory’

TL;DR

ICE has issued an RFI to build an "agentic software factory" that uses AI agents to perform large portions of the software development lifecycle, expanding its existing STELLA platform. The RFI asks vendors to provide AI application development, workforce training, continuous monitoring, and technology evaluation services, and explicitly requests methods to distinguish genuine vendor capabilities from AI-generated proposals. Responses are due October 16, 2024. This represents a near-term opportunity for contractors in IT services, AI, software development, DevSecOps, and training to engage with ICE/DHS (Department of Homeland Security) modernization efforts, but it raises new capture and technical validation challenges. Contractors should immediately inventory demonstrated AI/automation capabilities, prepare verifiable demonstrations and human oversight plans, map controls to relevant compliance surfaces, and begin capture activities. Use Cabrillo Signals to detect follow-ons, rescore pipelines, and Proposal Studio to organize compliant responses.

Key Points

• What happened: ICE issued an RFI to build an "agentic software factory" that leverages AI agents across the software development lifecycle and will expand the STELLA platform; vendors must provide AI application development, workforce training, continuous monitoring, and technology evaluation services.
• Who is affected: Contractors in IT Services, Artificial Intelligence, Software Development, DevSecOps, Training and Education, and Homeland Security; specific NAICS codes: 541511, 541512, 541519, 541611, 541690, 611420; agencies: DHS, ICE; contract vehicle: STELLA; compliance surfaces: NIST 800-171 (NIST Special Publication 800-171), FedRAMP (Federal Risk and Authorization Management Program).
• Timeline: Responses are due October 16, 2024.
• What contractors should do NOW: begin capture planning, assemble verifiable capability demos and human-oversight documentation, prepare workforce training and continuous monitoring offerings, map compliance to NIST 800-171 and FedRAMP, and configure Cabrillo Signals and Proposal Studio to track and respond.

Who Is Affected

Contractors offering IT services, AI application development, DevSecOps, software engineering, continuous monitoring, and training are the primary audience. Explicitly named items from segmentation include NAICS 541511, 541512, 541519, 541611, 541690, 611420; agencies DHS and ICE; contract vehicle STELLA; and compliance surfaces NIST 800-171 and FedRAMP. Organizations that do not match these segments should monitor for follow-on opportunities. Specific NAICS codes, agencies, and contract vehicles beyond those listed above pending source review.

Frequently Asked Questions

Q: What exactly is ICE asking for in this RFI?

A: ICE requests input for an "agentic software factory" that uses AI agents to perform significant portions of the software development lifecycle, expanding the STELLA platform, and requesting vendor capabilities in AI application development, workforce training, continuous monitoring, and technology evaluation. The RFI also asks vendors for methods to differentiate genuine capabilities from AI-generated proposals.

Q: Who should consider responding to this RFI?

A: Contractors that match the listed market segments and NAICS codes in the segmentation (541511, 541512, 541519, 541611, 541690, 611420) and that can provide AI application development, training, monitoring, and technology evaluation should plan capture activity. Specific eligibility rules for formal solicitations are pending source review.

Q: How should vendors show they are not submitting AI-generated or hollow proposals?

A: ICE is explicitly seeking methods to differentiate genuine vendor capabilities from AI-generated proposals. Vendors should prepare verifiable evidence of capabilities such as human-reviewed artifacts, live demonstrations, audited provenance of deliverables, workforce validation plans, and continuous monitoring approaches. Specific evaluation criteria from ICE are pending source review.

Definitions

• Agentic software factory: An environment or platform that employs autonomous or semi-autonomous AI agents to carry out substantial parts of the software development lifecycle.
• AI agents: Software entities that perform tasks autonomously or semi‑autonomously, here applied to software development activities.
• STELLA: The existing ICE platform referenced in the RFI that the agency plans to expand.

Intelligence Response

Cabrillo Signals War Room has detected this RFI and delivered this briefing. Use the following Cabrillo products to operationalize a capture and response:

• Cabrillo Signals War Room — already detected this event and delivered this briefing; continue real-time monitoring for updates, amendments, or follow-on solicitations.
• Cabrillo Signals Match Engine — rescore your opportunity pipeline immediately to reflect elevated priority for ICE/STELLA-related work and to reprioritize pursuits against competitors with AI agent capabilities.
• Cabrillo Signals Intelligence Hub — create saved searches for ICE/STELLA, the specified NAICS codes, and compliance triggers (NIST 800-171, FedRAMP). Set alerts for SAM.gov (System for Award Management) postings and amendments.
• Proposal Studio (Proposal OS) — build an RFI/RFP response skeleton with compliance matrices, provenance documentation templates, and win themes tailored to AI agent authenticity and human oversight.
• Proposal Studio Workflow Tracker — instantiate a 9-gate capture workflow to manage approvals, compliance routing, and audit-ready documentation for any formal solicitation that follows.

Notify these roles immediately: BD/Capture Lead (assign ownership), CTO/AI Lead (technical validation), Security & Compliance Lead (NIST/FedRAMP mapping), Training/Product Lead (workforce plans), and Proposal Manager (response orchestration). Reference the Winning Federal Contracts Guide (/insights/winning-federal-contracts) and related guidance such as the CMMC (Cybersecurity Maturity Model Certification) Compliance Guide (/insights/cmmc-compliance-guide) and CUI (Controlled Unclassified Information)-Safe CRM Guide (/insights/cui-safe-crm-guide).

First 48-hour playbook

• Hour 0–4: Ingest RFI into Cabrillo Signals; create saved searches and alerts in Intelligence Hub; notify BD/Capture Lead and assign Proposal Studio workspace.
• Hour 4–12: Run Match Engine to rescore pipeline; conduct rapid capability inventory and gap analysis against RFI requirements; begin compliance mapping to NIST 800-171 and FedRAMP.
• Hour 12–24: Draft high-level response outline in Proposal Studio, assemble evidence packages for verifiable demonstrations, and design workforce training and continuous monitoring approaches.
• Hour 24–48: Lock capture team roles, schedule live demo plans and provenance exhibits, run Workflow Tracker gates for initial compliance and executive review, finalize decision memo for bid/no-bid or next-step engagement.