State_of_Arizona_Amendment_25_Exhibit_I_Advantage_4_Upgrade_-_clean.pdf

CONSULTING SERVICES

STATEMENT OF WORK NO. 1

ADVANTAGE 4 UPGRADE

EXHIBIT I

This Exhibit I – Consulting Services Statement of Work No. 1 (as used herein “Statement of Work” or “SOW 1”) is issued pursuant to the March 12, 2013 Agreement as amended (the “Contract”) between the State of Arizona ("State") and CGI Technologies and Solutions Inc. (“CGI”). This SOW 1 incorporates the terms and conditions of the Contract as if the Contract were fully set forth in the text of this Statement of Work.

This Consulting Services Statement of Work No. 1 is effective as of April 1st, 2022 (“Effective Date”) and will remain in effect through June 30, 2025* unless terminated earlier in accordance with the terms of the Contract.

*Note: This Consulting Services Statement of Work No. 1 is in effect through June 30, 2025 due to the terms for Discretionary Support that extend beyond the Advantage 4 go-live.

1 INTRODUCTION

The State and CGI have agreed to restate and extend our existing long-term agreement to transform and support the State’s CGI Advantage® ERP system comprised of the upgrade Services in this Statement of Work and the long-term support services defined in Exhibit K (Consulting Services Statement of Work No. 2). Upgrading to CGI Advantage® 4 transforms the State’s technical infrastructure and processes, and provides the State a modernized application architecture and user experience (UX). The primary objectives of the upgrade are:

Upgrading to the latest Advantage 4 platform, Modernizing the technical infrastructure and support processes

Tailoring the user experience to State specific user roles to improve usability and enable data driven decisions

Analyzing and implementing select functional enhancements to improve business processes

Establishing a foundation for and executing test automation to transform the State’s long-term support model to improve quality, drive efficiencies, reduce manual testing, and adjust to the new release cadence

Transition the State to out of the box functionality in CGI Advantage by eliminating product customizations while maintaining critical State business capabilities

Establish a backlog inventory for new features and functionality available in Advantage 4 that could be leveraged by the State of Arizona in the future

Establish a State specific Advantage 4 environment to allow the State to have hands-on access to the new system and their data at the beginning of the upgrade to enable more effective education, analysis and design, knowledge transfer, and acceptance of the solution.

2 SOLUTION COMPONENTS

The professional services and activities described in this Section 2 includes the planning, solution foundation, design, configuration, validation, testing, and deployment of Advantage version 4 for HRM, Financials, Performance Budgeting, and Vendor Self Service.

2.1 Advantage Components

CGI will work with the State to upgrade the following Software, as licensed to the State in Exhibit E - Proprietary Software License Agreement:

1. CGI Advantage® Financial Management (“FIN”)

a. Financial Base System, including Annual Comprehensive Financial Reporting

(ACFR)

b. Fixed Asset Management

c. Grant Lifecycle Management

d. 1099 Reporting

e. Procurement Professional (limited use to support Procurement system integration)

f. Vendor Self-Service (“VSS”) (limited use to support Procurement system integration)

g. Inventory Management

h. Travel and Expense Management

i. State Reciprocity

j. Cash Management (inclusive of Debt and Treasury Management Functions)

2. CGI Advantage® Human Resource Management (“HRM”)

a. HRM Employee Self-Service (ESS) (limited use to support Travel and Expense functions)

b. Labor Distribution (limited use to support HRM Integration and Labor Distribution)

3. CGI infoAdvantage® (“infoAdvantage”)

4. CGI Advantage® Insight

5. CGI infoAdvantage® Dashboard

6. CGI infoAdvantage ei360

7. CGI Advantage® Administration

8. CGI Advantage® Connect

9. CGI Advantage® Intelligence

2.2 Customization Disposition

As part of transforming the State to Advantage 4, CGI is committed to migrating designated State’s customizations into the base Advantage product to facilitate a transition to out of the box functionality while maintaining critical State business capabilities. The State and CGI reviewed the customizations to determine how to handle each customization during the upgrade to Advantage 4 and the dispositions are described in Appendices 10.1 (Customization Disposition) of this Statement of Work.

2.3 Tools

In addition to the Software tools included in the Amended and Restated Proprietary Software License Agreement (“PSLA”) and Amended and Restated Proprietary Software Maintenance Agreement (“PSMA”), the following tools will be used:

The State is responsible for purchasing, licensing, and deploying Microsoft PowerBI Pro (“PowerBI”) to support the development of embedded analytics.

Three (3) instance of the CGI TestSavvy test automation tool (“TestSavvy”).

CGI will leverage our proprietary Application Services Optimization Program (“ASOP”) tool, which includes Jira®, Service Desk, Confluence®, and DataPlane for managing and tracking software issues and incidents, meeting notes and action items.

CGI will leverage its existing shared Microsoft SharePoint site (a.k.a. “Ensemble”) for managing project documentation.

CGI will leverage the 360 Eyes tool-set to facilitate the re-pointment of Business Objects reports from the current 3.11 environment to 4.x environments.

3 METHODOLOGY OVERVIEW

CGI and the State will use a hybrid agile methodology for the Advantage 4 upgrade, as illustrated in Figure 3.1 – Methodology Overview.

The Plan and Solution Foundation Phase activities are managed using a traditional waterfall approach.

The Design | Configure | Validate Phase activities are managed using an agile sprint based approach, with the exception of the operational cycle.

Test Phase activities are managed using a traditional waterfall approach, with the exception of integrated system testing (IST) and test automation.

Deploy Phase activities are managed using a traditional waterfall approach.

Figure 3.1 – Methodology Overview

3.1 Plan Phase

The goals of the Plan phase are to educate the project team in product functionality, define in-scope business process changes using the baseline product as a design basis, document the detailed strategies and plans that clearly articulate the project approach, roles and responsibilities, and expectations for the integrated team and prepare for the technical environments.

During this phase, the State and CGI will work collaboratively on refreshing project governance and management processes, refreshing the detailed project schedule, working with CGI’s Advantage Cloud team to confirm the environment plan and configuration management plan, defining the overall project test plan, and supporting the State’s disaster recovery exercises as covered under the existing Managed Advantage Statement of Work 1 (Exhibit C).

3.2 Solution Foundation Phase

The Solution Foundation Phase activities focus on creating an environment with Advantage 4 software with baselined State customizations, and converted State data. In this phase, the integrated CGI and State project team will start with project team training focused on the new navigation and user experience capabilities for user roles, profiles, and extensibilities.

CGI will lead the integrated team through the user experience analysis to define the user experience approach, boundaries, and roles and responsibilities.

For new functionality available in Advantage 4, CGI will work with the State to establish and prioritize a Backlog inventory, as defined in Section 5.2, of new functionality that can be enabled during the upgrade and those that will be deferred. The integrated team will analyze the upgrade impacts to the technical components including security and workflow, interfaces, reports, universes, Extract/Transform/Load (“ETL”), and forms to identify and prioritize changes in the Backlog.

Upgrade impacts that are required to implement Advantage 4 are included in the project scope. New functionality that is not technically required or specifically referenced as included in this Statement of

Work will be deferred for prioritization and implementation as part of the long-term support services defined in Exhibit K (Consulting Services Statement of Work No. 2), unless mutually agreed to be prioritized in the Backlog as part of the Advantage 4 upgrade.

Upgrade impacts identified during the analysis of the user experience and the technical components may require changes to business processes. As this analysis is completed, the CGI team will work with the State to review the existing business process inventory and identify gaps. The State will be responsible for updating the business processes.

3.3 Design | Configure | Validate Phase

The Design | Configure | Validate Phase is focused on configuring and testing the solution components including the user experience, interfaces, forms, reports, operational cycle, and data conversion. The project team will use an agile sprint-based approach to design, configure, and validate the user experience configuration, interface updates and modernization, updates to forms and reports, system testing of baselined customizations, conducting knowledge transfer, and introducing test automation using CGI TestSavvy. Updates to and testing of the operational cycle, mock data conversion.

3.4 Test Phase

The Test phase is focused on the remaining test activities for integrated system testing, User Acceptance Testing (“UAT”), mock conversion and cutover planning and execution, performance testing, and disaster recovery testing.

CGI will collaborate with the State to identify, prioritize, and automate test scripts that help mitigate business risks and establish a foundation of automated test scripts for shakedown testing for new software releases. The test scenarios evaluated may be from shakedown test scripts, integration testing, and/or User Acceptance Test scripts. CGI is responsible for shakedown and system testing focused on the specific customizations that will be baselined. The State is responsible for Integration and UAT with support from CGI.

3.5 Deploy Phase

The Deploy phase is focused on State conducted end-user training, ensuring business readiness for production cutover, conducting final cutover planning, executing production conversion and cutover activities, and deploying the solution to production. CGI will be responsible for all technical environmental readiness activities. After go-live cutover, CGI will provide post-implementation support.

4 IMPLEMENTATION STRATEGY

The implementation strategy is for a single go live timeline beginning April 1, 2022, with a go live scheduled of eighteen (18) months for on or about September 30th, 2023. The initial 6 months (approximate) will be used to merge the State of Arizona Customizations in to the baseline product.

5 UPGRADE IMPLEMENTATION SERVICES

This Statement of Work incorporates a RASCI designation of the respective responsibilities of the State and CGI with respect to the task or activity.

The Definition Key will be used throughout this Statement of Work:

Responsible – Party responsible for accomplishing the task or activity Accountable – Party answerable for the correct and thorough completion of the task or activity Support – Party providing as-needed assistance in completing the task or activity Consulted – Party consulting with the Responsible party in two-way communication Informed – Party kept apprised by Responsible party regarding the task or activity being planned and/or performed in one-way communication Shared – Each party is responsible for significant detailed tasks in order to complete an activity

5.1 Summary Roles and Responsibilities

The Advantage 4 upgrade is a collaborative effort between CGI and the State. The table below summarizes the roles and responsibilities at a high level with an indication of who leads each activity.

Each transformation activity topic is elaborated with more detailed roles and responsibilities in the remaining sections in Section 5 of this Statement of Work.

Section Ref Activity/Task CGI State

5.2 Project Planning and Management Responsible Support

5.3 Organizational Change Management Responsible Responsible

5.4 Technical Architecture Responsible Support

5.5 User Experience** Responsible Support

5.6 Embedded Analytics** Responsible Support

5.7 Application Configuration Support Responsible

5.8 Application Security and Workflows Support Responsible

5.9 Reports, Universes, ETL Shared Shared

5.10 BIRT Forms Responsible Support

5.11 Interface Updates Support Responsible

5.12 Operational Cycle Responsible Support

5.13 Test Automation** Responsible Support

5.14 Integrated System Test Support Responsible

5.15 Performance Testing Responsible Support

5.16 User Acceptance Testing Support Responsible

5.17 Training and Knowledge Transfer Shared Shared

5.18 Disaster Recovery Responsible Responsible

5.19 Mock Conversion and Cutover Responsible Support

Section Ref Activity/Task CGI State

5.20 Post-implementation support Responsible Support

Notes:

** Scope boundaries for CGI’s responsibilities apply and are referenced in the specific section below.

5.2 Project Planning and Management

CGI will provide ongoing project management and coordination to monitor and control the activities related to the Advantage 4 transformation project. Due to the nature of this upgrade, CGI will approach this using a hybrid methodology. Both CGI and the State will be responsible for adhering to the project schedule in order to avoid delays. In the event of a project delay, available options will be reviewed within five (5) business days or as mutually agreed to by the State and CGI Project Managers in order to minimize further delays to the project schedule. If an agreed to resolution cannot be made within the five

(5) business days (or as mutually agreed to by the State and CGI Project Managers), the State and CGI Project Managers will escalate the issue and options to the appropriate executive levels.

The “Master Project Plan” shall include the activities of both CGI and the State and identify the responsible party for each activity. The Master Project Plan will be updated at least twice a month, to be reviewed with the State during the regular scheduled bi-weekly Project Management (“PM”) and Team Lead (“Leads”) meetings. To effectively track progress in the Master Project Plan, the State shall provide updates to the Master Project Plan to CGI, at least twice a month, also to be reviewed during the regular scheduled bi-weekly PM and Leads meetings.

As described in Section 3 – Methodology Overview, the project will be managed using a hybrid agile approach. The detailed tasks and activities that are managed in sprints will be groomed, tracked and managed using the project backlog (“Backlog”). Dashboards and metrics for managing prioritized Backlog items in each sprint will be used to monitor the sprint progress. The Master Project Plan will contain the high-level sprints and will be updated based on the status of the Backlog items planned for the sprint at a summary level. The Backlog provides an opportunity to refine and reprioritize the overall project Backlog items while staying focused on delivering an agreed-to subset of functions/features during each sprint. Items that will be managed in the Backlog are identified throughout Section 5 of this Statement of Work and include:

User experience business roles, home pages, widgets, extensibilities Embedded analytics Business Processes Application security and workflow Report, universe, ETL Forms Interfaces Operational cycle Integrated System Test scripts Test scenario automation candidates

Weekly Management meetings will be conducted by CGI and State Leads to provide effective communication of the project’s progress, review status, project metrics, and decisions, as well as a forum for the identification and discussion of project issues and risks. A separate bi-weekly management meeting will be scheduled held to ensure action items and risks are being actively addressed.

The CGI and State Project Managers will conduct monthly meetings to communicate the overall project progress against the plan to the State’s ERP CAB meeting. Additional support will be provided to State team leadership during other periodic meetings including State CFO, and other applicable meetings. The State is responsible for coordinating any of the above referenced meetings.

CGI will continue to manage project decisions, risks, and issues on both CGI’s Shared/State SharePoint site. Project issues will be uniquely identified, include a severity/priority, projected completion date, and responsible party. Project risks will be uniquely identified, include a severity, probability, potential impact, mitigation steps, and responsible party. This information will also be reported out during the regular scheduled Weekly Leads meetings and included in the Weekly Status Report.

In addition to the usage of the CGI/State’s Shared SharePoint site for risks and issues, CGI will use a set of tools to provide management of the project which will be detailed in the Project Management Plan documents.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Prepare and manage master project plan Responsible Support

Provide State-specific activities for the master project plan Support Responsible

Review project plans Support Responsible

Set Backlog priorities Support Responsible

Manage the Backlog, including sprint planning and sprint meetings (stand-ups, demos, retrospectives)

Responsible Support

Prepare status reports and conduct project team meetings and status meetings

Responsible Support

Facilitate ERP Governance Board meetings Support Responsible

Manage issues and risks Responsible Support

Provide status of the State functional and technical readiness activities Support Responsible

Prepare and conduct functional and technical readiness assessments Responsible Support

5.3 Organizational Change Management

CGI is responsible for leading the Organizational Change Management (“OCM”) activities with the goal of helping the State departments successfully prepare for, accept, and adopt the new Advantage 4 functionality. CGI services include planning and managing organizational change management activities, aligning and engaging sponsors and stakeholders, and change champions, assessing and preparing for change impacts, assessing and preparing for resistance to change and change readiness, and assisting with communication activities.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Plan and Manage

Develop Organizational Change Management & Communications Plan

Responsible Support

Support, review, and approve Organizational Change Management & Communications Plan

Support Responsible

Align and Engage: Sponsors and Stakeholders

Activity/Task CGI State

Identify sponsors and stakeholders and conduct needs assessment Responsible Support

Develop sponsor and stakeholder assessments Responsible Support

Conduct and refine sponsor and stakeholder engagement activities Support Responsible

Align and Engage: Change Champions

Identify Department staff to participate on change champion network and UAT

Support Responsible

Develop Change Champion Network Charter Responsible Support

Conduct change champion monthly meetings, monitor UAT for organizational change impacts, and escalate issues

Responsible Support

Assess and Prepare: Change Impacts

Identify, analyze, and develop Change Impact Analysis Responsible Support

Prepare for change impacts Support Responsible

Monitor, assess, and refine change impact activities Responsible Support

Assess and Prepare: Resistance Management and Change Readiness

Develop resistance management and change readiness approach Responsible Support

Assess, monitor, and refine resistance management and change readiness in Change Readiness and Adoption Tracker

Responsible Support

Prepare and conduct organizational readiness assessments Responsible Support

Translate and Communicate

Develop communication materials Responsible Support

Conduct communications activities Support Responsible

5.4 Technical Architecture

The transformation to Advantage 4 provides the State with a modern architecture that delivers the platform using DevOps, delivers in secure containers, establishes test automation for long term efficiencies, and modernizes other platform tools, integration tools, and data analytics.

The State is already an Advantage Cloud client, and therefore, CGI maintains responsibilities in the technical architecture and provisioning space.

The State will provide appropriate resources to ensure connectivity requirements between State Networks and the new upgraded CGI Cloud environments are configured.

Additionally, any other VPN connectivity required by the State will be the responsibility of the State to coordinate with their third-party vendors, other than connectivity between the State’s procurement system and the CGI Cloud.

CGI is responsible for installing, managing, and updating the Advantage 4 application in all non-production and production environments during the upgrade, which is defined as the “Application Environment”.

As part of transforming the State to Advantage 4, CGI is committed to migrating designated State’s customizations, as identified in Section 10.1 – Customization Disposition, into the base Advantage product to facilitate a transition to out of the box functionality while maintaining critical State business capabilities.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Manage the Infrastructure Environments for the upgrade activities Responsible Informed

Conduct customization analysis and define the approach for eliminating customizations

Responsible Support

Conduct code compares, code merges (including ETL and customizations), data conversion, and regression test prior to making available in a State environment

Responsible Consulted

Acquire and provision Infrastructure Environments for the upgrade activities

Responsible Informed

Document/update the Technical Architecture and Environment Overview

Responsible Informed

Install the Advantage 4 application Responsible Informed

Conduct shakedown testing of the Advantage system Responsible Support

Manage the Application Environments for the upgrade activities Responsible Support

Provide the State with appropriate access to the System Responsible Informed

Establish/update connectivity between State Networks and State third party vendors for connections to the CGI Cloud environments

Support Responsible

Establish/update connectivity between the State’s procurement system vendor and the CGI Cloud

Responsible Support

Update the Operation Framework document that defines escalation and callout procedures, roles and responsibilities, and designated points of contact for the State and CGI

Responsible Support

Document the Technical Readiness Checklist and Technical Cutover Plan

Responsible Support

5.5 User Experience

A major component of the State’s ERP program transformation is the modernized, flexible, extensible, and mobile ready user experience that brings the right data into the business process for data driven decisions. Advantage 4 provides extensive capabilities for tailoring the user experience based on a user’s role in the organization and their business processes.

During the Solution Foundation phase for each program work stream, CGI will facilitate user experience analysis sessions to guide the integrated project team in assessing the business roles and processes to align the objectives, approach, boundaries, and expectations for the transformed user experience. The goal is to streamline the user experience, make the processes more efficient, and present relevant data to the user at the right time to drive efficiencies and make data driven decisions. The resulting analysis will be documented in the User Experience Plan Deliverable.

The planning and analysis starts with Knowledge Transfer (“KT”) sessions to provide the business leads and project team members an understanding of the various concepts and capabilities for configuring the user experience. The team will begin by formulating the initial list of roles.

For each role, the team will analyze key business processes, identify opportunities for process improvement that can be achieved through user experience configurations, evaluate how data is used during the process, and understand where data is sourced. In addition, the integrated team will analyze system usage to cultivate an understanding of how users currently use the system. The analysis will also include developing an understanding of how the existing security and workflow permissions impacts or affects each business role.

With the guidelines established in the User Experience Plan, the integrated team will configure the user experience using an agile sprint-based approach during each work stream. The CGI business team and State business product owners will work together to define, prioritize, build, and validate the user experience from both a State-wide standards perspective as well as by business role; including landing pages, home pages, data analytics, transactional updates, pages, and inquiries. As part of the design process, CGI will capture the business decisions that influenced the design.

With the flexibility provided to tailor the user experience, the team will need to collaboratively prioritize what can be tailored given the time and available resources for the Advantage 4 transformation. The goal is to establish enough of a framework that the State can continue to evolve the user experience over the life of the ERP program long after go-live through the Annual Planning Process and Fixed Capacity Model defined in Exhibit K (Consulting Services Statement of Work No. 2).

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Facilitate the user experience analysis sessions to guide the integrated team in analyzing the business roles, business processes, and system usage

Responsible Support

Conduct Knowledge Transfer sessions to introduce the project team to the Advantage 4 user experience configuration capabilities

Provide draft business roles based on best practices Responsible Support

Gather and analyze system usage data that informs how users are navigating the system, leveraging data, and using reports

Responsible Support

Analyze strawman roles and business processes to identify areas for improvement

Analyze system usage to cultivate an understanding of how users currently use the system and provide feedback

Support Responsible

Analyze business roles in the context of security and workflow and provide feedback

Support Responsible

Document the User Experience Plan Responsible Support

Provide user experience configuration templates Responsible Support

Prioritize user experience activities (including roles, landing pages, home pages, transaction updates, role pages, and inquiries, edits, and file-based extensions) in the Backlog

Support Responsible

Design, configure, and test the user experience configuration, including roles, landing pages, home pages, transaction updates, role pages, and inquiries, edits, and file-based extensions. Document the business decisions that influenced the design.

Responsible Support

Validate the new user experience configuration and provide feedback during each sprint

Provide Knowledge Transfer to the State product owners for maintaining user experience configurations (Note: configuration management of the user experience is part of the Configuration Management Plan)

Responsible Support

Update ‘To Be’ Business Process flows based on planned UX Business Roles

Assumptions:

CGI will configure up to 25 user roles with a unique home page associated with each role (up to 25)

Reviewing the business processes for improvements outside of the user experience configuration is out of scope unless specifically stated otherwise

5.6 Embedded Analytics

Embedded analytics is the visualization of data, created using Microsoft PowerBI, that can be presented as part of the user experience that is critical to support business functions for each user role.

During the user experience analysis sessions described in Section 5.5, the integrated team will identify opportunities for data analytic visualizations. In the Build phase, CGI will build a subset of in-scope analytics as part of Knowledge Transfer to provide examples to help the State learn how to create the analytics. The State will build any remaining prioritized analytics. Once the analytics are tested, CGI will embed the analytics on the designated pages.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Facilitate the user experience analysis sessions to identify opportunities for visual data analytics

Responsible Support

Analyze business processes and supporting data for each user role to define requirements for data visualization and the resulting actionable tasks

Shared Shared

Define the data analytic requirements Support Responsible

Prioritize data analytic requirements for development in the Backlog Support Responsible

Design, build, and test in-scope analytics (see assumptions) based on the prioritized Backlog

Responsible Support

Design, build, and test any additional analytics to be embedded in the user experience based on the prioritized Backlog

Support Responsible

Embed State developed analytics in the user experience Responsible Support

Analyze and resolve incidents related to State built PowerBI analytics Support Responsible

Analyze and resolve incidents related to CGI built PowerBI analytics Responsible Support

Provide Knowledge Transfer for CGI built PowerBI analytics Responsible Support

Migrate the embedded data analytics from non-production to production environment

CGI will build and embed up to 25 analytics The party, either the State or CGI, that builds the analytic is responsible for addressing security assumptions and performance of each analytic.

State is responsible for acquiring and managing the PowerBI Pro licenses and any related infrastructure. State will provide the required PowerBI Pro access such that CGI can complete the scope of services outlined above.

5.7 Application Configuration

The State and CGI will incrementally review and update Advantage application software configurations (“Application Configuration”) required as part of the Advantage 4 upgrade that are not part of the User Experience and Security and Workflow configurations. The State will configure the Advantage ERP software for the CGI recommended and State approved configuration changes that are required based on the prioritized Backlog.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Analyze and document in the Backlog the Advantage 4 upgrade impacts to the Application Configurations

Support Responsible

Conduct Backlog reviews and prioritization Support Responsible

Participate in Backlog reviews and prioritization Support Responsible

Configure and test Application Configurations as prioritized in the Backlog

Support Responsible

Review and validate Application Configuration changes and provide feedback during each sprint

Provide Knowledge Transfer for Application Configuration changes Responsible Support

5.8 Application Security and Workflow

With the Advantage 4 transformation, CGI’s scope for security and workflow will focus on the following areas:

CGI will provide the State with new resource information such that the additions (or removals) from the application can be incorporated into the existing security roles.

CGI will also analyze the consolidation of administrators across Advantage and provide recommendations for the consolidation.

CGI will work with the State to crosswalk and/or capture the business role assignments based on a combination of departmental input and/or logical crosswalk from the users assigned security roles.

The State will be responsible for modifications to security and workflow.

Below is a listing of CGI and State responsibilities.

Analyze State specific security and workflow for upgrade impacts to include in a backlog

Support Responsible

Prioritize security and workflow to be updated in a backlog Support Responsible

Provide support for new application resources (pages, transactions, tables, and inquiries) for security and workflow considerations

Responsible Support

Plan, design, develop, and test security and workflow as required based on prioritized impacts

Support Responsible

Support issue resolution for security and workflow updates Support Responsible

Assignment of Business Roles to Users during User Acceptance Testing and Production

5.9 Reports, Universes, and ETL

CGI will update State infoAdvantage reports and universes to repoint to the new Advantage 4 environment with the upgrade. With the transformation of the user experience in Advantage 4, some reports may not need to be retained. In conjunction with the user experience analysis and with the support of CGI, the State will identify reports that are no longer needed.

For reports that will be carried forward, the State will test the reports.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Provide full inventory of reports to be migrated Support Responsible

Provide comparison of Advantage universes Responsible Support

Upgrade universes with custom changes Responsible Support

Analyze report usage to identify reports where data should be pushed into the user experience and are no longer needed

Support Responsible

Identify impacts to the reports Support Responsible

Prioritize reports to be updated in a backlog Support Responsible

Update reports and universes to repoint to the new non-production environment

Support Responsible

Update and test reports Support Responsible

Analyze and resolve incidents related to the upgrade of the universes, and ETL

Responsible Support

Analyze and resolve incidents related to the upgrade of the reports Support Responsible

Plan, design, development, and test new or modified reports and universes

Informed Responsible

Migrate reports, universes, and ETL from non-production to production

CGI development of new infoAdvantage reports are not included Assumes agreed upon cutoff times during the project implementation for finalizing any updates to the defined reports in scope to be migrated over to the new environments, and no later than three

(3) to six (6) months before the go-live date.

Assumes up to 1,000 existing infoAdvantage reports for re-pointment. As part of the planning and implementation project, the State will provide CGI a listing of the planned 1,000 reports for migration.

Excludes non-Advantage reports

5.10 BIRT Forms

CGI is responsible for the design, updates, and system testing required for the Advantage 4 upgrade to BIRT forms.

The State is responsible for integration and UAT testing the forms. Advantage 4 data set changes and design consideration changes may require updates to the Advantage BIRT forms.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Provide full inventory of forms to be migrated to Advantage 4 Support Responsible

Analyze the upgrade data set changes and design impacts to forms Responsible Support

Prioritize form updates for development in a backlog Support Responsible

Update State specific forms to support upgrade impacts based on the prioritized backlog

Responsible Support

System Test forms Responsible Support

Integration Test/UAT test forms Support Responsible

Plan, design, development, and testing for new or modified forms Responsible Support

Migrate forms from non-production to production environment Responsible Support

New forms are not included Introducing new functionality to existing forms beyond what is required to support the upgrade impacts is not included

5.11 Interface Updates

The State is responsible for any PDI based integrations between State agencies and the Advantage system along with integrations with Third Party systems (for example, Bank). CGI will be responsible for the re-platforming of existing API based integrations with the Advantage 4 system using Advantage Connect.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Advantage inbound / outbound side of interfaces (PDI based)

Provide a full inventory interfaces used with Advantage Support Responsible

Conduct analysis on the existing interfaces to identify updates required for the upgrade

Support Responsible

Validate and prioritize the inventory of interfaces to determine ownership

Support Responsible

Update and test existing Actian DataConnect interfaces Shared Shared

Advantage inbound interfaces (API)

Provide a full inventory interfaces used with Advantage Responsible Support

Conduct analysis on the existing interfaces to identify updates required for the upgrade

Responsible Support

Validate and prioritize the inventory of interfaces to determine ownership

Responsible Support

Develop Advantage Connect Shared Shared

Provide knowledge transfer for Advantage Connect Responsible Support

Support defect resolution for updated interfaces Responsible Support

External or Other State Agency systems side of interfaces

Plan, design, develop, and test interface updates Support Responsible

Support defect resolution for interfaces Support Responsible

Migrate interfaces from non-production to production environment Support Responsible

Real time integrations included in the scope are as follows:

o Encumbrance with iValua system o Budget Check with iValua system o Payment Transaction with iValua system o Vendor Creation with iValua system o Vendor Modification with iValua system o TIN validation with multiple source State systems o Expenditure lookup API for ASET

5.12 Operational Cycle

As in current operations, CGI will be responsible for the establishment of the Operational Cycle in the tool leveraged by the Advantage Cloud team. This setup will occur in both the MA1 and PRD environments in accordance with the project plan. CGI will implement the operational cycle with support from the State on any changes needed.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Analyze the operational cycle, identify areas for improvement, and identify updates required to support Advantage 4

Shared Shared

Prioritize updates to the operational cycle in a backlog Support Responsible

Update the operational cycle in the Advantage Cloud environments (MA1 and PRD)

Test the operational cycle Support Responsible

Resolve issues for operational cycle related to cycle automation software/infrastructure and application software

Responsible Support

Resolve issues for operational cycle related to scripting and integration scripts

Support Responsible

Update operational cycle run-book documentation, as required Responsible Support

Migrate operational cycle from non-production to production

5.13 Test Automation

With the transformation to more frequent releases, test automation is a core capability to support the shift to containers, improve quality, and create efficiencies. CGI will leverage TestSavvy, a proprietary CGI tool developed on top of the Selenium open source platform, to begin building out a repository of automated test scenarios. CGI and the State will collaborate to define the objectives and approach for test automation, as defined in the Automation Test Plan.

The initial goal of test automation is to target scenarios that mitigate risks to the business based on the functional module starting with business processes that are core to the business. During the project lifecycle as the integrated project team identifies State specific test scenarios, the team will log and jointly prioritize the test scenarios that are candidates for automation in the Backlog. CGI will create TestSavvy test scripts based on the available capacity of the CGI test automation technical resources (see Section

5.14 assumptions below).

The State will have access to TestSavvy to create, execute, and support TestSavvy test scripts. The goal for test automation during the Advantage 4 upgrade is to establish a foundation of automated test scripts for shakedown testing of each new Advantage 4 container delivered to the State non-production environment. This foundation of automated tests can continue to be expanded after go-live using the local support services defined in Exhibit K (Consulting Services Statement of Work No. 2).

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Define the test automation objectives, approach and priorities as part of the Functional Test Plan

Responsible Support

Create core business functional test scenarios Responsible Support

Create unique State specific business functional test scenarios Support Responsible

Review and provide feedback on test scenarios Support Responsible

Prioritize test scenarios for automation in a backlog Support Responsible

Create technical test automation scripts for the functional scenarios Responsible Support

Execute test automation scripts based on the test plan Responsible Support

Knowledge Transfer of the Test Savvy Tool Responsible Informed

CGI test automation resource capacity is limited to one full time technical resource.

5.14 Shakedown and System Testing

CGI is responsible for all initial environmental shakedown activities. Shakedown activities include a predefined set of test scripts to execute for each environment to ensure stability before handing off to the State for IST testing or further system testing by CGI.

CGI is responsible for system testing all baseline customizations in the application environment, specifically in the SH1 environment, before the State begins its Integration testing efforts.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Define listing of Shakedown testing inventory Responsible Support

Develop list of System Test scripts and customization testing Responsible Support

Set up System Test Data Responsible Support

Execute Shakedown and System Test scenarios Responsible Support

Document Shakedown and System Test pass/fail test results Responsible Support

Analyze and resolve incidents related to the Advantage upgrade Responsible Support

Not applicable

5.15 Integrated System Testing

The State will review, update, create, and execute test scripts/scenarios for IST to test end to end business scenarios. IST test scenarios will leverage the already created UAT scenarios the State has utilized during the BREAZ project and updated most recently as part of the 3.11 upgrade. The State will leverage any updated business process documentation to then update its inventory.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Document the IST approach as part of the Functional Test Plan Responsible Support

Update or Develop new IST test scenarios for Advantage Support Responsible

Set up IST test data Support Responsible

Execute IST test scenarios Support Responsible

Document IST pass/fail test results Support Responsible

Analyze and resolve incidents related to the Advantage upgrade Responsible Support

Analyze and resolve incidents for non-application components that CGI was responsible for (forms, universes, analytics created by CGI)

Responsible Support

Analyze and resolve incidents for non-application components that State was responsible for (reports, interfaces, analytics by the State)

Excludes non-Advantage test scenarios

5.16 Performance Testing

CGI will plan and execute performance testing of Advantage 4 in the State’s production environment, including targeted infoAdvantage reports.

CGI will execute performance testing on the State’s production infrastructure to simulate expected peak loads to validate that the Advantage Cloud technical architecture will support the expected volumes.

CGI and the State will collaborate to mutually agree on the performance requirements, including expected peak volumes, transaction times, response times and cycle times, which will be documented in the Performance Test Plan.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Develop the Performance Test plan, including test scenarios and target metrics

Responsible Support

Review and provide feedback the Performance Test plan Support Responsible

Provision infrastructure for performance testing (State laptops, applicable access, etc.)

Support Responsible

Install performance test tools on the State infrastructure Responsible Support

Set up the required data to support performance testing Responsible Support

Execute performance test scenarios Responsible Support

Document pass/fail results and provide tuning recommendations Responsible Support

Identify, prioritize, and log incidents Responsible Support

Adjust any State infrastructure to meet the performance requirements Support Responsible

Includes performance testing of up to 10 highest execution time infoAdvantage reports Excludes stress testing Excludes interfaces, forms, ETL, and PowerBI analytics Excludes network traffic CGI will use JMeter for performance load testing State of Arizona will provide desktop, laptop and/or Virtual Machine (“VM”) access on the

State’s network to facilitate execution of the performance test in accordance with State standards used to login to Advantage.

5.17 User Acceptance Test (UAT)

The State already has a test inventory of UAT scripts that was created during the initial implementation and refined and updated during the 3.11.1c upgrade project. These test scripts will be updated to align with any changes to the existing business processes and then executed by the State. Participation of end users outside of the General Accounting Office (GAO) in the UAT is up to the discretion of the State leads and project management team.

CGI will support State staff during UAT in resolving issues found during the testing, as well as efforts associated with retesting.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Develop the User Acceptance Test plan Support Responsible

Collaborate with CGI to define UAT entrance and exit criteria Support Responsible

Update/Develop UAT test scripts/scenarios Support Responsible

Set up the required data to support UAT Support Responsible

Execute UAT test scripts/scenarios Support Responsible

Document results and identify, prioritize, and log incidents Support Responsible

Provide written acceptance based on exit criteria and test results Support Responsible

Analyze and resolve incidents related to the Advantage upgrade Responsible Support

Analyze and resolve incidents for non-application components that CGI was responsible for (forms, universes, analytics created by CGI)

Responsible Support

Analyze and resolve incidents for non-application components that State was responsible for (reports, interfaces, analytics by the State)

5.18 Training and Knowledge Transfer

CGI will provide functional and technical knowledge transfer and sharing during the project as defined in the Project Team Training and Knowledge Transfer Plan, which will address the following areas:

User experience analysis and configuration Advantage 4 navigation Embedded analytics Advantage Connect Test automation (Test Savvy)

The State is responsible for updating training materials and conducting end-user training.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Define the Project Team Training and Knowledge Transfer Plan Responsible Support

Set-up functional and technical knowledge transfer/sharing sessions and share supporting material

Responsible Support

Identify functional and technical attendees for the knowledge transfer/sharing sessions

Informed Responsible

Attend knowledge transfer/sharing sessions Informed Responsible

Plan, design, develop, coordinate, and deliver end-user training with a focus on business process changes and user experience navigation

Informed Responsible

Training for changes in business processes are the responsibility of the State.

Project team training provided by CGI will be focused solely on business roles and navigation.

5.19 Mock Conversion and Cutover

CGI will work with the State to define, plan, test, and execute the Mock Conversion Plan in preparation for the production cutover activities. The Mock Conversion plan is the foundation of the production cutover plan and will be executed twice in non-production environments prior to go live. Additional Mock Conversions may be scheduled if issues are encountered that require a re-conversion effort.

CGI and the State will collaborate to refine the Mock Conversion plan and create the Production Cutover Plan and Script. The purpose of the Production Cutover Plan and Script is to outline detailed roles and responsibilities, methods of communication, detailed schedule, roll-back strategies, milestones, data verification methods, application verification methods, shake-down activities, configuration management method of merging application configuration data for go-live, and cutover entrance and exit criteria. The mock conversion testing validates the conversion processes, data, and timing prior to production cutover.

Below is a listing of CGI and State responsibilities.

Activity/Task CGI State Develop the Mock Conversion Plan Responsible Support

Review and provide feedback on the Mock Conversion Plan Support Responsible

Iteratively update the conversion scripts, as needed Responsible Support

Execute mock conversion test runs Responsible Support

Identify, prioritize, and log incidents Responsible Support

Provide mock conversion test results and retrospective Responsible Support

Coordinate cutover communication review sessions Support Responsible

Develop the Production Cutover Plan and Script Responsible Support

Review and provide feedback on the Production Cutover Plan and Script

Support Responsible

Conduct final cutover Responsible Support

Execute State tasks defined in the Production Cutover Plan and Script as part of final cutover

Conduct final knowledge transfer and ownership to the State Responsible Support

Includes up to two (2) mock conversion runs Excludes non-Advantage data State is responsible for coordinating communication to internal departments and…