Solicitation 24322626R0007 - Federal HRIT Modernization.pdf

PAGE 1 OF 1. REQUISITION NO.

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NO. 5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

a. NAME b. TELEPHONE NO. (No Collect Calls) 8. OFFER DUE DATE/LOCAL

9. ISSUED BY CODE 10. THIS ACQUISITION IS UNRESTRICTED OR SET ASIDE: % FOR:

SMALL BUSINESS

HUBZONE SMALL

BUSINESS

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

WOMEN-OWNED SMALL BUSINESS

(WOSB) ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

8(A)

NAICS:

SIZE STANDARD:

11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

12. DISCOUNT TERMS

13a. THIS CONTRACT IS A

RATED ORDER UNDER

DPAS (15 CFR 700)

13b. RATING

14. METHOD OF SOLICITATION

RFQ IFB RFP

15. DELIVER TO CODE 16. ADMINISTERED BY CODE

17a. CONTRACTOR/OFFEROR CODE FACILITY CODE 18a. PAYMENT WILL BE MADE BY CODE

TELEPHONE NO. UEI: EFT:

PHONE: FAX:

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT SUCH ADDRESS IN OFFER

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a UNLESS BLOCK BELOW IS CHECKED

SEE ADDENDUM

19. 20. 21. 22. 23. 24.

ITEM NO. SCHEDULE OF SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

(Use Reverse and/or Attach Additional Sheets as Necessary)

25. ACCOUNTING AND APPROPRIATION DATA 26. TOTAL AWARD AMOUNT (For Govt. Use Only)

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1, 52.212-4. FAR 52.212-3 AND 52.212-5 ARE ATTACHED. ADDENDA ARE ARE NOT ATTACHED.

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN _______________ 29. AWARD OF CONTRACT: REF. ___________________________________ OFFER COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND DATED ________________________________. YOUR OFFER ON SOLICITATION DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY (BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED SET FORTH HEREIN IS ACCEPTED AS TO ITEMS:

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a. UNITED STATES OF AMERICA (SIGNATURE OF CONTRACTING OFFICER)

30b. NAME AND TITLE OF SIGNER (TYPE OR PRINT) 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER (TYPE OR PRINT) 31c. DATE SIGNED

AUTHORIZED FOR LOCAL REPRODUCTION (REV. NOV 2021)

PREVIOUS EDITION IS NOT USABLE Prescribed by GSA - FAR (48 CFR) 53.212

7. FOR SOLICITATION

INFORMATION CALL:

STANDARD FORM 1449

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL PRODUCTS AND COMMERCIAL SERVICES

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, & 30

24322626R0007 10/17/2025

Matthew Manning (202) 936-1155 TIME 10/31/2025 1pm EDT

U.S. Office of Personnel Management 1900 E St NW Room 1310 Washington, DC 20415-7710

X

541512

$24.5M

N/A

X

See Delivery Schedule

OPM 243226

U.S. Office of Personnel Management 1900 E St NW Room 1310 Washington, DC 24015-7710

OPM Delphi eInvoicing System h // i i https://einvoice.esc.gov

See CONTINUATION Page

This Request for Proposal (RFP) is issued for Federal Human Resources Information Technology (HRIT) Modernization

Period of Performance (PoP): 10-years Single-Award Indefinite Delivery Indefinite Quantity contract

Points of Contact Contract Specialist: Christina Barr, christina.barr@opm.gov Contracting Officer: Matthew Manning, matthew.manning@opm.gov

*** See Continuation Page ***

X X

SECTION B - SUPPLIES OR SERVICES AND PRICE

B.1 GOVERNING LAW

Federal law and regulations, including the Federal Acquisition Regulations (FAR), shall govern this Contract/Order. Commercial license agreements may be made a part of this Contract/Order but only if both parties expressly make them an addendum hereto, as permitted by FAR 12.212.

If the commercial license agreement is not made an addendum, it shall not apply, govern, be a part of or have any effect whatsoever on the Contract/Order; this includes, but is not limited to, any agreement embedded in the computer software (clickwrap), any agreement that is otherwise delivered with or provided to the Government with the commercial computer software or documentation (shrinkwrap), or any other license agreement otherwise referred to in any document. If a commercial license agreement is made an addendum, only those provisions addressing data rights regarding the Government’s use, duplication and disclosure of data (e.g., restricted computer software) are included and made a part of this Contract/Order, and only to the extent that those provisions are not duplicative or inconsistent with Federal law, Federal regulation, the incorporated FAR clauses and the provisions of this Contract/Order; those provisions in the commercial license agreement that do not address data rights regarding the Government’s use, duplication and disclosure of data shall not be included or made a part of the Contract/Order. Federal law and regulation including, without limitation, the Contract Disputes Act (41 U.S.C. § 7101 et seq.), the Anti-Deficiency Act (31 U.S.C. § 1341 et seq.), the Competition in Contracting Act (41 U.S.C. § 3301 et seq.), the Prompt Payment Act (31 U.S.C. § 3901 et seq.), Contracts for Data Processing or Maintenance (38 USC § 5725), and FAR clauses 52.212-4, 52.227-14, 52.227-19 shall supersede, control, and render ineffective any inconsistent, conflicting, or duplicative provision in any commercial license agreement. In the event of conflict between this clause and any provision in the Contract/Order or the commercial license agreement or elsewhere, the terms of this clause shall prevail. The Contractor shall deliver to the Government all data first produced under this Contract/Order with unlimited rights as defined by FAR 52.227-14. Claims of patent or copyright infringement brought against the Government as a party shall be defended by the U.S. Department of Justice (DOJ) in accordance with 28 U.S.C.

§ 516; at the discretion of DOJ, the Contractor may be allowed reasonable participation in the defense of the litigation. Any additional changes to the Contract/Order must be made by modification (Standard Form (SF) 30) and shall only be made by a warranted Contracting Officer. Nothing in this Contract/Order or any commercial license agreement shall be construed as a waiver of sovereign immunity.

B.2 CONTRACT TYPE

The contract type is Firm-fixed-Price (FFP).

B.3 PRICE SCHEDULE

The period of performance shall be 10 years from date of award.

CLIN DESCRIPTION QTY UNIT UNIT PRICE TOTAL PRICE

0001 Core Implementation in accordance with (IAW) paragraphs 5.1.1-5.1.5 of the Performance Work Statement (PWS).

This CLIN is to provide Core Implementation on a FFP basis IAW the PWS set forth in Section C.

Specific requirements and pricing shall be set forth under individual Task Orders.

Payments under this Contract Line Item Number (CLIN) shall be provided as follows:

Milestone Payment % Access to Non- Production Environments

10%

PIA and ATO 40% Interconnections and Configurations

20%

Training 0% Approved Production Environment

30%

1 LO $ $

0001AA Draft and Final IDIQ/Kickoff Presentation IAW paragraph 5.1.1 of the PWS.

Due five (5) days after IDIQ award.

1 LO NSP NSP

0001AB FedRAMP Moderate or Higher certified Core HCM Platform Solution IAW paragraph 5.1.1 of the PWS.

1 LO NSP NSP

Due five (5) days after IDIQ award. Access provided upon request within one (1) business day.

0001AC System Metrics Dashboard IAW paragraph 5.1.1 of the PWS.

Due within 15 days of IDIQ award and updated daily thereafter for the lifecycle of the project.

1 LO NSP NSP

0001AD Master Test Plan IAW paragraph

5.1.1 of the PWS.

Due within 15 days of IDIQ award and updated quarterly thereafter for the lifecycle of the project.

1 LO NSP NSP

0001AE User Acceptance Testing Report IAW paragraph 5.1.1 of the PWS.

Due one (1) day prior to each system release for the lifecycle of the project.

1 LO NSP NSP

0001AF Incident Outage Report IAW paragraph 5.1.1 of the PWS.

For planned downtime, include in the monthly status report. For unplanned downtime, for each incident report, due within two (2) hours of incident with status updates every hour.

1 LO NSP NSP

0001AG Security Incident Report IAW Paragraph 5.1.1 of the PWS.

Due within two (2) hours of each incident.

1 LO NSP NSP

0001AH Draft and Final Privacy Impact Assessment IAW Paragraph 5.1.1 of the PWS.

Draft due within 30 days of award and final due within 45 days of award.

0001AJ Draft and Final Authority to Operate Documentation IAW Paragraph 5.1.1 of the PWS.

Due within 30 days of award and final due within 45 days of award.

1 LO NSP NSP

0001AK Fit Gap Analysis Report IAW Paragraph 5.1.1 of the PWS.

Draft due within 30 days of IDIQ award. Final report due within 45 days of IDIQ award.

1 LO NSP NSP

0001AL System Release Notes IAW Paragraph 5.1.1 of the PWS

Due the day of each system release for the lifecycle of the project.

1 LO NSP NSP

0001AM System Requirements Backlog IAW Paragraph 5.1.1 of the PWS.

Due within 15 days of award and updated quarterly thereafter for the lifecycle of the project.

1 LO NSP NSP

0001AN Resilience Strategy/Plan IAW Paragraph 5.1.1 of the PWS.

Due within 30 days of award and updated quarterly thereafter for the lifecycle of the project.

1 LO NSP NSP

0001AP Contingency Plan IAW Paragraph

5.1.1 of the PWS.

Due within 30 days of award and updated quarterly thereafter for the lifecycle of the project.

1 LO NSP NSP

0001AQ API Documentation IAW Paragraph 5.1.2 of the PWS.

Due within 15 days of award and updated with each new interconnection.

0001AR ISAs and MOUs for Data Transmission IAW Paragraph 5.1.2 of the PWS.

Due within 30 days of IDIQ award.

1 LO NSP NSP

0001AS Data Tables and Data Dictionary IAW Paragraph 5.1.3 of the PWS.

Due within five (5) days of IDIQ award and updated throughout the lifecycle of the project.

1 LO NSP NSP

0001AT Draft and final Comprehensive Data Migration Strategy IAW Paragraph 5.1.3 of the PWS.

Due within five (5) days of IDIQ award. Final due within 10 days of approved draft.

1 LO NSP NSP

0001AU Online User Help Materials IAW Paragraph 5.1.4 of the PWS.

Due the day of each system release for the lifecycle of the project.

1 LO NSP NSP

0001AV Training Materials IAW Paragraph

5.1.4 of the PWS.

Due the day of each system release for the lifecycle of the project.

1 LO NSP NSP

0001AW Communications Materials IAW Paragraph 5.1.4 of the PWS.

Due no later than two (2) days prior to the engagement where the materials will be used for the lifecycle of the project.

1 LO NSP NSP

0001AX Monthly Status Briefing IAW Paragraph 5.1.4 of the PWS.

Due one (1) month after kickoff and updated monthly thereafter for the lifecycle of the project.

1 LO NSP NSP

0002 Agency Transition IAW paragraphs 5.2-5.2.6 of the PWS.

This CLIN is to provide Agency Transition services on a FFP basis

1 LO * $ * $

IAW the PWS set forth in Section C.

Specific requirements and pricing shall be set forth under individual Task Orders.

Payments under this CLIN shall be provided as follows:

Complexity Price Small $ Medium $ Large $ X-Large $

The following milestone payments apply to the Agency Transition Requirements for each agency regardless of Complexity category:

Milestone Payment % Agency TO Award

0%

Configurations 0% Interoperability 0% Migrate Data 10% 60-day Shadow Mode (User Acceptance Testing)

0%

30-Day Sign-off 70% 6-Month Sign-off 20%

* For Price Evaluation Purposes, use the following quantities for each Complexity Category: Small = 19, Medium = 12, Large = 3, X- Large = 1. *

0002AA Individual Task/Delivery Order Kickoff Meetings IAW Paragraph

5.2.1 of the PWS.

As required, due within five (5) days of Task Order award.

0002AB User Acceptance Testing Report IAW Paragraph 5.2.1 of the PWS.

Due 30 days ARO and updated weekly in the authoritative repository.

1 LO NSP NSP

0002AC System Release Notes IAW Paragraph 5.2.1 of the PWS.

Due 30 days ARO and updated weekly in the authoritative repository.

1 LO NSP NSP

0002AD API Documentation IAW Paragraph 5.2.2 of the PWS.

Due within 15 days after system identification.

1 LO NSP NSP

0002AE ISA and MOU for Data Transmission IAW Paragraph 5.2.2 of the PWS.

Due within 15 days after agency kickoff meeting.

1 LO NSP NSP

0002AF Agency Specific Data Migration Project Plan IAW Paragraph 5.2.3 of the PWS.

Due within five (5) days of kick-off meeting for individual task/delivery orders.

1 LO NSP NSP

0002AG Agency Specific Data Migration Status Report IAW Paragraph

5.2.3 of the PWS.

Due daily during data migration.

1 LO NSP NSP

0002AH System Data Schemas, Test Scripts and ETL Code for Data Migration IAW Paragraph 5.2.3 of the PWS.

Due within five (5) days of first task order migration being awarded.

1 LO NSP NSP

0002AJ UAT Testing Results Report IAW Paragraph 5.2.3 of the PWS.

Due 30 days ARO and updated weekly in the authoritative repository.

0002AK Subscription Management Report IAW Paragraph 5.2.4 of the PWS.

Due monthly for the lifecycle of the project.

1 LO NSP NSP

0002AL Tier 1 Help Desk Training for OPM IAW Paragraph 5.2.5 of the

PWS.

Due within five (5) days of CLIN 0003 task order and updated quarterly for the lifecycle of the project.

1 LO NSP NSP

0002AM Timely Resolution of Tier 2 and Tier 3 Tickets IAW Paragraph

5.2.5 of the PWS.

Tier 2 tickets resolved within two

(2) business days. Tier 3 tickets resolved within five (5) business days.

1 LO NSP NSP

0002AN Online User Help Materials IAW Paragraph 5.2.6 of the PWS.

Due

1 LO NSP NSP

0002AP Training Materials IAW Paragraph

5.2.6 of the PWS.

Due

1 LO NSP NSP

0002AQ Communication Materials IAW Paragraph 5.2.6 of the PWS.

Due

1 LO NSP NSP

0002AR Monthly Status Briefing IAW Paragraph 5.2.6 of the PWS.

0003 Licensing and Sustainment IAW paragraphs 5.3 of the PWS.

This CLIN is to provide Licensing and Sustainment services on a FFP basis IAW the PWS set forth in Section C.

Specific requirements and pricing shall be set forth under individual Task Orders.

This CLIN shall be priced Per Employee Per Year (PEPY).

* In the early part of this contract, it is expected that approximately half of all employees will not require licenses that include Time & Attendance functionality.

Therefore, CLIN 3001-1 pricing shall reflect licensing and sustainment for all required functionalities except for Time & Attendance; and CLIN 3001-2 shall reflect pricing for all required functionalities. At any given time, each employee license shall be provided under CLIN 3001-1 or CLIN 3001-2 and never simultaneously. *

0003-1 Licensing & Sustainment for all required functionalities except for Time & Attendance

*Payments under this CLIN shall be provided as follows:

Contract Year PEPY

Price Year 1 $ Year 2 $ Year 3 $ Year 4 $ Year 5 $ Year 6 $ Year 7 $ Year 8 $ Year 9 $ Year 10 $

* For price evaluation purposes, Offerors shall assume 1,000,000 employees require Licensing & Sustainment under this CLIN for a full year in every contract year.

The total price for CLIN 0003-1 shall be that sum. *

0003-2 Licensing & Sustainment for all required functionalities

*Payments under this CLIN shall be provided as follows:

Contract Year PEPY

Price Year 1 $ Year 2 $ Year 3 $ Year 4 $ Year 5 $ Year 6 $ Year 7 $ Year 8 $ Year 9 $ Year 10 $

* For price evaluation purposes, Offerors shall assume 1,000,000 employees require Licensing & Sustainment under this CLIN for a full year in every contract year.

The total price for CLIN 0003-2 shall be that sum. *

0003AA Subscription Management Report IAW Paragraph 5.3 of the PWS.

Due monthly for the lifecycle of the project.

1 LO NSP NSP

0004 Transition-Out for Continuity of Services IAW PWS paragraph 5.9.

This FFP CLIN shall include all management, services, and

1 LO $ $

materials for successful completion of the services and deliverables detailed in PWS 5.9

0005 Travel

The Contractor shall only be reimbursed for government-approved travel.

Specific requirements and pricing shall be set forth under individual Task Orders.

Grand Total $

Contract Maximum/Minimum Ceiling:

In accordance with Section I, FAR 52.216-22 entitled, “Indefinite Quantity” the maximum overall value of the contract for both the base period and options is set forth in the Price Schedule. In accordance with Section I, FAR 52.216-22 entitled, “Indefinite Quantity” the Minimum guaranteed value under the contract is $1,000. The initial order may require the Contractor to deliver a report that addresses aspects including, but not limited to, the following:

(1) A brief narrative on the skills and expertise of the prime and each subcontractor; (2) the Contractor’s approach to recognize, react to, and correct problems that may arise in the performance of a task order or the basic contract, including an escalation plan for any problems that do arise; (3) the Contractor’s organizational chart that includes titles and names of respective individuals; and (4) the Contractor’s processes to capture performance and contract metrics that will ensure execution of individual task orders in accordance with the contract.

SECTION C - DESCRIPTION/SPECIFICATIONS/STATEMENT OF WORK

U.S. Office of Personnel Management

Federal Human Resources Information Technology (HRIT) Modernization

Requirements Performance Work Statement (PWS)

Table of Contents

1 BACKGROUND

2 SCOPE OF WORK

2.1 GOVERNANCE STRUCTURE

2.2 A1.3 POSITION MANAGEMENT

2.3 A1.4 EMPLOYEE ENGAGEMENT

2.4 A3 TALENT DEVELOPMENT/LEARNING

2.5 A5 COMPENSATION AND BENEFITS (INCLUDING TIME AND ATTENDANCE WITH INTEGRATION TO FEDERAL PAYROLL

PROVIDERS)

2.6 A9 HUMAN CAPITAL ANALYTICS AND EMPLOYEE RECORDS

2.7 X1 PERSONNEL ACTION REQUEST PROCESSING

3 HIGH LEVEL OBJECTIVES

3.1 CORE IMPLEMENTATION

3.2 AGENCY TRANSITION

3.3 LICENSING AND SUSTAINMENT

4 PERFORMANCE REQUIREMENTS

4.1 PERIOD OF PERFORMANCE

4.2 PLACE OF PERFORMANCE

4.3 PROGRAM PERFORMANCE OUTCOMES

4.4 TRAVEL

5 SPECIFIC TASKS AND DELIVERABLES

5.1 CORE IMPLEMENTATION

5.2 AGENCY TRANSITION

5.3 LICENSING AND SUSTAINMENT

5.4 NOTIONAL TIMELINE

5.5 INDUSTRY BEST PRACTICES

5.6 MINIMIZATION OF CUSTOMIZATION

5.7 ALTERNATIVES TO IMPROVE EFFICIENCY

5.8 DELIVERABLES

5.9 TRANSITION-OUT FOR CONTINUITY OF SERVICES

6 OTHER GENERAL INFORMATION

6.1 GOVERNMENT-FURNISHED INFORMATION/EQUIPMENT

6.2 CONTRACTOR FACILITY ACCESS

6.3 SECURITY AND REGULATORY COMPLIANCE

6.4 CLASSIFICATION STANDARDS

6.5 PERSONNEL SECURITY

6.6 ADDITIONAL COMPLIANCE REQUIREMENTS

6.7 CONTRACTOR PERSONNEL TRAINING

6.8 QUALITY CONTROL PLAN (QCP)

6.9 DATA RIGHTS & OWNERSHIP – SUPPLEMENTAL REQUIREMENTS

6.10 PERFORMANCE METRICS

6.11 CONTRACTOR PERFORMANCE ASSESSMENT REPORTING SYSTEM (CPARS) EVALUATION

6.12 ORIGINAL EQUIPMENT MANUFACTURER (OEM)

7 TASK ORDER (TO) MANAGEMENT

7.1 GENERAL ORDERING

7.2 CONTRACTOR PROGRAM MANAGEMENT

7.3 CO-TERMING LICENSES

7.4 PRO-RATING LICENSES

7.5 PERIOD OF PERFORMANCE FOR LICENSES

7.6 MOST FAVORED CUSTOMER / PRICE REDUCTIONS

APPENDIX A: FUNCTIONAL REQUIREMENTS MATRIX

APPENDIX B: REQUIRED DATA MIGRATION AND SYSTEM INTEGRATIONS

INTEGRATION SECURITY & PRIVACY REQUIREMENTS

CORE IMPLEMENTATION INTEGRATIONS

AGENCY TRANSITION AND IMPLEMENTATION INTEGRATIONS & MIGRATIONS

APPENDIX C: OPM SPECIFIC PROVISIONS AND CLAUSES

1752.200-70 – ON-SITE WORKING CONDITIONS (MAY 2022)

1752.204-70 – CONTRACTOR PERSONNEL SECURITY REQUIREMENTS (JAN 2008)

1752.209-71 – CONTRACTOR’S KEY PERSONNEL (JULY 2005)

1752.209-74 – ORGANIZATIONAL CONFLICTS OF INTEREST (JULY 2005)

1752.224-70 – IDENTIFICATION AND AUTHENTICATION (DEC 2023)

1752.224-71 – IDENTIFICATION AND AUTHENTICATION CERTIFICATION (DEC 2023)

1752.224-72 – PROTECTING INFORMATION (DEC 2023)

1752.224-73 – INFORMATION PROTECTION POLICIES AND PROCEDURES (DEC 2023)

1752.224-74 – INFORMATION SECURITY INCIDENTS (DEC 2023)

1752.224-75 – INFORMATION SECURITY INSPECTIONS (DEC 2023)

1752.232-72 – LIMITATION OF GOVERNMENT’S OBLIGATION (MAY 2009)

1752.232-75 – ELECTRONIC SUBMISSION OF INVOICES (MAY 2021)

1752.233-70 – OPM PROTEST PROCEDURES (JULY 2023)

1752.239-70 – INTERNET PROTOCOL VERSION 6 COMPLIANCE (DEC 2023)

1752.239-71 – ACCESS TO OPM INFORMATION TECHNOLOGY SYSTEMS (DEC 2023)

1752.239-72 – SECTION 508 STANDARDS (DEC 2023)

1752.239-73 – INFORMATION SYSTEM SECURITY REQUIREMENTS (DEC 2023)

1752.239-74 – SECURITY ASSESSMENT AND AUTHORIZATION (DEC 2023)

1752.239-75 – CLOUD COMPUTING (DEC 2023)

1752.239-76 – INFORMATION TECHNOLOGY AWARENESS TRAINING (DEC 2023)

1752.239-77 – CONFIGURATION BASELINE (DEC 2023)

1752.239-78 – DATA PROTECTION REQUIREMENTS (DEC 2023)

1752.239-79 – DATA PROTECTION REQUIREMENTS CERTIFICATION (DEC 2023)

1752.239-80 – SECURITY MONITORING AND ALERTING REQUIREMENTS (DEC 2023)

1752.239-81 – CONTRACTOR INFORMATION TECHNOLOGY SYSTEM OVERSIGHT/COMPLIANCE (DEC 2023)

1752.239-82 – SUPPLY CHAIN RISK MANAGEMENT (DEC 2023)

1752.242-70 – RETURN OF OPM AND OPM-ACTIVITY-RELATED INFORMATION (DEC 2023)

1752.242-71 – SECURE DESTRUCTION OF OPM AND OPM-ACTIVITY-RELATED INFORMATION (DEC 2023) 1752.242-72 – RETURN OF OPM OWNED AND LEASED COMPUTING AND INFORMATION STORAGE EQUIPMENT (DEC 2023)

1 BACKGROUND

The U.S. Office of Personnel Management (OPM), as the federal government’s central human resources agency, is responsible for setting HR policies, providing HR services, and managing critical personnel systems for the civil service. Currently, OPM’s ability to execute its HR mission is constrained by the absence of a unified Core Human Capital Management (HCM) platform available for governmentwide use. This limitation has led to fragmented HR processes, inefficiencies, and increased administrative burdens across federal agencies.

To address these challenges, OPM is seeking to implement a centralized Core HCM platform that will scale across the Federal Government. This platform will exist as part of OPM’s suite of Federal HRIT products available to agencies through OPM’s Human Resources Solutions Shared Service Center. This initiative directly responds to systematic deficiencies and supports OPM’s statutory mission, addressing urgent needs to improve workforce management, ensure regulatory compliance, and enhance service delivery.

The centralized Core HCM platform will standardize and streamline HR processes across the federal government. OPM’s mandate is to modernize Federal HRIT operations through a secure, cloud-based HCM platform that complies with all applicable federal regulations. By offering a single, integrated platform that can support the entire government, OPM will establish the infrastructure necessary to provide a modern, data-driven federal HR ecosystem.

As America's largest employer, the federal government requires accurate and timely workforce data to manage its civilian workforce effectively and increase accountability to the American taxpayer. A unified Core HCM platform will improve data accuracy, reporting, and interoperability, enabling the Federal government to manage its workforce as a cohesive entity.

2 SCOPE OF WORK

The contractor must deliver and sustain a Federal Risk and Authorization Management Program (FedRAMP) Moderate or higher certified Core HCM platform compliant with all relevant federal laws and regulations that impact the scope of work outlined in this Performance Work Statement (PWS). Any Contractor providing a solution that is not FedRAMP Authorized at the time of submission will be reviewed by OPM’s Office of the Chief Information Officer (OCIO) to determine if the FedRAMP approval can be reasonably received by the time of contract award.

The Core HCM platform will be the system of record for approximately 2 million Executive Branch civilian employees. Postal Service and Intelligence Community employees are not included in the scope.

2.1 Governance Structure

The Government-wide alignment strategy will include multiple levels of engagement to drive strategic direction, create clarity in communication, and ensure alignment. The notional governance structure is shown below. This structure will serve as the central authority for scope decisions, risk mitigation, and escalation of issues.

OPM will chair this governance structure leading the vision and strategy and providing contract oversight. The contractor shall adhere to this structure and ensure consistent communication and coordination across workstreams. OPM expects Original Equipment Manufacturer (OEM) staff to be available and responsive and for the contractor to minimize using integrators/qualified partners/authorized representatives as “go-betweens”.

The Steering Committee and Customer Advisory Board will convene at least once a month. OPM will chair the Steering Committee and Customer Advisory Board and will seek support from the contractor for briefing materials. The contractor may participate in meetings as determined by OPM and the specific meeting agenda.

The OPM and OMB Directors will reserve the final decision-making authority on critical priorities and major system configurations, customizations, and/or enhancements. This reserved authority ensures that any significant changes or updates to the system align with the strategic objectives of the federal government. By maintaining centralized control over these decisions, the OPM and OMB Directors can guarantee that the Federal Core HCM platform remains cohesive, efficient, and responsive to the evolving needs of federal agencies. Additionally, this governance allows for swift adaptation to regulatory changes and technological advancements, thereby preserving the platform's integrity and effectiveness.

At a minimum, the Core HCM platform must include functionality tied to the following functions of Federal Human Capital Business Reference Model 4.0 (HCBRM), and cross walked in Appendix A:

2.2 A1.3 Position Management

• Position Management entails a carefully designed position structure that blends the skills and assignments of employees with the strategic mission and objectives of the organization.

2.3 A1.4 Employee Engagement

• Employee and Manager Self-Service: Access to personal information, pay stubs, benefits enrollment, leave requests, and training records, allowing employees to manage their own HR needs. The manager self-service portal must offer tools for managing team information, approving leave requests, conducting performance reviews, and tracking team performance. Both portals must feature mobile-friendly interfaces to allow access from any device, anywhere, and will be designed with user-friendly interfaces to enhance the overall user experience.

2.4 A3 Talent Development/Learning

• Learning: Support employee training and development by providing tools to create, manage, and deliver training courses and programs. The Learning Management System (LMS) will serve as the government-wide platform for learning, consolidating training resources and opportunities across federal agencies, while also enabling program and agency-specific training. Employees will benefit from personalized learning paths tailored to their roles, skills, and career goals, with robust progress tracking features to monitor advancement and completion of training programs. Certification management will automate the tracking of required credentials, certifications, and licenses, ensuring employees meet mandated training standards. E-learning capabilities will provide on-demand access to online training materials and resources for self-paced learning. By supporting both government-wide and agency-specific training, the LMS will enhance the overall training and development experience, fostering professional growth for employees and contributing to the success of the organization and the federal workforce as a whole.

2.5 A5 Compensation and Benefits (including Time and Attendance with integration to Federal payroll providers)

• Time and Attendance: Accurately track and manage employee time and attendance, comply with labor laws and regulations. Time tracking tools to allow employees to clock in and out, track hours worked, and report overtime, while leave management features automate the processes for requesting, approving, and tracking leave. Compliance with labor laws and regulations regarding working hours and leave entitlements to seamlessly integrate with payroll and other HR systems for accurate and timely payments.

• The Core HCM platform must provide both a time and attendance module and also be capable of integrating with time and attendance systems used by government agencies. Some agencies will immediately begin using the Core HCM time and attendance module, while others will start by having the Core HCM platform integrate with their current time and attendance system for a period of time until they are ready to implement the Core HCM time and attendance module.

• The Core HCM platform must be capable of interoperating with government payroll providers.

2.6 A9 Human Capital Analytics and Employee Records

• Analytics and Dashboards: Real-time dashboards to display key HR metrics and trends, allowing for quick and informed decisions at a local, enterprise, and government-wide level. Customizable reports to enable users to create and tailor reports based on specific needs and criteria, while predictive analytics tools will help forecast trends and identify potential issues before they arise. Data visualization features that present data in a visual format, making it easier to understand and analyze, ultimately improving the ability to make data-driven decisions.

• Employee System of Record: Include comprehensive employee profiles containing personal, employment, and contact information, as well as detailed records of each employee's work history (e.g., positions held, promotions, and transfers). Secure document management to store and manage employee-related documents such as contracts, performance reviews, and certifications. Robust data security measures to protect sensitive employee information, to remain confidential and secure. The employee record is consistently maintained even with the employee transitions between Federal agencies.

2.7 X1 Personnel Action Request Processing

• Personnel Action Processing: Feature automated workflows to simplify the initiation, approval, and processing of personnel actions, ensuring all necessary steps are completed efficiently and accurately.

Notifications and alerts generated automatically to inform relevant stakeholders of action items and approvals, reducing delays and improving communication. Compliance tracking for all personnel actions adhere to federal regulations and policies, while audit trails will maintain detailed records of all actions for auditing and reporting purposes.

The government anticipates that all existing agency/department Core HCM data will be migrated from the current Core HCM solution into the Federal Core HCM platform. Additionally, the government anticipates that the solution provider will provide the appropriate migration reporting as outlined in the PWS. The government anticipates that certain agency Core HCM systems may have built-in capabilities that can accelerate customer data migration.

The Core HCM platform will play a crucial role in integrating with other federal HRIT systems to ensure a seamless flow of information across various HR functions. Integration will enable efficient data exchange and synchronization, reduce redundancy and ensure consistency across all HR processes. Connecting these systems to facilitate comprehensive reporting and analytics, providing a holistic view of HR operations and supporting better decision-making. All integrations will ultimately contribute to a more streamlined and effective HR infrastructure for the Federal Government. More details and a list of application integrations expected can be found in Appendix B - Required System Integrations.

The government requires a Core HCM platform environment capable of operating in concert with Federal infrastructure, security, accessibility, and network policies to include, but not limited to:

• Software/ Application production, support, maintenance

• Systems management

• Data storage and management

• Data backup and recovery

• Application management

• Release management, upgrades, and patches

• Application configuration

• Incident management and reporting

• Systems integration

• Systems engineering

• Information system engineering

• Vulnerability management

The contractor shall provide risk identification and mitigation, continuous modernization, and innovation as part of the Core HCM platform. The contractor shall also manage the user experience, customer experience, and product design and improve service delivery using leading industry practices and human-centered design concepts. These methodologies will be executed to ensure optimal benefits for the various anticipated roles of system users.

See Appendix A – Functional Requirements Matrix, for a full list of functional requirements and Section 5 for Specific Tasks and Deliverables.

In scope:

**Dotted lines denote staggered go-live

Out of scope:

Payroll & Benefits

Hiring Assessments

Performance Management

Talent Acquisition

Employee system of record

Personnel action processing

Employee self-service

Manager self-service

Workforce Analytics

Time and Attendance

LearningPosition Management

Integration with payroll and talent management systems

Scope of Work

3 HIGH LEVEL OBJECTIVES

The objective of the Core HCM platform is to provide a centralized system across Federal Government, improve HR processes (e.g., transparency, efficiency, and accountability), reduce costs, improve all user experience, and reduce the HRIT integrations to support the lifecycle of federal employees.

The Core HCM platform will support approximately 2 million federal employees. At a minimum, it shall be adaptive, scalable to include multi-tenant capabilities, role-based workflows, and interoperate with agency systems. In addition, it shall provide the capability to support the divergent federal agency requirement HRIT landscape and federal civilian workforce.

To achieve this goal, the contractor shall leverage agile methodologies and industry best practices in planning, development, and execution processes. This approach will ensure continuous capability enhancements, minimal downtime, prompt responses to emerging needs, demonstrated reliability and availability, and optimized performance. These practices must align with OPM’s requirements, including those that facilitate the implementation of Executive Orders, OPM memorandums, or other policy documentation.

It is the intent for the Core HCM to be implemented across the entire federal government by July 4, 2027. The Government requires the Contractor to successfully provide at a minimum, but not all-inclusive, the following services and deliverables.

3.1 Core Implementation

FedRAMP moderate or higher certified Core HCM Software as a Service (SaaS) platform with functionality that will enable standardization of Core HRIT and processes across the federal government with minimal customization to meet federal legislative and regulatory requirements.

• Configure and customize the Core HCM platform to meet base functional requirements outlined in the PWS and provide the Authority to Operate (ATO) for system use.

• Provide interoperability between Core HCM platform and other systems outlined in Appendix B.

• Provide strategy for timely accurate data migration from the current HCM systems to the new Core HCM platform.

• Change management and project management to include the user materials to enhance the transition and knowledge for the new platform.

3.2 Agency Transition

Agency-specific transition planning, preparation, and trial usability access in the centralized Core HCM platform.

• Configure and customize the Core HCM platform with any agency-specific customization and configurations.

• Provide agency-specific interoperability between Core HCM platform and other HR systems.

• Complete data migration to the Core HCM platform from each agency’s current systems that is accurate and complete while minimizing business interruption and work stoppages.

• Test and ready the platform for agencies in Production.

• Provide platform access for all system users within the agency to validate production use and platform usability.

• The Core HCM platform will be deployed across all Federal agencies—serving approximately 2 million users—with a phased rollout to align with the government-wide implementation goal of July 4, 2027.

3.3 Licensing and Sustainment

Licensing, sustainment, and ongoing modernization of the centralized Core HCM platform by federal agencies.

• Ensure continuous user access to the Core HCM platform through active system licenses.

• Regular industry-leading, innovative updates and operations/maintenance of the platform.

• Provide continued change management and project management to include user materials to enhance the transition and knowledge for the new platform.

• Tier 2 and Tier 3 help desk support and ticketing resolution.

4 PERFORMANCE REQUIREMENTS

4.1 Period of Performance

Period Estimated Period of Performance

Base Ordering Period 10-years

The ordering period shall encompass all planning, configuration, testing, deployment, stabilization, support, license and sustainment activities necessary for the implementation and continued modernization and enhancements of the Core HCM platform.

4.2 Place of Performance

The place(s) of performance will be identified in each TO. For planning purposes, primary places of performance will include contractor and government facilities in the CONUS.

Performance at various CONUS locations, including deployments to provide technical support, will be identified in the TO.

4.3 Program Performance Outcomes

Completion of all milestones by the milestone dates, dates will be specified in the IDIQ TO. Performance will be based on the following outcomes:

Key Milestones

Milestone Core Implementation

1. Establish platform environments

2. Complete Privacy Impact Assessment and Achieve Authority to Operate

3. Complete platform configurations and interoperability with other systems

4. Test and receive OPM approval for governmentwide version of platform

Agency Transition

1. Complete agency-specific platform configurations and interoperability with other systems

2. 30-day sign-off of trial and usability access

3. 6-month sign-off of trial and usability access

Licensing and Sustainment

1. Deliver licenses, ongoing platform access and platform updates, conduct change management and project management

4.4 Travel

CONUS travel may be required to support TOs, including but not limited to:

1) Platform deployment and set‑up

2) Operational support activities

3) Test and evaluation activities

4) Rapid prototyping

5) Associated training and maintenance activities

The following travel policies and procedures apply:

4.4.1 Pre‑Approval Requirement

1) All travel and associated expenses must be pre‑approved in writing by the CO or COR prior to incurring any travel expense.

2) The Contractor shall submit an Estimated Travel Cost Request that includes:

a. Purpose of travel

b. Destination(s) and duration

c. Estimated transportation, lodging, meals, and incidental expenses

d. Any requests for exception to allowable per diem rates (e.g., hotel rates exceeding GSA limits)

3) Approval documentation must be submitted with the invoice for reimbursement.

4.4.2 Allowable Costs

1) Reimbursement will be made for allowable and reasonable travel costs in accordance with the Federal Travel Regulations (FTR) and applicable contract provisions.

2) The Contractor shall not invoice the Government for any associated fee or profit above the actual costs incurred for travel.

3) Overhead and General & Administrative (G&A) costs shall not be allowable for travel.

4.4.3 Cost Limitations

1) If the Contractor incurs travel costs in excess of the amount negotiated and agreed upon for each activity, the excess costs will be at the Contractor’s expense.

2) Reimbursement of local travel and commuting expenses is not authorized.

3) Local travel is defined as travel within a 50‑mile radius of the designated worksite.

4) The worksite will be identified in each IDIQ TO.

5 SPECIFIC TASKS AND DELIVERABLES

The Contractor shall provide, at a minimum, the following requirements.

5.1 Core Implementation

5.1.1 Core HCM Platform Readiness (described in Section 2: Scope of Work)

1) Stand up and provide access to the FedRAMP Moderate or higher certified Core HCM platform solution environments including Sandbox, Development1 and Development2, User Acceptance Testing (UAT) Staging, UAT1 and UAT2, Pre-production Gold/Staging, Production, and Post-production, for the purchased components of the Core HCM platform.

2) Stand up and provide access to FedRAMP Moderate certified Core HCM application services for the purchased components of the Core HCM platform.

3) Integrate and implement OPM approved identity management solution using OPM MS Entra-based solution.

4) Ensure the platform is a single platform that maintains a single code line on the latest version of the product.

5) Complete the OPM ATO evaluation process and receive a single ATO for the platform. In addition, support the preparation and submission of documentation for achieving an ATO, to obtain necessary approvals for system operation, complying with FISMA, NIST 800-53, and other federal security guidelines. OPM’s ATO covers any agency’s use of the platform. The ATO will be required before any work can be done in Production.

6) As part of ATO preparedness, ensure compliance with OPM policies and expectations for system availability and recovery through a Resilience Strategy/Plan that includes the following:

a. Disaster Recovery and Business Continuity: The Contractor shall maintain a fully documented and annually tested Disaster Recovery (DR) and Business Continuity Plan (BCP) that ensures uninterrupted service delivery in the event of a system failure, regional outage, or other catastrophic event. The Contractor shall implement:

i. Active-active or active-passive redundancy across geographically separated data centers.

ii. Automated failover mechanisms to minimize downtime.

iii. Real-time data replication to ensure zero data loss.

b. The Contractor shall notify the Government within 30 minutes of any event that triggers the DR plan and provide regular updates until full-service restoration.

c. Recovery Time Objective (RTO): The Contractor shall ensure that, in the event of a service disruption, the SaaS application and all associated services are restored and fully operational within a maximum Recovery Time Objective (RTO) of 12 hours. The Contractor shall provide evidence of DR testing that demonstrates the ability to meet this RTO upon request.

d. Recovery Point Objective (RPO). The Contractor shall ensure data loss is less than 1 hour (RPO < 1 hour 0) in the event of a system failure or disaster. This shall be achieved through:

i. Real-time or near-real-time data replication across redundant systems.

ii. Transactionally consistent replication to ensure data integrity.

iii. The Contractor shall provide documentation of the data replication architecture and testing results upon request.

e. Backup and Data Restoration. The Contractor shall test backup and restore procedures at least quarterly and provide test results to the Government upon request. The Contractor shall:

i. Perform automated full and incremental backups of all customer data at least every 24 hours.

ii. Implement real-time replication to a secondary site to support zero RPO.

iii. Encrypt all backups using FIPS 140-2 compliant encryption in transit and at rest.

iv. Retain backups for a minimum of 30 days, unless otherwise specified by the

Government.

v. Provide the ability to restore any data set within 30 minutes of request.

f. Performance and Compliance Monitoring. The Contractor shall:

i. Continuously monitor system availability, backup success rates, and DR readiness.

ii. Provide the Government with monthly reports on RTO/RPO performance, backup status, and DR test outcomes.

iii. Notify the Government of any deviation from agreed RTO/RPO thresholds within one

(1) business hour.

7) Complete a Privacy Impact Assessment (PIA) to ensure compliance with privacy regulations, protecting sensitive information and maintaining data privacy.

8) Develop a detailed Master Test Plan that defines test procedures, demonstrating that each technical and functional requirement element identified is addressed in testing. The Master Test Plan shall document items to be tested, test strategy, test criteria, test scripts, test deliverables, test schedule, test environments and locations, test data, staffing and training needs, risks and constraints, test metrics, patch dependencies, and coordinating Memoranda of Understanding with test sites.

9) Conduct user acceptance testing, to confirm the platform meets all user requirements, ensuring user satisfaction and system readiness. OPM will approve all testing.

10) Prior to initiating configuration activities, the Government, supported by the Contractor, shall conduct a comprehensive Fit-Gap Analysis to evaluate the alignment between the OPM business processes, functional requirements, and the baseline capabilities of the proposed Core HCM platform. The analysis shall identify areas where existing Core HCM functionality meets OPM’s requirements (“fits”) and where modifications, configurations, or business process changes are required (“gaps”). The Contractor shall document all findings in a Fit-Gap Analysis Report, including recommended approaches and timelines to address each identified gap, associated risks, and estimated effort. The Fit-Gap Analysis Report shall be reviewed and approved by the Government prior to commencement of Core HCM configuration.

11) Develop core system configuration in alignment with federal standards, to ensure the platform meets all functional and compliance requirements, adhering to the Guide to Data Standards, Guide to Processing Personnel Actions (GPPA), Government Performance and Results (GPR), Human Capital Information Model (HCIM) and those required by the government IAW Appendix A. It is the intent of government for the platform to have a common federal baseline configuration.

12) Configure the Core HCM platform in all environments to meet the government requirements. Release and test post-launch operations and maintenance items (ongoing system releases, security patches, and updates aligned with industry standards) in all environments.

Software Functionality Definitions for purposes of this PWS:

• Out-of-the-Box Functionality. Out of the Box Functionality is any functionality of the SaaS Core HCM platform that can be used as-is from templates, built-in workflows, and/or best practices provided directly by the Contractor. OPM’s definition of Out of the Box Functionality does not include functionality that can be configured to meet the functional requirements.

• Configuration. Configuration is defined as adjustments made to the SaaS Core HCM platform through delivered workflows, rules, security settings, and administrative features but does not start from an as-is capability. To be considered configurable, functionality must be forward-compatible with future releases. Platform extensions are considered configurations.

• Customization. The Government understands that it may be necessary to apply customizations to deliver the required capabilities. However, any approved and implemented customization must preserve the integrity, security, and upgradability of the Core HCM platform’s environment.

o Definition. Customization means any modification to the SaaS Core HCM platform’s delivered code, data model, or core logic that is beyond vendor-supported configuration, extension, or integration tools. Customization does not include configuration.

o Configuration-First Principle. The Government expects that the Contractor shall implement all functionality using standard configuration, personalization, or vendor-approved extensibility frameworks. Customizations may be proposed only when the required functionality cannot reasonably be achieved through configuration or integration and must be approved in writing by the Contracting Officer (CO) upon recommendation of the Contracting Officer’s Representative (COR) via the Steering Committee.

o Maintenance and Responsibility. The Contractor shall be responsible for maintaining approved customizations, ensuring compatibility with vendor upgrades and patches, and providing complete technical documentation to the Government. Any adverse impact caused by a customization shall be remediated by the contractor at no additional cost to the Government.

o Compliance. All customizations must comply with vendor support policies, licensing terms, and applicable federal information security and privacy requirements, including FedRAMP and the OPM ATO.

13) Release and test core implementation configurations In Accordance With (IAW) Appendix A in the non-production environment(s).

14) Release and test core implementation configurations IAW Appendix A in the production environment(s) after receiving go-live approval from the government.

15) Develop core implementation customizations required by the government IAW Appendix A.

16) Release and test (go-live) core implementation customizations IAW Appendix A in the production environment(s) after receiving go-live approval from the government.

17) Provide ongoing system backup and administration to allow for the continuation and expedient recovery of essential services for the Core HCM platform.

18) Provide an Incident Outage Report to the government, tracking all planned and unplanned system outages (downtime) lasting 30 minutes or longer, the resolution, and the mitigation strategy to prevent future unplanned outages covering the purchased components of the Core HCM platform.

19) Provide a Security Incident Report to the government, tracking and reporting all security incidents, the extent of the compromise, especially as it relates to privacy data, and all actions taken for incidents detected or suspected across the purchased components of the Core HCM platform.

20) Provide ongoing system testing, maintenance, and support to ensure continuous system operation and address any issues while maintaining system performance and availability.

21) Perform continuity testing at least annually to ensure system stability and reliability.

22) Develop a System Requirement Backlog of change request items, bugs, etc.

23) Provide automated, scheduled data extractions and system backups to ensure continuity of operations, minimize data dependency, and support recovery and reporting needs.

24) Develop dashboard of key system metrics updated daily including metrics…