Laserfiche WebLink
Exhibit A Scope of Work — Graviton Consultant Agreement <br />8 Oracle Cloud Implementation Acceptance <br />The City will have an opportunity to review and either (a) accept or (b) reject the Services and <br />Deliverables as set forth in this SOW ("Acceptance Process"). If City rejects, the City will provide Graviton <br />with a written description of the rejection. Graviton and the City will review the rejection and agree on a <br />resolution to the rejection. As part of such Acceptance Process, Graviton and City will (a) act reasonably, <br />taking into account the specifications of the Services and (b) not withhold acceptance of Services for <br />minor or insubstantial variations, as agreed to by both parties, to meet specifications unless such <br />variations materially and adversely impact City's use of the Services. City's use of the Services shall not <br />be deemed an Acceptance. City will not owe Graviton any compensation for the correction of Services <br />as part of the Acceptance Process. <br />8.1 Deliverable or Service Acceptance <br />Acceptance by the City is required for all Deliverables identified in this SOW. Graviton shall deliver <br />completed Deliverables for review and approval. Deliverables shall be accepted or rejected within five <br />(5) business days from the time of submittal for acceptance unless mutually agreed to another timeline. <br />The Deliverable Acceptance Process is described below. <br />1) Submission of Deliverables - The Graviton Project Manager, or designee, will prepare a <br />Deliverable Acceptance email and forward with the respective Deliverable to the City Project <br />Manager, or designee, for consideration. <br />2) Assessment of Deliverables -The City representative(s) will determine whether the Deliverable <br />meets the requirements as defined in this SOW, that the Deliverable is complete, and that the <br />Deliverable is free from errors. <br />3) Acceptance / Rejection -After reviewing, the City will either accept the Deliverable (by providing <br />an email reply stating the City approves the deliverable) or will provide a written reason for <br />rejecting it to the Graviton team. If feedback from multiple City representatives is received, then <br />the City Project Manager, or City designee, will consolidate that feedback before delivering it to <br />the Graviton team. <br />4) Correction of Service Deliverables — Graviton will correct in -scope problems found with the <br />service deliverable and will address the correction of out -of -scope changes according to the <br />Change Management Process. Graviton will submit a schedule for making changes to the service <br />deliverable within three (3) business days of receiving a rejected Deliverable Acceptance email. <br />Once Graviton corrects all previously identified in -scope problems, the Deliverable will go <br />through the acceptance process again. The Deliverable will be deemed accepted when City <br />provides an email reply stating the City approves the deliverable. <br />S) Monitoring and Reporting - The Graviton project team will track Deliverable acceptance. <br />Updates on Deliverable acceptance will be discussed in the project management status meeting. <br />Deliverable acceptance issues that cannot be resolved will be elevated to the Project Steering <br />Committee. <br />93 GRAVITQN <br />� � coNsuuwa services <br />