SOW For System Integrator DSCL v1.1

Scope of work of Dehradun Smart City Project-System Integrator
Scope of work for Dehradun Smart City Project – System Integrator
Version 1.0 Rev 01
Technology Doc. No: 006/2021
Release Date: 25th February 2021
(Confidential document)
Document History
Sr. Release Effective

Document Name Version Revision Remarks / Amendment
No. Date Date
1 Scope of work for 1.0 01
DSCL Project-SI
(Data Center)
Page 1 of 46
Confidential
Contents
1 Introduction.........................................................................................................................5
1.1 Technical submission...................................................................................................5
2 Technical Requirement of Network.....................................................................................6
2.1 High Level BoQ.............................................................................................................6
2.2 Technical Specification.................................................................................................7
2.2.1 Server.....................................................................................................................7
2.2.2 Storage...................................................................................................................8
2.2.3 Antivirus..................................................................................................................9
2.2.4 Workstation...........................................................................................................10
2.2.5 LAN Switch...........................................................................................................11
2.2.6 Racks....................................................................................................................11
2.2.7 Syslog server........................................................................................................12
2.2.8 Element Management System.............................................................................13
2.2.9 Firewall.................................................................................................................16
2.2.10 Backup Software................................................................................................18
2.2.11 NTP Server.........................................................................................................19
3 Planning and Designing the Network................................................................................20
3.1 Data Center Requirement...........................................................................................20
3.1.1 Traffic Flow (Tentative).........................................................................................20
3.1.2 Planning and Design Scope Requirement...........................................................21
3.1.3 Technical Information Criterion............................................................................22
3.2 Responsibility Matrix...................................................................................................22
4 Installation Commissioning, Integration, Acceptance Testing and Handover to Operations
..............................................................................................................................................26
4.1 Overall Scope.............................................................................................................26
4.2 Acceptance Testing....................................................................................................28
4.2.1 Partial Acceptance Testing..................................................................................28
4.2.2 Final Acceptance Testing.....................................................................................28
5 Operations and Maintenance............................................................................................34
5.2 SLA Calculations and Penalties.................................................................................36
Page 2 of 46
Confidential
5.2.1 SLA Calculations..................................................................................................38

6 AMC Contract....................................................................................................................39
6.1 Object of Service........................................................................................................39
6.2 AMC / Support for Services scope.............................................................................40
6.2.1 AMC Support desk...............................................................................................40
6.3 Trouble Ticketing........................................................................................................40
6.3.1 Telephone availability and Call Back time...........................................................42
6.3.2 Severity Levels.....................................................................................................43
6.3.3 RCA for Critical outages.......................................................................................44
6.4 Software Maintenance support...................................................................................44
6.4.1 Software Updates / Patch Fixing..........................................................................44
6.5 Hardware Maintenance Support.................................................................................45
7 Acronym............................................................................................................................47
1 Introduction
The objective of Dehradun Smart City Limited (DSCL) is to leverage the existing resources and
assets and use it optimally based on real time requirement and to improve the quality of service of
its citizen. To make this happen all the various Smart Elements like Wi-Fi, City surveillance, Digital
Display Board and Smart Lighting for citizen service need to be monitored and resource allocation
should happen on real time requirement basis. This leads to the need to connect these smart
network elements by a reliable, scalable, and high available Data Center network.
The scope of work for the partner in the Dehradun Smart City Project will be end to end starting
from planning, survey, installation and commissioning, integration, and Acceptance Testing and
handover to Operations. For that the partners must comply with the DSCL RFP and SmartX
requirement in entirety. Partner also must ensure that the philosophy of design, planning
assumptions and dimensions are adequate to meet the uptime requirement of RFP. For better
understanding and clarity, the entire scope of work will be divided into following subsections
• Planning and Design of the Network

• Installation, Commissioning, Integration and Handover to Operations
• Operation and Maintenance
• Annual Maintenance Contract
Page 3 of 46
Confidential
1.1 Technical submission
The partner participating in the RFP along with the compliance for the above scope has to
submit the following document as part of the technical submission
1. Requirement of SmartX – Partner understanding of customer requirement as mentioned

in these document
2. Technical Compliance – Partner to provide compliance for all Data Center components
like firewall, Compute (Server / Storage), NOC Switch (Distribution), Core Router, etc
3. Solution document – Capturing the logical connectivity and complete design of Data
Center, ICCC (LAN), Traffic flow from Field element till Command-and-Control Center via
Data Center, Technical Write-up and any other valuable Information which is required to
highlight the working of the overall system.
4. Server sizing for Applications like EMS, NTP server etc, Partner to identify the additional
applications to run overall solution till the completion of O&M, and include them in the
proposed solution.
5. Power, Space and Weight sizing for all the proposed components
6. BoQ in excel including spares as per MTBF/MTTR & uptime require of network.
7. Attach the detailed datasheets of all the proposed products.
Note: Partner to mention all Non-Compliance / Deviations etc in a separate section or document
with respect to the requirements of this document.
2 Technical Requirement of Network
The partner needs to capture and document all the assumptions, planning and dimensioning
principles, rules and inputs considered to plan and design the network. To prepare a high-level
solution document and network architecture visualizing to deliver the solution to fulfill the DSCL RFP
and Smartx requirement. In case of any deviation and technical requirement which the partner
solution is not complying, the partner need to be clearly highlight the same in a separate and
prominent heading of exclusion. In the absence of the same Smartx will assume that all the
requirement of DSCL RFP and SmartX requirement is fulfilled by partner solution in totality. Partner
to ensure to fulfill the requirement of DSCL RFP and Smartx requirement, the proposed BOQ is
final. Any change of BOQ to meet the RFP requirement or customer requirement at a later stage will
not be entertained by Smartx and will be the responsibility of partner.
2.1 High Level BoQ
Below is the list of items supplied by the Supplier under this project. This list forms the objective of
service under AMC scope of work.
S No Description Quantity Deployment Scope
Page 4 of 46
Confidential
Server / Storage
as per sizing of
1 Lot Data Center
applications of
Smart Elements
Server
2 Lot Data Center
Virtualization
3 Antivirus Lot Data Center
4 Workstation 2 Data Center
5 LAN Switch 1 ICCC
42U Rack (with
Cable Manager,
6 3 Data Center
MCB and other
accessories)
Power cable of
Suitable
dimension as
per the planned
load from UPS
7 Tapping point till Lot Data Center
the PDU of
Racks and
Earthing from
Racks till
Earthing point.
8 Syslog server 1 Data Center
Note – The above BOQ along with the Optional items mentioned below are subject to change as per
the network or solution or Smartx requirement. Smartx as its sole discretion can increase, decrease
or remove any line items
Optional Items:
Deployment
S No Description Quantity
Scope
1 Firewall 1+1 Data Center
Element
2 Management 1 Data Center
System
Backup Software+
3 1 Data Center
Tape Library
4 NTP Server 1 Data Center
2.2 Technical Specification
Page 5 of 46
Confidential
2.2.1 Server
Partner
Remarks
Sno Compliance
(Actual
values)
The server hardware offered for the NOC shall meet the following
minimum requirements. The servers shall be sized such that its
processing capacity utilization should not exceed 70% of total processing
1 capacity at peak load
2 The Server shall be configured with redundant power supply.
3 Server shall be with loaded with atleast 16x1G ports (optical)
Blade/node Server shall be minimum 24 cores with clock speed of 2.4
4 GHz or higher and minimum 1.5 MB L3 cache per core.
Partner
Remarks
Sno Compliance
(Actual
values)
5 Servers quoted shall have a product support roadmap of minimum 8
years
6 There shall be Separate Management VM server.
The servers shall have connectivity for Ethernet and FC which may be
given in separate interfaces or in combined form and should meet the
7 number of interface requirement as required
Servers shall be configured as per the sizing given by the respective
8 software OEM.
Servers shall be configured with CPU as per inputs from respective
9 software OEM.
The Server shall support Ethernet and fiber channel connectivity as
10 stated above.
11 The Server shall be configured to provide for port level redundancy.
It shall support remote/virtual KVM capability from an external keyboard,
video monitor and mouse to all blades installed in the chassis through
the management controllers and shall also support virtual media for
12 DVD access.
The Server shall be provided with hypervisor to enable provisioning
multiple virtual machines (VMs) on the Server. It should provide
distributed RAID and cache mirroring for intelligent placement of VM
objects across disks, hosts and server racks for enhanced application
availability and achieve Zero data loss with zero downtime in case of
13 disk, host and network failure.
i. The virtualized environment (including hypervisor) to be created at
14 NOC shall be capable to create and manage at least 100 VMs in total.
ii. The Solution must offer ability to Copy, convert, or migrate an image
15 (P2V, V2V, V2P & P2I).
16 iii. The management should provide Orchestration facility which would
simplify installation and configuration of the powerful workflow engine in
Management. The workflows should be launched directly from the Web
Page 6 of 46
Confidential
Client itself.
Server shall have 2x16 Gbps FC & 4x1/10 Gbps LAN ports. Server can
directly interface with Storage without requirement of SAN Switch
17
2.2.2 Storage
Partner
Sno Compliance Remarks
(Actual values)
The data should be available ONLINE for at least 12 Months and
1 archived data should be available for at least next 1 year.
a) Storage array shall comply with technical specifications
mentioned on TEC GR No TEC/GR/I/ESI-001/03/MAR12 for Mid-Tier
2 Storage.
Partner
Sno Compliance Remarks
(Actual values)
System to have at least Two (2) controllers, each controller shall have
64 bit CPU or higher. The Cache shall be mirrored and destaged. The
storage arrays shall have at least 128GB & above Cache across
3 controllers.
The Storage should have battery backed up to avoid any data loss in
4 case of power failure or cache module failure.
The storage array shall support the features to remove redundant
data, Data compression, for data reduction & for efficient use of
storage capacities, Secure Multi Tenancy for shared storage
infrastructure, Space efficient replicas/clones reduced total storage
5 capacity etc.
Storage System solution to have minimum 4 X 16 Gbps FC Ports per
Storage, 8 x 1GigE IP Ports for NAS functionality & 2 x 10 Gig Ports
6 for ISCSI functionality.
Easy to use GUI based and web enabled administration
interface for configuration, storage management. Storage
Management software must include both GUI and CLI tools. It must
be able to centrally manage the vendor’s same class of arrays over
the network. It must support web-based management. It must support
event auditing for security. Shall be able to support automated email
7 to vendor support centre for proactive maintenance.
Storage system shall be offered with native space saving
capabilities for data storage such as compression and de-duplication
8 without impacting the storage performance.
Storage management software shall be browser-based/web enabled
9 accessible over IP
Storage management software shall be able to perform and monitor
local and remote replication operations. Storage management
10 software shall be able to configure and manage tiering
Page 7 of 46
Confidential
Storage management software shall provide real time monitoring and

historical analysis of storage performance data such as total IOPS,
read%, write %, throughput, etc. for analyzing performance of the
11 systems.
Shall support Industry standard virtualization hypervisor like Hyper-V,

12 VMWARE and Citrix.
2.2.3 Antivirus
Sno Compliance Partner Remarks (Actual values)

The antivirus software shall be enterprise class
1 along with latest version of software.
Antivirus software should be upgradable to latest virus
2 definitions on periodic basis.
Page 8 of 46
Confidential
The solution should provide endpoint security solutions

to eliminate the agent footprint from the virtual
machines, offload intelligence to a security virtual
appliance, and run scans with minimal impact and
3 enhance virtual machine performance.
The antivirus license should be considered for the
4 contract life time.
2.2.4 Workstation

Latest generation 64bit X86 Quad core
1 processor(3Ghz) or better
2 Latest series 64bit Chipset
3 OEM Motherboard
Minimum 8 GB DDR3 ECC Memory @ 1600 Mhz.
Slots should be free for future upgrade. Minimum 4
4 DIMM slots, supporting up to 32GB ECC
2 TB SATA-3 Hard drive @7200 rpm with Flash Cache
of 64GB SSD. Provision for installing 4 more drives.
5
10/100/1000 Mbps autosensing on board integrated
6 RJ-45 Ethernet port.
7 Audio-Line/Mic IN, Line-out/Spr Out (3.5 mm)
8 104 keys minimum OEM keyboard
9 2 button optical scroll mouse (USB)
22” TFT LED monitor, Minimum 1920 x1080
resolution, 5 ms or better response time, TCO 05 (or
10 higher) certified
11 64 bit pre-loaded OS with recovery disc
BIOS controlled electro-mechanical internal chassis
12 lock for the system.
Loaded with Advanced antivirus, antispyware, desktop
firewall, intrusion prevention (comprising of a single,
deployable agent) which can be managed by a central
server. (Support, updates, patches and errata for the
13 entire contract/ project period)
To be loaded with Licensed version of MS Office, PDF
viewer and other basic softwares required to run the
14 operations
2.2.5 LAN Switch
Page 9 of 46
Confidential
12 ports minimum -1G Ethernet ports 2 numbers of

1 Uplink ports -1G /10G Optical (Multimode)
All ports can auto-negotiate between all allowable
speeds, half-duplex or full duplex and flow control for
2 half-duplex ports.
3 Support 10K MAC address.
4 Throughput-500 Mpps or better
Must support Port Mirroring, Port Trunking and
5 802.3ad LACP Link ,Aggregation port trunks
6 Support 802.1X Security standards
7 DHCP support
8 Support up to 1024 VLANs
9 Support IGMP Snooping and IGMP Querying
10 Support Multicasting
11 Should support Loop protection and Loop detection,
12 Support port security
13 Support 802.1x (Port based network access control).
14 Support for MAC filtering.
Should support TACACS+ and RADIUS authentication
15
Support 802.1Q Tagged VLAN and port based VLANs
16 and Private VLAN
The switch must support dynamic VLAN Registration
17 or equivalent
18 Dynamic Trunking protocol or equivalent supported
Network Time Protocol or equivalent Simple Network
19 Time Protocol support
Should have accessibility using Telnet, SSH, Console
access, easier software upgrade through network
using TFTP etc. Configuration management through
20 CLI
Should support AC and DC power supplies, for BoQ
21 consider AC power supply
22 Redundant Fans
2.2.6 Racks

Floor Mount Rack with Caster wheels - 42U with
Heavy Duty Extruded Aluminum Frame for rigidity. .
Top & Bottom cover with cable entry gland plates.
Heavy Duty Top and Bottom frame of MS. Two pairs
1 of 19" mounting angles with 'U' marking. Depth
Page 10 of 46
Confidential
support channels - 3 pairs. It should have both options

of wheel and grouting.
2 Front and Back doors should be perforated

All racks must be lockable on Front and Back sides
3 with unique key for each rack
Racks should have Rear Cable Management
4 channels, Roof and base cable access
The racks must have steel (solid / grill / mesh) front /
rear doors and side panels. Racks should NOT have
5 glass doors / panels
Both the front and rear doors should be designed with
quick release hinges allowing for quick and easy
6 detachment without the use of tools.
Tentative Rack Layout and Power requirement-
Note: Input power supply per rack will be 5-6 KW.
2.2.7 Syslog server

System Logging Protocol (Syslog) is a way network
devices can use a standard message format to
1 communicate with a logging server.
Devices can use a Syslog agent to send out
notification messages under a wide range of specific
2 conditions.
These log messages include a timestamp, a severity
rating, a device ID (including IP address), and
3
Page 11 of 46
Confidential
information specific to the event.

Syslog messages must be in a human-readable format
4
Syslog server is required to fetch logs from EMS,
firewall and other DC components, as per requirement,
Partner to ensure this integration. A Syslog server
needs to receive messages sent over the network
5
It should also have management and filtering software
that enables the server to automatically generate
6 alerts, alarms, and notifications
Partner to ensure the integration with any third-party
system like SIEM for pushing the logs from syslog
7 server to these systems
2.2.8 Element Management System

The Element Management System (EMS) is an
important requirement of this Project. Various key
1 components of the EMS are:
2 • SLA monitoring
3 • Network Monitoring System
4 • Server Monitoring System
• Integration with Helpdesk System, Trouble
5 ticketing etc, if required
Proposed EMS Solution shall be based on industry
6 standard best practice framework such as ITIL etc.
7 SLA & Contract management System
The SLA & Contract Management solution should
enable the Authority to capture all the System based
SLAs defined in this Tender and then calculate
quarterly (or for any duration) penalty automatically.
Measuring service performance requires incorporation
of a wide variety of data sources of the Surveillance
project. The SLA solution should support the
collection data from various sources in order to
calculate Uptime / Performance / Security SLAs.
Various features required in this component to EMS
8 are -
• It must be a centralized monitoring solution for
all IT assets (including servers, VMs, Application
9 instances, network equipment etc.)
• The solution must have integrated dashboard
providing view of non performing components / issues
10 with related to service on any active components
• The solution must follow governance,
11
Page 12 of 46
Confidential
compliance and content validations to improve

standardization of service level contracts

• Application should be pre-configured so as to
allow the users to generate timely reports on the SLAs
12 on various parameters.
• The solution must support Service Level
Agreements & Lifecycle Management including
Version Control, Status Control, Effectively and audit
13 Trail to ensure accountability for the project.
• The solution must have the ability to define and
calculate key performance indicators from an End to
End Business Service delivery perspective related to
14 this Project
• The solution should support requirements of the
auditors requiring technical audit of the whole system
· The solution most have an integrated dashboard,
view of Contract Parties & current SLA delivery levels
15 and view of Services & current SLA performance
• The solution should support SLA Alerts
16 escalation and approval process.
• Solution should support effective root cause
analysis, support capabilities for investigating the root
causes of failed service levels and must make it
possible to find the underlying events that cause the
17 service level contract to fail.
• Accept Data from a variety of formats; provide
pre-configured connectors and adapters, Ability to
define Adapters to data source in a visual manner
18 without coding.
• Support for Defining and Calculating Service
19 Credit and Penalty based on clauses in SLAs.
20 Reporting
• Ability to generate reports on penalty and credit
due, to check on non-compliance of SLAs for the
21 surveillance project
• Monetary penalties to be levied for
noncompliance of SLA, thus the system must provide
Service Level Performance Report over time,
22 contract, service and more.
• The solution should provide historical and
concurrent service level reports for the surveillance
project in order to ensure accountability of the service
23 provider’s performance
• Automatic Report creation, execution and
Scheduling, must support variety of export formats
24 including Microsoft Word, Adobe PDF etc.
Page 13 of 46
Confidential
• The solution must support Templates for report

generation, Report Filtering and Consolidation and
Context Sensitive Drill-down on specific report data to
drive standardization and governance of the
25 surveillance project
• The solution must support security for drill-down
capabilities in dashboard reports ensuring visibility for
26 only relevant personnel of the surveillance project

• Support real-time reports (like at-a-glance status)
as well as historical analysis reports (like Trend, Top N,
27 Capacity planning reports etc.)
o Resource utilization exceeding or below
28 customerdefined limits
o Resource utilization exceeding or below predefined
29 threshold limits
An indicative List of SLAs that need to be measured
centrally by SLA contract management system are
given in the Tender Document. These SLAs must be
represented using appropriate customizable reports to
30 ensure overall service delivery.
31 Network Management System
Solution should provide Fault, Configuration &
Performance management of the entire data centre
infrastructure and should monitor IP\SNMP enabled
devices such as Routers, Switches, Cameras, Online
UPS, etc. Proposed Network Management shall
integrate with SLA & Contract Management system in
order to supply KPI metrics like availability, utilization
in order to measure central SLA’s and calculate
penalties. Following are key functionalities that are
required, which will help measuring SLA’s as well as
assist administrators to monitor network faults &
performance degradations in order to reduce
downtimes, increase availability and take proactive
32 actions to remediate & restore network services.
o The proposed solution must automatically discover
manageable elements connected to the infrastructure
and map the connectivity between them. Solution
should provide centralized monitoring console
displaying network topology map from central location
33 to Zonal / Police Station Level.
o Proposed solution should provide customizable
reporting interface to create custom reports for
34 collected data.
o The system must use advanced root-cause
analysis techniques and policy-based condition
35 correlation technology for comprehensive analysis of
Page 14 of 46
Confidential
infrastructure faults.
o The system should be able to clearly identify
configuration changes as root cause of network
problems and administrators should receive an alert in
case of any change made on routers spread across
36 surveillance project.
o Network Performance management system should
provide predictive performance monitoring and should
be able to auto-calculate resource utilisation baselines
for the entire managed systems and networks and
allow user to set corresponding upper and lower
threshold limits based on baseline data instead of
37 setting up manual thresholds for monitored devices.
o The system must support the ability to create
reports that allow the surveillance administrators to
search all IP traffic over a specified historical period,
38 for a variety of conditions for critical router interfaces.
• The proposed system must be capable of
providing the following detailed analysis across
39 surveillance domain:
o Top utilised links (inbound and outbound) based on
40 utilisation of link
41 o Top protocols by volume based on utilisation of link
42 o Top host by volume based on utilisation of link
Server Performance Monitoring System

o The proposed tool should integrate with network
performance management system and support
operating system monitoring for various platforms
supplied as part of the Surveillance Project.
o The proposed tool must provide information about
availability and performance for target server nodes.
o The proposed tool should be able to monitor
various operating system parameters such as
processors, memory, files, processes, file systems,
etc. where applicable.
o The solution should provide a unified web based
console, which consolidates all aspects of role based
access under a single console.
o Proposed Network Management shall integrate
with SLA & Contract Management system in order to
supply KPI metrics like availability, utilisation, and
performance in order to measure central SLA’s and
calculate penalties.
Note: Tentative number of Elements to be managed is as follows-

Page 15 of 46
Confidential
1. Routers-5 (3 Aggregate, 2 Internet Router)

2. Switch -34 (30 Access Switch. 2 NOC Switch, 2 LAN Switch)
3. Firewall-2
4. Server- Option 1: 10 Rack Server with Total 50 VMs, Option 2: One Chassis-Blade server
with
50 VMs
(Excluding applications supplied by SI, SI to include elements supplied by it’s own)
5. Approx. 70 instances of Applications.
6. Additional 50 Licenses for Future purpose.
2.2.9 Firewall
Sno Compliance OEM Remarks (Actual values)

The proposed firewall shall be installed in HA mode and
secure the NOC applications from being accessed from
1 external network.
The Firewalls should be Hardware based, Redundant,
Reliable, purpose-built security appliance with hardened
operating system that eliminates the security risks
associated with general-purpose operating
systems with minimum 8 Nos. FE ports, 4 optical
2 ports of 1G
The Appliance should be Full-featured, high-performance
firewall, and IP Security/Secure Sockets Layer (IP
Sec/SSL) VPN technologies deliver robust application
security, user- and application-based access control, and
3 remote user/site connectivity.
The communication between all the components of
Firewall System (firewall module, logging & policy
management server, and the GUI/Web UI Console)
4 should be encrypted.
Firewall should support for static and dynamic routing
capabilities. The firewall should support open standard
5 protocols like RIP, OSPF and BGP.
The firewall should have at least local hard-disk or
equivalent, in order to keep the event logs in the event of
management server connection failure, etc. Provide
6 detailed information.
7 Firewall Throughput of Up to 1 Gbps.
8 VPN Throughput of Up to 1 Gbps.
Virtual Interfaces (VLANs) support for at least 100
9 VLANs for forming secure server Farms and DMZs.
10 Scalability through VPN clustering and load balancing.
Page 16 of 46
Confidential
VPN Module integrated with the firewall, IP Sec,

Dedicated tunnels, Encryption (DES, 3DES, AES), SHA-
1 / MD5 authentication, IKE certificate authentication
11 (X.509), Dead peer detection, NAT Traversal supported
Firewall should support Active/Active with Stateful
12 Failover for IP Sec VPN Connections.
13 Firewall should have a dedicated Console port
14 Firewall should have a Management port
Equipment must support SNMP v1/v2 for integration with
Element Management System. OEM to extend all
support in integration of device into third party Element
15 management system, if required
PAT/NAT logs to be stored and pushed towards syslog
16 server or any other third-party application
Sno Compliance OEM Remarks (Actual values)
Any changes or commands issued by an authenticated
17 user should be logged.
18 Must have IDPS and URL blocking capability
19 Space Requirement
20 Power Requirement (Max)
21 Ports-SFP
22 1G FE-8 (For 2 Firewall)
23 1G SR-8 (For 2 Firewall)
2.2.10 Backup Software
Partner Remarks
Sno Compliance
(Actual values)
1 Backup Database Management:
The solution should be able to back up the database and allow user
2 to backup all necessary files.
The system should be able to back up at least database files, log
3 files and system files.
The system shall have the ability to back up any of its system or
data files on demand or on a regularly basis. The timeframe for
regularly scheduled backups shall be user settable to any time of
day, may have a daily cycle, or may be different depending on the
day of the week, or have a weekly cycle. The system must be
capable of being backed up or restored from a single backup
device, at each physical location, and controlled from a single
console device. The system backup strategy selected shall be
designed to require no human intervention under non-failure
4 conditions for a configurable number of days.
Page 17 of 46
Confidential
Restoration of the whole system or any individually replaceable

5 functional software unit must be possible e.g. database.
All application software updates and database conversions to the
6 system shall be non-service affecting.
8 Backup & Restore Software:
Backup Software shall be capable of supporting backup /restore
9 from various platforms, VMs and Instances.
Ability to backup data from one server platform and restore it from
another server platform to eliminate dependence on a particular OS
machine and for disaster recovery purposes, as per software
10 application / database to be proposed by bidder please.
Software shall have full command line support on above mention
11 operating systems.
Partner Remarks
Sno Compliance
(Actual values)
Shall support wizard-driven configuration and modifications for
13 backups and devices.
The backup software shall support industry standard Common
14 Device Interface for advanced device reporting and handling.
Shall have cross platform Domain Architecture for User
management and shall also have role-based User management and
15 access control for multitenant environments.
16 Shall support de-duplicated backup and recovery.
Shall support backups for clustered servers and shall have the
ability to backup data from clustered servers from the virtual client,
backing up data only once and giving consistent backup in case of
17 failover of nodes.
18 Shall support backup / recovery of raw SCSI volumes.
The backup software shall support backup and restore of NDMP
19 data to media server attached Tape/NAS/Network Storage.
The backup software shall support for online backup for all the OS /
Data Bases supplied with out of box agents. Backup licenses shall
21 be provided based on database being used in the system.
Must support Hardware and storage array-based snapshot backup
for off host zero downtime and zero load on the primary backup
22 client.
The backup software shall support data movement directly from the
backup client to the disk target without passing through the backup
23 server.
2.2.11 NTP Server

Supports multiple NTP ports accommodates modern
networks as well as ones destined to be upgraded at
1 some future point in time
Page 18 of 46
Confidential
Keeps the network synchronized to a Reference

2 Clock Source
Must have ability to handle coincidental peak loading
3 of NTP requests (upto 500 devices)
4 Supports integration with external clocks
5 Must have separate client and server applications
Note: For total number of elements, Please refer “Note” below EMS Specifications.
3 Planning and Designing the Network
The partner needs to capture and document all the assumptions, planning and dimensioning
principles, rules and inputs considered to plan and design the network. To prepare a high-level
solution document and network architecture visualizing to deliver the solution to fulfill the DSCL RFP
and SmartX requirement. In case of any deviation and technical requirement which the partner
solution is not complying the partner need to be clearly highlight the same in a separate and
prominent heading of exclusion. In the absence of the same SmartX will assume that all the
requirement of DSCL RFP and SmartX requirement is fulfilled by partner solution in totality. Partner
to ensure to fulfill the requirement of DSCL RFP and SmartX requirement, the proposed BOQ is
final. Any change of BOQ to meet the RFP requirement or customer requirement at a later stage will
not be entertained by SmartX and will be the responsibility of partner.
3.1 Data Center Requirement
Data Center will consist of mostly Compute, Routing / Switching and Security Infrastructure to host
Centralized management applications for managing Smart elements like Wi-Fi hotspots, CCTV
camera, Smart Lighting and DBBs. As part of the project SmartX will install, 30 no of AP, 20 no of
CCTV camera, 30 no of VMD screen, and 60 no of Smart LED light The estimated bandwidth
capacity requirement of these elements is as listed below
Total
Smart City Unit Component Requirement Requirement
Sl No
Element (Mbps)
(Mbps)
1 Wi-Fi 50 1500
2 Camera 20 400
3 VMD 2 60
4 Smart Light 2 120
6 Total 74 2080
3.1.1 Traffic Flow (Tentative)
Page 19 of 46
Confidential
• In Data Center, we will terminate the ILL bandwidth of 100 Mbps (initially), to be terminated
on firewall (tentatively).
• Traffic from Network (field) side will terminate on Core (Aggregate) router installed in Data
Center. NOC Switch will be used for the interconnectivity of the devices in Data Center ie.,
Server/storage, Firewall, Routers and LAN Switches.
• Traffic from Network will flow towards compute Infrastructure where centralized management
applications will be installed.
• NOC users from ICCC will get access to these applications from LAN, connected via NOC
switch through Local LAN switch.
• Few applications may require integration with cloud-based applications on secured VPNs
through ILL.
3.1.2 Planning and Design Scope Requirement
As mentioned at the beginning the partner scope will be turnkey in nature and will be responsible for
end to end of all design and planning activities. However, the key expectation and deliverable of the
partner for better clarity are as mentioned below
• The partner to study the DSCL RFP and SmartX requirement and propose the most optimal
solution in line with customer requirement and RFP conditions
• The Partner to study and understand the Planned OFC and transport network for this project
along with the site locations for smart elements, based on this, partner will require to plan
traffic flow. This plan can be changed and need to be updated accordingly in case of any
change in OFC network or locations as suggested by SmartX /DSCL.
• Partner to support and keep in records for the plan of DCN, IP, VLAN, Bandwidth and
synchronization planning for the entire network in consultation with partner of Transport and
other smart elements
• Partner to do the Server sizing, Backup sizing, Power, Space and Cooling calculations for
the Applications and Devices to be hosted in Data Center. Datasheets and Manuals of all
components (which will be supplied by respective OEMs) will be shared with partner.
• Partner to understand the requirements of Third party items integration including but not
limited to existing Infrastructure of DSCL and consolidate them.
• Partner to plan and raise the requirements for all integrations related activities and share
with SmartX / DSCL timely.
• Partner to prepare consolidated HLD / LLD capturing end to end flow (in format, as asked by
SmartX / DSCL). Individual components HLD / LLD will be shared by the respective OEMs
of CCTV, DBB, Smart Light and WiFi. For Data Center components, partner to prepare
consolidated HLD/LLD
• The deliverable or requirement from SmartX side as per the proposed solution has to be
explicitly mentioned as separate heading and agreed with SmartX in writing.
• Partner to plan the Virtualization of Server, as per the requirements raised by various stake
holders of application OEMs and the applications provided by the partner.
• Partner to plan for the BoQ of all Virtualization, OS, DB etc related requirements for the
above point.
• Partner to plan a monitoring platform for all VMs (Example-VCenter) and consider all
underlying requirements for the installation of the same.
• Partner to plan the Policies to be applied on firewall, in consultation with the by various stake
holders of application OEMs and considering the requirements of his own applications.
Page 20 of 46
Confidential
• Partner to propose only those software applications which are Secured, COTS and have
Security certificates available from some third party agency.
• Partner to plan and prepare detailed project plan capturing the Manpower requirements and
timelines for completing the milestones inline to the RFP contract.
3.1.3 Technical Information Criterion
Sno Parameter Response

1 Last 3 projects done for Data Center implementation
2 Qualifications of Manpower to be provided for this project
Make and Model of proposed BoQ for asked requirements of Software
3 and Hardware
4 Experience of implementing Smart City projects
5 Experience of Security related audits
3.2 Responsibility Matrix
The high-level responsibility matrix of Partner for Data Center Network Design and Planning are as
follows-
Sl
Description of Activities Responsibility Support Remarks
No
Providing DSCL RFP & SmartX
requirement as the case may be along
1 SmartX
with scope of work or any other related
document
Providing planning and dimensioning

rules and guidelines to arrive at Spares should be
assumption if any and also the dimensioned
preparation of the solution and the taking into account
2 Partner MTBF/MTTR &
supplied BOQ. As part of BOQ spares
require for the solution also to be uptime require of
provided along with complete network
justification of proposed spares
Compliance to DSCL RFP or technical

requirement of SmartX along with
3 Partner
scope of work or any other related
document
DCN, IP, VLAN, Bandwidth and
synchronization planning for the
4 complete network and extending Partner All OEMs
synchronization to other smart city
Page 21 of 46
Confidential
elements as per the network

requirement
Partner to do the Server sizing, Backup
sizing, Power, Space and Cooling
5 calculations for the Applications and Partner All OEMs
Devices to be hosted in Data Center.
Datasheets and Manuals of all
Sl
No
components (which will be supplied by
respective OEMs) will be shared with
partner. Partner to plan the BoQ for
Server and Storage accordingly and
supply the same.
Partner to understand the requirements
of Third party items integration
SmartX /
including but not limited to existing Partner
DSCL
Infrastructure of DSCL and consolidate
them
Partner to plan and raise the
requirements for all integrations related
Partner
activities and share with SmartX /
DSCL timely
Partner to prepare consolidated HLD /
LLD capturing end to end flow (in
format, as asked by SmartX / DSCL).
Individual components HLD / LLD will
be shared by the respective OEMs of
CCTV, DBB, Smart Light and WiFi. For
Data Center components, partner to
Partner All OEMs
prepare consolidated HLD/LLD.
Partner to ensure the approval of the
same from SmartX / DSCL. LLD must
show the card level / Port Level
connectivity, configuration files of all
components, Data Center connectivity
and flow with writeup.
The deliverable or requirement from
SmartX side as per the proposed
solution has to be explicitly mentioned Partner
as separate heading and agreed with
SmartX in writing.
Partner to plan the Virtualization of
Server, as per the requirements raised
by various stake holders of application Partner All OEMs
OEMs and the applications provided by
the partner
Page 22 of 46
Confidential
Partner to plan for the BoQ of all

Virtualization, OS, DB etc related Partner All OEMs
requirements for the above point
Partner to plan a monitoring platform
for all VMs (Example-VCenter) and
Partner
consider all underlying requirements for
the installation of the same.
Partner to plan the Policies to be
applied on firewall, in consultation with
the by various stake holders of Partner All OEMs
application OEMs and considering the
requirements of his own applications.
Sl
No
Partner to plan the protocols to be used
for communication between various
components in Data Center and ICCC,
Partner All OEMs
like Routing protocols -OSPF, IS-IS,
Layer 2 VLANs etc in consultation with
all stakeholders
Partner to propose only those software
applications which are Secured, COTS
Partner
and have Security certificates available
from some third party agency.
Partner to plan and prepare detailed
project plan capturing the Manpower
requirements and timelines for Partner
completing the milestones inline to the
RFP contract
Providing of high level most optimum &
cost-effective solution of the
4 Partner
requirement of DSCL RFP & SmartX
requirement
The BOQ will be
Partner to plan and supply all required
complete in all
5 Patch chords (Optical or CAT6), as per Partner
aspect for the
design and requirement of Data Center
solution proposed.
Propose spares as per MTTR/MTBF
6 calculation in line with uptime Partner
requirement of RFP/ SmartX
BW Planning for end-to-end
7 connectivity of field elements to Partner
NOC/DC
Page 23 of 46
Confidential
To provide all necessary document if

required like test reports, certifications,
Security documents, etc (System In line with RFP
8 Partner
Documents, User Documents as per requirement
DSCL/ITIL Information Technology
Infrastructure Library standards)
Modification or amendment of HLD /
LLD due to site requirement changes
not limited to fiber routes, sites
12 Partner
constraint, project requirement,
customer requirement etc during the
project execution stage
Preparation and consolidation of LLD
from respective OEMs showing the
card level connectivity, configuration of
All
Data Center components, all Smart
13 elements, Partner respective
Data Center connectivity and OEMs
component and obtaining approval from
DSCL/ SmartX or both
Modification or amendment of LLD and
14 SLD due to site requirement not limited Partner
to fiber routes, sites constraint, project
Sl
No
requirement, customer requirement etc
during the project execution stage
Responsible for Planning and

maintaining record of IP (both Public &
Private) of entire network not limited to
15 Partner
Transport, Wi-Fi, CCTV, Digital Display
System, etc during the project
execution stage
Preparing and approving of Installation
16 Acceptance testing document form Partner
SmartX /DSCL as applicable
Preparing and approving of Full
17 Acceptance Testing (FAT) of entire Data Partner
Center Network from SmartX /DSCL
Provide solution to extend API of the
supplied EMS and provide all
necessary support and coordinate to
18 Partner
integrate with
Command Center solution for
consolidated view of the entire network
Responsible and extend all support to
Project team to fully comply with and
19 Partner
FAT (Full Acceptance Testing) of the
Page 24 of 46
Confidential
entire designed Data Center Network

to Operations as per the proposed
solution
Propose any other scope of work which
is not included in this document but is
required for delivery of overall solution
20 Partner
or to meet the RFP requirement on
separate heading for SmartX to review
and agree
4 Installation Commissioning, Integration, Acceptance Testing

and Handover to Operations
4.1 Overall Scope
As highlighted earlier based on the turnkey nature of the project execution the Partner has to
prepare a detailed project plan and get it approved by SmartX /DSCL as applicable in line with
SmartX requirement and as per RFP. As part of project plan the Partner has to provide the project
organization along with the manpower dimension for SmartX to review and approved. During the
entire stage of project execution till the network is handed over to Operations Partner to provide MIS
report of project in line with the format, type and frequency requirement of SmartX & DSCL as the
case may be. The key activities of Partner as part of project implementation from site survey till
completion of handover of entire Data Center Network to Operations after successful Network
Acceptance testing are outlined as below
• All necessary preparation like preparing Site Survey Format and getting it approved from
SmartX /DSCL for initiating site survey
• Get site details from SmartX to get the survey required and also the Partner may have to do
site survey in coordination with DSCL & SmartX to survey and finalize the sites
• On the basis of Site Survey Partner to propose and get approved site wise equipment along
with passive materials as required.
• Ensure the materials whether domestic or imported has to be delivered as per the agreed
timelines to SmartX designated warehouse.
• Imported materials to be delivered on DDP (Delivered Duty Paid) basis.
• Open case inspection (OCI) of delivered domestic and imported materials at SmartX
designated warehouse
• Verify and confirm to SmartX that materials delivered in as per the BOQ mentioned in the
Purchase Order and all materials are delivered to the warehouse. In case of any damage or
quality issue or loss or missing of items report immediately before GRN is raised in the
warehouse
• To take care of logistics for replacement and repair as the case may be for any equipment
dead on arrival or found faulty during the project execution stage and till the time the
network is handed over to Operations
• Site wise kitting (segregation of materials along with Installation kit or accessories) and
labelling of materials as per the approved site wise BOQ (In the SI partner scope will be
limited to Data Center / ICCC components logistics)
Page 25 of 46
Confidential
• To raise indent for requisition of materials from warehouse to site as per the SmartX
process and mutually agreed timelines to ensure the materials reaches site as per the
project timelines requirement
• Responsibility of materials safety and theft once handed over to sites or at warehouse as
the case may be till the time the network is handed over to operations. In case of theft of
material Partner shall follow the process like filing FIR in the local Police Station, etc
• Shifting of materials from one site to another due to change in plan or site conditions
• Undertake installation of all Data Center components (with support of OEMs) strictly as the
per HLD without any deviations. In case of any change then of plan due to site condition or
project priority or any other reason get the revise HLD approved from SmartX or DSCL as
applicable before implementation.
• Propose Acceptance Testing of Installation document along with check to be done for
SmartX & DSCL as applicable to review and approve
• After completion of Installation and before offering the sites for AT do a pre-AT or pre-AT
inspection with self-certification
• Along with the pre-AT self-certification offer the sites for AT to the SmartX quality team in
coordination with SmartX deployment team and getting the sites AT cleared without any
punch or pending points
• Powering up, POST test, configuration and commissioning of Individual equipment and the
network as per the approved LLD document. In case of any changes of either topology,
configuration or any technical parameters from the approved LLD, the modified LLD to be
proposed and get approved before commissioning the network.
• Provision of bandwidth in the transport network as per the requirement of RFP (Initially it
may be done by OEM / partner of transport, later any new configuration or modification has
to be taken care by SI / Partner), SmartX or DSCL as the case may be from the time the
node/partial network is deployed to till the network handed over to operations. During this
period, the provision bandwidth may be deleted or modified or any changes to be done as
per the requirement of SmartX. The bandwidth provision may be for smart elements
installed in Smart City or any other network as per SmartX requirement
• Extending all necessary support to the partner of Transport Network, CCTV, DBB, Wi-Fi,
Service Providers, SmartX, DSCL, etc in making the link through end to end. The support is
not limited to changing in configuration in transport network but collaborative approach to
resolve the issue as per SmartX requirement
• Offering the commissioned network to Final Acceptance Testing to SmartX or DSCL as the
case may be and ensure the conduct of AT as the approved FAT AT document with full
compliance.
• Post Final Acceptance Testing handing over the network to Operations with all necessary
document not limited to Equipment Technical Manual, Site Survey Report, AT documents,
Operations and Maintenance Manual, etc
Training for Customer:
• Partner has to impart one-day training for 2 batch of attendee about 15 peoples at Dehradun
in 2 different dates as per the DSCL/ SmartX requirement
• The training will include the high level understanding of the features and functionality and its
basic operations of equipment or systems supplied by the partner.
• First half will be dedicated for class room training and second half will be shown on the live
system to the extent possible without impact the operations after taking prior permission
Page 26 of 46
Confidential
• The training manual or literature (both hard copy and soft copy) to be provided by partner to
all trainee
• The class room along with Projector and permission to demonstrate on the live network will
be facilitated by DSCL/ SmartX
Partner can add any scope of work that is missed here but is required to deliver overall solution
or RFP requirement and should highlight in separate heading as “Additional Scope Not Covered
in the scope of RFP” for SmartX to review and agree for the same.
4.2 Acceptance Testing
The acceptance test for the Project shall be carried by SmartX or DSCL. The Partner should
cooperate with SmartX /DSCL to ensure successful completion of acceptance tests. The
acceptance test shall consist of a Partial Acceptance Test (PAT) and Final acceptance test (FAT)
depending on the phase wise implementation. The Service Provider shall submit a detailed
acceptance testing document at the stage of planning.
4.2.1 Partial Acceptance Testing
Partial Acceptance Test shall involve scrutiny of documents for various IT / Non-IT components to
verify if the specifications conform to the technical and functional requirements mentioned this
Agreement. SmartX /DSCL reserves right to conduct physical inspection of the equipment delivered
to ensure that they arrive at the sites in good condition and are free from physical damage and
incomplete shipments and shall return the products to the Service Provider at the Service Provider’s
expenses if required quality is not maintained. Physical inspection of hardware will also include
physical checking and counting of the delivered equipment in presence of the Service Provider. This
equipment will only be acceptable as correct when each received item corresponds with the
checklist that will be prepared by the Service Provider prior to shipment. Any shortfalls in terms of
number of items received may render the delivered equipment incomplete. Partner shall submit test
reports on performance for the supplied components. SmartX /DSCL reserves the rights to partially
accept the completion of a component by issuing a partial completion certificate to the Service
Provider. Before rendering the certificate SmartX /DSCL would do the testing in a real time condition
for at least 15 days of trouble-free operation.
4.2.2 Final Acceptance Testing
Post project implementation phase, the Service Provider would need to carry out Final Acceptance
Testing in 2 different phases - (a) Unit Testing and (b) Integration Testing. These tests would be
carried out based on the test cases developed by the Partner and validated by SmartX /DSCL.
Apart from the functional testing of the entire system components, the testing would also verify
following aspects:
• Configuration Testing (to ensure that all the components are configured properly)
• Security Testing (to review & evaluate security controls)
Final acceptance certificate shall be issued by SmartX /DSCL to the Service Provider after
successful testing in a real time condition for at least 15 days of trouble-free operation. The date on
Page 27 of 46
Confidential
which final acceptance certificate is issued for final phase shall be deemed date of the successful
commissioning of the Project. Any delay by the Partner in the performance of its Agreement
obligations shall render the Partner liable to the imposition of appropriate liquidated damages or
termination, unless agreed otherwise by SmartX.
The high-level responsibility of Partner to starting from site survey, supply of materials,
installation, commissioning, configuration, integration testing.
Sl
Description of Activities Responsibility Remarks
No
Prepare a high level & detailed project plan
to complete the projects as per the RFP
1 requirement & agreed scope of work. The Partner
project plan has to be approved by SmartX
& DSCL as applicable
Based on above project plan, propose the
project organization along with manpower
2 Partner
requirement and get it approved from
SmartX & DSCL as applicable
To prepare and submit Site Survey Format
and get it approved from SmartX & DSCL as
3 applicable. This format may be reviewed Partner
and changed and mutually agreed between
all stake holders
Partner has to coordinate
Providing Site Address and Access to Sites or liasion locally to get the
survey done. Further in
for Site Survey. In some cases, Partner has
some cases Partner has to
4 to discuss with DSCL or its Authorized third SmartX discuss with DSCL
party & SmartX to help finalized the site Authority or its authorized
location third party and SmartX to
survey finalized sites
In this exercise the partner
has to coordinate with
DSCL or other Government
agencies within it
Site survey as per the agreed site survey Jurisdiction to get
5 approved format of all sites in coordination Partner permission letter if
with SmartX deployment team. applicable for site survey.
Any type of resources
required not limited to tools,
tester and vehicles, etc to
be arrangement by Partner
On the basis of Survey input Partner to
6 prepare site wise materials which should Partner
Page 28 of 46
Confidential
cover all materials including active or

passive items and submit to deployment to
review and approve
Supply of imported items from Ports to
7 Partner
designated warehouse
8 Customer Clearance of imported items Partner
9 Payment of Import Duties (DDP) Partner
Logistics and Transport of equipment from
10 Partner
Ports to designated warehouse
Sl
No
Open Case Inspection (OCI) in the
warehouse to be done and any issue
11 Partner
(damage/quality/loss) to be reported before
GRN is raised in the warehouse
Verify and confirm the BOQ received at
12 Warehouse is per the Purchase Order and Partner
in case of any shortfall report immediately
If any equipment dead on arrival or found
SmartX to provide
faulty at sites during the project execution
documental support if
13 that is till the time network is handed over to Partner
required and
Operations all logistics to get the equipment
applicable
repaired or replaced
Kitting of material (Segregation of material In line with survey and
14 and labelling sitewise) as per approved Partner approved site wise list of
sitewise BoQ (active/passive/third party) materials
Any shifting of materials
The site wise materials to be Transport from
from one site to other sites
Warehouse to Site based on site conditions
15 Partner for any project related
readiness as per the Indent raised at
activties will be done by
mutually agreed timelines
Partner
16 Weekly materials reconcillation Partner
Responsibility of materials safety from theft,
damage, logistics once delivered to site post
17 Partner
issuance of material from warehouse till the
network is handed over to operations
OEM/ Partner shall ensure the safety of the
material after taking it from warehouse till
AT is conducted. In case of theft of material
Service Partner shall ensure to provide all
18 documentation of invoice/material Partner
inward/outward, FIR etc. to on which is
able to get the claim from Insurance.
Partner has to liaison with insurance
company as well for closure
19 Any change of plan or site conditions due to Partner
project requirement equipment need to be
Page 29 of 46
Confidential
moved from one site to other site

Partner to mark the actual place for
installing Racks in Data Center, and supply
20 all the necessary Power Cabling, earthing Partner
and patch chords as per actual
requirements on site.
The partner will be responsible for the
solution deployment / customization for
21
implementing end-to-end Data Center
Solution
Partner scope includes Supply and
Installation of Racks, Power cabling from
22
Source to Rack with proper Cable routing
through conduit, Earthing, MCB, PDU,
Sl
No
Cable Manager etc), as per the requirement
of SmartX and DSCL.
Partner scope includes Installation and

Commissioning of all applications and
hardware supplied by him. In addition,
Partner to assist other OEMs / partners in
creating VMs as per the desired hardware
23
sizing, Their IP, VLAN planning, and ensure
End to End data flow of the smart Elements
from Core / Aggregate Router to their
respective applications, and communication
with Internet.
The Partner should follow the SmartX EHS
guidelines and ensure safety guidelines to
24 Partner
be followed while installing the racks and
devices in data center
The Partner to ensure the desired Routing /
VLAN, VPN etc kind of configurations
including Firewall Policy, Access List, and
other configurations required for
communication of devices installed in Data
25 Center. Partner to ensure Data Integrity for Partner
the installed solutions in Data Center.
Partner to also design and commission LAN
switch and provide LAN infrastructure in
ICCC or Data Center, I&C of workstations,
Extending Internet to the workstations.
For the successful commissioning &
26 operation of the Data Center, partner to Partner
Page 30 of 46
Confidential
ensure that all the devices (weather

supplied by some other partner / OEM), are
configured with the planned IP addressing,
VLANs etc.
Partner to ensure the supply and availability
of required patch chords(optical / Electrical)
27 Partner
and Power cabling from Source till Rack for
connectivity of all Data Center components
Partner to provide sufficient Server / Storage
/ Backup for the supplied applications as per
partner/ OEM recommendations and
28 SmartX /DSCL requirements. The Data Partner
retention period must be atleast 1 year
online and 2 year offline (Backup in some
Tape library)
The partner shall ensure that the best
practices for software development and
29 customization are used during the software Partner
development/customization and
implementation exercise, if required
Sl
No
Installation and Commissioning of Server /
Storage-
a. Installation and Powering up the Server /
Storage (performing POST), observing for
30 any alarms Partner
b. Installation of any underlying software like
OS, DB, Antivirus etc
c. Installation of supplied Application in the
Server / Storage.
Partner to make VPNs, if required, over
Internet for remote Access of network. (This
has to be done only, when SmartX/DSCL
31 Partner
raises such requirement, and credentials to
be shared with key SPOC of SmartX only,
post approval from SmartX)
Partner need to tap power
32 Desired Power and Earthing Tapping point Partner and earthing from the
designated points
Installation AT (Acceptance Testing)
As per the latest revision of
33 parameter and format to be proposed and Partner
HLD
approved by SmartX /DSCL as applicable
AT planned to be agreed
Completion of Installation AT of installed
34 Partner between Partner & SmartX
equipment
deployment and
Page 31 of 46
Confidential
Partner to ensure the complete traffic flow of As per the latest revision of
all solutions (VMDs, CCTV, WiFi, Smart
LLD, OEMs / Other partner
Lighting) to their respective applications.
35 Partner to assist in configuring required Partner will assist in raising the
Policies, Routing etc in the data Center requirements for the traffic
components to achieve the same flow
Ensuring the feed of all installed applications
(including other OEMs applications) from
36 Partner
Data Center to ICCC (Considering data
center and ICCC are different locations)
Termination of ISP link for ILL and required
configurations for the peering with ISP,
37 Partner to perform all desired tests to check Partner
Speed , Latency, Traceroute (via Looking
glass) etc for the ILL bandwidth.
Offering and completing the Full Acceptance
Testing (FAT) of the entire Supplied
38 Partner
Applications and support in AT for the
applications supplied by other OEMs
Responsible and extend all support to
Project team to fully comply with PAT
39 (Partial Acceptance Testing) and FAT (Full Partner
Acceptance Testing) of the CCTV Network
to Operations as per the proposed solution
Tools / Tester required for conducting AT,
40 Partner
will be provided by Partner
Sl
No
Sharing Daily / Weekly /Monthly reports as
41 Partner
per the requirements of DSCL and SmartX
Conducting Training of 2 batches at
Dehradun Smart City office on system
42 description, configuration, operation and Partner
maintenance or as per the requirement of
SmartX or DSCL as applicable.
Propose any other scope of work which is
not included in this document but is required
43 for delivery of overall solution or to meet the Partner
RFP requirement on separate heading for
SmartX to review and agree
Preparation of As-Build document capturing
44 exact configurations and connectivity Partner
details, BoQ (with SFP details)
Site wise asset inventory at the time of
45 Partner
Handover
Self-certification i.e. Self AT document
46 Partner
before offering for AT
Page 32 of 46
Confidential
Partner to provide Self-Certification adhering

to the Security guidelines mentioned in the
RFP and industry standards. Partner to take
all required actions to fix the vulnerabilities
47 Partner
in the network to avoid any Security threat
like DDoS, Main in the middle attack,
Unauthorized access, Logging of events for
Security breach related events etc.
Propose any other scope of work which is
not included in this document but is required
48 for delivery of overall solution or to meet the Partner
RFP requirement on separate heading for
SmartX to review and agree
5 Operations and Maintenance
The scope of the work of operations and maintenance is primarily to run the handed over network
smoothly and meet the agreed SLA & KPI. The overall objective of this scope is to sustain it and
then undertake program to further improve the SLA gradually. The agreed SLA and KPI of the
network to be monitored on real time basis and take all preventive and corrective actions.
The key deliverables of Partners as part of Operations and Maintenance are as follows
• Monitor and manage all KPI (key performance Indicator) and SLA (service level agreement)
• Provide daily, weekly and monthly, Quarterly, etc KPI and SLA report as per SmartX or
DSCL as applicable requirement from time to time
• Fault and performance management of complete network through supplied EMS.
• Maintaining physical and logical inventory of all equipment and link including software
version • Maintain inventory of tools, desktops, server with hardware or software version
• Any new configurations and change in configurations of Data Center components as per the
network requirement raised by SmartX or DSCL.
• Carry out upgrades / updates as per the SmartX requirement or network performance
improvement
• FCAPS (fault, configuration, accounting, performance, security) of installed nodes and nodes
to be added future
• Maintain real time data base of all provisioned bandwidth customer id, link id with port and
path details
• Maintain updated physical and logical inventory of all equipment, links including software
version
• Maintain all contract details that SmartX sign with its customers for measuring performance
against these SLA
• Implementing Quality Management Procedures, implementing continuous improvement plan
• Feasibility of capacity either for new links or up-gradation of existing links as per SmartX
requirement within 24 hours
• To analysis the Data Center network as per the timelines agreed with SmartX and propose
changes in the network without any requirement of new hardware or software or new scope
to improve the performance of the network
• To conduct audit and find out that all IP used in Network or other Smart Element Network as
per the allocated IP network and in case of any deviation report to SmartX and coordinate
with the respective stake holders to change the IP plan
Page 33 of 46
Confidential
• To integrate and test new upcoming technologies/features the Partner shall support with all
required experts, tools, scripts, etc
• Monitor physical and logical access of network by authorized users
• Not allow access to the network to remote to login the system outside from India
The high level responsibility matrix for Partner to do operation, maintenance and life cycle
maintenance of the network are as follow
Sl
No
Monitor and manage all KPI (key performance Indicator) and
1 Partner
SLA (service level agreement)
Provide daily, weekly and monthly, Quarterly, etc KPI and
2 SLA report for the complete network as per SmartX Partner
requirement from time to time
3 Fault and performance management of network Partner
Maintaining physical and logical inventory of all equipment
4 Partner
and link including software version
Maintain inventory of tools, desktops, server with hardware or
5 Partner
software version
Monitoring and Maintaining the complete compute
Infrastructure, supplied Hardware and Software applications
6 and proactively suggest and do the changes if required as Partner
per the network requirement. Example- Expanding the VMs
RAM, Core etc if the usage goes above 70% of the CPU.
Addition of new nodes as and when added to the network

into the supplied EMS. In case of requirement of new
7 Partner
resources, the same will be incorporated with change
management process
Carry out all Data Center components upgrades / updates as

8 per the SmartX requirement or network performance Partner
improvement
FCAPS (fault, configuration, accounting, performance,
9 Partner
security) of installed nodes and nodes to be added future
Maintain real time data base of all provisioned bandwidth
10 Partner
customer id, link id with port and path details
Maintain updated physical and logical inventory of all
11 Partner
equipment, links working including software version
Page 34 of 46
Confidential
Maintain all contract details that SmartX sign with its

12 Partner
customers for measuring performance against these SLA
Implementing Quality Management Procedures,
13 Partner
implementing continuous improvement plan
Perform Security audits on its own and provide selfcertificate
14 on a frequency mutually agreed with SmartX / DSCL Partner
Operations team.
Feasibility of capacity either for new links or up-gradation of
existing links as per SmartX requirement within 24 hours
15 Partner
Sl
No
To analysis the Data Center network as per the timelines
agreed with SmartX and propose changes in the network
16 without any requirement of new hardware or software or new Partner
scope to improve the performance of the network
To conduct audit and find out that all IP used in entire

Network or other Smart Element Network as per the
17 allocated IP network and in case of any deviation report to Partner
SmartX and coordinate with the respective stake holders to
change the IP plan
Audit of the network to ensure that all IP used in network is
as per the IP/VLAN planned in LLD. Periodic update of
18 Partner
AsBuilt site documents as per actual connectivity and
configurations
Partner to ensure the latest (max one day or less older),
configuration backup of all Nodes and software applications
19 Partner
in some external drive or Tape Library, as per available
infrastructure
20 Performing periodic Switching test (for redundant nodes) Partner
Partner to monitor network utilization, on daily basis. Once it

21 reaches to certain threshold (70%), then upgradation has to Partner
be planned and intimated to SmartX
Providing Bandwidth Utilization graphs / reports etc as
22 Partner
required
All the records of IP / VLAN / Equipment wise configuration
23 files have to be maintained properly in a database, and Partner
needs to be updated, whenever any change is done
To integrate and test new upcoming technologies/features
24 the Partner shall support with all required experts, tools, Partner
scripts, etc
Monitor and ensure physical and logical access of network
25 Partner
by authorized users only
Page 35 of 46
Confidential
Not allow access to the network to remote login the system

26 Partner
outside from India
Propose any other scope of work which is not included in this
document but is required for delivery of overall solution or to
27 Partner
meet the RFP requirement on separate heading for SmartX
to review and agree
5.2 SLA Calculations and Penalties
This section is to be agreed by the selected Partner as the Service Levels and key performance
indicator for this engagement. The following section reflects the measurements to be used for
tracking, monitoring, and reporting of performance on a regular basis and imposition of penalties for
nonperformance as per the terms of this RFP.
The purpose of this section is to define the levels of service which shall be provided by the Partner
for the duration of the contract. Service Level Agreement (SLA) shall become the part of contract
between IT SmartX L/DSCL and the Partner. The Partner must comply with Service Levels
requirements to ensure adherence to project timelines, quality, and availability of services,
throughout the concession period.
For purposes of the SLA the definitions and terms as specified in the document along with the
following terms shall have the meanings set forth below:
a) “Total Time” - Total number of hours in the quarter being considered for evaluation of SLA
performance.
b) "Uptime” – Time period for which the specified services/ outcomes are available in the
quarter being considered for evaluation of SLA
c) “Downtime”- Time period for which the specified services / components /outcomes are not
available in the quarter being considered for evaluation of SLA
d) “Scheduled Maintenance Time”: Time period for which the specified services/ components
with specified technical and service standards are not available due to scheduled maintenance
activity. The Concessionaire is required to take at least 10 days prior approval from Client for any
such activity. This would be allowed in off peak hours- generally from midnight for a maximum of 4
hours and would be granted once in a quarter and exclude festive timings etc.
e) “Incident”: Any event / abnormalities in the service being rendered, that may lead to
disruption in normal operations and services to the end user.
f) “Response Time”: Time elapsed from the moment an incident is reported in the Helpdesk
over phone or by any applicable mode of communication, to the time when a resource is assigned
for the resolution of the same.
g) “Resolution Time”: Time elapsed from the moment incident is reported to Helpdesk either
in person or automatically through system, to the time by which the incident is resolved completely
and services as promised are restored.
Page 36 of 46
Confidential
5.2.1 SLA Calculations
These SLAs shall be used to evaluate the performance of the services post the Implementation
Phase and commencement of the O&M Phase. These SLAs and associated performance shall be
monitored on a monthly basis. Penalty levied for non-performance as per SLA shall be deducted. A
maximum level of performance penalty is established and described in this Section.
Sn Measuremen
o t Definition Target Penalty
No
It shall include all links individually >= 99.8% Deduction
Availability of
and shall be added for all applicable
1 all supplied
individual links that are unavailable
DC hardware
for a particular month.
>=99% to <99.8% 10%
>=98.5% to < 99% 15%
<98.5 % 20
Application Downtime shall be No

>= 99.7%
Availability of measured from the time the solution Deduction
supplied EMS becomes unavailable for Business
2 and other processing to the end user for
software performing all activities and tasks.
applications Each application shall be measured >=99.0% to <99.7
separately for penalty. 5%
%
>=98% to <99.0% 10%
>=96% to <98.0% 15%
<96 % 20
Method of Calculation for link uptime
Following formula will be used to calculate monthly uptime.

= (60*24*30) - (Sum of link down time in Min)
--------------------------------------------------------- x100
60*24*30
Note: the number of days in a month will be as per actuals.

6 AMC Contract
Page 37 of 46
Confidential
This section describes the operation and maintenance Support Service including all kinds of fault
handling that shall be provided by the Supplier. The Service concerns all Equipment (HW/SW)
delivered by the Supplier.
To secure robust Network, it is important for customers to have access to a trusted and reliable
partner that can assist by providing efficient support to meet their needs. As the competitive
landscape grows, securing overall network performance is essential to maintaining user satisfaction.
It is important to take steps to limit the risk of incidents taking place through fault prevention and
planning, and when incidents do occur, ensuring that downtime is as short as possible. Overall, a
reliable support agreement is an investment towards minimizing risks of unexpected network
failures.
This scope document outlines detailed scope of work & SLA with respect to AMC (Annual
Maintenance Contract) services. This AMC services are applicable to equipment supplied as per the
agreed object of services
6.1 Object of Service
Below is the list of items supplied by the Supplier under this project. This list forms the objective of
service under AMC scope of work.
S No Description Quantity Deployment Scope

Server / Storage
as per sizing of
1 Lot Data Center
applications of
Smart Elements
Server
2 Lot Data Center
Virtualization
3 Antivirus Lot Data Center
4 Workstation 2 Data Center
5 LAN Switch 1 Data Center
6 42U Rack 3 Data Center
7 Syslog server 1 Data Center
Note – The above BOQ along with the Optional items mentioned below are subject to change as per
the network or solution or SmartX requirement. SmartX as its sole discretion can increase, decrease
or remove any line items
Optional Items:
Page 38 of 46
Confidential
Deployment
S No Description Quantity
Scope
1 Firewall 1+1 Data Center
Element
2 Management 1 Data Center
System
Backup Software+
3 1 Data Center
Tape Library
4 NTP Server 1 Data Center
6.2 AMC / Support for Services scope
6.2.1 AMC Support desk
The Supplier would provide AMC Support Desk service to enable L1 and L2 teams to lodge
tickets/support request for the equipment supplied by the Supplier as per Objective of service list.
This Desk in turn would lodge ticket to respective support partner. Desk shall be available 24 x 7 to
respond to any queries/customer issues.
The Supplier shall answer to any reasonable query from the Purchaser on Normal Working Hours in
the Workdays Monday to Saturday. The help desk shall make all its effort to help the SmartX to
solve any such query by providing the necessary information from the correct resources. These
queries shall relate to the support on supplied hardware and software.
6.3 Trouble Ticketing
The Trouble ticketing application can be telephone/SMS/Email/internet based.
Trouble reports related to any fault will normally be sent to the Supplier after the fault is detected
and problem solving has started as Supplier’s helpdesk will be contacted directly first to avoid
unnecessary delays in problem solving phase.
The trouble tickets shall be answered by a written response (in case of critical failures, first plan of
action can be provided over call followed by mail). This shall either be an answer containing
information about the final solution, or, if the final solution is not known yet, a preliminary answer to
the trouble report and a description of the preliminary solution (the remedy).
Accordingly, the trouble ticket handling times shall be:
Page 39 of 46
Confidential
Severity level Remedy Preliminary trouble Final solution Final trouble report answer
report answer
Critical (Class A) Three (3) hours In advance to Twelve (12) In advance to

implementation of the hours implementation of the final
remedy solution
Major (Class B) Twenty Four In advance to Four (4) In advance to

(24) hours implementation of the calendar days implementation of the final
remedy solution
Minor (Class C) Fifteen (7) In advance to Thirty (30) In advance to

calendar Days implementation of the calendar days implementation of the final
remedy solution
For severity level A, the following requirements shall apply:
All Defects shall be corrected within three (3) hours of occurrence. For the purposes of this clause
“correction of the fault” shall mean a workaround solution made available.
The measured hours start from the time of occurrence of the fault. The final approved provisional
solution shall be available within twelve (12) Hours. Solutions including patch development shall be
provided within six calendar days.
For severity level B, the following requirements shall apply:
• All defects shall be corrected within twenty-four (24) hours after occurrence. For the
purposes of this clause “correction of the fault” shall mean a workaround solution made
available.
• The measured hours start from the time of occurrence of the fault
• The final approved solution shall be available within four (4) calendar Days measured from
the occurrence of the fault.
For severity level C, the following requirements shall apply:
• All Defects shall be corrected within fifteen days (15) calendar Days.
• The final approved solution shall be available within thirty (30) calendar Days
Note:
"Remedy" means a Workaround solution. The overall target is to restore the basic functionalities of
the affected system in order to minimize the observable impact on the end user.
When achieving the Remedy for the emergency situation, the vendor is not necessarily proposing to
implement a permanent fix, but is providing a workaround solution to ease the situation to an
acceptable level.
A permanent solution for the root cause will be delivered in accordance to the time schedule
already provided for Critical, Major and Minor Faults.
Page 40 of 46
Confidential
In case the Remedy is not acceptable to restore the services, the vendor will continue the work of
improving the Remedy until the time of providing the Final solution.
6.3.1 Telephone availability and Call Back time
Severity Telephone availability CSR Call-back Time
Critical (A) 7 x 24 10-15 minutes
Major (B) 7 x 24 1 hour
Minor (C) Normal Working Hours Next working day
6.3.2 Severity Levels
Severity Used for

Emergency Situations or Situations that may result in emergencies such as
- Any Failure, leading to affect service / traffic– the Data Center components supplied by partner
are down causing traffic disruption.
- Any fault affecting quality of service/availability of service of the links.
- Failure of Non-Redundant cards/ Links in the supplied equipments
- A reduction in capacity or traffic handling capability such that expected loads cannot be
handled.
- Loss of management of nodes in EMS causing loss of remote control of nodes
Critical - Corruption of files / Database of supplied EMS/other applications
- complete loss of I/O, OSS or communication for business-critical systems - Loss of access to
software applications like EMS/NMS - System hangs of software applications.
- Loss of Telnet to Data Center hardware / software components.
- Critical Alarm, as defined in the EMS of OEM.
- Upgradations failure / rollback requirements.
- Restoration of Database / configuration files.
Page 41 of 46
Confidential
Situations that may result in emergencies. Major problems or disturbances that requires immediate
action such as:
Systematic Faults (see above),
- Any fault affecting quality of service /availability of less than 2% of the links/subscribers
- important functionality is partially not available,
- failures of all important maintenance alarms
- reduction in any capacity/traffic measurement function.
Major - Sudden degradation of cluster or area or any network layer performance and quality -
disturbances affecting a specific area of functionality, but not the whole system.
- Serious disturbance which impacts end-user services such as:
- restarts,
- degraded performance or incorrect behavior with minor impact to the system,
- limited O&M functionality
- Major Alarm, as defined in the EMS of OEM.
General consultation and minor problems that have a minor effect on the functionality of the
product such as:
Examples:
- Faults that do not disturb traffic or causes any loss of service,
- incorrect System printouts,
Minor - documentation faults,
- minor design imperfections, - operational questions.
- Minor Alarm, as defined in the EMS of OEM.
6.3.3 RCA for Critical outages
To prevent serious situations occurring, it is vital to have information about events that can lead to
these situations i.e., Root Cause analysis document. This kind of information shall be published via
Email/web in Service Bulletins by Supplier within 24 hours of an Emergency situation occurring,
regardless of where in the world it has happened.
6.4 Software Maintenance support
The Supplier will collect a number of Software corrections and provide an Update of the delivered
Software Release. Based on the fault report forms received the Supplier shall prepare corrections to
rectify these faults. Technical notes describing the faults found, the corrective actions to repair the
faults shall be provided to the Purchaser.
The content of the next Software Update shall be provided to the Purchaser with intervals
depending on Software maturity. The Supplier will collect a number of Software corrections and
provide an Update of the delivered Software.
Page 42 of 46
Confidential
The Software Update will include corrections of faults and improvements of the existing Software. If
Hardware modifications are required, the Supplier is obliged to inform the Purchaser at least six (6)
Months before upgrading starts.
The Supplier undertakes to keep an updated version of the Software and Documentation. New
Software Update includes production, testing, and delivery of one Software package containing the
new Software Update including all descriptions, impact and installation instructions. If Purchaser
requires additional verification testing, this may take place at the Supplier's test bed.
The delivery of the Software Update shall take place only if Purchaser decides to implement the
new Software.
6.4.1 Software Updates / Patch Fixing
• The Supplier will secure that Purchaser at all times have the latest SW release in its network,
and provide SW support up to two releases back compared to the current available version
• The cost for any new Software Release, Software support, installation, and Updates, shall be
included in the compensation for Equipment.
• Information about the content and provision date of new Software Releases shall be
published at least one Year before the delivery of the new Software Release. The detailed
contents of the different Software Releases shall be made available to the Purchaser as
soon as the documents are ready, but not later than three (3) Months before the new
Software Release is ready for Implementation.
• Software Releases shall mainly include new and/or improved Functionality and Features of
the existing Software. New Software Releases will also act as a platform for future
Functionality and Features.
• As a prerequisite for major SW release upgrade the Supplier is obliged to provide the
Network impact report, impact on node HW and capacity, result from the test-bed and First
Office Application report well in advance (at least 6 months) of implementation.
• If Hardware modifications are required, the Supplier is obliged to give this information with
necessary HW dimensioning to Purchaser in sufficient time, however, no later than six (6)
Months before the planned Implementation. This shall also include information about the
Functionality in adjacent Network Elements necessary for the new Feature to function
properly, even if this Network Element is from a third-party supplier.
• A general requirement is that the actual Software Release shall be backward compatible to
all Network Elements and the interfaces included.
• The Supplier undertakes to keep an updated version of the Software and Documentation at
the Supplier's Service Center. New Software Releases will be made available in periods of
six (6) to twenty-four (24) Months depending on needs for new Features, as well as the
maturity of the Software.
• New Software Release includes production, testing, and delivery of one Software package of
the new Software Release, as well as production and delivery of one updated
Documentation set.
• The Supplier shall without any extra cost for the Purchaser perform Software Implementation
into the first Network Element of each type. At the Purchaser's request, the Supplier shall
carry out the Implementation of the Software into the remaining Network Elements under
terms of operation and maintenance assistance Service.
• The Supplier shall perform a Software audit on all Software Releases. The testing shall take
place at an agreed location.
Page 43 of 46
Confidential
• Testing and Acceptance of Software audits is included in the Software support Service,
• The delivered Software Release Updates shall be tested, and an Acceptance procedure
carried out by the Purchaser within three (3) Months period after the delivery. After this
period both Parties will sign either an Acceptance Certificate or a time schedule for Software
Update corrections shall mutually be agreed upon.
• The Supplier shall support the Software Release until the Purchaser terminates the support
agreement
• In case of Software application failure / corruption during normal operations or during
upgrades or patch fixing, then supplier has to install the new instance and restore the
database (with the latest available backup)
6.5 Hardware Maintenance Support
Any faults reported in the Network Elements will be attended by the Supplier as per below SLA table. Supplier
AMC team will act on fault post escalation by Supplier O&M team.
Network Element Support Program Repair & Return
Server /Storage Advance Same Day

Replacement
Router / Switches Advance Same Day

Replacement
Firewall Advance Same Day

Replacement
• Field maintenance and faulty replacement will be done by the Supplier O&M team, on site.
• Supplier AMC team will act on fault post escalation by Supplier O&M team,
• Repair and return SLA would be applicable once the faulty hardware has been made
available for repair by Supplier O&M Team.
• Advance replacement SLA would be applicable post fault identification by respective support
partner.
• Repair and return tickets will be logged on 8x5 basis, except for Critical issues.
Page 44 of 46
Confidential
7 Acronym
Acronym Full form
IP Internet Protocol
VLAN Virtual Local Area Network
VPN Virtual Private Network
BoQ Bill of Quantity
MTBF Mean Time Between Failures
MTTR Mean time to repair
USP Unique selling proposition
CCC Command and Control Center
RFP Request for proposal
DSCL Dehradun Smart City Limited
ITL Indus Towers Limited
VMD Variable Messaging display
DBB Digital Billboard
CCTV Closed-circuit television
WiFi Wireless Fidelity
EMS Element Management System
NMS Network Management System
KM Kilometer
STM Synchronous Transport Module
SLA Service Level Agreement
QOS Quality of Service
CIR Committed information rate
GPP Generation Partnership Project
Fault, configuration, accounting, performance,
FCAPS security
MCB Miniature Circuit Breaker
DCN dynamic circuit network
OFC Optical Fiber Cable
BOM Bill of Material
HLD High Level Diagram
LLD Low Level Diagram
ABD As Build diagram
SLD Site Level Diagram
NOC Network Operation Center
DC Data Center
FAT Full Acceptance Testing
OCI Open case inspection
GRN Goods Received Note
VMS Video Management System
PAT Partial Acceptance Test
DDP Delivered Duty Paid
Page 45 of 46
Confidential
Acronym Full form

FIR First Information Report
VM Virtual Machine
AT Acceptance Testing
KPI Key Performance Indicator
AMC Annual Maintenance contract
OSS Operations Support Systems
RCA Root Cause Analysis
-----------------------------------End of Document----------------------------
Page 46 of 46
Confidential

SOW For System Integrator DSCL v1.1

Uploaded by

Copyright:

Available Formats

SOW For System Integrator DSCL v1.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SOW For System Integrator DSCL v1.1

Uploaded by

Copyright:

Available Formats

Scope of work of Dehradun Smart City Project-System Integrator

Scope of work for Dehradun Smart City Project – System Integrator

Version 1.0 Rev 01

Technology Doc. No: 006/2021

Release Date: 25th February 2021

Sr. Release Effective

5.2.1 SLA Calculations..................................................................................................38

• Planning and Design of the Network

1.1 Technical submission

1. Requirement of SmartX – Partner understanding of customer requirement as mentioned

2.1 High Level BoQ

S No Description Quantity Deployment Scope

2.2 Technical Specification

Storage management software shall provide real time monitoring and

Shall support Industry standard virtualization hypervisor like Hyper-V,

Sno Compliance Partner Remarks (Actual values)

The solution should provide endpoint security solutions

Sno Compliance Partner Remarks (Actual values)

2.2.5 LAN Switch

Sno Compliance Partner Remarks (Actual values)

12 ports minimum -1G Ethernet ports 2 numbers of

Sno Compliance Partner Remarks (Actual values)

support channels - 3 pairs. It should have both options

2 Front and Back doors should be perforated

Tentative Rack Layout and Power requirement-

Note: Input power supply per rack will be 5-6 KW.

2.2.7 Syslog server

Sno Compliance Partner Remarks (Actual values)

information specific to the event.

2.2.8 Element Management System

Sno Compliance Partner Remarks (Actual values)

compliance and content validations to improve

Sno Compliance Partner Remarks (Actual values)

• The solution must support Templates for report

Sno Compliance Partner Remarks (Actual values)

Server Performance Monitoring System

Note: Tentative number of Elements to be managed is as follows-

1. Routers-5 (3 Aggregate, 2 Internet Router)

Sno Compliance OEM Remarks (Actual values)

VPN Module integrated with the firewall, IP Sec,

2.2.10 Backup Software

Restoration of the whole system or any individually replaceable

2.2.11 NTP Server

Sno Compliance Partner Remarks (Actual values)

Keeps the network synchronized to a Reference

3 Planning and Designing the Network

3.1 Data Center Requirement

3.1.1 Traffic Flow (Tentative)

3.1.2 Planning and Design Scope Requirement

3.1.3 Technical Information Criterion

Sno Parameter Response

3.2 Responsibility Matrix

Providing planning and dimensioning

Compliance to DSCL RFP or technical

elements as per the network

Partner to plan for the BoQ of all

To provide all necessary document if

Responsible for Planning and

entire designed Data Center Network