Attachment 4 PSHBS TO PWS_Amendment 2.docx
DOCX document 70 KB Posted
- Attached to
- Postal Service Health Benefits System (PSHBS)
- Solicitation number
- 24322623R0004
- Issued by
-
Office of Personnel Management
About this file
This performance work statement outlines the requirements for a contractor to develop and deliver a Postal Service Health Benefits System to support the Postal Service Health Benefits Program established under the Postal Service Reform Act. Key requirements include developing and delivering a scalable system to process enrollments, determine eligibility through data exchanges with partner agencies, provide decision support tools to compare plan options, reconcile enrollment and premium transactions, and conduct analytics and reporting on enrollment data. The contractor must also deliver minimum viable product capabilities for decision support, eligibility determination, data analytics, and enrollment processing by specified dates to support the initial open season period beginning in November 2024. Additional requirements include establishing governance, developing architecture and technical plans, ensuring regulatory compliance, conducting user research and design, and providing operations and maintenance support over the two year base period of performance.
View the file
Other files
Show all 30
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
RFP 24322623R0004 Postal Service Health Benefits System (PSHBS) Indefinite Delivery, Indefinite Quantity (IDIQ) Contract Office of Personnel Management (OPM) Postal Service Health Benefits Central Enrollment System and Customization Services Performance Work Statement (PWS)
Table of Contents
| 1.0 GENERAL | 1 |
| 1.1 Background | 2 |
| 1.2 Scope | 2 |
| 1.3 Relevant Federal Laws and Regulations | 2 |
| 2.0 SPECIFIC REQUIREMENTS | 3 |
| 2.1 Overview | 3 |
| 2.2 Contractor-Proposed Enhancements and Improvements | 5 |
| 3.0 Key Personnel | 5 |
| 3.1 Key Personnel | 6 |
| 4.0 PERIOD(S) OF PERFORMANCE | 7 |
| 5.0 DELIVERABLES | 7 |
| 7.0 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP) | 17 |
| 8.0 PLACE(S) OF PERFORMANCE | 17 |
| 10.0 HOURS OF OPERATION | 18 |
| 11.0 CONSTRAINTS | 18 |
| 12.0 TRAVEL | 18 |
| 12.1 Base Period and Option Period Travel | 19 |
| 12.2 Travel Related to Service Failures | 20 |
| 13.0 GOVERNMENT FURNISHED PROPERTY (GFP) | 20 |
| 14.0 INCIDENT REPORTING | 20 |
| 15.0 SECURITY CLEARANCES AND BACKGROUND INVESTIGATION | 20 |
| 16.0 CONTRACTING OFFICER’S REPRESENTATIVE (COR) | 21 |
1.0 GENERAL
As the Federal government’s human resources agency, the United States Office of Personnel Management (OPM) administers health insurance benefits for over 8 million Federal employees, retirees (“annuitants”) and their families. The Federal Employees Health Benefits (FEHB) Program covers a majority of those employed and retired from the Executive, Legislative and Judicial Branches of the Federal government, including employees and retirees of the United States Postal Service, temporary wildland firefighters and fire protection personnel, employees of Federally recognized Indian tribes, tribal organizations, and urban Indian organizations (tribal employer), and their eligible family members. Offerors can find more information about OPM and the benefits we administer on www.opm.gov/insure.
1.1 Background
Title I, Section 101 of The Postal Service Reform Act (PSRA, Pub. L. 117-108) requires OPM to establish the Postal Service Health Benefits (PSHB) Program, a health insurance program that will operate with a separate risk pool from the FEHB Program. The PSHB Program will offer coverage to the current FEHB-eligible Postal population of an estimated 1.7 million United States Postal Service (USPS) employees, annuitants, and their eligible family members currently enrolled in the FEHB Program. OPM is also responsible for enrolling Postal employees and annuitants in the PSHB Program. Under the Act, certain Postal Service annuitants are required to enroll in Medicare Part B, necessitating an eligibility determination based on partner Federal agency data.
1.2 Scope
Effective January 1, 2025, all current FEHB-eligible USPS employees, annuitants, individuals receiving workers compensation (“compensationers”), and their family members will only be eligible for health insurance coverage through the PSHB Program. During the initial open season in the fall of 2024, all PSHB eligible individuals will have the opportunity to enroll in a PSHB health plan of their choosing. If no choice is made during the initial open season, FEHB-enrolled PSHB eligible individuals will be auto-enrolled into a PSHB plan based on criteria in the Postal Service Reform Act (PSRA). PSHB coverage will begin in plan year 2025.
To meet PSRA statutory requirements, the contractor will work with OPM to develop and deliver a Postal Service Health Benefits System (herein referred to as PSHBS, or “the system”). Although the initial user base will include 1.7 million USPS enrollees, the PSHBS system will be built using scalable, flexible technology that enables OPM to (potentially) service approximately 6.5 million federal employees, annuitants, and eligible family members.
Starting in the fall of 2024, the system will process all enrollments and changes in enrollments for PSHB, including open season transactions, qualifying life events, and enrollments for newly eligible. The fully functional system will provide an account-based, one-stop-shop where enrollees can: 1) compare and learn about PSHB plan options, including benefits, provider networks, formulary, cost-sharing, and total out-of-pocket expenses, 2) select a plan that fits the unique needs of their family, and 3) complete the enrollment process. The system will also serve as the authoritative source for PHSBP enrollment data, ensure enrollee eligibility by exchanging data with relevant Federal agencies, and provide real-time enrollment and premium transaction information to all employing agencies and participating PSHBP health insurance issuers (herein referred to as Carriers).
The system will include a web-based portal for self-service enrollment transactions and robust decision support tools to assist enrollees. The system will also support enrollment transaction processing and ongoing reconciliation of enrollment and premiums.
1.3 Relevant Federal Laws and Regulations
Section 101 of the Postal Service Reform Act of 2022 (PSRA), Pub. L. 117-108, added new section 8903c to chapter 89 of title 5, United States Code, and directs OPM to establish the Postal Service Health Benefits (PSHB) Program for Postal Service employees, Postal Service annuitants, and their eligible family members. OPM will administer the PSHB Program in accordance with Chapter 89 of Title 5, United States Code and implementing regulations (title 5, parts 890 and 892, and chapter 16 of title 48, Code of Federal Regulations).
The contractor must be intimately familiar with the laws and regulations of the PSHB Program, to ensure contractual operations are in full compliance. Changes in the laws and regulations may affect system requirements and the PSHBS system must be updated to accommodate any such changes. OPM will evaluate offerors capabilities and insights through evaluation of their Corporate Experience and as a non-functional requirement to the RTM.
2.0 SPECIFIC REQUIREMENTS
2.1 Overview
OPM has a requirement to procure and deliver specific capabilities outlined below and integrate them into a solution with a seamless user experience. As noted above, the system will be built using scalable, flexible technology that enables OPM to (potentially) service approximately 8.5 million federal employees, annuitants and eligible family members.
Please refer to the attached Requirements Traceability Matrix (RTM) for all functional and non-functional requirements related to PSHBS and associated services.
In summary, through delivery of this Core Task Order, the PSHBS must have the capability to perform the following:
I. Eligibility Determination- PSHB annuitant enrollment requires routine exchange of enrollment data with the Social Security Administration, OPM Retirement Services, Department of Labor, Department of Veterans Affairs, and Indian Health Service to determine exceptions to the Medicare Part B enrollment requirement for Medicare eligible Postal Service annuitants and Medicare eligible family members. The PSHB will allow users to upload additional eligibility documentation.
II. Decision Support - Provide information to assist enrollees in making informed plan selection decisions. A primary component of the decision support process will be a web, tablet, and mobile-optimized tool allowing users to search and compare various PSHBP plan options.
III. Enrollment Processing - Create, operate, and maintain an enrollment portal and database to accept and process enrollment actions. Perform verification of family member eligibility.
IV. Enrollment Reconciliation - Ensure program integrity through enrollment data matching with Carriers and employing agencies.
V. Payment Processing – Collect premium payment confirmation data to ensure accurate accounting of payments by enrollees.
VI. Premium Reconciliation - On a regular schedule as proposed, maintain a record of premiums due for each enrollee, Payroll Office, and Plan Code, and communicate the balance and transaction details of records, and reconcile against actual premium amounts transferred between Payroll Offices, OPM, and Carriers.
VII. Data Analytics and Reporting – Capable of providing robust analysis of data housed in a data warehouse to include reporting and analytical tools.
In addition, the contractor must deliver the following minimal viable product (MVP) capabilities by the dates listed:
Definition of Minimum Viable Product (MVP):
| Timing |
| Function/Capability |
| MVP |
Sept 30, 2024 for Open Season (which begins in November 2024)
Decision Support
· The PSHBS shall have the ability for customers to search key health plan characteristics including premium, cost sharing (including for those with Medicare), with link to health plan brochure for more detailed information.
· The PSHBS shall follow industry best practices for modern, intuitive, similar decision support tools.
· The PSHBS shall provide anonymous shopping capability.
· The PSHBS shall have the ability to ingest and process carrier-specific information from OPM Systems (e.g., Carrier Connect).
Sept 30, 2024 for Open Season
Eligibility (All)
· The PSHBS shall have the ability to receive, ingest, and process necessary data from USPS to determine employee eligibility status.
· The PSHBS shall have the ability to receive, ingest, and process necessary information from OPM RS to determine current annuitant status.
· The PSHBS shall have the ability to exchange Flat Files on a predetermined schedule using secure means of transmission.
September 30, 2024
Data Analytics
· The PSHBS shall have the ability to analyze enrollment data using BI software, including standard reporting, query building capability, and (for certain analysts) open access using preferred analytic software.
· Per the PWS and RTM, OPM will own all PSHBS data; the vendor provides the data to OPM, as directed.
Oct 31, 2024
Reporting
· The PSHBS shall have the ability to create one-off reports, as needed.
· The PSHBS shall have the ability to release reports through the regular release cycle.
· The PSHBS will provide specific reports as defined in the RTM.
Oct 31, 2024 for Open Season
Enrollment Processing (w/ Carriers)
· The PSHBS shall be able to capture enrollee selection and send information to Carriers participating in PSHBP, using current processes with Data Hub (vendor to connect to Data Hub and not to all carriers).
· The PSHBS shall also provide the capability to send to RS, USPS and NFC for withholdings and contributions to premiums, including the financial management systems and programmatic systems.
Dec 15, 2024
Premium Payment
· The PSHBS shall enroll individuals paying directly using the National Finance Center to collect direct payments .
Dec 15, 2024 Immediately following Open Season
Auto-enrollment
· For individuals who do not select a PSHB plan, the system shall automatically enroll said individuals in a similar plan using criteria from PSRA and Interim Final Rule.
((OPM to provide vendor with crosswalk table showing FEHB plan and equivalent PSHB Plan (or default plan). Notifications will be provided, as delineated in the RTM)).
Mar 1, 2025
Enrollment Reconciliation
· The contractor shall create and pull required reports to validate enrollment and have a mechanism for the carriers to access this data (either through roles / privileges in PSHBS or exporting the reports into the Carrier Connect).
October 30, 2025
Premium Reconciliation
· The contractor shall use existing processes for premium payment and reconciliation (at the agency level).
Please refer to the attached Requirements Traceability Matrix (RTM) for ALL functional and non-functional requirements related to PSHBS, the MVP and associated services.
3.0 Key Personnel
The following personnel utilized in performance of the services described herein are considered “Key Personnel.” Key Personnel changes and substitutions shall be kept to an absolute minimum and shall be in accordance with clause 1752.209-71 Contractor’s Key Personnel (July 2005). Key Personnel changes within the first year of performance will be negatively reflected on contractor’s performance evaluation report. Communication is key to a strong positive relationship. Refer to Key Personnel Clause for additional information.
If the contractor personnel will be performing any of the duties described in the descriptions below, they are considered Key Personnel, regardless of the title used by their employer.
3.1 Key Personnel
| Senior Program Manager |
| The Senior Program Manager coordinates activities between multiple projects to ensure they align with the organization's goals. |
Experience and Expertise: 15+ years’ experience managing large scale programs, maintaining strict adherence to deadlines through an agile approach to product and program management, and coordinating across multiple stakeholders. Experienced in deploying customized solutions, including experience in overseeing the deployment of complex benefits systems. Has led large initiatives to develop strategies for business and technology transformation for public and private healthcare organizations and managed large and complex business transformation projects for public and private healthcare clients to implement new and evolving technologies.
| Chief Solution Architect |
| The Chief Solution Architect is responsible for defining and communicating a shared technical and architectural vision for the PSHBS Agile Release Train (ART) to help ensure the solution meets or exceeds benefits administration needs of USPS employees, annuitants, and their families. |
Experience and Expertise: 10+ years’ experience in delivering tailored solutions for clients to including the deployment of large, complex systems.
| Release Train Engineer |
| The release train engineer (RTE) facilitates program level processes and execution, drives continuous development, manages risks and escalates impediments while also acting as a full-time chief scrum master for a Scaled Agile Framework (SAFe). |
Experience and Expertise: 5+ years’ experience leading the deployment of technology systems and introducing and championing the implementation of risk mitigation strategies which have resulted in timely release deliveries, and improved customer experience.
| Benefits SME |
| The Benefits SME is an expert in the Federal employee benefit marketplace and ensures the PSHB Program and System meets OPM requirements. |
Experience and Expertise: More than 15 years expertise in health benefits consulting (government or otherwise)
| Lead Product Manager |
| The Lead Product Manager supervises the entire product development process from beginning to end, overseeing many steps, such as customer needs evaluation, product cost estimation, designing product schedules, creating product backlogs, and coordinating with all product stakeholders. |
Experience and Expertise: Experience in providing a portfolio strategy and vision for the implementation of a new product or solution.
4.0 PERIOD(S) OF PERFORMANCE
The contractor shall customize and deliver a fully functional system, as described above, to support Open Season 2024. The period of performance for this task order is 24 months consisting of a two (2) year base period and no option periods.
5.0 DELIVERABLES
A series of key tasks and deliverables will support the development of system functionality. The contractor shall provide Systems Development Lifecycle (SDLC) documentation, as required by OPM, for each stage of the development lifecycle. This includes a Project Management Plan, as described below. The primary deliverables are the development and delivery of a system that specifically addresses the unique requirements as outlined in the PWS and RTM for enrollment, premium administration, and related services.
The contractor must review, revise and distribute SOPs, manuals and training materials for the PSHBS system at least once per year, including upon publication of new, relevant regulations and/or statutes. The Government will review any edits before the contractor finalizes each new version.
During performance of the contract, the contractor must deliver upon the following according to the solution they have described in their technical proposal, as approved by OPM prior to award. Any changes from the approved technical proposal shall require approval by the Contracting Officer prior to the contractor executing those changes.
| Category |
| Deliverable |
| Description |
| Due Date |
| Program & Project Management |
| Project Charter |
| The PSHB project charter should include a statement of scope, objectives and people who are participating in a project. It begins the process of defining the roles and responsibilities of those participants and outlines the objectives and goals of the project. |
| 10 days after award. |
| Project Management Plan |
| The PSHB Project Management Plan (PMP) will baseline the scope, schedule, and cost associated with the program. It should include details related to scope, scope, schedule, cost, quality, human resources, communications, and risk. It will also address the establishment of additional plans to include, but not limited to, requirement management plan, change management plan, configuration management plan, and a process improvement plan. |
| 30 days after award. |
| Work Breakdown Structure (WBS) |
| The PSHB Work Breakdown Structure will identify large batches of work necessary to achieve goals of the program that includes a breakdown of deliverable- oriented work into smaller, discreet batches or components. |
| 10 days after award. |
| Detailed Project Schedule |
| The PSHB Detailed Project Schedule will thoroughly explain every project activity, timeline, resources, dependencies, milestones, etc. that will be the basis for a successful implementation. |
| 60 days after award. |
| Stakeholder Management Plan |
| Will outline how the PSHB program will identify key stakeholders and establish a Responsibilities assignment (RACI) matrix that describes each role and their responsibilities related to the program. |
| 10 days after award. |
| Communications Plan |
| The PSHB Communications Plan will audit existing communications methods across OPM with internal and external stakeholders while identifying any gaps in current communication activities. Audiences will be identified, and individual SMART goals will be established for affective communications with those stakeholders related to all things related to the implementation of rollout of the PSHBS. |
| 30 days after award. |
| Risk Management Plan |
| The PSHB Risk Management Plan will outline how risks and issues will be identified, tracked, mitigated, and coordinated across the Portfolio, Program and various Teams supporting the effort. The PSHB Risk Management Plan should also align with, and feed into OPM's Enterprise Risk Management Process. |
| 30 days after award. |
| Quality Management Plan |
| The PSHB Quality Management Plan will outline how value will be incorporated into all facets of the project to include Portfolio, Program and Team related activities. The PSHB Quality Management Plan should include a detailed continuous improvement approach that will span the entire portfolio that creates a feedback loop that will influence future requirements, priorities, and value to OPM as well as USPS employees, annuitants, and their families. |
| 30 days after award. |
| Systems Development Life Cycle (SDLC) Management Plan |
| A comprehensive plan that documents how the contractor will operate within the construct of OPM’s System Development Lifecyle while adhering to the industry best practices associated with the Scaled Agile (SAFe) methodology. The Plan should include: |
| 60 days after award. |
A plan for documenting, reporting, implementing approved changes and requests (includes change control requests [CCRs] from OPM, users, stakeholders, and contractors).
Address the Configuration Control Board (CCB) and its members, regular and emergency CCBs, and the method for submitting and documenting change requests.
Describe the methodology used to ensure documentation stays updated and accurately reflects the production system, including all change requests.
Describe how the system will remain in compliance with security and other Federal IT policies and OPM’s IT policies and procedures.
A detailed map of how SAFe can coexist within OPM’s SDLC and how it will be managed.
| Lean Portfolio Management |
| Portfolio Strategy |
| Connects the PSHB Portfolio to the OPM Strategy to includes goals and objectives. This strategy will also align the Scaled Agile methodology to the broader OPM SDLC and Enterprise Architecture while setting the stage for how the program will operate in such a hybrid environment. |
| 45 days after award. |
| Portfolio Vision |
| The Portfolio Vision describes the future state of the PSHB portfolio’s Value Streams and Solutions and describes how they will cooperate to achieve the portfolio’s objectives and the broader aim of the enterprise. |
| 30 days after award. |
| Portfolio Roadmap |
| PSHB portfolio roadmap should integrate aspects of the lower-level roadmaps into a more comprehensive view, communicating the larger picture to enterprise and portfolio stakeholders. |
| 60 days after award. |
| Lean Governance |
| Establishes the fundamental principles of financial governance for the PSHB program for the development and deployment of the PSHBS ensuring the portfolio operates and delivers within the approved budget. Focuses on funding value streams and not projects, guides the portfolio investments by horizon, and allows for adaptability as new requirements are identified and priorities shift. The Lean Governance should outline how the portfolio will be continuously measured, establish forecasting and dynamic budgeting, and coordinate continuous compliance. |
| 45 days after award. |
| Requirements Management |
| Requirements Management Plan |
| The PSHB Requirements Management Plan should outline the process for documenting, analyzing, tracing, prioritizing, and agreeing on requirements, Epics, Features, and User Stories and how changes will be controlled and communicated to relevant stakeholders continuously throughout the project. |
| 30 days after award. |
| Requirements Traceability Matrix |
| The PSHB Requirements Traceability Matrix maps and traces user requirement, including Epics, Features and User Stories with associated test cases that may include, but is not limited to unit tests, regression tests, user acceptance tests, etc. The contractor will be responsible for analyzing the functional and non-functional requirements captured in the RTM, identify any gaps, and address said gaps to deliver the PSHBS on time and budget. |
| 90 days after award. |
| Portfolio Backlog |
| The PSHB Portfolio Backlog will include large initiatives (Epics) that must be prioritized, reprioritized, and sequenced to meet the objectives of the Program and the Postal Reform Act. |
| 45 days after award. |
| Program Backlog |
| The PSHB Program Backlog will include a prioritized list of features that must be prioritized, reprioritized, and sequenced to meet the objectives and goals of the current and future program increments. |
| 90 Days after award. |
| Team(s) Backlog(s) |
| The PSHB Team Backlogs will include a prioritized list of user stories that must be prioritized, reprioritized, and sequenced to meet the objective and goals of each team associated with each 2-week increment. |
| Upon commencement of each Program Increment. |
| Change and Configuration Management |
| Enterprise Change Management Plan |
| The PSHB Enterprise Change Management Plan defines OPM’s approach to managing cross-organizational needs and their relationship to systems and infrastructure changes required to maintain or improve delivery of PSHBS. This plan will also have to incorporate plans to address the complexities of changes that span multiple agencies to include USPS, Treasury, VA, CMS, SSA, etc. |
| 90 Days after award. |
| IT Change Management Plan |
| The PSHB IT Change Management Plan should outline the process responsible for controlling the lifecycle of all changes with minimum disruption to IT services related to PSHBS. This plan will need to align tightly with the OPM OCIO ITSM-based process. |
| 60 days after award. |
| Configuration Management Plan |
| The PSHB Configuration Management Plan will establish and maintain how the program will drive consistency of PSHBS product's performance, functional, and physical attributes with its requirements, design, and operational information throughout the lifecycle of the service. The plan will have to align tightly with the OPM OCIO ITSM-based Configuration Management Process. |
| 60 days after award. |
| Technology & Architecture |
| Solution Architecture |
| The PSHBS Solution Architecture and Design deliverable will detail the discrete and focused operations and activities of the PSHBS and how IT will support the operations and activities leveraging both logical and physical depictions of the OPM cloud and on-premises environments. This deliverable will also identify dependencies between organizations, systems, integration points, etc. |
| 60 Days after award. |
| Detailed Design Specifications |
| A document which describes the high-level and low-level detailed design specifications, describes design goals and considerations, provides a high-level overview of the system architecture, and describes the data associated with the system, as well as the human to system interaction. This document should also detail system components, including hardware, internal communications, software, system integrity controls, and external interfaces. |
| 90 Days after award. |
| Data Architecture |
| The PSHBS Data architecture will include the models, policies/governance, rules, and standards that govern which data is collected and how it is stored, arranged, integrated, and use in data systems across OPM and its partner agencies. |
| 60 days after award. |
| Integration Plan |
| The PSHBS Integration Plan will define the integration and verification strategies for a project interface with the system design and decomposition into the lower-level elements. The plan will include all planned and required integration points within OPM and with external entities to include USPS, SSA, CMS, VA, Treasury, etc. |
| 90 days after award. |
| Cloud Hosting Plan |
| The PSHBS Cloud Hosting Plan will detail the operational and budgetary approach to hosting the solution within the OPM Azure Cloud environment. This plan should include expected license and service estimates across development, test, and production environments required to host and scale the solution over time. This plan should also include hosting models that predict costs should increases in usage or user populations increases significantly over time. |
| 30 days after award. |
| Test Management Plan |
| The PSHBS Test Management Plan will be the blueprint for conducting software testing operations as a defined procedure, which the test manager closely monitors and controls. The plan will document the scope, strategy, resources, and timetable of expected test activities, across various testing types including unit testing, regression testing, functional testing, user acceptance testing, performance testing, accessibility testing, etc. |
| 60 days after award. |
| System Configuration and Customization Plan |
| The PSHBS Configuration and Customization Plan will evaluate the functional and non-functional requirements identifying and prioritizing system configuration activities to meet those requirements leveraging customization as a last resort. This plan will also include alternative methods for achieving intended functional and non-functional requirements that may be achieved via an alternative means even if it diverges from the specifics of the requirement in question. The goal of the plan is to maximize the use of "out of the box" functionality over custom development if possible. |
| 90 days after award. |
| Release Plan |
| The PSHBS Release Plan A release will outline the strategy for capturing and tracking the features included in future releases of the solution. The release plan is an evolving, working plan for product and development teams that will span the lifecycle of PSHBS. |
| 90 days after award. |
| Security, Privacy & Compliance |
| Security, Privacy & Compliance Plan |
| The PSHB Security, Privacy and Compliance Plan will outline how the vendor will ensure alignment with various cybersecurity (e.g., FISMA), privacy and compliance (e.g., 508 compliance) requirements driven by various Federal laws and mandates as well as OPM- specific policies and procedures as outlined in the PWS and RTM for enrollment, premium administration, and related services. |
| 60 days after award. |
| Certification and Accreditation (C&A) Plan |
| A plan which outlines the methodology for obtaining Certification and Accreditation (C&A) for an ATO and maintaining its C&A status with OPM. |
| 90 days after award. |
| Administration |
| Training Plan |
| The Contractor shall collaborate with OPM to develop and provide a Training Plan, for OPM approval, that details all the activities required to efficiently, accurately, and effectively train all OPM identified and approved personnel, as well as end users in the complete use and operation of the PSHBS, in accordance with OPM’s training strategy. Once approved by OPM, the Contractor is responsible for implementing the Training Plan, as written, revised, and approved by OPM, to comply with all system and business operational standards and service levels of the enterprise-wide solution over the life of the Contract. |
| 120 days after award. |
| Staffing Plan |
| The PSHBS Staffing Plan will outline the strategic planning process designed to analyze current and future staffing needs across all of OPM and its partner agencies, be it contractor or Federal resources, focused on identifying all the staffing needs, by role and responsibilities, to deliver the program based on planned go-live dates. |
| 30 days after award. |
| Human Centered Design |
| Human Centered Design (HCD) Plan |
| The HCD Plan should outline the contractor's approach to human centered design and how the process will feed the Product Management function to ensure the solution is customer-centric and is focused on providing value to OPM, its employees, and the USPS employees, annuitants, and their families. Wherever possible, the HCD Plan should maintain alignment with OPM HCD processes as well as US Digital Services best practices. |
| 30 days after award. |
| User Research Plan |
| The PSHB User Research Plan should outline the approach by which qualitative and quantitative research methods will be leveraged to validate user requirements while driving continuous value to all users of the PSHBS. |
| 45 days after award. |
| Service Blueprints |
| A document that details current and future state benefits administration business processes to include front stage (e.g., personas, customer journeys, etc.) and backstage (e.g., data flows, system impacts, etc.) activities that highlight OPM and its partners’ user, business, data and system impacts prior to the development of PSHBS. |
| 60 days after award. |
| Personas |
| A User Persona is a fact-based visual representation of a set of users that helps design teams visualize, understand, and build relevant connections with the target users. |
| 90 days after award. |
| Customer Journey Maps |
| A Customer Journey Map enables organizations to understand interactions with its customers through various digital and non-digital touchpoints giving them insights to what motivates their customers - what their needs are, their hesitations, and concerns. |
| 60 days after award. |
| Wireframes |
| A visual guide that represents the skeletal framework of a website that can be created in both low fidelity and high fidelity to aid in user research and testing. |
| 90 days after award. |
| Operations & Maintenance |
| Operations and Maintenance Plan |
| The PSHBS Operations and Maintenance Plan will provide the details the contractor will leverage to run, maintain, update, and patch the solution once released to production. This plan will be based on ITSM best practices and in close alignment with OPM's ITSM policies, processes, and procedures. |
| 180 days after award. |
| Standard Operating Procedure Manual |
| The PSHBS Standard Operating Procedures Manual(s) will provide guidance to administrators in the form of standard operating procedures. This manual will be specific to various modules within the solution. The manual(s) will be based on ITSM best practices and in close alignment with OPM's ITSM polices, processes, and procedures. |
| 180 days after award. |
| Continuous Improvement Process (CIP) Plan |
| The CIP Plan shall outline repeatable, defined, and efficient management processes for optimization of PSHBS-related Services throughout the entire Service Lifecycle. |
| 180 days after award. |
| Service Strategy |
| The PSHBS Service Strategy shall support OPM Leadership in alignment with OPM priorities and goals. This strategy should monitor patterns of PSHBS business activity and provide suggestions for performance optimization via service design activities with OPM approval. |
| 180 days after award. |
| Transition Plan |
| In the event of a transition to a new contractor, the Transition Plan will provide the details required to adequately transfer responsibility of development and operations and maintenance activities of the PSHBS to the new contractor. |
| 30 days upon request. |
| Continuity of Operations Plan (COOP) |
| A detailed contingency/continuity of operations plan that: identifies communication procedures and protocols for activating and de-activating disaster recovery situations (in providing contingency and continuity of operations); and specifies assumptions used in the continuity of operations plans where reliance upon OPM systems, data or resources is expected. |
| 180 days after award. |
| Service Control Level Plan |
| This plan should describe: the process for scheduling maintenance, what it includes, and propose a maintenance schedule; and the process for monitoring and ensuring that service level goals are met, and necessary corrective actions are taken |
| 180 days after award. |
| Fully Functional PSHBS |
| Development, delivery, operation, and maintenance of a system that specifically addresses the unique requirements as outlined in the PWS and RTM for enrollment, premium administration, and related services. |
| 6/1/2025 |
RFP 24322623R0004 Postal Service Health Benefits System (PSHBS) Indefinite Delivery, Indefinite Quantity (IDIQ) Contract
Amendment 2 Attachment 4 Page 2 of 2
7.0 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)
The contractor’s performance shall be evaluated against a QASP tailored to the requirements and deliverables of this PWS, as well as agreed upon SLAs.
1. Monitoring Performance QASP Performance Standards are measured quarterly, and performance is evaluated annually. The contractor must report current standing of all QASP-referenced measures to OPM monthly by the end of the second full week following that month. A quarterly summary roll-up is to be provided by the contractor to OPM by the end of the second full week following the end of quarter. Reports may be required more frequently upon OPM’s request if there are performance concerns.
Standards are to be measured quarterly and evaluated annually by the contractor. The contractor must report current standing of these measures to OPM monthly by the end of the second full week following that month. A quarterly summary roll-up shall be provided by the end of the sixth full week following that. Reports may also be provided more frequently upon OPM’s request.
8.0 PLACE(S) OF PERFORMANCE
The primary place of performance shall be at a contractor-designated facility or facilities within the 50 United States or District of Columbia. None of the services of the contractor or any subcontractor may be conducted outside these geographic limitations. No services may be “off-shored.” Performance of this contract may not include any performance (permanent, or temporary, full time or part time) which takes place outside the 50 United States or District of Columbia.
The contractor is responsible for providing place(s) of performance appropriate and conducive to the work, performance standards and activities required under this contract, including providing the necessary space and security to house special equipment and/or other items as necessary to meet the needs of the Government. The contractor (and subcontractor) employees will also be required to acquire public trust security clearances for specialized staff handling Intelligence Community data.
10.0 HOURS OF OPERATION
The contractor points of contact must be available to OPM during OPM’s core business hours. Core business hours are Monday through Friday from 8:00 A.M. – 5:00 P.M. Eastern Time. The contractor must support extended business hours as determined by OPM.
11.0 CONSTRAINTS
The contractor must be aware of the following constraints that may have an impact on the services required in performance of this contract. The contractor’s solution must describe in detail the method it will use to address these constraints.
1. Section 508 Compliance – All applications to be used by enrollees or potential enrollees must be Section 508 compliant; this includes test sites. This compliance is subject to review by OPM.
2. Federal Security and Privacy – There are several constraints that may have an impact on the services the contractor must provide:
a. Compliance with Federal Information Security Management Act (FISMA) to include the National Institute of Standards and Technology (NIST) and the Office of Management and Budget (OMB) guidance
b. C&A process must be successfully completed, and C&A status maintained
c. Compliance with the Privacy Act of 1974 and related OMB guidance
d. Compliance with the privacy provisions of the e-Government Act and related OMB guidance
e. Refer to OPM Clause 1752.224-74 Privacy Act (Dec 2015) for additional information
f. Multi-factor Authentication
g. Continued Performance through Government Furloughs and Shutdowns
12.0 TRAVEL
The Government anticipates travel under this effort. Travel must be pre-approved in writing by the COR and in accordance with Federal Travel Regulations. Each contractor invoice must include copies of all receipts that support the travel costs claimed in the invoice. Local travel within a 50-mile radius from the contractor’s facility is considered the cost of doing business and will not be reimbursed. This includes travel, subsistence, and associated labor charges for travel time. Travel performed for personal convenience and daily travel to and from work at the contractor’s facility will not be reimbursed. Travel, subsistence, and associated labor charges for travel time for travel beyond a 50-mile radius of the contractor’s facility are authorized for reimbursement on a case-by-case basis and must be pre-approved by the COR and must be planned and executed according to Federal Travel Regulations. General and Administrative expenses will not be reimbursed. The Federal Travel Regulations can be located at: http://www.gsa.gov/portal/ext/public/site/FTR/file/FTRTOC.html/category/21865/hostUri/ portal.
Building and maintaining good working relationships with the contractor’s many stakeholders and partners is crucial to the long-term success of this initiative. Regular contact with stakeholders/ partners, including face-to-face meetings, conference calls, etc., is key to developing these relationships. While regular contact is important, we encourage using alternatives to onsite meetings wherever appropriate and practicable to save money.
12.1 Travel
All travel will be defined and priced as Not to Exceed. Travel by air shall be negotiated at a fair and reasonable price, not to exceed coach fare. The costs for meals and incidental expenses incurred by Contractor(s) personnel shall be considered reasonable and allowable to the extent they do not exceed, on a daily basis, the per diem rates set forth in the Federal Travel Regulations (FTR). Travel by privately owned vehicle shall be at the current GSA approved mileage rate. Except as indicated above, the Contractor(s) will be reimbursed for actual travel expenses incurred, in accordance with the FTR and FAR Part 31.205-46 - Travel costs. Contractor(s) or its representatives who incur travel costs that are more than the amount negotiated and agreed upon for each activity do so at its own expense.
The contractor should budget and plan for travel to meet with various PSHB stakeholders. The contractor should anticipate that onsite meetings may be necessary and more frequent in the first few years of the contract performance as relationships are developed.
Travel costs for the Task Order’s period of performance shall include the costs of all travel required including but not limited to:
· On Site Meetings with OPM – Allow for four trips per year to OPM’s location, at intervals mutually agreed upon by the parties.
· Annual visits to the major payroll and annuity providers (e-payroll providers and OPM annuity) as necessary and appropriate
· Ad-hoc visits to other payroll providers as needed
· Open Season Activities - The contractor may take up to ten (10) trips annually related to open season activities.
· One-on-one meetings with individual PSHB carriers, as necessary or desired
· Attendance at OPM-sponsored meetings and conferences for agency benefits officers
· Visits to subcontractors’ locations as necessary and appropriate Each travel event should include and budget for no more than three (3) contractor staff members.
If the contractor has scheduled travel to Washington DC for contract-related purposes, the contractor must inform OPM of its intent to do so. OPM reserves the right to request an additional visit at OPM Headquarters be added to any contract -related travel to Washington DC, to the extent such visit is reasonable and practical. If OPM requests an additional OPM Headquarters visit be added to any Washington DC trip, that visit shall not replace any of the four (4) on-site meetings with OPM budgeted per year.
12.2 Travel Related to Service Failures
The Government shall not be responsible for the expense of any travel required by OPM in connection with service failures by the contractor; travel required for service failures will be at the contractor’s expense. Additionally, service failure related travel will not replace any of the four OPM Headquarters On-Site Meetings allowance noted in the section above.
13.0 GOVERNMENT FURNISHED PROPERTY (GFP)
OPM will provide office space and reasonable accommodation, including all necessary identification to ease building access and communications, to include badges, phones, and computers.
14.0 INCIDENT REPORTING
The contractor must report those incidents that the contractor believes could have significant adverse impact to enrollee satisfaction, or OPM constituencies.
· Incidents which do not constitute a breach or potential breach shall be reported to the CO and COR (by email) within two hours of the contractor becoming aware, including nights, holidays, and weekends.
· The contractor must provide a preliminary incident report within 24 hours.
· The contractor must report any breach or potential breach to OPM Cyber solutions and the CO within 30 minutes of becoming aware of the risk – regardless of the time, or day of the week.
· Thereafter, the contractor must monitor and track the incident and provide the CO and COR with updates, new information and corrective plan of action at least weekly until final resolution.
ALL breaches must be reported, even if it is believed the breach is limited, small, or insignificant.
15.0 SECURITY CLEARANCES AND BACKGROUND INVESTIGATION
As previously noted, a limited number of contractor (and subcontractor) employees will require background investigations and security clearances to perform their duties.
16.0 CONTRACTING OFFICER’S REPRESENTATIVE (COR)
The COR will be assigned upon the award of this task order. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure the contractor performs the technical requirements of the contract; perform inspections necessary in connection with contract performance; maintain written and oral communications with the contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, and specifications; monitor the contractor's performance and notify both the CO and the contractor of any deficiencies; coordinate availability of Government-furnished property; and provide site-entry of contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates, or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the contract.
File details come from the government source that posted it. Updated .