AgdaPkt 2019-05-20 Joint SA PFA - Laserfiche WebLink

Browse Search

6.F. -Page 71 of 180 Number: F03 Name: Gap Analysis Stage: 2 - Config & Prototypes Track: 2 - Functional Type: Deliverable Description: The D01 Release 1 Prepare Prototype 1 will encompass approximately 20% of the requirements. Environment will be used by the project team to conduct the F03 Gap Analysis work sessions. For each module, a Gap Analysis will beprepared that identifies gaps between the requirements and del i vered functi ona I i ty a nd best practice configurati ons. Where "Gaps" exist, CherryRoad will document the gap and how the gap will be addressed via software configuration, custom report or process change. When appropriate the Gap Analysis will be re -visited prior to each Prototype. Sub-Deliverables/Milestones: There will be a Gap Analysis deliverable for each project phase, resulting in the following sub -deliverables: • F03.1 Gap Analysis - Phase 1 • F03.2 Gap Analysis - Phase 2 • F03.3 Gap Analysis - Phase 3 Format: Microsoft Word, Microsoft Excel Redwood City Role: The City will be responsible for completing the following tasks: • Attend Gap Analysis work sessions • Provide input for deliverable • Review and approve deliverable CherryRoad Role: CherryRoad will be responsible for completing the following tasks: • Facilitate Gap Analysis work sessions,, utilizing the discovery session questionnaires and GFOA workflows as part of background • Prepare and deliver Gap Analysis • Facilitate deliverable review sessions Acceptance Criteria: Prior to conducting the Gap Analysis work sessions, the project management team will designate the schedule, agenda, and attendees for each session. During the sessions, the project team will analyze the Oracle Cloud functionality and its ability to satisfy the corresponding Redwood City requirements. Following the Gap Analysis work sessions, the project team will produce a deliverable document that includes the following: 1. Updated Requirements List 2. Gap List by Functional Area 3. Gap resolution Deliverable/Milestone Assumptions: 1. Gap resolutions are limited to configuration changes, development of new reports/dashboards, or changes to City business processes 2. Any proposed extensions to the application would require analysis of both system and cost impact. All extensions of the application would require agreement by both the City and CherryRoad. Considerations for extensions of the application will not delay approval of the F03 Gap Analysis deliverable EXHIBIT A APPENDIXA DELIVERABLE DEFINITIONS A -A - 10 ATTY/AGR/2019.118/CHERRYROAD ERP IMPLEMENTATION SERVICES REV: 05-13-19 PR Page 63 of 172 178