TABLE OF CONTENTS
3.1 Switching Services Details
4 Payment Terminal Service Aggregator (PTSA) Services.
5 NIBSS Automated Clearing/Payment System Services.
5.1 NIBSS Automated Clearing/Payment System Services
6 Identity Management Services.
6.1 Identity Management Services
7 Web Operations and Portal Services.
7.1 Web Operations and Portal Services Details
8 Payment Processing and Reconciliation Services.
8.1 Payment Processing and Reconciliation Services
9.1 Application Support Service Details
10.1 Data Centre Service Details
11 Network Management Services.
11.1 Network Management Details
12 Compute & Storage Services.
12.1 Compute & Storage Services Details
13.1 Software Development Service Details
14 Information Security Services.
14.1 Information Security Services Details
15.1 Client Computing Service Details
16 External Service Providers.
1 Introduction
Nigeria Inter-Bank Settlement Systems (NIBSS) IT Services Catalogue identifies, in one cohesive document, the services provided by the Technology & Operations Division.
A common language is required between Technology & Operations (TO) Division and the business areas to effectively translate business requirements into IT capabilities that deliver measurable value.
This IT Services Catalogue enables TO Division to articulate how they add value to their internal customer (user) over the entire generic IT value chain or IT solution development cycle. For each service in the IT Services Catalogue, Value Propositions and Service Elements have been defined. It is meant to be a framework that supports the management of all IT stakeholders.
This document defines:
- A Common Catalogue of defined IT services
- Clear ownership of services
- Clear metrics for measuring level of service delivery
1.1 Objectives and Scope
The purpose of this document is to define the services that Technology & Operations (TO) provide to support NIBSS’s business. This IT Services Catalogue is a repository of IT services and provides a single source for service information such as service description, owner and metrics.
This IT Services Catalogue is based on the current state of IT service capabilities at NIBSS.
1.2 Definitions
The following sections provide a generic outline of the terms used to specify the service levels for Direct Services. Definitive statements are given in individual service level definitions.
S/N |
Term |
Description |
1 |
Service name |
The type of service that NIBSS expects IT to provide |
2 |
Service definition |
A description of the service and its major components being provided by T&O to NIBSS. The definition will generally contain a broad outline of the service. |
3 |
Targeted service level |
The standard of service expected in the delivery of described services. This is expressed in terms of scheduled hours of service, availability, reliability, serviceability and response time, to the extent each term is applicable and relevant to the services unless stated otherwise |
4 |
Scheduled hours of service
|
Scheduled hours of service are defined in terms of the hours within a day, or days within a larger period, during which the system or service is to be available. |
5 |
Scheduled downtime
|
Time agreed during which the system may be made purposefully unavailable to users to enable maintenance to be performed. |
6 |
Availability |
|
7 |
Reliability |
The reliability expected from the system or service. The systems shall provide an acceptable level of reliability in terms of the following:
|
8 |
Serviceability |
Serviceability outlines the timeliness with which IT will resolve loss of service. |
9 |
Outages measure the time lost per failure.
|
|
10 |
Response time
|
Time taken for users to perform an online transaction within the normal business environment. In the case of batch or manual services, the response time will include the completion time of tasks. Response times shall be measured as the average time lapse from initiating a request to completion of request. Each transaction that fails to meet this requirement shall be counted once. Response time data shall be collected and analysed using statistically valid techniques. |
11 |
Point of Service Delivery
|
The location at which the level of service defined is to be delivered and the point at which the service is measured. Measurement of performance The measurement of performance standards for service levels is specified in each service level |
12 |
Measurement period/reporting frequency |
The period of time over which availability, reliability, serviceability and response time will be measured and reported. |
13 |
System response and measurement
|
|
14 |
Responsibility for measurement
|
The party designated as being responsible for collecting measurement details. In all cases where IT is responsible for an activity according to this Service Catalogue, IT is also responsible for assessing and reporting its performance in the manner specified in this document. |
15 |
Service Elements |
Aspects of the service that work together to achieve the desired outcomes upon which the customer and the business base their perceptions of a service. |
16 |
Service Assets |
The assets of a service provider include anything that could contribute to the delivery of a service. Assets can be one of the following types: management, organization, process, knowledge, people, information, applications, infrastructure or financial capital. |
17 |
Measurement method
|
The definition of how the performance of the service is to be measured and/or calculated as set forth in the Performance Metric for the applicable service level. This section also includes, where applicable, points of measurement collection. Measurement will be made and reported monthly unless stated otherwise. |
2 Client Services
2.1 Client Service Details
Service Name: Client services |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|
||||
Description and Scope: Provide 1st level technical support on business applications to external customers.
|
|
Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition): This service provides external customers with a first point of contact on requests, complaints, inquiries etc. |
|
|||||
| ||||||
|
|
|
||||
Service Assets
|
|
Class of Service Standard
|
||||
2.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Business Applications Management |
On-line scheduled hours of application availability will be not less than 99.9% 24x7x365 |
Online reliability: No scheduled downtime allowed within the online scheduled hours of service.
|
Duration of unscheduled outages not to exceed 1 hour per occurrence for software faults and 3 hours for hardware faults during Scheduled Hours of Service. |
2 Hours |
Point of Service Delivery |
User terminal |
|||
Measurement period |
Monthly |
Monthly |
Monthly |
Weekly/Monthly |
Responsibility for measurement |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Enterprise Intelligence Unit |
Reporting frequency |
3 hours |
Monthly |
Monthly |
Weekly/Monthly/Quarterly |
Measurement method/rules and/or calculations |
Measurement data will be obtained from Freshservice. |
Measurement data will be obtained from Freshservice. |
Measurement data will be obtained from Freshservice. |
Based on the total time to respond (TTR) |
3 Switching Services
3.1 Switching Services Details
Service Name: NIBSS Instant Payment |
|
Service Customer:
|
|
Service Owner: Instant Payment Operations |
||
|
|
|
||||
Description and Scope: · Support internal and external clients on the NIP platform. · Service availability monitoring. · Network with all connecting Institutions (Banks, MFBs, MMOs, OFIs, PSSPs, PSBs) and NIBSS Client Services. · Execution of all approved NIP projects. · Support Head, Technology Operations. · Work with the ER team for error-free DR exercise.
|
|
Service Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition):
|
|
|||||
| ||||||
|
|
|
||||
Service Assets
|
|
Class of Service
|
||||
3.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Required service level |
On-line scheduled hours of host availability to support the above applications will be not less than 99.9% 24X7 |
Online reliability: No scheduled downtime allowed within the online scheduled hours of service.
|
Duration of unscheduled outages not to exceed 0.5 hour per occurrence for software faults and 0.5 hour for hardware faults during Scheduled Hours of Service. |
15 minutes |
Point of Service Delivery |
User terminal |
|
|
|
Measurement period |
Monthly |
Monthly |
Monthly |
Weekly/Monthly |
Responsibility for measurement |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Enterprise Intelligence Unit |
Reporting frequency |
3 hours |
Monthly |
Monthly |
Weekly/Monthly/Quarterly |
Measurement method/rules and/or calculations |
Based on the number of Server and Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the total time to respond (TTR) |
4 Payment Terminal Service Aggregator (PTSA) Services
4.1 PTSA Services Details
Service Name: Payment Terminal Service Aggregator |
|
Service Customer:
|
|
Service Owner: PTSA |
||
|
|
|
||||
Description and Scope: · Support internal and external clients on the POS platform. · Service availability monitoring. · Network with all connecting Institutions (Banks, MFBs, MMOs, OFIs, PSSPs, PSBs) and NIBSS Client Services. · Execution of all approved PTSA projects. · Support Head, Technology Operations. · Work with the ER team for error-free DR exercise.
|
|
Service Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition): This service manages the platform used for acquirer's terminal aggregation and switching in POS transactions |
|
|||||
| ||||||
|
|
|
||||
Service Assets
|
|
Class of Service
|
||||
4.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Required service level |
On-line scheduled hours of host availability to support the above applications will be not less than 99.9% 24X7 |
Online reliability: No scheduled downtime allowed within the online scheduled hours of service.
|
Duration of unscheduled outages not to exceed 0.5 hour per occurrence for software faults and 0.5 hour for hardware faults during Scheduled Hours of Service. |
15 minutes |
Point of Service Delivery |
User terminal |
|
|
|
Measurement period |
Monthly |
Monthly |
Monthly |
Weekly/Monthly |
Responsibility for measurement |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Enterprise Intelligence Unit |
Reporting frequency |
3 hourly |
Monthly |
Monthly |
Weekly/Monthly/Quarterly |
Measurement method/rules and/or calculations |
Based on the number of Server and Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the total time to respond (TTR) |
5 NIBSS Automated Clearing/Payment System Services
5.1 NIBSS Automated Clearing/Payment System Services
Service Name: NIBSS Automated Clearing/Payment System Services |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|
||||
Description and Scope:
|
|
Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition): This service provides interfaces with connecting institutions to the clearing and payment solutions to transmit transactions, receive payment files and download reports. This system also enables the generation of weekly billing file for revenue collection from the participating Banks for clearing, payment and settlement. |
|
|||||
| ||||||
|
|
|
||||
Service Assets
|
|
Class of Service Standard
|
||||
5.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Required service level |
On-line scheduled hours of host availability to support the above applications will be not less than 99.9% 24X7 |
Online reliability: No scheduled downtime allowed within the online scheduled hours of service. |
Duration of unscheduled outages not to exceed 0.5 hour per occurrence for software faults and 0.5 hour for hardware faults during Scheduled Hours of Service. |
15 minutes |
Point of Service Delivery |
User terminal |
|
|
|
Measurement period |
Monthly |
Monthly |
Monthly |
Weekly/Monthly |
Responsibility for measurement |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Enterprise Intelligence Unit |
Reporting frequency |
3 hourly |
Monthly |
Monthly |
Weekly/Monthly/Quarterly |
Measurement method/rules and/or calculations |
Based on the number of Server and Application downtimes reported on the Orion and Freshservice IT Service desk portal. |
Based on the number of Server and Application downtimes reported on the Orion and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the total time to respond (TTR) |
6 Identity Management Services
6.1 Identity Management Services
Service Name: Identity Management Services |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|
||||
Description and Scope:
|
|
Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition): This service provides customers with a repository of bank customers’ account information and biometric and demographic data which is used to validate customers for financial transactions. |
|
|||||
| ||||||
|
|
|
||||
Service Assets
|
|
Class of Service Standard
|
||||
6.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Required service level |
On-line scheduled hours of platform availability will be not less than 99.9%
|
Online reliability: No scheduled downtime allowed within the online scheduled hours of service.
|
Duration of unscheduled outages not to exceed 1 hour per occurrence for software faults and 3 hours for hardware faults during Scheduled Hours of Service. |
2 hours |
Point of Service Delivery |
User terminal |
|||
Measurement period |
Monthly |
Monthly |
Monthly |
Weekly/Monthly |
Responsibility for measurement |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Enterprise Intelligence Unit |
Reporting frequency |
3 hours |
Monthly |
Monthly |
Weekly/Monthly/Quarterly |
Measurement method/rules and/or calculations |
Based on the number of Server and Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the total time to respond (TTR) |
7 Web Operations and Portal Services
7.1 Web Operations and Portal Services Details
Service Name: Web Operations and Portal Services |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|
||||
Description and Scope:
|
|
Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition): This service provides a platform for collections. |
|
|||||
| ||||||
|
|
|
||||
Service Assets
|
|
Class of Service Standard
|
||||
7.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Required service level |
On-line scheduled hours of platform availability will be not less than 99.9%
|
Online reliability: No scheduled downtime allowed within the online scheduled hours of service.
|
Duration of unscheduled outages not to exceed 1 hour per occurrence for software faults and 3 hours for hardware faults during Scheduled Hours of Service. |
2 hours |
Point of Service Delivery |
User terminal |
|||
Measurement period |
Monthly |
Monthly |
Monthly |
Weekly/Monthly |
Responsibility for measurement |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Enterprise Intelligence Unit |
Reporting frequency |
3 hours |
Monthly |
Monthly |
Weekly/Monthly/Quarterly |
Measurement method/rules and/or calculations |
Based on the number of Server and Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the total time to respond (TTR) |
8 Payment Processing and Reconciliation Services
8.1 Payment Processing and Reconciliation Services
Service Name: Payment Processing and Reconciliation Services |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|
||||
Description and Scope:
|
|
Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition): This service provides a platform for Corporate and Government institutions to transmit payment files and receive payment reports and connects to other sub-components that enables account validation or balance enquiry. |
|
|||||
| ||||||
|
|
|
||||
Service Assets
|
|
Class of Service Standard
|
||||
8.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Required service level |
On-line scheduled hours of platform availability will be not less than 99.9%
|
Online reliability: No scheduled downtime allowed within the online scheduled hours of service.
|
Duration of unscheduled outages not to exceed 1 hour per occurrence for software faults and 3 hours for hardware faults during Scheduled Hours of Service. |
2 hours |
Point of Service Delivery |
User terminal |
|||
Measurement period |
Monthly |
Monthly |
Monthly |
Weekly/Monthly |
Responsibility for measurement |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Application: Service Owner Server: Compute & Storage Operations |
Enterprise Intelligence Unit |
Reporting frequency |
3 hours |
Monthly |
Monthly |
Weekly/Monthly/Quarterly |
Measurement method/rules and/or calculations |
Based on the number of Server and Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of Server & Application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the total time to respond (TTR) |
9 Application Support
9.1 Application Support Service Details
Service Name: Application Support |
|
Service Customer: External clients
|
|
Service Owner:
|
||
|
|
|
||||
Description and Scope: Provide 3rd level technical support on business applications to external customers.
|
|
Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition): This service provides NIBSS with a one-stop-shop for all its requirements in the area of requirement definition, design, development, deployment and maintenance of business applications that are required to perform routine business processes. |
|
|||||
| ||||||
|
|
|
||||
Service Assets
|
|
Class of Service Standard
|
||||
9.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Business Applications Management |
On-line scheduled hours of application availability will be not less than 99.9% 24x7x365 |
Online reliability: No scheduled downtime allowed within the online scheduled hours of service.
|
Duration of unscheduled outages not to exceed 1 hour per occurrence for software faults and 3 hours for hardware faults during Scheduled Hours of Service. |
15 minutes |
Point of Service Delivery |
User terminal |
|||
Measurement period |
Monthly |
Monthly |
Monthly |
Weekly/Monthly |
Responsibility for measurement |
Application: Service Owner |
Application: Service Owner
|
Application: Service Owner |
Enterprise Intelligence Unit |
Reporting frequency |
3 hours |
Monthly |
Monthly |
Weekly/Monthly/Quarterly |
Measurement method/rules and/or calculations |
Based on the number of application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the number of application downtimes reported on the SolarWinds Orion monitoring tool and Freshservice IT Service desk portal. |
Based on the total time to respond (TTR) |
10 Data Centre Services
10.1 Data Centre Service Details
Service Name: Data Centre Management |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|
||||
Description and Scope:
|
|
Service Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition): A highly available and standard datacentre maintenance which supports the uptime of NIBSS services. |
|
|||||
| ||||||
|
|
|
||||
Service Assets
|
|
Class of Service Standard
|
||||
10.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Required service level
|
On-line scheduled hours of datacentre availability will be not less than 99.982% 24x7x365
|
Online reliability: No scheduled downtime allowed within the online scheduled hours of service.
|
Duration of unscheduled outages not to exceed 0.5 hour per occurrence for software faults and 1 hour for hardware faults during Scheduled Hours of Service. |
2 Hours |
Applications
|
|
|
|
|
Service point of delivery |
Datacentre |
|||
Measurement period |
Monthly |
Monthly |
Monthly |
Monthly |
Responsibility for measurement |
Datacentre Team |
Datacentre Team |
Datacentre Team |
Enterprise Intelligence Unit |
Reporting frequency |
Monthly |
Monthly |
Monthly |
Monthly |
Measurement method/rules and/or calculations |
[Period – Downtime] x100 Period |
Based on the number of Server/Datacentre incidents reported. |
Based on the number of Server/Datacentre incidents reported. |
Based on the total time to respond (TTR) |
11 Network Management Services
11.1 Network Management Details
Service Name: Network Management |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|
||||
Description and Scope:
|
|
Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition):
|
|
|||||
| ||||||
|
|
|
||||
Service Objects LAN
WAN
Internet Access Service Objects
|
|
Class of Service: Standard
|
||||
11.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Provision of LAN, and WAN service |
Service availability should be greater than 99.9% (LAN), 99.8% (WAN)
|
Not to exceed 1 per month based on a 3-month rolling average |
Not less than 90% of all faults affecting availability to be resolved within: LAN: 4 (four) hours. WAN: 6 (six) hours. |
2 hours |
Provision of Internet access service |
Scheduled hours of Service: 24x7x365 |
Not to exceed 1 outage per month during Scheduled Hours of Service |
Not to exceed 1 hour per outage during Scheduled Hours of Service. |
Where there is PoP (24 hours) Where there is no PoP (5 work Days) |
Service point of delivery |
LAN & WAN: Access via data point connection Internet: Access via LAN from user terminal. |
|||
Measurement period |
Monthly |
Monthly |
Monthly |
Monthly |
Responsibility for measurement |
Network Operations |
Network Operations |
Network Operations |
IT Service Desk |
Reporting frequency |
Weekly |
Weekly |
Weekly |
Weekly |
Measurement method/rules and/or calculations |
As recorded by WAN/LAN monitoring systems (i.e. SolarWinds Orion)
|
Based on number of LAN/WAN/Internet incidents reported.
|
Based on data obtained from Service Desk application |
Based on the total time to respond (TTR) |
12 Compute & Storage Services
12.1 Compute & Storage Services Details
Service Name: Compute & Storage |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|
||||
Description and Scope:
|
|
Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition):
|
|
|||||
| ||||||
|
|
|
||||
Service Objects
|
|
Class of Service: Standard
|
||||
12.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Required Service Levels |
On-line scheduled hours of Server and Storage availability will be not less than 99.9% 24x7x365
|
No scheduled outage allowed within Scheduled Hours of Service. Scheduled outages must be authorized. |
99% of unscheduled outages to have duration no longer than 30 minutes. |
2 hours |
Point of Service Delivery |
User terminal |
|||
Measurement period |
Weekly/Monthly |
Monthly |
Monthly |
Weekly/Monthly |
Responsibility for measurement |
Compute & Storage Operations |
Compute & Storage Operations |
Compute & Storage Operations |
Enterprise Intelligence Unit |
Reporting frequency |
Weekly/Monthly |
Monthly |
Monthly |
Weekly/Monthly/Quarterly |
Measurement method/rules and/or calculations |
Measurement data will be obtained from SolarWinds Orion. |
Measurement data will be obtained from SolarWinds Orion. |
Measurement data will be obtained from SolarWinds Orion. |
Based on the total time to respond (TTR) |
13 Software Development
13.1 Software Development Service Details
Service Name: Software Development |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|
||||
Description and Scope: 1. Software development – Internal process automation 2. Software development – Customer facing solutions 3. Process automation 4. Integration |
|
Service Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition):
|
|
|||||
| ||||||
Service Assets
|
|
Class of Service Standard
|
||||
13.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Required service level
|
On-line scheduled hours of application availability will be not less than 99.9% during the periods |
Online reliability: No scheduled downtime allowed within the online scheduled hours of service. |
Duration of unscheduled outages not to exceed 0.5 hour per occurrence for software faults and 1 hour for hardware faults during Scheduled Hours of Service. |
2 Hours |
Service point of delivery |
User Terminal |
|||
Measurement period |
Monthly |
Monthly |
Monthly |
|
Responsibility for measurement |
Application Support Team |
Application Support Team |
Application Support Team |
Application Support Team |
Reporting frequency |
Monthly |
Monthly |
Monthly |
Monthly |
Measurement method/rules and/or calculations |
[Period – Downtime] x100 Period |
[Period – Downtime] x100 Period |
Measured outage hours |
Based on the total time to respond (TTR) |
14 Information Security Services
14.1 Information Security Services Details
Service Name: Information Security |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|||||
|
|
|
||||
Description and Scope: Security of IT applications and services to support business processes. |
|
Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition):
|
|
|||||
| ||||||
|
|
|
||||
Service Objects
|
|
Class of Service Standard |
||||
14.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Enterprise Security |
Service availability should be greater than 99.9%, 24 x 7 x 365 |
No failures in recovery |
Not Applicable |
2 hours |
Service point of delivery |
Network Perimeter and User Terminals
|
|||
Measurement period |
Monthly |
Monthly |
Monthly |
Monthly |
Responsibility for measurement |
IT Enterprise Security |
IT Enterprise Security |
IT Enterprise Security |
IT Service Desk |
Reporting frequency |
Monthly |
Monthly |
Monthly |
Monthly |
Measurement method/rules and/or calculations |
Measurement data will be obtained from the various security tools (InsightVM, Nessus) as well as the monitoring server (Orion). |
Measurement data will be obtained from the various security tools (InsightVM, Nessus) as well as the monitoring server (Solar winds). |
For each downtime occurrence, the IT Enterprise security team would compute and record the duration of the downtime. |
Based on the total time to respond (TTR) |
15 Client Computing Services
15.1 Client Computing Service Details
Service Name: Client Computing Service |
|
Service Customer:
|
|
Service Owner:
|
||
|
|
|||||
|
|
|
||||
Description and Scope:
|
|
Elements:
|
||||
| ||||||
|
|
|||||
Customer Benefits (value proposition):
|
|
|||||
| ||||||
|
|
|
||||
Service Objects
|
|
Class of Service Standard
|
||||
15.2 Agreed Service Level
Measures |
Availability |
Reliability |
Serviceability |
Response |
Required service level
|
On-line scheduled hours of availability will be not less than 99.9% during the periods:
|
Online reliability: No scheduled downtime allowed within the online scheduled hours of service.
|
Duration of unscheduled outages not to exceed 0.5 hour per occurrence for software faults and 1 hour for hardware faults during Scheduled Hours of Service. |
2 Hours |
Service point of delivery |
User Terminal |
|||
Measurement period |
Monthly |
Monthly |
Monthly |
Weekly |
Responsibility for measurement |
Helpdesk team |
Helpdesk team |
Helpdesk team |
Enterprise Intelligence Unit |
Reporting frequency |
Monthly |
Monthly |
Monthly |
Weekly/Monthly |
Measurement method/rules and/or calculations |
Measurement data will be obtained from Freshservice. |
Measurement data will be obtained from Freshservice. |
Measurement data will be obtained from Freshservice. |
Based on the total time to respond (TTR) |
16 External Service Providers
This section in simple form, list of services offered/to be offered/was offered by a service provider.
S/N |
Supplier Name |
Services |
Supplier Address |
Department/Unit |
Main Supplier - Contact Person |
Main Supplier - Emails |
Main Supplier -Phone Numbers |
1 |
Main One |
Collocation |
Chief Chuks Ikokwu Street, Graceland Estate, Ajah, Lagos |
Data Centre Operations |
Gbolahan Atoyebi |
|
08077777268 |
2 |
Inlaks |
Data Centre Infrastructure Maintenance |
1611 Adeola Hopewell St, Victoria Island, Lagos |
Data Centre Operations |
Victor Oyenibi |
08060658712 |
|
3 |
Royal Power |
Data Centre Infrastructure Maintenance |
Amodu Ojikutu Street, 1218B Sam Adegbite Cl, Victoria Island 101241, Lekki |
Data Centre Operations |
Joseph Nkwor |
08025117901 |
|
4 |
Upperlink Limited |
Domain Hosting services |
Plot 4 ASSBIFI Road, Central Business District, Alausa, Ikeja, Lagos |
Network Design & Operations |
Adeola Raji |
08180145994 |
|
5 |
Lotus Beta Analytics Nigeria Ltd |
Microsoft Cloud Services Partner |
Plot 21 Omorinre Johnson, off Mobolaji Johnson Road By Second Roundabout, Lekki Phase 1, Lagos |
System Administration |
Abiodun Olokode
|
09062848361 |
|
6 |
|
|
|
|
|
|
|
7 |
|
|
|
|
|
|
|
8 |
|
|
|
|
|
|
|
9 |
|
|
|
|
|
|
|
10 |
|
|
|
|
|
|
|
11 |
|
|
|
|
|
|
|
12 |
|
|
|
|
|
|
|
13 |
|
|
|
|
|
|
|
14 |
|
|
|
|
|
|
|
15 |
|
|
|
|
|
|
|
16 |
|
|
|
|
|
|
|
17 |
|
|
|
|
|
|
|
18 |
|
|
|
|
|
|
|
19 |
|
|
|
|
|
|
|
20 |
|
|
|
|
|
|
|
21 |
|
|
|
|
|
|
|
22 |
|
|
|
|
|
|
|
24 |
|
|
|
|
|
|
|
25 |
|
|
|
|
|
|
|
26 |
|
|
|
|
|
|
|
27 |
|
|
|
|
|
|
|
28 |
|
|
|
|
|
|
|
29 |
|
|
|
|
|
|
|
30 |
|
|
|
|
|
|
|
31 |
|
|
|
|
|
|
|
32 |
|
|
|
|
|
|
|
34 |
|
|
|
|
|
|
|
35 |
|
|
|
|
|
|
|
36 |
|
|
|
|
|
|
|
37 |
|
|
|
|
|
|
|
38 |
|
|
|
|
|
|
|
39 |
|
|
|
|
|
|
|
40 |
|
|
|
|
|
|
|
41 |
|
|
|
|
|
|
|
42 |
|
|
|
|
|
|
|
43 |
|
|
|
|
|
|
|
44 |
|
|
|
|
|
|
|
45 |
|
|
|
|
|
|
|
46 |
|
|
|
|
|
|
|
47 |
|
|
|
|
|
|
|
17 Appendix: Acronyms
POS
Point of Sale-Payment terminal for processing e-Channels transactions.
NOC
Network Operating Centre- A location from which network management including network monitoring and control is done.
TTR
Time taken to respond to a new incident/ request.
LAN
Local Area Network – the infrastructure that connects all the IT equipment at a site.
WAN
Wide Area Network – the infrastructure that connects sites together.