OFC HCM SaaS IDIQ SOO 05 JUN 2025.pdf

Statement of Objectives (SOO) for

Human Capital Management (HCM) Software-as-a-Service (SaaS) 5 June 2025

Prepared by:

Platform Modernization and Integration Branch (AFLCMC/GBHP)

Air Force Life Cycle Management Center (AFLCMC) Joint Base San Antonio-Randolph, TX 78150

Distribution Statement C: Distribution authorized to U.S. Government agencies and their contractors date 14 February 2025. Other requests for this document must be referred to AFLCMC/GBH, 1st Street West, Bldg. 977, Joint Base San Antonio-Randolph, TX 78150.

Destruction Notice – For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of document.

DISCLAIMER - The contents of this document are not to be construed as an official Department of the USAF position unless so designated by other authorized documents. The use of trade names in this document does not constitute an official endorsement or approval of the use of such commercial hardware or software. Do not cite this document for the purpose of advertisement.

This page intentionally left blank

Table of Contents

1.0 Background

2.0. Objectives

3.0. Constraints & Considerations

4.0. Desired Outcomes

5.0. Acceptance and Inspection Criteria

6.0. Definition of Done

1.0 Background

The Department of the Air Force (DAF) seeks to modernize its Human Capital Management (HCM) infrastructure by integrating a secure, scalable, and intuitive Software-as-a-Service (SaaS) platform. This requirement focuses exclusively on the implementation and system integration effort—not the software licensing—with the goal of retiring duplicative legacy HR systems.

1.1 The Air Force has procured Oracle Fusion Cloud HCM as its baseline platform for this project. Previous implementation efforts failed to achieve operational integration due to data migration and system alignment challenges, as well as a lack of agile responsiveness.

Traditional acquisition approaches did not yield a fully integrated, deployable solution, highlighting the need for a more adaptive execution strategy.

1.2 To address these challenges, the Government is leveraging the Commercial Solutions Opening (CSO) authority under 10 U.S.C. 3458 to encourage innovative implementation and integration solutions - particularly from traditional or non-traditional vendors and emerging commercial practices. The objective is to rapidly field a secure, network interoperable, user-centered system while navigating legacy infrastructure, meeting audit standards, ensuring user adoption, and maintaining cost and schedule discipline.

1.3 This effort is not a license purchase but rather a modernization and implementation initiative requiring vendors to align agile delivery, integration, data migration, and change management within a complex enterprise environment. Offerors must propose actionable, modular approaches aligned with the Statement of Objectives (SOO) to deliver a fully configured system integration on the selected platform.

2.0. Objectives

2.1 Innovation, speed-to-field, and effectiveness in proposed modular and open integration methodology, facilitating seamless data exchange and interoperability with existing and future systems.

2.2 Integrate Oracle Fusion Cloud HCM to support core functions such as Core HR, Talent Management, and Benefits Administration, leveraging open standards and APIs to ensure interoperability and avoid vendor lock-in.

2.3 Deliver a Minimum Viable Product (MVP) within 6 months of contract award, demonstrating an Agile approach with clear and measurable acceptance criteria for key deliverables, and establishing a robust Continuous Integration/Continuous Delivery (CI/CD) pipeline for ongoing updates and enhancements.

2.4 Migrate all relevant legacy HR data with full fidelity, security, and audit traceability, while minimizing disruption to ongoing operations, with a focus on key systems such as MilPDS, WINGS, COMPASS, and AFRISS-TF.

2.5 Attain and maintain compliance with FedRAMP Moderate+ and applicable DISA STIGs, ensuring continuous security monitoring and a proactive DevSecOps approach to identifying and mitigating vulnerabilities throughout the software lifecycle.

2.6 The proposed solution and implementation approach shall align with the principles and best practices outlined in DoDI 5000.87, Operation of the Software Acquisition Pathway, particularly regarding agile development, continuous integration/continuous delivery (CI/CD), modularity, and DevSecOps. The offeror shall describe how its solution and approach will support rapid adaptation to changing requirements and integration with other DoD systems

3.0. Constraints & Considerations

3.1 The system must accommodate at least 7,500 concurrent users.

3.2 Data sovereignty is required: all data remains government-owned and must be exportable.

3.3 Integration must include Role-Based Access Control (RBAC) and Single Sign-On (SSO).

3.4 Seamless and bi-directional interoperability with MilPDS and designated downstream HR systems is required.

3.5 The government encourages agile execution through iterative delivery (e.g., sprints or increments).

3.6 Offerors should propose secure and efficient methods for interface development, data transformation/migration, and achieving RMF accreditation.

3.7 All deliverables, code, data artifacts, training materials, and configuration documentation generated under this effort shall be provided with Government Purpose Rights in accordance with DFARS 252.227-7013 and DFARS 252.227-7014, or with Unlimited Rights when developed exclusively at government expense.

4.0. Desired Outcomes

4.1 Improved user experience via intuitive, modern interfaces and streamlined workflows.

4.2 Demonstrated cost avoidance through system consolidation and process reengineering.

4.3 Real-time analytics and dashboarding to enable data-driven HR decisions.

4.4 Fully accredited solution with sustained Authorization to Operate (ATO) in government environments.

5.0. Acceptance and Inspection Criteria

The solution or technical proposal shall define clear acceptance and inspection criteria equal to or exceeding recognized commercial best practices. These criteria must be measurable, repeatable, and used to validate the completion of each sprint, deliverable, or integration milestone. Examples may include data migration accuracy thresholds, integration test success rates, system uptime metrics, or user adoption benchmarks.

6.0. Definition of Done

The Definition of Done (DoD) shall be jointly developed and agreed upon during the contract kickoff phase. The definition of done shall represent the minimum set of criteria required for a deliverable, feature, or system increment to be considered complete and ready for acceptance. This must include:

6.1 Functional Testing Passed and Automated: All relevant functional tests must pass. These tests must be automated and integrated into the CI/CD pipeline to ensure continuous validation.

6.2 Security Scans Completed with No Critical or High-Severity Vulnerabilities: Security scans (e.g., SAST, DAST, SCA) must be completed, and all critical and high-severity vulnerabilities must be remediated and re-tested. Medium-severity vulnerabilities must have an approved mitigation plan with a defined timeline for remediation.

6.3 Documentation Delivered and Approved: Documentation, including user guides, API documentation (if applicable), and system documentation, must be delivered and approved by the designated stakeholders. Documentation should be version controlled and easily accessible.

6.4 Stakeholder Sign-Off and Acceptance Criteria Met: Stakeholders must sign off on the deliverable, feature, or system increment, confirming that all acceptance criteria defined in the user story or sprint backlog have been met.

6.5 Training Delivered (if applicable) and User Feedback Incorporated: Training materials must be delivered (if applicable), and user feedback from training sessions must be incorporated into the documentation and/or system.

6.6 Code Review Completed and Approved: All code must be reviewed and approved by a qualified peer to ensure code quality, maintainability, and adherence to coding standards.

6.7 Performance and Scalability Tests Passed: Performance and scalability tests must be conducted to ensure the system meets the defined performance requirements under expected load. Any identified performance bottlenecks must be addressed.

6.8 Accessibility Requirements Met (if applicable): If applicable, the deliverable must meet accessibility requirements (e.g., Section 508 compliance) to ensure usability for individuals with disabilities.

6.9 Deployment Ready: The deliverable must be packaged and ready for deployment to the target environment, with clear instructions for deployment and rollback (if necessary)