06 Amendment 2 - 16PBGC25R0056.pdf

Commercial Solicita on FAR Part 13 in Conjunc on with FAR Part 12 Solicita on #: 16PBGC25R0056

Combined Synopsis & Solicita on for Commercial Products or

Commercial Services

This is a combined synopsis/solicita on for commercial products or commercial services prepared in accordance with the format in Federal Acquisi on Regula on (FAR) subpart 12.6, as supplemented with addi onal informa on included in this no ce. This announcement cons tutes the only solicita on; proposals are being requested and a wri en solicita on will not be issued.

This is a request for proposal. The solicita on number is 16PBGC25R0056. The solicita on document and incorporated provisions and clauses are those in effect through Federal

Acquisi on Circular 2025-03.

The applicable NAICS code is 541511 with a size standard of $34 million. This solicita on is issued as a small business set-aside. All qualified small businesses may respond.

The price schedule, descrip on of work, period of performance, instruc ons, evalua on criteria, clauses, provisions, and due date are contained in the documents a ached to this announcement.

Contents

Sec on 1: SUPPLIES OR SERVICES AND PRICES/COSTS

Sec on 2: PERFORMANCE WORK STATEMENT

1. INTRODUCTION

2. BACKGROUND

3. SCOPE OF WORK & REQUIREMENTS

3.1 Actuarial Services, Actuarial Exper se, Actuarial Studies and PIMS Related Projects

3.2 Opera ons and Maintenance (O&M) to the Legacy PIMS Models

3.3 System Modifica ons to Legacy PIMS

3.4 Project Management - Planning, Scheduling, Tracking, Managing, Repor ng

4. SCHEDULE OF DELIVERABLES

5. PERFORMANCE REQUIREMENT SUMMARY

6. PERIOD OF PERFORMANCE

7. HOURS OF OPERATION

8. PLACE OF PERFORMANCE

Sec on 3: INSTRUCTIONS TO VENDORS

Sec on 4: EVALUATION FACTORS FOR AWARD

Sec on 1: SUPPLIES OR SERVICES AND PRICES/COSTS

1.1 Introduc on

The Government intends to award a firm-fixed priced (FFP) standalone C-type contract in accordance with the procedures of FAR parts 12 and 13.

The Contractor shall provide the required services, as defined in Sec on 2, of this Request for Proposal (RFP). The associated North American Industry Classifica on System (NAICS) code is 541511. See A achment 2 - Legacy PIMS Task Map & Labor Projec ons referenced in the performance work statement (PWS) for a list of tasks related to pricing.

1.2 Pricing Schedule

Legacy PIMS Actuarial & IT Support Services Base Year: September 1, 2025 – August 31, 2026

CLIN Description Qty Unit Unit Price Total Price

Operations & Maintenance Legacy ME-PIMS Models 12 Months

Operations & Maintenance Legacy SE-PIMS Models 12 Months

Projections Report Modeling Legacy ME-PIMS Model 12 Months

0004 ME & SE Technical Assistance Requests 3 EA

Optional

Projections Report Modeling Legacy SE-PIMS Model 12 Months

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Special Project Requests 1 EA

Optional

ME & SE Special Project Requests 1 EA

Total Price

See con nued pricing schedule below

Option Year 1: September 1, 2026 – August 31, 2027

CLIN Description Qty Unit Unit Price Total Price

Optional

Operations & Maintenance Legacy ME-PIMS Models 12 Months

Optional

Projections Report Modeling Legacy ME-PIMS Model 12 Months

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

Operations & Maintenance Legacy SE-PIMS Models 12 Months

Optional

Projections Report Modeling Legacy SE-PIMS Model 12 Months

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Special Project Requests 1 EA

Optional

See con nued pricing schedule below

Option Year 2: September 1, 2027 – August 31, 2028

CLIN Description Qty Unit Unit Price Total Price

Optional

Operations & Maintenance Legacy ME-PIMS Models 12 Months

Optional

Projections Report Modeling Legacy ME-PIMS Model 12 Months

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

Operations & Maintenance Legacy SE-PIMS Models 12 Months

Optional

Projections Report Modeling Legacy SE-PIMS Model 12 Months

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Technical Assistance Requests 3 EA

Optional

ME & SE Special Project Requests 1 EA

Optional

Sec on 2: PERFORMANCE WORK STATEMENT

LEGACY PIMS ACTUARIAL and IT SUPPORT SERVICES

1. INTRODUCTION

The Pension Benefit Guaranty Corpora on (PBGC) was established to develop and administer the pension plan insurance programs as provided in Title IV of the Employee Re rement Income Security Act

(ERISA) of 1974. PBGC’s primary mission is to encourage the con nua on and maintenance of voluntary private pension plans for the benefit of their par cipants, provide for the mely and uninterrupted payment of pension benefits to par cipants and beneficiaries under plans to which Title IV applies, and maintain PBGC insurance premiums at the lowest level consistent with carrying out its obliga ons under

Title IV.

ERISA established two insurance programs to be administered by PBGC. The single-employer (SE) program covers plans maintained by one employer, or by a group of employers, but not pursuant to a collec ve bargaining agreement. The mul employer (ME) program covers plans that are collec vely bargained and cover the employees of two or more unrelated employers. Each insurance program is operated and financed separately from the other, and assets from one cannot be used to support the other.

2. BACKGROUND

The Pension Insurance Modeling System (PIMS) is a tool developed by the Policy, Research and Analysis

Department (PRAD) to model the SE and ME pension plan universes. A key purpose of PIMS is to enable

PBGC to produce its annual Projec ons Report in order to sa sfy its statutory obliga on under ERISA

4008 to produce an “actuarial evalua on of the expected opera ons and status of [PBGC’s] funds” each year. The current SE PIMS and ME PIMS models in conjunc on are referred to as Legacy

PIMS. A newer PIMS model (“T-PIMS”) has recently been deployed into Produc on but is not currently being u lized as the PIMS System of Record. The scope of work for this contract only applies to the current Legacy PIMS. This scope of work also includes decommissioning of the Legacy SE PIMS during this contract’s overall Period of Performance.

Single-Employer (SE) PIMS

The single-employer program is the largest of the two programs, insuring about 19.4 million workers and re rees covered by about 23,000 plans as of September 30, 2024. SE PIMS is a stochas c (i.e., random) simula on model that PBGC uses to evaluate its exposure and likelihood of future claims and to quan fy the amount of risk facing the single-employer insurance program. SE PIMS portrays PBGC's future financial condi on as a func on of a variety of economic parameters. SE PIMS has over 60,000 lines of computer code wri en in the C++ programming language as well as a user-interface and post-processing that is wri en in c#. SE PIMS is the most complex system of Legacy PIMS. Addi onal informa on about

SE PIMS can be found in A achment 1 – Legacy PIMS Fact Sheet.

Mul employer (ME) PIMS

ME PIMS is a stochas c (i.e., random) simula on model that PBGC uses to evaluate its exposure and likelihood of future claims and to quan fy the amount of risk facing the mul employer insurance

Program. It is also used to sa sfy PBGC's statutory requirement under Sec on 4022 of ERISA to conduct quinquennial studies of the mul employer insurance program to determine the adequacy of mul employer premium rates and benefit guarantees.

ME PIMS was developed by PRAD during 2018 for versa lity flexibility. This model is developed in Excel.

The calcula ons are completed in Excel-based formulas, with Visual Basic for Applica ons (VBA) components to improve efficiency and reduce run- me. ME PIMS was designed to allow users to easily make changes to the model and to adapt to the Technical Assistance requests received from Capitol Hill.

ME PIMS relies on data from the Form 5500 database, primarily from the Schedules MB and H/I.

Projected benefit payment cash flows for plans are developed in part using other suppor ng spreadsheets that calibrate to the Current Liabili es and Current Liability Normal Cost with sample census distribu ons. Addi onal informa on about ME PIMS can be found in A achment 1 – Legacy PIMS

Fact Sheet.

PIMS Opera ons

The contractor shall support PIMS through the architecture for the produc on environment. The SE PIMS produc on environment is comprised of 11 cloud servers under Microso Azure, running on Windows

Server 2022 Datacenter. While one of the server acts as APPS server, other 10 servers are used as drones. These are connected to an MS SQL Server and exposed to the user through their individual

Windows 11 Desktop. The Development and QA environments are comprised of 53 cloud servers under

MS Azure, running on Windows Server 2022 Datacenter, with a MS SQL server on the back end. This drone farm is exposed to the user via Windows 11 VDI desktops. From a user desktop within PRAD, the user can perform the following tasks:

1. View/edit data

2. Submit jobs

3. Review progress of jobs

4. View/Print results

5. Compare job results/se ngs

6. Execute post-processing using SAS, a sta s cal analysis tool used by PRAD staff as a suppor ng tool and found outside the PIMS boundaries

Once a user opens the PIMS manager and submits a job, PIMS will update the queue database with a job request. The PIMS Agent service, which uses a service account and password, then polls all the pending jobs in the queue and assigns them to different CPUs. From there, the assigned drone server calls an execu on file to calculate the job. The database servers upload the dataset at the beginning of the job to send back to the drone server. From there, calcula ons done within PIMS produces output files and stores them in job-specific output directories. These output directories are in the applica on/file server.

Most of the code is wri en in C++. The codebase itself contains ac ve code as well as old code that, while is no longer in use, remains in the code base. SAS is used by PRAD as a sta s cal tool. For some

SAS programs, the output is automa cally converted into excel for addi onal graphs and reports for the end user.

3. SCOPE OF WORK & REQUIREMENTS

The Contractor shall manage and provide support in all areas below. Specifically, individual model and system change requests under PWS Sec ons 3.1 and 3.3 will be tracked and completed using a cke ng system. To track the progress under 3.4, PRAD will ini ate requests and the contractor will create a cket. For O&M work under 3.2, produc on ckets will be submi ed via Service Now, and technical changes will be submi ed into DevOps as a user story and tracked to comple on. Each specific cket will be classified to the applicable performance area (i.e. Opera ons and Maintenance, Projec ons Report, Technical Assistance, or Special Project). The contractor will process and close out ckets under an ini ally agreed-upon meframe with PRAD based on the scope, an cipated level of effort and tes ng, and risk of each individual cket.

Opera ons and Maintenance (O&M) for the Legacy PIMS Models The Contractor shall perform tasks associated with the opera on and maintenance of the system in the test and produc on environments for both the Legacy SE PIMS and ME PIMS. The requirements for the Opera ons and Maintenance of the Legacy SE-PIMS model are more significant than that of the Legacy ME-PIMS model. This includes, but is not limited to, providing support to users, performing system backups, performing system issue triage and fixes using patch and defect management methods, so ware maintenance, and disposal of system. On-call support shall be required to resolve cri cal and urgent system issues determined by the agency. The Legacy SE PIMS system is also required to be decommissioned a er the new official agency System of Record becomes opera onal. The decommissioning ac vi es of the Legacy SE PIMS system are incorporated into this requirement.

The ME-PIMS model is built within Microso Excel files and therefore does not u lize separate dedicated system environments (e.g. Development, Test, Produc on). As a result, the requirements for the Opera ons and Maintenance of the ME-PIMS model are highly simplified and consist of user support related to troubleshoo ng issues and bugs within the ME-PIMS Excel files.

Projec ons Report Modeling The Contractor shall support SE Legacy PIMS and/or ME-PIMS to include wri ng code to make updates to the model or system, including adjustments to reflect new pension rules and regula ons, for purposes of producing PBGC’s Annual Projec ons Report1. This includes the required programming setup and support for the models used to produce the results published in the report. The final produc on of the report and the development of the data and assump ons used in the model runs which support the report’s findings are not included within the scope of this contract.

Technical Assistance (TA) Requests The Contractor shall provide PIMS modeling support and other ad hoc analy cal support, as necessary, to address the requirements of a request to PBGC for Technical Assistance from Congress, another Federal Agency, or an external organiza on. A single Technical Assistance request to PBGC may require the Contractor to complete mul ple new programming requirements and/or produce mul ple PIMS runs in order to develop a response. Fulfillment of a single Technical Assistance request requires the Contractor to provide all the modeling and analysis necessary to enable PBGC to fully respond to the en re request made to PBGC, with the excep on of any tasks for which there are data and/or tools necessary to complete the request that are not made available to the Contractor (e.g. sensi ve data;

1 Copies of historical PBGC Projec ons Reports can be found here: h ps://www.pbgc.gov/about/projec ons-report another PBGC department’s system). The Contractor shall perform all required quality reviews and documenta on included in PWS Sec ons 3.3 and 3.4.

Special Project (SP) Requests The Contractor shall conduct analysis on PRAD research projects, analysis of PRAD assump ons, or other special projects as requested by PBGC management. These projects are independent from requests for Technical Assistance and are longer-term in nature. An example includes a project to perform the data and actuarial analysis to complete an experience study for a PIMS assump on. The Contractor shall perform all required quality reviews and documenta on included in PWS Sec ons 3.3 and 3.4.

Requirements The contractor shall ensure compliance with all applicable federal regula ons, PBGC policies, processes, and procedures along with all direc ves and clauses in the performance of this contract. The requirements hereunder will be directed to the contractor as work assignment(s). Each assignment is categorized by type which then incorporates tasks related to O&M, projec ons modeling, TA, and SP requests. Addi onal informa on about the tasks specifically related to these requirement types can be found in A achment 2 – Legacy PIMS Task Map and Labor Projec ons.

3.1 Actuarial Services, Actuarial Exper se, Actuarial Studies and PIMS Related Projects The Contractor shall provide support for actuarial services, exper se, studies and other Legacy PIMS related projects. Services may include but are not limited to:

1) Annual actuarial evalua ons of PBGC's expected opera ons and financial status required under Sec on 4008 of ERISA. This includes all PIMS related modeling support required to develop PBGC’s annual Projec ons Report, as well as performing the “transcrip on process” to document all numbers published in the Projec ons Report to the underlying source (including but not limited to PIMS output).

2) Analyses of legisla ve, regulatory, and/or policy proposals to determine the impact on PBGC's financial posi on, projected PBGC cash flows, and/or the impact to the universe of plans insured by PBGC. This includes all PIMS-related modeling support.

3) Other ad hoc analysis to support PRAD research projects, analysis of PRAD assump ons, or other special projects as requested by PBGC management. This may include PIMS-related modeling support or other ad hoc analy cal analysis.

4) Develop Scope statements for system change requirements to support the produc on of the annual Projec ons Report.

3.2 Opera ons and Maintenance (O&M) to the Legacy PIMS Models In order to maintain the PIMS applica on in produc on and provide user support, the Contractor shall do the following to meet the customer's needs, organiza on's goals, and objec ves.

1) Contact users and provide technical support to ensure issues are resolved mely. Effec vely communicate with the users to provide the status of the open issues.

2) Conduct analysis of problems reported by users and recommend func onal and/or technical improvements, including the addi on of business and technical features to exis ng so ware. Provide alterna ve solu ons to improve the related processes and assist in exploring possibili es of using new features, func ons, and modules

3) Par cipate in root cause analysis in order to resolve produc on and user support issues effec vely.

4) Effec vely respond to ques ons about the system outages and errors. Resolve technical issues with Informa on Technology Infrastructure Opera ons Department (ITIOD), produc on SQL Database Administrators (DBAs), network support, other PBGC teams, and other systems.

5) Provide support to ITIOD to resolve applica on produc on issues.

6) Support system administra on du es as needed.

7) Support applica on and system audits from external and internal auditors.

8) Par cipate in corporate-wide IT ini a ves such as System Security Plan (SSP) updates and assist with PIMS System Assessment and Accredita on (SA&A) process leading to the a ainment of an Authority to Operate for ME PIMS and SE PIMS.

9) Provide technical support to PBGC as needed. Examples include, but are not limited to, tes ng and migra on of applica ons to future versions of so ware, database and opera ng systems on servers.

10) Re re applica ons. The Contractor may propose processes, and methods for re ring and archiving applica ons, as long as they do not conflict with the current PBGC guidelines for decommissioning systems and are approved by the COR and ITIOD.

11) Plan and par cipate in Disaster Recovery (DR) tes ng for the PIMS applica ons; develop DR tes ng scenarios; work with users and DR team to execute DR tests and document results if requested.

12) Support ac vi es for transi oning applica ons from/to other teams.

13) Support other PBGC teams responding to ques ons related to PIMS and/or related applica ons.

14) Provide other produc on support as needed, such as troubleshoo ng, debugging, iden fying problems/errors, making correc ons and improving efficiencies of PIMS and implemen ng changes in laws, policies and regula ons as they occur.

15) Ensure compliance with the PBGC infrastructure changes and ITIOD roadmap and infrastructure requirements.

16) Support the IT and Business Program Managers in conduc ng the annual opera onal analysis.

17) Decommissioning: Upon request of the COR, the contractor shall take all steps required to decommission the system and/or components. This includes archiving code and documenta on, coordina ng removal/uninstall of code and components from all IT environments and ensuring data back-up and archiving as well as working with PIMS Transforma on Contractor related to any data migra on for the transi on to the new PIMS system.

18) Support for:

I. Giving ongoing expert advice in the opera ons and capabili es to users on all areas of the PIMS and related systems

II. Maintaining a "problem log" of reported PIMS problems. The "problem log" is an up-to-date list of PIMS system problems which have been reported to the Contractor either by applica on users or by the Contractor's own personnel.

III. Determining the scope and level of effort of proposed modifica on or correc ons to the exis ng

PIMS system.

IV. Making correc ons to the PIMS system as requested and approved by the Subject Ma er Expert (SME) and the COR according to an agreed upon schedule.

V. Providing correc ons to documenta on according to an agreed upon schedule.

VI. Providing subject ma er exper se in the current workings of PIMS and current PIMS technology to IT groups and PIMS Transforma on team including working with PIMS transforma on contractor.

3.3 System Modifica ons to Legacy PIMS

Changes are generally requested to improve so ware in response to PBGC business processes, user interface, technology advancements or changes, and industry mandates. To support the system modifica on efforts, the Contractor shall:

1) Perform and complete project ini a on, planning, research, analysis, design, development, and tes ng and implement any approved system modifica on and requirements to the exis ng applica on in compliance with the IT processes including Informa on Security Risk Management Framework and Informa on Technology Solu ons Life Cycle Management (ITSLCM) Framework

2) Schedule and coordinate the releases with the integrated project/program team and deliver the releases on me.

3) Deploy high quality so ware releases in produc on and minimize down me in produc on due to quality issues.

4) Leading the effort to analyze, priori ze and conduct mee ngs to determine system modifica ons.

5) Ensure the design is interoperable with other integrated systems and meets Enterprise Architecture (EA) guidelines and other PBGC standards.

6) Coordinate extensively with all stakeholders such as OIT, PRAD, Security and Privacy teams, and other applicable divisions and systems within PBGC and the Federal Government.

7) Deploy all so ware system modifica ons through releases according to established PBGC So ware Configura on Management Procedures and Change and Release Management Policy, Processes and Procedures and PBGC security policies to ensure the agency standards are accurately captured and incorporated into the releases.

8) Conduct appropriate system level tests (e.g., unit tes ng, parallel tes ng, regression tes ng, integra on tes ng, performance tes ng, load tes ng, func onality tes ng) to modify the quality of so ware releases. The Contractor may use automated tes ng tools.

9) Support and assist applica on users in User Acceptance Tes ng (UAT) of the applica on, including, but not limited to, (1) the prepara on of test plans, test cases/scripts and test results, (2) the use of automated tes ng tools, and (3) the development and maintenance of opera on system documenta on and procedures.

10) Effec vely coordinate the no fica on of the deployment of releases to users, stakeholders, Service Desk, COR, and other impacted par es in a mely manner to provide impacted par es me to prepare for the release.

11) Providing system modifica ons that include the design, programming, tes ng and implementa on of major upgrades or significant new modeling capabili es based on user requirements developed by

PRAD.

12) Propose system modifica ons and correc ons for both Models

13) Implement system modifica ons or correc ons to both Models as approved by PRAD management and in accordance with an agreed upon implementa on schedule.

14) Produce a System Change Request (SCR) document summarizing the following:

o A detailed descrip on of the requirements for the enhancements o Dates documen ng the following

Date of request Date of comple on of development Date of comple on of review o Documenta on of who completed the enhancement and who reviewed it o Summary of the end-to-end tes ng conducted o Limita ons of the enhancement o Quan ta ve summary of changes in the results of the model from the previous version.

This includes commentary about any notable differences and reasonability checks are conducted.

o Other important commentary about the enhancement, tes ng, and analysis o Other documenta on about the enhancement, as requested by PBGC

15) Provide on-call support as needed during periods of Technical Assistance requests.

3.4 Project Management - Planning, Scheduling, Tracking, Managing, Repor ng The contractor shall work directly with the COR, BISD Project and Program Managers, PRAD Project and Program Managers and PRAD customers to proactively plan and manage all work performed under this contract. The contractor shall:

1) Conduct scope management to ensure project scope is baselined and changes to scope are managed through the project lifecycle. This includes the ini al and preliminary “Scope Statements” to include requirements for system and model changes to support annual Projec ons Reports. Establish and follow procedures for release management and change control, including an impact assessment.

2) Follow the Change Management Process outlined in A achment 3 – Team Workflow and Separa on of Du es Chart. This process and any changes required to be implemented during the performance period shall be implemented by the contractor at the discre on of the agency.

3) Conduct schedule management to include establishing a resource-loaded and baselined schedule in PBGC’s approved project management system (currently Microso Project Online, a.k.a. P3M)

4) Develop project schedules and project baselines for iden fied projects to include releases or any ac vity where resources are deployed to make changes to or support applica ons in this Task Order.

Follow the ITSLCM framework in developing the schedule and ensure the schedule includes the deliverables, milestones, planned dura ons for each task, project start and end dates, resources, work breakdown structure of ac vi es, and other specific informa on needed to track the projects.

The Contractor will work with the subject ma er experts and other stakeholders in elici ng requirements.

5) Maintain rela onships and partnerships with all integrated system leadership for systems both internal and external to the project IT applica ons/systems.

6) Prepare project status reports as defined by the Federal IT Project Manager along with understanding agency priori es and aligning their team’s ac ons to meet changing priori es.

3.4.1 Project Management - Issue and Risk Management

PBGC places great importance on actively performing risk management by identifying, developing and using mitigation strategies while also effectively escalating risks as a key component of project management. The Contractor shall:

1) Include risk management strategies, based on PBGC Risk Management Policy. Addi onal informa on can be found in A achment 4 - IT Risk Management Strategy and Process.

2) Iden fy and track risks that may impact the project and PBGC systems and iden fy mi ga on strategies in BISD’s system of record (currently P3M).

3) Iden fy and track issues and work to resolve and ensure system opera ons and releases remain on-schedule.

3.4.2 Project Management - Status Repor ng

Regular and ad hoc reporting is required to ensure all PBGC project stakeholders are aware of project and system status. Tools shall be kept up to date to enable status reporting and status views at any time by the PBGC team. The Contractor shall provide regular status and ad hoc reporting to the COR, IPT, and executive sponsors for all contractor activities.

3.4.3 Project Management - Integrated Project Team (IPT)

PBGC uses integrated project teams (IPTs) to provide governance and guidance for IT systems and projects. These IPTs consist of members from various PBGC stakeholder groups including the Information System Owner, Information System Security Manager, IT Infrastructure, Enterprise Architecture, system operations and development team, IT project manager and many others. All system operations and changes shall be guided by an IPT.

The contractor shall:

1) Coordinate and facilitate IPT governance bodies to enable decisions on system changes and to provide a venue for dissemination of system information.

2) Provide status on system operations and changes.

3.4.4 Project Management - Mee ng Par cipa on

Throughout the management and support of PBGC systems and projects, meetings will be conducted to gather information, make decisions, disseminate information, etc. Conducting efficient meetings and maintaining accurate minutes of those meetings is essential to the success of PBGC projects. The Contractor shall:

1) Develop agendas and circulate those agendas ahead of any mee ngs organized by the contractor.

2) Develop mee ng materials when the contractor is presen ng.

3) Facilitate mee ngs that allow for in-person and/or remote par cipa on via teleconference, Skype and/or other remote par cipa on tools.

4) Record and provide minutes of all mee ngs conducted or a ended as part of this contract work and deliver those minutes for par cipant review and comment.

5) Par cipate in mee ngs as required for other PBGC efforts that may impact or be impacted by this contract.

3.4.5 Project Management - System Documenta on and Documenta on Maintenance

PBGC system documenta on includes any documenta on generated as part of a maintenance or system modifica on effort, technical documenta on, models, opera onal manuals, mee ng agendas/minutes and any documenta on used or created as part of the performance of PBGC system support. All documenta on shall be maintained and kept current during the maintenance period by the

Contractor using PBGC’s SharePoint sites or a PBGC approved tool.

Updated documents must be reviewed and approved by BISD COR in coordina on with BISD Project and Program Managers, and PRAD's Program Manager and SMEs. Upon request by the COR, the

Contractor shall provide training to users on PIMS and/or related systems.

The Contractor shall:

1) Develop or update PBGC documenta on, including manuals (e.g., opera ons, system administra on, system maintenance, user and training) and plans (e.g. system integra on and site implementa on). Documenta on shall follow the latest approved standards at the me of the execu on effort and delivery of the system. The Contractor shall develop documenta on and/or update exis ng IT Solu ons Life Cycle Management (ITSLCM) documents that are required as a result. Addi onal informa on about the ITSLCM can be found in A achment 5 – ITSLCM Framework.

2) Comply with PBGC standards and guidelines for all documenta on, update all system documents when changes occur in the applica on or process, and maintain and revise PBGC system and business process documenta on in accordance with the processes determined by the agency.

3.4.6 Project Management - Transi on Support

The objec ve of transi on support is to ensure con nuity of services in the areas supported by the incumbent while the incoming contractor learns how to support these services. The Contractor shall support transi on from the outgoing incumbent, as well as transi on to PBGC or a new contractor, if required.

Transi on In - Upon award, the Contractor shall begin an effec ve transi on of work from the incumbent. The contractor shall assume full responsibility for an orderly phase-in of opera ons that minimize the impact to PBGC. The contractor shall ensure that transi on ac vi es are transparent to the current opera ons and do not disrupt or adversely affect the current day to day opera ons. The transi on in period shall not exceed 60 days a er contract award. The plan should address all work to be assumed from the incumbent and the tasks required to accomplish successfully taking on the scope of work including onboarding, technical access, transfer of documenta on, transfer of all knowledge and any other ac vi es required.

Transi on Out - The Contractor shall accommodate transi on for at least two (2) months of its func ons to PBGC or a new contractor upon re-compete of this contract. The Contractor shall deliver all documenta on, informa on for the opera on and maintenance of the PBGC systems, and provide communica ons, training, and support to PBGC to ensure a successful transi on of PBGC to another vendor. The Contractor shall develop a Transi on Strategy detailing the steps necessary to transi on opera ons and maintenance to PBGC, another PBGC selected vendor and any ac ve documenta on or ac vi es for releases. At comple on of the contract, all licenses revert to PBGC. All documenta on shall be maintained and kept current during the transi on period by the Contractor.

4. SCHEDULE OF DELIVERABLES

The table below includes all deliverables required to fulfill the requirements outlined in sec on 3 above.

Specifically, the required ming of all model and system changes under requirements sec on 3.1 and 3.3 in order to support PRAD in the mely comple on of the annual PBGC Projec ons Report as well as ad hoc modeling requests such as requests for Technical Assistance from external stakeholder. In addi on, individual model and system change requests will be tracked and completed using a cke ng system.

PRAD will ini ate requests and the contractor will create a cket to track the progress under requirements sec on 3.4. The contractor will process and close out ckets under an ini ally agreed-upon meframe with PRAD based on the scope, an cipated level of effort and tes ng, and risk of each individual cket.

Task # Sec on(s) Deliverable Descrip on Deadline

1 3.1, 3.3, 3.4

Dra or revise the ini al “Scope Statement” to include the requirements for system and model changes to support the annual Projec ons Report completed during the current performance year.

Within first 30 calendar days of the beginning of each performance year

2 3.1, 3.3, 3.4

Provide a Detailed Project Schedule to complete all requirements of the ini al Scope Statement by

January 31st.

Due 15 days a er requirements are approved

3 3.1, 3.3, 3.4

Begin the preliminary implementa on of all requirements included in the ini al Scope

Statement. Implementa on includes delivery of all requirements in the Scope Statement, and all applicable System Change Request documenta on.

Due by January 31st of each calendar year

4 3.1, 3.3

Finalize all system and model changes and complete PIMS-related set-up and support, to include applicable PIMS sub-processes, to enable

PRAD to produce all PIMS runs required to produce the annual Projec ons Report. This includes any cri cal requirements iden fied a er the ini al Scope Statement was developed.

This includes all applicable System Change

Request (SCR) documenta on.

Due by April 15th of each calendar year, or later as directed by the

COR

5 3.1, 3.3, 3.4

Dra a preliminary Scope Statement to include requirements for system and model changes to support the Annual Projec ons Report completed during the next performance year.

Due by April 15th of each calendar year

Task # Sec on(s) Deliverable Descrip on Deadline

6 3.1, 3.3, 3.4

Provide a detailed Project Schedule to complete next year’s preliminary Scope Statement by the end of the current performance year.

Due by April 30th of each calendar year

7 3.1, 3.3

Provide a final, approved version of the system and model to be used for the annual Projec ons

Report into Produc on.

Due by May 31st of each calendar year, or later as directed by the

COR

8 3.1

Complete the “transcrip on process” to document all numbers published in the

Projec ons Report to the underlying source

(including but not limited to PIMS output).

TBD based on Projec ons Report ming, with target date of June

30th of each calendar year

9 3.1, 3.3

Complete all system and model changes included in the April 30th Project Schedule and preliminary

Scope Statement. This includes all applicable

System Change Request documenta on.

Due by the end of the performance year

10 3.2 Problem log and document all known system issues and provide a plan to resolve them.

End of each Month

11 3.4.1, 3.4.2

Prepare and Submit a Monthly Program

Management Report (PMR) deck which includes at a minimum an outage, staffing, release schedule, risk register, system issues, and compliance to new or changing IT requirements.

As required by the COR

12 3.4.2

Provide monthly Status Reports to include deliverable status, milestones, planned ac vi es, completed ac vi es.

Monthly

13 3.4.2, 3.4.3 Provide ad hoc repor ng to COR, IPT, execu ve sponsors for all contractor ac vi es.

Monthly

14 3.4.4 Provide mee ng agendas and mee ng minutes as directed by the COR.

As required by the COR

15 3.4.5

Develop and update PBGC documenta on in accordance with the latest approved standards by following the IT Life Cycle Solu ons Management

Framework (ITLCSM) as determined by the IT

Project Manager/COR and in accordance with all

PBGC clauses.

As required for releases

16 3.2 Develop and execute a Legacy SE PIMS

Decommission Plan as directed by the COR.

As required by the COR

Task # Sec on(s) Deliverable Descrip on Deadline

17 3.4.6

Develop and implement a “Transi on in Plan” to ensure a seamless transi on between contractor personal if necessary as determined by the agency.

Required 30 days a er award

18 3.4.6

Develop and implement a “Transi on out Plan” to ensure a seamless transi on between contractor personal if necessary as determined by the agency.

Required 30 days prior to the end of the final performance period

5. PERFORMANCE REQUIREMENT SUMMARY

The government shall evaluate the contractor's performance under this contract in accordance with the quality standards defined in the Quality Assurance Surveillance Plan below. The Contractor shall maintain the quality assurance plan (QASP) to ensure performance in accordance with the performance standards awarded under this contract.

Quality Assurance Surveillance Plan Item

Performance

Standard Required Performance

Acceptable Quality

Level (AQL)

Surveillance

Method Used

1 Timeliness All deliverables will be provided by the deadline referenced in Sec on 3.

All deliverables will be provided by their deadline unless revised by the COR

Email monitoring of receipt date. 100% COR inspec on/ acceptance of each final deliverable

2 Quality

All Scope statements include the requirements for system and model changes to support the Annual

Projec ons Report

No more than 2 revisions requested by the

COR

Email monitoring of receipt date. 100% COR inspec on/ acceptance of each final deliverable

3 Quality

Provide a Project Schedule that incorporates the meline/milestones to complete all the requirements of the ini al Scope statement

No more than 2 revisions requested by the

COR

Email monitoring of receipt date. 100% COR inspec on/ acceptance of each final deliverable

Quality, Timeliness, &

Accuracy

All system and model changes are completed by the deadline outlined in sec on 3 and produce the outcomes required to build the Annual Projec ons

Report

All system issues and model changes resolved a er 1 request by the COR

Email monitoring of receipt date. 100% COR inspec on/ acceptance of each final deliverable

Item

Performance

Standard Required Performance

Acceptable Quality

Level (AQL)

Surveillance

Method Used

5 Accuracy

All Required documents are in accordance with ITSLCM (e.g., meeting agendas/materials/minutes, PMR, project and system documentation).

100% of required documents meet

ITSLCM standards

Email monitoring of receipt date. 100% COR inspec on/ acceptance of each final deliverable

6 Timeliness

Provide a response to On-Call Support within 2 hours of ini al request by the agency and resolve or escalate issue within 2 hours of ini al request

No more than 2 delayed on-call responses per contract year.

Email monitoring of receipt date. 100% COR inspec on/ acceptance of each final deliverable

6. PERIOD OF PERFORMANCE

Base Period – September 1, 2025 – August 31, 2026.

Op on Period 1 – September 1, 2026 – August 31, 2027

Op on Period 2 – September 1, 2027 – August 31, 2028

7. HOURS OF OPERATION

Primary core hours that the contractor shall be available are Monday-Friday 8:00 AM-5:00 PM EST. Hours of availability may be altered with prior approval by the COR. Opera ons support personnel should be available during Core Hours and for on call TA and SP requests. The contractor shall follow FAR and PBGC policy regarding holidays and inclement weather in coordina on with the COR.

8. GOVERNMENT FURNISHED PROPERTY & INFORMATION

The Government shall provide all necessary informa on, data and documents to the Contractor for work required under this contract. The Contractor shall use Government furnished informa on, data and documents only for the performance of work under this contract and shall be responsible for returning all Government furnished informa on, data and documents to the Government at the end of the performance period. The Contractor shall not release Government furnished informa on, data and documents to outside par es without the prior and explicit consent of the Contrac ng Officer. The Contractor shall possess the capability to store and safeguard from unauthorized disclosure of the Government Furnished Informa on and Data required for this effort. The Government shall provide the equipment necessary to meet this requirement. When required, PBGC will authorize GFE to operate from an alternate site loca on.

8. PLACE OF PERFORMANCE

Contractor personnel may perform this work remotely or in-person at PBGC headquarters, at their discre on. The PBGC address is 445 12th Street SW, Washington, DC 20024. In-person work is con ngent upon the availability of desk space and equipment. The Government will not pay for travel between telework loca ons and PBGC headquarters, for parking, or for local travel as defined by OPM locality pay

(see h ps://www.opm.gov/policy-data-oversight/payleave/salaries-wages/2020/locality-pay-area-defini ons/#DC-MD-VA-WV-PA). The Contractor must maintain EST opera ng hours and is expected to be available during 8:30 am – 5:00pm EST and all work shall be performed within the United States.

Sec on 3: INSTRUCTIONS TO CONTRACTORS

3.1 Commitment of the Government

This solicitation does not commit the Government to award a purchase order.

3.2 Communica ons and Ques ons

All communica ons concerning this RFP, shall be made by email to Frank Argenziano (Argenziano.Frank@pbgc.gov) and Tre Brummell (Brummell.Joseph@pbgc.gov). All ques ons, in response to this solicita on shall be in wri ng and received by the Government on or before May 15th, 2025 at 12:00 PM Eastern Time. Ques ons shall iden fy the applicable sec on, page number, and paragraph. The Government will provide a list of all ques ons received with the Government responses in the form of an amendment to the RFP. The Government may or may not consider ques ons received a er this date.

3.3 Proposal Submission Due Date and Time

Proposals shall include three (3) separate documents that address the requirements. The contractor shall provide – (1) a cover le er, (2) an Experience & Past Performance proposal (Volume 1), and (3) a Price Proposal (Volume 2) in Adobe PDF format by email to Frank Argenziano (Argenziano.Frank@pbgc.gov) and Tre Brummell (Brummell.Joseph@pbgc.gov) by the RFP submission deadline.

3.4 Proposal Prepara on Instruc ons

a. All proposals must conform to these instruc ons.

b. Proposals shall be separated into three documents: a cover le er, Volume 1 – Experience and Past Performance, Volume 2 – Price Proposal. Volume 1 shall be completed in Adobe PDF format and Volume 2 shall be completed in Microso Excel format. Both volumes shall be submi ed by email to the contacts listed in the preceding sec on.

c. Each document shall reference the solicita on number.

d. Cover Le er. The cover le er shall address, at a minimum, the following informa on:

i. Business name and address.

ii. Business size for the NAICS code applicable to this work.

iii. Unique En ty Iden fica on (UEI).

iv. Any known organiza onal conflict of interest (OCI) or appearance of OCI that would result from award of this contract to the business submi ng the proposal.

v. Any assump ons about the work that the contractor relied upon in developing its proposal.

vi. A statement of agreement to all terms, condi ons, and provisions included in the solicita on including compliance with Sec on 508 of the Rehabilita on Act.

vii. Corporate point(s) of contact, including email address(es) and phone number(s).

e. Volume 1 – Corporate Experience & Past Performance Proposal

1. The contractor shall provide up to three (3) instances of corporate experience performed within the past seven (7) years which indicates work the same or similar to the work described in the PWS. The contractor must provide evidence that the corporate experience is substan ally similar in size, scope and complexity to that required by the solicita on and NAICS Category 541 - Professional, Scien fic, and Technical Services.

The contractor shall include a descrip on for each corporate experience instance referenced, to include the following:

The date The dollar value Evidence of similar size, scope and complexity to this requirement

2. The contractor shall provide up to three (3) past performance references related to their corporate experience which includes the name, email, phone number, posi on tle, and corpora on or agency name. The contractor shall also provide contract numbers for the associated past performance appraisals in CPARS.

3. This volume shall not exceed three (3) typed pages using a minimum of 10-point font. The page count does not include the cover page.

f. Volume 2 – Price Proposal. The contractor shall complete A achment 7 – Pricing Schedule Table in Excel format.

Sec on 4: EVALUATION FACTORS FOR AWARD

4.1 Evalua on of Proposals

PBGC will evaluate proposals in three (3) phases as described below. Any proposals deemed to be not among the most compe ve during any phase of the evalua on will be ineligible for award and removed from further considera on.

a. Phase 1 – Proposal Acceptability.

1. Ensure proposals are in accordance with the terms, condi ons, and instruc ons of this

RFP, and that the business submi ng the proposal is registered in the System for Award

Management and otherwise eligible to receive award. Any proposal deemed ineligible due to substan ve flaws in the proposal or contractor’s status will be removed from further considera on for award.

b. Phase 2 – Price.

1. A price analysis shall be performed where proposal prices will be determined as fair and reasonable or unreasonable. Any proposal containing an excessively high price will be deemed ineligible for award and removed from further considera on. In addi on, PBGC reserves the right to review prices and determine whether they are too low and reflect a lack of technical understanding, in which case the quota on may be rejected.

c. Phase 3 – Corporate Experience, Past Performance and Price.

1. Corporate experience shall be evaluated based on recency, relevancy and quan ty. PBGC will also consider price under this phase.

i. A ra ng will be ascribed to each instance based on recency using these defini ons.

An overall recency ra ng with the same defini on will be assigned for the proposal’s corporate experience.

Recent – Effort is ac ve and ongoing or has a comple on date within the past 3 years.

Somewhat recent – Effort has a comple on date of greater than 3 years but no more than 7 years.

Not Recent – Effort has a comple on date of greater than 7 years.

ii. A ra ng will be ascribed to each instance based on relevancy using these defini ons. An overall relevancy ra ng with the same defini on will be assigned for the proposal’s corporate experience.

Relevant – Effort involves a similar scope and requirements that match this solicita on.

Somewhat relevant – Effort involves some of the scope and requirements that match this solicita on.

Not relevant - Effort involves li le or none of the scope and requirements that match this solicita on

iii. The number of corporate experiences will be totaled (0-3).

2. PBGC will evaluate the past performance of corporate experience instances that are determined to be at least somewhat recent and somewhat relevant as described in the ra ng defini ons. An individual confidence ra ng will then be ascribed to each of these

Past performance references using the same overall confidence ra ng metrics.

PBGC will make a good-faith effort to reach past-performance points of contact. PBGC will not penalize a contractor for lack of past performance references or because its points of contact are non-responsive; however, all else being equal, a contractor with references that support a substan al or sa sfactory confidence past performance record will be deemed more compe ve than a contractor that does not have any past performance record available to evaluate.

3. An overall confidence ra ng will be assigned separately to each proposal’s Corporate

Experience and Past Performance.

Substan al Confidence - A ra ng of substan al confidence shall be assigned based on the agency’s expecta on that the contractor will provide a high quality of service that exceeds the performance standards set in this requirement.

Sa sfactory confidence - A corporate experience ra ng of sa sfactory confidence shall be assigned based on the agency’s expecta on that the contractor will provide a sa sfactory quality of service that meets the performance standards set in this requirement.

Low Confidence – A corporate experience ra ng of low confidence shall be assigned based on the agency’s expecta on that the contractor will provide a low quality of service that does not meet the performance standards set in this requirement.

Undefined – A ra ng of undefined shall be assigned to past performance references based on the agency’s inability to contact the offerors references or there is no recent or relevant performance record available.

4. Any proposals determined not among the most compe ve based on an assessment of

Corporate Experience, Past Performance and Price will be deemed ineligible for award and removed from further considera on. PBGC will then select the most advantageous proposal among those remaining.

d. Phase 4 Overall Assessment.

1. PBGC will…