Appendix-2B-Exit-Services.pdf

PDF 159 KB Posted

Attached to
RFP Enterprise Resource Planning Suite and System integrator Services
Solicitation number
RFP 26-00268-AHAC
Issued by
Philadelphia County, Philadelphia City, Pennsylvania

About this file

This document is an Exit Services appendix related to Pennsylvania's RFP for Enterprise Resource Planning Suite and System Integrator Services. The appendix establishes requirements for transition and exit services that the successful vendor must provide at the conclusion of the contract term or upon early termination. The vendor is required to develop and maintain a comprehensive Exit Services Plan that must be submitted within 120 days of contract execution and updated at least annually. Key requirements include full cooperation with the Commonwealth and any successor vendor, transfer of all knowledge and documentation, migration of data in agreed-upon formats, return of all Commonwealth property and data, and continuation of services during the transition period. The vendor must provide personnel with appropriate expertise and knowledge to ensure orderly transition, participate in transition planning meetings, and deliver all documentation including system architecture, operational procedures, and configuration details.

The exit services must be performed at no additional cost beyond the contract price, and the vendor is required to provide up to 12 months of transition assistance if requested by the Commonwealth. The vendor must ensure no service degradation during the transition period and provide access to all systems, software, and documentation necessary for the successor to assume responsibilities. All exit services must comply with security protocols, and the vendor is responsible for ensuring complete data integrity during transfer. The Commonwealth reserves the right to withhold final payment until all exit service obligations are satisfactorily completed and all deliverables are accepted. The vendor must also assign all applicable licenses and provide training to Commonwealth staff or the successor vendor as needed to ensure continuity of operations.

View the file

Other files

Show all 12

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Appendix 2B – Exit Services

Contents

1.0 Introduction

2.0 General Conditions and Requirements

2.1 Conditions and Requirements

2.2 Pre-Transfer Services

2.3 Transfer Services

2.4 Exit Requirements by Expected Services

2.4.1 Planning and Design Phase Exit Requirements

2.4.2 Configuration/Build/Test Phase Exit Requirements

2.4.3 Train/Deploy/Initial Support Phase Exit Requirements

2.4.4 Org. Change Mgmt. (OCM) Exit Requirements

2.5 General Acceptance and Sign-off Requirements

2.6 Post-Transfer Services

3.0 Exit and Transfer Services Responsibilities

1.0 Introduction

This document presents the conditions and requirements for the services to be delivered by the Proposer, upon request of SEPTA, in the event of termination of one or more of the Services by either party (the “Exit”). This document would also apply, as mutually agreed to by both parties, to lengthy suspension of the program, at SEPTA’s request.

This document summarizes the services, requirements, standards and the roles and responsibilities of all parties. Related charges will be specifically identified in a subsequent final contract with the selected Proposer.

2.0 General Conditions and Requirements

The Proposer shall at the time of Exit address at a minimum the requirements and activities set forth in this document and shall prepare a check list to be used by both parties to verify that the applicable criteria have been met.

2.1 Conditions and Requirements

Upon notice from SEPTA, Proposer shall fully co-operate with SEPTA and/or designee and shall promptly take all steps required to assist SEPTA in effecting the transfer of Services from Proposer, as per the final contract.

The term “Exit Plan Project” is used throughout this document to indicate an instance when a Service is being transferred to either SEPTA personnel or a contracted third-party. Proposer shall prepare an Exit Plan that provides the necessary information to facilitate a transfer of the knowledge, tools, documentation, and data from Proposer to SEPTA or to another contracted third-party as directed by SEPTA.

As may be applicable, Proposer shall state, describe and document project and non-project specifics:

Processes and methodologies that Proposer will use to transfer a service to a new contracted third-party Activities that SEPTA will need to plan, schedule and/or initiate prior to the start-up of an

Exit Plan Project, including but not limited to a collaboration model for conducting reviews of configurations, security operations, and similar processes

Conditions that must be completed prior to commencement of an Exit Plan Project Criteria and requirements that must be met by SEPTA prior to the commencement of an

Exit Plan Project Processes and tools to be applied for the necessary knowledge transfer

For each Exit Plan Project, the Proposer shall describe in detail how services will be transferred.

Each plan shall include (but not be limited to):

Access to all contracted services that were in existence the hour before notification of the

Exit and access to Key Personnel throughout the Exit process and until all services and assets are transitioned

A comprehensive checklist that identifies each of the tasks/processes/decisions that will be used by Proposer and SEPTA as a traceability document to ensure each tasks/process/decision is addressed in the Exit Plan and delivered in the Exit Plan Project

Costs to SEPTA shall only be required for additional resources that are required to be added beyond the final contract to execute the Exit Plans. Where other activities can be shed (without degradation of service delivery) to focus on the Exit activities, these costs will be absorbed by the existing or replaced resources

Work with SEPTA to identify the key criteria to measure success of the Exit Plan Project, including any specific performance criteria that will be evaluated by SEPTA prior to acceptance by SEPTA

Prepare a project file in Microsoft Project, or another similarly accessible format, that describes the time scale, dependencies, staffing (Proposer, SEPTA and/or contracted third-party) and similar information required for the withdrawal of the Services from the Proposer

State, describe and document those project specific activities, if any, that SEPTA will need to plan, schedule and/or initiate prior to the start-up of the Exit Plan Project

State, describe, and document those project specific activities, if any, that SEPTA will need to complete prior to the start-up of the Exit Plan Project. For purposes of clarification, this includes, but is not limited to, identifying specialized software, test environments or connectivity that is not a part of the normal level of Services

State, describe and document those project specific activities to achieve full Knowledge Transfer by the end of the Exit Plan Project

State, describe and document those project specific activities to achieve the transfer to a fully configured, fully working environment by the end of the Exit Plan Project

State, describe, and document an estimate of how many SEPTA and/or third-party FTE resources that the Proposer believes will be needed to carry out the Exit Plan Project, along with a description of the skills, knowledge and experience required for each identified role

State, describe, and document a collaboration model for conducting procedure reviews (e.g., configuration, security, operations, etc.) that will occur during the Exit Plan Project

Identify start date of Exit and timing of transfer activities including final end date of transfer

Identify resources, assets and assigned contracts to be transferred to SEPTA (or designee) as set forth below

Proposer training to appropriately skilled SEPTA-designated personnel to perform the Services that are to be transferred

Provide SEPTA or replacement contracted third-party with information regarding the services that are necessary to transfer the Services to either a third party or back to SEPTA, and provide such information regarding the Services as necessary for SEPTA or its designee to assume responsibility for continued performance of the Services in an orderly manner, so as to minimize disruption to the operations of SEPTA, including key support contacts (names and phone numbers) of SEPTA and/or third party personnel, and of the Proposer personnel during the transition

Provide to SEPTA or replacement contracted third-party a complete inventory and documentation on the then current SEPTA environment, technical specifications, and all other materials and user documentation for each item of software that the Proposer is licensed or otherwise authorized to use with effect from the effective date of termination, along with run documentation and job control listings, and other similar information necessary for SEPTA to run such software on and from the date of termination for SEPTA or its replacement Provider

Provide SEPTA or the replacement contracted third-party with all specifications of the project and environment that supports some or all of the then current Services

Provide SEPTA or designee with reasonable access to, and use of, Proposer equipment and software

Provide all information regarding the Services or as otherwise needed for such transfer, including all code and configuration information and documentation prepared and maintained by Proposer, ticket history, data conversion, interface specifications, and related professional services and any other information, data or material as required by

SEPTA

Fully cooperate and assist with due diligence activities by SEPTA or replacement Provider on the Services

SEPTA shall accept and sign-off on the Exit Plan Project prior to commencement of each Exit Plan Project.

The Proposer shall ensure that all other Services are maintained without interruption or impairment during the Services specific to each Exit Plan Project executed in accordance with this document, whether the Exit Plan Project is for one, multiple or all of the Services provided to SEPTA, unless expressly agreed in writing by SEPTA.

2.2 Pre-Transfer Services

Specific pre-transfer assistance to be provided by the Proposer shall include the following:

Assist in the preparation of that portion of the Exit Plan detailing Provider responsibilities, including schedules and resource commitments Provide SEPTA documentation used by the Proposer to provide the Services Assist SEPTA in notifying third party Providers of the procedures to be followed during the transfer Identify and explain naming conventions Cooperate and assist SEPTA with the preparation and testing of transitioning systems, applications, and services

2.3 Transfer Services

Specific transfer assistance to be provided by the Proposer shall include the following:

Work with SEPTA and third-party providers to fully transfer knowledge and assets necessary for the continuation of the services by SEPTA or its third-party providers in conjunction with SEPTA and/or designee, conduct a rehearsal of the Exit prior to cutover at such time as is reasonably acceptable to the Parties

Participate to ensure all documents, software, data and configurations arrive safely from the Proposer to the new workspaces provided

Provide any source code managed by the Provider and ensure arrival at the new source code location

Once all services are transferred and accepted, protect SEPTA data including: removal of all SEPTA data files and other SEPTA Confidential Information from the systems except as the Proposer is required to keep pursuant to the audit and record keeping requirements set out in the Agreement; return all SEPTA data and other SEPTA confidential information to SEPTA; transfer responsibility for off-site tape and document storage; make available any SEPTA Data stored on desktop computers and servers for which the Proposer is responsible, including backup tapes

Deliver all requested SEPTA documents and data files (with content listing) and printouts of control file information to SEPTA

Provide an image copy of SEPTA Data files in dump / restore mode Ensure the integrity and accessibility of all data provided throughout the transfer and Exit processes Participate in the ongoing service delivery to SEPTA to ensure SEPTA’s ongoing full-scale business continuity for a seamless transfer

2.4 Exit Requirements by Expected Services

The following sections describe the specific exit requirements in the event a termination will occur during the execution of any of the following services for any of the rollouts contracted under the Agreement.

2.4.1 Planning and Design Phase Exit Requirements

In addition to that which is applicable above, Proposer will provide all the deliverables for work completed to date. The SEPTA PMO and functional/technical leads will determine the level of work completed to date. The artifacts include but are not limited to the following in the event of an Exit during or after completion of the Planning and Design Services:

Complete up to date global template plan, status, issues log, and risk log Communications plan and roles, as it pertains to global template stakeholders and delivery staff All documents, e.g., requirements, functional specifications, checked in to any applicable document management or configuration management tool Complete and up-to-date inventory of reports, interfaces, conversions, extensions, forms, and workflows Scope for deployment as known, including updates to reflect any changes Data Migration Plan, including data mapping status, data standards identification, data normalization/conversion tools identification, and data governance process definition Requirements traceability matrix as known Business and Technical reference architectures as known Clear documentation of all credentials/authentication configurations as required for

SEPTA security transition Integration architecture as known Current state, gap analysis, target state as known Up-to-date staffing and budget analysis Value Realization Plan

Test plans, as known OCM and training development plans as known Infrastructure status, environment, security, connectivity, site analyses as currently developed End-to-End business functional processes and configurations as presently known documented and placed into applicable configuration management tool Demonstrate a documented transition plan and complete all elements to mutual agreement between Provider and SEPTA before departure

2.4.2 Configuration/Build/Test Phase Exit Requirements

Proposer will provide a set of artifacts that include but are not limited to the following in the event of an Exit during or after completion of the Configuration/Build/Test Services. The SEPTA PMO and functional/technical leads will determine the level of work completed to date.

The full list of documents and components as described in the previous section Complete up to date deployment plan, status and issues Communications plan and execution roles, as it pertains all remaining implementation activities Configuration and specific status by business capability Documentation (i.e., functional and technical specifications) and source code for all development objects created by the Provider – all within the applicable configuration management tool

Clear documentation of all credentials/authentication configurations as required for SEPTA security transition

Tests executed with error logging reviewed; tests yet to executes known and documented;

all included in the applicable testing tool being used

Process changes (business and IT) identified and applicable documentation completed OCM and training plans updated and confirmed Training development and delivery status; “Train-the-Trainer” sessions scheduled Demonstrate a documented transition plan and complete all elements to mutual agreement between Provider and SEPTA before departure Business Leaders / Stakeholder business readiness sign-off

2.4.3 Train/Deploy/Initial Support Phase Exit Requirements

Proposer will provide a set of artifacts that include but are not limited to the following in the event of an Exit during or after completion of the Deploy/Initial Support Services. The SEPTA PMO and functional/technical leads will determine the level of work completed to date.

The full list of documents and components as described in the previous sections Complete up to date deployment plan, status, and issues Configuration and specific cutover status by business capability within each region/site

Tests executed (including post-mock migration testing) with error logging reviewed; tests yet to executes known and documented; all included in the applicable testing tool being used

Cutover and Roll-out plans documented Demonstrate a documented transition plan and complete all elements to mutual agreement between Provider and SEPTA before departure Business Leaders / Stakeholder business readiness sign-off

2.4.4 Org. Change Mgmt. (OCM) Exit Requirements

Proposer will provide a set of artifacts that include, but are not limited to, the following in the event of an Exit during or after completion of the OCM and Training Services. The SEPTA PMO, functional leads, and OCM/Training leads will determine the level of work completed to date.

Training plan and development/delivery roles and work products/artifacts, as they pertain to all remaining implementation activities Process and system change (business and IT) mapping completed or in progress.

System-, process-, and configuration-specific inputs provided to support change impact assessments.

Training development and delivery status, including “Train-the-Trainer” and end user training scheduled/completed System role mapping and security role design completed or in progress.

Business Leaders / Stakeholder business readiness sign-off

2.5 General Acceptance and Sign-off Requirements

Acceptance of each Exit Plan Project will be based on Proposer meeting the criteria set forth in this document and as articulated in each Exit Plan.

During the performance of each Exit Plan Project, Proposer shall be responsible for maintaining all Exit Plan Project documentation including: the Microsoft Project (or similar) plan; Deliverables identified in the Exit Plan and tracking the acceptance/rejection of each Deliverable; and other performance measures set forth in the Exit Plan.

Proposer shall identify any contingencies that could have an impact on its ability to deliver the Services under an Exit Plan Project and shall review such with SEPTA for SEPTA’s approval.

Proposer shall promptly identify any changes during the execution of the Exit Plan that impacts its ability to deliver the Services under the Exit Plan Project in accordance with the approved project schedule.

Upon successful execution and completion of each Exit Plan Project, Proposer shall prepare an acceptance letter for SEPTA’s review and approval. Final payment for each Exit Plan Project will be contingent upon approval of the Services.

2.6 Post-Transfer Services

With respect to the Services that have been terminated under a partial termination and following the completion of the Services specific to the Exit Plan Project, the Proposer shall provide additional assistance as requested by SEPTA to assure continuity of operations.

The Proposer shall return to SEPTA any remaining property in its possession or under its control (or its Subcontractors), including any remaining reports, material, data, information, SEPTA data and other SEPTA Confidential Information that are related to the terminated Services and are not otherwise reasonably required by Proposer to continue to deliver other Services for which the Proposer remains responsible.

For each Exit Plan Project, Provider will present a traceability matrix and exit acceptance plan.

Remove and destroy data requiring destruction per the terms of the agreement after full acceptance.

3.0 Exit and Transfer Services Responsibilities

The following table identifies the underlying roles and responsibilities for Exit Services. An “X” is placed under the party that will be responsible for performing the task.

Table 1. Exit Roles and Responsibilities

Exit Roles and Responsibilities Proposer SEPTA Notify Proposer of full or partial termination X Prepare a check list of the criteria identified in this schedule X Prepare and present Exit Plan X Evaluate Exit Plan X Approve Exit Plan X Execute all Exit Services X Return all SEPTA data X Approve completion of Exit Services X

File details come from the government source that posted it. Updated .