Scope of work RFB 030/15-16 Provision of MPLS WAN Service to the NHLS for a period of three (3) years
Acronyms
MPLS – Multiprotocol Label switching
VPN – Virtual Private Network
PE – Provider Edge
CE – Customer Edge
SIEM – Security Incidents and Events Management
FTP – File Transfere Protocol
AV – Antivirus
LAN – Locala Area Network
WAN – Wide Area Networl
QOS – Quality of Service
CoS - Class of service
SLA – Service Level Agreement
APN – Access Point Name
VSAT - Very Small Aperture Terminal
Page 1 of 18
NOC – Network Operations Centre
POP – Point of precense
IPS – Intrusion Prevetion Systems
NRC – Non reoccuring cost
MRC – Monthly reoccuring cost
1. Background
The NHLS has WAN that covers approximately 266 sites countrywide. This WAN infrastructure is made up of MPLS cloud network ,Telkom
point to point diginet links, Neotel Metro-e, Neotel Neolinks, Broadlink wireless links, Durban/Ethekwini-Metro metroconenct links, Telkom VSAT
links, MTN 3G based links using private NHLS APN and internet based 3G using IPSec. These links are used to connect NHLS labs and offices
to NHLS data centres located in Braamfontein and Sandringham head office respectively. See attached WAN diagram. Our LAN is segmented
partially.
1.1 Current Network Architecture
The current WAN infrastructure is has been Outsourced. The current service provider manages and monitors our WAN. The LAN, FIREWALLS,
INTERNET and a few of NEOTEL Links is being managed internally by the Network team. Different models of HP and Cisco switches are used on
the LAN and Cisco routers are used on WAN. See table below with a list of device type and see attached WAN diagram showing the current
layout of NHLS WAN and how different sites are connected to the network. For details on device models, see attached inventory list.
Summary of the device types
Page 2 of 18
Machine Type
Cisco 1841
Total
113
Cisco 1921/K9
37
Cisco 1941K9
52
Cisco 2801
52
Cisco 2811
23
Cisco 3745
1
Cisco 3845
1
Catalyst 65XX
4
Procurve Switch 2524
Procurve Switch 2610-24
Procurve Switch 261024-PWR
Procurve Switch 26-1048
Procurve Switch 2610-48
PWR
8
24
1
17
2
Procurve Switch 2626
6
Procurve Switch 2650
31
Procurve Switch 2824
1
Procurve Switch 410GL
2
Procurve Switch 4108GL
1
Procurve Switch 4208VL
2
Procurve Switch 5308xl
1
Procurve Switch 5304XL
1
Procurve Switch 5406zL
4
Page 3 of 18
IOS Versions per device
IOS_Version_for_Cis
co_Devices-11June2012 V2.xls
NHLS WAN Diagram
NHLS-WAN.PNG
1.2
NHLS sites list
Page 4 of 18
1.2.1 MPLS sites
NHLS-Site List.xlsx
1.2.2 Broadlink sites
Termination Point
Line
Speed
Circuit
number
Backhaul
NHLS - Kalafong
1 Modderfontein Sandringham
512 Kbps
GP1462
No
GP NHLS Braamfontein Hospital
1 Modderfontein Sandringham
2Mbps
GP0952
No
1 Prince Street Public Health
Head Office, Durban
512Kbps
KZ0172
No
512Kbps
2Mbps
GP0711
No
1 Modderfontein Sandringham
2Mbps
GP0940
No
GP NHLS Kalafong
1 Modderfontein Sandringham
512Kbps
GP1462
No
NHLS - Medunsa
1 Modderfontein Sandringham
2 Mbps
GP1460
No
NHLS - Rustenburg
1 Modderfontein Sandringham
512Kbps
NW0024
No
NHLS Port Elizabeth (incl. backhaul)
1 Modderfontein Sandringham
4Mb
PE0010 /
BH0052
Yes
NHLS Universitas Bloemfontein
1 Modderfontein Sandringham
4Mb
FS0019/BH
TBC
Yes
Site Name
KZ Greys Hospital
NHLS_Coronation
Hospital_Coronationville
NHLS_Helen Joseph
Hospital_Rossmore
GP Baragwanath Hospital
1 Modderfontein Sandringham
1 Modderfontein Sandringham
Page 5 of 18
GP0712
No
NHLS - Pelonomi Hospital
Universitas Bloemfontein
2Mb
Page 6 of 18
FS0020
No
1.2.3 Durban Metro-connect sites
B site
Reference number
Line
Size
A site
149 Prince street durban
Management Link to FirstTech
1008010010
512Kb
149 Prince street durban
1008010011
2Mb
149 Prince street durban
Inkos Albert Luthuli Central
King Edward VIII Hospital
1008010021
512Kb
149 Prince street durban
Clairwood Hospital
1008010015
512Kb
149 Prince street durban
RH Khan
1008010022
512Kb
149 Prince street durban
Prince Mshiyeni Hospital
1008010019
512Kb
149 Prince street durban
King George V
1008010016
512Kb
149 Prince street durban
Wentworth
1008010020
512Kb
149 Prince street durban
Mahatma Gandhi
1008010018
512Kb
149 Prince street durban
Addington Hospital
1008010014
512Kb
149 Prince street durban
KwaMashu Poly
1008010017
512Kb
1.2.4 Telkom VSAT site
Circuit Number
NHL0001
Lab name
Catherine
Booth
NHL0002
Mbongolwane
NHL0003
St Appolinaries
NHL0004
Helen Franz
NHL0005
Natalspruit
NHL0006
Zebediela
VSAT
Bandwidth
Physical address
N2 North, Amatikulu Sugar Mill turn-off, 11 km past mill.
N2 to Ulundi/Melmoth turn-off, left at Eshowe/Nkandla
turn-off + 30 km to Ntumeni, left to Pett Store, turn right,
+15 km to school, turn right, + 3 km
From Ixopo take road to Denebrook, then left and take
road to Creighton. From Creighton take the gravel road
for 15 km and the hospital is near Centow Mission,
Centocow.
Helen Franz Hospital, Senwabarwana Township 0790
Shared
256kb/256kb
NHLS Lab –New Vosloorus Hospital Stand number
1230 Nguza street , Extension 14 Vosloorus Gauteng
Zebediela Hospital, Magatle village, Limpopo Province
NHLS Lab-Glen Grey Hospital, 65 Indwe Road, LadyFrere, Eastern Cape
NHL0007
Glen Grey
NHL0008
Canzibe
Canzibe Hospital in Eastern Cape province
NHL0013
Qumbu
Main Street, Qumbu, Eastern Cape
Page 7 of 18
1.2.5 MTN 3G Site using private APN.
Site name
Province
GPS co-ordinates
Greenville
N.TRANSKEI
S30 55.817 E30 06.547
All saints
S.TRANSKEI
S31 39.667 E28 02.817
Madwaleni
S.TRANSKEI
S32 05.831 E28 52.704
Zitulele
S.TRANSKEI
S32 25.781 E28 28.284
Lillian Ngoyi Clinic @ Chris Hani
Baragwanath Hospital
Gauteng
Physical Address
Depo of Bizana east
bizana
out
Potchefstroom Road
close to Chris Hani
Baragwanath
Hospital
1.2.6 Vodacom 3G site
Site
Connection type
Physical Address
Shongwe
GSM 3G – Internet based
IPSec
Shongwe Mission Hospital, Jeppie's Reef Rd, Malelane district
1331
1.2.7 Wireless linked site (PtP NHLS owned)
Site
Connection type
Physical Address
Edenvale
Point-point wireless
Edenvale Hospital, modderfontein Road
1.2.8
ADSL linked site
o Witkoppen Lab.
1.2.9 NEOTEL linked sites
Page 8 of 18
Custom
er name
National
Health
Laborato
ry
Services
National
Health
Laborato
ry
Services
National
Health
Laborato
ry
Services
National
Health
Laborato
ry
Services
Type of
service
NeoMet
ro
Bandwi
dth
2Mbps
Type
of
SLA
99.50
%
Link details
GPRY1-GSCN1EGSCN1001
Service Id's
027JOHA68000327
3306
RFS Date
dd/mm/yyyy
2010/11/09
2Mbps
99.50
%
GNHB1-GNHP1-ET-0001SPP-MISC
027BRAA29200244
3847
NeoLink
4Mbps
99.50
%
GNHB1-KNHD1-ET-0001SPP-MISC
027BRAA29200155
4650
2009/05/27
NeoLink
2Mbps
99.50
%
GNHP1-GNHS1-ET-0001SPP-MISC
027JOHA29200244
3831
2010/03/23
NeoLink
Page 9 of 18
2010/03/18
Station A
SITA, John
Vorster
Drive,
Centurion,
Pretoria
Cnr
Hospital
and De
Korte
Street,
Braamfonte
in
Cnr
Hospital
and De
Korte
Street,
Braamfonte
in
7 York
Road,
Parktown,
Johannesb
urg
Station B
1
Modderfont
ein Road,
Sandringha
m,
Johannesb
urg
7 York
Road,
Parktown,
Johannesb
urg
149 Prince
Street,
Durban
1
Modderfont
ein Road ,
Sandringha
m
National
Health
Laborato
ry
Services
National
Health
Laborato
ry
Services
National
Health
Laborato
ry
Services
National
Health
Laborato
ry
Services
National
Health
Laborato
ry
Services
NeoLink
NeoLink
NeoMet
ro
2Mbps
99.50
%
GNHS1-GVEG1-ET-0001SUN-MISC
027JOHA29200216
5221
4Mbps
99.50
%
GNHS1-KNHD1-ET-0001SPP-MISC
027JOHA29200155
4666
2Mbps
99.00
%
GNSB1-GNSB1EGNATHE001
027JOHA68000461
2483
2009/11/16
2009/05/27
2011/11/23
NeoMet
ro
2Mbps
99.00
%
GNSB1-GNSB1ENAIHE001
027BRAA68000461
2505
2011/11/18
NeoInte
rnet
5Mbps
99.50
%
GNST1-GSAT1IGNHB001
027JOHA27800080
7994
2010/05/19
Page 10 of 18
1
Modderfont
ein Road ,
Sandringha
m
1
Modderfont
ein Road ,
Sandringha
m
NHLS 1
Modderfont
ein Road
Sandringha
m
Johannesb
urg
GAUTENG
2192
Cnr
Hospital
and De
Korte
Street,
Braamfonte
in
North
Station
POP Rissik
Street,
Johannesb
Verizon
113
Bowling
Avenue,
Gallo
Manor
149 Prince
Street,
Durban
NHLS
Prinshof
Campus Dr
Savage
Drive
.
Pretoria
GAUTENG
0001
NHLS
Prinshof
Campus Dr
Savage
Drive
.
Pretoria
GAUTENG
0001
Cnr
Hospital
and De
Korte
Street
urg
National
Health
Laborato
ry
Services
National
Health
Laborato
ry
Services
NeoMet
ro
NeoMet
ro
2Mbps
100Mbp
s
99.50
%
99.50
%
WCCT1-WGAH1EWOLDHS001
GNST1-GNST1EGMODROC001
027CAPE68000327
2351
027JOHA68000333
9310
Page 11 of 18
2011/07/10
2011/02/09
Old
Hospital
Complex,
Portswood
s Road,
Green
Point,
Cape Town
1
Modderfont
ein Road,
Sandringha
m,
Johannesb
urg
Braamfonte
in
112
Harrington
Street,
Cape Town
Corner De
Korte and
Hospital
Road,
Braamfonte
in
1.3 Applications used at NHLS

ERP – Oracle EBS centralised

TrakCare Lab ( Laboratory Information System ) centralised – publised on Citrix

CDW – Netezza Data Warehouse an Oracle based Coporate Data Warehousing- centralised

Email – Microsoft Exchange – located at different sites (Pretoria, Green point, Sandringham,
Braamfontein).

AV Servers – Sophos for Novell and Microsoft server

AV PC’s – Symantec Endpoint

Document management system – Qpulse

FTP – data replication

ECM – Enterprise Content Management

Internet and Intranet
1.4 Current challenges with the NHLS WAN infrastructure

Complex network architecture

Monitoring
2. Objectives of the MPLS VPN tender.

Simplify the NHLS WAN architecture

Eliminate single point of failure on network devices for selected critical sites by implimenting
redundant/dual LAN and WAN devices.

Improve uptime of the WAN infrastructure.

Move away from the legacy methods of connectivity (i.e. Expensive long haul point-to-point links)
to a cloud based MPLS VPN solution.

Cut costs of managing and running of the WAN infrastructure.
Page 12 of 18

Move away from CAPEX to OPEX financial model for the WAN environment.

Eliminate single point of failure on network links by implementing backup links in either load
sharing configuration or primary/secondary link configuration at selected critical sites. Where
possible backup links must be of different technology or from a different service provider. If the
backup link used is the same as the primary link, then it must be installed using different routes
and terminating at different POP (e.g. diginet link must terminate at different exchange and used
different path to the client sites).

Attach SLA on each link and WAN device to ensure uptime of between 99.5 % – 99.95%
depending on the sites requirements.

Minimize number of sites affected by provider’s trunk link failures. Fewer sites must share same
trunk infrustructure from one provider.

Quick resolution time to connectivity problems (within SLA).
3. NHLS Requirements
NHLS hereby invites service provider to provide the following on a 3 year contract, with an option
to renew for 2 years maximum on a yearly basis.
3.1.1 Fully managed secure layer 3 (MPLS) Multiprotocol Label switching network services to
connect NHLS’s production and disaster recovery data centers to all NHLS Laboratories and
offices accross the country. Note that NHLS reserves the right to add and remove sites at
its discretion.
3.1.2 Provide access routers and/or re-use of existing routers until they reach end of life or end of
support. See above invetory list of makes and model of devices with IOS software versions.
3.1.3 Provide physical access circuits or re-use of existing circuits to connect to the MPLS cloud
nearest POP for all sites listed in the table below. Allocate bandwidth and apply QOS as per
NHLS requirements. In-case of new links the provider is expected to procure the link and
impliment. Where existing links are used, NHLS and the successful vendor will engage the
supplier of the existing link to move ownership of the link/s to the successful service provider
on the same or better term and conditions.
3.1.4 Add SLA to all links, so that the required uptime target for each site as specified on the table
below is archieved.
3.1.5 Securely configure access devices (CE) and the MPLS core network devices to ensure that the
confidentiality and integrity of NHLS data is mantained.
3.1.6 Provide a high availability/resilient MPLS backbone infrastructure. A list of MPLS POPs must
be provided accompanied with detailed diagram showing how the POPs are connected. A
Page 13 of 18
description of the level of redundancy and fail over process within the cloud must also be
provided.
3.1.7 Supply and install network links (access circuits) or re-use of the existing links (depending on
existing contracts and agreement from the existing suppliers with NHLS). Supplier will be
required to take over the existing contracts where the existing contract are less than the
duration of MPLS contract, that NHLS will enter into with the successful supplier.
3.1.8 The supplier can use existing networking equipment where possible or buy back equipment at
a reasonable price.
3.1.9 Work with NHLS resources to ensure end to end commutation for all sites during the migration
and after the migration phase.
3.1.10 Provide advice to NHLS on the best possible setup/configuration to ensure high availability on
the LAN to WAN device connections at each site, especially where dual core switches and
dual access routers (CE) are implemented.
3.1.11 Proactive monitoring of all links and devices - taking appropriate action to resolve any issue
that arises within the agreed SLA (e.g. notification of service interruption to selected NHLS
employees and providing regular updates until issue/s have been resolved). The supplier must
provide an SLA which must include significant penalties for non performance.
3.1.12 Provide on demand and monthly reports for the following (Link Utilization, Availability, SLA and
QOS). All reports must be email to NHLS prior to a monthly service review meetings to be held
at NHLS with the NHLS networking and/or senior manager/s.
3.1.13 Communicate all service and non service impacting changes on the network for NHLS
consideration and approval.
3.1.14 Provide NHLS network team and service desk personnel read only access to monitoring tools
and systems used to monitor and manage NHLS network. These tools must provide up/down
status of links and devices, bandwidth utilization, netflow traffic, QOS policies queues etc and
interface errors or discards.
3.1.15 Provide alerting solution, using a combination of email, sms depending on the severity of the
incidents and site/s impacted.
3.1.16 Provide NHLS access to a solution architecture and senior network engineering resources
when required for technical discussions.
3.1.17 Configure QOS for selected services as required by NHLS and reports on configured QOS.
3.1.18 Provided any to any communications for sites on the MPLS cloud.
3.1.19 Ensure that the MPLS network can support VOIP and Video conferencing. Note that NHLS
currently has 3 x sites using the WAN for Video Conference (Sandringham, Durban and
Page 14 of 18
Greenpoint). We also have an IP Telephony solution implemented at Greenpoint complex in
Cape Town with one remote site Kayelitsha lab using the IPT PABX in Greenpoint in VOIP
configuration.
3.1.20 Service provider to play an advisory role for possible new solution that can enhance or
improve NHLS networking infrastructure.
3.1.21 Ensure that the network is configured and working optimally at all times.
3.1.22 Assignment of service manager as single point of contact for queries, service request etc.
3.1.23 Configure QOS for selected services as required by NHLS and reports on configured QOS
3.1.24 Service provider to play an advisory role for possible new solution that can enhance or
improve NHLS networking infrastructure
3.2 QOS requirements per link on the MPLS clouds
QOS bandwidth allocation for all NHLS links connecting to the MPLS clound. SP must be able to support
multiple QOS queues or class of services as detailed below. Where we are running Video Conference on
the WAN link, a separate priority queue must be created and the remainder of the bandwidth will be
allocated using the model below.

60% - Mission critical application (Citrix based TrakCare Laboratory Information System).

20% - Transactional application (HTTP based applications including: Oracle EBS ERP, CDW
(Corporate Dataware house, Active directory and Qpulse).

15% - Bulk applications (Email, Internet and FTP).

5% - Default (any other application not define above i.e AV update and PC patching).
NB: NHLS will provide ip addresses and port number used by different applications for classification and
marking purpose. It is still the service provider responsibility to ensure that everything has been catered
for to esnure that NHLS user gets the best possible application perfomace through the network.
Page 15 of 18
3.2.1 List of sites connected on MPLS cloud.
List of NHLS sites that are connected to the MPLS with their bandwidth and SLA requirements per site – NHLS reserve the right to add or
remove sites from the list as and when it makes business sense or it is cost effective to do so ( before the final scope document has been signed).
For the purpose of this tender, vendors/suppliers are requested to base their response on the following site list and requirements.
Page 16 of 18
4. TENDER Response (format)
4.1 Full description of the solution
4.2 Detailed Technical architecture of the NHLS WAN based on MPLS showing each NHLS site and
MPLS POP, where each NHLS sites will be connecting toincluding the back link, associated
bandwidth and link type that will be used.
4.3 Detailed Technical architecture of the MPLS backbone showing the number, location of MPLS
POP and redundacy deployed within the cloud. Description of the failover process incase of link
or device failure in the cloud.
4.4 Response to NHLS requirement (Section 3) above – all response/answers must be in the same
order of questions and sub questions. Please comment on each line item.
4.5 Site list - Attach list of all sites and indicate per site if you will be able to meet the requirements for
the site (including the following – Physical link, Bandwidth, SLA, redundancy).
4.6 Response to NHLS security requirements (Section 4) above – Answer all question is the same
order.
4.7 NHLS expectation – Please answer or comment on each line item. Detail how you going to meet
these expectations. Use the same order for your answers and comments as in section 5 above.
4.8
Attach a copy of Project Management plan, including a project schedule with estimated time
lines. It must be noted that the cutover will take place after hours at most of the sites to minimize
impact. The plan must take this into account.
4.9 Service level agreement clearly highlighting Call logging and escalation procedures as well as
penalties for non performance.
4.10 Incident management procedure.
4.11 Problem management procedure.
4.12 Change management procedure.
4.13 Assigment of service manager as single point of contact for queries, service request etc.
4.14 Presence (foot print) of the service provider across the country – list of offices and staff
complement at each office. Any partner ship with other service providers must be clearly listed
here.
Page 17 of 18
Page 18 of 18