250505 Dist A - Agile Professional Services Industry Day.pdf

Distribution Statement A. Approved for public release: distribution unlimited

Agile Professional Services Industry Day

May 12, 2026

Controlled by: Army

Controlled by: CPE ST3

CUI Category: Distro A

Distribution/Limited Dissemination Control: Unlimited

POC: Rodney Figaroa, 520-692-3794

Agenda

• Purpose

• Background

• Executive Orders, Directives driving change

• New Approach

• Contract Strategy and Structure

• Construct – Agile Program Management

• Requirements

• Selection Approach

• Draft Timeline

Purpose

• Provide Industry with planned approach for transformation of the competitive Agile Professional Services (APS) requirement, previously SETA.

Background

• Department of War and Army Acquisition Transformation Initiatives demand a change in how we contract for services

• Agile, Flexible, Responsive and Effective

• The key to success of this contract is continued transformation into Agile Program Management

• Adopt a task-based, outcome focused, and capability centric approach

• Enables flexibility, responsiveness and scalability

• Provide accountability to Performance Based methodologies

Executive Orders and Directives driving the change….

• Army Directive 2024-02, Enabling Modern Software Development and Acquisition Practices

• Emphasizes the adoption of agile methodologies, modern software practices, and the elimination of outdated institutional processes.

• Executive Order (E.O.) 14222, Implementing the President’s “Department of Government Efficiency” Cost Efficiency Initiative

• Emphasizes fiscal responsibility, transparency, and the elimination of waste in federal contracting and requires agencies to justify the necessity of service contracts and prioritize in-house capabilities

• SECDEF’s Memorandums with limitations on new contracts or task orders for consulting, advising, assisting, or any professional services performing similar functions

• E.O. 14240, Eliminating Waste and Savings Taxpayer Dollars by Consolidating Procurement

• Directs agencies to consolidate procurement of common goods and services under the General Services Administration (GSA) to eliminate duplication and inefficiencies.

• E.O. 14271, Ensuring Commercial, Cost-Effective Solutions in Federal Contracts

• Requires agencies to prioritize commercially available solutions

• E.O. 14402, Promoting Efficiency, Accountability, and Performance in Federal Contracting

• Establishes that executive branch departments and agencies shall, in procurement, maximize the use of fixed-price contracts

New Approach - Was vs To-Be

• Focus on output-based vs staffing positions (no “butts in seats”)

• Output needs to be tangible, definable, measurable (aka “Definition of Done”)

• Output based dashboards enabling Data Driven visibility, prioritization and decisions

• Contract for highly specialized skills not easily sourced or cost effective within organic formations vs broad functions or mandated Government functions

• Examples – Cloud Architect, Data Visualization, DevSecOps Eng

• Don’ts - System engineers, Program Manager, Administrative support

• Move towards an Enterprise Capacity model vs dedicated assignment to a Project/Product Office

• Enables alignment of resources against enterprise priorities

• Flexibility to surge unique and critical expertise

• Commercial Solution vs custom developed support services

Contracting Strategy and Structure

• Considering existing GSA vehicle or MAPS to award two commercial task orders

• Transforming from nine to two Task Orders that are capability aligned

• Technical and Acquisition Support Capabilities – supporting PM/PL shops

• Staff capabilities – supporting G-staff functions

• Requirement will focus on skill/expertise/service that may be needed during the course of the Task Order

• Tasks to be execute will be during Program Increment Planning and further refined during Spring planning

• Period of Performance: TBD

• Contract Type: Pending final determination between T&M and FFP

• CLIN Structure will be aligned to Appropriation type and/or Physical Locations

• RDTE, OMA, PROC, FMS

• CDRLs: Moving away from traditional submissions

• One Cost Report per Task Order

• Agile Dashboard/Knowledge Management Portal (where all Deliverables will be “delivered” and all status updates will be provided)

• Transition Plan (for transition in/out)

• Must fall in and use the current Government JIRA instance

Construct – Agile Program Management

• Agile Enterprise Management of Tasks

• Each PM/PL / HQ function prioritizes their tasks in Jira

• Contractor will estimate hours/resource required to complete tasks and enter in

Jira

• CPE (or designee) will prioritize task backlog at the Enterprise level quarterly, potentially resulting in contractor resources “moving” across the enterprise

• CPE level retrospective executed quarterly to see what was accomplished from the planned tasks and define the plan for the next quarter

• QASP will define Performance Standards for tasks

Requirements Construct for Acquisition and Technical Support Capabilities

• Key Personnel – Agile Program Manager

• Acquisition Task “Buckets” (not comprehesive)

• Resource and Operations Execution

• Risk Management Analysis

• Documentation Streamlining

• Military Doctrine Analysis

• Product Support Execution

• Business Manager Support

• Management Process Support

• Knowledge Management

• FMS Unique Requirements

• Test and SOF Unique Requirements

Degree or certificate requirements with requisite experience MUST be met for certain labor categories Degree/Certificate must be in an equivalent field. Ex. Civil Engineer is not the same as a Software Engineer

Requirements Construct for Acquisition and Technical Support Capabilities (cont)

• Technical Task “Buckets”

• Cloud Architect

• Combat Training Center Engineering

• Configuration Management

• Cyber Security Engineering

• Data Engineering

• DevSecOps Engineering

• Enterprise Architecting

• Geospatial Data Engineering

• Live Collective Aviation Engineering

• Network Engineering

• Process Improvement

• Requirements Engineering

• RF/Communication Engineering

• Safety Engineering

• Software Engineering

• Systems Architecting

• Technology Integration Engineering

• Test Engineering

• Virtual Aviation Engineering

• Visual Engineering

Degree or certificate requirements with requisite experience MUST be met for certain labor categories Degree/Certificate must be in a equivalent field. Ex. Civil Engineer is not the same as a Software Engineer

Requirements Construct for Staff Support Capabilities

• Key Personnel – Agile Program Manager

• Staff Task “Buckets”

• Plans, Programs and Resourcing

• Enterprise Operations

• Management Process Support

• Security in Stand alone Facilities, Physical Security, Emergency Management, Antiterrorism/Force Protection

• Facilities, PBO

• ITAS requirements, Cybersecurity training compliance, spectrum certification, host nation frequency coordination, liaison to Network Enterprise Center

** NOTE: OCI Firewall shall be established between performance under the HQ/G-staff Task Order and future CPE ST3 competitive efforts

Degree or certificate requirements with requisite experience MUST be met for certain labor categories Degree/Certificate must be in a equivalent field. Ex. Civil Engineer is not the same as a Software Engineer

Selection Approach

• Phased selection approach (not representative of evaluation factors)

• Phase 1 – Agile Services Concept Paper

• Focus Area

• Enterprise Capacity model

• Agile Services (or relevant) Past Performance

• Key Personnel: Agile Program Manager

• Transparency & Metrics Implementation

• Transition Plan (In/Out)

• Phase 2 – Oral Presentation and Live Demonstration

• Focus Area

• Conduct Mock Agile Ceremony

• Live JIRA Demonstration

• Dashboard

The Government will not evaluate Phase 2 preparations during Phase 1, but Offerors should only submit a Phase 1 Concept Paper if they are fully capable of executing the Phase 2 Live JIRA Demonstration

Selection Approach

• Use of AI tools in support of the Evaluation is being considered

• The Government may employ AI as a tool to assist in the analysis and review of the offerors proposals. AI tools may be used to support tasks such as summarizing proposal content, identifying compliance with request for task order proposal / solicitation requirements, and highlighting areas of potential strengths, weakness, or risks.

• Maintaining Inherently Governmental Function:

• Notwithstanding the use of AI tools to support the evaluation process, all final evaluation judgements, including the assignment or assessment of adjectival ratings, best value determination, and source selection decisions, will be made exclusively by duly appointed Government personnel. The Government retains sole responsibility for all inherently Government functions and will not delegate decision making authority to an AI tool.

• Offeror Confidentiality and Data Protection:

• The AI tools utilized by the Government will be employed in a manner consistent with applicable regulations that govern the protection of proprietary and source selection sensitive information. The AI tool will be an output-only system. Any generated report data is not saved. No proposal data will be transmitted to or processed by external, non-Government systems without appropriate safeguards and authorizations in place

Draft Timeline

4/1 RFI Release

7/2026 Final RFP Release

6/15 Draft RFP Release

4/13 RFI Close

5/12 Industry Day

8/2026 Proposals Due

8/2026 Down Select

9/2026 Decision

10/2026 Award 2/15 Full Performance

Start

NOV Performance Start

Back Up