16PBGC22R00080001.pdf

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NUMBER

IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

Attachment Page

PAGE 2 OF 22 16PBGC22R00080001

Continuation Page

The purpose of this amendment is to answer questions received and provide updated language in Section L.

As a result of this amendment the following changes are made:

1. Added J.5 Amendment 0001 Questions Answered

2. Updated Section L with track changes.

3. All other terms and conditions remain the same.

Table of Contents

SECTION J LIST OF ATTACHMENTS

J.1 Amendment 0001 Questions Answered

SECTION L INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 Section L Amendment 0001

PAGE 3 OF 22 16PBGC22R00080001

SECTION J

LIST OF ATTACHMENTS

J.1 Amendment 0001 Questions Answered

PAGE 4 OF 22 16PBGC22R00080001

Question Number Referenced Solicitation Page # Referenced Solicitation Section Offeror Question(s) Government Answer

1 319 Section L, subsection 12(b)

We think you are referring to standard Form 1449 (provided in 2017); however, would you confirm where we find SF 33 and SF30(s)

Correct, we were referring to the SF1449 publishing this solicitation and the SF30's published for subsequent amendments (such as the one used to publish the answer tp this question). SF 33 was published in error and has been corrected in Section L.

2 304 Section L, subsection 1(a) viii

Please confirm that all of the requirements in this section should be applied to the electronic submission (as opposed to both hard copy and electronic submissions)?

We are only seeking electronic submissions. If an offeror does not have the means to submit an electronic copy they may contact gangi.jeffrey@pbgc.gov to arrange for a paper submission. Additionally the reference to the SF33 in the specificed section has been correced to

SF1449.

PAGE 5 OF 22 16PBGC22R00080001

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 Section L Amendment 0001

PAGE 6 OF 22 16PBGC22R00080001

Section L: Instructions to Offerors

1. GENERAL REQUIREMENTS

The Offeror shall provide a proposal that conforms to the requirements outlined in this solicitation. The Offeror’s failure to follow any of the requirements in the instructions may result in the proposal not being evaluated for award.

a. Proposal Requirements

i. The written proposal shall be well-organized, legible, and professional in appearance.

ii. The proposal shall be submitted in three (3) separate volumes as described below so the evaluation of each part may be conducted independently.

iii. Each volume shall include a table of contents reflecting only the contents of that volume.

iv. Tables of contents shall reference the labeled tabs, making it clear to the reader which tab contains the topic.

v. Every page shall be sequentially numbered.

vi. The written proposal shall be single-spaced, printed double-sided in black ink on 8.5 x 11 inch white paper with a font size 10 pitch font or larger and a style common to professional communications, margins one inch and page numbers centered in the bottom margin.

vii. When describing sequential events or enumerating substantive lists, Offerors should use bullets or numbered lists rather than embedding the events or list items into narrative paragraphs.

viii. Proposals shall be submitted electronically to gangi.jeffrey@pbgc.gov and Baldus.Carl@pbgc.gov no later than the Offer Due Date identified in Block 8 of the SF33SF1449.

2. QUESTIONS CONCERNING THE SOLICITATION

a. Questions/inquiries for information about any aspect of the solicitation shall be submitted to Jeff Gangi (gangi.jeffrey@pbgc.gov) and Rudy Baldus (Baldus.Carl@pbgc.gov) no later than August 20, 2022. Responses to all inquiries/questions will be published by amendment to the solicitation at www.sam.gov, giving due regard to the proper protection of proprietary information. Offerors shall be responsible for assessing www.sam.gov for the agency’s responses. No information concerning this solicitation shall be provided in response to telephone calls. Prospective Offerors are warned against contacting any PBGC personnel outside the Procurement Department prior to award of a Contract resulting from this solicitation. If such contact occurs and is found to be prejudicial to competing Offerors, the Offeror making such

PAGE 7 OF 22 16PBGC22R00080001

contact may be excluded from award consideration. Prospective Offerors are asked to submit their questions grouped by solicitation section using the format below.

Question Number

Referenced Solicitation Page #

Referenced Solicitation Section

Offeror Question(s)

3. DETERMINATION OF RESPONSIBILITY

A contract awarded resulting from this solicitation shall be awarded to only one (1) responsible Contractor.

4. LETTER OF TRANSMITTAL

a. The proposal shall be accompanied by a cover letter (letter of transmittal) prepared on the company’s letterhead stationery. The letter of transmittal shall identify all enclosures being transmitted as well as a table of contents for all volumes. The first or title page shall be in accordance with FAR 52.215-1(c). Specifically, the first page of the proposal must show—

i. The solicitation number;

ii. The name, address, and telephone and facsimile numbers of the Offeror (and electronic address if available);

iii. A statement specifying the extent of agreement with all terms, conditions, and provisions included in the solicitation and agreement to furnish any or all items upon which prices are offered at the price set opposite each item;

iv. Names, titles, and telephone and facsimile numbers (and electronic addresses if available) of persons authorized to negotiate on the Offeror’s behalf with the Government in connection with this solicitation; and

v. Name, title, and signature of person authorized to sign the proposal. Proposals signed by an agent shall be accompanied by evidence of that agent’s authority, unless that evidence has been previously furnished to the issuing office.

vi. A statement that the Offeror’s proposal is valid for a period of 180 calendar days from the submission date of the proposal.

vii. Any information included in the Offeror’s cover letter will not be evaluated in relation to Volumes I-III.

5. COMPLIANCE

a. All proposals shall be evaluated preliminarily to ensure compliance with the requirements set forth in this solicitation which include the following:

PAGE 8 OF 22 16PBGC22R00080001

i. Timely receipt of the offer.

ii. Information presented in the manner required by Proposal Submission Instructions above.

iii. Inclusion in the offer of all information required by Mandatory Requirements, and Technical Proposal and Business / Price Proposals below.

6. LATE PROPOSALS

a. Complete electronic versions must both be received before the time and date specified for receipt in SF 1449 Block 8. If the electronic version of the proposal is received at the virtual destination after the time and date specified for receipt, the proposal will be considered late and will be dealt with in accordance with the late proposal provision of

FAR 52.215-1.

b. No exceptions will be made for the submission deadline above. PBGC recommends early submission, as computer traffic gets heavy near announcement closing. Do not wait until the last minute. PBGC is not responsible for missed proposal submission due to system lag or inaccessibility.

8. PROPOSAL PREPARATION COST

a. This Request for Proposal does not commit the Government to pay any costs incurred in the preparation and submission of your proposal. By the submission of its offer, the offeror assumes all associated cost.

9. PROPOSAL VOLUMES

a. Offeror’s proposal shall be evaluated in two (2) separate Phases, Phase I and Phase II.

The proposals shall be divided into three (3) separate Volumes – Volume I, Volume II and Volume III, as described in further detail below.

b. Phase 1

i. Volume I –Mandatory Volume Requirements – (Section J.1 Mandatory Requirements Certification and J.2 Mandatory Volume Requirements Excel Sheet) will be the only Volume evaluated in Phase 1; the evaluation team will review Volume I as standalone documents.

c. Phase 2

i. Volume II – Technical Proposal shall contain only responses to:

Factor 1 – Past Performance

Factor 2 – Technical Proposal (subfactors 1-6)

PAGE 9 OF 22 16PBGC22R00080001

ii. Volume III Factor 3 –Price Proposal shall contain only the Offeror’s response to the Business / Price Proposal. Volumes II and III shall be evaluated during Phase II only if the Offeror meets all requirements of Phase I.

** The Offeror shall ensure that no pricing information is included in any other Volume except for Volume III. Incomplete packages may be eliminated from the competition.

10. PAGE LIMITS

a. Below are the page limits associated with each section of the contractor proposal.

PBGC will not evaluate or consider any pages that exceed the page limits listed for each item in the table below. Cover pages, table of contents, tabs, exhibits, attachments and supporting documentation are not included in the count.

Section Page Limit

Phase I, Volume I – Mandatory Requirements 50 Phase II, Volume II Past Performance and Written Technical Proposal, including all subfactors

Phase II, Volume III – Cost/Price Proposal, including:

• Price Proposal

• Signed SF30

• Signed SF30 (if applicable

• Section K “Representations, Certifications, and Other Statements of

Offerors”

Unlimited

11. WRITTEN PROPOSAL CONTENTS

a. Volume 1 – Mandatory Requirements

i. Offerors are required to provide the following within Volume I – Mandatory Requirements:

1. A fully completed Section J.1 Mandatory Requirements Certification and;

2. Section J.2 Mandatory Volume Requirements Excel Sheet; and

3. Any evidence or information supporting answers in J.1 and J.2.

ii. Evidence supporting an offeror’s answers provided in Volume I shall constitute standalone information and shall be evaluated as such. If similar information is necessary for Volumes II and/or Volume III, the information provided in Volume I will not be considered during Phase 2 of the evaluation. Proposals that do not include required information and supporting documents that provide convincing evidence of how all Mandatory Requirements are met will not advance to Phase 2.

PAGE 10 OF 22 16PBGC22R00080001

iii. Mandatory Volume Requirements (MVR) Spreadsheet Attachment J.2

iv. The offeror shall submit the completed MVR spreadsheet demonstrating three years of experience processing volume at equivalent or greater to the minimum volumes stated in the MVR spreadsheet.

1. Mandatory Requirements Certification (MCR) (Attachment J.1)

A. The offeror shall submit a completed MCR, signed, and on company letterhead. The completed MCR shall include the following:

B. Certify the contents of the MVR spreadsheet to be accurate and complete.

C. Identify each member (prime, subcontractor(s), joint venture(s), etc.) of the team that processed the volumes identified on the MVR spreadsheet.

D. Identify the primary and backup locations, system ownership, Maximum Tolerable Downtime (MTD), Recovery Time Objective (RTO) and FIPS 140-2 compliant file encryption protocol, EFT Operations, Check, Tax Forms, and Statement Print/Mail.

b. Volume 2 – Factor 1- Past Performance

i. The offeror shall provide within the written technical proposal evidence of their past performance including meeting delivery dates and schedule that same as, or substantially similar to, that required by the solicitation. The Offeror shall provide at least three references that have knowledge of the Offeror’s performance on work similar to that described in Section C of the solicitation. For each reference the Offeror shall provide:

A. Names, phone number, and e-mail addresses (if available) of contact persons who can provide information regarding the Offeror’s performance.

B. Provide the approximate number and dollar amount of payments made per year.

C. Provide the starting and ending dates of the contract.

D. Indicate whether or not this reference provided a Past Performance Questionnaire.

ii. The Offeror shall forward the Past Performance Questionnaire (Attachment J.3) to at least three references that during the past three years the Offeror has performed work substantially similar to the work described in Section C of this solicitation. Request that each reference return the completed questionnaire by e-

PAGE 11 OF 22 16PBGC22R00080001

mail to gangi.jeffrey@pbgc.gov and Baldus.carl@pbgc.gov. At least one questionnaire should be completed by a client for which the Offeror has managed a transition from a prior paying agent.

c. Volume 2 – Factor 2 - Written Technical Proposal

i. In its Volume 2 – Written Technical Proposal and for each of the Factor 2 subfactors, the offeror shall describe in detail how their proposed solution will meet key elements of the Performance Work Statement (Section C). The offeror’s proposal shall:

A. Reflect an understanding of PBGC requirements and constraints;

B. Address each specific element articulated in the instructions for each sub- factor;

C. Clearly articulate processes and procedures, the sequencing of events, and the flow of information;

D. Clearly identify the roles of the Paying Agent, any Sub-Contractors, and PBGC, and;

E. Reflect an understanding of the risks and problems inherent in the process being described and provide a sound strategy for managing those risks and problems.

ii. Sub-factor 1 – Disburse Benefit Payments

A. Gross to Net Calculation

1. The offeror shall describe its proposed process for performing the gross-to-net calculation for PBGC benefit payments. At a minimum the description shall:

2. Identify the timeframe(s) for the activity with the assumption that data from PBGC (including any last-minute manual changes) have already been received, processed, and balanced.

3. Identify the scope of the activity.

4. Summarize the sequence of events your system and staff go through to perform the activity.

5. Describe any special measures taken to ensure timeliness and quality included evidence (reports, screenshots, etc.) reviewed subsequent to the activity and any authorization process associated with the activity.

PAGE 12 OF 22 16PBGC22R00080001

6. Identify any special Phases that apply to certain categories of payees (e.g. those with multiple roles or subject to IRS tax levies, child support, or life/medical insurance deductions).

B. Electronic Funds Transfers (EFT) Payments

1. The offeror shall describe their proposed process for initiating PBGC benefit payments by EFT. At a minimum the description shall:

a. Identify the timeframe(s) for file creation and the timeframe(s) for file transmission to the ACH Operator and how these timeframe(s) relate to the timeframe(s) for creating a paper check file(s).

b. Address the issue of ACH deletions.

c. Identify the scope of the activity and what data from PBGC is included in the ACH file.

d. Describe how each ACH entry will be mapped to the associated payment in PBGC’s System.

e. Summarize the sequence of events your system and staff execute to perform the activity.

f. Describe any special measures taken to ensure timeliness and quality including evidence (reports, screenshots, etc.)

reviewed subsequent to the activity and any authorization process associated with the activity.

g. Describe any specialist measures taken to ensure the payment history file reflects payments on the first of the month, when the first of the month in not a bank day.

C. Paper Checks

1. The offeror shall describe their proposed process for initiating PBGC benefit payments by paper check. At a minimum their description shall:

a. Identify the timeframe(s) for file creation and the timeframe(s) for file transmission to the check printer and how these timeframes related to the timeframe(s) for creating the ACH file(s). If there is a substantial time delay between file creation and transmission to the printer, address the possibility of deleting payments from the file.

b. Identify the scope of the activity.

PAGE 13 OF 22 16PBGC22R00080001

c. Identify exactly what data from PBGC is included in the paper check file.

d. Describe how each payment in the file will be mapped to the associated payment in PBGC’s system.

e. Summarize the sequence of events your system and staff execute to perform the activity.

f. Identify any special measures that are involved in the activity.

g. Describe any special measures taken to ensure timeliness and quality including evidence (reports, screenshots, etc.)

reviewed after the activity and any authorization process associated with the activity.

h. Describe the security features of your check stock.

i. Describe the settlement process including how it is recorded with checks clear and how outstanding checks are tracked.

j. Describe the offeror’s payee positive pay services

k. Describe the process for stale dated checks.

iii. Sub-factor 2 – Manage Tax Withholding and Other Deductions

A. The offeror shall describe their proposed process for managing tax withholdings and other deductions for PBGC benefit payments included QDROs and life/medical premiums. At a minimum the description shall:

1. Summarize the sequence of events your system and staff execute to create and transmit any electronic files associated with deductions.

2. Describe the process and timeframe(s) for remitting withheld taxes to the IRS.

3. Describe any special cases (e.g. levies, unusual tax situations, multiple roles) where information about deductions may have to follow a special path (e.g. eCARF or NDE instead of Spectrum).

4. Describe your process for recovering overpayment to the IRS.

5. Describe any special measures taken to ensure timeliness and quality including evidence (reports, screenshots, etc.) reviewed subsequent to the activities and any authorization process associated with the activities.

PAGE 14 OF 22 16PBGC22R00080001

6. Include a description of the process and timeframe(s) for reconciling taxes withheld with taxes remitted to the IRS.

7. Describe any special measures that take place just before or after the end of the tax year.

iv. Sub-factor 3 – Maintain and Exchange Data

A. The Offeror shall separately summarize the sequence of events for:

1. Validating, processing, and loading the Spectrum files.

2. Validating, processing, and loading the NFDE files.

3. Creating and transmitting the acknowledgement files.

4. Creating and transmitting the trial balance projection.

5. Creating and transmitting the payment history files.

6. Creating and transmitting the ACH return and NOC files

For each of the above files:

a. Identify the timeframe(s)

i. Summarize the sequence of events your system and staff execute to perform the activity.

ii. Describe any special measures taken to ensure timeliness and quality including evidence (reports, screenshots, etc.)

reviewed subsequent to the activity and any authorization process associated with the activity.

iii. Identify any special measures involved in the activities.

b. Identify any special payment situations (e.g. changes to pre-existing lump sums, complicated tax situations) that would require data to be transmitted via NFDE instead of Spectrum.

c. Describe your proposed process for establishing new accounts on your pension payment system for newly terminated PBGC pension plans including the turnaround time.

d. Describe your process for periodically reviewing user accounts to ensure only authorized users have access to PBGC data including the timeframe for such reviews.

v. Sub-factor 4 – Exception Processing

PAGE 15 OF 22 16PBGC22R00080001

A. The offeror shall describe their proposed process for managing each category of exception associated with PBGC benefit payments. At a minimum the description shall address:

1. Pre-check run exception reports.

2. ACH deletions.

3. Stop payment on checks.

4. Replacement checks for stale dated checks.

5. Manual checks.

6. ACH returns.

7. Return of funds.

8. Manual changes.

9. Notices of Change.

10. ACH reclamations, recoveries, written demands.

11. ACH traces.

B. Payment history adjustments.

C. For each of the above exceptions the offeror shall:

1. Identify any timeframe constraints.

2. Summarize the sequence of events your system and staff execute to perform the activity.

3. Describe any special measures taken to ensure timeliness and quality including evidence (reports, screenshots, etc.) reviewed subsequent to the activity and any authorization process associated with the activity.

4. Identify any special Phases (especially anything manual) involved in the activities.

5. Identify any challenges you foresee with using PBGC’s Collaboration Tool eCARF solution for managing these exceptions and how describe how you propose to overcome them.

vi. Sub-Factor 5 – Financial Management

A. The offeror shall describe the proposed cash accounts that will be established for PBGC benefit payments and describe the flow of funds

PAGE 16 OF 22 16PBGC22R00080001

through the accounts from funding to settlement. At a minimum the description shall:

1. Funding:

a. Describe the proposed process for calculating funding.

b. Identify the timeframe for the calculations.

c. Summarize the sequence of events your system and staff execute to perform the calculation.

d. Identify any special measures that apply to certain categories of payments.

e. Describe any special measures taken to ensure timeliness and quality including evidence (reports, screenshots, etc.)

reviewed subsequent to the activity and any authorization process associated with the activity.

2. Returning of Funds:

a. Describe your proposed process for returning funds to

PBGC.

b. Identify the timeframe for the activity

c. Summarize the sequence of events your system and staff execute to perform the activity.

d. Identify any special measures that apply to certain categories of payments.

e. Describe any special measures taken to ensure timeliness and quality including evidence (reports, screenshots, etc.)

reviewed subsequent to the activity and any authorization process associated with the activity.

3. Financial Stability and Internal Controls

a. The offeror shall submit the following mandatory documents.

b. Service Organization Controls (SOC) 1 Type 2 Reports for each of the most recent two years prepared in accordance with SAS-70 /SSAE 18.

c. Audited financial statements for each of the most recent two years.

PAGE 17 OF 22 16PBGC22R00080001

d. The Management Letters for each of the most recent two years.

vii. Sub-factor 6 –Information Technology Infrastructure/Cyber Security NIST 800 Requirements

A. Information Security Program

1. The offeror shall provide the following to demonstrate the current Risk Posture of the system and environment proposed to execute the services required by this solicitation.

a. A current System Security Plan (SSP), ISO 27001, or SOC Report, showing audited compliance with the NIST 800-171 “Protecting Controlled Unclassified Information in Non-Federal Information Systems & Organizations” Guidance.

b. A current Authority to Operate (ATO) (redacted as needed) covering their system and infrastructure

c. A current Plan of Action & Milestone (POAM)

d. Vendor Management Policy

2. NIST Security Controls: Provide information as to whether or not the NIST security controls identified to be applicable to the system and/or environment are implemented. The PBGC Cybersecurity & Privacy Catalog provided, details organizationally defined parameters for control compliance:

a. How many controls are implemented consistently with PBGC settings?

b. How many controls are implemented, but our organization-defined setting is not consistent with PBGC’s setting?

c. How many controls are not implemented?

d. How many control statuses are currently unknown?

3. Discuss why the status of NIST security controls provided is or is not an accurate and complete representation of the control environment encompassing the proposed team which would handle PBGC sensitive data under this contract. Specify any caveats/reservations. If not accurate or complete, explain in detail the exceptions.

PAGE 18 OF 22 16PBGC22R00080001

B. Information Technology Infrastructure:

1. Provide the following about your Primary IT infrastructure:

a. Name of company & unit

b. Geographic location(s)

c. Services provided

C. Support IT infrastructure and services

a. Name of company & unit

b. Geographic location(s)

c. Services provided

D. Other services

1. provide information pertaining to client personally identifiable information (PII):

a. Service(s)

b. Name of company & unit

c. Primary location

i. Transmissions of client PII to/from this location are/are not encrypted?

ii. If encrypted, are or are not operating in FIPS 140-2 mode.

A. If not FIPS mode, describe how your transition plan addresses this.

**The Offeror shall provide a statement that no foreign nationals will perform work on the resultant contract, if awarded to the Offeror, and that all the work shall be performed in the United States.

viii. Sub-factor 7 - Transition In:

A. The offeror shall provide a detailed description of the proposed transition plan into the new contract. The proposed transition plan shall address the following:

1. Security Assessment and Authorization (SA&A) of the PA’s pension payment system and retiree/employee self-service system.

2. Decommissioning (if applicable) of the incumbent PA’s systems in accordance with NIST standards.

3. Establishing the Interconnection between PBGC and the PA’s primary and backup data centers for the file transmissions.

4. FIPS 140-2 compliant software/hardware for PBGC file transmissions.

5. Interconnection Security Agreement (ISA) between PA’s pension payment system and PBGC’s Benefits Administration System.

PAGE 19 OF 22 16PBGC22R00080001

6. ISA between PA’s retiree/employee self-service system and PBGC’s MyPBA.

B. Data Conversion: The offeror shall provide a detailed description of their capability to conduct the following transition in requirements:

1. Establish accounts for each of the 4,000+ PBGC plans.

2. Establish records for each of the 800,000 PBGC payees.

3. Convert special Fleming/FLEM data.

4. Identify and resolve variance between prior and new PA’s records for each plan and each payee.

C. Software development: Design, develop, test, deploy, the offeror shall provide a detailed description of their capability to conduct the following requirements:

1. Conversion program for Spectrum files (approved payment changes);

2. Conversion program for NFDE files (approved payment changes);

3. Conversion program for Trial Balance Projection;

d. Conversion program for Payment History (payee sub-ledger) files;

4. Conversion program for NOC/ACH return files;

5. Single/Multi report for FOD and;

6. Other reports required by the Section C of the solicitation if automated.

D. Reports: The offeror shall address each of the following reports. If a standard P A report is already available, provide a sample or a detailed description including the data elements on the report:

a. BPD Report

b. ECD Report

c. FOD Report

E. Capabilities to implement PBGC scanners for scanning replacement checks for ACH returns in to IPS (if applicable).

F. Capabilities establishing access to PA’s pension payment system for approximately 500 PBGC users.

G. Capabilities for training PBGC employees on use of PA’s pension payment system.

H. Capabilities for establishing case accounts for PBGC funds

PAGE 20 OF 22 16PBGC22R00080001

I. Capabilities for establishing outside agreements (i.e. Medical and life insurance deductions for certain steel plans, establish interaction between PA and custodian bank as needed).

d. Volume 3 – Factor 3 -- Price Proposal

i. Fee Schedule:

a. The services described within the Performance Work Statement (Section C), Forecasted Quantities Document (Attachment J.2 Volume Requirements) and the offeror’s Written Technical Proposal shall be the basis of the offeror’s proposed fee schedule.

b. The offeror’s fee schedule shall include pricing for all CLINs in the Base Year and each respective option year CLINs identified in Section B and supporting documentation. Further, at a minimum, the Offeror shall clearly identify a Firm Fixed Price for the work required by the solicitation as well as identify the elements of work included within the Firm Fixed Price. The offeror may propose a fee schedule that consist of bundling related elements of work and propose a Firm Fixed Price for each bundle, in which case the proposed fee schedule shall clearly identify the elements of work included within each bundle.

c. “For evaluation purposes only, the total evaluated price is the sum of the total prices submitted for (a) the base period, (b) all option periods, and (c) the six-month extension authorized by FAR clause 52.217-8. For purposes of determining the total price for the six-month extension authorized by FAR 52.217-8, the total price is calculated as one-half of the total price for the final option period of the contract. Accordingly, Offerors must include pricing in their price proposals regarding the exercise of FAR 52.217-8. The agency will include the pricing for 52.217-8 its overall pricing evaluation. Evaluation of the six-month extension option(s) will not obligate the Government to exercise the option(s).”

d. AN OFFEROR’S FAILURE TO PROVIDE PRICING FOR

THE FAR 52.217-8 EXTENSION OF SERVICES CLAUSE

WILL RESULT IN THE OFFEROR’S PROPOSAL OR QUOTE

BEING FOUND EITHER NON-COMPLIANT OR

TECHNICALLY UNACCEPTABLE AND INELIGIBLE FOR

AWARD.”

e. If a fee schedule is provided consisting of bundling related elements of work, the Firm Fixed Price for each bundle should

PAGE 21 OF 22 16PBGC22R00080001

equate a total Firm Fixed Price overall for this effort. Only the overall Firm Fixed Price will be evaluated for this effort.

f. The fee schedule shall clearly identify all exceptions, limitations, and assumptions included within the Firm Fixed Price proposed.

12. ADDITONAL REQUIRMENTS:

a. The offeror shall include the completed representations and certifications contained in Section K of the solicitation.

b. The offeror shall include the signed SF 33SF1449 of the solicitation and the signed SF30(s) for all amendments to the solicitation that may be issued.

c. Offer Validity Statement: Offeror(s) shall make a clear statement in their proposal that the proposal is valid for no less than 180 calendar days from the closing date of the solicitation

PAGE 22 OF 22 16PBGC22R00080001

1.2

C:\PERFORM\FORMS\S30.FRP

Forms Management

C:PERFORMFORMSS30.FRP

Acrobat PDFWriter 2.01 for Windows D:19971010095222 D:19990614133004 Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER

3. EFFECTIVE DATE

4. REQUISITION/PURCHASE REQUISITION NUMBER

5. PROJECT NUMBER (If applicable)

7. ADMINISTERED BY (If other than Item 6)

CODE

STANDARD FORM 30 (REV. 11/2016) Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended.

is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority) Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY

CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer) Previous edition unusable

PROCUREMENT DEPARTMENT

445 12th St. SW

WASHINGTON DC 20024-2101