ACWS_INDUSTRY_DAY_FINAL.pdf

Army Contract Writing System

(ACWS)

Industry Day

23-July-2026

ACWS Enables Speed Through Contracting OCTOBER 1, 2025

"DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited."

Mr. Doug Haskin

Project Manager

Acquisition, Training & Readiness

Ms. Sabrinna Cosom

ODASA(P) Functional Sponsor Ms. Karen Loss

Contracting Officer

Opening Remarks

AT&R| ACWS

2Briefer: LTC Morgan

Distribution &

Publication

• This brief is marked “Distribution Statement

A. Approved for Public Release, Distribution

Unlimited”.

• The Government will not publish Industry-

Proprietary questions/comments or their responses.

• The Government intends to publish Industry-

General frequently asked questions (FAQs) with Government-prepared responses.

• The “final” version of these slides and a list of the registered companies will be posted to www.SAM.gov

Acquisition &

Authority

• Nothing presented in this Industry Day commits the U.S. Army to any acquisition approach, agreement, or contract.

• Any future published opportunity will take precedence over information presented today or in response to questions.

Resources &

Follow-On Actions

• Post-Industry Event Questions Link:

https://forms.osi.apps.mil/r/KEDeJyk6 w6

• Call for Solutions on SAM.gov:

https://sam.gov/opp/0db7f0a354f1456

6b43baea1afb93d15/view

MODERATOR ENFORCEMENT CHECKLIST

✓ Start with rules reminder ✓ Monitor chat actively ✓ Enforce time limits ✓ Address disruptions immediately ✓ Document action items

Rules of Engagement (RoE)

AT&R| ACWS

Briefer: Ms. Karen Loss https://forms.osi.apps.mil/r/KEDeJyk6w6 https://forms.osi.apps.mil/r/KEDeJyk6w6 https://sam.gov/opp/0db7f0a354f14566b43baea1afb93d15/view https://sam.gov/opp/0db7f0a354f14566b43baea1afb93d15/view

Time

11:00-11:05

11:05 - 11:25

AT&R| ACWS

Agenda

11:25 - 12:00

12:00 - 12:10

12:10 - 12:30

Speaker Objective

Contracting Officer

Product Manager (PM)

PM, DPdM, VCE, and

Functional Sponsor

Contracting Officer

KO (Moderator) & PM

Set ground rules. Emphasize that verbal remarks are non-binding and outline how formal Q&A will be handled via SAM.gov

Explain the strategic vision. Discuss the transition from legacy systems

(SPS/PADDS) to ACWS and the need for modernization

Walk through the Requirements

(Contractor Accountability, IL-6

Implementation, VCE Merger, Continuous Capability Delivery)

Topic

Explain the Phased approach and evaluation process

Answer pre-submitted questions first. If time permits, answer live questions.

Defer complex technical questions to the formal SAM.gov written Q&A

Briefer: Ms. Karen Loss 4

Welcome & Rules of Engagement

PM Introduction & Problem Statement

Deep Dive: Requirements

Submission & Evaluation Process

Moderated Q&A

DEPUTY PRODUCT MANAGER

MR. AARON KOCHANSKI

▪ Problem Statement

▪ ACWS Stakeholders

▪ ACWS Mission

▪ Requirements & Objectives

▪ Submission Details

▪ Submission Details File Structure

▪ Phased Evaluation Process

AT&R| ACWS

ACWS Overview

5Briefer: Mr. Aaron Kochanski 5

▪ Despite successfully replacing legacy contract writing systems, the Army Contract Writing System (ACWS) remains constrained by compounding technical debt that limits the agility of its 9,000 global enterprise users.

▪ To bridge these gaps, ACWS urgently requires commercial Low

Code/No Code (LCNC) and AI/ML technologies to establish secure, real time data flows between core writing systems, legacy financial repositories, and compliance heavy environments like PIEE.

▪ Ultimately, the Army must resolve this underlying technical debt and transition raw contracting data into an active strategic asset without disrupting active, worldwide contracting operations.

Briefer: Mr. Aaron Kochanski

Revolutionize Army Contracting!

Eliminating Technical Debt to

Unleash AI/ML Capability!

Recompete Scope

Mission: Deliver a world class, single, enterprise-wide contract writing and management solution at the speed of relevance. Capable of meeting the current and future non-classified, classified, and disconnected state missions of the Army contracting community.

Enables the full Contract Procurement Lifecycle - from Requirements Submission to Contract Closeout.

• Sunset SPS-A on 15 December 2025

• Fielded to over 9,000 Global Contracting Professionals

• Annual sustainment savings of $29M from legacy systems

(SPS-A~ $20M / PADDS ~ $9M)

• Over 62,331 contract files migrated from legacy systems to

ACWS.

• Executed over 177,120 contract actions

• Obligated $61B in native actions and $243B on migrated actions

By the Numbers

Fast Facts

ACWS is the system that facilitates contract execution, from submission to close-out.

• ROI realized by leveraging CONIT Baseline

• Scalable improvements over Legacy Systems

• Minimum Viable Product (MVP) August 2023

• Enforce Data Standards, Audit and Compliance

Readiness.

• Cloud enabled (Hosted in DLA/PIEE) and in alignment with modernized system operation

• Enhanced data sharing and interoperability

ACWS Technology Stack

• Developed using Appian (Low Code/No Code)

• Shared code between Services

• VCE is being refactored into the Appian platform

• Automate AI within Appian Platform

• Interfaces with sister services - 1st Program and

CWS to Interface with the Corps of Engineers

Financial Management System (CEFMS).

Enables the Full Contract Procurement Lifecycle - from Cradle to Grave

The Army Contract Writing System (ACWS)

Briefer: Mr. Aaron Kochanski

ASA(ALT) | DASM

The Army Contract Writing System (ACWS): ACWS is the Army's unified, next-generation procurement solution. It successfully replaced the legacy Standard Procurement

System (SPS) Army and remains on schedule to fully phase out the Procurement Automated Data and Document System (PADDS) by the end of FY 2026.

FY26 FY28-34FY27

Briefer: LTC Morgan

User Adoption & Training

• Onboard and train 1,600 PADDS users by Q4.

• Migrate over 21,000 PADDS files to the ACWS platform.

• Provide End-of-Fiscal-Year (EOFY) support for more than 9,000 ACE users.

System Transition

• Launch the LMP/GFEBS interface on June 29.

• Sunset the legacy PADDS Major Weapon Systems

(MWS) on September 30.

• Initiate a Call for Solutions to facilitate a contract recompete.

Initial Capabilities

• Deploy GOAT for OTA capabilities.

• Provide ongoing sustainment and support.

• Prioritize the development of holistic functional requirements.

• Begin the initial deployment of a next-generation acquisition lifecycle automation system.

Subsume PADDS by September 30, 2026

• Finalize the project scope for ACWS.

• Field ACWS to over 9,000 global ACE users.

• Maintain a continuous joint effort to support the CWS refactoring initiative with service partners

Award Contract

• Issue a Call for Solutions (CFS) with a hybrid Fixed-Price

Incentive Firm (FPIF) and Firm-Fixed-Price (FFP) contract structure.

• Appoint a single portfolio coordinator to oversee multiple vendors.

Sustainment, Deployment, and Modernization

• Ensure vendor accountability is tied to performance metrics.

• Provide continuous Tier 3 support for all systems.

• Continue VCE and CWS refactoring efforts.

Make Secure Contracting (IL6) fully operational.

• Establish an operational, secure disconnected instance.

• Deliver Holistic Functional Requirements

• Drive continuous transformation by delivering Holistic Functional

Requirements.

• Enhance RADV by leveraging AI/LLMs to accelerate the procurement lifecycle.

Modernize ACWS with AI/LLMs

• Automate EPICS, such as the 9.0 Enterprise-Wide Pre-Award

Capabilities.

• Implement AI and LLM technologies throughout the ACWS platform to enhance automation and efficiency.

Full Deployment

• Achieve Full Deployment by completing the ACWS backlog.

• Provide ongoing sustainment for the ACWS platform.

Deliver Holistic Functional Requirements

• Commit to a cycle of continuous sustainment and transformation.

• Refine holistic functional requirements to maintain a competitive advantage and accelerate ACWS modernization.

• Leverage AI Human-in-the-Loop (HITL)

• Smart Contract Auditing & Compliance Checking

• IL6 Boundary Controls

AT&R| ACWS

Program Roadmap

Briefer: Mr. Aaron Kochanski

10Briefer: Mr. Aaron Kochanski

Service Area Current State Future Goal

Hosting & System

Health

Configuration Drifts and

Operational Chaos

Risk of system outages, degradation of services, and resource draining

Reliability Engineering

Clear, Standardized processes leading to predictable delivery, reliability, and accountability

Service Desk Support

(Tier 2 & 3)

Black-Hole Handoffs and Band-

Aid Mentality

Poor communication leading to silent-fixes with no knowledge created; Symptoms patched versus root-cause resolution

Seamless Tier 2 & 3 Support

Reduce resolution times, scale with knowledge codification and eliminate recurring failures

Agile Sustainment

Accumulating Technical Debt

System fragility and decreased productivity

SAFe Agile Sustainment

Culture, Architecture, and Process paradigms for tech debt reduction restoring operational stability

Secure & Stabilize

Environments

Deliver Responsive

Tier 2 & 3 Technical Support

Drive Agile Sustainment

AT&R| ACWS

Requirement #1 – Vendor Accountability: Modernization, Service Desk Support and Agile Sustainment

11Briefer: Mr. Aaron Kochanski

Requirement #1 – ACWS Technical Stack

PLAN

Jira

Confluence

Service Now

BUILD

Appian

Java

GitLab

Maven

Docker

.NET

Apache

SAP BO

QLIK

SECURE &

DEPLOY

GitLab

SonarQube

Appian

Nexus Repository

Liquibase

Ansible

Fortify

OPERATE,

MONITOR &

SUPPORT

Oracle

JBoss

Appian

AWS

Splunk

Apache

ServiceNow

Teams

QLIK

SAP BO

Briefer: Ms. Audrey Diaz 12

Develop:

Optimize existing ACWS technical and functional capability for IL6 environment.

Sustain:

Obtain and maintain approved ATO for IL6 environment while navigating the RMF process.

Deploy:

Deploy ACWS IL6 instance in cArmy and sustain a fully functional capability within a SIPR/Impact

Level 6 (IL-6) environment.

IL6 Capability Outline

▪ Assess software performance against future business, technical, and lifecycle needs.

▪ Verify organizational readiness for continued deployment.

▪ Confirm alignment with DoW Information

Enterprise policies and architecture.

▪ Review test results, including cybersecurity, for adequate performance and security.

▪ Evaluate program progress against baselined cost, schedule, and performance.

▪ Ensure CCA compliance.

▪ Identify required support actions for sustained capability.

Requirement #2 – IL6 Secure Contracting

➢ Paperless Contract Files (PCF): Serves as the secure, centralized electronic repository for all Army contracting official records.

➢ Announcement of Award (AoA): Automates the public and internal notification of contract awards.

Contract Execution & Records Management

➢ PCO Warranting (Warrants): Digitally Manages, tracks, and audits the delegation of authority for Procurement Contracting

Officers, across the Army. This ensures that Contracting

Officers act strictly within their authorized financial and legal limits.

Workforce Management & Administration

➢ Business Intelligence (BI) and Dashboards: Consolidates and analyzes data from across the contracting enterprise to generate executive dashboards, predictive workloads, and status reports.

➢ Automated Data Validation Tool (ADVT): Runs background checks and automated validation logic on procurement data quarterly to maintain strict data integrity and acquisition oversight.

Enterprise Intelligence & Data Integrity

➢ DD2579 Small Business Coordination: Digitizes and automates the creation, routing, and approval of the DD Form 2579.

➢ Small Business Appointment Module (SBAM): Coordinates engagement by facilitating hiring, tracking and managing appointments of Army Small Business Professionals.

Small Business Programs & EngagementACWS

AT&R| ACWS

Requirement #3 – Virtual Contracting Enterprise Refactor

Virtual Contracting Enterprise CORE Capabilities

13Briefer: Mrs. Brijette Aris

14Briefer: Mr. Dave Kuhla

Requirement #4 – AI/API Modernization & Innovation

FUNCTIONAL PRIORITIES FOR ACWS

• Replace and retire Standard Procurement System (SPS) in the Army

COMPLETED in December 2025

• Replace and retire Procurement Automated Data and Documents System (PADDS)

IN PROGRESS, Expected Completion by December 2026 completion expected

• Maintain Operational Readiness of the Army Contracting Community through continued sustainment of

ACWS:

• ACWS is currently in use by over 9,000 Army Contracting Professionals

• Operations and Maintenance of ACWS includes software and platform updates, emerging data interoperability requirements, and ongoing end-user support

• Deploy capability to support Secure Environment Contracting:

• Initial fielding would place an instance of ACWS in an IL-6 enclave and integrate with

GFEBS-SA

• Build out full set of Army contracting requirements while modernizing processes and leveraging automation:

• Evaluate, ingest, and integrate capabilities from commercial and Government pipelines

• Solutions should incorporate intelligent automation and artificial intelligence to reduce redundancies, eliminate manual tasks, and otherwise provide lift to Army Contracting

Professionals

• Prioritize the re-use of and/or integration with existing enterprise capabilities including those found in the Procurement Integrated Enterprise Environment (PIEE) or developed by Air Force, Navy, and Defense Logistics Agency.

15Briefer: Mr. Dave Kuhla

Requirement #4 – AI/API Modernization & Innovation

ACWS EPICS: FUNCTIONAL REQUIREMENTS BACKLOG

7. Secure Environment Contracting

• Host ACWS and provide secure access on IL-6

• Integrate with GFEBS-SA for Commitments and Obligations

8. Enterprise-Wide Award Execution Capabilities

• PIEE CAC Enabled Digital Signature Integration – Planned

• Bi-Lateral Digital Signatures with Vendor

• Electronic Transmission of Awards & Modifications

• Line-Item Enhancements (line deletion, step ladder pricing, etc.)

9. Enterprise-Wide Pre-Award Capabilities

• PIEE Solicitation Module Integration – IN PROGRESS

– Automatic Solicitation and Notice Posting to SAM.gov

• Reverse Auction & Dynamic Form Creation

10. Enterprise-Wide Post-Award Capabilities

• Automated DFY Identification Management & automated Army wide order tracking & management

• PIEE Closeout Module Integration – COMPLETE

• Closeout for Non-FAR actions

• Automated ULO Management & Other Contract Administration

Capabilities

1. Integration with VCE Portfolio – MVP Met

2. Installation Contracting for Sites Supporting GFEBS Requiring Activities –

COMPLETE

3. Construction Contracting For USACE - MVP Met

4. FPDS Enhancements and Enhancements to the Baseline Software

▪ FPDS Enhancements MVP Met

▪ FPDS Integration Services – IN PROGRESS

▪ Forms, Attachments & Contract File Management MVP Met

▪ Document Rendering Integration – Planned

▪ Clause Logic Service MVP Met;

▪ Adopt PIEE Albert Clause Engine (ACE) – Planned

5. Non-FAR Actions: Grants, Agreements & Other Transactions – MVP Met

▪ Ingestion of GOAT Capability – IN PROGRESS (January 2027)

▪ ADS XML generation for non-FAR integrations with financial systems

▪ Integration with FAADC and FPDS for OTAs

6. Major Weapons Systems Procurement – IN PROGRESS (September 2026)

▪ Full Integration with LMP and GFEBS for Handshakes 1- 4 – IN

PROGRESS

▪ Concurrent modification improvements – Planned

▪ Automated Ingestion of External ACO Modifications – Planned

16Briefer: Mr. Dave Kuhla

Requirement #4 – AI/API Modernization & Innovation

ACWS EPICS: FUNCTIONAL REQUIREMENTS BACKLOG

11. Functional System Administration

• Mass modifications

• Re-alignment of workflows

• Advanced PID number maintenance

12. Workload Assignment & Strategic Sourcing

• PR/Workload Assignment (Automatic & Manual) – Pre-Award &

Post-Award

• Workload tracking

• Automated intelligent sourcing identification

13. Audit Support Processes

• Pilots

• Legal Holds

• Protest & Dispute Management

• Archiving

14. Source Selection

• All capabilities to support integrated both simple and complex source selection procedures into ACWS

15. Foreign Military Sales – MVP Met

• All additional capabilities necessary to support any unique requirements of the FMS community not already met by ACWS

16. System Help/Contextual Assistance

• Capabilities such as “hover over” tips, built-in assistance workflows, etc.

• Artificial intelligence to assist users in creating and administering contract actions, from simple to complex

17. Disconnected State

• Technical capabilities to allow for execution of contracts while disconnected from the network

• Final Call Release Date Tentatively Scheduled for 28 July 2026

• Solution Briefs due 1200 CST 11 August 2026

• Email Submission Address: usarmy.ria.acc.mbx.acws-cso@army.mil

• Required Subject Line Format: ACWS-CFS-001 Submission - [Company Name]

• Register and monitor in SAM.gov

• Pages over limit are removed/not evaluated

• Observe submission deadlines, late submissions will NOT be evaluated

17Briefer: Ms. Karen Loss

AT&R| ACWS

Submission Details mailto:usarmy.ria.acc.mbx.acws-cso@army.mil mailto:usarmy.ria.acc.mbx.acws-cso@army.mil mailto:usarmy.ria.acc.mbx.acws-cso@army.mil

File Naming Convention Contents & Page Limits

File 1: Administrative CompanyName_Admin.pdf

Title Page (Max 1 Page):

Company Name, Call Title, Date, POC details, Address, Commercial and Government Entity (CAGE) and UEI.

Executive Summary (Max 1 Page): Summary of the Company and corporate commercial experience.

Business Certifications (Max 2 Pages): Affirmation of Business Status (Attachment A).

IP Statement & Organizational Conflict of Interest (OCI) (No Page Limits): Identify Property (IP) restrictions and Organizational Conflicts of Interest mitigation.

File 2: Solution Brief CompanyName_Solution.pdf

Solution Brief: Maximum 5 pages (including diagrams and tables). Describe the proposed technical architecture, its direct alignment with the REQUIREMENTs, and its scalability across the Army

Contracting Enterprise. Submissions must address the following structural areas:

Technical Approach & REQUIREMENT Alignment: Explain the unique technical aspects of your solution and explicitly map capabilities to the specific REQUIREMENTs addressed.

Modern Architecture Standards: Detail the platform’s technical approach to scalability, use of open

APIs, implementation of containerization, and adherence to standard data schemas.

Security & Compliance: Outline how the solution complies with Army hosting, network, and security requirements.

Deployment Readiness: Explicitly state the solution’s current Authority to Operate (ATO) status and designate its current DoD Technology Readiness Level (TRL).

File 3: ROM & Schedule CompanyName_Pricing_Schedule.pdf

ROM (No Page Limit): Must contain the breakout of pricing. Tie pricing to milestones, where appropriate. Annotate assumptions used to develop the ROM.

Notional Schedule (No Page Limit): Must contain a project schedule outlining major tasks, milestones, and/or timeline for delivering the proposed solution. Annotate assumptions used to develop the schedule.

Briefer: Ms. Karen Loss 18

Submission Details File Structure

"The Government's objective is that ALL requirements be met, either by a single vendor or by a team of vendors under a single submission."

19Briefer: Ms. Karen Loss

Phase 1:

Solution Brief

Evaluation against four key criteria

• Technical Approach &

Requirement Alignment

• Modern Architecture

Standards

• Security & Compliance

• Deployment Readiness

Phase 2: Pitch

Selected companies may be invited to pitch/demonstrate capability

Government may limit invitees or bypass Phase

Phase 3:

Solution Proposal

Select companies invited to submit a full Solution Proposal

Award subject to availability of funding and need

Phased Evaluation Process

Existing Interagency Agreement (IAA) expires on 31 December 2026:

The ACWS Program requires a contractor to rapidly deliver scalable unclassified, classified, and disconnected solutions to support the Army's contracting mission and ensure operational continuity.

REQUIREMENTS PACKAGE DUE SOLICITATION RELEASE NEW CONTRACT AWARD

✓ Market Research ✓ Requirement Refinement ✓ Budget

CURRENT CONTRACT

EXPIRATION

FY26 Q1 FY27

Formal Proposals Due

• 1-14 October Evaluation and Selection

• 15 October Negotiations Begin

Contract Award

• 04 November

Project Scope

• Modernizes and sustains the Army Contracting

Enterprise for 9,000 global users by sunsetting PADDS, deploying IL6 secure contracting, delivering DSO and

Universal Capabilities, and providing continuous

DevSecOps and Tier 3 support.

Contract Vehicle

• Commercial Solutions Opening under the Army Open

Solicitation

Contract Type

• FFP (with possible FPIF CLINs)

Market Research

• 05-15 May ~ Completed Vendor one-on-one meetings to determine requirement viability, vehicle and contract type.

• 14-27 July Draft Call for Solutions and Industry Day

FY27

AT&R | ACWS

Call for Solutions Timeline

Call for Solutions

• 28 July to 11 August Industry prepares Solution Brief

Solution Brief

• 25 August Solution Brief and ROM Evaluation Complete

• 26 August First Advisory Down-Select

Oral Presentations

• 26 August - 9 September Industry prepares for Oral

Presentations and Technology Demos

• 10 September Oral Presentations

• 17 September Second Advisory Down-Select

Formal Proposals Preparation

• 18-30 September Industry prepares Formal Proposals

Tentative Call for Solutions Timeline

20Briefer: Ms. Karen Loss

Questions and Answers (1 of 2)

Industry Question Government Answer

1. Platform & Modernization

What is the Army’s intent regarding the current Appian platform? Will you consider alternative Low-Code/No-

Code (LCNC) platforms?

Yes. As stated in the CFS, the current solution has compounding technical debt from the initial MVP architecture. The Army is exploring the best way to resolve this debt and deliver a modern LCNC solution. Per Section 7.1, we will evaluate the

Technical Merit of all proposed solutions, whether they optimize the existing platform or propose a compelling alternative.

2. Scope & Capabilities

Which Virtual Contracting Enterprise (VCE) capabilities are in scope for the merger, and what are the highest priority AI use cases?

The objective is to absorb and modernize all VCE, PADDS, and PCF capabilities.

Requirement 4 and Appendices B & D of the CFS outline the ACWS product backlog and Universal Capabilities, which are the Government’s priorities for AI-driven modernization.

3. Teaming & Evaluation

How will the Government evaluate teaming arrangements, especially between a platform provider and a smaller, innovative AI/automation vendor?

The Government’s objective is that all requirements be met, either by a single vendor or by a team under a single submission. As stated in Section 5.2, the Army places no restrictions on how Primes/Teams are organized. Past performance and technical merit will be assessed on the solution as a whole.

4. Hosting & Security

Will the Government provide the IL-6 hosting environment, or is the vendor expected to bring and accredit their own?

The Government will provide the underlying hosting environment. Per Section 3, ACWS currently has an ATO for DLA PIEE hosting. The vendor is responsible for deploying, securing, and sustaining the ACWS instance within the Government-provided environment and must supply a timeline for any new ATO required by their solution.

Below is a summary of Industry Questions submitted on SAM.gov and the Government’s Answers:

Briefer: Ms. Karen Loss 21

Questions and Answers (2 of 2)

Industry Question Government Answer

5. Submission Scope

Does our Solution Brief have to address all four

Requirements, or can we propose a solution for a single Requirement, like AI modernization?

Your solution must address all four Requirements. As stated in the CFS, the

Government's objective is to receive a comprehensive solution for the entire scope of work, either from a single vendor or a team. We are not seeking point solutions for individual requirements at this time.

6. Technical Debt

The CFS mentions "compounding technical debt" as a primary driver. Can you provide specific examples of this debt?

The primary sources of technical debt stem from the initial MVP architecture, which now constrains our ability to scale and rapidly integrate new capabilities. This includes limitations in the current LCNC implementation, challenges with the VCE merger, and difficulties in establishing seamless, real-time data flows with financial systems. We are seeking a holistic architectural solution to these issues.

7. Evaluation of Innovation

How will the Government evaluate teaming arrangements, especially between a platform provider and a smaller, innovative AI/automation vendor?

Per Section 7.1, Technical Merit is the most important factor. The evaluation is not designed to favor any specific platform. A compelling and innovative response to the CFS that clearly demonstrates a feasible path to resolving our technical debt and delivering superior capability will be evaluated favorably, regardless of its origin.

8. Small Business & Teaming

What is the Government's strategy regarding Small

Business participation?

While there is no specific small business set-aside for this effort, we encourage robust small business participation at the subcontracting level. Per Section 5.2, vendors are free to form teams, and these teaming arrangements must be outlined in your Phase 1 Solution Brief.

Below is a summary of Industry Questions submitted on SAM.gov and the Government’s Answers:

Briefer: Ms. Karen Loss 22

Acronyms

Acronym Definition

ACWS Army Contract Writing System

ADVT Automated Data Validation Tool

AoA Announcement of Award

ATO Authority to Operate

CAGE Commercial and Government Entity

CFS Call for Solutions

CLIN Contract Line Item Number

FFP Firm-Fixed-Price

FPDS-NG Federal Procurement Data System – Next Generation

FPIF Fixed-Price Incentive Firm

GFEBS General Fund Enterprise Business System

IL-6 Impact Level 6

LCNC Low Code/No Code

MVP Minimum Viable Product

Acronym Definition

PADDS Procurement Automated Data and Document System

PCF Paperless Contract Files

PIEE Procurement Integrated Enterprise Environment

ROM Rough Order of Magnitude

SAM System for Award Management

SPS Standard Procurement System

TRL Technology Readiness Level

UEI Unique Entity Identifier

ULO Unliquidated Obligation

USACE U.S. Army Corps of Engineers

VCE Virtual Contracting Enterprise

MWS Major Weapon Systems

HITL Human-in-the-Loop

THE ARMY RELIES ON

Capability Program Executive Enterprise Software and Services (CPE ES2)