Attachment+#4+Statement+of+Work.docx

ATTACHMENT 4

EXHIBIT A: Phase One– Statement of Work Below are deliverables that STATE expects to be produced as part of this work effort for the implementation of the proposed solution. Descriptions, expectations of STATE and CONTRACTOR, and Acceptance Criteria have been included to the best of STATE’S knowledge. For the purposes of this RFP, CONTRACTOR is expected to review and include any comments on these proposed deliverables.

Note that in this current draft of Exhibit A, STATE is responsible for producing Deliverables 1, 2, 22, and 23, as they are project management deliverables required for this project. CONTRACTOR will be expected to review and agree to CONTRACTOR role and expectations for these deliverables.

CONTRACTOR shall include the additional deliverables for the implementation they anticipate providing STATE. A section has been provided below for CONTRACTOR to add information on these deliverables.

deliverable 1: project kickoff meeting Description CONTRACTOR shall coordinate with STATE to schedule a Kickoff Meeting virtually via STATE’s Microsoft Teams site, or in Bismarck, ND, with the core project and planning team. CONTRACTOR’s Project Manager shall lead the meeting. The Kickoff Meeting must facilitate the introduction of CONTRACTOR and STATE core project team members, and level-set understanding and awareness of project objectives, scope, governance, schedule, and project risks and issues.

Expectations of CONTRACTOR CONTRACTOR shall provide content to STATE for a detailed agenda in advance of the meeting.

CONTRACTOR and STATE shall facilitate the meeting, and discuss and further define, at a minimum, the following:

Effective project communication Project vision, background, purpose, and objectives Project governance structure, and project roles and responsibilities Approach to creating the Project Plan Initial risk assessment Expectations of STATE STATE shall finalize agenda and send agenda to invitees.

STATE shall coordinate the logistics and co-facilitate the Kickoff Meeting.

STATE’s Project Sponsor and project team members shall participate in the Kickoff Meeting.

Acceptance Criteria For the acceptance of this deliverable to occur, the Kickoff Meeting results in:

Facilitation of Kickoff Meeting using a clearly defined agenda An introduction of critical CONTRACTOR and STATE resources assigned to the project Review of STATE’s Project Charter to include project governance structure, roles and responsibilities, project purpose, objectives, and scope Discussion of communications approach and structure Discussion of known project risks and issues Completion Date CONTRACTOR shall start work with STATE within five (5) business days after the signing of this Contract to schedule the Kickoff Meeting.

deliverable 2: Project plan Description CONTRACTOR shall participate, contribute, and collaborate with STATE, led by STATE’s Project Manager, to develop a baseline Project Plan. The Project Plan will include the project schedule.

Expectations of CONTRACTOR CONTRACTOR shall participate, contribute, and collaborate with STATE to provide requested content for the Project Plan. Typical sections CONTRACTOR may be asked to contribute to are as follows:

Management plans to control cost, schedule, scope, and quality Governance structure for the project Roles and responsibilities of the project team Communication management Quality management Risk, issue, and action item management CONTRACTOR shall provide CONTRACTOR tasks and participate and collaborate with STATE on a detailed project schedule created in Microsoft Project. The project schedule will follow STATE best practices as defined in the ND PMO Scheduling Best Practices, including:

Project has appropriate start date.

Project has appropriate Work Breakdown Structure.

All project tasks have appropriate predecessors and successors, with the exception of summary tasks.

All project tasks are auto-scheduled using predecessors to drive the task dates (dates are not manually entered).

No use of constraints.

Both STATE and CONTRACTOR tasks are included.

Project tasks are broken down into timeframes that can be reasonably managed – STATE encourages a maximum task length of approximately 80 hours/two (2) weeks.

Project tasks have appropriate resources assigned with appropriate and reasonable allocation.

Schedule has appropriate working times and incorporates STATE and CONTRACTOR holidays and nonworking times.

CONTRACTOR shall provide written confirmation from an authorized individual confirming contents of the Project Plan.

Expectations of STATE STATE shall lead the project planning effort.

STATE’s Project Manager shall be responsible for the Project Plan.

The Project Plan shall follow STATE template and best practices.

STATE’s Project Manager shall incorporate STATE tasks into the project schedule.

STATE shall obtain written confirmation from an authorized individual at CONTRACTOR for the contents of the Project Plan.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

CONTRACTOR shall provide requested content to STATE for the Project Plan regarding all services, tasks, and products delivered by CONTRACTOR.

CONTRACTOR and STATE agree upon the baselines, scope, schedule, and management plans for the project.

The Project Plan shall adhere to STATE template and STATE project management best practices.

The Project Plan must be presented to STATE’s Oversight Committee for approval on any recommendations.

Completion Date CONTRACTOR shall start work with STATE within five (5) business days after signing of this Contract to create the Project Plan.

deliverable 3: business process improvements Description CONTRACTOR shall provide detailed report documenting improvement opportunities.

Expectations of CONTRACTOR Using the information gathered during the Current State Business Process analysis, CONTRACTOR shall identify potential improvement opportunities for processes for evaluation by STATE.

Expectations of STATE STATE shall provide additional information or details to assist CONTRACTOR in identifying improvements.

STATE shall not try to influence CONTRACTOR in identification, prioritization, or documentation of improvements.

Acceptance Criteria For the acceptance of this deliverable to occur, the Business Process Improvements deliverable must include:

List of prioritized business process improvements Supporting documentation, including rationale deliverable 4: future state business process model Description CONTRACTOR shall provide future state business process maps and supporting documentation. STATE may use the Future State Business Process Model to provide information to a prospective vendor, staff member, or project team member to understand business targets and identify potential opportunities for improvements.

Expectations of CONTRACTOR CONTRACTOR shall lead the business process modeling effort.

CONTRACTOR shall conduct interviews with key STATE personnel and collaborate with STATE to identify and document mutually agreed-upon future state business processes.

CONTRACTOR shall use CONTRACTOR’s standard business process modeling processes and best practices.

CONTRACTOR shall document models using business process modeling tools and formats that can be utilized and accessed by STATE post-project.

Expectations of STATE STATE shall actively participate in interviews and analysis sessions.

STATE shall collaborate with CONTRACTOR to produce and confirm future state workflows.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Process maps include process flow diagrams and documentation of resources used to execute the process, which can be easily understood and confirmed by STATE.

Process maps include all agreed-upon STATE business processes.

Process maps and supporting documentation are delivered electronically to STATE.

STATE can independently access and edit process maps and supporting documentation.

deliverable 5: requirements package Description CONTRACTOR to collaborate with STATE to document, categorize, and prioritize requirements. STATE may use the requirements to provide information to a prospective vendor, staff member, or project team member to understand system needs and provide a system solution.

Expectations of CONTRACTOR CONTRACTOR shall lead the requirements effort and elicit the business rules and requirements.

CONTRACTOR shall conduct interviews with key STATE personnel, collaborate with STATE, consider current and future state, conduct and use any external research, and use business analysis best practices to identify and document STATE business rules and requirements.

CONTRACTOR shall document requirements in a manner that can be used in a future request for proposal.

CONTRACTOR shall collaborate with STATE to write business/stakeholder requirements, functional requirements, and technical requirements, and to define and document these categories.

CONTRACTOR shall collaborate with STATE to define requirement priority levels and document the priority level for each requirement.

Expectations of STATE STATE shall actively participate in requirements elicitation activities.

STATE shall collaborate with CONTRACTOR to produce and confirm requirements.

STATE shall make timely decisions regarding requirements and prioritization.

Acceptance Criteria For the acceptance of this deliverable to occur, the Requirements Package must include:

Business rules Requirements documented, categorized, and prioritized in a matrix format that can be independently accessed and edited by STATE, and electronically inserted into a request for proposal Requirements written according to business analysis best practices to be clear, concise, complete, consistent, testable, and traceable Supporting documentation Requirements that can be used by STATE to obtain solution that meets STATE’s needs deliverable 6: gap analysis Description CONTRACTOR to review, analyze, and confirm understanding of system functionality, business practices, interfaces, configurations, and customizations.

Expectations of CONTRACTOR CONTRACTOR shall lead the analysis effort.

CONTRACTOR shall demonstrate how system’s core functionality meets the requirements as defined in the Request for Proposal.

CONTRACTOR shall identify and document gaps between the system’s out-of-the-box functionality and STATE’s requirements, and business processes and practices.

CONTRACTOR shall identify any gaps that require system configuration or customization changes.

CONTRACTOR shall identify any gaps that require system customization beyond the Request for Proposal response.

CONTRACTOR shall collaborate with STATE to document agreed-upon changes to the system that may be needed as a result of the review and confirmed understanding.

Expectations of STATE STATE staff shall actively participate in work and analysis sessions.

STATE shall collaborate with CONTRACTOR to confirm requirements and gap analysis.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Gap analysis to be presented in a matrix that lists requirements and identifies which requirements can be met out-of-the-box, which need configuration, and which need customizations in accordance with CONTRACTOR’s Request for Proposal response.

Gap analysis matrix includes a descriptive statement on how CONTRACTOR will meet each requirement.

Gap analysis matrix identifies which requirements that, through understanding and analysis, cannot be accomplished without additional efforts, including a recommended approach to resolve the gap and CONTRACTOR’s level of effort.

deliverable 7: system configuration Description CONTRACTOR shall configure the system according to the requirements established during the Analysis phase, and decisions made throughout the configuration effort.

Expectations of CONTRACTOR CONTRACTOR shall lead the configuration effort CONTRACTOR shall confirm and reach configuration decisions in collaboration with STATE.

CONTRACTOR shall configure components in alignment with requirements and decisions confirmed or identified in the Gap Analysis deliverable, and demonstrate completed configurations and reporting capabilities to STATE.

Expectations of STATE STATE shall make necessary configuration decisions.

STATE shall provide information and documentation as needed to configure the system.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

System configured according to the specifications and requirements documented in the Gap Analysis deliverable, and according to the information provided by STATE Successful demonstration of the configuration and reporting capabilities deliverable 8: system customization design Description CONTRACTOR shall design the system customizations in alignment with the analysis effort and outlined in the Gap Analysis deliverable.

Expectations of CONTRACTOR CONTRACTOR shall lead the customization design effort.

CONTRACTOR shall develop a high-level conceptual design for the customizations.

CONTRACTOR shall outline the design decisions and development specifications for STATE approval.

Expectations of STATE STATE shall actively participate in design review sessions.

STATE shall provide support and make any necessary design decisions.

STATE shall review and provide feedback to CONTRACTOR.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Proposed system context and workflow to be accomplished with the customizations Documentation of development and how the development meets the requirements outlined in the Gap Analysis deliverable deliverable 9: system customization development and release Description CONTRACTOR shall develop and release the customizations.

Expectations of CONTRACTOR CONTRACTOR shall complete development of the customizations in accordance to the Customization Design deliverable.

CONTRACTOR shall conduct thorough technical testing of the customizations as identified in the Testing Management Plan.

CONTRACTOR shall resolve issues identified with the customizations.

CONTRACTOR shall install and validate the customizations in preparation for user acceptance testing.

Expectations of STATE STATE shall participate in the identification, troubleshooting, and resolution of any development issues.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Release of the customizations to STATE’s user acceptance testing environment Completion of CONTRACTOR’s testing effort and remediation of any testing failures deliverable 10: DATA CONVERSION PLAN Description CONTRACTOR shall collaborate with STATE to create a Data Conversion Plan. The plan is intended to address the overall approach that will be followed for the data conversion effort and will be a subordinate plan to the Implementation Plan deliverable. The plan will define methodology, strategies, required competencies, tools, templates, quality standards, data cleansing, and data discrepancy resolution strategies.

Expectations of CONTRACTOR CONTRACTOR shall lead the data conversion planning effort.

CONTRACTOR shall create a Data Conversion Plan that will outline the approach to convert the agreed-upon data by collaborating with and gathering input from STATE.

CONTRACTOR shall be responsible for the final product.

Expectations of STATE STATE shall actively participate in planning session.

STATE shall provide support and make any necessary decisions.

STATE shall review and provide feedback to CONTRACTOR.

STATE shall work with CONTRACTOR to develop approaches planned for STATE’s data cleansing efforts.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Data conversion methodologies and strategies to be used including a repeatable extract, transform, and load (ETL) process Details regarding the tools and templates to be used Outline of strategies and actions planned to resolve data discrepancies and mapping issues, which may include customizations and data cleansing Outline of the testing approach and methodology, including defined success criteria and quality standards Executive summary deliverable 11: data conversion design Description CONTRACTOR shall design the overall data conversion approach to convert data from the legacy system.

Expectations of CONTRACTOR CONTRACTOR shall lead the data conversion design effort.

CONTRACTOR shall provide all necessary data conversion documentation to STATE.

CONTRACTOR shall provide example conversion files to STATE to assist STATE in generating successful data conversion files.

Expectations of STATE STATE shall assist CONTRACTOR’s review and design of data elements applicable to data conversion.

STATE shall provide necessary and relevant resources to make design decisions.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Proposed system context and workflow to be accomplished with the customizations Documentation of development and how the development meets the requirements outlined in the Gap Analysis deliverable deliverable 12: data conversion validation Description CONTRACTOR and STATE shall validate the data conversion effort by reviewing the data loaded into the user acceptance testing environment and making any fixes to the system or data conversion process to ensure data transfers accurately and completely.

Expectations of CONTRACTOR CONTRACTOR shall initially validate the data conversion into the user acceptance testing environment and resolve any issues prior to STATE data conversion validation efforts Expectations of STATE.

CONTRACTOR shall support STATE’s effort to identify and resolve any issues with the data conversion prior to Go Live.

Expectations of STATE STATE shall test the data conversion into the user acceptance testing environment.

STATE shall identify, document, troubleshoot, and work with CONTRACTOR to resolve any data conversion issues.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Successful upload of accurate and complete data extract from the legacy system to the user acceptance testing environment CONTRACTOR review of STATE-documented user acceptance testing issues and recommendations for file extract changes to remediate issues Subsequent load(s) of STATE-provided revised data extracts to confirm resolution of issues, or documented alternatives to resolution deliverable 13: interface design Description CONTRACTOR shall design the interface from the system to STATE’s internal and external interfaces including the system inventory list, including any configurations or customizations required to support the integration of the interface with the system.

Expectations of CONTRACTOR CONTRACTOR shall lead the interface design effort.

CONTRACTOR shall develop a high-level conceptual design for the interface.

CONTRACTOR shall collaborate with STATE to finalize design.

Expectations of STATE STATE shall review conceptual designs and provide feedback and clarification as requested.

STATE shall provide technical resources and subject matter experts who will assist and collaborate with CONTRACTOR during the design process.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Design documentation for the interface Document detailing any customization to support the integration between the systems deliverable 14: interface development and release Description CONTRACTOR shall build and release the interface with STATE’s internal and external interfaces including the system inventory list, per the requirements defined during analysis and the Interface Design deliverable.

Expectations of CONTRACTOR CONTRACTOR shall complete development of the interface.

CONTRACTOR shall conduct thorough technical testing of the interface as identified in the Testing Management Plan.

CONTRACTOR shall resolve issues identified with the interface.

CONTRACTOR shall install and validate the interface in preparation for user acceptance testing.

Expectations of STATE STATE shall provide technical resources and an environment for testing of the interface.

STATE shall collaborate with CONTRACTOR to validate CONTRACTOR installed interface correctly.

STATE shall validate interface is ready for user acceptance testing.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Release of the interface to STATE’s user acceptance testing environment Completion of CONTRACTOR’s testing effort and remediation of any testing failures deliverable 15: testing management plan Description CONTRACTOR shall create a Testing Management Plan that outlines the overall testing approach for CONTRACTOR and STATE testing.

Expectations of CONTRACTOR CONTRACTOR shall lead the test planning effort.

CONTRACTOR shall assign a resource as a testing coordinator to provide a single point of contact for STATE for testing activities CONTRACTOR shall create a Testing Management Plan with STATE support.

CONTRACTOR shall conduct working session(s) with STATE to review and finalize the Test Management Plan prior to start of testing.

CONTRACTOR shall coordinate with STATE to schedule all testing activities.

CONTRACTOR shall provide tools, existing test cases, user acceptance test case templates, and reporting formats for testing.

CONTRACTOR shall train STATE to conduct user acceptance tests and report results.

CONTRACTOR shall participate, contribute, and collaborate with STATE in development of user acceptance test cases.

Expectations of STATE STATE shall actively participate in planning sessions.

STATE shall provide support and make any necessary decisions.

STATE shall review and provide feedback to CONTRACTOR.

STATE shall be responsible for creating the test scripts for performance and user acceptance testing, with support and guidance of CONTRACTOR.

STATE shall conduct application performance testing on STATE server(s).

STATE shall conduct user acceptance testing.

STATE shall assign a resource as a testing coordinator to facilitate STATE’s testing activities.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Approach containing:

Real-world scenarios STATE testing of anomalies, various browsers and connections, and entry/navigation mistakes Converted data Testing strategy containing:

Agreed-upon high-level testing schedule in accordance with the project schedule Testing assignments and responsibilities Test script creation practices including detail regarding system environments used during testing Method for reporting testing issues and tracking of remediation Statistical reporting strategy for issues and fixes CONTRACTOR support Outline of the approaches and strategies for testing the requirements, federal and state reporting, interfaces, data conversion, and performance User acceptance test case template Testing issues reporting approach containing:

Template for reporting issues Prioritization and severity methodology, including a Service Level Agreement for CONTRACTOR support and fixes Resolution approach Documentation of what priority and severity issues must be fixed before the system moves into production Description of resources for testing, including numbers of testers and necessary skill sets Identification of testing risks Executive summary deliverable 16: acceptance testing Description CONTRACTOR shall support STATE testing efforts, make fixes, and remediate testing issues during STATE’s user acceptance testing and performance testing efforts. STATE’s testing effort will use STATE use cases and allow testers the opportunity to deviate from the “happy path” and discover any system issues.

Expectations of CONTRACTOR CONTRACTOR shall ensure that the system is comprehensively tested, with documented test coverage demonstrating that all critical functionality and at least 85% of configurable components have been validated against product specifications and agreed-upon requirements.

CONTRACTOR shall perform all system and performance testing and demonstrate system functionality prior to commencement of acceptance testing by STATE.

CONTRACTOR shall review and consult on STATE’s test scripts to ensure scripts are accurate and thorough.

CONTRACTOR shall provide template to document testing results.

CONTRACTOR shall provide testing support to identify, troubleshoot, and resolve issues.

CONTRACTOR shall provide technical assistance with testing, verification, and classification of issues.

CONTRACTOR shall correct validated issues based on priorities and severities defined by STATE.

CONTRACTOR shall work with STATE to ensure the development environment is correctly copied into the testing environment and all users have appropriate access.

Expectations of STATE STATE shall provide the testing environment.

STATE shall lead the testing effort and issue resolution process.

STATE shall ensure STATE testing occurs according to the project schedule, and test results and resolutions are documented.

STATE shall create test scripts according to STATE-defined workflows and processes.

STATE shall provide adequate and knowledgeable system users to participate in testing.

STATE shall perform user acceptance testing.

STATE shall perform application performance testing.

STATE shall document any identified issues, assign priority and severity, and provide results to CONTRACTOR for troubleshooting.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Completion of system testing, performance testing, and system functionality demonstration by CONTRACTOR Completion of user acceptance testing and performance testing support by CONTRACTOR STATE has tested anomalies, various browsers and connections, and entry/navigation mistakes STATE was able to test using converted data Resolution of all priority and severity issues STATE and CONTRACTOR agreed must be fixed before system can go into production Testing approach and execution is in alignment with the Testing Management Plan deliverable 17: training management plan Description CONTRACTOR shall create a Training Management Plan. The plan will address training approaches, courses to be delivered, course instructors, overall objectives and competencies, training schedule, evaluation, and required resources.

Expectations of CONTRACTOR CONTRACTOR shall lead the training planning effort.

CONTRACTOR shall create a Training Management Plan with STATE support.

CONTRACTOR shall conduct working session(s) with STATE to review and finalize the Training Management Plan prior to start of training.

CONTRACTOR shall coordinate with STATE to schedule all training activities.

Expectations of STATE STATE shall actively participate in planning sessions.

STATE shall provide support and make any necessary decisions.

STATE shall review and provide feedback to CONTRACTOR.

STATE will define training effectiveness criteria.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Description of training session(s) including the scope of the training (what information will be covered) Inclusion of training required for Acceptance Testing Identification of roles and responsibilities, intended audience, training objectives, and evaluation methods Identification of agreed-upon high-level timing and approach for training Executive summary deliverable 18: training Description CONTRACTOR to conduct end user and administrator system training.

Expectations of CONTRACTOR CONTRACTOR shall provide up-to-date and accurate user manuals, training videos using STATE’s Microsoft Teams site, and any other training materials that can be given to training participants and future STATE staff.

CONTRACTOR shall provide a training syllabus to STATE for review and feedback in advance of the training. Training shall include basic system navigation, real-life scenarios and appropriate focus should be given to the work that STATE does most often.

CONTRACTOR shall provide qualified instructors.

CONTRACTOR shall conduct training sessions at a location and time mutually agreed-upon with STATE.

CONTRACTOR shall make any recorded training sessions and videos immediately available to STATE.

Expectations of STATE STATE shall review and provide feedback on the training syllabus to verify that desired areas are part of the training.

STATE shall make assigned trainees available for the scheduled training sessions.

STATE shall provide training facilities and equipment.

STATE shall develop and conduct survey of training participants to verify training was effective.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Delivery of user manuals and training materials Delivery of training in accordance with the syllabus Recorded session available to STATE on STATE’s Microsoft Teams site STATE survey concludes that CONTRACTOR training was effective and included the appropriate topics and real-life scenarios.

Training approach and execution is in alignment with the Training Management deliverable 19: training (train-the-trainer scenario) Description CONTRACTOR to conduct train-the-trainer and administrator system training. The train-the-trainer training will focus on persons that will ultimately perform training for end users. The administrator training will focus on persons that will act as system administrators.

Expectations of CONTRACTOR CONTRACTOR shall provide up-to-date and accurate user manuals, training videos, and any other training materials that STATE trainers can give to training participants and future STATE staff.

CONTRACTOR shall provide a training syllabus to STATE for review and feedback in advance of the training. Training shall include basic system navigation, real-life scenarios and appropriate focus should be given to the work that STATE does most often.

CONTRACTOR shall provide qualified instructors.

CONTRACTOR shall conduct training sessions at a location and time mutually agreed-upon with STATE.

CONTRACTOR shall make any recorded training sessions and videos immediately available to STATE.

Expectations of STATE STATE shall review and provide feedback on the training syllabus to verify that desired areas are part of the training.

STATE shall make assigned trainees available for the scheduled training sessions.

STATE shall provide training facilities and equipment.

STATE shall develop and conduct survey of training participants to verify training was effective.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Delivery of user manuals and training materials Delivery of train-the-trainer and administrator training in accordance with the syllabus Recorded session available to STATE on STATE’s Microsoft Teams site STATE survey concludes that CONTRACTOR training was effective and included the appropriate topics and real-life scenarios.

Training approach and execution is in alignment with the Training Management Plan deliverable 20: IMPLEMENTATION AND TRANSITION PLAN Description CONTRACTOR shall collaborate with STATE to create an Implementation and Transition Plan to manage the implementation of the product, and also transition the product and work from the project structure to maintenance.

Expectations of CONTRACTOR CONTRACTOR shall lead the planning effort.

CONTRACTOR shall create an Implementation and Transition Plan with STATE support.

CONTRACTOR shall conduct working session(s) with STATE to review and finalize the Implementation and Transition Plan prior to any implementation or transition work.

Expectations of STATE STATE shall actively participate in planning sessions.

STATE shall provide support and make any necessary decisions.

STATE shall review and provide feedback to CONTRACTOR.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Implementation strategy Implementation resources and tasks Implementation entry and exit criteria Implementation contingency plan Transition/business migration strategy Transition resources and tasks Transition entry and exit criteria Transition contingency plan Required system documentation including, but not limited to, the following:

Requirements documents Architectural diagrams Technical design specifications Security role matrix Test script library inclusive of test scripts used for all phases of testing utilized (unit, system, integration, etc.)

Communication plan specific to implementation and transition activities Assumptions and constraints deliverable 21: IMPLEMENTATION Description CONTRACTOR shall support multiple/iterative releases, as needed, to implement the final system.

Expectations of CONTRACTOR CONTRACTOR shall collaborate with STATE to determine the need for multiple/iterative releases to end users.

CONTRACTOR shall collaborate with STATE for implementation preparations.

CONTRACTOR shall make any fixes required in a timely manner to implement the system as approved in the Acceptance Testing deliverable.

CONTRACTOR shall provide technical support to STATE as needed for implementation efforts.

Expectations of STATE STATE shall participate, contribute, and collaborate with CONTRACTOR for implementation preparations.

STATE shall provide the production environment.

STATE shall monitor the implementation and notify CONTRACTOR of any issues.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

CONTRACTOR support during implementation System go-live with no unresolved issues deliverable 22: post-implementation report Description CONTRACTOR shall participate, contribute, and collaborate with STATE, led by STATE’s Project Manager, to provide content for the Post-Implementation Report.

Expectations of CONTRACTOR CONTRACTOR shall have project team members participate in the Post-Implementation Survey.

CONTRACTOR shall participate, contribute, and collaborate with STATE, led by STATE’s Project Manager, to develop a Post-Implementation Report that provides, at a minimum, the following:

Key project metrics related to schedule, cost, scope, and quality Business metrics related to project objectives and measurements as defined in the Project Charter Comprehensive lessons learned valuable to future projects Success stories from the project Results of the Post-Implementation Survey Expectations of STATE STATE shall provide the three (3) and six (6) month measurements (with each project in the program) to determine if a 20% reduction in time was achieved for each of the business functional areas.

STATE shall provide the three (3) and six (6) month measurements (with each project in the program) to determine if an aggregate of 20% decrease in the number of applications and workarounds’ objective was achieved.

STATE’s Project Manager shall be responsible for the final product.

STATE’s Project Manager shall design and conduct the Post-Implementation Survey.

The Post-Implementation Report shall follow STATE template.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

CONTRACTOR shall participate in the Closeout Meeting and provide content to STATE for the Post-Implementation Report CONTRACTOR shall participate in the Post-Implementation Survey and provide content to STATE for the Post-Implementation Report regarding all services, tasks and products delivered by CONTRACTOR:

Key project metrics related to schedule, cost, scope, and quality Business metrics related to project objectives and measurements as defined in the Project Charter Lessons learned from the project Success stories from the project The Post Implementation Report must be presented to STATE’s Oversight Committee for approval on any recommendations.

Deliverable 23: Close Out meeting Description CONTRACTOR shall coordinate with STATE to schedule a Close Out Meeting virtually via STATE’s Microsoft Teams site with the core project team and interested stakeholders. STATE’s Project Manager shall lead the meeting, though CONTRACTOR may be asked to present on certain agenda items. The Close Out Meeting must present a completed Post-Implementation Report and facilitate discussion of the project closeout.

Expectations of CONTRACTOR CONTRACTOR shall provide content to STATE for detailed agenda in advance of the meeting.

CONTRACTOR shall provide STATE any required information for STATE’s Project Manager to present the Post-Implementation Report.

CONTRACTOR shall expand upon the success stories and lessons learned captured from the Post-Implementation Survey, and discuss details related to the lessons learned to provide comprehensive information to future projects.

Expectations of STATE STATE shall finalize and send agenda to invitees.

STATE shall coordinate logistics and facilitate the Post-Implementation Meeting.

STATE shall expand upon the success stories and lessons learned captured from the Post-Implementation Survey and discuss and further document details related to the lessons learned to provide comprehensive information to future projects.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

Completed Program Objectives and Measurements Completion and confirmation of the Post-Implementation Report deliverable Comprehensive lessons learned and success stories valuable to future projects deliverable 24: final acceptance Description Upon completion of all deliverables, and upon mutual agreement of STATE and CONTRACTOR, the project work will be considered complete and retainage paid to CONTRACTOR.

Expectations of CONTRACTOR CONTRACTOR shall address any outstanding issues or completion of deliverables.

Expectations of STATE STATE shall alert CONTRACTOR to any outstanding issues.

Acceptance Criteria For the acceptance of this deliverable to occur, the following criteria must be met:

No outstanding or unfinished deliverables No outstanding project or system issues Acceptance Process Upon completion of a deliverable, the parties shall follow the acceptance process in accordance with this Contract.

Project Deliverable Payment Schedule:

Note. Do not complete this Section. Complete Attachment 2 Cost Proposal.

The following table defines all payment points. After completion of the Project Plan, this table will be amended with all dates filled in.

Project Total Note. Do not complete this section.

The total budget for the project portion of this Contract is $amount.