DEFINITION OF SERVICE AVAILABILITY

"Service Availability" describes the availability of:

• A cloud instance (where the instance is up and available to the internet)
• The hosting environment (being the servers, storage, routers, switches and internet connectivity) under our exclusive control.
• Service Availability is measured as a percentage of time that the Zambion Cloud Platform is operational and contactable from the internet, calculated over a calendar month, excluding any Scheduled Outages.

SERVICE LEVEL INCLUSIONS AND EXCLUSIONS

The Service Level applies only to a released product.

• Any scheduled outages, being any outage windows scheduled by us when maintenance is required to be performed on the Zambion Cloud Platform (Scheduled Outages);
• Any Beta product (being any product released to the market for testing and feedback);
• Any outages or downtime initiated or caused by your acts or omissions, any software of configuration issues relating to your software, hardware or services.
• We have no obligation to meet the Service Level if any undisputed invoice is overdue for payment or if your account is suspended for any reason in accordance with this Agreement.

OUTAGES

We will use reasonable endeavours to notify you of any Scheduled Outages at least 5 Business Days prior to the date on which the Schedule Outage is proposed to occur. Although system outages for scheduled maintenance are rare we will use reasonable endeavours to plan these outages between 8pm-10pm on a Thursday, Friday, Saturday or Sunday.

SERVICE CREDITS

If we fail to meet any Service Level (Service Level Failure), your sole and exclusive remedy is to claim a Service Credit equal to 10% of the monthly fees paid or payable for the Services (excluding GST) in the calendar month in which the Service Level Failure occurred, subject to the terms and conditions set out in this Annexure.

To claim a Service Credit, you can email the Zambion Service Team within 60 days of the Service Level Failure and provide the following details:

• Details of the date(s) and time(s) of the Service Level Failure; and
• Details of the outage you experienced (Service Credit Claim).

ESCALATION PROCEDURES / ISSUE RESOLUTION

• There is no charge for customer incident resolutions (i.e. unlimited)
• Incidents can be emailed at any time to the Zambion Service Team
• Incidents can be telephoned to the Zambion™ Help desk during the hours of 9am – 5pm Monday to Friday NZT or AEST

Outside of these hours, we suggest you initially call the help desk and leave a message then immediately follow up with an email as Zambion staff sometimes monitor their emails over the weekends and up to 8pm week days. Additionally, if the incident is of a critical nature certain support team members can be reached directly on their mobile phones.

Zambion™ Issue Resolution service provides a secure, confidential escalation process that complements primary email / phone-based support. Zambion uses 5 severity levels. These are as follows:

*Zambion™ will determine the severity level of the ticket and will notify the sender of the assigned level in the first email response
*Severity level times start from when the call or the email is received by Zambion
*Severity level response times are only applicable inside business working hours

 

SERVICE SERVERITY LEVEL EXAMPLES

Below are a few examples of the types of service requests and the severity level we would assign. Please note that these are generic examples to act as a guideline. Severity levels will be assigned based on the email and the situation at the time.

• Level 1 - A number of users cannot access the Zambion Servers/Cluster
• Level 2 - A key function might be running slow or certain key staff cannot access Zambion
• Level 3 - A issue with the award interpretation where the customer requires an immediate change
• Level 4 - A user's Zambion access needs to be added or modify, or a staff member might not to be able access from their home computer or mobile phone and Zambion has been ask to assist / advised
• Level 5 - A new feature or report has been requested

 

INFORMATION SECURITY INCIDENTS

An information security incident is an event that poses a threat to computer or network security in respect of availability, integrity and confidentiality. Examples of information security incidents include theft and burglary, packet flooding, unauthorised access or use of system resources, unauthorised use of another user's acount, unauthorised use of system privileges, system penetration or intrusion, and massive virus attacks.

Zambion monitors for security breaches at all times but if you would like to report a suspected incident, email or telephone the Zambion Service Team.

If an information security incident that may affect the security of your information or interconnected systems is detected or reported, we will reasonably endeavour to:

• Notify you of the incident
• Recover data and services following the information security incident
• Share post-incident reports with you, the affected customer, provided there is no sensitive customer data relating to other customers in the report