KAMI Service Level Agreement (SLA)

Modified on Fri, 14 Jun at 1:08 PM

About this Document

This Service Level Agreement for KAMI Workforce ("KAMI") (this “SLA”) is a part of your KAMI Workforce Master Service Agreement (the “Agreement”). Capitalized terms used but not defined in this SLA will have the meaning assigned to them in the Agreement. This SLA applies to the KAMI Workforce Services listed herein (a “Service” or the “Services”), but does not apply to separately branded services made available with or connected to the Services or to any on-premise software that is part of any Service.

 

If we do not achieve and maintain the Service Levels for each Service as described in this SLA, then you may be eligible for a credit towards a portion of your monthly service fees. We will not modify the terms of your SLA during the initial term of your subscription; however, if you renew your subscription, the version of this SLA that is current at the time of renewal will apply throughout your renewal term. We will provide at least 90 days’ notice for significant material changes to this SLA. 

 

Previews and Online Services and/or service tiers provided free of charge are not included or eligible for SLA claims or credits.



Definitions

Applicable Monthly Period” means, for a calendar month in which a Service Credit is owed, the number of days that you are a subscriber for a Service. 

Applicable Monthly Service Fees” means the total fees actually paid by you for a Service that are applied to the month in which a Service Credit is owed.

Downtime” is defined as any period of time when end users are unable to login to the KAMI application or entirely unable to access any specific KAMI module. Downtime does not include Scheduled Downtime. Downtime does not include unavailability of a Service due to limitations described below.

Error Code” means an indication that an operation has failed, such as an HTTP status code in the 4xx or 5xx range.

External Connectivity” is bi-directional network traffic over supported protocols such as HTTP and HTTPS that can be sent and received from a public IP address.

Incident” means (i) any single event, or (ii) any set of events, that result in Downtime.

"Monthly Uptime Percentage" is calculated using the following formula.


(User Minutes - Downtime) / User Minutes * 100


where Downtime is measured in user-minutes; that is, for each month, Downtime is the sum of the length (in minutes) of each Incident that occurs during that month multiplied by the number of users impacted by that Incident.


Management Portal” means the web interface, provided by KAMI, through which customers may manage the Service.

Scheduled Downtime” means periods of Downtime related to network, hardware, or Service maintenance or upgrades. We will publish notice or notify you at least five (5) days prior to the commencement of such Downtime.

Service Credit” is the percentage of the Applicable Monthly Service Fees credited to you following KAMI’s claim approval.

Service Level” means the performance metric(s) set forth in this SLA that KAMI agrees to meet in the delivery of the Services.

Service Resource” means an individual resource available for use within a Service.

Success Code” means an indication that an operation has succeeded, such as an HTTP status code in the 2xx range.

Support Window” refers to the period of time during which a Service feature or compatibility with a separate product or service is supported.

User Minutes” means the total number of minutes in a month, less all Scheduled Downtime, multiplied by the total number of users.


Service Credit

Monthly Uptime PercentageService Credit
< 99%25%
< 97%50%
< 95%75%
< 93%100%



Terms

Claims

In order for KAMI to consider a claim, you must submit the claim to customer support at KAMI including all information necessary for KAMI to validate the claim, including but not limited to: (i) a detailed description of the Incident; (ii) information regarding the time and duration of the Downtime; (iii) the number and location(s) of affected users (if applicable); and (iv) descriptions of your attempts to resolve the Incident at the time of occurrence.

 

We must receive the claim by the end of the calendar month following the month in which the Incident occurred. For example, if the Incident occurred on February 15th, we must receive the claim and all required information by March 31st.

 

We will evaluate all information reasonably available to us and make a good faith determination of whether a Service Credit is owed. We will use commercially reasonable efforts to process claims during the subsequent month and within forty-five (45) days of receipt. You must be in compliance with the Agreement in order to be eligible for a Service Credit. If we determine that a Service Credit is owed to you, we will apply the Service Credit to your Applicable Monthly Service Fees.

 

Service Credits

Service Credits are your sole and exclusive remedy for any performance or availability issues for any Service under the Agreement and this SLA. You may not unilaterally offset your Applicable Monthly Service Fees for any performance or availability issues.


Service Credits apply only to fees paid for the particular Service, Service Resource, or Service tier for which a Service Level has not been met. In cases where Service Levels apply to individual Service Resources or to separate Service tiers, Service Credits apply only to fees paid for the affected Service Resource or Service tier, as applicable. The Service Credits awarded in any billing month for a particular Service or Service Resource will not, under any circumstance, exceed your monthly service fees for that Service or Service Resource, as applicable, in the billing month.

 

If you purchased a Service from a reseller, you will receive a service credit directly from your reseller and the reseller will receive a Service Credit directly from us. The Service Credit will be based on the estimated retail price for the applicable Service, as determined by us in our reasonable discretion.


Limitations

This SLA and any applicable Service Levels do not apply to any performance or availability issues:

  1. Due to factors outside our reasonable control (for example, natural disaster, war, acts of terrorism, riots, government action, or a network or device failure external to our data centers, including at your site or between your site and our data center);
  2. That result from the use of services, hardware, or software not provided by us, including, but not limited to, issues resulting from inadequate bandwidth or related to third-party software or services;
  3. That results from failures in a single KAMI Datacenter location, when your network connectivity is explicitly dependent on that location in a non-geo-resilient manner;
  4. Caused by your use of a Service after we advised you to modify your use of the Service, if you did not modify your use as advised;
  5. During or with respect to preview, pre-release, beta or trial versions of a Service, feature or software (as determined by us) or to purchases made using KAMI subscription credits;
  6. That result from your unauthorized action or lack of action when required, or from your employees, agents, contractors, or vendors, or anyone gaining access to our network by means of your passwords or equipment, or otherwise resulting from your failure to follow appropriate security practices;
  7. That result from your failure to adhere to any required configurations, use supported platforms, follow any policies for acceptable use, or your use of the Service in a manner inconsistent with the features and functionality of the Service (for example, attempts to perform operations that are not supported) or inconsistent with our published guidance;
  8. That result from faulty input, instructions, or arguments (for example, requests to access files that do not exist);
  9. That result from your attempts to perform operations that exceed prescribed quotas or that resulted from our throttling of suspected abusive behavior;
  10. For licenses reserved, but not paid for, at the time of the Incident.
  11. Any planned maintenance window that incurs a downtime to patch your server and infrastructure is excluded from the uptime calculation.

 



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article