A production OT that operationalizes, scales, and sustains the advanced data engineering and analytics (DE&A) capability SBCC proved out under the DACC II prototype (FA6800-25-9-0001), awarded by the 767 Enterprise Sourcing Flight at Barksdale AFB. Critically, the agreement is written like an IDIQ: it is structured to let multiple government customers — AFGSC, HAF, and other DoD customers — place orders against the established DE&A scope, with dedicated AFGSC, HAF, and DoD-customer ALINs built into the funding structure. 

The predecessor prototype delivered six government-owned analytics solutions (PPlan/PMsg Action Item, STRATCOM Continuous Evaluation Program, Bomber Ecosystem Tool, AFGSC NC3 Cyber Security Tool, AOC Mission Tracker, and Aircrew Scheduling Tool) and codified a formal CONOPS as an addendum to the AFGSC DMAB/DACC charters — establishing the proven foundation this production OT scales.

DE&A solutions across the AFGSC data strategy's four core capabilities (dashboards/reports, automation/workflows, analysis, and prediction/decision support), an agile DevSecOps development and deployment process, testing and evaluation frameworks, AI/ML model and tooling work within native DoD platforms (Palantir Envision, Advana, the "Big Six"), data-literacy training, and sustainment of deployed use cases — all adhering to VAULTIS principles and scalable across AFGSC's 33,000 Airmen, 11 wings, and geographically separated units, with explicit reach to other DoD customers. 

Because this is a centralized OT written like an IDIQ, a customer cannot order directly. The requirement owner must first route a requirement package — scope of work derived from the agreement, a funding document, and a designated AOR — to the Agreements Officer, and AFGSC/A9 must approve use of the agreement as the Chief AOR (the requirement owner retains oversight of its own effort). The customer then defines the work in a short (~2-page) Customer Requirement Order (CRO) pulling from the Task Description Document, identifying funding type (R&D/O&M), travel, and customer type. SBCC submits a technical and price proposal against the established LCAT rates, and once scope and level of effort are agreed, the CRO is added to the agreement via a funded ASLIN and executed by the single assigned 767 ESF Agreements Officer 

Directed.

As a follow-on production OT under 10 U.S.C. § 4022(f), work flows to SBCC sole-source with no competition — SBCC is the only performer on the agreement. The IDIQ-like construct simply governs how multiple customers reach that single performer: any AFGSC, HAF, or DoD customer can place a CRO against the established scope, but every order is vetted and approved by AFGSC/A9 and written by the single 767 ESF Agreements Officer. This is not a FAR contract and is not subject to the FAR or its supplements 

Production-scale digital transformation; operationalizing prototyped analytics/decision-support capabilities; sustainment and scaling of digitally engineered solutions. 

A fast, direct, and streamlined path to contract for Air Force (and broader DoD) data-transformation and CE&I production work — AFGSC has already stood up this single-award OT using our authority, so the vehicle is in place and ready. Lead with the proven lineage (six fielded, government-owned solutions and a codified CONOPS) and the runway through 2033. Set expectations honestly: ordering runs through an AFGSC/A9-approved CRO and the single 767 ESF Agreements Officer, and a new customer's funding must align to purpose (R&D vs. O&M) before work starts. 

Production-phase digital transformation — taking a capability that was proven in the OT prototype and producing, fielding, scaling, and sustaining it for the Air Force. Think operationalizing prototyped analytics/decision-support capabilities and sustaining digitally engineered solutions at scale. 

Beyond core DE&A, the agreement carries commercial-engagement and integration (CE&I) work tied to digital transformation. The scope expressly includes scouting and evaluating commercial analytics solutions to benchmark native vs. commercial technologies, implementing expert systems leveraging commercial and enterprise platforms (e.g., Salesforce, ServiceNow, Oracle Cloud), conducting market research and technology scouting for state-of-the-art IT solutions, recommending acquisition strategies for commercially available solutions, facilitating the Authority to Operate (ATO) process for those solutions, and providing project-management integration support for commercial tools — collaborating with AFGSC/A9 innovation branches and Air Force Spark Cells. This makes the OT a natural complement to the CEI-RADS IDIQ — the same commercial-engagement DNA, applied to data modernization production work. 

Scope is tethered to the prototype lineage – this is the production continuation, not a blank-check services vehicle. It requires AFGSC/A9 approval to use and a warranted agreements officer to award. Brand-new work unrelated to the prototyped capability does not belong here. 

Scope is tethered to the prototype lineage and DE&A/CE&I mission — not a general services vehicle. Ordering requires AFGSC/A9 approval and a warranted Agreements Officer (not a standard FAR CO). Funding is incremental and purpose-bound (O&M for sustainment/operations; RDT&E for development/maturation), and no work begins until properly aligned funds are obligated 

Air Force, HAF, or DoD customer + the need is data engineering/analytics or CE&I production work that derives from the DACC II prototype scope + the requirement owner can route a CRO package (scope, funding, designated AOR) for AFGSC/A9 approval + funding aligns to purpose (O&M for sustainment/operations, RDT&E for development) → fit, executed sole-source by the single 767 ESF Agreements Officer. If the customer wants a brand-new prototype rather than scaling/sustaining a proven capability, that's the OT Prototype Authority path, not this agreement.