My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
25A - AGMT - AGENDA WORKFLOW AND STREAMING
Clerk
>
Agenda Packets / Staff Reports
>
City Council (2004 - Present)
>
2017
>
12/19/2017
>
25A - AGMT - AGENDA WORKFLOW AND STREAMING
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/8/2019 3:21:33 PM
Creation date
12/14/2017 7:06:51 PM
Metadata
Fields
Template:
City Clerk
Doc Type
Agenda Packet
Agency
Clerk of the Council
Item #
25A
Date
12/19/2017
Destruction Year
2022
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
100
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
G G R A N I C U S RFP NO.: 17-107 Automated Agenda Workflow <br />Program and Meeting Video Streaming/Archiving <br />3. OUT OF SCOPE <br />This section captures the most common out -of -scope scenarios that Granicus <br />encounters during the lifecycle of any given project. Granicus will not engage in any <br />out -of -scope work without prior written approval from Client. Any product change or <br />enhancement not explicitly listed in the project scope in Section 2 is considered out-cf- <br />scope. <br />1, CREATION OF CUSTOM REPORTS <br />a. A custom report is defined as a report that requires modifications to the core <br />application code in order to achieve a desired format or purpose. <br />b. Examples of out -of -scope custom reports include, but are not limited to: <br />I. Creating a brand new data field that does not exist on any report or <br />existing database <br />II. Having data that displays on one type of report display on another <br />III. Adding a second logo to a report <br />IV. In general, modifications to formatting (font, size, or justifications), or <br />hiding or moving certain data elements on a single report, are not <br />considered custom reports, and are thus considered "in -scope." <br />c. The creation of any custom reports requires a separate assessment and project <br />scope. Billing for custom reports is assessed on an hourly basis at the current <br />professional services rate. <br />2. AN Integrations <br />a. Examples of out -of -scope AN requests include, but are not limited to: <br />I. Requests to make modifications to API functionality to accommodate any <br />third party integration <br />II. Any feasibility/data gap analysis to determine whether or not an API will <br />be suitable for any Client integration or business need <br />III. Any custom programming/configuration done by a Granicus staff <br />member or contractor to accomplish or in pursuit of accomplishing any <br />AN integration <br />IV. Any request for support regarding a third -party integration not created by <br />Granicus or its contractors <br />V. Any other AN integration not clearly defined by this original scope of work <br />b. Billing for out -of -scope API integrations is assessed on an hourly basis at the <br />current professional services rate. <br />granicus.com I info@granicus.ccm <br />25A-64 <br />page 31 <br />
The URL can be used to link to this page
Your browser does not support the video tag.