Royal Saudi Air Force

Directorate of Communications and

Information Technology

Network Engineering and Computer

Center

SPECIFICATIONS AND STANDARDS FOR

NETWORK INFRASTRUCTURE

Version: 5.1
Dated: 29 January 2018

Page 1 of 35
 Document History

Issue No Date Reason for Issue

1.0 9 June 2013 Initial issue

2.0 2 October 2013 Reviewed

3.0 12 May 2014 Various updates

3.1 20 April 2015 Reviewed

3.2 9 June 2015 Various updates by NOC

3.3 17 June 2015 Various updates by NOC

4.0 11 Jan 2016 Various updates

4.1 15 Jan 2016 Various updates

4.2 7 Mar 2016 Additions to Sect 2.1

4.3 19 July 2017 Comm Room & DC Requirements

5.0 1 Sep 2017 General Update

Typo and other minor corrections, no change to

5.1 29 Jan 2017 content meanings. Re-Including the minimum
content for the As Built document set.

Page 2 of 35
 Abbreviations
Abbreviation Definition
AC Air Conditioning
BoQ Bill of Quantity

CITW Communication and Information Technology Wing

DCIT Directorate of Communication and Information Technology
FO Fibre Optic
HLD High Level Design
HQ Head Quarter
IDF Intranet Distribution Frame
IT Information Technology
IP Internet Protocol
ISP Inside Plant
LLD Low Level Design
MPLS Multi-Protocol Label Switching
NECC Network Engineering and Computing Center
NIP Network Implementation Plan
NOC Network Operation Center
NRFU Network Ready For Use
OEM Original Equipment Manufacturer
OSP Out Side Plant
PDU Power Distribution Unit
POE Power Over Ethernet
RSAF Royal Saudi Air Force
SoR Statement of Requirements
SoW Statement of Work
UTP Universal Twisted Pair
VoIP Voice over IP

Page 3 of 35
 Table of Contents
1 Introduction ........................................................................................................... 5
2 Requirements ........................................................................................................ 5
2.1 Generic Requirements .......................................................................................... 5
2.2 Existing LAN Infrastructure Survey ....................................................................... 6
2.3 Design Requirements: .......................................................................................... 7
2.4 OSP Fibre Requirements ...................................................................................... 8
2.5 ISP & UTP Requirements ................................................................................... 10
2.6 Active Component Requirements ....................................................................... 11
2.7 VoIP ..................................................................................................................... 13
2.8 Communications Rooms IT Requirements ......................................................... 14
2.9 Ancillary and C3 systems Requirements ............................................................ 15
3 Implementation .................................................................................................... 18
3.1 Network Implementation Plan ............................................................................. 18
3.2 Network Migration Support ................................................................................. 18
3.3 Implementation Activity ....................................................................................... 19
4 Testing and Commissioning............................................................................... 19
5 Acceptance and Handover ................................................................................. 20
6 Further Information ............................................................................................. 21

Tables
Table 4-1: OSP Specifications ............................................................................................. 30
Table 4-2: ISP Material Specifications ................................................................................. 31
Table 4-3: Cabinet Specifications ........................................................................................ 32
Table 7-1: As Built Document Set ........................................................................................ 35

Appendices
APPENDIX 1: OSP Civil Work Specifications ................................................................... 22
APPENDIX 2: Solution Path .............................................................................................. 28
APPENDIX 3: Generic LAN Schematic ............................................................................. 29
APPENDIX 4: Material Specifications................................................................................ 30
APPENDIX 5: HLD Content ............................................................................................... 33
APPENDIX 6: Acceptance and Handover ......................................................................... 34
APPENDIX 7: Content of As Built Document Set.............................................................. 35

Page 4 of 35
 1 Introduction
The aim of this document is to outline the RSAF IT Networking Requirements for a contractor. It
is not exhaustive but aims to indicate basic standards in use within the RSAF. The document
does not negate the requirement for a local survey by the contractor and does not constitute
generic RSAF design approval in any way. The RSAF HQ DCIT NECC design approval shall
only be granted on approval of a contractor SoW and detailed design documents.

2 Requirements
2.1 Generic Requirements
2.1.1 All the specifications mentioned in this standard document are valid only for six (6)
months from the date of issuance and if there is no change in technology. If the delivery
starts after the expiration date, then the specification shall be returned to RSAF DCIT
for approval.

2.1.2 The contractor should produce a workable, high available network solution that serves
the business requirement of the project and comply with RSAF DCIT network
standards. This solution shall not have any single point of failure in any part of it.

2.1.3 The contractor shall design, supply, install, test, configure, commission and set to work
all the components (OSP, ISP, active) associated with the network solution. This
includes components are needed on the existing core and distribution switches to
connect and integrate with the network components being provided through the project.

2.1.4 The Contractor shall submit all project documentation (HLD, LLD, NIP, NRFU,
operational and test procedures, As-Built documentation) to RSAF DCIT NECC for
review and approval.

2.1.5 All project documentation supplied shall be correctly version numbered and dated. This
includes presentation material.

2.1.6 All network installations are to be an expansion of the RSAF MPLS network. The RSAF
will not approve bespoke disparate network installations for anything apart from very
short term to cope with urgent operational need.

2.1.7 Unless previously agreed with the RSAF, HLD shall be provided by the contractor.

2.1.8 Ordering and procurement shall only be carried out after the agreement of the HLD and
LLD documents by RSAF DCIT.

2.1.9 Records of all serial numbers, part numbers, description, model number, location
installed for assets supplied within the implementation is to be compiled and provided
to the DCIT for input into the ICTMS CMDB.

2.1.10 Contractor or Sub-Contractors shall be qualified and have sufficient experience to carry
out the network tasks. All Sub-Contractors are to be approved by RSAF DCIT.

Page 5 of 35
 2.1.11 Contractors are responsible to provide a complete capability insertion. This will include
concepts, ongoing technical support, documentation, training, etc.

2.1.12 All Cisco devices must be covered under SmartNet Contract for at least 3 years
activated from the handover date or spares switches supplied in lieu of SmartNet as
directed by the DCIT.

2.1.13 All network products (both active and passive) are to be purchased through a local
vendor office and covered with a premium support under the RSAF agreement.

2.1.14 All the IT equipment should be IP based and connected to and integrated with RSAF
network.

2.1.15 All the components shall be labelled by the contractor according to RSAF Standards.

2.1.16 All The licenses must be procured in the RSAF's name and provided to the RSAF during
handover.

2.1.17 The RSAF standards for network monitoring and management tools are Cisco Prime,
Orion Solarwinds, Fluke Network, Microsoft SCOM and APM and the contractor shall
increase the licenses of these existing monitoring systems as required to encompass
monitoring the additional network components.

2.1.18 The contractor is to submit monthly progress reports showing the progress of the work
to RSAF DCIT project officer for review.

2.1.19 For any IT related system not mentioned in this document, a workshop with RSAF DCIT
is to be held to discuss the proposed solution and obtain approval prior to any
procurement or installation.

2.1.20 RSAF DCIT is to approve any deviation from this standard on a case by case basis.
Any deviation is to be clearly stated by the contractor and a meeting held between the
PC, RSAF, and Contractor to discuss and agree way forward for each deviation.

2.2 Existing LAN Infrastructure Survey

A site survey is required to assess the current usage and spare capacity of the network
infrastructure into which the new facilities will integrate. The in-scope facility would, under the
current network design, integrate into the current distribution switches already installed. This
initial assessment should be conducted to capture:

a. The existing manholes and hand holes for fibre connection.

b. The spare fibre, if any, exists between the new in-scope facility and the existing
distribution switches.
c. Where fibre currently runs to the in-scope facility and assessment of the currently
spare number of cores must be determined.
d. The spare capacity, if any, exists within the existing distribution switches to integrate
the new access switches which will be located within the buildings.
e. Whether opportunities exist to expand the current distribution switches to
accommodate the connection of the required additional access switches.
f. The output of the survey needs to be presented to RSAF DCIT and used to produce
the HLD.

Page 6 of 35
 2.3 Design Requirements:
2.3.1 The contractor shall co-ordinate with RSAF DCIT for all design, selection and
installation of IT LAN equipment and shall obtain RSAF approval before any
implementation works.

2.3.2 The Generic solution path for design, implementation and testing to be taken when
designing the network infrastructure solution is shown at APPENDIX 2: and all
documentation should be submitted to RSAF DCIT.

2.3.3 The generic campus layout shall conform to the schematic provided at APPENDIX 3:

2.3.4 Resilience shall be built into any design from the outset. No single points of failure shall
be within the design or implementation.

2.3.5 A set of workshops will be required to agree the design approach and high-level
network architecture (HLD) for any changes required to support the network extension.
The stakeholders for these workshops must be agreed with the DCIT NECC prior to the
commencement of the workshop.

2.3.6 As a minimum, the HLD will contain the details listed at APPENDIX 5:

2.3.7 The output from the design activity is a detailed Low-Level Design document (LLD).
The template for this document is a standard Cisco LLD deliverable.

2.3.8 The LLD document must include the following in addition to the HLD:

a. Routing and Switching Network Architecture.

b. Design Considerations.
c. Design Objectives.
d. Hardware used.
e. Software Versions
f. Connectivity options
g. Physical Network Topology
h. Port Connectivity Tables & Drawings
i. Logical Network Topology.
j. Naming Convention.
k. Layer 2 and 3 setups.
l. IP Addressing.
m. End-to-End Convergence.
n. High Availability.
o. Configuration files.

2.3.9 It is a requirement that the LLD contains sufficient detail on both the configuration of
the switches and the physical locations of the switches to enable a detailed cable
design document to be produced.

Page 7 of 35
 2.3.10 Once the LLD has been produced, the contractor must hold a LLD presentation to
provide DCIT NECC with an overview of the produced design. The contractor will be
responsible for issuing the LLD to the customer and updating the document to reflect
the provided RSAF comments.

2.4 OSP Fibre Requirements

2.4.1 The contractor shall supply, install and test all the outdoor fibre cabling solution and
must be aligned to the LLD document.

2.4.2 At least 24 (twenty four) fibre cores shall be used to connect each building to each of
its IDF distribution switch buildings. Some buildings will require more fibre depending
on its use, but 50% (fifty) spare fibre capacity at least will remain after implementation.

2.4.3 Each facility shall be connected with a minimum of two optical fibre cables to adhere
with the dual resilience design requirement which will be fully detailed within the
network LLD document.

2.4.4 To mitigate the risk of complete network failure in the event of a fibre run being severed
or cut at least 25 (twenty five) metres separation between each fibre run is required.

2.4.5 The exact routing of the external optical fibre cabling shall be surveyed by the contractor
during the design phase and agreed with the RSAF prior to installing the fibre.

2.4.6 All fibre cores shall be terminated.

2.4.7 The Outdoor fibre shall be terminated in the Ground Floor, then from ground floor it
shall connects to all floors using separate Indoor Fibre cables and Patch panels.

2.4.8 The OSP cable shall be labelled every 25m (twenty five).

2.4.9 External optical fibre cabling shall be of a loose tube single-mode (OS1) cable type and
have the following characteristics:

a. Non-metallic RBG central strength member.

b. Layer of stranded elements.
c. Dry interstices.
d. Layer of tapes.
e. Corrugated steel tape armour.
f. Polyethylene outer sheath (labelled with distance measurements to assist with fault
finding activities)

2.4.10 Prior to installation, the contractor shall inspect all optical fibre cabling on the drum and
record the manufacturer certification and batch numbers. After the optical fibre cabling
has been installed the contractor shall perform a commissioning test to confirm point to
point light continuity and optical attenuation of all installed optical fibre cores and
present the results to RSAF DCIT.

2.4.11 The contractor shall ensure that a minimum of 50% optical fibre core capacity is
available after installations have been completed. In instances where the minimum
sizes of fibre cores is inadequate, the Contractor shall install an appropriate multiple of
24 (twenty four) core optical fibre cabling to provide this requirement.

Page 8 of 35
 2.4.12 The contractor shall install optical fibre cabling routed from the building to the IDF
building via diverse routes. Where practical each optical fibre cable should enter the
facility via diverse entry points thus providing dual resilience in the event of a single
cable being accidentally severed or damaged.

2.4.13 The contractor should assume that external inspection chambers containing draw wires
are available for each facility which will support the entry of the new optical fibre into
the building. If no chamber exists it is the responsibility of the contractor to install the
required inspection chamber and associated ducting.

2.4.14 The contractor shall provide all excavations and reinstatement, bedding, cable covers,
markers, joints and terminations forming part of the external optical fibre cable
installations.

2.4.15 Subject to RSAF approval, existing ducts under roadways may be used by the
contractor where sufficient capacity is available.

2.4.16 The contractor should assume that where cable need to traverse taxi ways and other
paved areas, underground ducting with draw wires will be provided. Where new road
crossings are required, optical fibre cabling shall be installed within ducts with duct
capacity not exceeding 70% (seventy), together with draw wires and suitable protection.

2.4.17 All optical fibre cabling to be installed shall be continuous throughout its length with no
joints or splicing other than at terminate ends. Joint fibre cables are not accepted.

2.4.18 All existing below ground mechanical and electrical services in areas of excavation
works shall be identified and if required, diverted or replaced to facilitate the LAN
cabling installation. Diverted services shall be complete with appropriate protection and
route marking.

2.4.19 All fibre runs shall be laid in ducts. These ducts shall conform to the detailed
specifications at APPENDIX 1: and will comply with the requirements below:

a. Trenching shall be excavated to a depth of more than one meter with its base
suitably finished and tamped.
b. The depth of the trench shall be such that the height from the top of the conduit to
the ground shall be not less than one meter.
c. 100mm diameter high density plastic conduit shall be laid in the trench and
protected on all sides by rough cast concrete.
d. Conduits are to be held 30 mm apart and lengths suitably bonded to each other.
e. 100mm sand layer shall be provided at the bottom and top of the conduit.
f. The trench shall be inspected prior to back filling by an RSAF representative.
g. The trench shall be back filled and compacted to a depth of 300mm.
h. Yellow plastic warning tape marked “Fibre Optic Cable” shall be laid upon
compacted material.
i. The trench shall be back filled and compacted to surface level.
j. The surface shall be made good to depth and material of original.
k. Ducts are to be sealed against water ingress using suitable sealing compound.
l. 4mm multi-stranded galvanized steel pull-throughs are to be laid in each duct.
m. A mandrel test shall be carried out after completion of all duct work

Page 9 of 35
 n. All Manholes and hand holes shall be provided with watertight access manhole
cover with “Fiber cables” written in top of it.
o. Jelly filled cables shall not enter the buildings.
p. Manhole Specifications
• Type ‘A’ Manhole: 1500mm wide x 3150mm in length x 2000mm deep.
Manhole must include racks for cable, ladder, grounding bus bar, sump
drain, and expansion plugs installed in un-used conduits.
q. Hand Hole Specifications
• Hand holes vary in size from 1200mm by 1200mm by 1200mm to 2400mm
by 4000mm by 1200mm.
r. Inner Ducts
• Smooth wall or longitudinal ribbed inner duct.
• Preferably tricolour, three inner duct 30mm diameter in 100mm conduit with
colour scheme of orange, blue and white having mule tape or polyethylene
pull rope installed.

2.5 ISP & UTP Requirements

2.5.1 The contractor shall supply, install and test the indoor fibre and UTP solution which
must be aligned to the LLD document.

2.5.2 All network cabling designs shall be provided and to be agreed with RSAF DCIT.

2.5.3 Contractor shall install new optical fibre termination cabinets for the facilities to provide
termination of external optical fibre cabling. Where the agreed cable design details new
fibre terminating in existing facilities that already contain fibre termination cabinets
these may be used, however, new fibre termination cabinets must be supplied by the
contractor if the there is insufficient spare capacity currently exists within the cabinet.
Wherever possible, new fibre termination cabinets must be located adjacent to the
patch panels terminating the internal UTP.

2.5.4 Optical fibre cabling shall be directly terminated on Little Connector (LC) bulkhead
connectors which shall have an insertion loss of no greater than 0.5 dB per connector.
On completion of termination, all LC bulkhead connectors, unused patch panels or
gland holes shall be covered with appropriate dust caps. The optical fibre enclosure for
the LC bulkhead connectors shall be a 1 U 24 (twenty four) way patch panel. For each
1 U of optical fibre patch panel a 1 U horizontal cable management panel shall be
installed. The first 1 position shall only be used for the installation of a cable
management panel.

2.5.5 All internal optical fibre cabling shall be tied off to adequately room containment to
within a minimum of 500 (five hundred) millimetres intervals. All containment installed
shall stand off the wall or floor with a minimum 25 (twenty five) millimetre gap and be
correctly aligned. The optical fibre cabling must not be bent beyond a 150 (one hundred
and fifty) millimetre radius.

2.5.6 The optical fibre cabling shall be suitable to be installed within an enclosed building
environment with a minimum life expectancy of 25 (twenty five) years and be Low
Smoke and Fume (LSF)

Page 10 of 35
 2.5.7 Optical fibre cabling shall be fire stopped when passing through any fire barrier or fire
wall. The outer layer of the optical fibre cabling shall be optimised for abrasion
resistance and fibre processing properties.

2.5.8 The contractor shall provide a minimum of 2 (two) metres servicing loop to optical fibre
cabling termination points, coiled and located on a plinth or under false flooring. ISP
fibre cores and cable management panels shall be provided as required plus a
minimum of 25% (twenty five) spare capacity.

2.5.9 There shall be at least 5 metres of spare UTP inside the cabinet for moving the cabinet
in future.

2.5.10 UTP cabling shall be of the type CAT 6 and providing a minimum bandwidth of 1 (one)
GB to each outlet tap. All cabling shall be continuous throughout its length with no joints
other than at terminate ends. Cable bundles shall be restricted to 48 (forty eight) cables
with individual bundles not tied together.

2.5.11 The number of nodes provided shall be based on site survey but will conform to the
RSAF requirements. For Offices areas 1 (one) TAP is required per 2 (two) square
meters. For other areas, the number of UTP nodes shall be according to the business
need and agreed with the RSAF DCIT NECC which areas are to be considered as office
areas are to be agreed with the RSAF DCIT.

2.5.12 CAT 6 UTP cabling shall connect outlet taps to the network cabinet which shall be
terminated in RJ45 patch panels. The UTP RJ45 patch panel shall be of a 1 U size and
terminated by an Insulation Displacement Connection. For each 1 U of patch panel
installed, a 1 U horizontal cable management panel shall be positioned above.

2.5.13 All TAPs shall be active and the Construction Contractor shall provide suitable capacity
access switches including 25% spare capacity on switch ports after TAPs installation.

2.5.14 Each ISP, UTP cables, Patch panels shall be identified and labelled in accordance with
the agreed naming convention as all cables and outlet TAPs.

2.5.15 The distribution and the final locations of UTP nodes inside the rooms are to be in
accordance with these standards for numbers, distributed in line with the furniture
layout for the rooms and agreed with the RSAF DCIT or base CITW prior to installation.

2.5.16 The maximum length of CAT6 cabling shall be 80 meters.

2.5.17 All the UTP nodes are to be separated from the power outlet in a separate cable tray.

2.5.18 TAPs shall be supplied in floor points in office areas and shall be distributed throughout
the office area. Additional power points in the floor points are to be supplied
commensurate with the number of TAPs.

2.5.19 The contractor is to include a list of rooms included within scope in the HLD together
with its size in square metres and number of TAPs included.

2.6 Active Component Requirements

2.6.1 The contractor is required to procure, install, test, commission and configure all the
network components required to implement the agreed network design defined within
the LLD including the configuration of network management and monitoring tools.

Page 11 of 35
 2.6.2 In order to get the specifications of the active components the contractor shall refer to
the RSAF profile with Cisco.

2.6.3 The Contractor shall provide the RSAF with Cisco certification indicating that all active
components are as RSAF Cisco profile, still on sale items, and that they are supportable
for the upcoming five years after procurement. The type and content of the certificate
to be agreed with DCIT.

2.6.4 All active components should be agreed and HLD or BoQ signed formally by RSAF
DCIT prior any procurement.

2.6.5 If distribution switches are co-located within a building, consideration should be given
to moving one to a separate building to increase resilience. Should a new zone be
required then the distribution switches for these zones are to be placed in different
buildings. The location of the new zone needs to be agreed in the detailed HLD
document.

2.6.6 The contractor should assume that no ports or modules are available in the IDF’s and
a need to provide a new IDF due to the full ports should be considered. The contractor
should do the site survey to get the actual availability. If the IDF is full and no slots are
available, the contractor shall provide two new IDF switches with all required modules
and SFPs based on the agreed HLD.

2.6.7 The Contractor shall provide 1-GIG or 10-GIG module cards (as agreed with DCIT) and
the all SFPs for the existing IDF switches, if there is a free slot in them.

2.6.8 25% spare switch capacity is required after installation of all components.

2.6.9 Each Access Switch in the building shall connect to both the distribution switches in its
respective zone IDF.

2.6.10 All Cisco equipment shall be covered under a premium maintenance contract (Cisco
SmartNet) that shall run for duration of at least three years from the date of the
handover and acceptance.

2.6.11 Access switches shall not be stacked unless formally agreed with the RSAF HQ DCIT
NECC.

2.6.12 Cisco Advanced Services are to be employed to perform design, configuration and
documentation on all RSAF network upgrades unless otherwise agreed on a case-by-
case basis with the RSAF DCIT.

2.6.13 The contractor shall apply the configuration to all active components and integrate them
with RSAF network as per the agreed detailed LLD document.

2.6.14 Only 24 port switches are to be used or as agreed with RSAF DCIT.

2.6.15 Each switch in the IT cabinet shall be connected to two separate UPS units to ensure
resilience.

2.6.16 All Active components are to be placed in a secure dedicated communication room.

2.6.17 All the active components are to be monitored in a central location in the base’s Network
Operation Centre (NOC). The contractor is to provide telepresence solution to enable
the communication with HQ NOC.

Page 12 of 35
 2.6.18 The contractor is to provide a monitoring solution in the central location (NOC) with all
licenses required to monitor all active components which should be licensed also.

2.6.19 All servers shall comply with RSAF DCIT standards and to be placed in the DCIT/CITW
Datacentres.

2.6.20 All WAN circuits are to be Saudi Telecom Company (STC) and all communications with
STC should be officially through RSAF DCIT NECC.

2.6.21 The activities expected to be done the contractor during the configuration of the
components should include, but is not limited to:

a. The contractor will have to liaise with all parties involved and produce a
configuration schedule.
b. Configures any 'backbone' network components such as core and distribution
switches as soon as possible.
c. Aligns the configuration of switches within individual buildings with the RSAF
building construction and handover process.
d. Identification of when each buildings network will be configured and ready for
deployment of IT infrastructure.
e. Arrange any required downtime
f. Manage change control
g. Perform basic connectivity test. Is fibre to core up? Basic ping tests.
h. Check that each switch install matches the documentation. e.g. location in rack,
serial number, fibre numbers. Etc. as defined within the LLDD and detailed cable
design document
i. Put access ports into appropriate VLAN and document.
j. Apply appropriate port settings i.e. 1000 Full or auto-negotiate.
k. Configure as required devices for a smooth integration with existing RSAF networks
(including existing devices)
l. Configure the switches to integrate and be monitored by the RSAF network
monitoring system.
m. Take a copy of the running configuration once switch build is complete. This will
form part of the handover documentation

2.7 VoIP
2.7.1 All phones installed shall be VoIP and integrated with the existing call manager.

2.7.2 The models of IP Phones shall be determined by the category of the user. The following
phones shall be used unless agreed otherwise with the RSAF DCIT:

• Cisco UC Phone 8945. Normal users

• Cisco UC Phone 9971. Executive offices

• Cisco UC Phone 8831. Conference rooms

Page 13 of 35
 • Gai-Tronics TITAN. External locations (weather proof)

2.7.3 VoIP Call Manager licences are to be provided if required and agreed with the DCIT.

2.7.4 All PCs to be slaved to VoIP telephone handsets where possible.

2.7.5 As a minimum standard, one network access point/ VoIP telephone will be installed per
room.

2.8 Communications Rooms IT Requirements

2.8.1 The contractor is responsible to build a communication room and provide all electrical
requirements, air conditioning and cooling requirements to support the installation of
the network design detailed in the LLD.

2.8.2 The communication rooms in the building shall be constructed on the same vertical line
and a vertical shaft shall connect the signal closet vertically. The Signal Closet shall be
in the middle of the Floor or as agreed with RSAF DCIT.

2.8.3 Each floor in the building shall have a communication room at least 3x3m to place all
the network equipment. The size of the room depends on the number of IT cabinets
installed in it. Each room should have a 25% (of its size) free physical capacity after
installing all the cabinets.

2.8.4 The communication room should have sufficient AC, fire alarm system, power, paint,
locks, smart PDUs, CCTV and lights.

2.8.5 The fire system installed in the communication room shall be NOVEC system and
connected to the main panel in the main fire station.

2.8.6 The maximum distance between the communication room and the longest UTP cable
shall be within 80 meters. If the distance is more than 80 Meters then a new
communication room shall be constructed.

2.8.7 All communication rooms shall have a dedicated cooling separate from the building’s
cooling system.

2.8.8 Every IT cabinet in the communication rooms should have a dual UPS in order not to
have a single point of failure when powering up the access switches.

2.8.9 The IT cabinet should have smart IP based PDUs and the number of PDUs is based
on the number of equipment’s in the cabinet. The PDU is to be connected to the RSAF
network in order to monitor it from NOC.

2.8.10 The communication room should have single and three phase power outlets based on
the equipment to be installed in the cabinets.

2.8.11 The communication room is to be secured using push button combination lock and
CCTV camera covering the whole room.

2.8.12 The communication room shall have a temperature meter to monitor the temperature
inside the room and should be connected to the RSAF network.

2.8.13 The communication room temperature shall be maintained at 20-21°C

Page 14 of 35
 2.8.14 Each communications room shall have a wall mounted VoIP phone.

2.8.15 Each Core and Distribution switch shall be protected by a Legrand 20 kva UPS Modular
sufficient to provide power for a period of 30 minutes for building with internal generator
and 2 hours for buildings without internal generator

2.8.16 Each switch cabinet shall be protected by two Legrand UPS units that meets RSAF
standards and sufficient to provide power for the maximum equipment within the
cabinet for a period of 2 hours for buildings without internal generator and for buildings
with internal generator 30 minutes

2.8.17 Each UPS is to be able to operate in bypass mode which, the case of UPS failure, will
still allow main power to operate the switches.

2.8.18 Each UPS should follow RSAF DCIT standards and should be agreed with DCIT prior
any procurement.

2.8.19 The contractor shall provide support for the UPS units including the UPS batteries
replacement for the duration of 3 (three) years from the date of handover.

2.8.20 Each Access layer switch cabinet is to have two fibre patch panels, one connected to
each IDF switch.

2.8.21 All IT cabinets are to be earthed in line with international standards.

2.8.22 All cabinets shall have clearly labelled diagrams on the front door explaining the
connectivity achieved within that cabinet.

2.9 Ancillary and C3 systems Requirements

2.9.1 General Requirements:

a. The C3 systems are access control, CCTV, public address, fire system,
intrusion detection system, telepresence, brief/debrief, master clock,
scramble system, building management system (BMS), Fault Signalling
System and any other system to be connected to RSAF network.

b. All Ancillary and C3 Systems shall be TCP/IP compliant and integrated with
the RSAF network. The contractor shall utilise the existing RSAF General IT
LAN, if available, for implementation of the ancillary systems. The contractor
shall supply and install all ancillary system equipment and additional
accessories, external optical fibre cabling as required, internal optical fibre
and CAT6 UTP cabling, distribution equipment, switches, patch panels and
final connections, as required for the facility to set all systems to work properly.

c. All design approvals for ancillary and C3 systems shall be from the RSAF
DCIT prior to procurement and installation. The design documents shall be
bespoke to the design and not just Original Equipment Manufacturer (OEM).

d. UPS are required for essential C3 Systems to ensure that the systems
operating integrity is maintained, should power fail. Facilities with standby
generators shall be provided with sufficient UPS power for all C3 equipment
to allow the generators to come online. The exact specifications should be
agreed with RSAF DCIT prior to implementation.

Page 15 of 35
 e. All C3 systems are to be covered with a minimum of 3 (three) years vendor
premium support from system handover to the RSAF. The support should
include PMI (Preventative Maintenance Inspection) visits for the duration of
the support. The detail and duration of the PMI should be approved by the
RSAF DCIT.

f. The contractor shall provide formal certified structured training to designated

RSAF personnel to enable independent operation and maintenance of all
ancillary systems installed. Training shall be provided in the form of both
classroom and On-the-Job Training. All instruction shall be performed by
qualified instructors. The contractor shall provide ancillary system technical
information detailing functionality and published in the English language.
Training requirements (type of courses, duration, number of participants,
location etc.) shall be closely co-ordinated and approved by RSAF DCIT.

g. All the workstations or PCs used for C3 systems is to be protected using

Symantec antivirus and integrated with the RSAF Symantec Manager.

2.9.2 Access Control System:

a. The contractor shall supply and install a complete Access Control System to
control access/egress to the facility entrance and secure areas. The system
to be provided shall be agreed by the Contractor with the RSAF DCIT, but will
generally consist of swipe card access, door handle release egress,
collector/controller, magnilock / release door control and main panel within the
reception area.

b. Access control is to be integrated with current access control systems and

RSAF active Directory.

c. The access card will support both physical and logical access.

d. The contractor is to provide a printer that manufacturers HID smart cards to

hold and access information. It is to also have ability to burn and store PKI
certificates.

e. The printer should be able to print RSAF logo and security watermark on both
sides of the card. High quality laminated printing is required.

f. The Access Control system is to be a centralised system that shall be

monitored and given access level permission from RSAF HQ.

g. The Contractor shall provide the required license, enrolment stations, high
resolution plug and play camera and the server as per RSAF Infrastructure
Standard.

h. The access control readers are to be connected to RSAF switches.

i. Final locations and quantities for the access control system will be agreed by
the contractor with the RSAF during detailed design.

2.9.3 CCTV System:

a. The contractor shall supply and install a complete CCTV system to monitor
access/egress at the front entrance, all final exit fire doors and secure areas.

Page 16 of 35
 b. The system shall generally consist of PTZ (Pan Tilt and Zoom) Full HD colour
day/night cameras, multiplexor, split screen monitor, controller and hard drive
& compact disc archive recorder for up to 31 (thirty one) days monitoring with
automatic overwrite. The monitor shall be located at the reception desk.

c. The CCTV system should have the capability to be monitored from a central
location through the network. The contractor is to provide all necessary
components to enable central monitoring.

d. Remote outdoor CCTV cameras are to be connected through fibre and

dedicated power supply. CCTV cameras adjacent to buildings and indoor
CCTV camera shall be connected through UTP cable to the nearest access
switch and use POE.

e. POE is to be utilised to power the UTP connected CCTV camera units.

f. Final locations and quantities for the CCTV System will be agreed with the
RSAF during detailed design.

2.9.4 Public Address System:

a. The Contractor shall supply and install a modern, robust and proven IP based
public address system integrated with the RSAF network.

b. The Public Address System shall provide audible live general announcements
throughout the facility in which it has been installed and from other nominated
facilities on the RSAF Network.

c. Nominated telephone (Paging System) extensions shall also be provided to

enable the announcements onto the Public Address system.

d. The Public Address system shall be integrated with the existing base call
manager.

e. Final locations and quantities for the Public Address system will be agreed by
the contractor with the RSAF during detailed design.

Page 17 of 35
 3 Implementation
3.1 Network Implementation Plan
The following services and deliverables are required:

3.1.1 Crafting and providing a Network Implementation Plan (NIP) at least five (5) business
days before the scheduled commencement of the implementation services.

3.1.2 NIP refers to a document that provides the information necessary to carry out the
implementation of the equipment at the RSAF locations and to verify basic operation
and ready for service configuration.

3.1.3 Ready for service means that the network, or a sub-set of it, is functioning as per the
specifications documented in the NIP. It is a guide for the implementation engineer to
follow. It contains node and site specific information and records the basic tests and
actions carried out.

3.1.4 NIP should capture if there is any need for network migration services to integrate the
new components with the existing RSAF network.

3.1.5 Crafting and providing the Network Ready for Use (NRFU) document.

3.1.6 The NRFU document defines and records the specific set of procedures and/or tests
based on Cisco template and agreed by RSAF that are necessary to test all the network
product and to declare that it is ready for use. Successful test execution will signify
completion of the implementation services.

3.1.7 The NRFU document should include all fibre and UTP testing.

3.1.8 Obtaining sign-off signature from the DCIT for the NIP and NRFU.

3.2 Network Migration Support

The following services are required:

3.2.1 Carrying out a network service migration workshop with DCIT NECC to understand
RSAF's migration requirements and plan the migration steps.

3.2.2 Working with RSAF to draft the NMP (Network Migration Plan), defining the strategy
and detailing the activities, specific steps, as well as the configuration changes that may
be required to migrate the RSAF specified services.

3.2.3 Reviewing the NMP with DCIT for comment and approval, before it is formally released
and completed.

3.2.4 NMP should have proposed time to carry out the downtime and migration services.

3.2.5 Obtaining sign-off signature from the DCIT for the NMP.

Page 18 of 35
 3.3 Implementation Activity
3.3.1 The contractor should have agreed HLD, LLD, NIP and NRFU before starting the
implementation of the network solution.

3.3.2 The contractor shall follow the exact steps mentioned in the NIP and coordinate with all
parties within RSAF.

3.3.3 Implementation and testing will be conducted by the contractor. However, Cisco are
required to provide on-site engineers to support the contractor during the NRFU testing
phase.

3.3.4 The contractor is to provide qualified engineers on site for the duration of the project.
These engineers should be qualified to resolve any issues could happen during the
installation.

3.3.5 The contractor is to provide assurance that the NRFU procedures and tests have been
followed appropriately

3.3.6 The contractor is to provide assurance that the test results are accurate.

3.3.7 The contractor is to collect all the test results and add it to the handover document set.

3.3.8 During the implementation, the contractor shall collect all the data required to generate
an accurate As-Built documentation set.

4 Testing and Commissioning

4.1.1 The contractor is required to demonstrate that the network and C3 upgrades are fully
functional and resilient and that existing network services remain unaffected by the
upgrades prior to handover to the relevant teams.

4.1.2 The contractor shall perform the POST (power on self-test) for all the active
components before installing them in the network.

4.1.3 The contractor is required to successfully execute the network ready for use procedures
and tests as defined within the NRFU document.

4.1.4 All tests defined within the NRFU document must be successfully executed and test
results captured within a test report.

4.1.5 All tests should be done with the presence of RSAF DCIT representative.

4.1.6 The contractor is to supply all required material and devices to ensure the success of
the test procedures and all equipment shall be handed over to RSAF DCIT.

4.1.7 Cisco Advanced Services will provide network engineers on site during the execution
of the NRFU to both witness the testing and provide the RSAF with assurance that the
testing has completed successfully will full NRFU coverage.

Page 19 of 35
 4.1.8 The contractor shall perform functional and non-functional testing in line with the agreed
test and acceptance strategy

4.1.9 The contractor shall test all fibre cores (indoor and outdoor) using fibre testing
equipment and test all UTP nodes using the Fluke. All test results are to be provided to
the RSAF as part of the handover documents.

4.1.10 The contractor shall add all equipment to the monitoring systems in the Network
Operation Center (NOC) to test them and demonstrate the states to RSAF DCIT.

4.1.11 The following deliverables are required for this activity:

a. Testing Plan.
Acceptance criteria includes:
• Alignment with RSAF building and acceptance schedule
• Identification of when each buildings network will be configured and ready
for deployment of IT infrastructure
• Alignment with the NRFU

b. Test Reports
For each individual test, the following are required:
• Date, time and result of each test run
• Incidents and defects that occur
• Resolution action for each defect found

c. Configuration data

d. Acceptance criteria includes:

For each patch panel:
• A mapping of the patch panel ports to termination points
• The initial patching of ports on the switch to termination points

e. A plan of each server room, switch room or cabinet showing the 'as built' layout of
the location. This will show the physical location of the cabinets within the room,
the power supplies for the racks, the data cable routes to and from each rack.

f. A plan of each rack showing the location of every piece of equipment located in
the rack.

5 Acceptance and Handover

The diagram at Appendix 6 illustrates the principles involved with any acceptance. This involves
the provision of evidence to the the local CITW, local testing and configuration, issuing CoC
(Certificates of Completion) signed by the local CITW and final sign off by the DCIT. Should any
system testing be required to be witnessed by the DCIT they will formally state this.

The Contractor is to deliver a comprehensive training for all the systems delivered. The training
is to enable RSAF personnal to take over the responsibility of operating and maintaining the
delivered systems after the handover. The kind and the duration of the training required should
be provided to RSAF DCIT for review and approve.

Page 20 of 35
 The following document deliverables are required and must be approved at each stage by RSAF
and should be delivered as a handover pack:
a. Programme Schedule detailing the key project milestones and dependencies
b. High Level Design (HLD): showing the high level design.
c. Low Level Design (LLD): showing the detailed network design
d. Network Implementation Plan (NIP): showing how the LLD will be implemented.
e. Test and Acceptance document (NRFU): showing the test procedures will be done
to the network.
f. Test reports: showing the test results for each component.
g. As built documentation: showing what has been implemented OSP, ISP and Active
components including serial numbers, port mapping matrix, fibre routes, equipment
warranties, all software and software licenses, support, etc.
h. Support model document: showing the support methodology for each system
delivered.
i. Training materials (official courses or OJT).

6 Further Information
Further information can be provided as needed by contacting the RSAF HQ DCIT NECC.

Page 21 of 35
 APPENDIX 1: OSP Civil Work
Specifications

For laying the fibers OutSide Plant (OSP), the contractor shall build a new duct as per the
specification that will be provided by the DCIT NECC and O&M department.

Figure 1-1: Excavation Specifications for Sand Areas

(Drawing not to scale)

Page 22 of 35
 Figure 1-2: Excavation Specifications for Asphalt and Road Cut Areas

(Drawing is not to scale)

Page 23 of 35
 Figure 1-3: Ducted Fibre Trenching for Technical Areas

Page 24 of 35
 Figure 1-4: Hand Hole Specifications

Page 25 of 35
 Figure 1-5: Hand Hole Specifications

Page 26 of 35
 Figure 1-6: Hand Hole Specifications

Page 27 of 35
 APPENDIX 2: Solution Path

Industry Best Concept of

RSAF Standards SoR
Practice Operations

International
As is state
Standards

Statement of Work

Formal Review Gate

HLD

Formal Review Gate

LLD

Formal Review Gate

Implementation
Plans (NIP)
Formal Review Gate

Implementation

Formal Review Gate

Testing

As Built Documents

Page 28 of 35
 APPENDIX 3: Generic LAN Schematic

Bldg 1

Bldg 2

Bldg 3

Min 24 Core Bldg 4

from each
Distribution
switch to Each
Building
Zone 1 Zone 1
Dist 1 Dist 2

MDF SCC/SOC
Core Core

Zone 2 Zone 2
Dist 1 Dist 2

Bldg 5

Bldg 6

Page 29 of 35
 APPENDIX 4: Material Specifications

Table 4-1: OSP Specifications

Item # Description Part #
1 Stranded Loose Tube Cable A-DF(ZN)2YW2Y, G.652.D, 4x12-fibers,
Outdoor for direct ground installations R304218

2 19" 1U UniRack2 24xLC-Duplex G.652.D, PC, ceramic, C/2 loaded with

R819330
connectors and pigtails
3 Patch Cord LC-Duplex PC - LC-Duplex PC, blue/blue, G.652.D, D/3, F8
R316491
2.0x4.1mm, 3 m
4 Splice Holder R30/R40, 12x shrink splice protection R320246
5 Heat Shrink Splice Protection 35 mm R30087-35
SYNO Dome Closure STP24 with Valve
SYNO-D25/35-V-STP/24
R812550
6 SYNO dome closure with valve complete prepared for tray assembling (2x
12 TPU), incl. sealing ring, clamp, loose tube tray kit for loop storage, 1
splice tray cover with tools, 2 desiccant bag 20g
Single Circuit Splice Tray for 12 HS splices, 1x
1x Single Circuit (SC) tray
7 R804270
1x holder for 12 heat shrink splice protectors
1x label
SYNO D25 Entry Kit 2x 7-14mm
SYNO-D25-SGB-2x7-14mm
8 R812564
SYNO cable entry kit for 2 cable Ø7-14mm incl. gel segment, cable strain
relief, central strength member fixing and 2 plugs for unused ports
SYNO D25 Entry Kit 1x 12-21mm
SYNO-D25-SGB-1x12-21mm
9 R812565
SYNO cable entry kit for 1 cable Ø12-21mm incl. gel segment, cable strain
relief, central strength member fixing and 1 plug for unused port
SYNO D25 Entry Kit Blind
SYNO-D25-SGB-BLIND R812568
10
SYNO blind segment used as filler for unused cable entry bays

Page 30 of 35
 Table 4-2: ISP Material Specifications

Item# Description Part# Brand

Patch Cord SC-Duplex PC - SC-Duplex PC, blue, G.652.D, D/3,
1 R320880 R&M
F8 2.7x5.5mm, 10 m

Patch Cord SC-Duplex PC, blue - LC-Duplex PC, blue/blue,

2 R321800 R&M
G.652.D, D/3, F8 2.0x4.1mm, 10 m

Patch Cord LC-Duplex PC - LC-Duplex PC, blue/blue, G.652.D,

3 R316491 R&M
D/3, F8 2.0x4.1mm, 3 m

Patch Cord LC-Duplex PC - LC-Duplex PC, blue/blue, G.652.D,

4 R317478 R&M
D/3, F8 2.0x4.1mm, 5 m

Patch Cord LC-Duplex PC - LC-Duplex PC, blue/blue, G.652.D,

5 R321801 R&M
D/3, F8 2.0x4.1mm, 10 m

19" 1U UniRack2 12xLC-Duplex G.652.D, PC, ceramic, C/2

6 R819607 R&M
loaded with connectors and pigtails

7 19" HD Cable Management 1U, 075 OFR, staggered, black R795627 R&M

8 Installation Cable Cat.6A, F/FTP, 4P, 650 MHz, LSZH, 500 m R320249 R&M

Patch Cord EL Cat.6A, U/FTP, 4P, LSZH, gray, RJ45/s-RJ45/s,

9 R820357 R&M
1.0 m

Patch Cord EL Cat.6A, U/FTP, 4P, LSZH, gray, RJ45/s-RJ45/s,

10 R820359 R&M
3.0 m

11 BS Faceplate 86x86, 2x1-Port, pure white R795068 R&M

12 Central Loose Tube Cable I/A-DQ(ZN=B)H, G.652.D, 12-fibers R304147 R&M

13 Splice Holder R30/R40, 12x shrink splice protection R320246 R&M

14 Heat Shrink Splice Protection 35 mm R30087-35 R&M

15 19" 1U PC Patch Panel 24-Port/s, Cat.6A, gray, empty R813485 R&M

16 Connection Module Cat.6A EL, 1xRJ45/s, Special, 10x R813508 R&M

Page 31 of 35
 Table 4-3: Cabinet Specifications
Brand
Item# Description Part #
Name
19" Cabinet CMS 42U, 800x1000 mm, Black 2 pairs of 19" profiles
(front/back), Swing handle with lock, Front and back door
1 R512787 R&M
ventilated 83%, 19" Fan 250V/76W, 448m³/h, black with
Thermostat of 0°C -60°C 19" Socket Strip 250V, 7 way UK outlets

19" Cabinet CMS 42U, 800x1000 mm, Black 2 pairs of 19" profiles
(front/back), Swing handle with lock, Front and back door
ventilated 83% Load rate 1000KG
Basic PDU, plug IEC 309 3m, Outlet 1 - 20xC13, Outlet 2 - 4xC19,
2 power rating 16A R512790 R&M
Brackets for mounting of vertical PDU IP-BA into RSF rack with A-
type of extrusions, set for 1 PDU

Page 32 of 35
 APPENDIX 5: HLD Content
The table below outlines the ideal content of a High Level Design document.

Item# Section Description

1 Introduction An outline of the project and its high level aims.

2 Scope A broad outline of the scope of the project.

3 Design An overal high level design of the project.

A description of the active portion of the solution

4 Active Components This is to include diagrams and tables with the numbers
of TAPs switches etc.

5 External Fibre Schematic of external fibre

Table with building connectivity
Physical routing of all OSP fibre

6 Internal Works Schematics of all Racks

Layout of all comms rooms
What internal connectivity is to be provided?
UPS details

7 Support Full details of what support is being offered. This shall

include details of Manuafacturers Warrantee, other
hardware support, OJT and training.

8 Schedule High Level schedule of project with indicative dates.

9 Handover and Acceptance Details of the handover and acceptance plan

10 Exclusions A list of things that are not being supplied as part of this
design.

11 Assumptions A list of assumptions that have been made when

designing the solution.

12 Dependencies A list of the dependencies are being placed on the

RSAF.

13 BoM Bill of Materials to be provided.

Table 5-1: HLD Content

Page 33 of 35
 APPENDIX 6: Acceptance and Handover

Page 34 of 35
 APPENDIX 7: Content of As Built Document Set
The table below outlines the minimum deliverables to be included in the As Built Document Set. All
the information below is to be in English and clearly readable.

Table 7-1: As Built Document Set

Item # Content Description Format

Routing of all external fibre installed by the .dwg and .pdf

1. Fibre Routing
project

Fibre .dwg and .pdf

2. Details of all fibre terminations and labling.
Termination

3. Fibre Test Fibre test evidence .pdf

Comms After installation loadout diagrams of all .dwg and .pdf

4.
Racks racks affected by the project.

Details of the configuration are to be As needed

supplied. This data is to include IP
5. Configuration
addresses, switch build scripts, build
documents etc.

Details of all warranties. This is to include .pdf and/or .docx

6. Waranty warranty agreements, contact details and
start and finish dates.

A complete list of all hardware supplied. .xlsx

This is to include part number, serial,
7. Hardware List installtion location, and warranty
information. This data is to be provided on
an RSAF templete which will be supplied.

Manual A complete set of manuals is required in .pdf and .docx

English. This can be in soft format but need
8. to be bespoke to the RSAF installation and
not generic. These manuals will allow the
users/operators and maintenance

All notes and presentations used during the As needed

Training/OJT
9. provision of training and/or OJT are to be
Notes
provided.

Page 35 of 35