Issuu on Google+

Invitation to Tender For

Data Networking Solution and Framework Agreement Prepared on behalf of

University of Stirling

Tender Reference 8080 Š 4C Strategies Limited 2009

Document Reference: Version: Originator:

531/ITT/DATA V1.0F Brian Cawley


4C Strategies Ltd

TABLE OF CONTENTS Table of Contents................................................................................................................................ 1 General Information............................................................................................................................ 3 1.1 INTRODUCTION............................................................................................................................... 3 1.2 PROJECT SCOPE............................................................................................................................ 3 1.3 DOCUMENT OBJECTIVES................................................................................................................. 3 1.4 KEY DATES.................................................................................................................................... 3 1.5 BASIS OF TENDERS........................................................................................................................ 4 1.6 RESPONSES................................................................................................................................... 5 1.7 SUBMISSION OF TENDERS............................................................................................................... 6 1.8 EVALUATION................................................................................................................................... 6 1.9 DISCLAIMERS................................................................................................................................. 7 1.10 BRIEFING..................................................................................................................................... 7 1.11 CONFIDENTIALITY......................................................................................................................... 7 1.12 CANVASSING................................................................................................................................ 7 1.13 QUERIES...................................................................................................................................... 8 1.14 FREEDOM OF INFORMATION.......................................................................................................... 8 2. Scope of Procurement..................................................................................................................... 9 2.1 LOT 1 CORE NETWORK UPGRADE DESIGN AND IMPLEMENTATION.....................................................9 2.2 LOT 2 FURTHER DEVELOPMENT OF NETWORK AND DEPLOYMENT OF EDGE NETWORK.........................9 2.3 INCLUSIONS.................................................................................................................................... 9 2.4 EXCLUSIONS................................................................................................................................ 10 3. Operational Requirement.............................................................................................................. 11 3.1 INTRODUCTION............................................................................................................................. 11 3.2 CURRENT CORE NETWORK DESIGN.............................................................................................. 11 3.3 PROPOSED NETWORK DESIGN...................................................................................................... 12 3.4 FIREWALL SERVICES..................................................................................................................... 15 3.5 SYSTEMS MANAGEMENT............................................................................................................... 15 3.6 CORE NETWORKING FEATURES..................................................................................................... 15 3.7 EDGE / ACCESS NETWORK........................................................................................................... 17 4. Installation Management .............................................................................................................. 19 4.1 RELATION TO LOTS....................................................................................................................... 19 4.2 DEPLOYMENT STRATEGY.............................................................................................................. 19 4.3 PROJECT MANAGEMENT............................................................................................................... 20 4.4 ENGINEERING SKILL BASE............................................................................................................ 21 4.5 WORKING WITH OTHERS............................................................................................................... 21 4.6 LABELLING................................................................................................................................... 22 4.7 PRE-STAGING.............................................................................................................................. 22 4.8 ACCEPTANCE TESTING................................................................................................................. 22 4.9 EQUIPMENT HANDOVER................................................................................................................ 23 4.10 CHANGE-OVER........................................................................................................................... 23 4.11 IN SERVICE SUPPORT................................................................................................................. 23 4.12 MAINTENANCE HANDOVER.......................................................................................................... 23 4.13 HEALTH & SAFETY POLICY.......................................................................................................... 23 4.14 SITE RULES............................................................................................................................... 23 5. Training Requirements.................................................................................................................. 25 5.1 RELATION TO LOTS....................................................................................................................... 25 5.2 GENERAL REQUIREMENT.............................................................................................................. 25 5.3 TRAINING CONTACT...................................................................................................................... 25 5.4 TRAINING PLAN............................................................................................................................ 25 5.5 MANDATORY TRAINING REQUIREMENTS.........................................................................................25 5.6 DESIRABLE TRAINING REQUIREMENTS........................................................................................... 26 6. Support and Maintenance Requirements....................................................................................27 6.1 RELATION TO LOTS....................................................................................................................... 27 6.2 GENERAL REQUIREMENT.............................................................................................................. 27 6.3 FAULT REPORTING SERVICE......................................................................................................... 27 6.4 ON-LINE FAULT SERVICE............................................................................................................... 27 6.5 SPECIFIC REQUIREMENTS............................................................................................................. 27

University of Stirling Data Networking Framework Tender v1.0F

Page 1


4C Strategies Ltd 6.6 HELP DESK.................................................................................................................................. 28 6.7 SERVICE LEVEL AGREEMENT........................................................................................................ 28 6.8 SUPPORT PERIOD........................................................................................................................ 28 6.9 EXISTING EQUIPMENT................................................................................................................... 28 7. Questionnaire................................................................................................................................. 29 7.1 SUPPLIER INFORMATION............................................................................................................... 29 7.2 PRODUCT INFORMATION............................................................................................................... 29 7.3 REFERENCES .............................................................................................................................. 29 7.4 SOLUTION ARCHITECTURE / CAPACITY ......................................................................................... 29 7.5 RESILIENCE FEATURES................................................................................................................. 30 7.6 PROTOCOL SUPPORT / TRAFFIC MANAGEMENT / MULTIMEDIA TRAFFIC HANDLING...........................30 7.7 MANAGEMENT SYSTEM................................................................................................................. 30 7.8 PRODUCT DEVELOPMENT............................................................................................................. 31 7.9 OTHER FUNCTIONALITY................................................................................................................ 31 Appendix A – Core network port requirements..............................................................................32 Appendix B – Pricing Schedule....................................................................................................... 34

University of Stirling Data Networking Framework Tender v1.0F

Page 2


4C Strategies Ltd

GENERAL INFORMATION 1.1

Introduction

University of Stirling has set out a strategy to update and improve its campus data network. In order for the University to deploy and support the latest and future network applications the University is looking to migrate the current data network to a more future proof infrastructure. In line with this a parallel project is being undertaken to replace the obsolescent BTeX telephony system with an IPT / Unified Communications solution. University of Stirling has appointed 4C Strategies to provide technical input and assist in the procurement and deployment of an appropriate data network. Further information regarding the University, its objectives and its estate can be found at www.stir.ac.uk.

1.2

Project Scope

1.2.1

Inclusions

The scope of this procurement specifically includes the following elements: •

Data Networking Equipment

Associated Applications

Design and Installation services

Training

Maintenance and support services

1.2.2

Exclusions

The scope of this procurement excludes IP Telephony and Unified Communications applications which will be subject to a separate subsequent procurement.

1.3

Document Objectives

The objectives of this document are as follows: 1. To summarise University of Stirling’s current data network infrastructure. 2. To provide sufficient information relating to the technical and operational requirements for the data network so that suppliers can put forward detailed proposals for a solution that will support and enable University of Stirling’s data network requirements. 3. To confirm the formal tender process that Suppliers need to follow in order to submit valid and compliant proposals.

1.4

Key Dates

At this juncture, the key dates relating to this procurement are as follows:

University of Stirling Data Networking Framework Tender v1.0F

Page 3


4C Strategies Ltd

Activity

Start

Finish

Issue Tender Document

12th May 2009

Supplier Briefing Date

21st May 2009

Tender Closing Date

5th June 2009

Evaluate and Agree Preferred Supplier

8th June 2009

10th July 2009

Place Order

Mid July 2009

Initial deployment complete

To Be Agreed

Suppliers should note that these dates may be subject to change as the procurement progresses.

1.5

Basis of Tenders

1.5.1

References

Suppliers shall only reference information contained within this document, or other information subsequently communicated as part of this procurement, when preparing their proposals. 1.5.2

Purchase Contract

This procurement is being undertaken through the OGC Buying Solutions Framework agreement – Specialist Solutions – Data Solutions. The terms and conditions of contract shall be as agreed within the framework. 1.5.3

Support Contract

The support contract(s) shall be based on the Supplier’s standard terms and conditions of contract. However, the University reserves the right to negotiate amendments where necessary. 1.5.4

Fixed Discount

All prices submitted in the tender document shall reflect a fixed discount to be offered to the University. The fixed discount level shall apply from manufacturer’s list prices in GBP and shall be valid for a 4 year period following award of contract. 1.5.5 Currency Where supplier’s list prices are originally priced in a currency other than GBP, suppliers shall state any assumptions on exchange rates and shall detail whether any prices or discounts offered are subject to change as a result of any future exchange rate fluctuations. 1.5.6

Variations to Contract

All variations to the contract shall only be agreed via a formal change management process. 1.5.7

Purchase Payment Terms

Payment terms will be agreed with the preferred supplier in accordance with the framework contract. 1.5.8

Support Payment Terms

University of Stirling Data Networking Framework Tender v1.0F

Page 4


4C Strategies Ltd The payment terms for the support contract shall be annual in advance. 1.5.9

VAT

All prices quoted shall exclude VAT. 1.5.10 Validity The proposal shall remain valid and open to acceptance for a minimum period of 3 calendar months after the closing date. 1.5.11 Right to Accept or Reject The University shall reserve the right to accept or reject any proposal and has no obligation to accept any proposal. 1.5.12 Right to Clarify The University shall reserve the right to undertake post tender clarifications with the successful supplier to agree the exact content and timescales of the contract. 1.5.13 Tender Costs The University shall not be liable for any costs that may be incurred from responding to this Invitation to Tender

1.6

Responses

1.6.1

Content

The Tender response shall comprise: Section 1

A management summary. (No more than three pages)

Section 2

A completed pricing schedule

Section 3 A statement of compliance to the requirements of all Sections 2 to 6 and a completed response to Section 7. Section 5

A copy of the proposed support contract

Section 6

A high-level project plan showing key milestones.

Section 7

Contact information for resolving queries arising from the response.

Section 8 Customer List and references. In addition to a customer list suppliers shall provide full details of up to 3 projects similar in scope to that proposed for the University, undertaken in the last 3 years. 1.6.2

Statement of Compliance

The statement of compliance against each requirement of this document must commence with one of the following: We comply

Where you fully comply with the stated requirement.

University of Stirling Data Networking Framework Tender v1.0F

Page 5


4C Strategies Ltd We partially comply Where you meet only part of the requirement. You may then describe your partial compliance and offer alternatives if appropriate. We do not comply

Where you do not comply with the requirement. You may then describe alternatives available if appropriate.

The use of the term noted is not acceptable. Each statement shall be complemented by a brief summary of how the compliance will be achieved. In particular, the specific information requested in sections 2 – 6 must be supplied. 1.6.3

Statement of Compliance Format

The statement of compliance shall comprise both the text of this document and Supplier’s response. To assist the evaluation process, Supplier’s response shall be in a different font colour to the original text (preferably blue).

1.7

Submission of Tenders

1.7.1

Tender Responses

3 hard copies and 1 soft copy (On CD Rom or similar) shall be submitted by the due date and time to the following address: Mr C B Elliott Procurement Manager Commercial and Procurement Services Room 2B10 Cottrell Building University of Stirling Stirling FK9 4LA 1.7.2

Closing Date and Time

Tenders shall be received by 12 Noon on 5th June 2009 1.7.3

Packaging

The tender submission should be clearly marked with the following wording: “TENDER 8080 for the provision of Data Networking Infrastructure” “Closing Date 12 Noon - 5th June 2009” Please ensure there are no markings on the envelope, which could identify the sender of the Tender. Failure to follow these instructions may render the Tender invalid.

1.8

Evaluation

1.8.1

Principles

University of Stirling and 4C Strategies shall evaluate all proposals using a scoring matrix that takes account of price so that a price performance score can be calculated for each Supplier.

University of Stirling Data Networking Framework Tender v1.0F

Page 6


4C Strategies Ltd The evaluation criteria applied shall be: •

Fitness for purpose including quality (60%)

Supplier capacity and capability (15%)

Lifecycle costs (25%)

University of Stirling does not make any representation that it will accept the lowest or any of the tenders. 1.8.2

Process

In summary, the evaluation process shall be as follows: 

Evaluation of all proposals to identify a short-list that can be evaluated in further detail.

Meetings and presentations with short-listed Suppliers to identify preferred supplier(s)

Meetings and presentations with the preferred supplier(s) to agree the final content and terms of a contract and agreement.

1.9

Disclaimers

Information provided in this document is supplied for general guidance in the preparation of proposals. Suppliers shall satisfy themselves to the accuracy of the information as the neither University or 4C Strategies accept any responsibility for inaccurate information.

1.10

Briefing

To assist Suppliers to prepare their proposals, suppliers are invited to attend a supplier briefing session which will be held at the University at 10.30am on 21st May 2009 Please confirm if you wish to attend the briefing by emailing bcawley@4c.co.uk by 18th May 2009 when instructions for attendance will be issued.

1.11

Confidentiality

The information contained in this documentation is confidential and is provided to enable Suppliers to submit firm proposals. This document may not be copied or passed to any third party except for the specific reason of responding to this definition of requirements.

1.12

Canvassing

Suppliers shall not, in connection with this procurement: •

Offer any inducement, fee or reward to any member of the University or an advisor acting on behalf of the University.

Do anything that would constitute a breach of the Prevention of Corruption Acts 1889 to 1916.

Canvass any of the persons detailed in this document.

University of Stirling Data Networking Framework Tender v1.0F

Page 7


4C Strategies Ltd •

Contact any member of the University, except as authorised by this document, regarding any aspect of the project or for soliciting information in connection with the project.

1.13

Queries

All questions should be addressed to the contact below. Questions should be submitted by email. Questions and responses shall be made available to all suppliers. No questions will be considered from 1 week prior to the tender return date. Mr B Cawley Director 4C Strategies Ltd Terminal Warehouse Union Wharf Market Harborough LE16 7UW Email:

1.14

bcawley@4c.co.uk

Freedom of Information

FREEDOM OF INFORMATION (SCOTLAND) ACT 2000 All information submitted to the University may need to be disclosed and /or published by the University. If you consider that any information provided to the University to be commercially confidential please identify it and explain (in broad terms) what harm might result from disclosure and/or publication. You should be aware that, even where you have indicated that information is commercially sensitive, we may require to disclose and /or publish it. Whilst information of a sensitive nature (e.g. pricing and daily rates) will not normally be disclosed and /or published, in certain circumstances we may require to disclose and/or publish such sensitive information where the public interest in its disclosure and /or publication requires us to do so.

University of Stirling Data Networking Framework Tender v1.0F

Page 8


4C Strategies Ltd

2.

SCOPE OF PROCUREMENT

Through the tendering process, it is the University’s intention to nominate a preferred supplier or suppliers for the following:

2.1

Lot 1 Core Network Upgrade Design and Implementation

This Lot shall be awarded to a single supplier and shall comprise the following two elements: 2.1.1 Review the University’s network solution (Design Phase) The University and 4C Strategies have undertaken an initial design workshop.. The output of this has been the creation of a new network design along with a definition of specific requirements for the new data network. The selected supplier will be required to review the design, provide input and recommendations for revision if necessary and underwrite the solution for deployment. 2.1.2

Undertake the initial deployment of the data networking core equipment and configuration (Deployment Phase 1) For the initial deployment of this new network the University wishes to procure a new network based on a dual resilient core interconnected at 10 Gbit/s The selected supplier will be expected to undertake the supply, installation and support of this deployment whilst working closely with the University’s own technical staff. Suppliers are asked to complete the attached pricing schedule in accordance with this requirement.

2.2

Lot 2 Further development of network and deployment of edge network

This Lot shall be awarded to one or more suppliers and shall comprise: 2.2.1

A framework agreement for the continued development of the data network (Deployment Phase 2)

The University wishes to put in place a framework agreement to enable the purchase, supply and installation of additional data networking equipment for the continued development of the data network. Suppliers shall note that the framework agreement shall incorporate the following points: • • •

The duration of the framework agreement shall be four years. The Supplier shall be expected to conduct price discount benchmarking on an annual basis to demonstrate that the discount levels offered remain in line with market rates (Subject to an agreement on the methodology with the University). Whilst the University shall use the framework supplier(s) for the majority of purchases, the University reserves the right to purchase equipment and services from other suppliers at its discretion.

Suppliers are asked to complete the attached pricing schedule in accordance with this requirement.

2.3

Inclusions

The scope of this procurement includes: i.

Backbone / core networking equipment including switches and routers as appropriate.

University of Stirling Data Networking Framework Tender v1.0F

Page 9


4C Strategies Ltd ii.

A network management system to manage, configure, administer and monitor all network equipment (software only – computing hardware will be provided by the University). Distribution and access layer equipment including switches as required. UPS provision for the core network and as required for the edge equipment.

iii. iv.

For all of the elements above, the supplier will be expected to: i.

Assess and develop the proposed network design (including IP addressing scheme and vLAN structure for voice). It shall be noted however that the University is intending to retain the current IP addressing scheme for data. Work with representatives from the University and 4C Strategies to agree and implement a suitable QoS policy for voice and video traffic Supply equipment Conduct Pre-staging of new equipment as necessary and demonstrate network operation of the new core components and a sample of edge switches to representatives from the University and 4C Strategies Ltd Configure, test and install new equipment as necessary and assist with the reconfiguration of existing core equipment. Train University personnel in the management, administration and troubleshooting of the network Provide comprehensive system and configuration documentation Provide comprehensive maintenance services in respect of all core equipment supplied. This may be extended through negotiation to include existing equipment so that a single maintenance and support contract is in place for the whole core network. Provide a comprehensive support service to support University staff in their management and administration of the infrastructure.

ii. iii. iv.

v. vi. vii. viii.

ix.

All of these elements apply to both the initial core requirements and also to the majority of future purchases on the framework agreement (although some purchases may be ‘supply only’ i.e. additional access layer switches). It is important for suppliers to note that the University wishes to be included throughout all stages of the network design and configuration to ensure its personnel thoroughly understand the solution as deployed. Suppliers shall make full allowance for this skills transfer.

2.4

Exclusions

The following works shall be conducted by the University and are therefore excluded from this procurement: • • • •

Supply and Installation of CAT5e and CAT6 structured cabling Supply and Installation of Inter wiring centre fibre optic cabling. Patch Cords WAN connections to other University sites

University of Stirling Data Networking Framework Tender v1.0F

Page 10


4C Strategies Ltd

3.

OPERATIONAL REQUIREMENT

3.1

Introduction

3.1.1

Introduction

The University’s new data network will form the foundation of a new common infrastructure. The network shall provide support for both voice and data traffic along with being able to support any future applications that the University may decide to deploy for example Video or IP CCTV. In parallel with this project the University is also running a project to replace its obsolescent BTeX telephony platform. All of the existing core network equipment at the University is Cisco. The University network staff are therefore very familiar with this brand and less familiar with other products on the market. Given this, the University has identified the Cisco product sets that best suits the current need and has specified the requirements below in the context of that equipment, its features and functionality. Cisco specific terms may be used throughout the specification, however other products will be considered providing their features and functionality are demonstrably equivalent to those indicated. The proposed core equipment must be fully interoperable with the existing core network in relation to the functionality listed in this specification.

3.2

Current Core Network Design

The diagram below provides a high level overview of how the topology is organised at present:

gbmh

gbmain

gbx

gbimc

gbfraser

gbash

3.2.1.1

gbpath

gblib

Current Network Design Overview

The Stirling Campuses The main campus is at Stirling and there is a smaller one in Inverness connected by a 10M bps link supplied by Thus and a much smaller campus in Stornoway, connected by a 10M IP tunnel via the network of UHI (the University of the Highlands and Islands) and the Janet network. The Stornoway Campus has one Cisco router belonging to UHI and 3 HP Procurve switches. The Inverness Campus has a Cisco Catalyst 3560G layer 3 switch plus 11 other switches, all Cisco. The rest of these notes describe the Stirling campus. The Inverness and Stornoway campus’s are outside the scope of the initial procurement however equipment may subsequently be purchased for these sites through the framework arrangements.

University of Stirling Data Networking Framework Tender v1.0F

Page 11


4C Strategies Ltd Network Backbone This consists of 8 Cisco Catalyst layer 3 switches connected by 1G links in a redundant configuration. See Figure above. The switches named gbmh, gbfraser and gbash are in student residences and the others are in academic buildings. Name of Switch

Location

gbmain gbpath gblib gbx gbimc gbash gbmh gbfraser

Cottrell West Computer Room Pathfoot Computer Room Library Computer Room Cottrell Central Comms Room Iris Murdoch Building Andrew Stewart Hall Murray Hall Fraser of Allander Hall

The current equipment deployed is as follows

Name of Switch

Type

gbmain

WS-C4507R with Supervisor IV

gbpath

WS-C3750G-12S stacked with WS-C3750G-24TS-1U

gblib

WS-C3550-12G

gbx

WS-C3750G-12S

gbimc

WS-C3750G-12S

gbash

WS-C3750G-12S

gbmh

WS-C3750G-12S

gbfraser

WS-C3560G-24TS

3.3

Proposed Network Design

The following sets out the proposed design parameters for the new network. It is intended to create a dual core architecture with the core distributed between two new switches. One of these will be located in Cottrell West Computer Room and will replace gbmain. The other will be located in a new Computer Room currently being constructed (Cottrell East) and will be known as gbacr. Example switches for this purpose: Cisco 6509 (or equivalent). Any solution proposed must be resilient in the event of failure of one of these switches. The two cores should be connected at 10 Gbit/s. A 3 layer model will be retained with the distribution layer also being connected to the core at 10 Gbit/s Appendix A and the pricing schedule indicates the number of each type of ports required at each core, however options for all applicable cards shall be included in the pricing schedule. Within each of the two core locations two distribution switches shall be provided each connected at 10Gbit/s to the core. Each access level wiring centre will be connected to both distribution layer switches (in a single location). It is the intention that the access layer uplinks will be upgraded to 10Gbit/s as required during the edge network upgrade project. As further fibre is installed each wiring centre will become connected to a distribution layer switch in each of the core locations. University of Stirling Data Networking Framework Tender v1.0F

Page 12


4C Strategies Ltd

There is no requirement for PoE at the core or distribution layers and this requirement is limited to the access layer. 3.3.1

Core Architecture and Processing

Suppliers shall describe in detail their core architecture and processing methodology. Suppliers shall describe and cost for any options for additional / resilient processing in each core. 3.3.2

Core Capacity

Suppliers shall describe the capacity of their proposed core architecture and describe all cards and their associated port capacity. 3.3.3

Proposed Network Design Diagram

The following schematics set out the proposed network architecture. 3.3.3.1

Computer Room / Server Connectivity Computer Room Distribution Network

gbmain

gbacr

Cottrell West 99686

switch

Cottrell East L2 switch

L2 switch

switch

switch

Pathfoot 99682

switch

99683

switch

99684

switch

1G bps link 10G bps link

University of Stirling Data Networking Framework Tender v1.0F

Page 13


4C Strategies Ltd 3.3.3.2

Initial Wiring Centre Connectivity User Devices

User Devices

User Devices

Wiring Centre

Wiring Centre

Wiring Centre

Distr Switch 2

Distr switch 1

gbmain

. 3.3.3.3

Target Wiring Centre Connectivity User Devices

User Devices

User Devices

Wiring Centre

Wiring Centre

Wiring Centre

Distr switch 1

Distr Switch 2

gbmain

3.3.4

gbacr

gbacr

Equipment Redeployment

The existing core switch in gbmain is a Cisco 4507R supervisor 4. Suppliers are invited to put forward proposals for the buyback or redeployment of this equipment within the new network. 3.3.5

UPS

For each core location suppliers shall provide an itemised cost for a UPS (SNMP manageable) to provide 2 hour power support at maximum equipped capacity. This shall support the core and distribution layers in these locations. Suppliers shall also include sample costs for a range of UPS as part of the framework agreement for deployment at the access layer. University of Stirling Data Networking Framework Tender v1.0F

Page 14


4C Strategies Ltd

3.4

Firewall Services

The University is considering the deployment of an advanced application-aware firewall and proposals for an integral or external firewall shall be submitted together with the supplier’s recommendations and associated pricing. The University currently connects to the Internet via the EastMAN network over two 155 Mbps circuits. This will shortly be upgraded to a 1 Gbps circuit and the proposed firewall shall support this throughput.

3.5

Systems Management

The University wishes to enhance its management tools and capability and proposals for systems management shall be submitted together the supplier’s recommendation and associated pricing. It is essential that the proposed solution can be used to manage and fully exploit all the functionality of the existing equipment and suppliers shall confirm how they can comply with this requirement.

3.6

Core Networking Features

3.6.1

Single Virtual Switch

It must be possible to configure and manage the proposed dual core as a single unit e.g. Cisco VSS (or equivalent). Suppliers shall state how this will be achieved. 3.6.2

Per Vlan Spanning Tree

In addition to RSTP and MSTP the University will wish to run a an instance of spanning tree per VLAN. Single instance spanning tree and multiple spanning tree alone are not sufficient. 3.6.3

Auto QoS

Suppliers shall describe any features available to facilitate the setting up of QoS on the network. 3.6.4

Software Upgrades

The equipment should be capable of in-service software upgrades to eliminate unnecessary downtime. 3.6.5

SNMP V3

The proposed core must support SNMP V3 3.6.6

Optional Service Modules

Suppliers shall describe the modularity of the proposed system and shall detail all available modules including optional service modules and their relation to backplane capacity, e.g. firewall, wireless etc 3.6.7

Remote Traffic Analysis

The solution shall support ER-SPAN and R-SPAN for remote network traffic analysis

University of Stirling Data Networking Framework Tender v1.0F

Page 15


4C Strategies Ltd

3.6.8

Protocol Support

The network will be required to support the full implementation of the following protocols in hardware: •

IPv4

IPv6

The selected Supplier will be required to have a clear development strategy for the support of IPv6. Details should be provided in response to the questionnaire. 3.6.9

Multi-cast Protocols The network must support industry standard multicast routing protocols such as PIM. All versions of IGMP must be supported.

3.6.10 vLAN Support The network will be required to support multiple virtual LANs (vLANs). The following specific support will be required: •

Support for multiple vLANs

vLANs to conform with IEEE802.1q

Support for protocol based vLANs

Support for port based vLANs

Support for secondary IP addresses on VLAN interfaces

3.6.11 Quality of Service The network must support a rich set of traffic classification, prioritisation and policing features, using advanced QOS mechanisms such as Network Based Application Recognition. 3.6.12

Access Control Lists

Independent of any firewall device, the switch itself will offer advanced ACL features that can classify traffic at the application layer. Vlan ACL's and Mac-address based ACL's should also be supported. 3.6.13 802.1x Support The network must fully support 802.1x and multiple EAP types for network admission control. 3.6.14 VRF (or equivalent) The network must support virtual routing and forwarding or the equivalent feature 3.6.15 Dynamic ARP inspection The network must support dynamic address resolution protocol inspection to block forged ARP packets 3.6.16 IP Source Guard The network must support IP source guard or equivalent to block any packets sent from the port claiming to be from a different IP address than that assigned by DHCP. 3.6.17 DHCP Snooping

University of Stirling Data Networking Framework Tender v1.0F

Page 16


4C Strategies Ltd The network must support DHCP snooping

3.7

Edge / Access Network

Suppliers shall put forward proposals for access layer switches in the following configurations: • • • •

24 port PoE 24 port Non PoE 48 port PoE 48 port non PoE

Where the supplier is able to offer options for either 1 gbit or 10 gbit uplinks this shall be stated and optional pricing provided. Where suppliers are able to offer other switch configurations these shall be described and pricing submitted. 3.7.1

Required Features

For each switch type offered Suppliers shall confirm compliance with the following minimum specification: I. Triple speed edge ports with fibre connectivity options (dual personality). II. Ability to provide power to all 48 ports on switch when running IEEE 802.3af, class 3 power (15.4 Watts), or state maximum power available / ports supported. III. Ability to bundle links to increase bandwidth (802.3ad). IV. Rapid Spanning-Tree protocol and BPDU port protection V. Vlan tagging based on the IEEE 802.1Q standard. VI. Ability to assign vlans dynamically. VII. MAC-based port security and isolation of ports on switch to allow communication with downlink port only. VIII. Mac-address lockout. IX. Source port filtering. X. 802.1X. XI. Web based authentication. XII. Mac-based authentication with Radius Server. XIII. Secure FTP XIV. SNMP v3 XV. Radius / TACACS + for switch management security. XVI. SSH v2 and SSL support XVII. IP Multicast snooping and support for all IGMP versions. XVIII. LLDP network discovery protocol. XIX. Per port broadcast and multicast throttling. XX. Traffic prioritisation based on 802.1P XXI. Ability to assign 802.1P tag based on I.P address, I.P Type of Service (TOS), Layer 3 protocol, TCP / UDP port number, source port and differentiated services (diffserv). XXII. Traffic accounting and monitoring. XXIII. RMON XXIV. Support for more than one Operating System flash image. XXV. Basic traffic monitoring features to allow use of packet analyser. XXVI. Ability to stack switches. XXVII. Auto Mdix to eliminate use of crossover cable.

University of Stirling Data Networking Framework Tender v1.0F

Page 17


4C Strategies Ltd 3.7.2

Desirable Features

In addition to the switches offering the features as described above suppliers shall also propose for switches able to offer some or all of the following. The University will require a range of different switches to meet its requirements. I. Remote-Span to collect edge traffic and deliver to remote Network Management Station. This saves network staff time and eliminates the need for local placement of traffic analysis kit. II. Broadcast, Multicast and Unicast traffic throttling. III. Per-Vlan spanning-tree. IV. Ability to provide more than 15.4 Watts per port (enhanced PoE). V. Layer 2 traceroute VI. 10Gb Ethernet support and ability to split 10G port into 2 * 1G ports (twin gig converter). VII. Option for redundant power supply (rps). 3.7.3 UPS The University will wish to consider the deployment of UPS at the access layer and suppliers shall provide a range of indicative prices for UPS to support between 24 and 240 switch ports for the following period •

20 Minutes

1 Hour

2 Hours

University of Stirling Data Networking Framework Tender v1.0F

Page 18


4C Strategies Ltd

4.

INSTALLATION MANAGEMENT

4.1

Relation to Lots

This section primarily relates to Lot 1 comprising the initial design phase and core deployment. Suppliers bidding for this Lot shall provide a detailed response to this section. Suppliers who are only bidding for Lot 2 shall also provide a response however may state not applicable to those aspects which relate solely to the initial deployment project.

4.2

Deployment Strategy

Further details on the University’s requirements and the scope and phasing of the procurement will be provided at the supplier briefings however in summary there are 3 main phases: i.

Design Phase

ii.

Deployment Phase 1 – Core network and pilot edge deployment

iii.

Deployment Phase 2 – Phased edge / access layer deployment

4.2.1

Design Phase

The design phase will be undertaken immediately upon the selection of a preferred supplier and will include the following activities: •

Evaluation, development and agreement of the proposed data network design

Assisting with the approval, definition and preparation of IP and VLAN schemas

Definition and preparation of a migration/deployment plan for deployment phase 1

4.2.2

Deployment Phase 1

The initial deployment phase will follow on immediately from the design phase. This phase includes the following activities: •

Deployment and configuration of new cores at Gbmain and Gbacr

Deployment and configuration of new distribution layer switches in GB Main and Gbacr

Reconfiguration and reconnection of other distribution layer switches as required.

Initial skills transfer / training

Provision of edge switches for a pilot edge deployment.

Suppliers shall submit an outline programme demonstrating how they will achieve the above objectives assuming a contract award date of Mid July 2009 4.2.3

Deployment Phase 2

The second deployment phase will roll on from the initial deployment phase over the following 3 years and will include the following activities: •

A phased programme to replace the edge switches in line with the estates strategy to support the deployment of IP telephony and associated services.

University of Stirling Data Networking Framework Tender v1.0F

Page 19


4C Strategies Ltd •

Continued development of the network as required to provide 10gbit connectivity from the access layer.

4.3

Project Management

4.3.1

General Requirement

Effective project management is considered essential to the successful completion of the initial project comprising the deployment and configuration of the new network core, distribution and pilot edge deployment. The Supplier’s Project Manager shall take a leading and proactive role on behalf of the company and will be an integral member of the University’s project team. The Project Manager should be, at minimum, familiar with working within a PRINCE2 environment. 4.3.2

Costs

The Supplier shall provide a cost for the appointment of an experienced Project Manager able to fulfil the role expected of them. No claims for additional project management costs or for the Project Manager’s attendance on-site at the request of the University shall be considered after award of contract. 4.3.3

Primary Interface

The Project Manager shall be the primary interface for all matters between the Supplier and the University. The Project Manager shall be responsible for all of the Supplier’s activities on site including those of sub contractors. 4.3.4

Third Party Liaison

The Project Manager shall be responsible for liaison with third parties, e.g. network operators, to ensure full inter-working of their equipment with the equipment and services of others. 4.3.5

Continuity

The Project Manager shall remain in post for the duration of the contract. However, the University reserve the right to request a change of Project Manager if their performance is deemed to be unsatisfactory. 4.3.6

Project Meetings / Site Inspections

The Project Manager shall attend regular project meetings / site inspections to discuss progress and to resolve any issues arising. The Project Manager shall represent the Supplier and any sub contractors at these meetings. It is anticipated that main project meetings / site inspections will be held every week during the implementation period, with other meetings to discuss project set up and go live. The Project Manager will attend all meetings as reasonably requested by the University. 4.3.7

Programme of Work

In advance of the Set Up meeting, the Project Manager shall prepare a detailed Programme of Work with Microsoft Project. The issued project plan should be compatible with Microsoft Project 2003.

University of Stirling Data Networking Framework Tender v1.0F

Page 20


4C Strategies Ltd

The Programme of Work shall detail all key tasks and milestones within the project including those which are the responsibility of others, e.g. network service installations. The Project Manager shall update the Programme of Work for each project meeting and provide paper copies as required. 4.3.8

Site Supervisor

In addition to the Project Manager, the Supplier may appoint site supervisors as necessary for the day-to-day management of the works. 4.3.9

Organisation Chart

The Supplier shall submit an organisation chart showing the position of Project Manager within the organisation and the relationship to site supervisors/staff and sub contractors. 4.3.10 Variation Orders An agreed process for the issuing of variation orders will be agreed and the Project Manager will have the necessary authority to accept these on behalf of the Supplier. The University will nominate personnel with the authority to issue variation orders and any instructions accepted from personnel other than those nominated, and in accordance with the agreed procedures, will be at the Supplier’s risk and cost. Any variation costs submitted will be at the framework price or better.

4.4

Engineering Skill Base

4.4.1

Sub Contracting

Suppliers shall state as to whether any elements of the scoped activities will be sub contracted and if so which elements and to whom they will be sub contracted to. 4.4.2

Lead Engineer

The supplier shall provide a lead engineer for the duration of the installation. The lead engineer shall be fully qualified in all of the relevant networking equipment (to the highest relevant level). The lead engineer shall be assigned for the complete duration of the initial deployment phase. 4.4.3

Engineering Qualifications

Suppliers shall also provide details of the numbers of trained engineers and their relevant manufacturer accreditation.

4.5

Working with Others

The Supplier shall be required to work with others to deliver the project. Others shall include (but not be limited to) the following: • • • • •

Representatives of the University Representatives of 4C Strategies Ltd The University’s telephony solution system provider Network Service Providers Cabling Contractors

Suppliers shall include all costs to work in parallel with others as required. The University shall not accept further costs for delays or abortive costs. University of Stirling Data Networking Framework Tender v1.0F

Page 21


4C Strategies Ltd

In particular the Suppliers must recognise the need to work closely with the University’s provider of telephony systems to enable the commissioning of IP telephony.

4.6

Labelling

The supplier shall clearly label all network devices in accordance with the University’s labelling scheme.

4.7

Pre-Staging

4.7.1

Participation

The Supplier shall be required to pre-stage all equipment. The Supplier shall then allow the University / 4C Strategies Ltd access to inspect the pre-staged equipment, this should include an indepth technical description of the way each piece of equipment has been configured and why; a demonstration, including an agreed set of functionality and performance tests; and access to the equipment to conduct additional experiments and functionality tests as necessary. 4.7.2

Inclusive Costs

The Supplier shall make full allowance in their costs for the attendance of all necessary personnel to conduct the pre-staging as no claims for additional costs will be considered after award of contract.

4.8

Acceptance Testing

4.8.1

Participation

The Supplier shall participate in the preparation and completion of formal acceptance tests prior to the installation being considered ‘Ready For Service’ (RFS). 4.8.2

Inclusive Costs

The Supplier shall make full allowance in their costs for the attendance of all necessary personnel during this period as no claims for additional costs associated with acceptance testing will be considered after award of contract. 4.8.3

Acceptance of Test Plans

The Supplier shall accept the test plan put forward by the University and 4C. 4.8.4

QoS Testing

The Supplier shall provide a facility to test and record voice traffic simulations on the network to proved the correct operation of quality of service configurations. The results of the testing shall be provided to the University in a detailed paper-based report (also available electronically) 4.8.5

Attendance

The Lead Engineer shall be on-site during the testing activities to supervise the engineers.

University of Stirling Data Networking Framework Tender v1.0F

Page 22


4C Strategies Ltd

4.9

Equipment Handover

The Supplier shall be fully responsible for all equipment until the point of handover. Suppliers shall note the equipment shall not be covered under the University’s insurance policy until the system is signed-off during successful acceptance testing

4.10

Change-Over

The Supplier shall make full allowance in their costs for the attendance of all necessary personnel during this period as no claims for additional costs associated with attendance for the changeover will be considered after award of contract. The Project Manager and lead engineer shall be on-site during the changeover activities.

4.11

In Service Support

The new installation shall be supported by on-site personnel for at least the first two days of service. The Supplier shall make full allowance in their costs for the attendance of all necessary personnel during this period as no claims for additional costs associated with attendance for the first two days will be considered after award of contract. The on-site personnel shall comprise of technical and training resources. The Project Manager shall also be on-site for the first two days of service.

4.12

Maintenance Handover

The proposed handover from ‘Installation’ to ‘Support’ shall be discussed and agreed with 4C Strategies and the University to ensure all outstanding issues and actions are clearly documented.

4.13

Health & Safety Policy

The Supplier shall comply with the University’s health and safety policy. The policy will be tabled at the project set up meeting.

4.14

Site Rules

The Supplier shall comply with the University’s site rules. The rules will be tabled at the project set up meeting, however as minimum, the following will apply: 4.14.1 Smoking Supplier personnel shall comply with the University’s no smoking policy 4.14.2 Waste Disposal The Supplier shall remove all rubbish and packaging from the site and dispose of it in a non harmful way to the environment. 4.14.3 Deliveries

University of Stirling Data Networking Framework Tender v1.0F

Page 23


4C Strategies Ltd Supplier personnel shall take responsibility for receiving all deliveries. 4.14.4 Site Access The Supplier shall note that the project must be undertaken with minimal disruption to the operation of each site. Accordingly, all access to site must be pre-arranged and pre-agreed with site representatives. The Supplier will be required to work according to a detailed programme agreed with the University. This condition may require some activities to be undertaken out of normal working hours.

University of Stirling Data Networking Framework Tender v1.0F

Page 24


4C Strategies Ltd

5.

TRAINING REQUIREMENTS

5.1

Relation to Lots

The University may require training service in relation to both Lots 1 and 2. For Lot 1 suppliers shall provide a cost for the training as specified in addition to a day rate for additional ad-hoc training. Suppliers who are only bidding for Lot 2 shall provide a day rate for training.

5.2

General Requirement

The University recognises the benefit of high quality training on the new data network to its IT personnel. In addition to any specific training requirements set out below the University will wish to work with the supplier on the installation and commissioning of the initial deployment and benefit from skills transfer.

5.3

Training Contact

5.3.1

Nominated Individual

The Supplier shall nominate a Training Contact for the University. 5.3.2

Co-Ordination

The Training Contact shall be responsible for co-ordinating all training to be provided. 5.3.3

Project Set Up Meeting

The Training Contact shall attend the Project Set Up meeting for the phase 1 deployment.

5.4

Training Plan

In advance of the Set Up meeting, the Training Contact shall prepare a draft Training Plan. The Training Plan shall take account of the requirements below and shall confirm the following information: 1. The location and duration of each element of training 2. The syllabus for each element of training 3. The training materials that are to be provided within the tendered costs 4. The training materials that are available as a cost option The Training Contact shall update the Training Plan as required for each project meeting.

5.5

Mandatory Training Requirements

Suppliers shall provide training for three personnel and shall detail all proposed training on the pricing schedule. 5.5.1

Network Administrator

University of Stirling Data Networking Framework Tender v1.0F

Page 25


4C Strategies Ltd The primary objective of the course is to train the delegates on how to use and administrate the data network on a day-to-day basis and in the use the proposed network management system. 5.5.2

Documentation

Each training course shall be complemented by comprehensive documentation that is to be provided on a per delegate basis.

5.6

Desirable Training Requirements

5.6.1

Electronic Documentation

Each training course shall be complemented by comprehensive documentation that is available in electronic format, e.g. CDROM. 5.6.2

On Line Tutorials

Each training course shall be complemented by a tutorial that is available on-line.

University of Stirling Data Networking Framework Tender v1.0F

Page 26


4C Strategies Ltd

6.

SUPPORT AND MAINTENANCE REQUIREMENTS

6.1

Relation to Lots

The primary requirement is for the maintenance and support of the Core and Distribution layers of the network (Lot 1). Suppliers shall describe the warranty and repair arrangements for all access layer equipment proposed for Lot 2.

6.2

General Requirement

The University requires a high quality support and maintenance service that represents value for money.

6.3

Fault Reporting Service

The Supplier shall provide a fault reporting service that is available to receive fault reports on a 24/7 basis.

6.4

On-line Fault service

The Supplier shall provide an on-line fault reporting system. The system shall also allow the University’s IT staff to check the status of existing logged faults.

6.5

Specific Requirements

6.5.1

Hours of Cover

The University wishes to consider a range of options for the support services based on the following: Option 1 – 9.00am – 5.00pm 5 days a week Option 2 – 6.00am – 10.00pm 5 days a week Option 3 – 6.00am – 10.00pm 7 days a week. Suppliers shall note the cover is not required from the 25th Dec to 2nd Jan inclusive in any year. For all other periods cover for bank holidays should be included within the costs 6.5.2

Response and Fix Times

The Supplier shall respond at all times as per the following tables: Fault Type Critical Urgent 6.5.2.1

Example Loss of Core Loss of Blade

Remote Response 30Minutes 60 Minutes

Response to Site

Fix Time

4 Elapsed Hours 4 Elapsed Hours

2 Elapsed Hours 2 Elapsed Hours

Notes

1. ‘Response to Site’ time is from the time of the initial fault report. ‘Fix Time’ is from the time of arrival on-site.

University of Stirling Data Networking Framework Tender v1.0F

Page 27


4C Strategies Ltd 6.5.3

Items Covered

The maintenance contract shall cover all hardware and software items supplied under the purchase contract excluding stackable switch devices. Itemised costs for support and maintenance shall be provided in the pricing schedule.

6.6

Help Desk

The Supplier shall provide a 24/7 Help Desk service for resolving operational issues, which are not classified as faults.

6.7

Service Level Agreement

Suppliers shall put forward details of a proposed Service Level Agreement (SLA) to adhere to the requirements for maintenance (with appropriate penalties for missing these targets).

6.8

Support Period

The Supplier shall guarantee to support the overall solution for a minimum period of 7 Years. The University however requires suppliers to provide pricing for maintenance based on a 36-month initial support contract.

6.9

Existing Equipment

Where suppliers are able to offer support on any existing equipment they are invited to submit pricing for this as an option.

University of Stirling Data Networking Framework Tender v1.0F

Page 28


4C Strategies Ltd

7.

QUESTIONNAIRE

In addition to the system specific information requested in the above section, Suppliers are also required to provide the following general and background information:

7.1

Supplier Information

i.

Please provide details of corporate history, ownership and structure

ii.

Will you sub-contract any element of the proposed works? If so which element and to whom?

7.2

Product Information

i.

What system(s) do you intend to supply for each element of this procurement?

ii.

Does your company manufacture the system(s)? If not, who is the manufacturer and what is the relationship between your company and the manufacturer?

iii.

What manufacturer accreditation(s) does your company hold for the proposed products and at what level.

iv.

Please give details of the number of manufacturer accredited technical pre-sales staff and engineers (please give details of how many and to what level)

v.

What main technologies does your solution employ?

vi.

Please provide a history of all software / firmware upgrades for the last 3 years with upgrade costs from level to level?

7.3 i.

References Please provide full details of three reference sites where similar systems or services have been provided and whom the University may contact, (preferably in the higher education sector and preferably in Scotland) Please provide the following details in respect of each reference provided:

7.4

Contact details of a client representative who will be prepared to discuss the installation with University’s representatives.

Details of the products and technology deployed.

Details of the capacities of the systems installed.

Date of installation.

Solution Architecture / Capacity

i.

Please provide an overview of the solution clearly explaining why the particular products have been proposed and how they meet the University’s requirements.

ii.

Please provide an architectural schematic of your proposed solution showing all components (including switches, routers, and management system).

iii.

Please describe the technology deployed within the equipment.

iv.

For each of the products offered, suppliers shall provide the following information: •

Details of any restrictions regarding its “any card – any slot” capability.

University of Stirling Data Networking Framework Tender v1.0F

Page 29


4C Strategies Ltd

v.

7.5

Details of all interface cards available including media and number of ports.

The modularity of all interface cards.

The total number of slots available for interface cards.

The number of the above slots which will be spare initially (“equipped” capacity).

Details of any equipment other than additional interface cards that will be required to expand each system to the University’s expected requirements. (Eg. additional switching capacity etc).

Details of the system software licensing policy, in particular with respect to any additional licences which the University might have to purchase to expand the systems.

What is the traffic handling capacity (throughput) of each of the products in terms of the systems in terms of packets per second?

Resilience Features What are the key resilience features associated with the solution? In particular:

i. ii. iii. iv. v.

Are resilient switching engines available? Do these load share or act in active / standby mode? Are resilient power supplies available? Do these support n + 1 operation? Does the infrastructure support resilient links between the core and edge devices? Can these load share in normal operation? What other resilient features are available? What resilience features are included within the costed proposals? •

vi.

7.6 i. ii.

How is resilience provided (included) in respect of the core switch?

• What resilience is provided (included) in respect of the edge devices? What additional optional resilience features are available? Please provide pricing for optional features in the schedule of prices.

Protocol Support / Traffic Management / Multimedia Traffic Handling Please provide details of all LAN protocols supported by the network and any restrictions regarding the routing / bridging of these protocols. What are the product’s capabilities in respect of Quality of Service features? In particular: •

Is the solution able to prioritise traffic (eg. video / voice traffic)?

What QoS standards does the product conform to?

iii. iv. v. vi. vii.

7.7 i. ii.

Will the QoS features inter-work with other vendors equipment? If so has this been independently verified? How does the network handle & manage broadcast and multicast traffic? What packet filtering options and features are available? Will the network support TACACS? Will the network support RADIUS? Does the hardware support any proprietary protocols that are not compatible with other vender hardware? If so please give details.

Management System Please provide an outline description of the management system proposed. What are the minimum hardware and operating system requirements for the management system?

University of Stirling Data Networking Framework Tender v1.0F

Page 30


4C Strategies Ltd iii. iv. v. vi. vii. viii. ix. x. xi. xii. xiii.

7.8

Does the system offer management, administration and monitoring for all elements of equipment within a single application? Is the system GUI based for all activities? What standards does the management system conform to? Are there any restrictions regarding the number of network components or devices that can be managed? What management information / statistics are available regarding the utilisation of the core switches? What management information / statistics are available regarding the utilisation of the Quality of Service features / traffic streams? Is the system able to provide traffic information regarding specific protocols (eg. IP, IPX etc)? Is the system able to provide traffic information regarding specific network devices (eg, servers, switches etc)? How is system configuration and network traffic data backed up? Can this be done across the network? Will the system “alarm” in the case of failure of any networking element? Can the system be set to “alarm” when user configurable traffic thresholds are reached?

Product Development

To assist in the evaluation of the products offered, suppliers shall provide the following information in respect of their product development plans:i. ii. iii. iv. v. vi.

7.9

Details of the manufacturer’s plans to upgrade the product line to support 10Gigabit/s Ethernet. Details of how support for IPv6 will be incorporated into the products proposed. A detailed description of the development plans and upgrade paths for the product(s) offered for the next 2 years. A general description of the product strategy covering the next 4 years. Details of any development plans in respect of the management system. Details of any development plans in respect of the firewall.

Other Functionality

Please provide details of any other functionality which you believe may be of particular interest to the University.

University of Stirling Data Networking Framework Tender v1.0F

Page 31


4C Strategies Ltd

APPENDIX A – CORE NETWORK PORT REQUIREMENTS

University of Stirling Data Networking Framework Tender v1.0F

Page 32


4C Strategies Ltd

Approximate initial Port Requirements Gbmain and distribution layer 36 * gbic / sfp module 48 * utp 4 * 10G: 1 * 10G connection to GBACR core switch 1 * 10G connection to replacement for ne99681 gbacr 4 * 10G for: 1 * 10G connection to new gbmain 1 * 10G connection to main L2 switch for gbacr 24 * 1G sfp smaller local connections (e.g. L2 switch for local laptop/desktops) Note optional costs are required on the pricing schedule to provide 8 port 10G modules in lieu of the 4 port requirement identified above.

University of Stirling Data Networking Framework Tender v1.0F

Page 33


4C Strategies Ltd

APPENDIX B – PRICING SCHEDULE To Follow

University of Stirling Data Networking Framework Tender v1.0F

Page 34


stiuni