Attach. 1 - CSO UPK Problem Statement.pdf
PDF 780 KB Posted
- Solicitation number
- FA877026SC003
About this file
This is a Commercial Solutions Opening (CSO) Solicitation issued by the Department of the Air Force for the replacement of Oracle User Productivity Kit (UPK) with a modern Digital Adoption Platform (DAP). The solicitation number is FA877026SC003, issued by the Business and Enterprise Systems Directorate at Wright-Patterson Air Force Base for the AFLCMC/GBGD Defense Enterprise Accounting and Management System (DEAMS) program, with a release date of November 2026.
The Air Force seeks a commercially available DAP to replace the legacy, end-of-life UPK system and address a critical operational gap in enterprise training capabilities for approximately 26,000+ geographically dispersed personnel across 170+ global locations. The solution must provide real-time in-application guidance, streamlined content creation, and simplified software adoption integrated with Oracle e-Business Suite (EBS) and modern web applications. The solicitation is organized around three Areas of Interest: (1) Content Authoring & Development requiring no-code creation, multi-format recording, rich content editing with PII masking, multiple output formats (.PDF, .DOCX, .PPT, .HTML), localization support, and preferably automated UPK content migration capabilities; (2) Agile Content Lifecycle Management & Governance including a centralized content library, role-based access control, content reusability mirroring Oracle UPK's Reusable Content Objects model, and desired DevSecOps alignment with CI/CD pipeline integration; and (3) Content Delivery & End-User Experience providing context-sensitive in-application guidance, user segmentation and targeting, cross-application desktop support, desired AI-powered assistance, and proactive change management tools.
All proposed solutions must meet strict eligibility requirements including: server-side compatibility with on-premises and government-managed Oracle Cloud Infrastructure with client-side operation on NIPRNet Windows OS; licensing based on server instances or limited authoring seats with no end-user named or concurrent licensing; native support for CNSA 1.0 PKI (minimum RSA-3072/RSA-4096 and SHA-384) and NIST-approved Post-Quantum Cryptography algorithms per CNSA 2.0; delivery of a comprehensive Software Bill of Materials in CycloneDX format; alignment with DISA Security Technical Implementation Guides with federated multi-factor authentication using DoD Common Access Cards and PKI; full Section 508 and WCAG 2.1 Level AA accessibility compliance with Voluntary Product Accessibility Template; compliance with FAR 52.204-23 and FAR 52.204-25 with disclosure of any NDAA Section 1260H Chinese Military Companies list associations; native support and default to TLS 1.3 for encrypted network traffic; FedRAMP Moderate or High authorization if proposing a SaaS model; and demonstrated ability to scale to 26,000+ personnel across 170+ locations without ERP performance degradation.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DEPARTMENT OF THE AIR FORCE
BUSINESS AND ENTERPRISE SYSTEMS DIRECTORATE
WRIGHT-PATTERSON AIR FORCE BASE, OHIO
Commercial Solutions Opening (CSO) Solicitation Oracle User Productivity Kit (UPK) Replacement — Digital Adoption Platform (DAP)
Solicitation Number: FA877026SC003
Program Office: AFLCMC/GBGD — Defense Enterprise Accounting and Management System
(DEAMS)
Project Name: Oracle User Productivity Kit (UPK) Replacement — DAP
Release Date: November 2026
Table of Contents Table of Contents
1. Section I: Program Overview & Background
1.1 Purpose
1.2 Mission Impact & Capability Gap
1.3 Scope of the Target Environment
2. Section II: Areas of Interest (AOIs)
2.1 AOI 1: Content Authoring & Development
2.2 AOI 2: Agile Content Lifecycle Management & Governance
2.3 AOI 3: Content Delivery & End-User Experience
3. Section III: System, Technical, & Security Requirements
Attach. 1 - CSO UPK Problem Statement
1. Section I: Program Overview & Background
1.1 Purpose
The Department of the Air Force (DAF), Business and Enterprise Systems (BES) Directorate, AFLCMC/GBGD, is issuing this Commercial Solutions Opening (CSO) to identify and acquire an innovative, commercially available Digital Adoption Platform (DAP). This platform will replace the legacy Oracle User Productivity Kit (UPK), which is reaching its official end-of-life.
The primary goal of this acquisition is to secure a modern, sustainable, enterprise-ready software-guided training and performance-support tool. It must streamline content creation, simplify software adoption, and provide real-time in-application guidance for the DEAMS user base.
1.2 Mission Impact & Capability Gap
The current solution (Oracle UPK) represents unsupported software and significant technical debt. Its retirement creates a critical operational gap in how training is conducted across the enterprise.
The replacement DAP will modernize training material outputs, provide interactive in-application assistance, and reduce the overall training footprint. This capability is designated as a Criticality (1) — Must Have requirement to support continuous financial and enterprise operations.
1.3 Scope of the Target Environment
• User Base: Approximately 26,000+ geographically dispersed personnel across 170+ global locations.
• Primary Integration: Stable and proven integration with Oracle e-Business Suite (EBS) (including
Forms & OAF pages) and modern web applications.
• Target Environments: The DAP must be deployable and tested across both Development (Dev) and
Test environments before transitioning to Production.
2. Section II: Areas of Interest (AOIs) The Air Force is seeking commercial solutions that address three primary Areas of Interest (AOIs).
Proposals will be evaluated on how comprehensively they meet the validated requirements within each
AOI:
2.1 AOI 1: Content Authoring & Development
• No-Code Content Creation: The solution must provide an intuitive, user-friendly authoring interface that allows non-technical personnel to rapidly record, create, and update application guidance without writing code.
• Multi-Format Recording: Authors must have the ability to record user interactions with web-based applications (specifically Oracle EBS) and desktop applications to automatically generate simulations, step-by-step instructions, and videos.
• Rich Content Editing: The authoring tool must provide advanced formatting, text annotations, callouts, branching logic, and the automated masking of sensitive data (specifically Personal Identifiable Information (PII)). It must support a library catalog capability to automatically connect and update hierarchies of job aids (e.g., “parent–child” links).
• Multiple Output Formats: The platform must publish content to multiple formats from a single source recording, including interactive simulations, printable documents (.PDF, .DOCX), presentation slides (.PPT), and standard learning formats (.HTML) for LMS integration. Users must be able to interact with the output formats (e.g., select/deselect graphical images).
• Localization & Translation (Desired Capability): Built-in tools supporting multi-language translation and localization of training materials.
• UPK Content Migration & Conversion (Preferred Capability): High preference will be given to vendors providing automated software tools, conversion utilities, or professional services capable of migrating legacy training content from the proprietary Oracle UPK .ODARC format into the new platform’s native format without loss of instructional integrity.
2.2 AOI 2: Agile Content Lifecycle Management & Governance
• Centralized Content Library: A secure, centralized repository for storing, versioning, and managing all training and support content.
• Agile Content Lifecycle / DevSecOps (Desired Capability): Alignment of the DAP content lifecycle with the ERP’s developmental cycle, featuring automated version control, CI/CD pipeline integration, testing in non-production environments, and automated application change detection.
• Role-Based Access Control (RBAC): Administrators must be able to define granular permissions for authors, reviewers, and administrators, supporting collaborative content lifecycles with peer review and approval workflows.
• Content Reusability: The ability to reuse content snippets across multiple modules and perform bulk updates. This should mimic Oracle UPK’s Reusable Content Objects (RCO) model (“one–to–many” or “parent–child” relationship model).
2.3 AOI 3: Content Delivery & End-User Experience
• In-Application Guidance: Real-time, context-sensitive guidance delivered directly within the live
Oracle EBS application, featuring interactive walkthroughs, tooltips, checklists, and field validations.
• User Segmentation & Targeting: Delivery of customized guidance tailored to different user roles, groups, or site-specific workflows.
• Cross-Application & Desktop Support: A unified guidance layer spanning a diverse technology stack, including web-based applications (Oracle EBS), custom systems, and on-premises desktop applications.
• AI-Powered Assistance (Desired Capability): Integration of AI features to power a self-help knowledge base, provide predictive analytics, and offer intelligent, conversational help.
• Proactive Change Management: Tools to create in-app announcements, pop-ups, and guided tours to inform users about software updates and process modifications.
3. Section III: System, Technical, & Security Requirements To safeguard the Air Force enterprise and comply with Department of Defense directives, all proposed solutions must meet strict technical and security mandates.
Requirement Description Compliance Type
Architecture Compatibility Server-side must be compatible with on-premises and government-managed Oracle Cloud Infrastructure (OCI).
Client-side (interfaces, recorders, browser extensions) must operate securely on NIPRNet Windows OS.
Eligibility Requirement
Licensing Model Proposed licensing must be based on server instances and/or limited client-side authoring seats. There shall be no individual named or concurrent end-user licensing for the consumption of training content.
Eligibility Requirement
CNSA 1.0 PKI Mandate Native support for CNSA 1.0 compliant cryptographic algorithms (minimum RSA-3072/RSA-4096 and SHA-384).
Ability to ingest, process, and validate 4K-bit certificates.
Eligibility Requirement
CNSA 2.0 PQC Mandate Native support for NIST-approved Post-Quantum Cryptography (PQC) algorithms in alignment with CNSA 2.0.
No proprietary pre-shared key (PSK) mechanisms.
Eligibility Requirement
Software Bill of Materials Delivery of a comprehensive, machine-readable Software Bill of Materials (SBOM) in a standardized CycloneDX format.
Eligibility Requirement
DoW Security Compliance Alignment with DISA Security Technical Implementation Guides (STIGs). Must support federated multi-factor authentication (MFA) utilizing DoD Common Access Cards (CAC) and PKI.
Eligibility Requirement
Accessibility Compliance Fully compliant with Section 508 of the Rehabilitation Act and WCAG 2.1 Level AA standards. Vendor must provide a Voluntary Product Accessibility Template (VPAT).
Eligibility Requirement
Regulatory Compliance Complete compliance with FAR 52.204-23 and FAR 52.204-25.
Must disclose any components or parent organizations associated with the NDAA Section 1260H Chinese Military Companies list.
Eligibility Requirement
Transport Layer Security Must natively support and default to TLS version 1.3 for all encrypted network traffic.
Eligibility Requirement
Hosting Model (SaaS) If proposing a SaaS model, the solution must have achieved, or be on a validated path to, FedRAMP Moderate or High authorization.
Eligibility Requirement
Requirement Description Compliance Type
Scalability & Performance Must demonstrate the ability to scale to 26,000+ personnel across 170+ locations without ERP performance degradation.
Eligibility Requirement
| Table of Contents |
| 1. Section I: Program Overview & Background |
| 1.1 Purpose |
| 1.2 Mission Impact & Capability Gap |
| 1.3 Scope of the Target Environment |
| 2. Section II: Areas of Interest (AOIs) |
| 2.1 AOI 1: Content Authoring & Development |
| 2.2 AOI 2: Agile Content Lifecycle Management & Governance |
| 2.3 AOI 3: Content Delivery & End-User Experience |
3. Section III: System, Technical, & Security Requirements
File details come from the government source that posted it. Updated .