IT Support Services...
Our IT support services
All of our IT support service offerings are specifically designed to allow small and medium sized businesses access to an efficient and effective IT support service normally only found within big businesses. How do we achieve this? Simple, we put you, the customer, in control of on going IT support costs by allowing you to decide the severity of problems encountered and the speed by which those problems are dealt with. Both of these variables dictate how much you will pay for your IT support service
IT Support is a critical part of operating an effective IT system. Companies need to be supported by a quality level of technical expertise that can solve problems as they arise and not leave themselves struggling with uncooperative IT equipment. Typically, IT Support comes in three flavours:
- 1 st Line (Helpdesk) – takes and progresses user fault reports and identifies whether problems are at a system level (hardware, software, communications, or documentation)
- 2 nd Line (On/Off-site Support) – progresses problems escalated from 1ST line support and identify specific design defects or procedural shortcomings. 2ND line support may also provide work-rounds pending the permanent resolution of a fault
- 3 rd Line – called upon by 2ND line support to seek a permanent solution to the reported problem. This may involve correcting bugs in software, repairing hardware or revising user documentation
Breakwater offers the following three types of IT support service contracts:
- 1 Year 1 st / 2 nd Line Service Support Contract
The provision of a contracted (12 month commitment) ServiceDesk (Helpdesk) facility (within core BWIT business hours of Monday to Friday, 8am – 6pm) that records and manages all reported incidents against agreed Service Level Agreements (SLAs). Weekly and monthly reports provided to the customer on all open and closed calls. Calls get assigned to 2nd line support staff who can quickly and efficiently resolve incidents – either remotely or on-site. Also included is IT Asset (both software and hardware) management locking down systems against un-authorised configuration change
- Pay As You Go! IT Support
This support proposal includes provision of the services detailed in above (excluding Asset tagging and helpdesk reports) but on a ‘Pay-as-you-go’ basis. In addition to a nominal retainer fee costs are incurred per incident (as detailed later)
- 1 Year 1 st – 3 rd Line Service Support Contract
As 1 st option but extended by getting to the root cause of incidents and seeking a permanent fix as opposed to continually “plastering over the cracks!”. Also, it ensures best practices are applied when applying changes to the IT environment. This involves proving and testing in non-live environments prior to “Go Live” with continual review of applicable software patching and control of software distribution following proven techniques. Finally, the monitoring of system capacities across IT equipment thus proactively managing system bottlenecks avoiding foreseeable downtime. SLAs to monitor uptime, thus maximising systems availability within business hours, will also be created
Industry Best Practice - ITIL Modular Approach
Breakwater’s IT Support service is underpinned by use of ITIL (the IT Infrastructure Library) which is the most widely accepted approach to IT service management in the world. It provides a comprehensive and consistent set of best practices for IT service management, promoting a quality approach to achieving business effectiveness and efficiency in the use of information systems. Breakwater use the following modules:
Module |
ITIL Terminology |
Layman’s Terms |
SERVICE DESK |
Provide a single point of contact for Customers. To facilitate the restoration of normal operational service with minimal business impact on the Customer within agreed service levels and business priorities |
Helpdesk facility that records and manages all reported incidents against agreed SLAs. Weekly and monthly reports provided to the customer on all open and closed calls |
INCIDENT MANAGEMENT |
Restore normal service operation as quickly as possible and minimise the adverse impact on business operations, thus ensuring that the best possible levels of service quality and availability are maintained. 'Normal service operation' is defined here as service operation within Service Level Agreement (SLA) limits |
This is the process behind dealing with incidents that have been reported by the helpdesk. Calls get assigned to 2nd line and 3rd line support staff to quickly, and efficiently resolve incidents – either remotely or on-site within agreed SLAs |
PROBLEM MANAGEMENT |
Minimise the adverse impact of Incidents and Problems on the business that are caused by errors within the IT Infrastructure, and to prevent recurrence of Incidents related to these errors. This is achieved by getting to the root cause of Incidents and then initiate actions to improve or correct the situation |
This involves getting to the root cause of incidents and seeking a permanent fix as opposed to continually “plastering over the cracks!” |
CHANGE MANAGEMENT |
Ensure that standard methods and procedures are used, such that changes can be dealt with quickly, with the lowest possible impact on service quality whilst recording full traceability |
Ensures best practices are applied when applying changes to the IT environment. This involves proving and testing in non-live environments prior to Go Live! |
RELEASE MANAGEMENT |
To plan and oversee the successful rollout of software and related hardware. To design and implement efficient procedures for the distribution and installation of Changes to IT systems ensuring that hardware and software being changed is traceable, secure and that only correct, authorised and tested versions are installed |
Continual review of applicable software patching and control of software distribution following proven techniques |
CONFIGURATION MANAGEMENT |
Account for all the IT assets and configurations within customer and its services by providing accurate information on configurations and their documentation to support all the other Service Management processes |
IT Asset (both software and hardware) management locking down systems against un-authorised configuration change |
Service Level Agreements
It is now widely accepted that IT service provision and receipt should be governed by an agreement. This is essential to define the parameters of the service, for the benefit of both the provider and the recipient. The SLAs detailed below illustrates how Breakwater approach’s Service Support.
ServiceDesk – Incident SLAs
Reacting to incidents reported to the ServiceDesk, adhering to the following standard SLAs.
| Priority |
Initial Response |
2 nd Line Trigger |
3 rd Line Trigger |
Target Fix Time |
Critical |
<=15 minutes |
20 minutes |
03 hours |
04 hours |
High |
<=01 hour |
02 hours |
03 hours |
01 day |
Medium |
<=01 day |
02 days |
04 days |
05 days |
Low |
<=02 days |
04 days |
08 days |
10 days |
Problem Management SLAs
Taking reoccurring incidents “offline” and looking at providing a permanent resolution to the underlying problem.
| Priority |
Initial Response |
2 nd Line Trigger |
Target Fix Time |
Critical |
N/A |
01 day |
05 days |
High |
N/A |
05 days |
10 days |
Medium |
N/A |
10 days |
20 days |
Low |
N/A |
30 days |
60 days |
Request For Change SLAs
Changes to the IT environment, i.e. proactive not reactive, are handled using longer timelines.
| Priority |
Initial Response |
2 nd Line Trigger |
Target Fix Time |
Critical |
<=04 hour |
02 days |
05 days |
High |
<=01 day |
04 days |
10 days |
Medium |
<=02 days |
10 days |
20 days |
Low |
<=04 days |
20 days |
60 days |
Service Deliverables
| Delivery Type |
Frequency |
Service Description |
Service Reports |
Weekly |
|
|
|
The number of ServiceDesk incidents raised by/ for the BP (sorted by priority) |
|
|
The number of ServiceDesk incidents closed within SLA |
|
|
The number of ServiceDesk incidents closed outside stated SLA |
|
Monthly |
|
|
|
The number of ServiceDesk incidents raised by/for the BP |
|
|
The number of ServiceDesk incidents closed within SLA |
|
|
The number of ServiceDesk incidents closed outside stated SLA |
|
|
The number of ServiceDesk incidents still open |
|
|
The top 10 oldest ServiceDesk incidents for BP |
|
Annual |
|
|
|
A report listing current software compliance status |
|
|
A report listing current hardware life cycle status |
|
|
A report listing ServiceDesk performance |
|
|
A report listing service availability/performance/checks |
|
|
A report listing change management performance |
|
|
Contractual costs surrounding current and future module/variable requirements |
|
 |