Laserfiche WebLink
Exhibit A Scope of Work — Graviton Consuitant Agreement <br />4.4.1.1 Change Log <br />From the start of the project, team members will capture changes and their anticipated impact on City <br />stakeholders in a change log. For all changes documented in the Change Log, the project team will <br />include recommended actions. The changes included in the change log will also serve as the foundation <br />upon which department readiness workplans will be developed and monitored. Graviton will leverage <br />Smartsheet for the change log. The specific use of Smartsheet for the purpose of recording and <br />managing changes will be determined by the City and Graviton project managers and will be <br />documented in the Project Management Plan and Change Management Plan deliverables. <br />4.4.1.2 Communications Authoring <br />Graviton will develop video communications using Adobe Captivate as the authoring <br />tool. The specific use of Adobe Captivate for developing communications will be <br />determined by the City and Graviton project team members and will be documented in <br />the Communications Plan deliverable. Adobe Captivate will be administered by <br />Graviton project team members though completion of the Project Closeout <br />deliverable. <br />4.4.1.3 Department Work Plans <br />Department readiness encourages City departments to become fully engaged with the Oracle Cloud <br />project, complete specific tasks and activities required for implementation, and assess departmental <br />readiness for go -live. Department work plans will be developed as part of the department readiness <br />activities. Department work plans identify, document, and provide specific engagement and completion <br />activities for the departments to address to be ready to use and adopt the new Oracle Cloud system and <br />related business processes. Graviton will use Smartsheet as the standard tool for establishing and <br />monitoring department work plans. The departments themselves will be responsible for recording the <br />status of their departmental tasks in the work plans. <br />4.4.1.4 Operations RASCI Chart <br />The purpose of the Operations Transition Plan will be to provide the City with detailed <br />recommendations for post implementation operations and maintenance support. A critical component <br />of the Operations Transition Plan is identifying City staff who will fill the operations and maintenance <br />roles. The Operations Transition Plan will include operational roles and responsibilities listed as a RASCI <br />(Responsible, Accountable, Supports, Consulted, Informed) chart. This RASCI chart will provide detailed <br />direction regarding "who does what" for supporting the Oracle Cloud applications after implementation. <br />The RASCI chart will be drafted during the build stage, maintained throughout implementation, and then <br />finalized with the City's transition to operations and maintenance. <br />��`� 5$ LGRavi-rQr� <br />�� r..o NSi�Lrir� � SE�V�CtS <br />