Service Attribute |
Attribute Definitions |
Service Target |
---|---|---|
Service Reception |
Answering a telephone call from a customer and logging information relevant to a fault or other details relevant to the service required. | Service Restoration: incoming phone calls to be answered 24 hours a day, every day. |
Normal Service Hours |
Those hours during which, when a customer reports a fault, Spark will commence restoration activity at no additional cost. (See note 1 below). | 24 hours per day, 7 days per week. |
Service Restoration Targets |
The elapsed time, during Normal Service Hours, between customer reporting a fault to Spark and confirmation to the customer that the service has been restored. | 24 hours (reasonable endeavour) |
Service Attribute |
Attribute Definitions |
Service Target |
---|---|---|
Service Reception |
Answering a telephone call from a customer and logging information relevant to a fault or other details relevant to the service required. | Service Reception: Incoming phone calls to be answered 24 hours a day, seven days a week, within 20 seconds. Billing and Provisioning: Incoming phone calls are to be answered on Business Days (refer to clause 2 of 'Notes and Definitions' below), 0800 to 1730 within 20 seconds. |
Normal Service Hours |
Means those hours during which, when the customer reports a fault, Spark will commence restoration activity at no additional cost. In the event the customer requests fault restoration, Call-out Fees may apply (refer to clause 1 of 'Notes and Definitions' below). |
24 hours per day, 7 days per week. |
Initial Restoration Update |
The elapsed time, during Normal Service Hours, between the customer reporting a fault to Spark and confirmation to the customer that initial diagnosis has been completed and an estimated time to restore is provided, if known. | Within 60 minutes. |
Progress Updates | Updates on the status of service restoration activity. | Provided to the customer on a 'significant event basis', or as agreed. |
Service Restoration Targets |
The elapsed time, during Normal Service Hours, between the customer reporting a fault to Spark and confirmation to the customer that the service has been restored. | 6 Hours - reasonable endeavours |
Provisioning Change Target |
The elapsed time between the confirmed acceptance via email, fax or phone by Spark of the customer's Provisioning and Change Request and the implementation of that request, unless the customer specifies a longer time. | As per the following page entitled "Provisioning and Change Targets". |
Billing Issue Resolution Target |
The elapsed time between the customer initiating a billing enquiry and confirmation to the customer of its resolution. | Single account, with account arrears less than 90 days: 2 Business Days. Multiple accounts, or account arrears more than 90 days: by mutual agreement. |
Service Attribute |
Attribute Definitions |
Service Target |
---|---|---|
Service Reception |
Answering a telephone call from a customer and logging information relevant to a fault or other details relevant to the service required. | Service Reception: Incoming phone calls to be answered 24 hours a day, seven days a week, within 20 seconds. Billing and Provisioning: Incoming phone calls are to be answered on Business Days (refer to clause 2 of 'Notes and Definitions' below), 0800 to 1730 within 20 seconds. |
Normal Service Hours |
Those hours during which, when a customer reports a fault, Spark will commence restoration activity at no additional cost. (See note 1 below). | 24 hours per day, 7 days per week. |
Initial Restoration Update |
The elapsed time, during Normal Service Hours, between reporting a fault to Spark and confirmation to the customer that initial diagnosis has been completed and an estimated time to restore is provided, if known. | Within 60 minutes. |
Progress Updates | Updates on the status of service restoration activity. | Provided to the customer on a 'significant event basis', or as agreed. |
Service Restoration Targets |
The elapsed time, during Normal Service Hours, between customer reporting a fault to Spark and confirmation to the customer that the service has been restored. | 6 Hours - reasonable endeavours |
Provisioning Change Target |
The elapsed time between the confirmed acceptance of a Provisioning/Change Request and the implementation of that request, unless the customer specifies a longer time. | |
Billing Issue Resolution Target |
The elapsed time between the customer initiating a billing enquiry and confirmation to the customer of its resolution. | Single account, with account arrears less than 90 days: 2 Business days Multiple accounts, or account arrears more than 90 days: by mutual agreement |
Service Measure |
Description |
Service Target |
Exclusions & Notes |
---|---|---|---|
Provisioning Target |
The elapsed time between Spark's written acceptance of a provisioning request and the implementation of that request, unless the customer specifies a longer time. | 21 Business Days | Based on the availability of fibre or cable into the requested site. If fibre or cable does not exist, installation targets will be by negotiation. Subject to the availability of IP Addresses (factors involved in obtaining an IP address may result in delays, which are out of Spark's immediate control). |
Service Capacity Upgrades |
The elapsed time between a request for increased capacity and the implementation of that request, unless the customer specifies a longer time. | 21 Business Days | Provided that the capacity upgrade required is in accordance with your forecast. Spark requires the customer to update their anticipated forecasts every three months to enable Spark to meet DDS Dedicated Internet Access requirements for the customer. |
Service Reception |
Spark answering a telephone call from a customer and (if necessary) logging information relevant to a fault or other details relevant to the service required. | Answered within 20 seconds | Service Restoration: incoming phone calls to be answered 24 hours a day, every day, within 20 seconds. Billing and Provisioning incoming phone calls to be answered within 20 seconds, during Normal Service Hours on Business Days. |
Restoration Activity |
Those hours during which, the customer reports a fault, Spark will commence restoration activity for the customer at no additional cost (see note 1 below). | 24 hours, 7 days a week | Including public holidays |
Initial Restoration Update |
The elapsed time, during Normal Service Hours, between the customer reporting a fault to Spark and confirmation to the customer that initial diagnosis has been completed and an estimated time to restore is provided, if known. | Within 60 minutes | |
Progress Updates |
Updates on the status of service restoration activity. | Hourly or as agreed | Provided to the customer on a significant event basis, or as agreed. |
Service Restoration Target |
Normal Service Hours, between the customer reporting a fault to Spark and confirmation to the customer that the service has been restored. | Major Metropolitan Areas: 6 Hours Other Areas: 8 hours |
Spark will charge a fee for investigating and fixing faults caused by incorrect advertising of routes from the customer to Spark. |
Planned Outage Targets |
The period of time that the service is temporarily suspended owing to the need for network maintenance or upgrading. | 6 hours in aggregate during any one week. 12 hours in aggregate during any 3-month period. |
|
Planned Outage Notification Target |
The elapsed time between Spark advising the customer by email of intended planned outage and the commencement of that outage. | 3 Days | If urgent circumstances arise, Spark may need to give less than 3 days notice (Spark would only instigate outages during peak times or without prior notice under extreme conditions). |
Service Measure |
Description |
Service Target |
Exclusions & Notes |
---|---|---|---|
Provisioning Target |
The elapsed time between Spark's written acceptance of a provisioning request and the implementation of that request, unless the customer specifies a longer time. |
21 days | Based on the availability of fibre or cable into the requested site. If fibre or cable does not exist, installation targets will be by negotiation. Subject to the availability of IP Addresses (factors involved in obtaining an IP address may result in delays, which are out of Spark's immediate control). |
Service Capacity Upgrades |
The elapsed time between a request for increased capacity and the implementation of that request, unless the customer specifies a longer time. | 3 Business Days | Provided that the capacity upgrade required is in accordance with your forecast. Spark requires the customer to update their anticipated forecasts every three months to enable Spark to meet CID requirements for the customer. |
Service Reception |
Spark answering a telephone call from a customer and logging information if necessary, relevant to a fault or other details relevant to the service required. | Answered within 20 seconds | Service Restoration: incoming phone calls to be answered 24 hours a day, every day, within 20 seconds. Billing and Provisioning incoming phone calls to be answered within 20 seconds, during Normal Service Hours on Business Days. |
Normal Service Hours |
Those hours during which, the customer reports a fault, Spark will commence restoration activity for the customer at no additional cost (see note 1 below). | 24 hours, 7 days a week | Including public holidays |
Initial Restoration Update |
The elapsed time, during Normal Service Hours, between customer reporting a fault to Spark and confirmation to the customer that initial diagnosis has been completed and an estimated time to restore is provided, if known. | Within 60 minutes | |
Progress Updates |
Updates on the status of service restoration activity. | Hourly or as agreed | Provided to the customer on a significant event basis, or as agreed. |
Service Restoration Target |
The elapsed time, during Normal Service Hours, between the customer reporting a fault to Spark and confirmation to the customer that the service has been restored. | Major Metropolitan Areas: 6 Hours Other Areas: 8 hours |
Spark will charge a fee for investigating and fixing faults caused by incorrect advertising of routes from the customer to Spark (see also Notes 2, 6, 7 and 10 below). |
Planned Outage Targets |
The period of time that the service is temporarily suspended owing to the need for network maintenance or upgrading. | 6 hours in aggregate during any one week. 12 hours in aggregate during any 3-month period. |
|
Planned Outage Notification Target |
The elapsed time between Spark advising the customer by email of intended planned outage and the commencement of that outage. | 3 Days | The customer must maintain correct contact details on the CID web page in default of which Spark will use latest contact details as supplied to Spark. If urgent circumstances arise, Spark may need to give less than 3 days notice (Spark would only instigate outages during peak times or without prior notice under extreme conditions). |
Service Attribute |
Attribute Definitions |
Service Target |
---|---|---|
Provisioning Target | The elapsed time between Spark's written acceptance of a provisioning request and the implementation of that request, unless the customer specifies a longer time. | Up to 128k - 15 Business Days Over 128k - 21 business days |
Service Reception |
Answering a telephone call from a customer and logging information relevant to a fault or other details relevant to the service required. | Service Reception: Incoming phone calls to be answered 24 hours a day, seven days a week, within 20 seconds. Billing and Provisioning: Incoming phone calls are to be answered on Business Days (refer to clause 2 of 'Notes and Definitions' below), 0800 to 1730 within 20 seconds. |
Normal Service Hours |
Those hours during which, when a customer reports a fault, Spark will commence restoration activity at no additional cost. (See note 1 below). | 0700 to 1900 inclusive, Business Days |
Initial Restoration Update |
The elapsed time, during Normal Service Hours, between reporting a fault to Spark and confirmation to the customer that initial diagnosis has been completed and an estimated time to restore is provided, if known. | Within 60 minutes. |
Progress Updates | Updates on the status of service restoration activity. | Provided to the customer on a 'significant event basis', or as agreed. |
Service Restoration Targets |
The elapsed time, during Normal Service Hours, between customer reporting a fault to Spark and confirmation to the customer that the service has been restored. | 6 Hours - reasonable endeavours |
Provisioning Change Target |
The elapsed time between the confirmed acceptance of a Provisioning/Change Request and the implementation of that request, unless the customer specifies a longer time. | |
Billing Issue Resolution Target |
The elapsed time between the customer initiating a billing enquiry and confirmation to the customer of its resolution. | Single account, with account arrears less than 90 days: 2 Business days Multiple accounts, or account arrears more than 90 days: by mutual agreement |
Service Attribute |
Attribute Definitions |
Service Target |
---|---|---|
Provisioning Target | The elapsed time between Spark's written acceptance of a provisioning request and the implementation of that request, unless the customer specifies a longer time. | Up to 128k - 15 Business Days Over 128k or n x 64 kbit/s - 21 business days |
Service Reception |
Answering a telephone call from a customer and logging information relevant to a fault or other details relevant to the service required. | Service Reception: Incoming phone calls to be answered 24 hours a day, seven days a week, within 20 seconds. Billing and Provisioning: Incoming phone calls are to be answered on Business Days (refer to clause 2 of 'Notes and Definitions' below), 0800 to 1730 within 20 seconds. |
Normal Service Hours |
Those hours during which, when a customer reports a fault, Spark will commence restoration activity at no additional cost. (See note 1 below). | 0700 to 1900 inclusive, Business Days 0700 to 1700 Saturday 0800 to 1700 Sunday |
Initial Restoration Update |
The elapsed time, during Normal Service Hours, between reporting a fault to Spark and confirmation to the customer that initial diagnosis has been completed and an estimated time to restore is provided, if known. | |
Progress Updates | Updates on the status of service restoration activity. | Provided to the customer on a 'significant event basis', or as agreed. |
Service Restoration Targets |
The elapsed time, during Normal Service Hours, between customer reporting a fault to Spark and confirmation to the customer that the service has been restored. | 4 Hours - reasonable endeavours |
Billing Issue Resolution Target |
The elapsed time between the customer initiating a billing enquiry and confirmation to the customer of its resolution. | Single account, with account arrears less than 90 days: 2 Business days Multiple accounts, or account arrears more than 90 days: by mutual agreement |
Spark continuously monitor throughput on the broadband network and work to make sure the average performance continues to be among the best in the world. However, we cannot provide specific speed performance guarantees and acknowledge that faults do occur.
Whilst we always strive to provide a consistent service, there are a number of factors that influence reliability. For this reason, we do not guarantee bandwidth, latency (delay) or bit rate through our broadband network to the ISP at any one point in time.
Broadband service performance can be impacted by many factors, including customer's house wiring, performance of other networks the traffic passes through, and geographical location of the website e.g. International websites always perform slower than local ones due to the additional distance the data has to travel. More information is available at the Xtra Products Web page.
Spark will provide service management including the following services and capabilities for Managed Mail Service customers.
The service boundaries of the Managed Mail Service do not extend beyond the Managed Mail customer and Internet facing firewalls.
Exclusions
Currently the Managed Mail Services does not provide:
Definitions
Software - Client Configuration - If the customer is accessing the Managed Mail service via their Outlook client they will need to configure Microsoft Outlook (MAPI access) or POP client to allow them access to email from the Managed Mail Service.
In advance of any migration to the Managed Mail service the customer will be responsible for the ensuring that all workstations/laptops meet the minimum configuration of Microsoft Windows 2000 / Office/Outlook 2000 and Internet Explorer 6. Service pack levels for this minimum configuration and later versions are detailed below:
Operating System:
Microsoft Windows 2000 Service Pack 2 (SP4 recommended)
Microsoft Windows XP Service Pack 1
Office / Outlook:
Microsoft Office / Outlook 2000 Service Pack 3
Microsoft Office XP / Outlook 2002 Service Pack 3
Microsoft Office XP / Outlook 2003 (Most recent Service Pack available)
Browser:
Microsoft Internet Explorer 6 Service Pack 1
Note: If RPC over HTTP access or mobility services such as OMA or Active Sync are required the following minimum configuration is applicable:
Note: Access to the Managed Mail service may be restricted if the client does not meet the minimum software version as stated above. Changes to the minimum version required will be notified to all users.
1.3. Mail Policies
This feature provides customers with the ability to enforce control over all email in and out of their organisation through policies implemented in this service. All email through this service is virus scanned and checked against the policies defined.
Mail Policy selection: The standard Managed Mail Policy template is implemented. This document will be supplied to the customer detailing the standard incoming/outgoing mail policy.
2. Service Targets
2.1. Service Delivery Performance Targets
Spark will endeavour to achieve the following targets:
Spark continuously monitor throughput on the broadband network and work to make sure the average performance continues to be among the best in the world. However, we cannot provide specific speed performance guarantees and acknowledge that faults do occur.
Whilst we always strive to provide a consistent service, there are a number of factors that influence reliability. For this reason, we do not guarantee bandwidth, latency (delay) or bit rate through our broadband network to the ISP at any one point in time.
Broadband service performance can be impacted by many factors, including customer's house wiring, performance of other networks the traffic passes through, and geographical location of the website e.g. International websites always perform slower than local ones due to the additional distance the data has to travel. More information is available at the Xtra Products Web page.
Spark will provide service management including the following services and capabilities for Managed Mail Service customers.
The service boundaries of the Managed Mail Service do not extend beyond the Managed Mail customer and Internet facing firewalls.
Exclusions
Currently the Managed Mail Services does not provide:
Definitions
Software - Client Configuration - If the customer is accessing the Managed Mail service via their Outlook client they will need to configure Microsoft Outlook (MAPI access) or POP client to allow them access to email from the Managed Mail Service.
In advance of any migration to the Managed Mail service the customer will be responsible for the ensuring that all workstations/laptops meet the minimum configuration of Microsoft Windows 2000 / Office/Outlook 2000 and Internet Explorer 6. Service pack levels for this minimum configuration and later versions are detailed below:
Operating System:
Microsoft Windows 2000 Service Pack 2 (SP4 recommended)
Microsoft Windows XP Service Pack 1
Office / Outlook:
Microsoft Office / Outlook 2000 Service Pack 3
Microsoft Office XP / Outlook 2002 Service Pack 3
Microsoft Office XP / Outlook 2003 (Most recent Service Pack available)
Browser:
Microsoft Internet Explorer 6 Service Pack 1
Note: If RPC over HTTP access or mobility services such as OMA or Active Sync are required the following minimum configuration is applicable:
Note: Access to the Managed Mail service may be restricted if the client does not meet the minimum software version as stated above. Changes to the minimum version required will be notified to all users.
1.3. Mail Policies
This feature provides customers with the ability to enforce control over all email in and out of their organisation through policies implemented in this service. All email through this service is virus scanned and checked against the policies defined.
Mail Policy selection: The standard Managed Mail Policy template is implemented. This document will be supplied to the customer detailing the standard incoming/outgoing mail policy.
2. Service Targets
2.1. Service Delivery Performance Targets
Spark will endeavour to achieve the following targets:
Spark continuously monitor throughput on the broadband network and work to make sure the average performance continues to be among the best in the world. However, we cannot provide specific speed performance guarantees and acknowledge that faults do occur.
Whilst we always strive to provide a consistent service, there are a number of factors that influence reliability. For this reason, we do not guarantee bandwidth, latency (delay) or bit rate through our broadband network to the ISP at any one point in time.
Broadband service performance can be impacted by many factors, including customer's house wiring, performance of other networks the traffic passes through, and geographical location of the website e.g. International websites always perform slower than local ones due to the additional distance the data has to travel. More information is available at the Xtra Products Web page.
Spark will provide service management including the following services and capabilities for Managed Mail Service customers.
The service boundaries of the Managed Mail Service do not extend beyond the Managed Mail customer and Internet facing firewalls.
Exclusions
Currently the Managed Mail Services does not provide:
Definitions
Software - Client Configuration - If the customer is accessing the Managed Mail service via their Outlook client they will need to configure Microsoft Outlook (MAPI access) or POP client to allow them access to email from the Managed Mail Service.
In advance of any migration to the Managed Mail service the customer will be responsible for the ensuring that all workstations/laptops meet the minimum configuration of Microsoft Windows 2000 / Office/Outlook 2000 and Internet Explorer 6. Service pack levels for this minimum configuration and later versions are detailed below:
Operating System:
Microsoft Windows 2000 Service Pack 2 (SP4 recommended)
Microsoft Windows XP Service Pack 1
Office / Outlook:
Microsoft Office / Outlook 2000 Service Pack 3
Microsoft Office XP / Outlook 2002 Service Pack 3
Microsoft Office XP / Outlook 2003 (Most recent Service Pack available)
Browser:
Microsoft Internet Explorer 6 Service Pack 1
Note: If RPC over HTTP access or mobility services such as OMA or Active Sync are required the following minimum configuration is applicable:
Note: Access to the Managed Mail service may be restricted if the client does not meet the minimum software version as stated above. Changes to the minimum version required will be notified to all users.
1.3. Mail Policies
This feature provides customers with the ability to enforce control over all email in and out of their organisation through policies implemented in this service. All email through this service is virus scanned and checked against the policies defined.
Mail Policy selection: The standard Managed Mail Policy template is implemented. This document will be supplied to the customer detailing the standard incoming/outgoing mail policy.
2. Service Targets
2.1. Service Delivery Performance Targets
Spark will endeavour to achieve the following targets:
Service Attribute |
Attribute Definitions |
Service Target |
---|---|---|
Call Reception |
The elapsed time for answering incoming telephone calls. | Fault Reporting: Within 20 seconds Other Enquiries: Within 30 seconds |
Normal Service Hours |
Those hours during which customer calls & requests are supported & system monitored. | 24 hours x 7 days x 365 days/year |
Alarm Notification | The elapsed time between a service impacting alarm occurring (which will be treated as an Urgent Fault) and notification that it has occurred. | 1 Normal Service Hour |
Initial Restoration Update |
The elapsed time between Call Reception or Alarm Notification (as applicable) and notification that initial diagnosis is completed and an impact report is provided. | Within 120 minutes Estimated restoration time is to be provided, if known. |
Progress Updates | Updates on the status of service restoration activity. | Hourly for severity 1, two hourly for severity 2 or at intervals as agreed. Severity 3 and 4 at intervals as agreed. |
Service Restoration |
The elapsed time between Call Reception or Alarm Notification and notification that service is restored to the defined levels. | Severity 1 Severity 2 Severity 3 Severity 4 |
Maintenance Window | The period when routine maintenance can be undertaken on Managed Mail Service. |
Weekly maintenance window for Managed Mail Service is 2:00 am to 7:00 am, Sundays (NZST). Usual customer notification service levels apply. |
Service Availability (Exchange Web Portal) | The availability of the Managed Mail Service. | Spark will use reasonable endeavours to maintain full service availability but does not guarantee the service will be continuously available. |
Billing Enquiry Resolution |
The elapsed time between Call Reception of a billing enquiry and confirmation to the customer of its resolution. | Single account, with account arrears less than 90 days: 2 Business days Multiple accounts, or account arrears more than 90 days: by mutual agreement |
Change Requests (MACs) Simple | The elapsed time between a Change Request being received and completed. |
Within 8 Normal Service Hours |
Change Requests (MACs) | The elapsed time between a Change Request being received and acknowledgement of receipt. | Within 4 Normal Service Hours |
The elapsed time between a Change Request being received and advice of an initial assessment. If possible an expected delivery date/time for the change will be confirmed. | Within 2 Business Days | |
The elapsed time between a Change Request being received assessed as being Complex or a Project, and advising the expected delivery date for the change. | As agreed in discussion with requestor | |
The elapsed time between the changes being completed and advising that it is ready for testing by the customer. | Within 1 Business Day | |
The elapsed time between advising that a change is ready for testing by the customer and the change request being closed. | After 5 Business Days | |
Planned Outage Notification | Notice of any maintenance that could cause a service outage to customer. Please note that not all maintenance will necessarily cause an outage to a customer. |
Weekly Maintenance Window: Outside Weekly Maintenance Window: Emergency Maintenance: |
The customer must provide the first level support point of contact for its users - Managed Mail does not provide direct support to the customer's end users.
The customer must provide the first level support point of contact for its users - Managed Mail does not provide direct support to the customer's end users.
The customer must provide the first level support point of contact for its users - Managed Mail does not provide direct support to the customer's end users.
Severity |
Impact |
Definition |
Initial Response |
---|---|---|---|
1 | Critical | Critical system and/or functionality unusable. Impacts all or more than one customer (Users). No workaround available. Requires immediate corrective action using resources available. |
30 minutes |
2 | High | System and/or functionality unusable to a single customer site (or users associated with that customer) Work around available Problems severely affecting system usage, service levels to customers Requires prompt corrective action using dedicated resource(s). |
45 minutes |
3 | Medium | Problems that do not significantly impair the functioning of the system and do not significantly affect service to customers. Requires managed restoration. |
2 hours |
4 | Low | Problems with no impact to system functionality or service to customers. Requires managed restoration. |
|