Project No.:
Document No.:
NETWORK TECHNICAL SPECIFICATION
Project name
insert project name
Release
Draft/Final
Date:
Author:
Project
Director:
Project
Champion:
Accountable
Body:
Imperial College – Commercial in Confidence
81915004
insert project name
Date:
.
DOCUMENT HISTORY
Document
Location
This document is only valid on the day it was printed.
The source of the document is:
Revision History
Revision
date
Distribution
Author
Summary of Changes
New
Version
This document has been distributed to:
Name
Title
Date of
Issue
Version
PURPOSE
To document the network specifications within a project. Identify any hardware or network
resources required and associated timelines. To illustrate the architecture on which a proposed
solution is built and demonstrate that consideration has been given to network capacity, resilience
and ongoing maintenance.
CONTENTS
Network Requirement ..................................................................................................................... 3
Architecture ................................................................................................................................. 3
Procurements .............................................................................................................................. 3
Resources ................................................................................................................................... 3
Capacity and Resilience .............................................................................................................. 3
Monitoring ................................................................................................................................... 4
Maintenance ................................................................................................................................ 4
Change Control ........................................................................................................................... 4
Risks ........................................................................................................................................... 4
Related Documents ........................................................................................................................ 4
Technical Approval .......................................................................................................................... 5
Imperial College – Commercial in Confidence
Page 2
81915004
insert project name
Date:
.
NETWORK REQUIREMENT
Ensures the project uses standards based network technologies
Will the project fit into an existing infrastructure or will it require new network hardware or
infrastructure?
The College uses a standards based IP network.
Where possible all product(s)/service(s) should be physically located in ICT controlled space.
Architecture
A physical and logical diagram (in MS Visio) must be produced and should be maintained in the
Configuration Library or CMDB
Illustrate all components that make up the entire system and any physical connections required for
connectivity to the IP network or storage networks (e.g. fibre optic connections, copper RJ-45 or
other, cabinets/racking space)
Illustrate all devices that make up the entire system including dependencies (e.g. authentication
services), data links/feeds (e.g. HR data), storage (e.g. SAN, local disks), security (e.g. firewalls)
Procurements
Should any network hardware/infrastructure be required indicate:
1. Funding source and any tendering processes or purchasing requirements
2. Required date(s) or milestones if over several stages
3. Indicate consideration to other projects or services
Resources
What are the technical resources required to implement and maintain the product(s)/service(s)?
Consider technical skills
Consider time required for each stage of the project
Consider ongoing technical resource to support the end product(s)/service(s) in an operational
environment
What are the hardware/infrastructure resources required for delivery of the product(s)/service(s)?
Capacity and Resilience
Will the final product be under an SLA?
How will resilience be provided for the service? Consider and include options:
1. Hardware Server Load Balancing of multiple servers
2. Multiple servers in HA clustered configurations (High Availability)
3. Dual attachment of servers/services (NIC Teaming)
4. DR (Disaster Recovery) and business continuity (see Security Technical Specification)
5. Identify single points of failure for the service and document (e.g. authentication services)
N.B. To allow virtualisation of services service names should not be directly linked to the hostname
of any server providing the service. All service names should be an alias to the server(s) providing
the service (see Virtualising Services document for further information).
Consider bandwidth requirements
Consider peak usage/load requirements (e.g.
product(s)/service(s))
Consider anticipated growth
Consider failure modes
back
ups,
peak
periods
of
usage of
Imperial College – Commercial in Confidence
Page 3
81915004
insert project name
Date:
.
Monitoring
How will the product(s)/service(s) be monitored?
How will alarms or status be reported to Operations/Support? (may include 3rd party support
services)
What reporting (if any) will be required?
Consider: to whom, how often, what format and what information should be reported
Maintenance
What maintenance of the product(s)/service(s) will be required?
Consider warranties of products or support contract(s), any ongoing costs and renewal of support
contract(s), maintenance and location of information referring to support contracts (typically
CMDB/TrackIT)
How will maintenance requirements be met?
Consider and agree impact of maintenance processes and procedures (e.g. complete loss of
service, reduced service, agreed regular periods for maintenance)
Change Control
Describe the change control processes (standard, urgent and emergency) in line with ICT Change
Control policy
Consider notifications and approvals
Consider updates to CMDB or Document Library and document owners
Risks
Identify all risks associated with the product(s)/service(s) and implementations
Identify any contingency plans
RELATED DOCUMENTS
This document should inform the Release to Production documentation.
Refer to any Security and Platform technical specification documents
Imperial College – Commercial in Confidence
Page 4
81915004
insert project name
Date:
.
TECHNICAL APPROVAL
Any Network Technical Specification being proposed requires review by the teams that will
implement it and service it in production. In seeking approval, ensure to gain commitment from the
Technical teams that implementation of the proposed platform is realistic and achievable within the
resources available.
APPROVAL:
Threshold
Accountable
Body
£0-100k
N/A
£100k-1m
Operations
Committee
£1-5m
Management
Board
Council
>£5m
Approval
Please Tick
Operations
Services
Security Team
Manager/Network
Operations
Manager/Data Centre
Operations Manager
Data Centre
Manager/Security Group
Manager/Network Group
Operations Manager
Faculty Support
Manager/Business
Systems Support
Manager/Service Desk
Manager
ICT Link
Manager/Campus
Support
Manager/Service
Delivery Manager
Head of IT Services

Deputy Director of ICT

Head of Technology
Operations
Director of ICT


Name:
Signature:
Date:
………………………
………………………
………………………
………………………
………………………
………………………
Name:
Signature:
Date:
Name:
Signature:
Date:
Imperial College – Commercial in Confidence
Page 5