My WebLink
|
Help
|
About
|
Sign Out
OPEN GOV
City of Pleasanton
>
CITY CLERK
>
CONTRACTS
>
O
>
OPEN GOV
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/1/2023 4:37:11 PM
Creation date
12/1/2023 4:36:57 PM
Metadata
Fields
Template:
CONTRACTS
Description Type
Professional Services
Contract Type
New
NAME
OPEN GOV
Contract Record Series
704-05
Munis Contract #
2024407
Contract Expiration
12/31/2023
NOTES
PERMITTED TO USE OPENGOV'S HOSTED SOFTWARE SERVICES AND RECEIVE PROFESSIONAL SERVICES
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
26
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Appendix A:Engagement Charter <br />A-1:Communication and Escalation Procedure <br />Active engagement throughout the implementation process is the foundation of a successful <br />deployment.To help assess progress,address questions,and minimize risk during the course of <br />deployment both parties agree to the following: <br />●Regular communication aligned to the agreed upon project plan and timing. <br />○OpenGov expects our customers to raise questions or concerns as soon as they <br />arise.OpenGov will do the same,in order to be able to address items when known. <br />●Executive involvement <br />○Executives may be called upon to clarify expectations and/or resolve confusion. <br />○Executives may be needed to steer strategic items to maximize the value through <br />the deployment. <br />●Escalation Process: <br />○OpenGov and Customer agree to raise concerns and follow the escalation process, <br />resource responsibility,and documentation in the event an escalation is needed to <br />support issues raised <br />●Identification of an issue impeding deployment progress,outcome or <br />capturing the value proposition,that is not acceptable. <br />●Customer or OpenGov Project Manager summarizes the problem statement <br />and impasse. <br />●Customer and OpenGov Project Managers jointly will outline solution, <br />acceptance or schedule Executive review. <br />●Resolution will be documented and signed off following Executive review. <br />●Phase Sign-Off <br />○OpenGov requests sign-offs at various stages during the implementation of the <br />project.Once the Customer has signed-off,any additional changes requested by <br />Customer on that stage will require a paid change order for additional hours for <br />OpenGov to complete the requested changes. <br />A-2:Change Order Process <br />This SOW and related efforts are based on the information provided and gathered by OpenGov. <br />Customers acknowledge that changes to the scope may require additional effort or time, <br />resulting in additional cost.Any change to scope must be agreed to in writing or email,by both <br />Customer and OpenGov,and documented as such via a: <br />●Change Order -Work that is added to or deleted from the original scope of this SOW. <br />Depending on the magnitude of the change,it may or may not alter the original contract <br />amount or completion date and be paid for by Customer.Changes might include: <br />o Timeline for completion <br />o Sign off process <br />o Cost of change and Invoice timing <br />o Amending the SOW to correct an error. <br />2023 Statement of Work v2.1 <br />9 <br />DocuSign Envelope ID: B15D270E-E3B1-4F57-8C92-589FF8DAFA15DocuSign Envelope ID: 2B2F7267-322F-4A10-85EF-ADB56278A499
The URL can be used to link to this page
Your browser does not support the video tag.