Attachment H - Order 1 PWS.pdf

RFP-CIO-30100000-23-001

TASK ORDER 1

PERFORMANCE WORK STATEMENT

MAINFRAME CLOUD TRANSITION SERVICES AND SUPPORT

1.0 SCOPE OF WORK

Under this Task Order, the Contractor shall provide Kick-Off Meeting, Weekly Status, and Project Plan and Schedule, (2.1.1), Transition Plan (2.1.1), Set-Up and Transition Services (2.1.1), Cloud Environment Hosting (2.1.2 and 2.1.3) Cloud Environment Hosting – Surge (2.1.2 and 2.1.3), Operation Services (2.1.2) as it relates to the specified Base IDIQ PWS Sections.

2.0 PLACE(S) OF PERFORMANCE

The Contractor shall perform the work off-site at their location and, if needed, come on-site at the following Government location with COR approval at the Task Order level:

Metro Center I 6505 Belcrest Road Hyattsville, MD 20782

Third Street Building 200 Third Street Building Parkersburg WV 26101

Avery Street Building 320 Avery Street Parkersburg, WV 26101

Liberty Center Building 401 14th Street, SW Washington, DC 20227

Kansas City Regional Operations Center 4241 NE 34th Street Kansas City, MO 64117

1618 East Woodward Austin, TX 78714

13000 Townsend Road Philadelphia, PA 19154

836 15th Street North Birmingham AL 35203

Travel may also be required to third-party hosting providers at the following locations:

Ashburn, VA East Rutherford, NJ

Austin, TX Minneapolis, MN

Chandler, AZ Omaha, NE

Colorado Springs, CO San Jose, CA

Dallas, TX Washington, DC

Research Triangle Park, NC

3.0 PERIOD OF PERFORMANCE

The anticipated period of performance is as follows to allow for the completion of the initial series of tasks.

However, the Government will consider alternative proposed periods if it provides the best value to the Government:

Base Period: 32 Months from date of award Option Period 1: Months 33 – 45 Option Period 2: Months 46 – 58

4.0 ACQUISITION TYPE

The Government intends to award a Task Order with fixed-priced rates and services.

5.0 TASKS AND DELIVERABLES

Under Task Order 1, the Contractor shall perform the following tasks and provide the corresponding deliverables.

5.1. Kick-Off Meeting, Weekly Status, and Project Plan & Schedule

Prior to the Contractor arriving at the Government’s site, The Contractor and the Government shall conduct five (5) joint conference calls that last sixty (60) minutes per call during the first ten (10) days of the contract. The purpose of these conference calls is for introductions and discussing the Project Plan & Schedule and for reviewing the scope of work, the governance procedures and requirements.

The Contractor shall hold at least one one-hour -weekly conference call with the Government to discuss and update the Project Plan & Schedule. The Contractor should also hold separate bi-weekly through the status of the ATO status meetings with the ISSO and Security personnel. The Contractor shall update the Project Plan & Schedule, within 5 days of an agreed upon verbal change(s) and within 5 days after the conclusion of each month during the life of the order. The Project Plan & Schedule shall include the following:

a. Project timeline, mandatory tasks with task durations, inclusive of who will be accountable for each

b. Project progress for work accomplished in reporting period and project milestones

c. Work to be accomplished in next reporting period

d. Project risks, if any, and anticipated delays

5.2. Transition Plan

The Contractor shall develop and submit an on-premises to cloud mainframe transition plan.

Deliverable: Within two (2) weeks of the Kickoff Meeting (5.1), the Contractor shall develop a transition that identified the actions, plans, personnel, procedures, deliverables, work products, and timelines by functionality necessary to transition from start date to full operational status. The plan shall identify the individuals, inclusive of roles and responsibilities, of those participating on the transition team and shall include, but is not limited to, the following:

a. Essential tasks, work products, and deliverables by phase

b. Personnel roles and responsibilities

c. Documentation/information needed and applicable dates

d. Parallel operations by contactor and incumbent

e. Communications process between the incumbent and new Contractors, Fiscal

Service staff, and other Fiscal Service Contractors (as necessary)

f. Duration of transition activities

5.3. Set-Up and Transition Services

The Contractor shall build an environment that closely mirrors the Fiscal Service mainframe environment and conduct needed activities to transition Fiscal Service applications from using Fiscal Service mainframe services to using cloud mainframe services. Set-up and transition services include:

a. Develop, maintain, and execute a transition plan to target completion by September 15, 2023, but not to exceed November 30, 2023, for transitioning mainframe dependent applications and potential non-mainframe dependent applications from the Fiscal Service platform to the contractor platform.

b. Begin transition activities within thirty (30) days of order award in the mainframe cloud platform.

i. The platform shall comply with all Security Requirements as outlined in Security

Attachments A-D.

c. Establish infrastructure and network connectivity to Fiscal Service (i.e. contractor must provide a Cloudlink Connection from Equinix to the contractor’s site).

d. Provide XRC or similar mainframe mirror technology to transition and cutover from the Fiscal Service Parkersburg, WV data center to the contractor platform.

e. Provide best practices and subject matter expertise (SME) for set up, transition, and cutover activities that can simultaneously support 30+ applications.

f. Support the establishment and annual review of the Fiscal Service Authority To Operate (ATO)

g. Transition Fiscal Service mainframe workloads and associated data to the Cloud hosting environment.

h. Provide three (3) application testing windows to test cloud environment before final cutover.

Testing validation activities shall require full performance testing, inclusive of load testing.

i. Provide one (1) application testing window to validate regional failover capability to secondary site within the 4-hour Return to Operation (RTO) objective before final cutover. Testing validation activities shall require full performance testing, inclusive of load testing.

j. Support environment/application testing and cutover activities during transition.

k. Transition Management areas include, but are not limited to, transition planning, transition infrastructure readiness, testing, and cutover.

l. Cutover shall occur during one or more non-disruptive periods, such as a weekend or a holiday weekend.

Deliverable: All set-up and transition activities shall be completed within 6 – 9 months of award but no later than November 30th, 2023. Preferred transition timeline will complete all transition activities by September 15, 2023. Transition activities shall be completed fully prior to operation services accruing and becoming invoiceable.

For any period that extends or occurs beyond November 30, 2023, for which failure occurs on behalf of the Contractor or the Government to meet the November 30, 2023, transition deadline, this order may be subject to termination in accordance with FAR 52.212-4.

5.4. Cloud Environment Hosting

a. The Contractor shall develop a cloud environment that meets or exceeds the following critical specifications:

i. 2184 MIPS (269 MSUs)

ii. 14 LPARs

iii. 124TB DASD at main site

iv. 324TB DR DASD

v. 400TB VTS; Main and DR site

vi. Infrastructure Recovery Time Objective (RTO): 4 Hours; Recovery Point Objective

(RPO): 5- minute maximum; Uptime: 99.9%

vii. Ability to run approx. 390,000 Batch jobs per Month

viii. 14 Datacom Subsystems

ix. 26 CICS Regions

x. 13 DB2 Subsystems

xi. 4 IMS subsystems

xii. 10 MQSeries Queue Managers

xiii. Core Information Technology Service Management (ITSM) infrastructure services.

xiv. Network, Storage, Cyber, Mainframe Management including administration, monitoring and console operations.

xv. Security Operations Center (SOC)

xvi. Transition /Migration services to migrate existing workload into the contractor’s environment

xvii. 24x7x365 (24x7x366 in leap years) US Citizen based support only - to include clearance requirements for admins (Public Trust, Secret)

xviii. Support 30+ mainframe systems at a platform as a service (PAAS) model

xix. Full IBM MLC Software

xx. Pervasive Encryption for system Z

xxi. z Operating System (zOS) version 2.5

xxii. Mainframe hardware IBM z15

b. Upon delivery of the cloud environment as described in in section 5.4a. of this PWS, the contractor shall host the Fiscal Service mainframe systems within it.

c. The Fiscal Service anticipates capacity demand to decrease over the life of the contract. Over the Period of Performance, a decreased quantity of the specifications identified in 5.4a. is likely.

d. The Contractor shall provide a service response and resolution that meets or exceeds the following minimum response levels:

i. Critical (No work can be accomplished or a function that is vital to the organization’s mission is impaired) – 2 hours or less

ii. High (Ability to do major work functions is completely impaired) – 4 hours or less

iii. Medium – (Ability to do some functions is completely impaired.) – 24 hours or less

iv. Low – (Ability to work is slightly impaired) – 40 hours or less

5.5. Cloud Environment Hosting - Surge

a. The Contractor shall provide surge support within the hosted cloud environment. Surge services are occasionally required when mainframe capacity needs to scale up to meet peak performance and then retract to normal, pre-surge capacity. The contractor shall react same-day to unexpected business demands by increasing resources in the cloud environment for short periods of time to execute these demands with the expectation to return to pre-surge levels upon completion of surge activities. The hosted cloud environment shall meet or exceed the specifications as described in section 5.4. Surge prices shall be coordinated with Fiscal Service in alignment with section 5.6u cost model. Surge cost shall only begin if Fiscal Service exceeds the expected operations window on the base hosting requirements.

5.6. Operation Services

At the completion of Transition Services, the contractor shall maintain the cloud mainframe utilizing Platform as a Service (PaaS) for the transitioned Fiscal Service applications and General Support System (GSS). Includes, but is not limited to the following:

a. Operations- Incident management, system operations, batch job scheduling, batch monitoring and restart, and application library maintenance.

b. Operating System Support- Installs, upgrades, maintaining operating system host network IP addressing and routing configurations, and maintaining Hardware Management Console (HMC) network IP addressing and routing configurations.

c. Software Maintenance and Currency- Reviewing base and ISV products to identify support end dates and any new availability dates, upgrading supported software, maintaining an inventory of key expiration dates, and providing a maintenance schedule.

d. Performance and Capacity Management- Workload Manager service classes, reporting classes and performance goals. Activities include, but are not limited to, maintaining WLM definitions, maintaining SMF/RMF data collection and configurations, generating trending reports, providing recommendations to improve workload performance, providing recommendations for future resource requirements, and determining problems.

e. Storage Management- Dataset management, storage environments, storage replication management, backups/restores, and media and tape media management.

f. Network- GBS, SMBDI Connectivity, OSA Card, LAN switches, WAN routers, WAN circuits, Network channel extenders, and Network within the contractor’s Datacenter.

g. Hardware and Software Management

i. Device or software (HMC) upgrades.

h. Change Management

i. Activities that the contractor will perform on base or approved software.

ii. Coordination and support with Fiscal Service for application management activities including non-business day or after-hours troubleshooting / upgrades / releases.

iii. All system changes and planned outages shall be coordinated and approved by Fiscal Service and coordinated to occur during non-disruptive periods.

i. Problem Management

i. Open, track, close, root cause analysis of any problems associated with the hardware, base offering, or the approved ISV software. Problem management includes troubleshooting and root cause analysis of application incidents.

j. CICS, DB2, IMD, and MO

i. Specific roles for CICS, DB2, IMS, and MQ

k. Disaster Recovery- Work in conjunction with Fiscal Service to develop a disaster recovery plan, testing plan execution, and assessing disaster recovery activities to ensure four (4) hours return to operation (RTO) with regional failover. Contractor shall support at least two (2) regional failover Disaster Recovery tests annually for every hosted application. The two failovers will encompass all applications. Disaster Recovery Exercise shall require full performance testing inclusive of load testing. These activities shall occur during non-disruptive periods such as weekends or holidays.

l. Logging- Produce real time, comprehensive logs to Fiscal Service.

m. Asset tagging shall comply with Fiscal Service Standards.

n. Priority ticketing and problem/incident resolution (at or near real time).

o. Minimum Service Response Levels:

i. Critical (No work can be accomplished or a function that is vital to the organization’s mission is impaired) – 2 hours or less

ii. High (Ability to do major work functions is completely impaired) – 4 hours or less

iii. Medium – (Ability to do some functions is completely impaired.) – 24 hours or less

iv. Low – (Ability to work is slightly impaired) – 40 hours or less

p. Participation in testing activities include but not limited to application release testing, upgrade testing, indecent resolution testing, and disaster recovery tests. Testing and release activities shall include weekend and holiday testing. Contractors shall be available 24/7/365 (24/7/366 in leap years) to support testing and incident resolution.

q. Actively seek process and efficiency improvements.

r. Perform management within an encryption key manager.

s. Surge Services – ability to increase cloud environment capacity as needed (e.g., MIPS

Storage, DR Storage, Virtual Tape Library, and Memory). Occasionally, mainframe capacity may need to scale up to meet peak performance and then retract to pre-surge operating capacity.

t. React quickly (same day) to unexpected business demands by increasing resources in the cloud environment for short periods of time to execute these demands with the expectation to return to pre-surge levels upon completion of surge activities. Surge activities shall be approved with Fiscal Service.

u. Additional Cloud Hosting Services are not included in this Order, however the cloud environment developed shall be flexible to expand to x86 RHEL and Windows workloads within short notice, less than 30 days.

v. Align hosting cost to consumption. Provide cost model for monthly hosting charges based on 2.1.3 hosting requirements. Cost model shall provide scalability (e.g., if MIPS reduce from 2184 to 1500, etc.). Hosting cost model shall include MIPS Storage, DR Storage, Virtual Tape Library, LPARS, and Memory and each shall be consumption based. A cost model shall include a base cost plus a consumption-based rate. Additionally cost model shall include a fixed consumption rate based upon requirements in section 5.4 with a window of minimum and maximum consumption change before resulting in a price variable. Any excess charges beyond the base consumption rate must be coordinated and approved by Fiscal Service.

i. In the Option years, contractor shall provide options periods with the ability to scale down cost at 50% and 25% capacity as well as with maintained capacity.

w. Contractor shall complete the Roles and Responsibilities Attachment.

Deliverable: The contractor shall conduct all activities as described in section 5.6 and meet

Service Level Agreements. Contractor shall submit monthly Service Level Agreement statistics.

6.0 ADDITIONAL KEY PERSONNEL QUALIFICATIONS

6.1 Personnel shall meet the minimum requirements established in the base IDIQ.

6.2 Identification of Key Personnel

For the purpose of this Task order, the approved Contractor key personnel are TBD.

7.0 QUALITY CONTROL PLAN (QCP)

The Contractor shall establish a complete internal QCP for this Task Order that includes methods for monitoring, identifying, and correcting deficiencies for each performance category. The QCP shall be maintained by the Contractor for them to ensure the requirements of the BPA Order are met as specified in the Quality Assurance Surveillance Plan (QASP). The Contractor shall report any performance issues that they found immediately to the COR for discussing remediation options.

8.0 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

The Government shall evaluate the Contractor's performance in accordance with this Quality Assurance Surveillance Plan (QASP) identified herein. The purpose of the QASP is to ensure reliable, uninterrupted services are provided in accordance with the PWS. This plan shall also ensure acceptable performance and assist in avoiding unnecessary mistakes and/or delays.

8.1 Performance Categories & Standards. The COR shall summarize and document the Contractor's service and delivery performance utilizing the following categories and standards:

a. Quality of Service - Tasks and Deliverables were 100% completed within the expectation of the Government by the Contractor

b. Schedule/Timeliness - Tasks and Deliverables were 99% completed within the agreed upon schedule and specified periods of performance.

c. Cost Control (if labor hour contract) - Cost were 99% managed effectively and within budget and/or cost overruns were properly justified and notified in a timely manner.

d. Business Relations - customer service/interactions was 99% responsive and professional.

e. Management of Key Personnel &/or Subcontractors - Contractor management of key personnel and subcontractors was 99% effective in successfully performing the tasks of the contract/order.

f. If applicable, utilization of Small Businesses (if an other-than-small business contractor and contract > $650k) - Contractor provided the maximum practicable opportunity for Small Business (including Alaska Native Corporations (ANCs) and Indian Tribes) (including Small Disadvantaged Businesses (which also includes ANCs and Indian Tribes), Women Owned Small Businesses, Economically Disadvantaged Women Owned Small Business, HUBZone, Veteran Owned, Service Disabled Veteran Owned Small Business, and ANCs and Indian Tribes that are not Small Disadvantaged Businesses or Small Businesses) to participate in contract/order performance consistent with 100% efficient performance of the contract/order and the small business reports were timely and accurate.

8.2 Surveillance method. Random Evaluation. This method employs a “spot check” style of evaluation and may be adjusted based on quality trends. The Government retains the right to inspect all requirements of the contract.

8.3 Incentive/Disincentive

a. Incentive - If Contractor performs the tasks and deliverables in accordance with performance standards then they shall be rated satisfactory. If they provided extra tangible benefits beyond the contract, then they shall be rated very good or exceptional and favorable comments shall be documented in the Contractor’s Past Performance.

b. Disincentive - If the Contractor does not perform the tasks and deliverables in accordance with the performance standards, then lower ratings (Marginal, Unsatisfactory) along with unfavorable comments shall be documented on Contractor’s Past Performance.

8.4 Performance Issues. If the Government evaluations identify unacceptable performance in any of the above categories, the COR shall record it and notify the Contractor and Administrative Contracting Officer within three (3) business days. The Contractor shall initial the observation, however, initialing of the observation does not constitute concurrence with the observation; it only indicates acknowledgement that the Contractor has been made aware of a potential performance issue(s). The Contractor shall meet the Government for developing and implementing a plan to correct any performance issue(s) at no additional cost to the Government. If the Contractor does not agree with correcting the unacceptable performance issue(s) within the time specified by the Government, then the COR shall notify the Contracting Officer who shall take the appropriate administrative action for unacceptable performance.

9.0 SECURITY REQUIREMENTS

The Contractor and/or Contractor personnel performing services under this order shall comply with all of the security requirements listed in Attachments A – D (Security Requirements).