My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
To BOCC
>
Meetings
>
2017
>
03. March
>
To BOCC
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/10/2018 11:50:35 AM
Creation date
4/10/2018 11:50:08 AM
Metadata
Fields
Template:
Meeting
Date
3/21/2017
Meeting title
Commissioners' Agenda
Location
Commissioners' Auditorium
Address
205 West 5th Room 109 - Ellensburg
Meeting type
Regular
Meeting document type
Supporting documentation
Supplemental fields
Alpha Order
i
Item
Request to Approve a Resolution for a Sales Order with Paladin Data Systems Corporation and to Authorize the Chairman’s Signature on the Terms of Service Agreement for Phase II Implementation of SMARTGOV
Order
9
Placement
Consent Agenda
Row ID
35566
Type
Contract
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
14
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
<br />Page 1 of 3 <br />v416 <br />SMARTGOV® Service Level Agreement <br /> <br />This Service Level Agreement (“SLA”) for SMARTGOV® Software as a Service (SaaS) describes the service that You <br />will receive from Us and serves as a supplemental document to the Paladin Data Systems Corporation Master SaaS <br />Subscription and Professional Services Agreement (“Agreement”) which the Parties have executed. <br />1.1. "Access Protocols" will mean industry standard internet access protocols through which We make SMARTGOV® <br />accessible to You, which includes, unless otherwise specified, HTTPS. <br />1.2. "Annual Subscription Service Fee" will mean the annual SMARTGOV® SaaS Subscription fee. <br />1.3. "Application Service” will mean the SMARTGOV® software application being delivered as a hosted service by <br />Us excluding any testing or training environment. <br />1.4. "Disaster" will mean a catastrophic event that is caused by acts beyond Our reasonable control and that result in <br />significant or potentially significant downtime or disruption of the production environment and requires Us to invoke <br />Our Disaster Recovery plan. We have the sole and exclusive right to declare a Disaster. <br />1.5. "Disaster Recovery" will mean Our process to restore System Availability in the event that We declare a Disaster <br />as defined above in 1.4. <br />1.6. “Party or Parties” will mean either We, Us, or Our, as well as You or Your individually or collectively. <br />1.7. "Scheduled Downtime" will mean the total amount of time during any Service Year during which the Application <br />Service core features and functions are unavailable for the majority of Your users according to the Access <br />Protocols, due to planned System maintenance performed by Us, as set forth below. We will provide reasonable <br />notice for all Scheduled Downtime. We will exercise reasonable efforts to perform scheduled System maintenance <br />outside of standard business hours. Generally these scheduled System maintenance activities occur once a <br />month. <br />1.8. “Service Standard” will mean the System Availability during each Service Year will equal or exceed ninety-nine <br />percent (99%). <br />1.9. “Service Year” will mean the preceding 365 days from the date of an SLA claim. <br />1.10. “Start Date” will mean the date in which the Annual Subscription Service Fee commences. Start Date is also <br />known as go-live date. <br />1.11. "System" will mean the Application Service. <br />1.12. "System Availability" will mean, with respect to any Service Year, the ratio obtained by subtracting Unscheduled <br />Downtime during such Service Year from the total time during such Service Year (525,600 minutes) and thereafter <br />dividing the difference so obtained by the total time dur ing such Service Year. If You have been using the <br />Application Service for less than 365 days from the Start Date, Service Year is still the preceding 365 days but <br />any days prior to Your use of the service will be deemed to have had 100% availability. Represented <br />mathematically, System Availability for any particular Service Year is determined as follows: <br />System Availability = (Total Service Year Time - Unscheduled Downtime) / Total Service Year Time. <br />NOTE: "Total Service Year Time" is deemed to include all minutes in the relevant Service Year period as <br />described above (525,600 minutes). <br />1.13. "Unscheduled Downtime" will mean the total amount of time in minutes during any Service Year during which <br />the Application Service core features and functions are unavailable for Your access according to Access <br />Protocols, other than Scheduled Downtime, as defined above. See section 4.1 for details on detection of <br />Unscheduled Downtime. <br />1.14. “We, Us, or Our” will mean Paladin Data Systems Corporation. <br />1.15. “You or Your” will mean the company or other legal entity for which you are accepting this Agreement. <br /> <br />2.1. System Availability. We will undertake commercially reasonable measures to make sure System Availability <br />meets the Service Standard, provided that any Unscheduled Downtime occurring as a result of circumstances <br />beyond Our reasonable control including, but not limited to: (i) Your breach of any provision of this Agreement; <br />(ii) non-compliance by You with any provision of this Agreement; (iii) incompatibility of Your equipment or software <br />with the Application Service; (iv) poor or inadequate performance of Your Systems; (v) Your equipment failures; <br />(vi) Your network and internet service provider; (vii) public internet; (viii) security exposure; or (ix) force majeure, <br />will not be considered toward any reduction in System Availability measurements. In the event of a Disaster , <br />System Availability service levels defined 1herein do not apply. <br />2.2. System Response Times. We will undertake commercially reasonable measures to make sure that observed <br />System requests are processed within the System on average within 500ms, excluding circumstances beyond <br />Our reasonable control including, but not limited to: (i) large or complicated reporting requests; (ii) poor or <br />inadequate performance of Your Systems; (iii) Your equipment failures; (iv) Your network and internet service <br />provider; or (v) public internet. Circumstances beyond Our control will not be considered toward any reduction in <br />System requests.
The URL can be used to link to this page
Your browser does not support the video tag.