06_RFQ - Legacy PIMS Comprizon.pdf

SOLICITATION, OFFER AND AWARD 1. THIS CONTRACT IS A RATED

ORDER UNDER DPAS (15 CFR 7900)

RATING

PAGE OF

PAGES

2. CONTRACT NUMBER 3. SOLICITATION NUMBER 4. TYPE OF SOLICITATION 5. DATE ISSUED 6. REQUISITION/PURCHASE NUMBER

16PBGC20Q0036 SEALED BID (IFB)

NEGOTIATED (RFP)

RQ-32-20-000018

RQ-32-20-000018

7. ISSUED BY CODE PD 8. ADDRESS OFFER TO (If other than Item 7)

PENSION BENEFIT GUARANTY CORP

PROCUREMENT DEPARTMENT

1200 K ST NW

WASHINGTON DC 20005-4026

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

SOLICITATION

9. Sealed offers in original and 1 copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if handcarried, in the depository located in until 10:00

AM ET

local time JUN 09, (Hour) (Date)

CAUTION - LATE Submissions, Modifications, and Withdrawls: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

B. TELEPHONE (NO COLLECT CALLS)10. FOR

INFORMATION CALL

A. NAME

Esan Sumner AREA CODE NUMBER

EXTENSION

C. E-MAIL ADDRESS

11. TABLE OF CONTENTS

(X) SEC. DESCRIPTION PAGES(S) (X) SEC. DESCRIPTION PAGE(S)

PART 1 - THE SCHEDULE PART II - CONTRACT CLAUSES

X A SOLICITATION/CONTRACT FORM 1 - 1 I CONTRACT CLAUSES -

X B SUPPLIES OR SERVICES AND PRICES/COSTS 2 - 2 PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

C DESCRIPTION/SPECS./WORK STATEMENT - J LIST OF ATTACHMENTS -

D PACKAGING AND MARKING - PART IV - REPRESENTATIONS AND INSTRUCTIONS

E INSPECTION AND ACCEPTANCE - K REPRESENTATIONS, CERTIFICATIONS AND OTHER -

F DELIVERIES OR PERFORMANCE - STATEMENTS OF OFFERORS

G CONTRACT ADMINISTRATION DATA - L INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS -

H SPECIAL CONTRACT REQUIREMENTS - M EVALUATION FACTORS FOR AWARD -

OFFER (Must be fully completed by offeror) NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within calendar days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

13. DISCOUNT FOR PROMPT PAYMENT

(See Section I, Clause No. 52.232-8)

10 CALENDAR DAYS (%) 20 CALENDAR DAYS (%) 30 CALENDAR DAYS (%) CALENDAR DAYS (%)

14. ACKNOWLEDGMENT OF AMENDMENTS AMENDMENT NO. DATE AMENDMENT NO. DATE

(The offeror acknowledges receipt of amendments to the SOLICITATION for offerors and related documents numbered and dated):

CODE FACILITY 16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER

15A. NAME AND

ADDRESS OF

OFFEROR

(Type or print)

15B. TELEPHONE NUMBER 15C. CHECK IF REMITTANCE ADDRESS IS DIFFERENT

AREA CODE NUMBER

EXTENSION FROM ABOVE - ENTER SUCH ADDRESS IN SCHEDULE.

17. SIGNATURE 18. OFFER DATE

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED 20. AMOUNT 21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

10 U.S.C. 2304(c) 41 U.S.C. 3304(a) ( )

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

(4 copies unless otherwise specified)

ITEM

24. ADMINISTERED BY (If other than Item 7) 25. PAYMENT WILL BE MADE BY CODE

26. NAME OF CONTRACTING OFFICER(Type or print) 27. UNITED STATES OF AMERICA 28. AWARD DATE

(Signature of Contracting Officer)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is unusable

STANDARD FORM 33 (REV. 6/2014)

Prescribed by GSA - FAR (48 CFR) 53.214(c)

PAGE 1 OF 53 16PBGC20Q0036

SCHEDULE Continued

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

Invoicing Address:

SUBMIT INVOICES TO:

INVOICEMANAGER@PBGC.GOV

GENERAL ACCOUNTING BRANCH (GAB/PBGC)

1200 K ST NW WASHINGTON DC 20005-4026

The items below are used for PBGC internal funding purposes only. The official Contract Line Item Number (CLIN) schedule follows in Section B. The contractor shall invoice in accordance with the official CLIN schedule and IAW clauses PBGC 52.232-7000.

0001 The Contractor shall perform the services in accordance with the Statement of Work (SOW), as required in Section C - Description/ Specifications/ Work Statement of this award.

PR NUMBER: RQ-32-20-000018

DELIVERY DATE: 09/01/2020

SHIP TO:

SEE SCHEDULE

DC

FOB : Destination Period of Performance: 09/01/2020 to 08/31/2021

1.00 EA

Invoicing Address:

SUBMIT INVOICES TO:

INVOICEMANAGER@PBGC.GOV

GENERAL ACCOUNTING BRANCH (GAB/PBGC)

1200 K ST NW WASHINGTON DC 20005-4026

The items below are used for PBGC internal funding purposes only. The official Contract Line Item Number (CLIN) schedule follows in Section B. The contractor shall invoice in accordance with the official CLIN schedule and IAW clauses PBGC 52.232-7000.

0002 The Contractor shall perform the services in accordance with the Statement of Work (SOW), as required in Section C - Description/ Specifications/ Work Statement of this award.

PR NUMBER: RQ-32-20-000018

DELIVERY DATE: 09/01/2020

SHIP TO:

SEE SCHEDULE

DC

FOB : Destination Period of Performance: 09/01/2020 to 08/31/2021

1.00 EA

PAGE 2 OF 53 16PBGC20Q0036

Table of Contents

Combined Synopsis/Solicitation

52.204-7 SYSTEM FOR AWARD MANAGEMENT (OCT 2018)

52.212-1 INSTRUCTIONS TO OFFERORS--COMMERCIAL ITEMS (MAR 2020)

52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS--COMMERCIAL ITEMS (MAR 2020)

52.212-4 I CONTRACT TERMS AND CONDITIONS--COMMERCIAL ITEMS (OCT 2018)--ALTERNATE I (JAN 2017)

52.216-31 TIME-AND-MATERIALS/LABOR-HOUR PROPOSAL REQUIREMENTS -- COMMERCIAL ITEM ACQUISITION (FEB

2007)

52.224-1 PRIVACY ACT NOTIFICATION (APR 1984)

52.239-1 PRIVACY OR SECURITY SAFEGUARDS (AUG 1996)

52.242-15 STOP-WORK ORDER (AUG 1989)

52.246-25 LIMITATION OF LIABILITY--SERVICES (FEB 1997)

52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS--COMMERCIAL

ITEMS (MAR 2020)

52.217-8 OPTION TO EXTEND SERVICES (NOV 1999)

52.217-9 OPTION TO EXTEND THE TERM OF THE CONTRACT (MAR 2000)

52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

PBGC 52.201-7000 CONTRACTING OFFICER'S REPRESENTATIVE (JAN 2012)

PBGC 52.204-7000 RECORDS MANAGEMENT (SEP 2017)

PBGC 52.207-7000Contingency Telework (COVID-19) (MAR 2020)

PBGC 52.209-7001 ORGANIZATIONAL CONFLICTS OF INTEREST (AUG 2017)

PBGC 52.209-7002 HANDLING PBGC DATA (MAY 2017)

PBGC 52.232-7001SUBMISSION OF INVOICES (TIME AND MATERIAL AND LABOR-HOURS) (SEPT 2017)

PBGC 52.232-7006SUBMISSION OF INVOICES/VOUCHERS - IPP (OCT 2018)

PBGC 52.237-7000 KEY PERSONNEL (APR 2018)

PBGC 52.237-7002 FITNESS DETERMINATION (APR 2019)

PBGC 52.237-7004 TRAINING (MAR 2016)

PBGC 52.237-7005 INFORMATION SECURITY TRAINING (MAR 2020)

PBGC 52.237-7007 DISPLAY OF PBGC IDENTIFICATION BADGES (FEB 2013)

PBGC 52.239-7000 SECTION 508 ACCESSIBILITY STANDARDS (MAR 2020)

PBGC 52.239-7005 NON-CLOUD MANAGED SERVICES (APR 2016)

PBGC 52.239-7006INFORMATION TECHNOLOGY MANAGEMENT (AUG 2018)

PBGC 52.242-7000 POSTAWARD CONFERENCE (MAR 2016)

PBGC 52.246-7000 INSPECTION AND ACCEPTANCE OF DELIVERABLES (JAN 2012)

PBGC 52.247-7000 PACKAGING AND MARKING (JAN 2012)

PAGE 3 OF 53 16PBGC20Q0036

CLAUSES

Combined Synopsis/Solicitation

PAGE 4 OF 53 16PBGC20Q0036

Combined Synopsis/Solicitation Description:

(i) This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; quotes are being requested and a written solicitation will not be issued. The Government intends to award a Labor Hour (LH) contract under Simplified Acquisition Procedures (SAP) using FAR Part 13.

(ii) The solicitation reference number is 16PBGC20Q0036. This requirement is issued as a Request for Quotation (RFQ).

(iii) This RFQ and incorporated provisions and clauses are those in effect through Federal Acquisition Circular (FAC) 2005-63.

(iv) This solicitation is not set aside for small business. The associated North American Industry Classification System (NAICS) code is 541611 - Administrative Management and General Management Consulting Services.

(v) The Contract Line Item Numbers, Items, Quantities, and Units of Measure (including options) are listed in Attachment A Price Schedule. The anticipated date for contract award is September 1, 2020.

(vi) The description of requirements for the services. PBGC is seeking to obtain qualified, experienced, and highly competent contractor to provide professional services as set forth in Attachment B the Statement of Work (SOW).

(vii) PBGC anticipates a Base Period of 12-months commencing on date of award followed by four (4) 12-months Option Periods. Total of base period and all option periods shall not exceed 60 months:

- Base Period: September 1, 2020 through August 31, 2021

- Option Period 1: September 1, 2021 through August 31, 2022

- Option Period 2: September 1, 2022 through August 31, 2023

- Option Period 3: September 1, 2023 through August 31, 2024

- Option Period 4: September 1, 2024 through August 31, 2025

Dates and place of delivery are included in Attachment B the Statement of Work (SOW).

(viii) The provision at 52.212-1, Instructions to Offerors – Commercial Items (Mar 2020), applies to this acquisition. Please see Attachment C for more information.

Each Quoter shall submit pricing as a separate document that shall include the format identified in Attachment E.

(ix) The provision at 52.212-2, Evaluation – Commercial Items (Oct 2014), applies to this acquisition. Please see Attachment D for more information.

(x) FAR 52.212-3 Offeror Representations and Certifications—Commercial Items

PAGE 5 OF 53 16PBGC20Q0036

(Mar 2020), applies to this acquisition. The Quoter shall complete only paragraph (b) of this provision if the Quoter has completed the annual representations and certification electronically via the System for Award Management (SAM) website located at 26T26TUUhttps://www.sam.gov/portalUU26T26T.

If the Quoter has not completed the annual representations and certifications electronically, the Quoter shall complete only paragraphs (c) through (u) of this provision.

(xi) The clause at 52.212-4, Contract Terms and Conditions – Commercial Items (Oct 2018), Alternate I (Jan 2017) applies to this acquisition. The following addendum has been attached to this provision:

Addendum The clause 52.217-9 Option to Extend the Term of the Contract (Mar 2000).

(a) The Government may extend the term of this contract by written notice to the Contractor within 30 days provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least 30 days before the contract expires. The preliminary notice does not commit the Government to an extension.

(b) If the Government exercises this option, the extended contract shall be considered to include this option clause.

(c) The total duration of this contract, including the exercise of any options under this clause, shall not exceed 60 months.

Original invoices shall be e-mailed to: 26T26TINVOICEMANAGER@PBGC.GOV26T26T with a courtesy going to the Contracting Officer Technical Representative (COR), and Contracting Officer.

(xii) The provision at 52.212-5, Contract Terms and Conditions Required to Implement Statutes or Executive Orders – Commercial Items (Mar 2020), applies to this acquisition.

(xiii) A statement regarding any additional contract requirement(s) or terms and conditions (such as contract financing arrangements or warranty requirements) determined by the contracting officer to be necessary for this acquisition and consistent with customary commercial practices. N/A.

(xiv) Rating under the Defense Priorities and Allocations System (DPAS) – N/A.

(xv) The date, time and place quotes are due: Quotes shall be submitted via email to the Contracting Officer (CO), Esan Sumner, at 26T26TSumner.Esan@pbgc.gov26T26T and the Contract Specialist, Olena Evans, at 26T26TEvans.Olena@pbgc.gov26T26T, no later than 10:00 AM Eastern Daylight Time (EDT) on June 9, 2020.

(xvi) Questions regarding this solicitation shall be submitted via email to the Contracting Officer (CO), Esan Sumner, at 29TUSumner.Esan@pbgc.govU29T and the Contract Specialist, Olena Evans, at 29TEvans.Olena@pbgc.gov29T, no later than 10:00 AM Eastern Daylight Time (EDT) on May 19, 2020.

Responses to all inquiries/questions will be published by amendment to the solicitation. No information concerning this solicitation will be provided in response to telephone calls.

Prospective Quoters are instructed to submit their questions using the template in Attachment E of this solicitation.

PAGE 6 OF 53 16PBGC20Q0036

Attachment A

SUPPLIES OR SERVICES AND PRICES/COSTS

1. DESCRIPTION OF SERVICES

The Contractor shall perform all services for the Legacy Pension Insurance Modeling System (PIMS) to the PBGC as listed in Attachment B the Statement of Work (SOW).

2. PRICE SCHEDULE

Hourly Rates: The Contractor shall use the hourly rate for each labor category listed below for the base and each option period. The hourly rate for each category includes direct labor, all indirect costs, and profit (fully burdened).

Base Year: September 1, 2020 through August 31, 2021

CLIN Labor Category Unit

No. of Units

Unit Price

Total Amount

0001 Base Year:

(a) Project Manager (Key Personnel) Hour TBP** TBP TBP

(b) Senior Actuary (Key Personnel) Hour TBP TBP TBP

(c) Actuary Hour TBP TBP TBP

(d) Senior Analyst/ Software Engineer Hour TBP TBP TBP

(e) Analyst/ Programmer Hour TBP TBP TBP [add here, if necessary] Hour TBP TBP TBP

Total, Base Year: 7,093* TBP

Option Year 1: September 1, 2021 through August 31, 2022

Unit

No. of Units

Unit Price

Total Amount

1001 Option Year 1:

(a) Project Manager (Key Personnel) Hour TBP** TBP TBP

(b) Senior Actuary (Key Personnel) Hour TBP TBP TBP

(c) Actuary Hour TBP TBP TBP

(d) Senior Analyst/ Software Engineer Hour TBP TBP TBP

(e) Analyst/ Programmer Hour TBP TBP TBP

Total, Option Year 1: 7,093* TBP

Option Year 2: September 1, 2022 through August 31, 2023

Unit

No. of Units

Unit Price

Total Amount

2001 Option Year 2:

(a) Project Manager (Key Personnel) Hour TBP** TBP TBP

(b) Senior Actuary (Key Personnel) Hour TBP TBP TBP

(c) Actuary Hour TBP TBP TBP

PAGE 7 OF 53 16PBGC20Q0036

(d) Senior Analyst/ Software Engineer Hour TBP TBP TBP

(e) Analyst/ Programmer Hour TBP TBP TBP

Total, Option Year 2: 7,093* TBP

Option Year 3: September 1, 2023 through August 31, 2024

Unit

No. of Units

Unit Price

Total Amount

3001 Option Year 3:

(a) Project Manager (Key Personnel) Hour TBP** TBP TBP

(b) Senior Actuary (Key Personnel) Hour TBP TBP TBP

(c) Actuary Hour TBP TBP TBP

(d) Senior Analyst/ Software Engineer Hour TBP TBP TBP

(e) Analyst/ Programmer Hour TBP TBP TBP

Total, Option Year 3: 4,002* TBP

Option Year 4: September 1, 2024 through August 31, 2025

Unit

No. of Units

Unit Price

Total Amount

4001 Option Year 4:

(a) Project Manager (Key Personnel) Hour TBP** TBP TBP

(b) Senior Actuary (Key Personnel) Hour TBP TBP TBP

(c) Actuary Hour TBP TBP TBP

(d) Senior Analyst/ Software Engineer Hour TBP TBP TBP

(e) Analyst/ Programmer Hour TBP TBP TBP [add here, if necessary] Hour TBP TBP TBP

Total, Option Year 4: 4,002* TBP

*Estimated not-to-exceed (NTE) number of hours **TBP = To be proposed by quoter

Not to Exceed (NTE) Total Contract Ceiling Price: [TBP]. Not to Exceed Total Hours:

29,283.

Contract ceiling prices and total number of hours for each period of performance are not to be exceeded unless modified via bilateral modification.

PAGE 8 OF 53 16PBGC20Q0036

Attachment B

STATEMENT OF WORK (SOW)

LEGACY PENSION INSURANCE MODELING SYSTEM (PIMS)

ACTUARIAL SUPPORT SERVICES

1. INTRODUCTION AND BACKGROUND

The Pension Benefit Guaranty Corporation (PBGC) was established to develop and administer the pension plan insurance programs as provided in Title IV of the Employee Retirement Income Security Act (ERISA) of 1974. PBGC’s mission is primarily to: 1) encourage the continuation and maintenance of voluntary private pension plans for the benefit of their participants, 2) provide for the timely and uninterrupted payment of pension benefits to participants and beneficiaries under plans to which Title IV applies, and 3) maintain PBGC insurance premiums at the lowest level consistent with carrying out its obligations 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 collective bargaining agreement. The multiemployer (ME) program covers plans that are collectively 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.

The single-employer program is by far the larger of the two programs, insuring about 24.7 million workers and retirees covered by about 24,000 plans as of September 30, 2019. This program guarantees payment of benefits, subject to limits set by law. If an insured plan terminates without enough money to pay all benefits, then PBGC trustees the plan, takes over any assets and assumes the responsibility to pay plan participants. As of September 30, 2019, PBGC has terminated or trusteed nearly 5,000 single-employer plans and assumed responsibility for the benefits of nearly 1.5 million workers and retirees. In fiscal year 2019, PBGC paid over $6 billion in benefits, and by the end of the year it was paying retirement benefits to more than 887,000 people each month.

There are about 1,400 multiemployer plans that cover more than 10.8 million workers and retirees. Unlike the single-employer program, under which PBGC guarantees payment of benefits upon termination of an underfunded plan, under the multiemployer program, PBGC guarantees payment of benefits if a covered plan is insolvent and unable to pay basic PBGC guaranteed benefits when due. Also, unlike the single-employer program, insolvent multiemployer plans are not trusteed by PBGC. Rather PBGC financially assists insolvent plans to enable them to continue paying guaranteed benefits themselves.

The Pension Insurance Modeling System (PIMS) is the tool developed by the Policy, Research and Analysis Department (PRAD) to model the SE and ME pension plan universes. The current SE PIMS and ME PIMS models in conjunction are referred to as Legacy PIMS. A newer PIMS model is currently under development. This contract only sustains the current Legacy PIMS;

Development of a future state PIMS is out of scope for this contract. PBGC anticipates that after the implementation of a future state PIMS, the Legacy PIMS will be decommissioned during this contract’s overall Period of Performance.

PAGE 9 OF 53 16PBGC20Q0036

Single-Employer PIMS – SE PIMS is a stochastic (i.e., random) simulation model that PBGC uses to evaluate its exposure and likelihood of future claims and to quantify the amount of risk facing the single-employer insurance program. SE PIMS portrays PBGC's future financial condition as a function of a variety of economic parameters. For further discussion, please see the PIMS webpage at PBGC.GOV. SE PIMS has over 55,000 lines of computer code written in the C++ programming language. The input database for the model includes significant details on a sample of about 500 pension plans, key financial variables from approximately 400 companies that sponsor those pension plans, details on the PBGC's current assets and benefit payment obligations, and recent history of key financial market returns. Pension plan and actuarial data is taken from the Form 5500, the Schedule SB and attachments; it includes benefit formulae, age/service matrices of active workers, number of retirees, benefit payouts, actuarial assumptions, and schedules of amortization bases.

SE PIMS simulates thousands of random scenarios of potential future outcomes using a pseudo-random number generator and measures of the volatility of key variables and the correlation among them. The scenarios projected in the simulation extend up to 20 years into the future. In each year of a scenario, the program simulates:

1. Annual returns of stock and bond market indices; changes to the financial variables of each plan sponsor.

2. Changes to each pension plan's liabilities reflecting advancements in age and service, as well as retirements and other employment separations, among the active participants, hiring and retirement rates consistent with changes to sponsors' total employment levels, advancement in ages and mortality rates among the retired population, benefit and/or salary level increases, and changes to valuation discount rates.

3. Changes to the asset level of each plan, including asset returns determined by plans' portfolio selections and the simulated market returns, benefit payments to retired participants, and contributions from the plan sponsor meeting the requirements of the Internal Revenue Code’s pension funding rules.

4. Random occurrences of bankruptcy among the pension plan sponsors, with bankruptcy probabilities being determined by each firm's financial variables, and calculation of whether the funding levels of plans sponsored by bankrupt firms implies a claim on the PBGC insurance fund.

5. Changes to PBGC assets and liabilities that reflect premium revenues from plan sponsors, benefit payments to trusteed beneficiaries, asset returns and changes to liability discount rates, age advancement and mortality among beneficiaries, and new claims presented by underfunded plans of bankrupt firms.

The program stores output on key variables related to pension funding and PBGC assets and liabilities. The output is analyzed by the PBGC to develop probability distributions over the range of financial outcomes the PBGC could experience in the future.

The actuarial component of the program, which tracks plans' liabilities, assets and contribution requirements through time, represents the most significant component of the model in terms of programming detail and complexity.

PAGE 10 OF 53 16PBGC20Q0036

Multiemployer PIMS – Like SE PIMS, Legacy ME PIMS is also a stochastic (i.e., random) simulation model that PBGC uses to evaluate its exposure and likelihood of future claims and to quantify the amount of risk facing the multiemployer insurance Program. It is also used to satisfy PBGC's statutory requirement under Section 4022 of ERISA to conduct quinquennial studies of the multiemployer insurance program to determine the adequacy of multiemployer premium rates and benefit guarantees.

ME PIMS was entirely recoded by PRAD during 2018 to make it more flexible and powerful.

This model is developed in Excel. All calculations are completed in Excel-based formulas, with some Visual Basic for Applications (VBA) components to improve efficiency and reduce run-time. This allows users to easily make changes to the model and to adapt to the Technical Assistance requests received from Capitol Hill.

The Model relies on data from the Form 5500 database, primarily from the Schedules MB and H/I. The census data (ultimately the cash flows) are developed using other supporting spreadsheets that calibrate to the Current Liabilities and Current Liability Normal Cost with sample census distributions.

2. DEFINITION OF WORK REQUIRED

The Contractor shall provide support for the Legacy PIMS Model to the PBGC in two regards:

i. The Contractor shall support SE Legacy PIMS. This includes programming, running, and evaluating the results of SE PIMS.

ii. The Contractor shall assist PRAD on the technical programming and evaluation of work performed with the ME Legacy PIMS model, including but not limited to Technical Assistance requests from Capitol Hill and assistance on the PRAD report deliverables.

3. SCOPE OF WORK

Work hereunder will be directed to the Contractor by work assignments. The services required of the Contractor fall within the following headings:

3.1. Actuarial Services, Actuarial Expertise, Actuarial Studies and PIMS Related

Projects

The Contractor shall provide support for actuarial services, expertise, studies and other Legacy PIMS related projects. Services may include but are not limited to:

a) Annual actuarial evaluations of PBGC's expected operations and financial status required under Section 4008 of ERISA.

b) Quinquennial studies of the multiemployer insurance program to determine the adequacy of multiemployer premium rates and benefit guarantees required under Section 4022 of

ERISA.

c) Analyses of legislative, regulatory, and/or policy proposals to determine the impact on PBGC's financial position.

d) The production of input to the annual and mid-session financial forecasts for PBGC's

PAGE 11 OF 53 16PBGC20Q0036

President's Budget submissions to DOL and OMB.

e) Other special reports and analyses as requested by PBGC management or other Executive or Legislative branch staff.

3.2. Operation and Maintenance (O&M) to the Legacy PIMS Models

In order to maintain the PIMS application in production and provide user support, the Contractor shall do the following to meet the customer's needs, organization's goals, and objectives.

a) Contact users and provide technical assistance to ensure issues are resolved timely.

Effectively communicate with the users to provide the status of the open issues.

b) Conduct analysis of problems reported by users and recommend functional and/or technical improvements, including the addition of business and technical features to existing software. Provide alternative solutions to improve the related processes and assist in exploring possibilities of using new features, functions, and modules.

c) Participate in root cause analysis in order to resolve production and user support issues effectively.

d) Effectively respond to questions about the system outages and errors. Resolve technical issues with Information Technology Infrastructure Operations (ITIO), production SQL Database Administrators (DBAs), network support, other PBGC teams, and other systems.

e) Provide support to ITIO to resolve application production issues.

f) Support system administration duties as needed.

g) Support application and system audits from external and internal auditors.

h) Participate in corporate-wide IT initiatives such as System Security Plan (SSP) updates and assist with PIMS System Assessment and Accreditation (SA&A) process leading to the attainment of an Authority to Operate for ME PIMS and SE PIMS.

i) Provide technical assistance to PBGC as needed. Examples include, but are not limited to, testing and migration of applications to future versions of software, database and operating systems on servers.

j) Retire applications. The Contractor may propose processes, and methods for retiring and archiving applications, as long as they do not conflict with the current PBGC guidelines for decommissioning systems and are approved by the COR and ITIOD.

k) Plan and participate in Continuity of Operations Plan (COOP) testing for the PIMS applications; develop COOP testing scenarios; work with users and COOP team to execute COOP tests and document results if requested.

l) Support activities for transitioning applications from/to other teams.

m) Support other PBGC teams responding to questions related to PIMS and/or related applications.

n) Provide other production support as needed, such as troubleshooting, debugging, identifying problems/errors, making corrections and improving efficiencies of PIMS and implementing changes in laws, policies and regulations as they occur.

PAGE 12 OF 53 16PBGC20Q0036

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

p) Provide ongoing expert advice to PRAD in all areas of both Models, including their operation and capabilities.

q) Support the IT and Business Program Managers in conducting the annual operational analysis required by the PBGC Information Technology Portfolio Review Board

(ITPRB).

r) 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 documentation, coordinating removal/uninstall of code and components from all IT environments and ensuring data back-up and archiving as well as working with PIMS Transformation Contractor related to any data migration for the transition to the new PIMS system.

s) The following are examples of the type of support expected from the Contractor, but not limited to:

1) Giving ongoing expert advice in the operations and capabilities to users on all areas of the PIMS and related systems.

2) 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 application users or by the Contractor's own personnel.

3) Determining the scope and cost (in time and dollars) of proposed modification or corrections to the existing PIMS system.

4) Making corrections to the PIMS as requested and approved by the Subject Matter Expert (SME) and the COR according to an agreed upon schedule.

5) Providing corrections to documentation according to an agreed upon schedule.

6) Providing subject matter expertise in the current workings of PIMS and current PIMS technology to IT groups and PIMS Transformation team, including working with PIMS transformation contractor.

3.3. System Modification to Legacy PIMS

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

a) Perform and complete project initiation, planning, research, analysis, design, development, and testing and implement any approved system modification and requirements to the existing application in compliance with the Information Technology Solutions Life Cycle Management (ITSLCM) Framework.

b) Schedule and coordinate the releases with the integrated project/program team and deliver the releases on time and within budget.

c) Deploy high quality software releases in production and minimize downtime in production due to quality issues.

d) Leading the effort to analyze, prioritize and conduct meetings to determine system modifications.

PAGE 13 OF 53 16PBGC20Q0036

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

f) 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.

g) Deploy all software system modifications through releases according to established PBGC Software Configuration 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.

h) Conduct appropriate system level tests (e.g., unit testing, parallel testing, regression testing, integration testing, performance testing, load testing, functionality testing) to modify the quality of software releases. The Contractor may use automated testing tools.

i) Support and assist application users in User Acceptance Testing (UAT) of the application, including, but not limited to, (1) the preparation of test plans, test cases/scripts and test results, (2) the use of automated testing tools, and (3) the development and maintenance of operation system documentation and procedures.

j) Effectively coordinate the notification of the deployment of releases to users, stakeholders, Service Desk, COR, and other impacted parties in a timely manner to provide impacted parties time to prepare for the release.

k) Providing system modifications that include the design, programming, testing and implementation of major upgrades or significant new modeling capabilities based on user requirements developed by PRAD.

l) Propose system modifications and corrections for both Models.

m) Implement system modifications or corrections to both Models as approved by PRAD management and in accordance with an agreed upon implementation schedule.

3.4. Project Management - Planning, Scheduling, Tracking, Managing, Reporting

The contractor shall work directly with COR, BISD Project and Program Manager, PRAD Program Manager and PRAD customers to proactively plan and manage all work performed under this contract. The contractor shall:

a) Understand priorities and align their team with changing priorities.

b) Follow the Change Management process outlined in the Team Workflow and Separation of Duties chart below.

c) Develop project management plans and project baselines for identified projects to include releases or any activity where resources are deployed to make changes to or support the PBGC systems.

d) Conduct scope management to ensure project scope is baselined and changes to scope are managed through the project lifecycle. Establish and follow procedures for release management and change control, including an impact assessment.

e) Conduct schedule management to include establishing a resource-loaded and baselined schedule in PBGC’s approved project management system (currently Microsoft Project

PAGE 14 OF 53 16PBGC20Q0036

Online, a.k.a. P3M).

f) Conduct cost management to ensure baselined costs are maintained and managed throughout the project lifecycle to include reporting on burn rates and associated cost measures.

g) Maintain relationship and partnership with all integrated system leadership for systems both internal and external to the project IT applications/systems.

h) Follow the ITSLCM framework and PBGC IT FAR Supplement Clauses in developing the schedule and ensure the schedule includes the deliverables, milestones, planned durations for each task, project start and end dates, resources, work breakdown structure of activities, and other specific information needed to track the projects. The Contractor will work with the subject matter experts and other stakeholders in eliciting requirements.

(See, below):

PAGE 15 OF 53 16PBGC20Q0036

PAGE 16 OF 53 16PBGC20Q0036

3.4.1 Issue and Risk Management

PBGC places great importance on actively performing risk management. Identifying, developing mitigation strategies and effectively escalating risks are a key component of project management. The Contractor shall:

a) Establish risk management plan based on PBGC Risk Management Policy.

b) Identify and track risks that may impact the project and PBGC systems and identify mitigation strategies in BISD’s system of record (currently P3M).

c) Identify and track issues and work to resolve to ensure system operations and release remain on-schedule.

3.4.2 Status Reporting

Regular and ad hoc reporting is required to ensure all PBGC project stakeholders are aware of project and system status. The Contractor shall provide regular status and ad hoc reporting to COR, IPT, executive sponsors for all contractor activities (both oral and written) as required.

The contents of the Project Management Report (PMR) and Monthly Status Report (MSR) are identified in Section 10 - Deliverables (below).

3.4.3 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:

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

b) Provide status on system operations and changes.

3.4.4 Meeting Participation

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:

a) Develop agendas and circulate those agendas ahead of any meetings organized by the contractor.

b) Develop meeting materials when the contractor is presenting.

c) Facilitate meetings that allow for in-person and/or remote participation via teleconference, Skype and/or other remote participation tools.

d) Record and provide minutes of all meetings conducted or attended as part of this contract work and deliver those minutes for participant review and comment.

e) Participate in meetings as required for other PBGC efforts that may impact or be impacted by this contract.

PAGE 17 OF 53 16PBGC20Q0036

3.4.5 System Documentation and Documentation Maintenance

PBGC system documentation includes any documentation generated as part of a maintenance or system modification effort, technical documentation, models, operational manuals, meeting agendas/minutes and any documentation used or created as part of the performance of PBGC system support. All documentation 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 coordination 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:

a) Develop or update PBGC documentation, including manuals (e.g., operations, system administration, system maintenance, user and training) and plans (e.g. system integration and site implementation). Documentation shall follow the latest approved standards at the time of the execution effort and delivery of the system. The Contractor shall develop documentation and/or update existing ITSLCM documents that are required as a result.

b) Maintain and revise PBGC system and business process documentation in accordance with changes made to PBGC.

c) Comply with PBGC standards and guidelines for all documentation.

d) Update all system documents when changes occur in the application or process.

3.4.6 Transition Support

The objective of transition support is to ensure continuity of services in the areas supported by the incumbent while the incoming contractor learns how to support these services. The Contractor shall support transition from the outgoing incumbent, as well as transition to PBGC or a new contractor, if required.

Transition In - Upon award, the Contractor shall begin an effective transition of work from the incumbent. The contractor shall assume full responsibility for an orderly phase-in of operations that minimize the impact to PBGC. The contractor shall ensure that transition activities are transparent to the current operations and do not disrupt or adversely affect the current day to day operations. The transition in period shall not exceed 60 days after 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 documentation, transfer of all knowledge and any other activities required.

Transition Out - The Contractor shall accommodate transition for at least two (2) months of its functions to PBGC or a new contractor upon re-compete of this contract. The Contractor shall deliver all documentation, information for the operation and maintenance of the PBGC systems, and provide communications, training, and support to PBGC to ensure a successful transition of PBGC to another vendor. The Contractor shall develop a Transition Strategy detailing the steps necessary to transition operations and maintenance to PBGC, another PBGC selected vendor and any documentation or activities for releases work that may be underway. At completion of the contract, all licenses revert to PBGC. All documentation shall be maintained and kept current during the transition period by the Contractor.

PAGE 18 OF 53 16PBGC20Q0036

4. PIMS ARCHITECTURE AND OPERATION

The architecture for the production environment is comprised of 9 blade servers, running on Windows 2016 Standard. These are connected to an MS SQL Server and exposed to the user through a Windows 16 Desktop. The Development and QA environments are comprised of 50 blade servers, running on Windows 2016 Standard, with a MS SQL server on the back end. This drone farm is exposed to the user via Windows 16 desktops. From a user desktop within PRAD, the user can perform the following tasks:

i. View/edit data

ii. Submit jobs

iii. Review progress of jobs

iv. View/Print results

v. Compare job results/settings

vi. Execute post-processing using SAS, a statistical analysis tool used by PRAD staff as a supporting 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 execution 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, calculations done within PIMS produces output files and stores them in job-specific output directories. These output directories are in the application/file server.

Most of the code is written in C++. The codebase itself contains active 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 statistical tool. For some SAS programs, the output is automatically converted into excel for additional graphs and reports for the end user.

(See, below):

PAGE 19 OF 53 16PBGC20Q0036

5. PERSONNEL

The Contractor shall provide the right skill mix of qualified personnel with actuarial and systems development skills for each effort.

5.1. Key Personnel

The following are qualifications required for the Key Personnel category:

Labor Category Qualifications*

Project Manager

• Minimum 7 years of experience with IT software development projects.

• Project Management Professional (PMP)®.

• 4+ years (can be included within the 7 years) hands-on experience providing project management on Federal government contracts, including Project Management Tools, work break down structures, project structure, scheduling, and performance reporting.

• Written and verbal communication skills, including experience in presenting material to senior Government officials.

• Management of manpower utilization, procurement, problem resolution, and employee relations.

• Maintenance of project schedules and deliverables completed according to Government requirements.

• B.S. or B.A Degree Information Technology, Actuarial Science, Computer Science, Business, Management, Engineering, Mathematics, or other related discipline) or equivalent experience

• Technical experience shall include previous work managing projects of staff that worked with computer applications or languages such as: Visual Basic, C++, Excel, .Net, MS-Access, Crystal Reports, MS SQL Database.

Senior Actuary

• Certification by the quoter that the individual functions as a senior actuary with authority to sign actuarial reports and certify actuarial results prepared by the firm.

• At least 3 years of experience working with Title IV or ERISA.

• 10 years of Defined Benefit (DB) pension plan experience

• a Fellow of the Society of Actuaries (FSA) and Enrolled Actuary (EA)

• a minimum of 10 years of DB pension plan experience.

• Bachelor's degree.

*Note: Key Personnel experience and education may be substituted without substantially deviating from the minimum requirements at PBGC’s discretion.

PAGE 20 OF 53 16PBGC20Q0036

5.2. Non-Key Personnel

The following are qualifications required for the Non-Key Personnel category:

Labor Category Qualifications*

Actuary

• Bachelor's degree.

• Five years of Defined Benefit (DB) pension plan experience, and meets one of the following requirements:

FSA with five years of DB pension plan experience, a minimum of two years obtained alter receiving the later or the FSA or EA designations; or ASA with five years of DB pension plan experience, a minimum of four years obtained after receiving the later of the ASA or EA designations; or EA with five years of DB pension plan experience, a minimum of four years obtained after receiving the EA designation. Bachelor's degree in Mathematics, Actuarial Science, Statistics, Computer Science, or a related discipline.

Senior Analyst/ Software Engineer

• Eight years of experience in actuarial related systems development.

• At least five of these years involve primary technical responsibility for systems design and development. Experience should include demonstrated ability to work independently and in teams and provide technical leadership to more junior staff.

• Must have demonstrated experience with MS SQL. C#/C++ programming and experience in the development or web-based systems utilizing products/languages such as Visual Basic, .Net, and Crystal Reports.

• Demonstrated government or commercial contract experience utilizing state-of-the-art technologies or specialized skills in support or IT system development efforts.

Analyst/ Programmer

• Five years of programming experience including one years of actuarial programming experience. This experience shall include developing and testing programs in at least one or more of the following languages: Visual Basic, .Net, C#/C++ and experience with MS SQL.

*Note: Non-Key Personnel experience and education may be substituted without substantially deviating from the minimum requirements at PBGC’s discretion.

6. CONSTRAINTS

The Contractor shall ensure compliance with applicable federal regulations, standards, PBGC policies, processes, procedures, and directives in the performance of this contract.

7. PERIOD OF PERFORMANCE

PBGC anticipates a Base Period of 12-months commencing on date of award followed by four

(4) 12-months Option Periods. Total of base period and all option periods shall not exceed 60

PAGE 21 OF 53 16PBGC20Q0036

months:

- Base Period: September 1, 2020 through August 31, 2021

- Option Period 1: September 1, 2021 through August 31, 2022

- Option Period 2: September 1, 2022 through August 31, 2023

- Option Period 3: September 1, 2023 through August 31, 2024

- Option Period 4: September 1, 2024 through August 31, 2025

8. PLACE OF PERFORMANCE

The work shall be performed primarily at PBGC Headquarters or off-site as agreed to by the Government.

It is anticipated that the PBGC offices will be relocated during the period of performance of this contract but remain in Washington, D.C. service area. At such time as the relocation occurs, the work conducted at the Government site will move to the new location.

The Government will not pay for travel or parking. The Contractor shall perform all work described herein that is ordered by the Government during the term of the contract at any location specified. The Government may allow services to be performed from off-site in instances where special tasks must be accomplished to meet project schedules or deadlines. In instances where tasks do not require direct involvement of Government personnel, work may be performed off-site. Performance of such tasks will be coordinated with the COR. The government shall furnish contractors with the equipment required to provide remote access support and utilized Government-provided and - approved software for connectivity, if remote support is required.

9. HOURS OF OPERATION

Primary core hours that the contractor shall be available are Monday-Friday 8:00AM-5:00PM.

Hours of availability may be altered with prior approval by the Contracting Officer Technical Representative (COR).

Operations support personnel should be available during core hours and on-call needs. The contractor shall follow FAR and PBGC policy regarding holidays and inclement weather in coordination with the COR.

10. DELIVERABLES

PRAD, COR, and the IT Project Manager shall use deliverable quality, accuracy, and timeliness to assess contract performance.

RFQ

Section

Deliverable Description Frequency

3.3 Schedule of Releases for performance year. Within first 30 calendar days of the beginning of each fiscal year

PAGE 22 OF 53 16PBGC20Q0036

RFQ

Section

Deliverable Description Frequency

3.3 Detailed Project Schedule for releases. Due 15 days after requirements are approved

3.4 Technical Approach to the SOW Due 30 days after contract

award

3.4 Level of Effort (LOE) Documentation to include at a

minimum business need, scope, effort hours, cost, high level requirements, risks, feasibility analysis, alternatives, and comparative analysis of alternatives, recommended alternatives, risks, and project deliverables.

TBD in coordination with the COR

3.4.2 Prepare and Conduct Monthly PMR (at a minimum, outage, staffing, burn rate, release schedule, risk register, issues, compliance to new or changing IT requirements).

Monthly

3.4.2 Status reports (including contractor hours report, any

deliverable status, milestones, planned activities, completed activities).

Monthly

3.4.2 Regular status and ad hoc reporting to COR, IPT, executive sponsors for all contractor activities.

TBD in coordination with the COR

3.4.4 Meeting Agendas and minutes. As required by

customer/COR

3.4.5 ITLSCM Documentation as determined by the IT Project

Manager/COR.

As required for releases

11. PLACE OF DELIVERY

All agreement deliverables must be delivered to the Contracting Officer’s Representative (COR) as identified in the contract.

PAGE 23 OF 53 16PBGC20Q0036

Attachment C

INSTRUCTIONS, CONDITIONS, AND NOTICES TO QUOTERS

1. RESPONSIBILITY

This contract shall be awarded only to a responsible prospective Quoter. To be determined responsible, the Quoter must:

a) Have adequate financial resources to perform the contract, or the ability to obtain them;