My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
R2020-162 Resolution Authorizing City Manager to Purchase OpenGov Permitting, Licensing and Code Enforcement Software and Related Deployment Services
COD
>
City Clerk
>
RESOLUTIONS
>
2020
>
R2020-162 Resolution Authorizing City Manager to Purchase OpenGov Permitting, Licensing and Code Enforcement Software and Related Deployment Services
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
3/11/2021 12:46:47 PM
Creation date
11/3/2020 1:32:49 PM
Metadata
Fields
Template:
Resolution/Ordinance
Res Ord Num
R2020-162
Res Ord Title
R2020-162 Resolution Authorizing City Manager to Purchase OpenGov Permitting, Licensing and Code Enforcement Software and Related Deployment Services
Department
Econ and Com Dev
Approved Date
11/2/2020
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
33
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
(D OPENGov <br /> The communication path for this engagement will be outlined in the kick off meeting, <br /> documenting both phone numbers and email.The general path is: <br /> OpenGov Project Manager — Professional Services Sr. Manager / SVP --> Executive <br /> Sponsor <br /> 6. Escalation Process <br /> The purpose of this section is to define the escalation process, should it be needed, to <br /> support closing issues that are raised, discussed to move forward with the deployment. <br /> OpenGov and Customer agree to raise concerns and follow the escalation process, <br /> resource responsibility,and documentation. <br /> 6.1. Process <br /> • Identification of an issue impeding deployment progress, outcome or capturing the <br /> value proposition,that is not acceptable. <br /> • Customer or OpenGov Project Manager summarizes the problem statement and <br /> impasse. <br /> • Customer and OpenGov Project managers will outline solution, acceptance or <br /> schedule Executive review in accordance with SLA as defined in Section 7 General <br /> Project Assumptions. <br /> • Resolution will be documented and signed off following Executive review in <br /> accordance with SLA as defined in Section 7 General Project Assumptions. <br /> 6.2. Escalation Requirements <br /> • OpenGov and Customer Project Managers will summarize impasse and <br /> recommendation to present at scheduled or ad hoc executive meetings. Unless <br /> otherwise noted in this SOW,Customer Project Manager can approve how hours are <br /> used,but not where funding is required. <br /> • Executive Sponsors attend monthly (or other frequency) executive meetings to <br /> review deployment status,documented issue list,status,and closure summary. <br /> • Steering Committees, where applicable, will be the arbitrator to direction and issue <br /> closure. Unless otherwise noted in this SOW,the Customer Executive Sponsor must <br /> approve change orders that result in additional cost. <br /> • Customer or OpenGov Subject Matter Experts may be requested to provide input to <br /> the issue and assist in closure. Both Customer and OpenGov will make best effort to <br /> enable those Subject Matter Experts to be available and participate. <br /> 11 <br />
The URL can be used to link to this page
Your browser does not support the video tag.