CORRIGENDUM NO. 3 to RFP Notice No. 10 of 2013 - Gujarat State ...
CORRIGENDUM NO. 3 to RFP Notice No. 10 of 2013 - Gujarat State ...
CORRIGENDUM NO. 3 to RFP Notice No. 10 of 2013 - Gujarat State ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
September 3, <strong>2013</strong><br />
Subject : Corrigendum <strong>No</strong>. 3 in the <strong>RFP</strong> <strong><strong>No</strong>tice</strong> <strong>No</strong>. <strong>10</strong> <strong>of</strong> <strong>2013</strong><br />
Reference: <strong>RFP</strong> <strong><strong>No</strong>tice</strong> <strong>No</strong>. <strong>10</strong> <strong>of</strong> <strong>2013</strong><br />
<strong>CORRIGENDUM</strong> <strong>NO</strong>. 3 <strong>to</strong> <strong>RFP</strong> <strong><strong>No</strong>tice</strong> <strong>No</strong>. <strong>10</strong> <strong>of</strong> <strong>2013</strong> by GSDMA<br />
Following is the corrigendum <strong>to</strong> presently available <strong>RFP</strong> for “Selection <strong>of</strong> Build, Own, Operate, and Transfer (BOOT) Opera<strong>to</strong>r <strong>to</strong> Set-up and<br />
manage Information & Communication Technology System (ICTS) Infrastructure for <strong>Gujarat</strong> <strong>State</strong> Disaster Response”.<br />
Sr. # Page # Clause #<br />
1<br />
2<br />
3<br />
4<br />
5<br />
6<br />
7<br />
Description <strong>of</strong><br />
Terms / Headings<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
Existing Clause Queries Reply<br />
How is the Integration with other services<br />
done and will it be only on state<br />
MPLS/SWAN<br />
Type <strong>of</strong> Phones and Specifications for<br />
Agents<br />
More details on Radio Gateway<br />
Integration and Interface is sought<br />
Number <strong>of</strong> Users and Locations with<br />
Location wise User count<br />
Requirement <strong>of</strong> Voice Gateways at each<br />
location, with Gateway specifications<br />
Type <strong>of</strong> Phones <strong>to</strong> be provided at each<br />
locations with Specifications<br />
Paging Requirements, With Zones and<br />
Integration with AWS<br />
Integration will be via GSWAN<br />
Left <strong>to</strong> the choice <strong>of</strong> opera<strong>to</strong>r.<br />
Phones should be user friendly<br />
and reliable in operations.<br />
As per <strong>RFP</strong><br />
Information as far as possible is<br />
included in the <strong>RFP</strong>.<br />
Gateway design is left <strong>to</strong> the<br />
opera<strong>to</strong>r and it expected <strong>to</strong><br />
meet specifications. VoIP<br />
gateway for VSAT and MPLS<br />
VPN is <strong>to</strong> be provided by the<br />
opera<strong>to</strong>r. It should facilitate<br />
voice communication between<br />
various users on the network.<br />
Left <strong>to</strong> the choice <strong>of</strong> opera<strong>to</strong>r.<br />
Phones should be user friendly<br />
and reliable in operations.<br />
There is no paging requirement<br />
at the moment.
8<br />
9<br />
<strong>10</strong><br />
11<br />
12<br />
<strong>10</strong>5<br />
2/246<br />
and<br />
5/249<br />
Videoconferencin<br />
g Room / Display<br />
facilities<br />
a) Systems and<br />
sub systems <strong>to</strong> be<br />
tested<br />
b)Equipment<br />
installed at ERC,<br />
DEOC and TEOC in<br />
standalone modes<br />
and in network<br />
mode<br />
<strong>10</strong>7 1.3.5 Call Center NA<br />
Page 150<br />
-<br />
<strong>No</strong>minal<br />
specifications for<br />
Multipoint Control<br />
Unit<br />
<strong>No</strong>minal<br />
specifications for<br />
Multipoint Control<br />
Unit<br />
Large VC camera <strong>to</strong> cover every<br />
person in the room with<br />
capability <strong>to</strong> track speaker<br />
au<strong>to</strong>matically<br />
a) Systems and sub systems <strong>to</strong><br />
be tested b)Equipment<br />
installed at ERC, DEOC and TEOC<br />
in standalone modes and in<br />
network mode<br />
Conferencing capability<br />
addition<br />
Please delete "capability <strong>to</strong> track speaker<br />
au<strong>to</strong>matically" (i) the au<strong>to</strong> tracking works<br />
erroneously in such a briefing room with<br />
multiple participants. (ii) The ideal range<br />
<strong>of</strong> the au<strong>to</strong> tracking is normally 23 feet,<br />
thus a large size room with 24 participants<br />
having 12 seats on one side <strong>of</strong> the table<br />
this will not work well. (iii) Au<strong>to</strong> tracking is<br />
a proprietary feature <strong>of</strong> only one OEM.<br />
This limits the competition.<br />
Pl clarify the Standalone and network<br />
mode….….. Does Standalone mode refer<br />
<strong>to</strong> survivability <strong>of</strong> the DEOC and TEOC<br />
location?<br />
Tender is looking for IVR system. Request<br />
you please share the IVR call flow & what<br />
all services are <strong>to</strong> be extended on IVR. Is it<br />
also expected o integrate the IVR / ACD<br />
system with the backend Portal / DB.<br />
Would request the resolution at which<br />
such calls are <strong>to</strong> be made as <strong>10</strong>0<strong>No</strong>s. 720p<br />
resolution calls would not be the same as<br />
<strong>10</strong>0<strong>No</strong>s. CIF calls, would also request for<br />
dynamic allocation <strong>of</strong> resources such that<br />
<strong>10</strong>0<strong>No</strong>. 720p calls or 400<strong>No</strong>s. VoIP calls<br />
could be specified instead <strong>of</strong> <strong>10</strong>0<br />
video/voice which is ambiguous.<br />
Request the clause for Scalability <strong>to</strong> higher<br />
capacity without change in main hardware<br />
, by either cards or licenses as and when<br />
required<br />
Requirements are worked out<br />
on the basis <strong>of</strong> needs <strong>of</strong> the<br />
organization and not on<br />
manufacturer.<br />
<strong>No</strong> change<br />
Standalone mode will check<br />
connectivity <strong>of</strong> various<br />
equipment within a location,<br />
where as network mode applies<br />
<strong>to</strong> interconnectivity <strong>of</strong> all nodes<br />
on statewide networks. This<br />
doesn't refer <strong>to</strong> survivability <strong>of</strong><br />
DEOC , and TEOC<br />
IVR is meant for dissemination<br />
<strong>of</strong> updates on disaster<br />
incidences <strong>to</strong> public / NGOs etc.<br />
The call centre agents will<br />
record updates on the<br />
incidences that can be accessed<br />
by people dialing in on the IVR.<br />
<strong>No</strong> change in specifications<br />
Please note that these calls are<br />
<strong>to</strong> be made <strong>to</strong> discuss regarding<br />
disaster situations and<br />
temporary drop in quality <strong>to</strong><br />
meet operational requirements<br />
will be <strong>to</strong>lerated. Connectivity<br />
requirements are the priority.<br />
<strong>No</strong> Change. Opera<strong>to</strong>r is<br />
expected <strong>to</strong> design the systems<br />
<strong>to</strong> meet operational<br />
requirements
13<br />
14<br />
15 118-<br />
119<br />
16 118-<br />
119<br />
17 118-<br />
119<br />
-<br />
-<br />
1.5<br />
1.11<br />
1.16<br />
<strong>No</strong>minal<br />
specifications for<br />
Multipoint Control<br />
Unit<br />
<strong>No</strong>minal<br />
specifications for<br />
Multipoint Control<br />
Unit<br />
Information<br />
Management<br />
Portal System<br />
Information<br />
Management<br />
Portal System<br />
Information<br />
Management<br />
Portal System<br />
addition<br />
addition<br />
The system should provide<br />
mechanisms for provisioning<br />
user identities and relationships<br />
among multiple direc<strong>to</strong>ries<br />
The systems should Support<br />
role-based access <strong>to</strong> system<br />
functions provided by the portal<br />
so that end-users are provided<br />
with the appropriate set <strong>of</strong><br />
application functions relevant <strong>to</strong><br />
their role within the state<br />
disaster management<br />
operations and their<br />
organizational affiliation.<br />
Provide the capability <strong>to</strong> Invite -<br />
Using information provided<br />
during the location <strong>of</strong> those<br />
individuals or roles, invite them<br />
<strong>to</strong> collaborate and <strong>to</strong> share<br />
valuable information.<br />
Request for redundancy clause <strong>to</strong> allow<br />
functioning in case <strong>of</strong> failure <strong>of</strong> single<br />
component<br />
Request more details for allowing better<br />
suitability <strong>of</strong> solution (as per tech specs)<br />
Need <strong>to</strong> know if this is LDAP or Active<br />
direc<strong>to</strong>ry?<br />
Need <strong>to</strong> clearly define and understand the<br />
Roles and Functions do they have the<br />
clarity on this? Can they provide the Roles<br />
and Functions?<br />
Need <strong>to</strong> understand what they mean by<br />
“capability <strong>to</strong> Invite”?<br />
Design for redundancy is left <strong>to</strong><br />
the opera<strong>to</strong>r as system<br />
performance is <strong>to</strong> meet SLA<br />
requirements<br />
Design for the system is left <strong>to</strong><br />
the opera<strong>to</strong>r as system<br />
performance is <strong>to</strong> meet SLA<br />
requirements<br />
Active direc<strong>to</strong>ry<br />
Roles and functions will be<br />
defined by GSDMA<br />
Capability <strong>to</strong> invite means -<br />
sending a secured request for<br />
individual within or outside the<br />
system <strong>to</strong> edit/view the content<br />
/ conversation.
18 119-<br />
122<br />
1.2<br />
Incident<br />
Management<br />
System<br />
It should provide all necessary<br />
components for a<br />
comprehensive disaster &<br />
emergency management<br />
solution including:<br />
• Alert and warning <strong>No</strong>tification,<br />
• Crisis Information<br />
Management,<br />
• Calls and message Dispatch<br />
System,<br />
• GIS, Map Data, Collaboration<br />
Framework,<br />
• Unified Communication for<br />
Planning, Dynamic Incident &<br />
Asset Management and<br />
Recovery Services.<br />
The system should support<br />
shared information on:<br />
• How and where the disaster<br />
event has taken place or is<br />
taking place,<br />
• Relevant geospatial data using<br />
GIS layers <strong>to</strong> indicate location <strong>of</strong><br />
the event, with his<strong>to</strong>rical<br />
context (whether similar event<br />
has occurred in the past at the<br />
place or nearby areas)<br />
• People likely <strong>to</strong> be affected by<br />
the event and possible extent <strong>of</strong><br />
damage <strong>to</strong> houses etc.<br />
• Location <strong>of</strong> resources<br />
necessary <strong>to</strong> ensure effective<br />
response<br />
• Standard Operating<br />
Procedures (SOP) as per<br />
Government <strong>of</strong> Bihar’s Disaster<br />
Management Policy<br />
Advice from experts on similar<br />
incidences in the past<br />
The Details are required which are devices<br />
for alter are being used? Which devices<br />
are used for Warning<br />
What is the workflow <strong>of</strong> the devices<br />
communication, What are the SOP’s for<br />
the Crises management required?<br />
The Scope <strong>of</strong> and the workflow <strong>of</strong> the<br />
various subsystems should be defined,<br />
Some configuration and some<br />
development on the Existing product as<br />
the scope is not well defined here.<br />
Design <strong>of</strong> Alert and warning<br />
system is part <strong>of</strong> the opera<strong>to</strong>r’s<br />
responsibilities. <strong>RFP</strong> clearly<br />
indicates number <strong>of</strong> Alert and<br />
warning <strong>to</strong>wers <strong>to</strong> be installed.<br />
Any bidder with previous<br />
experience will understand <strong>RFP</strong><br />
requirements. Warning<br />
messages <strong>to</strong> disaster responders<br />
are <strong>to</strong> be delivered via SMS and<br />
voice calls. Similarly warning<br />
messages will be disseminated<br />
via public broadcast systems<br />
such as Radio and TV.
19 119-<br />
122<br />
1.4<br />
Incident<br />
Management<br />
System<br />
The information should be<br />
accessible from fixed and mobile<br />
locations on EOCI<br />
The Details are required as what devices<br />
are required for Fixed and mobile<br />
locations is it Lap<strong>to</strong>p?<br />
How the workflow are expected<br />
What are the means <strong>of</strong> communications?<br />
Information should be available<br />
on desk <strong>to</strong>ps or lap<strong>to</strong>ps at Fixed<br />
locations as well as ERV. Exact<br />
requirements are indicated in<br />
the <strong>RFP</strong><br />
20 119-<br />
122<br />
21 119-<br />
122<br />
22 119-<br />
122<br />
23 119-<br />
122<br />
1.5<br />
1.6<br />
1.9<br />
1.<strong>10</strong><br />
Incident<br />
Management<br />
System<br />
Incident<br />
Management<br />
System<br />
Incident<br />
Management<br />
System<br />
Incident<br />
Management<br />
System<br />
The system should include<br />
universal communication<br />
interface based on common<br />
(e.g. VoIP ) switching for voice<br />
call connectivity across various<br />
technology based equipment’s<br />
such as VHF radio, VSAT, VoIP<br />
calls on MPLS-VPN etc.<br />
The system should interface<br />
with alert and warning facility <strong>to</strong><br />
issue SMS / Voice mail / E-mail<br />
based warning messages inside<br />
the EOCI as well as <strong>to</strong> outside<br />
agencies such as social media,<br />
broadcast media using CAP<br />
compliant messaging<br />
The system should have ability<br />
<strong>to</strong> handle all types <strong>of</strong> files<br />
(documents, presentations,<br />
spreadsheets, images,<br />
multimedia and others) either<br />
by uploading and s<strong>to</strong>ring; or by<br />
linking <strong>to</strong> them.<br />
It should be possible <strong>to</strong> index<br />
unstructured content, such as<br />
radio, telephony, images, video,<br />
documents, using relevant<br />
metadata, including geospatial<br />
attributes<br />
What are the specifications <strong>of</strong> these<br />
devices? How many VHF? VSATs what will<br />
be the workflow? How this<br />
communications is used in terms <strong>of</strong> EOC<br />
operation?<br />
What are the Alter warning system<br />
available, Describe them? What is the<br />
interface available?<br />
Is SDK / API available?<br />
We need <strong>to</strong> know exact no <strong>of</strong> interfaces so<br />
that the same can be accounted for while<br />
bidding<br />
Handling <strong>of</strong> files is just attaching the<br />
files??<br />
This needs description in detail.<br />
This needs description in detail. Please<br />
define which make model <strong>of</strong> the interfaces<br />
and how many <strong>of</strong> them and what is the<br />
existing infrastructure available?<br />
Specifications are on page<br />
number 259- Other information<br />
is not required <strong>to</strong> design the<br />
system.<br />
End <strong>to</strong> end system design from<br />
IMS <strong>to</strong> Alert system is the<br />
responsibility <strong>of</strong> the opera<strong>to</strong>r<br />
which also includes alert<br />
generation centre at SEOC<br />
These files are <strong>to</strong> help<br />
understanding <strong>of</strong> disaster<br />
situation; Work involves<br />
uploading, searching, opening<br />
and displaying as well as linking<br />
<strong>of</strong> information for decision<br />
support.<br />
The requirement is <strong>to</strong> s<strong>to</strong>re and<br />
facilitate quick access <strong>of</strong><br />
relevant information from<br />
different sources via associated<br />
keys. The design is left <strong>to</strong> the<br />
opera<strong>to</strong>r
24 119-<br />
122<br />
25 119-<br />
122<br />
26 119-<br />
122<br />
27 119-<br />
122<br />
1.11<br />
1.12<br />
1.14<br />
1.15<br />
Incident<br />
Management<br />
System<br />
Incident<br />
Management<br />
System<br />
Incident<br />
Management<br />
System<br />
Incident<br />
Management<br />
System<br />
The system should also support<br />
creation <strong>of</strong> links between<br />
different files, so as <strong>to</strong> link<br />
several files <strong>to</strong> a particular<br />
incident report<br />
It should provide search<br />
capability for searching data<br />
records within the system,<br />
including geospatial attributes<br />
The system should provide<br />
scalability features and support<br />
`load balancing, high availability<br />
& disaster recovery. It should<br />
allow up-<strong>to</strong> <strong>10</strong>0 concurrent<br />
users performing queries and 50<br />
concurrent updaters<br />
The system should facilitate:<br />
• Upload / download any type <strong>of</strong><br />
files<br />
• Access <strong>to</strong> end-user device with<br />
standard operating systems<br />
such as Windows XP, Vista,<br />
Windows 7 etc<br />
• Use <strong>of</strong> popular browser-based<br />
clients – Firefox, Internet<br />
Explorer, Mozilla, Google<br />
Chrome etc.<br />
The logical for the creation <strong>of</strong> the links<br />
should be defined. This is very High Level<br />
requirement and need detailed<br />
clarification.<br />
The details <strong>of</strong> the workflow need <strong>to</strong> be<br />
explained. Is it Geospatial Search or call<br />
record search, what department meant by<br />
it? What should be searched and which<br />
record is <strong>to</strong> be searched the detailed<br />
workflow is required.<br />
Load balancing could be done using the<br />
network hardware is this acceptable?<br />
What sizes <strong>of</strong> the files? For what purpose<br />
<strong>of</strong> upload and download <strong>of</strong> the files? Who<br />
will upload these files and what actions<br />
are required on theses uploaded files.<br />
Is it manda<strong>to</strong>ry <strong>to</strong> use browser? the<br />
uploaded and download can be achieved<br />
using better desk<strong>to</strong>p apps<br />
The requirement is facility <strong>to</strong><br />
access <strong>of</strong> relevant information<br />
from different sources via<br />
associated keys. The design is<br />
left <strong>to</strong> the opera<strong>to</strong>r<br />
Search for all types <strong>of</strong><br />
information should be possible<br />
via links or keywords. Geospatial<br />
attributes are <strong>to</strong> be considered<br />
only for the data including video<br />
that has geospatial information<br />
associated with it.<br />
Any solution which will meet the<br />
requirement is acceptable.<br />
Files can contain data, video as<br />
well as voice recording<br />
information. Files will uploaded<br />
by persons authorized <strong>to</strong> access<br />
the system. The purpose<br />
obviously is <strong>to</strong> ensure sharing <strong>of</strong><br />
disaster situational information<br />
across the network and disaster<br />
management responders
28 119-<br />
122<br />
29 119-<br />
122<br />
30 119-<br />
122<br />
31<br />
1.16<br />
1.21<br />
1.22<br />
Incident<br />
Management<br />
System<br />
Incident<br />
Management<br />
System<br />
Incident<br />
Management<br />
System<br />
118 Annexure III<br />
The system should have<br />
capabilities <strong>of</strong> creating the alert<br />
content for disseminating <strong>to</strong> end<br />
users. It should also generate<br />
CAP compliant warning<br />
messages for external<br />
broadcasting organizations like<br />
Radio, TV etc.<br />
Ability <strong>to</strong> integrate with modern<br />
as well as legacy systems,<br />
Provide ability <strong>to</strong> link <strong>to</strong> 3rd<br />
party databases and<br />
applications will be preferred.<br />
The system with ability <strong>to</strong> be<br />
receive, compile, s<strong>to</strong>re and<br />
analyses data on rainfall, flood,<br />
water level, wind speed and<br />
direction, earth shake,<br />
temperature, cyclone<br />
progression provided by various<br />
Government / <strong>No</strong>n-Government<br />
agencies will be preferred.<br />
The Details <strong>of</strong> the <strong>No</strong> <strong>of</strong> Equipment’s and<br />
The action on the alert should be defined.<br />
Please share detail about Legacy system<br />
and 3rd party database, what do you<br />
mean by it<br />
The feed and necessary inputs and the<br />
number <strong>of</strong> connections should be well<br />
defined.<br />
Our system can integrate Weather station,<br />
dopper radar, etc but will GSDMA given<br />
access and API <strong>to</strong> integrate them<br />
<strong>RFP</strong> defines the technical specifications for<br />
an Incident Management Portal system. Is<br />
this portal going <strong>to</strong> replace the GSDMA<br />
website or somehow connected <strong>to</strong> it?<br />
Please clarify so bidders can allocate<br />
necessary time/budget for such<br />
integration.<br />
<strong>No</strong> <strong>of</strong> alert and warning <strong>to</strong>wers<br />
is included in the <strong>RFP</strong> and is part<br />
<strong>of</strong> opera<strong>to</strong>r's responsibility.<br />
Number <strong>of</strong> <strong>of</strong>ficers who are <strong>to</strong><br />
be informed about the<br />
incidences will be in the range <strong>of</strong><br />
1,000. CAP compliant messages<br />
are <strong>to</strong> be issued <strong>to</strong> at least up <strong>to</strong><br />
<strong>10</strong> radio channels and <strong>10</strong> TV<br />
channels.<br />
Legacy systems are GIS based<br />
data base s based on ESRI and<br />
open standards. SDRN data base<br />
also need <strong>to</strong> be linked <strong>to</strong> IMS.<br />
All parameters <strong>of</strong> incidences<br />
that can lead <strong>to</strong> disasters are<br />
not available as on date.<br />
However opera<strong>to</strong>r should<br />
provide at least one input port<br />
for each parameter<br />
(approximately <strong>10</strong> ports will<br />
meet the requirement). Data<br />
will be sent <strong>to</strong> opera<strong>to</strong>r's system<br />
via matching interface.<br />
<strong>No</strong>.<br />
IMPs and GSDMA website will<br />
operate independently.
32<br />
33<br />
34<br />
35<br />
118 1.1<br />
<strong>10</strong>5<br />
145<br />
1.2.6 Brief<br />
description <strong>of</strong> the<br />
project<br />
Information<br />
Management<br />
Portal System<br />
(IMPS)<br />
SEOC connectivity<br />
and facilities<br />
Video Equipment<br />
/ Video<br />
conference<br />
endpoint<br />
Communication between first<br />
responders such as<br />
police, disaster rescue forces,<br />
fire brigades that use<br />
wireless communication<br />
systems mostly equipment<br />
operating in Very High<br />
Frequency (“VHF”) band and<br />
administra<strong>to</strong>rs on terrestrial or<br />
satellite based Very<br />
Small Aperture Terminals<br />
(“VSAT”), should be possible<br />
with Voice over Internet<br />
Pro<strong>to</strong>col (“VoIP”) based<br />
unified communication system.<br />
Optional Feature<br />
Video Conference Room<br />
HD <strong>10</strong>80p, 12x zoom or higher,<br />
UNIVERSAL INTERFACE SYSTEM (UIS)<br />
a) Will any other device other than<br />
Universal communication Interface be<br />
connected with the VSAT IDU (modem)<br />
over L AN (RJ 45) ports (i.e. IP interface)?<br />
Please confirm.<br />
b) Does UIS support SIP signaling for VoIP?<br />
[As UIS will convert wireless<br />
communication <strong>to</strong> Internet Pro<strong>to</strong>col (IP)<br />
format and VoIP Gateway will be installed<br />
at the SEOC, which means it supports SIP<br />
Signaling for VoIP] Please confirm?<br />
c) Will this box be connecting <strong>to</strong> VSAT<br />
Modem over LAN (RJ45) port for the<br />
communication between ERVs & SEOC on<br />
IP pro<strong>to</strong>col?<br />
d) Provide the specifications/capability<br />
details <strong>of</strong> this Universal Interface System.<br />
e) Schematic Diagram <strong>of</strong> Universal<br />
Interface system showing the traffic flow<br />
<strong>of</strong> VHF system and VSAT system.<br />
Features like collaboration, IM, Presence<br />
Awareness, Web<br />
Conference are mentioned as optional<br />
features for IMSP. We understand these<br />
futures can be complied by either IMS or<br />
IMPS and will be used only by Dept users /<br />
stakeholders and not by other users?<br />
Kindly confirm.<br />
Au<strong>to</strong>matic camera tracking is biased <strong>to</strong><br />
single OEM. This can be done manually<br />
also. So request you <strong>to</strong> pl remove this<br />
point.<br />
12x camera will be biased <strong>to</strong> single OEM,<br />
please change it <strong>to</strong> <strong>10</strong>x camera<br />
a) One more LAN port for<br />
videoconferencing, voice<br />
communication, data<br />
communication etc. is<br />
necessary,<br />
b) Yes<br />
c) Yes<br />
d) Please refer <strong>to</strong> page 259<br />
e) UIS is a standard solution<br />
available from many OEMs,<br />
hence this information is not<br />
included in the <strong>RFP</strong><br />
IMS will be used by department<br />
users where as limited portion<br />
<strong>of</strong> IMPS can be accessed by<br />
NGOs, public etc.<br />
<strong>No</strong> change. This facility is<br />
required <strong>to</strong> ensure proper<br />
visibility <strong>of</strong> speaker when a large<br />
number <strong>of</strong> persons participate in<br />
VC.<br />
<strong>10</strong> x camera will be accepted.
36<br />
151<br />
<strong>No</strong>minal<br />
specifications for<br />
Multipoint Control<br />
Unit<br />
Interface and data rate<br />
capability<br />
Kindly change <strong>to</strong> : 64kbps <strong>to</strong> 4mbps<br />
conference data rates<br />
4.0 Mbps rate will be accepted.<br />
37<br />
38<br />
39<br />
97<br />
Connectivity<br />
Matrix<br />
- Establish LAN within SEOC<br />
- Establish LAN at ERC and<br />
disaster location using wired or<br />
wireless medium<br />
- Establish LAN using wireless<br />
medium at ERVs<br />
Kindly clarify for designing <strong>of</strong> LAN Network<br />
provision for how many LAN I/O points is<br />
<strong>to</strong> be provided at-<br />
- SEOC<br />
- DEOC<br />
- ERC<br />
- ERV<br />
Provision <strong>of</strong> Broadband Internet at ESF<br />
(Emergency Support Functions)<br />
1) Internet Bandwidth <strong>to</strong> be provided at<br />
ESF departments / organizations at <strong>State</strong><br />
Headquarters (14) has not been provided.<br />
Kindly provide the same.<br />
2) Internet Bandwidth <strong>to</strong> be provided at<br />
ESF departments / organizations at District<br />
Headquarters (14) - provisioned how<br />
much not known.<br />
PSTN will be backup network for<br />
1.<strong>State</strong> EOC (SEOC),<br />
2.DEOCs<br />
3 ERCs,<br />
4 ESFs at <strong>State</strong> Head quarters,<br />
5.ESFs at District Head quarters<br />
6.TEOCs<br />
Whether this telephone network is <strong>to</strong> be<br />
provisioned by the opera<strong>to</strong>r or would be<br />
provided by <strong>Gujarat</strong> <strong>State</strong> Disaster<br />
Management Authority? If opera<strong>to</strong>r’s<br />
responsibility details w.r.t no. <strong>of</strong> PSTN<br />
lines/ <strong>No</strong>. <strong>of</strong> connections desired sought<br />
for estimation <strong>of</strong> exchange equipments..<br />
Part <strong>of</strong> the design and solution<br />
development y the opera<strong>to</strong>r.<br />
Requirements for Government<br />
<strong>of</strong>ficers / state functionaries /<br />
press briefing rooms etc are<br />
included in <strong>RFP</strong>.<br />
1) and 2) Opera<strong>to</strong>r is not<br />
expected <strong>to</strong> provide any<br />
network resources at ESF<br />
locations either at state <strong>of</strong><br />
district levels. Internet<br />
broadband will be provided by<br />
state or GSDMA at these<br />
locations<br />
Opera<strong>to</strong>r is responsible <strong>to</strong><br />
provide 2XE1 (60) ISDN lines and<br />
5 GSM phones at SEOC. <strong>No</strong><br />
other PSTN connectivity is<br />
expected from the Opera<strong>to</strong>r
40<br />
41<br />
42<br />
116<br />
82<br />
Satellite Phone mentioned as backup <strong>to</strong><br />
Portable VSAT, ERV and with Alert and<br />
Warning <strong>to</strong>wer- <strong>No</strong>te # mentions required<br />
number <strong>of</strong> satellite phones will be<br />
procured.<br />
Whether Satellite phone is <strong>to</strong> be<br />
provisioned by the opera<strong>to</strong>r or would be<br />
provided by <strong>Gujarat</strong> <strong>State</strong> Disaster<br />
Management Authority? If opera<strong>to</strong>r’s<br />
responsibility Kindly provide the details<br />
w.r.t Total <strong>No</strong>. <strong>of</strong> Satellite phones desired.<br />
HF based walkie talkie integration is<br />
planned at SEOCs and ERVs. How many<br />
number <strong>of</strong> Walkie talkie sets are required?<br />
Kindly elaborate the desired VHF network;<br />
the information required is not sufficient?<br />
Multimedia management system for<br />
handling live video feeds coming from<br />
multiple sources like video-conferencing<br />
devices, surveillance and remote cameras<br />
or footage captured through video<br />
cameras on ERV transmitted via VSAT<br />
links.<br />
Kindly elaborate the desired surveillance<br />
system. Does tenderer expect CCTV<br />
cameras, if yes then at how many<br />
locations?<br />
Alert and warning <strong>to</strong>wers can<br />
use satellite data modems<br />
(Imarsat M2M) systems as backup<br />
for link between the <strong>to</strong>wer<br />
and SEOC. <strong>No</strong> satellite phone is<br />
proposed for warning system.<br />
Satellite phones will be<br />
procured by GSDMA as they<br />
need special permission from<br />
government <strong>of</strong> India.<br />
HF based transceiver (1) is<br />
required at SEOC and each ERV<br />
(not a walky-talky). Each ERV<br />
should have one base station<br />
and <strong>10</strong> handsets (walkie-talkies).<br />
Detailed specs are available at<br />
page 133<br />
CCTV cameras at SEOC are<br />
provided by GSDMA.<br />
Requirement <strong>of</strong> cameras at ERV<br />
are included in the<br />
specifications. System should be<br />
able <strong>to</strong> handle inputs coming<br />
from these cameras as well as<br />
any other video system installed<br />
by other government agencies<br />
e.g. police, municipal<br />
corporation etc.
43<br />
44<br />
Access Control<br />
Kindly confirm whether LCD and projec<strong>to</strong>r<br />
screen <strong>to</strong> be provided and there numbers<br />
for each <strong>of</strong> the following:<br />
(i) SEOC Command / Operation room -2<br />
LCD in no.- size 80 / <strong>10</strong>0”<br />
(ii) Videoconference Room – 2 LCD in no.-<br />
(at least <strong>10</strong>0 inches) +1 projec<strong>to</strong>r roll<br />
down Screen(with Ceiling mounted<br />
projec<strong>to</strong>r )<br />
(iii) Press Conference Room (PCR) – 1 LCD<br />
in no.<br />
(iv) Rooms occupied by senior <strong>of</strong>ficers,<br />
Incident commander etc. -6 LCD Screen<br />
size in the range <strong>of</strong> 40 <strong>to</strong> 50 Inches<br />
Access Control - The controller must be an<br />
intelligent controller. It must use Ethernet<br />
and in-built power supply with all internal<br />
wirings.<br />
The controller shall be capable <strong>of</strong> having<br />
1500 card holder database on-board and a<br />
buffer memory capacity <strong>of</strong> <strong>10</strong>0,000 events<br />
/ alarms with date & time.<br />
What is events/alarm as mentioned in the<br />
<strong>RFP</strong>? Elaborate<br />
As per revised <strong>RFP</strong><br />
Events / alarms are related <strong>to</strong><br />
access control system. These<br />
will include forced entries /<br />
impersonation etc.<br />
45<br />
Servers<br />
(a) Application Server<br />
(b) Data base server<br />
(c) Proxy Services<br />
(d) Anti-virus<br />
Kindly give:<br />
1) Specifications <strong>of</strong> servers<br />
2) Type <strong>of</strong> Database<br />
This left <strong>to</strong> design <strong>of</strong> the<br />
opera<strong>to</strong>r. System performance<br />
guidelines are included in the<br />
<strong>RFP</strong><br />
46<br />
Direc<strong>to</strong>ry Services<br />
For how many users authentication &<br />
authorization is <strong>to</strong> be provided?<br />
Information included in the <strong>RFP</strong>.
47<br />
48<br />
49<br />
Extension <strong>of</strong> date<br />
<strong>of</strong> submission <strong>of</strong><br />
tender<br />
How many Anti-virus licenses required?<br />
It is requested <strong>to</strong> extend the date <strong>of</strong><br />
submission <strong>of</strong> the subject <strong>RFP</strong> by 1<br />
months, this will help us understand the<br />
requirements and further interact with<br />
OEMs, vendors and service providers in a<br />
more comprehensive manner.<br />
<strong>RFP</strong> has asked Network Moni<strong>to</strong>ring<br />
System (NMS) but there is no technical<br />
specifications mentioned in <strong>RFP</strong>. Can you<br />
please specify the technical specifications<br />
for NMS<br />
50 Do you need network configuration<br />
management as part <strong>of</strong> NMS s<strong>of</strong>tware?<br />
Depends upon system proposed<br />
by the bidder. Number <strong>of</strong><br />
computers etc, required is<br />
already included in the <strong>RFP</strong>.<br />
The date <strong>of</strong> submission <strong>of</strong> bid<br />
has been extended <strong>to</strong><br />
September 23, <strong>2013</strong> as per<br />
corrigendum 2<br />
It will be a standard NMS that<br />
moni<strong>to</strong>rs performance <strong>of</strong><br />
various networks /nodes, <strong>to</strong><br />
check failures <strong>of</strong> nodes as well<br />
change over <strong>to</strong> a better network<br />
in case <strong>of</strong> failure / poor<br />
performance <strong>of</strong> working<br />
network links (e.g. Change over<br />
from GSWAN <strong>to</strong> MPLS or VSAT<br />
links in case <strong>of</strong> failure <strong>of</strong> GSWAN<br />
link) - NMS will also help in<br />
checking up time <strong>of</strong> ICT links and<br />
calculations <strong>of</strong> penalties will be<br />
easier.<br />
It will be a standard NMS that<br />
moni<strong>to</strong>rs performance <strong>of</strong><br />
various networks /nodes, <strong>to</strong><br />
check failures <strong>of</strong> nodes as well<br />
change over <strong>to</strong> a better network<br />
in case <strong>of</strong> failure / poor<br />
performance <strong>of</strong> working<br />
network links (e.g. Change over<br />
from GSWAN <strong>to</strong> MPLS or VSAT<br />
links in case <strong>of</strong> failure <strong>of</strong> GSWAN<br />
link) - NMS will also help in<br />
checking up time <strong>of</strong> ICT links and<br />
calculations <strong>of</strong> penalties will be<br />
easier.
51<br />
52<br />
53<br />
18 1.2.6<br />
<strong>10</strong>7 1.3.5<br />
Emergency &<br />
Disaster<br />
Management<br />
(DM)/Brief<br />
description <strong>of</strong> the<br />
project<br />
SEOC<br />
Facility/Architectu<br />
re <strong>of</strong> Call /<br />
Dispatch center<br />
The large display systems, voice,<br />
data communication links and<br />
video-audio conferencing<br />
facilities at SEOC are for<br />
simultaneous use <strong>of</strong> the<br />
concerned <strong>of</strong>ficers from GSDMA<br />
and <strong>of</strong>ficers <strong>of</strong> departments<br />
(<strong>to</strong>gether up-<strong>to</strong> 30 persons)<br />
responsible for emergency<br />
support functions (“ESF”)<br />
SEOC will have provision <strong>of</strong><br />
required infrastructure for<br />
activating up-<strong>to</strong> 30 seat call<br />
center <strong>to</strong> handle end user calls<br />
and other alerts received during<br />
pre and post emergency<br />
situation. The call center system<br />
will<br />
have flexibility <strong>to</strong> allow<br />
relocation <strong>of</strong> specific number <strong>of</strong><br />
opera<strong>to</strong>r <strong>to</strong> other GSDR-ICTS<br />
nodes during severe incident.<br />
During normal period <strong>of</strong> steadystate<br />
conditions, up <strong>to</strong> 5 seats<br />
will remain active at the call<br />
center 24*7<br />
Do you need patch management solution<br />
for desk<strong>to</strong>ps? Please specify the technical<br />
requirements for the same?<br />
Apart from the Audio-video bridge, are<br />
you looking for an additional 30 port<br />
Audio bridge<br />
We will provision for a 30-seater call<br />
center with recording from day one at<br />
SEOC. However, relocation <strong>of</strong> specific<br />
number <strong>of</strong> opera<strong>to</strong>rs <strong>to</strong> other GSDR-ICTS<br />
nodes will depend on the infrastructure<br />
available at that particular site. It is<br />
suggested that a maximum qty for<br />
relocation is freeze and accordingly<br />
infrastructure for those many agents<br />
should be ready from day -one at all the<br />
GSDR-ICTS <strong>No</strong>des.<br />
Patch management has <strong>to</strong> come<br />
a part <strong>of</strong> solution.<br />
Solution should be designed<br />
commensuration with<br />
requirements specified in <strong>RFP</strong>.<br />
GSDMA is aware <strong>of</strong> limitations<br />
<strong>of</strong> these requirements. The<br />
opera<strong>to</strong>r should provide best<br />
solution using available<br />
resources. Freezing <strong>of</strong> numbers<br />
is not feasible as infrastructure<br />
at each ERC, DHQ will differ.
54<br />
55<br />
56<br />
127<br />
VSAT HUB<br />
Specifications<br />
Site Visit<br />
Project Report<br />
Page 115 talks <strong>of</strong> 512-1Mbps in-route and<br />
page 127 talks <strong>of</strong> 2 Mbps in route. As <strong>of</strong><br />
<strong>to</strong>day DOT only permits 512 Kbps<br />
inbound. A 4 Watt BUC is overkill for 512<br />
Kbps. Please Clarify.<br />
It is requested <strong>to</strong> arrange for a site visit<br />
including the visits <strong>to</strong> the buildings already<br />
available.<br />
As per established practices, the authority<br />
must have prepared a project report. It is<br />
requested <strong>to</strong> share the project report with<br />
us <strong>to</strong> understand the project con<strong>to</strong>urs.<br />
Design requirement is for a 2<br />
Mbps in route even if present<br />
permission is only for 512 Kbps<br />
data links. Please note that<br />
system is planned <strong>to</strong> operate for<br />
at least next <strong>10</strong> years, during<br />
which data rate restrictions may<br />
be relaxed. Higher Wattage ODU<br />
is recommended <strong>to</strong> ensure<br />
reliable operations even during<br />
heavy rains. Disasters in India<br />
such as Cyclones, floods either<br />
cause or are a result <strong>of</strong> heavy<br />
rains and network is expected <strong>to</strong><br />
work even during disaster<br />
situations.<br />
The bidder is free <strong>to</strong> visit the<br />
sites during working hours. The<br />
open house at SEOC site was<br />
organized on September 1, <strong>2013</strong><br />
It is not possible <strong>to</strong> share the<br />
project report with bidders.<br />
57<br />
23 1.3.6 Sec-1 - Overview<br />
Bid Due Date -<br />
31 August, <strong>2013</strong>, 1800 hrs<br />
As the project involves multiple sites and<br />
aspects, it is requested <strong>to</strong> extend the Bid<br />
Date by at least one month.<br />
The bid due date has been<br />
extended <strong>to</strong> September 23,<br />
<strong>2013</strong> as per the Corrigendum 2
58<br />
41 3.2.1 Sec-2 - ITB,<br />
2 Financial Strength -<br />
Documents Required<br />
a) The Bidder should have a<br />
minimum average turnover <strong>of</strong><br />
INR 200 Crores for the last five<br />
financial years from all its<br />
businesses and a minimum<br />
average turnover <strong>of</strong> INR 80<br />
Crores for the last five financial<br />
years from all its IT<br />
infrastructure services<br />
businesses.<br />
b) Sole Bidder / All Member <strong>of</strong><br />
the Consortium should have<br />
positive net worth for each <strong>of</strong><br />
the last five financial years.<br />
c) Minimum net worth <strong>of</strong> the<br />
Sole Bidder/ Lead Member at<br />
the end <strong>of</strong> last financial year<br />
should be at least INR 50.0<br />
Crores.<br />
d) The Sole Bidder/ Lead<br />
Member <strong>of</strong> the Consortium<br />
should have positive earnings<br />
(net pr<strong>of</strong>it), for each <strong>of</strong> the last<br />
five financial years.<br />
As we understand, in case <strong>of</strong> a<br />
Consortium, the minimum net worth<br />
requirement and the positive earnings<br />
requirement have <strong>to</strong> be met by the Lead<br />
Member, whereas the minimum average<br />
turnover requirements <strong>of</strong> INR 200 Cr. and<br />
<strong>of</strong> INR 80 Cr. have <strong>to</strong> be met by the<br />
combined turnover <strong>of</strong> the Consortium.<br />
Please confirm.<br />
The minimum average turnover<br />
has <strong>to</strong> be met by the lead<br />
bidder.
59<br />
60<br />
43 3.2.2 <strong>RFP</strong>, Sec-2 - ITB<br />
84 1.2<br />
<strong>RFP</strong>, Schedules &<br />
Annexes,<br />
Criteria for Evaluation <strong>of</strong><br />
Financial Strength Score for the<br />
sole bidder/lead member <strong>of</strong> the<br />
consortium<br />
The Opera<strong>to</strong>r shall obtain all<br />
necessary approvals/ clearances<br />
from concerned authorities /<br />
departments, as applicable,<br />
including:<br />
1) DoT/ TEC/ TRAI/ BSNL for<br />
network installation and<br />
operations.<br />
2) From Wireless Planning<br />
Commission (WPC) wing and<br />
Standing Advisory Committee<br />
for Frequency Allocation<br />
(SACFA), as required, for use <strong>of</strong><br />
Radio/ Microwave/ Wireless<br />
links and/or any related<br />
equipment.<br />
3) From local authorities (like<br />
Municipalities, PWD, HPSEB<br />
etc.), as required, including<br />
laying their own cables, mast<br />
erection, etc.<br />
The criteria related <strong>to</strong> CAGR, Debt <strong>to</strong><br />
Equity ratio and DSCR are highly stringent<br />
and will curb the competition. Further, the<br />
risk <strong>to</strong> the project increases with these<br />
conditions as a high CAGR (<strong>of</strong> last 5 years)<br />
<strong>of</strong> 20% is possible mostly with the<br />
emerging companies and may not be<br />
possible with the well established mature<br />
companies.<br />
It is, therefore, requested <strong>to</strong> remove these<br />
criteria and have the established practices<br />
<strong>of</strong> evaluating the Net Worth and Turnover<br />
figures.<br />
In last few years, many <strong>of</strong> the PPP projects<br />
have failed just on account <strong>of</strong> the project<br />
not getting the necessary approvals /<br />
clearances. It has been realized that the<br />
most suitable party for this responsibility<br />
is government. Hence, it is requested that<br />
while all facilitation would be extended by<br />
the Opera<strong>to</strong>r, GSDMA will obtain and<br />
provide any necessary approvals /<br />
clearances for the Project.<br />
<strong>No</strong> Change<br />
GSDMA is responsible for VSAT<br />
and wireless lance and satellite<br />
phones. All other licenses /<br />
clearances are <strong>to</strong> be obtained by<br />
the opera<strong>to</strong>r. GSDMA will<br />
extend all possible help.
61<br />
62<br />
63<br />
43<br />
220<br />
page 43<br />
3.2.2 Detailed<br />
Technical Criteria<br />
Service<br />
Agreement,<br />
Schedule II, Clause<br />
1.2 (a), Pages 220<br />
General<br />
b. Marks will be allotted <strong>to</strong> the<br />
bids based on quality and<br />
specifications <strong>of</strong> ICT systems and<br />
applications <strong>of</strong>fered by the<br />
bidder (sole or consortium) as<br />
well as his partners or<br />
subcontrac<strong>to</strong>rs<br />
The Opera<strong>to</strong>r shall transfer all<br />
the Assets on the last day <strong>of</strong> the<br />
Exit Management Period<br />
(“Transfer Date”) <strong>to</strong> GSDMA at<br />
zero value (INR 1) in case <strong>of</strong><br />
expiry <strong>of</strong> the Agreement, and in<br />
case <strong>of</strong> termination <strong>of</strong> the<br />
Agreement, at a fixed value<br />
which is equivalent <strong>to</strong> INR<br />
20,00,00,000/- (Indian Rupees<br />
Twenty Crores) less INR<br />
1,00,00,000/- (Indian Rupees<br />
One Crores) for each quarter or<br />
part there<strong>of</strong>, being the period<br />
from the Implementation Phase<br />
Completion Date / Go – Live till<br />
the Transfer Date..........<br />
It means experience <strong>of</strong> technology partner<br />
or subcontrac<strong>to</strong>r attributing <strong>to</strong> the<br />
technical scoring would be considered.<br />
Kindly confirm.<br />
Bankability <strong>of</strong> the service agreement is<br />
very important for successful financial<br />
closure <strong>of</strong> the project. As per established<br />
practices, the Termination Payment<br />
should be arrived on the basis <strong>of</strong><br />
independent valuation by the experts and<br />
must cover the Debt Due. Otherwise<br />
financing <strong>of</strong> the Project by Lenders would<br />
not be possible. Also in case <strong>of</strong><br />
Termination due <strong>to</strong> default by GSDMA, the<br />
Termination Payment should also include<br />
an amount equal <strong>to</strong> 1<strong>10</strong>% <strong>of</strong> Equity<br />
invested by the Opera<strong>to</strong>r <strong>to</strong> protect the<br />
opera<strong>to</strong>r's investments.<br />
It is requested <strong>to</strong> hold another prebid<br />
meeting after the site visit (say 2 weeks)<br />
so that we can clarify our doubts.<br />
Confirmed. However the bidder<br />
shall produce a back <strong>to</strong> back<br />
contract with the technology<br />
partner <strong>of</strong> subcontrac<strong>to</strong>r<br />
<strong>No</strong> change<br />
<strong>No</strong> Change
64 requirement is simple analog<br />
communication<br />
65<br />
66<br />
254,<br />
258,<br />
259<br />
Hardware, servers<br />
, peripherals etc:<br />
Schedule II Annex<br />
I Section 1.3.3:<br />
Hardware and<br />
peripherals:<br />
Routers, firewalls<br />
for<br />
interconnection<br />
with GSWAN and<br />
MPLS-VPN<br />
Addition requested<br />
We request you <strong>to</strong> consider modern<br />
digital network under pay as per usage<br />
plan.<br />
This will be similar <strong>to</strong> availing services<br />
instead <strong>of</strong> owning the network example<br />
TETRA network is being used in Delhi by<br />
the MCD, Home guard & Civil Defense,<br />
Revenue Department, and DTC, Health<br />
and Family Welfare department and Delhi<br />
Police. This mission critical service is<br />
found <strong>to</strong> be successfully running in Delhi.<br />
The same reduces the cost without<br />
compromising quality.<br />
We understand that GSDMA is seeking for<br />
best quality services at the time <strong>of</strong><br />
disasters. Owning the network<br />
components/elements (at least a few) are<br />
not the priority.<br />
Hence purchasing services (where ever<br />
possible/best suited) instead <strong>of</strong> owning<br />
the network (for example VSAT) can be<br />
considered as a solution.<br />
The same will bring down the cost<br />
effectively as because after 5 years most<br />
<strong>of</strong> the electronics component may be<br />
outdated.<br />
To have tighter integration & better<br />
interoperability, we suggest <strong>to</strong> have<br />
Routing, Switching & Security components<br />
from the same OEM. This will ensure one<br />
click integration between all these<br />
devices.<br />
<strong>No</strong> change. Bidder can <strong>of</strong>fer<br />
digital network but no financial<br />
compensation will be assured.<br />
<strong>RFP</strong> requirements are based on<br />
regula<strong>to</strong>ry conditions and not<br />
on the costing.<br />
<strong>No</strong> change
67<br />
68<br />
69<br />
<strong>10</strong>5<br />
1.3.4 SEOC - Audio<br />
Visual and<br />
Miscellaneous<br />
Services -<br />
Videoconference<br />
Room<br />
General<br />
Addition requested<br />
Large VC camera <strong>to</strong> cover every<br />
person in the room with<br />
capability <strong>to</strong> track speaker<br />
au<strong>to</strong>matically<br />
Routing & Switching systems provided<br />
OEM should be listed in Gartner’s Magic<br />
Leaders Quadrant for last 3 Years. Such<br />
clause would ensure GSDMA <strong>to</strong> have only<br />
qualified OEM participating in this bid.<br />
This would also ensure OEM's that are<br />
blacklisted in few countries can't<br />
participate in this secured & prestigious<br />
project.<br />
In a large conference room like the one<br />
you have requested in the <strong>RFP</strong>, this<br />
au<strong>to</strong>matically tracking the speaker may<br />
not be practical. There will be many<br />
participants in the room and there will be<br />
other noise / chatting, apart from the<br />
person who is talking. Hence the Camera<br />
will not be accurately track the person<br />
who is speaking, as there will be other<br />
ambient noise as well. A better solution is<br />
<strong>to</strong> provide "Look at Me" But<strong>to</strong>n on the<br />
table in front <strong>of</strong> every participant, so that<br />
the person can just <strong>to</strong>uch that but<strong>to</strong>n<br />
when he speaks, so that the camera will<br />
focus on that person only. This solution is<br />
more practical and useful in your kind <strong>of</strong><br />
scenario & requirement.<br />
In the interest <strong>of</strong> ICT Security, we strongly<br />
recommend that bidders should quote all<br />
the network equipments which comply <strong>to</strong><br />
EAL2 or higher standard. This will enable<br />
only <strong>to</strong>p OEMs in each category <strong>to</strong> qualify<br />
and will quote products which have<br />
undergone stringent security measures<br />
certified by independent certifying<br />
authorities. EAL2 or higher certification is<br />
applicable <strong>to</strong> switching and routing<br />
products which form the backbone <strong>of</strong> the<br />
network<br />
<strong>No</strong> change<br />
<strong>No</strong> change<br />
<strong>No</strong> change.
70<br />
The network will be operational on any<br />
INSAT series satellite in Ku Band. Please<br />
provide basic satellite parameters so that<br />
sample link budgets can be prepared<br />
What should be the concurrency fac<strong>to</strong>r in<br />
71<br />
the network? This is required for<br />
calculating inbound and outbound<br />
bandwidth for the network<br />
As voice and video will be prime<br />
72<br />
applications in the network, so do you<br />
require a RTT <strong>of</strong> less than 700 ms?<br />
73 Do you require multicast from remote <strong>to</strong><br />
remote or remote <strong>to</strong> hub?<br />
There are technically 2 requirements for<br />
Au<strong>to</strong> Geographic Hub Redundancy as<br />
required in the tender:<br />
a. 1. Both the Hubs should have the<br />
identical/similar Baseband technologies<br />
74<br />
b. Both the Hubs should operate on the<br />
same Satellite and Frequency Band<br />
Secondly, as per the regulations, the<br />
Shared Hub Service Providers may not<br />
operate Moving and Moveable Sites<br />
(Vehicle Mount/Fly-aways), so these sites<br />
may not operate on Shared Hub license<br />
The satellite capacity will be<br />
provided by Antrix on available<br />
satellite after installation and<br />
commissioning <strong>of</strong> the hub. The<br />
location arc <strong>of</strong> the satellite is<br />
indicated <strong>to</strong> ensure antenna<br />
tracking capabilities. <strong>RFP</strong> has<br />
included specifications for<br />
antenna and RF components<br />
that can support transmission<br />
up <strong>to</strong> 45.0 Mbps carrier on any<br />
satellite even with minimum<br />
G/T. GSDMA network<br />
requirement is only around 5.0<br />
Mbps outroute carrier as such<br />
no difficulty will be experienced<br />
for operation with any satellite.<br />
Suggested bandwidth will be<br />
sufficient for peak traffic loads<br />
at respective nodes. The node at<br />
SEOC may be at 16.0 mbps rate.<br />
One way (end <strong>to</strong> end) delay <strong>of</strong><br />
700 Ms. Is acceptable<br />
Yes<br />
Decision on hub redundancy will<br />
be taken by GSDMA in future.
75<br />
76<br />
121<br />
118<br />
Annexur<br />
e III<br />
Section<br />
1.2<br />
Annexur<br />
e III<br />
Section<br />
1.1<br />
Technical<br />
Specifications for<br />
Incident<br />
Management<br />
Application<br />
Sr 1.1 .Technical<br />
Specifications for<br />
Incident<br />
Management<br />
Portal<br />
The system should support:<br />
· Integration with ESRI ARCGIS<br />
server 9.3 <strong>to</strong> s<strong>to</strong>re, manage and<br />
analyze spatial data, including<br />
interoperability with the ARCGIS<br />
Server Web Application<br />
Development Framework (ADF).<br />
· Advanced spatial data types<br />
representing geometries such as<br />
points, lines, and polygons and<br />
many functions and features<br />
that interoperate with these<br />
data types.<br />
· All Vendors should ensure that<br />
proposed GIS platform (s)<br />
comply <strong>to</strong> OGC standards such<br />
as WMS, WPS, WFS, WCS etc.<br />
It is mentioned that there are<br />
“3000 certified users” and<br />
general public can also access<br />
the portal.<br />
Will GSDMA accept IMS s<strong>of</strong>tware which<br />
uses non-ESRI platforms like Google Map<br />
or similar as the base layer for the GIS<br />
module? Google Map provides a lot <strong>of</strong><br />
base data for India out <strong>of</strong> the box and IMS<br />
application can take advantage <strong>of</strong> the base<br />
data and can provide the capability <strong>to</strong><br />
create/view/update/delete necessary<br />
layers and provide all functionalities<br />
referred <strong>to</strong> in the <strong>RFP</strong> (and later integrate<br />
<strong>to</strong> whatever GIS platform, ESRI ARCGIS<br />
etc., the government might already have if<br />
required at all). Essentially we are trying <strong>to</strong><br />
clarify if ESRI product ArcGIS 9.3 Server<br />
based GIS is an absolute requirement for<br />
this project, or can vendors propose<br />
comparable/better mapping capability<br />
based on “<strong>No</strong>n-ESRI platforms” like<br />
Google Maps?<br />
• What is the meaning <strong>of</strong> “certified<br />
users”? What is the functionality they will<br />
allow <strong>to</strong> execute? - I am assuming<br />
certified users are registered users <strong>of</strong> the<br />
application and their access <strong>to</strong> the site is<br />
role and responsibility based<br />
• How general public will access portal?<br />
What will be registration mechanism for<br />
these users? – So we are assuming that<br />
general public will have access <strong>to</strong> the<br />
unrestricted area <strong>of</strong> the website<br />
We need <strong>to</strong> develop application<br />
considering load balancing as well as load<br />
testing and stress testing needs <strong>to</strong> be<br />
performed in order <strong>to</strong> make application<br />
scale well with more users.<br />
(Application should be able <strong>to</strong> scale<br />
horizontally.)<br />
IMS s<strong>of</strong>tware working on <strong>No</strong>n<br />
ESRI platform will be accepted.<br />
Google map or other suitable<br />
base layer is accepted provided<br />
IMS meets other specifications<br />
Certified users are those that<br />
have been registered and<br />
approved for access by GSDMA:<br />
These include accredited NGOs,<br />
International aid agencies, press<br />
personnel etc. Assumptions<br />
regarding access <strong>to</strong> public are<br />
correct.
77<br />
78<br />
118<br />
118<br />
Annexur<br />
e III<br />
Section<br />
1.1<br />
Annexur<br />
e III<br />
Section<br />
1.1<br />
Sr. <strong>No</strong>. - 1.2<br />
Technical<br />
Specifications for<br />
Incident<br />
Management<br />
Portal<br />
Sr. <strong>No</strong>. - 1.3<br />
Technical<br />
Specifications for<br />
Incident<br />
Management<br />
Portal<br />
The system should support<br />
menus driven by statically<br />
defined role-based access<br />
control for various stake holders<br />
as per requirements <strong>to</strong> access<br />
information regarding status <strong>of</strong><br />
disaster (s)<br />
Sr. 3. The system should<br />
support:<br />
· Syndicated content from news<br />
feeds (RSS)<br />
· External web-based<br />
applications with options <strong>to</strong><br />
launch in popup window, display<br />
in iFrame and content<br />
syndication via web clipping<br />
· For JDBC/ODBC<br />
· For web services (SOAP, WSDL<br />
and UDDI)<br />
· for Web Services for Interactive<br />
Applications (WSIA)<br />
· free text searches<br />
· structured searches driven by<br />
metadata<br />
· management <strong>of</strong> content from<br />
multiple reposi<strong>to</strong>ries<br />
· In-place editing <strong>of</strong> content<br />
· Content conversion (e.g. Word<br />
<strong>to</strong> HTML)<br />
· Widely used operating systems<br />
and web browsers<br />
· Industry standard database<br />
management systems and<br />
· Widely used direc<strong>to</strong>ry servers<br />
Please confirm, if there be “district” or<br />
“taluka” level admin who can broadcast<br />
disaster related information?? Also the<br />
‘roles’ need <strong>to</strong> be defined duly.<br />
We propose there will be one master<br />
admin > district level admin > end users.<br />
We need set <strong>of</strong> functionality so that roles<br />
can be mapped <strong>to</strong> functionality. Will this<br />
be acceptable??<br />
This application will be a CMS site so all<br />
RSS feeds can be defined by admin and<br />
these will be shown on <strong>to</strong> all the users<br />
which they can turn <strong>of</strong>f or on <strong>to</strong> control<br />
the feeds they want <strong>to</strong> receive<br />
“External web-based applications with<br />
options <strong>to</strong> launch in popup window,<br />
display in iFrame and content syndication<br />
via web clipping” - Does it mean that the<br />
requirement is <strong>to</strong> launch another web<br />
application inside the IMPS and not as a<br />
new window?<br />
“In-place editing <strong>of</strong> content “and<br />
“Content conversion (e.g. Word <strong>to</strong> HTML)<br />
“– We are assuming admin <strong>of</strong> the site<br />
would need these features – Would the<br />
application need an RTE (Rich Text edi<strong>to</strong>r)<br />
for the admin <strong>to</strong> these update?<br />
“Widely used direc<strong>to</strong>ry servers” – Please<br />
provide some examples <strong>of</strong> this<br />
requirement?<br />
GSDMA will clearly define the<br />
Roles and users as part <strong>of</strong> SOP<br />
handed over <strong>to</strong> the selected<br />
bidder. The application should<br />
be configurable.<br />
1) The assumption regarding<br />
IMPS is valid.<br />
2) Assumptions regarding<br />
content conversion are also<br />
valid<br />
3) Widely used is applicable in<br />
cases <strong>of</strong> Internet browsers and<br />
not direc<strong>to</strong>ry servers
79<br />
80<br />
81<br />
82<br />
83<br />
84<br />
85<br />
86<br />
87<br />
118<br />
118<br />
Annexur<br />
e III<br />
Section<br />
1.1<br />
Annexur<br />
e III<br />
Section<br />
1.1<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
Sr. <strong>No</strong>. - 1.4<br />
Technical<br />
Specifications for<br />
Incident<br />
Management<br />
Portal<br />
Sr. <strong>No</strong>. - 1.4<br />
Technical<br />
Specifications for<br />
Incident<br />
Management<br />
Portal<br />
Sr. 1.13 The systems should<br />
allow The administra<strong>to</strong>r <strong>to</strong><br />
configure user interface <strong>to</strong><br />
deliver a standard taxonomy<br />
and terminology. Site<br />
management must enable<br />
department level cus<strong>to</strong>mization<br />
<strong>of</strong> specific elements<br />
Sr. <strong>No</strong> 1.15 The systems should<br />
Provide federated search<br />
capabilities <strong>to</strong> enable propertybased<br />
and full-text queries<br />
against multiple reposi<strong>to</strong>ries,<br />
returning an aggregated result<br />
set.<br />
What is meant by “Site management must<br />
enable department level cus<strong>to</strong>mization <strong>of</strong><br />
specific elements”??<br />
Federated search will be amongst<br />
different departmental only. Please clarify<br />
if it can also contain external data??<br />
Request <strong>to</strong> provide the Au<strong>to</strong> CAD Electrical<br />
Single Line Diagram <strong>of</strong> EOC<br />
Request <strong>to</strong> confirm the EOC room height<br />
from True ceiling <strong>to</strong> True floor<br />
Request <strong>to</strong> provide the Electricity board<br />
sanction power availability in kva or kw<br />
Request <strong>to</strong> provide the details <strong>of</strong> existing<br />
Distribution transformer<br />
Request <strong>to</strong> confirm the availability <strong>of</strong><br />
lightning arrester in EOC<br />
Request <strong>to</strong> confirm the location <strong>of</strong> Earth<br />
pit for Electrical panel, UPS, batteries and<br />
DG, fuel tank.<br />
Request <strong>to</strong> confirm the route <strong>of</strong> cable<br />
entering in <strong>to</strong> the EOC room<br />
The specification is related <strong>to</strong><br />
appearance, heading, content<br />
etc. for any department in the<br />
website. This should be possible<br />
for administra<strong>to</strong>r by using<br />
browser based <strong>to</strong>ols<br />
Assumption is correct. External<br />
data search should be possible<br />
after it has been archived in the<br />
system.<br />
The layout <strong>of</strong> the SEOC has been<br />
attached for your reference. An<br />
Open house was conducted on<br />
September 1 at SEOC for the<br />
same. The bidders can<br />
undertake site visit <strong>of</strong> EOCs for<br />
further information<br />
Ref supporting documents<br />
Ref supporting documents for<br />
genera<strong>to</strong>r specification at SEOC<br />
These details are not essential<br />
<strong>to</strong> design the solution GSDMA<br />
guarantees required quantity <strong>of</strong><br />
mains power<br />
Opera<strong>to</strong>r has <strong>to</strong> ensure the<br />
availability<br />
Opera<strong>to</strong>r's responsibility <strong>to</strong><br />
construct earth pits at all sites<br />
Site visit will provide necessary<br />
details.
88<br />
89<br />
90<br />
91<br />
92<br />
93<br />
94<br />
95<br />
96<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
Request <strong>to</strong> confirm the position <strong>of</strong> all the<br />
equipments like UPS, batteries, Electrical<br />
panels & DG set<br />
Request <strong>to</strong> provide <strong>to</strong>tal Power required<br />
for SEOC<br />
Request <strong>to</strong> provide <strong>to</strong>tal Power required<br />
for DEOC<br />
Request <strong>to</strong> provide <strong>to</strong>tal Power required<br />
for TEOC<br />
Request <strong>to</strong> provide <strong>to</strong>tal capacity <strong>of</strong> UPS &<br />
back up time required for SEOC<br />
Request <strong>to</strong> provide <strong>to</strong>tal capacity <strong>of</strong> UPS &<br />
back up time required for DEOC<br />
Request <strong>to</strong> provide <strong>to</strong>tal capacity <strong>of</strong> UPS &<br />
back up time required for TEOC<br />
Request <strong>to</strong> provide <strong>to</strong>tal capacity <strong>of</strong> DG &<br />
back up time required for SEOC<br />
Request <strong>to</strong> provide <strong>to</strong>tal capacity <strong>of</strong> DG &<br />
back up time required for DEOC<br />
Site visit will provide necessary<br />
details.<br />
Power requirements depend<br />
upon opera<strong>to</strong>r's design. Existing<br />
systems such as lighting, airconditioning<br />
are already catered<br />
for.<br />
Power requirements depend<br />
upon opera<strong>to</strong>r's design. Existing<br />
systems such as lighting, airconditioning<br />
are already catered<br />
for.<br />
Power requirements depend<br />
upon opera<strong>to</strong>r's design. Existing<br />
systems such as lighting, airconditioning<br />
are already catered<br />
for.<br />
Please refer <strong>to</strong> detailed specs<br />
and testing conditions in <strong>RFP</strong><br />
Please refer <strong>to</strong> detailed specs<br />
Please refer <strong>to</strong> detailed specs<br />
Please refer <strong>to</strong> existing<br />
equipment details for DG set<br />
requirement. Opera<strong>to</strong>r has <strong>to</strong><br />
ensure back-up genera<strong>to</strong>r and<br />
fuels supply <strong>to</strong> last up <strong>to</strong> at least<br />
48 hours <strong>to</strong> ensure continuity <strong>of</strong><br />
operations<br />
Opera<strong>to</strong>r has <strong>to</strong> provide back-up<br />
for his equipment, lighting and<br />
air-conditioning (for 20.0 Sq.<br />
Meters) area at DEOC. Should<br />
also provide fuel for at least up<br />
<strong>to</strong> 48 hours <strong>of</strong> operations
97<br />
98<br />
99<br />
<strong>10</strong>0<br />
<strong>10</strong>1<br />
<strong>10</strong>2<br />
<strong>10</strong>3<br />
<strong>10</strong>4<br />
133<br />
<strong>10</strong>8<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
14<br />
POWER<br />
SUPPLY<br />
1.3.7<br />
Facility<br />
Manage<br />
ment<br />
Room<br />
POWER SUPPLY<br />
Access control<br />
system need <strong>to</strong> be<br />
provided as part<br />
<strong>of</strong> the solution<br />
<strong>10</strong>KVA Diesel genera<strong>to</strong>rs as<br />
main power source<br />
All SEOC area other than press<br />
conference room should have<br />
Access control system<br />
Request <strong>to</strong> provide <strong>to</strong>tal capacity <strong>of</strong> DG &<br />
back up time required for TEOC<br />
Request <strong>to</strong> confirm whether we need <strong>to</strong><br />
consider redundancy for DG, UPS &<br />
Cooling units in all the PoPs.<br />
Request <strong>to</strong> confirm the type Air<br />
conditioning for EOC either PAC or<br />
comfort AC.<br />
Request <strong>to</strong> confirm the distance between<br />
Cooling indoor unit and out door unit<br />
Request <strong>to</strong> confirm whether you need<br />
raised floor & false ceiling in every EOC<br />
Request <strong>to</strong> confirm which type <strong>of</strong> furniture<br />
& workstation required for call center,<br />
video conference room<br />
Request <strong>to</strong> provide <strong>to</strong>tal back up time<br />
required for ERV<br />
Request <strong>to</strong> confirm whether bidder has <strong>to</strong><br />
consider Manual fire extinguisher , Fire<br />
Alarm system, Rodent repellent and<br />
Building Management System <strong>to</strong> moni<strong>to</strong>r<br />
each and every EOC<br />
Opera<strong>to</strong>r has <strong>to</strong> provide back-up<br />
for his equipment, lighting and<br />
air-conditioning (for 20.0 Sq.<br />
Meters) area at TEOC. Should<br />
also provide fuel for at least up<br />
<strong>to</strong> 48 hours <strong>of</strong> operations<br />
Redundancy is essential at SEOC<br />
Opera<strong>to</strong>r's choice <strong>to</strong> ensure<br />
efficient cooling<br />
Site survey will provide details<br />
<strong>No</strong>t required<br />
Ergonomical and aiding efficient<br />
operations in call centre.<br />
Furniture in operations room<br />
and VC should be up <strong>to</strong> the<br />
standard expected for use <strong>of</strong><br />
senior government <strong>of</strong>ficers and<br />
state functionaries.<br />
Back-up for 24X7 operations till<br />
availability <strong>of</strong> mains supply at<br />
site<br />
BMS is necessary at SEOC. GoG<br />
will take care <strong>of</strong> requirements at<br />
other locations.
<strong>10</strong>5<br />
<strong>10</strong>6<br />
<strong>10</strong>7<br />
91<br />
<strong>10</strong>5<br />
1.<strong>10</strong><br />
Operatin<br />
g<br />
expenses<br />
(OPEX) <strong>of</strong><br />
GSDR-<br />
ICTS<br />
opera<strong>to</strong>r<br />
1.3.4<br />
SEOC<br />
84 1.2<br />
Facility<br />
Management<br />
Press conference<br />
room<br />
Project<br />
Implementation<br />
Expenses for consumables<br />
(eg.:paper, ink cartridge & fuel<br />
etc) genera<strong>to</strong>r fuel/ lubricant<br />
and electricity consumption at<br />
the PoP<br />
This is a large room already<br />
furnished (please refer <strong>to</strong> the<br />
furniture & fixture layout<br />
already provided)<br />
The Opera<strong>to</strong>r shall obtain all<br />
necessary approvals/ clearances<br />
from concerned authorities /<br />
departments, as applicable,<br />
including:<br />
From local authorities (like<br />
Municipalities, PWD, HPSEB<br />
etc.), as required, including<br />
laying their own cables, mast<br />
erection, etc.<br />
All expenses like fuel, lubricant, Electricity<br />
consumption & refrigrent for AC should<br />
have be taken care by the bidder?<br />
Request <strong>to</strong> provide the Layout for<br />
furniture & fixture <strong>of</strong> all the rooms & how<br />
many seaters required in press conference<br />
room<br />
All fiber which is terminating <strong>to</strong> SEOC from<br />
DEOC, TEOC <strong>to</strong> DEOC, TEOC <strong>to</strong> Village is <strong>to</strong><br />
be provided by GSDMA. As per the clause<br />
1 GENERAL REQUIREMENT PAGE <strong>NO</strong>: 82<br />
(<strong>State</strong> Data Centre (SDC) will be<br />
integrated with SEOC through OFC/GB<br />
Ethernet. This would be provided by<br />
GSDMA.<br />
· <strong>Gujarat</strong> <strong>State</strong> Wide Area Network (an e-<br />
Governance infrastructure) would be<br />
linked <strong>to</strong>/ Integrated with GSDR-ICTS<br />
through OFC/GB Ethernet. This would be<br />
provided by GSDMA.)<br />
We understand that as laying <strong>of</strong> OFC is<br />
out <strong>of</strong> scope <strong>of</strong> GSDR ICTS, Still we need<br />
<strong>to</strong> take the approval from Municipalities,<br />
PWD, HPSEB etc if yes then for what<br />
purpose.<br />
Yes<br />
The layout <strong>of</strong> the SEOC has been<br />
attached for your reference [Ref<br />
Supporting documents]. All<br />
bidders were invited <strong>to</strong> open<br />
house on 1st September <strong>to</strong> see<br />
the size and furniture <strong>of</strong> rooms<br />
at SEOC<br />
GSDMA has taken necessary<br />
clearnace from concerned<br />
departments for right <strong>of</strong> the way<br />
<strong>to</strong> lay OFC / telephone cables<br />
between SEOC, SDC, SICN and<br />
GIDM and has laid the cables<br />
<strong>10</strong>8<br />
84 1.1 The project Plan Conduct detailed site survey<br />
Request <strong>to</strong> provide the complete au<strong>to</strong> cad<br />
drawing for all the sites.<br />
Refer supporting documents for<br />
layout <strong>of</strong> SEOC
<strong>10</strong>9<br />
1<strong>10</strong><br />
111<br />
<strong>10</strong>8 1.3.7<br />
Facility<br />
management<br />
room page <strong>10</strong>8<br />
<strong>10</strong>8 1.4 District EOC<br />
116 1.9<br />
Alert & Warning<br />
System<br />
All SEOC areas other than Press<br />
Conference Room (PCR) should<br />
have electronic access control<br />
system that allows the access <strong>of</strong><br />
facility <strong>to</strong> authorized personals.<br />
· Access controls should be<br />
installed for entry <strong>to</strong> all<br />
operational rooms and <strong>of</strong>fices <strong>of</strong><br />
senior <strong>of</strong>ficers with restricted<br />
access <strong>to</strong> different areas based<br />
on defined access policy.<br />
· The system must also log the<br />
entry and exit for card holders<br />
and provides the data for<br />
auditing.<br />
· Access control must use either<br />
card or dual authentication <strong>of</strong><br />
card + finger print on the predefined<br />
entry side and release<br />
switch on the exit side.<br />
DEOC would be interfaced with<br />
Existing GSWAN Network<br />
through OFC / GB Ethernet and<br />
Communicate with GSDR-ICTS<br />
Network<br />
Total <strong>of</strong> 21 siren <strong>to</strong>wers will be<br />
controlled and managed by<br />
SEOC or by concerned DEOC(s)<br />
as per the list enclosed<br />
- Please explain for facility management<br />
rooms all Ethernet cabling required for<br />
access control is already laid or opera<strong>to</strong>r<br />
needs <strong>to</strong> fac<strong>to</strong>r the laying <strong>of</strong> cable.<br />
( As stated in the bid page <strong>10</strong>2 - all rooms<br />
other than operation room,<br />
videoconference room and alert and<br />
warning room are already furnished and<br />
General lighting, air-conditioning,<br />
telephone and Ethernet wiring is installed<br />
in all rooms as shown in relevant<br />
building)<br />
We understand the OFC connectivity from<br />
DEOC and with Existing GSWAN is<br />
provided by GSDA<br />
We assume that no control is needed at<br />
TEOCs & ERVs (configuration <strong>of</strong> sirens etc),<br />
but can issue alerts. Pl suggest.<br />
Ethernet cabling exists. However<br />
it has not been used for last two<br />
years; as such opera<strong>to</strong>r may<br />
have <strong>to</strong> lay new cabling for<br />
proposed systems.<br />
GSDMA has taken necessary<br />
clearance from concerned<br />
departments for right <strong>of</strong> the way<br />
<strong>to</strong> lay OFC / telephone cables<br />
between SEOC, SDC, SICN and<br />
GIDM and has laid the cables<br />
Read page 117 "The warning<br />
message controller is <strong>to</strong> be<br />
installed at GSEOC Gandhinagar<br />
with back-up controls at<br />
concerned DEOCs"
112<br />
113<br />
114<br />
<strong>10</strong>0 2 b-c<br />
42 3.2.1<br />
<strong>10</strong>1 1.12<br />
Infrastructure<br />
provided by<br />
GSDMA<br />
Captive VSAT communication<br />
network is <strong>to</strong> be set-up <strong>to</strong><br />
operate in Ku-Band frequency<br />
including Hub at Gandhinagar<br />
The bidder must have<br />
experience <strong>of</strong> implementing at<br />
least one project related <strong>to</strong>:<br />
Emergency Operations Centre or<br />
Network Operations Centre<br />
experience Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations ) in<br />
Projects with over 50 WAN<br />
nodes for Defense or Finance<br />
organization<br />
SEOC, DEOC, TEOC and ERC<br />
buildings have already been<br />
constructed or identified in the<br />
state. Building drawings <strong>of</strong> SEOC<br />
are given in the separate files.<br />
SEOC building is provided with<br />
the main power supply through<br />
redundant feeders (two sources)<br />
from domestic electric<br />
distribution company. The<br />
building also has a Diesel<br />
genera<strong>to</strong>r <strong>of</strong> requisite capacity<br />
as a backup arrangement and it<br />
au<strong>to</strong>matically takes over the<br />
load during interruption <strong>of</strong> the<br />
normal source.<br />
We suggest that for bandwidth<br />
requirement <strong>of</strong> mere 5 Mbps, a dedicated<br />
Hub setup is not required. The same may<br />
be put on a Shared Hub network. GSDMA<br />
may apply for special COTM license with a<br />
permission <strong>to</strong> work on Shared Hub. This<br />
will reduce the cost implication <strong>of</strong> the<br />
overall project and will facilitate optimized<br />
solution <strong>to</strong> GSDMA.<br />
Is it manda<strong>to</strong>ry <strong>to</strong> have Defense or<br />
Finance experience?<br />
Other state/central govt organization<br />
experience will be considered. Request<br />
Confirm<br />
Pls provide the building details?<br />
Transportable and portable<br />
VSATs are not allowed in shared<br />
Hub services; hence GSDMA has<br />
opted for captive hub.<br />
Necessary funds are allocated<br />
<strong>to</strong>wards cost <strong>of</strong> captive hub.<br />
The bidder must have<br />
experience <strong>of</strong> implementing at<br />
least one project related <strong>to</strong>:<br />
Emergency Operations Centre or<br />
Network Operations Centre<br />
experience Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations ) in<br />
Projects with over 50 WAN<br />
nodes for Defense/Finance<br />
organization/Central or <strong>State</strong><br />
Government<br />
Details can be obtained from<br />
site visit.
115<br />
<strong>10</strong>3 1.3.3<br />
SEOC Connectivity<br />
& facility<br />
Multi-purpose, IP based Help<br />
desk /contact center shall be<br />
used during normal as well as<br />
during emergencies. The facility<br />
will have flexible design <strong>to</strong><br />
absorb sudden scalability<br />
requirement during severe<br />
incidents. The contact center<br />
will have interfaces with<br />
emergency call services like <strong>10</strong>8,<br />
<strong>10</strong>1,<strong>10</strong>0,<strong>10</strong>2. The key features<br />
<strong>of</strong> Helpdesk systems are – Call<br />
management (from private and<br />
public domain), inven<strong>to</strong>ry<br />
tracking and its management,<br />
recording <strong>of</strong> all incidents and<br />
service calls (in and out),<br />
Configuration management,<br />
Service level management,<br />
Problem management , Change<br />
management<br />
Pls specify the number <strong>of</strong> call takers,<br />
Supervisors, and Helpdesk staff at SEOC.<br />
Number <strong>of</strong> call centre agents /<br />
shift for normal as well<br />
emergency situations is<br />
specified in the <strong>RFP</strong>. Number <strong>of</strong><br />
supervisors and help desk staff<br />
is <strong>to</strong> be decided by the opera<strong>to</strong>r.
116<br />
117<br />
<strong>10</strong>4 1.3.4<br />
<strong>10</strong>4 1.3.4<br />
SEOC Command /<br />
Operational Room<br />
SEOC Command /<br />
Operational Room<br />
Each display should be able <strong>to</strong><br />
have video feed from a variety<br />
<strong>of</strong> sources, including staff<br />
computers, DVD/CD players,<br />
public news broadcasts, and<br />
teleconferencing systems. Each<br />
console station for staff should<br />
have a minimum <strong>of</strong> 1 desk<strong>to</strong>p, 1<br />
telephone and 1 data<br />
communication connections and<br />
possible radio connections.<br />
Public address capability is <strong>to</strong> be<br />
installed from positions <strong>of</strong><br />
senior <strong>of</strong>ficers (first row),<br />
possibly through the phone<br />
system, as well as connections<br />
<strong>to</strong> the communications and<br />
command conference spaces.<br />
The <strong>to</strong>tal number <strong>of</strong> stations<br />
required in the operations room<br />
will be a function <strong>of</strong> the number<br />
<strong>of</strong> staff required <strong>to</strong> be present. A<br />
provision for 40 workstations<br />
may be made in Operations<br />
room and up-<strong>to</strong> 30 workstations<br />
in Call centre.<br />
What type <strong>of</strong> telephones need <strong>to</strong> be<br />
provided <strong>to</strong> each staff i.e. Analog / VOIP,<br />
This contradicts with requirement <strong>of</strong> 8<br />
VOIP phone requirement in operation<br />
room mentioned in Pg <strong>No</strong> <strong>10</strong>3. Pls clarify<br />
By data connection, it is unders<strong>to</strong>od that<br />
operation room staff will have LAN &<br />
Internet connectivity. Pls confirm our<br />
understanding is correct. If not pls specify<br />
what additional type <strong>of</strong> data connectivity<br />
is required at each desk<strong>to</strong>p.<br />
What type <strong>of</strong> radio connectivity is<br />
expected at operation room?<br />
How these radios will be operated by the<br />
staff, usage <strong>of</strong> the same with an example<br />
will be really helpful.<br />
Do we need <strong>to</strong> consider 30 workstation<br />
with call taking & supervising capabilities?<br />
If the above is not correct, pls specify the<br />
no <strong>of</strong> call takers, no <strong>of</strong> supervisors<br />
operating normally and the maximum call<br />
takers / supervisors during disaster<br />
situation.<br />
1) ISDN telephones are<br />
necessary in the operations<br />
room for use <strong>of</strong> Government<br />
staff <strong>to</strong> access outside world.<br />
These staff will use ISDN lines<br />
2) 8 VoIP phones will be used on<br />
GSWAN, MPLS , Internet and<br />
VSAT in case ATA is not used<br />
3) assumptions regarding LAN<br />
connectivity are correct<br />
4) Operations room / call centre<br />
will have VHF radio gateway via<br />
USI for interconnection with<br />
wireless radios <strong>of</strong> ESF<br />
departments (police , fire<br />
brigade etc.) . HF radio<br />
transceiver will also be<br />
available. Use <strong>of</strong> these sets /<br />
gateway is <strong>to</strong> interact with ESF<br />
departments and first<br />
responders.<br />
Yes. This is required <strong>to</strong> take care<br />
<strong>of</strong> emergency situations when<br />
full staff is deployed.<br />
118<br />
<strong>10</strong>6<br />
Schematic <strong>of</strong><br />
Signal<br />
Connectivity<br />
within SEOC<br />
building<br />
Surveys <strong>of</strong> the GSDMA infrastructure<br />
provided for SEOC / DEOC’s will need<br />
some time.<br />
Request provide extension <strong>to</strong> bid<br />
submission for undertaking these activities<br />
The last date <strong>of</strong> submission <strong>of</strong><br />
bid extended <strong>to</strong> September 23,<br />
<strong>2013</strong>. [Refer corrigendum 2]
119<br />
120<br />
<strong>10</strong>7 1.3.5<br />
<strong>10</strong>8 1.3.8<br />
Architecture <strong>of</strong><br />
Call / Dispatch<br />
Center<br />
Public Address<br />
System<br />
External emergency call centers<br />
operated and managed by other<br />
agencies (<strong>10</strong>8, industrial<br />
emergency, health, fire, police<br />
etc) will be interfaced with the<br />
SEOC call center.<br />
A public address system with<br />
redundant amplifiers and<br />
speakers for reliable operations<br />
should be installed in SEOC for<br />
broadcasting important<br />
messages or instructions. PA<br />
system will also be used for<br />
security and disaster (fire alarm)<br />
related messages. The system<br />
must be capable <strong>of</strong> taking inputs<br />
from different areas (call<br />
stations) <strong>of</strong> SEOC like<br />
conference room, video<br />
conference or meeting room<br />
with priority settings as well as<br />
priority bypass switch for<br />
emergencies. Speakers should<br />
be installed as a mix <strong>of</strong> ceilingmount,<br />
surface-mount, horn and<br />
cabinet speakers<br />
DIAL<strong>10</strong>0 / <strong>10</strong>8 calls will be routed <strong>to</strong> their<br />
respective control centers, mostly<br />
operated by police.<br />
How will these calls get diverted <strong>to</strong> SEOC’s<br />
during disaster situation, and who will be<br />
responsible for such call routing i.e.<br />
Service provider / GSDMA.<br />
Pls specify the no <strong>of</strong> rooms in SEOC <strong>to</strong> be<br />
equipped with PA system<br />
Routing will be done by 24X7<br />
call centre staff for respective<br />
help lines via ISDN links at SEOC<br />
as per agreed SOP between call<br />
centers and GSDMA.<br />
PA system already in place with<br />
specific number <strong>of</strong> location.<br />
Bidders are required <strong>to</strong> assess<br />
the existing system and decided<br />
<strong>to</strong> integrate / not <strong>to</strong> integrate<br />
same in the solution. Existing PA<br />
system will be handed over <strong>to</strong><br />
opera<strong>to</strong>r in "as is condition".
121<br />
122<br />
123<br />
124<br />
<strong>10</strong>8 1.4 Cl <strong>No</strong> District EOC<br />
120 1.9<br />
120 1.15<br />
120 1.17<br />
120 / 1.2/ Sr. <strong>No</strong><br />
1.9<br />
120 /1.2/ Sr. <strong>No</strong><br />
1.15<br />
120 /1.2/ Sr. <strong>No</strong><br />
1.17<br />
The system should have ability<br />
<strong>to</strong> handle all types <strong>of</strong> files<br />
(documents, presentations,<br />
spreadsheets, images,<br />
multimedia and others) either<br />
by uploading and s<strong>to</strong>ring; or by<br />
linking <strong>to</strong> them.<br />
The system should facilitate:<br />
Upload / download any type <strong>of</strong><br />
files<br />
The system should support<br />
Web-based administration <strong>to</strong>ols<br />
<strong>to</strong> enable remote system<br />
management at any time or<br />
place<br />
• Pls specify the no <strong>of</strong> PC’s required at<br />
DEOC’s<br />
• <strong>No</strong> <strong>of</strong> VOIP Phones / Analog phones<br />
required with each staff<br />
• Limited call taking / dispatch capabilities<br />
is required. Pls specify no <strong>of</strong> call takers /<br />
dispatchers required and methodology <strong>to</strong><br />
connect the incoming calls. Will it be thru<br />
PSTN phone line locally or calls landing on<br />
SEOC will be directed.<br />
• Is it manda<strong>to</strong>ry <strong>to</strong> provide Hardware<br />
based video conferencing device, if not<br />
can we propose desk<strong>to</strong>p based VC facility<br />
meeting the operational requirement and<br />
quality <strong>of</strong> service.<br />
Do you currently have any incident<br />
management application?<br />
Do you have plan for implementing<br />
complete Help desk system including<br />
(Request, Call, incident, problem<br />
management, knowledge management)<br />
Please confirm types <strong>of</strong> file <strong>to</strong> be uploaded<br />
or downloaded.<br />
Please elaborate Remote system<br />
management requirement in detail.<br />
Detailed information is available<br />
in the <strong>RFP</strong>.<br />
1) <strong>No</strong>.<br />
2) Help desk system is <strong>to</strong> be<br />
provided by the opera<strong>to</strong>r as per<br />
<strong>RFP</strong><br />
Files will include data from<br />
various organizations<br />
responsible for providing alerts,<br />
SDRN data files, emails ,<br />
Geospatial databases, video files<br />
etc.<br />
It should be possible <strong>to</strong> take<br />
control and operate IMS or IMSP<br />
from fixed or transportable<br />
nodes if necessary
125<br />
126<br />
127<br />
128<br />
120 1.2<br />
113 1.4<br />
248 3<br />
248 3<br />
120 /1.2/ Sr. <strong>No</strong><br />
1.20<br />
Screen sharing, Shared<br />
electronic whiteboard, Online<br />
meeting management services<br />
<strong>to</strong> schedule, attend or view<br />
information about scheduled<br />
and finished meetings<br />
It is expected <strong>to</strong> hold and<br />
manage the Reposi<strong>to</strong>ry <strong>of</strong><br />
various SW along with latest<br />
patches for fast deployment.<br />
Downloading new network<br />
parameters remotely <strong>to</strong> all<br />
VSATs<br />
Measure bandwidth utilization<br />
for various applications<br />
Please elaborate on shared electronic<br />
whiteboard requirement.<br />
Please elaborate which s<strong>of</strong>tware and<br />
patches <strong>to</strong> be deployed.<br />
Please elaborate <strong>of</strong> new network<br />
parameters remotely <strong>to</strong> all VSATs.<br />
Currently do they have any application<br />
which is used for moni<strong>to</strong>ring and<br />
managing VSATs?<br />
Please give us details about list <strong>of</strong><br />
application for bandwidth measurement<br />
It should be possible <strong>to</strong> provide<br />
inputs / have access <strong>to</strong> white<br />
boards from multiple locations<br />
Patches are <strong>to</strong> be provided <strong>to</strong> all<br />
operational system application<br />
s<strong>of</strong>twares including security<br />
systems<br />
This is a standard facility<br />
provided by all reputed OEMS<br />
for all VSAT networks that<br />
allows effecting changes in<br />
network parameters including<br />
frequencies, up link power etc.<br />
at remote locations through<br />
NMS at Hub.<br />
Data and video transfers /<br />
videoconferencing and Internet<br />
usage for IMPS<br />
129<br />
143 1.4 Annexure-I<br />
The data needs <strong>to</strong> be migrated<br />
in<strong>to</strong> the new system and the<br />
database/applications need <strong>to</strong><br />
be redesigned in consultation<br />
with GSDMA<br />
Please provide us the size and volume <strong>of</strong><br />
the SDRN data for <strong>Gujarat</strong> <strong>to</strong> be migrated.<br />
Kindly provide details as <strong>to</strong> the type <strong>of</strong><br />
redesigning database /application<br />
required<br />
Database will be less than <strong>10</strong>0<br />
Mbytes. The database is <strong>to</strong> be<br />
redesigned for better user<br />
friendliness and <strong>to</strong> integrate<br />
with IMS for use in DSS<br />
130<br />
111 1.2 Annexure-I<br />
Portal should have the capability<br />
<strong>to</strong> connect/integrate with the<br />
legacy systems/ databases/<br />
applications in the department.<br />
Please provide the number <strong>of</strong> legacy<br />
systems that need <strong>to</strong> be integrated,<br />
technologies used for development,<br />
database types size <strong>of</strong> the data that will<br />
need <strong>to</strong> be exchanged between the portal<br />
and the legacy systems<br />
SDRN and Geospatial database<br />
for pipelines etc. are the only<br />
legacy systems. Details <strong>of</strong> both<br />
are provided in the <strong>RFP</strong>.
131<br />
132<br />
133<br />
134<br />
111 1.2 Annexure-I<br />
119 1.1-1.15 Annexure-III<br />
119 1.2-1.1 Annexure-III<br />
119 1.2-1.2 Annexure-III<br />
All information and services<br />
being published on portal must<br />
manda<strong>to</strong>rily have metadata for<br />
effective search.<br />
The systems should Provide<br />
federated search capabilities <strong>to</strong><br />
enable property-based and fulltext<br />
queries against multiple<br />
reposi<strong>to</strong>ries, returning an<br />
aggregated result set.<br />
The IMS should facilitate sharing<br />
<strong>of</strong> visual and textual information<br />
on various aspects <strong>of</strong> a disaster<br />
<strong>to</strong> decision makers working at<br />
<strong>State</strong>, District and disaster sites.<br />
The system should support up <strong>to</strong><br />
<strong>10</strong>0 concurrent users and 700<br />
<strong>to</strong>tal users.<br />
It should provide all necessary<br />
components for a<br />
comprehensive disaster &<br />
emergency management<br />
solution including:<br />
Alert and warning <strong>No</strong>tification,<br />
Crisis Information Management,<br />
Calls and message Dispatch<br />
System,<br />
GIS, Map Data, Collaboration<br />
Framework,<br />
Unified Communication for<br />
Planning, Dynamic Incident &<br />
Asset Management and<br />
Recovery Services.<br />
We are assuming that GSDMA will be<br />
providing the metadata for all the<br />
information and services coming from the<br />
existing and legacy systems. Moreover for<br />
the new information which will be coming<br />
GSDMA has in place metadata system<br />
Please provide how many reposi<strong>to</strong>ries and<br />
what types <strong>of</strong> reposi<strong>to</strong>ries will be used<br />
(that is flat files or databases<br />
Please provide the maximum number <strong>of</strong><br />
concurrent users and maximum number <strong>of</strong><br />
<strong>to</strong>tal users. This will help us in<br />
recommending hardware and<br />
infrastructure requirements for deploying<br />
the solution.<br />
What kind <strong>of</strong> alert and warning<br />
notification is expected? We are assuming<br />
that the system will trigger alert and<br />
warning system as mentioned in point 1.6<br />
<strong>of</strong> Annexure III section 1.2 is our<br />
understanding correct?<br />
Please elaborate what is meant by<br />
collaboration framework, unified<br />
communication for planning<br />
Confirmed.<br />
Number <strong>of</strong> reposi<strong>to</strong>ries can be<br />
in the range <strong>of</strong> 20 which will<br />
include both flat files and<br />
databases<br />
Information is provided in the<br />
<strong>RFP</strong><br />
Alert and warning notifications<br />
will include :<br />
1) SMS and voice mails <strong>to</strong><br />
responsible government <strong>of</strong>ficers<br />
/ agencies<br />
2) Generation <strong>of</strong> Audio warning<br />
messages for delivery via<br />
remote warning <strong>to</strong>wers. Towers<br />
will have built in siren which<br />
sounds prior <strong>to</strong> audio message<br />
<strong>to</strong> draw attention <strong>of</strong> people.<br />
3) Collaboration framework is<br />
for communication / interaction<br />
for effective coordination<br />
between responsible<br />
government agencies
135<br />
136<br />
137<br />
138<br />
139<br />
120 1.2-1.<strong>10</strong> Annexure-III<br />
121 1.2-1.13 Annexure-III<br />
121 1.2-1.13 Annexure-III<br />
121 1.2-1.14 Annexure-III<br />
121 1.2-1.15 Annexure-III<br />
It should be possible <strong>to</strong> index<br />
unstructured content, such as<br />
radio, telephony, images, video,<br />
documents, using relevant<br />
metadata, including geospatial<br />
attributes<br />
The system should preferably<br />
have ability <strong>to</strong> generate alert(s)<br />
from data received on disaster<br />
related parameters, based on<br />
defined pre-conditions.<br />
The system should allow users<br />
<strong>to</strong>:<br />
Open and enter data in a form<br />
directly from the map & display<br />
these records as icons on the<br />
map.<br />
The system should provide<br />
scalability features and support<br />
`load balancing, high availability<br />
& disaster recovery. It should<br />
allow up-<strong>to</strong> <strong>10</strong>0 concurrent<br />
users performing queries and 50<br />
concurrent updaters<br />
The system should facilitate:<br />
Upload / download any type <strong>of</strong><br />
files<br />
As per our understanding the<br />
unstructured content such as radio,<br />
telephony images, videos documents will<br />
have the metadata which would be s<strong>to</strong>red<br />
in Database with a primary key. This<br />
primary key will be used <strong>to</strong> link the<br />
unstructured content with the geospatial<br />
attributes and other data used by the<br />
application.<br />
Kindly elaborate and clarify.<br />
What kinds <strong>of</strong> alerts are expected? What<br />
would be the frequency <strong>of</strong> data updates<br />
received from field? Please provide a<br />
sample conditions along with sample data<br />
<strong>to</strong> better understand the requirement.<br />
Please elaborate.<br />
Please provide the maximum number <strong>of</strong><br />
concurrent users and maximum number <strong>of</strong><br />
<strong>to</strong>tal users for performing queries and<br />
updates. This will help us in<br />
recommending hardware and<br />
infrastructure requirements for deploying<br />
the solution.<br />
Please provide a list <strong>of</strong> expected file<br />
formats that need <strong>to</strong> be uploaded<br />
Assumptions are correct.<br />
Information is already provided<br />
in response <strong>to</strong> similar query. The<br />
bidder is expected <strong>to</strong> have<br />
previous experience <strong>of</strong> design<br />
and operation <strong>of</strong> similar<br />
systems.<br />
The explanation provides<br />
requirement in details. Design <strong>of</strong><br />
the appropriate system is the<br />
responsibility <strong>of</strong> the bidder.<br />
Already included in the <strong>RFP</strong>.<br />
<strong>RFP</strong> mentions any type <strong>of</strong> file.<br />
140<br />
120<br />
1.2/ Sr.<br />
<strong>No</strong>./ 1.3<br />
Relevant geospatial data using<br />
GIS layers <strong>to</strong> indicate location <strong>of</strong><br />
the event, with his<strong>to</strong>rical<br />
context<br />
Kindly provide the source dataset <strong>to</strong> be<br />
integrated for his<strong>to</strong>rical context.<br />
Also provide the available format for the<br />
his<strong>to</strong>rical data.<br />
Information on SDRN and<br />
Geospatial data base is included<br />
in the <strong>RFP</strong>
141<br />
142<br />
143<br />
121<br />
120<br />
1.2/ Sr.<br />
<strong>No</strong>./ 1.13<br />
1.2/ Sr.<br />
<strong>No</strong>./ 1.8<br />
The system should allow users<br />
<strong>to</strong>:<br />
• Open and enter data in a form<br />
directly from the map & display<br />
these records as icons on the<br />
map.<br />
• Display documents & files on<br />
the map<br />
• Define map symbols as well as<br />
use existing map symbol<br />
libraries<br />
• Draw lines and polygons on<br />
map <strong>to</strong> s<strong>to</strong>re and share with<br />
other authorities responsible for<br />
disaster response.<br />
The geospatial display must<br />
show the area affected<br />
(indicating the specific and<br />
surrounding affected areas and<br />
links <strong>to</strong> all the spatial and other<br />
relevant data associated with<br />
the area). The system should<br />
have capability <strong>to</strong> superimpose<br />
dynamic status information<br />
received from sources at<br />
disaster sites or other agencies<br />
<strong>to</strong> have clear picture <strong>of</strong> available<br />
resources including state <strong>of</strong><br />
roads for travel etc. The type <strong>of</strong><br />
event (classification by type,<br />
magnitude and severity), Status<br />
<strong>of</strong> critical infrastructure<br />
catalogued in the system<br />
General<br />
Does the user require data editing feature<br />
on Web? If yes, then, What is the no. <strong>of</strong><br />
concurrent GIS users need facility for<br />
editing the spatial and attribute data over<br />
web browser?<br />
As per our understanding, live updates are<br />
required <strong>to</strong> be displayed in the GIS system<br />
<strong>to</strong> superimpose dynamic status<br />
information.<br />
Kindly provide details as <strong>to</strong> who will be<br />
responsible for providing the live updates<br />
and in what format the information needs<br />
<strong>to</strong> be integrated in the GIS.<br />
Please clarify.<br />
Is there any preference for selection <strong>of</strong><br />
Open Source GIS program/ S<strong>of</strong>tware<br />
programs? If yes, then which ones?<br />
Yes. <strong>RFP</strong> mentions on that.<br />
Live updates will be received<br />
from government staff<br />
responsible for DM activities at<br />
disaster sites as well as other<br />
EOCs. Information will be in e-<br />
mail formats, textual reports<br />
and video files<br />
<strong>No</strong>.
144<br />
145<br />
146<br />
147<br />
148<br />
149<br />
150<br />
1.5<br />
1.5 Portable VSAT<br />
system<br />
Voice Gateways<br />
Telephony - EPABX<br />
VOIP Server<br />
Telephony - EPABX<br />
Call Center<br />
General<br />
A telescopic mast <strong>to</strong> mount<br />
wireless network antenna and<br />
electrical hoisting mechanism<br />
for the mast should be provided<br />
with the system.<br />
At which locations gateways (with<br />
multiple communication links/channels) <strong>to</strong><br />
be installed or how many gateways (with<br />
multiple communication links/channels)<br />
will be in all communication network?<br />
How many ports /channels <strong>of</strong><br />
PRIs/Analog(PSTN)<br />
Trunks/Radio(UHF,VHF)/GSM/VSAT<br />
systems <strong>to</strong> be integrated at each<br />
locations?<br />
Which type <strong>of</strong> data integration or<br />
application is <strong>to</strong> be integrate with VOIP<br />
Communication server?<br />
Please specify the number <strong>of</strong> DEOCs and<br />
TEOCs with gateways and type <strong>of</strong><br />
connectivity?<br />
IVR –Describe level <strong>of</strong> IVR. If any database<br />
integration required? If yes, please<br />
provide the type <strong>of</strong> DB.<br />
Headsets for the agents <strong>to</strong> be consider? If<br />
Yes, then Please specify?<br />
As bidders need <strong>to</strong> undertake detailed<br />
survey before submission <strong>of</strong> this<br />
exhaustive integrated solution, We would<br />
request extension <strong>to</strong> bid submission date<br />
by at least one month.<br />
What should be the height <strong>of</strong> telescopic<br />
mast with portable VSAT system <strong>to</strong> install<br />
the Wireless antenna?<br />
Voice gateway is <strong>to</strong> be installed<br />
at SEOC for MPLS VPN / Internet<br />
based VoIP calls. Gateway for<br />
VSAT based voice switching is <strong>to</strong><br />
be collocated with Hub at SEOC.<br />
Required information is already<br />
provided in the <strong>RFP</strong>.<br />
There is no specification for data<br />
integration with VoIP server.<br />
The server is expected <strong>to</strong><br />
interconnect all registered VoIP<br />
phones as per dialing<br />
information.<br />
<strong>No</strong> gateways are specified at<br />
DEOC and TEOC<br />
<strong>No</strong> data base integration is<br />
required. IVR data is <strong>to</strong> be<br />
upgraded by call centre staff <strong>to</strong><br />
provided latest status <strong>of</strong><br />
disasters.<br />
The date <strong>of</strong> submission <strong>of</strong> bid<br />
has been extended <strong>to</strong><br />
September 23, <strong>2013</strong> as per<br />
corrigendum 2<br />
5.0 Meters
151<br />
152<br />
153<br />
154<br />
2.2<br />
2.2<br />
2.1<br />
19<br />
2.2 Connectivity<br />
and<br />
Internetworking<br />
requirements<br />
2.2 Connectivity<br />
and<br />
Internetworking<br />
requirements<br />
2.14 Quality <strong>of</strong><br />
Service<br />
Pg. <strong>No</strong>. 19 / 1.2.9 /<br />
c<br />
The connectivity on MPLS-VPN<br />
between SEOC and DEOCs will<br />
be at 1 Mbps rate and between<br />
District and TEOC will be at 128<br />
Kbps rates.<br />
Connectivity between SEOC,<br />
DEOC, ERC, DMI, and disaster<br />
location(s) using VSAT network<br />
at nominal 512 Kbps rates that is<br />
upgradable <strong>to</strong> 1.0 Mbps from<br />
affected districts EOCs and ERVs<br />
Bit Error Rate (BER): Better than<br />
<strong>10</strong>e-6<br />
End <strong>to</strong> end delay: ≤ 700<br />
milliseconds<br />
Connectivity with:<br />
• <strong>State</strong> Operation Centre<br />
(“SOC”); Central node <strong>of</strong> <strong>Gujarat</strong><br />
<strong>State</strong> Wide Area Network<br />
(“GSWAN”), Gandhinagar (1);<br />
• DEOCs (27);<br />
• ERCs (5);<br />
• TEOCs (29);<br />
• Portable VSAT systems (<strong>10</strong>);<br />
• Emergency Response Vehicles<br />
(6).<br />
What should be assumed as the<br />
concurrency for the backhauling <strong>of</strong> all<br />
DEOC B/W <strong>to</strong> SEOC and for backhauling all<br />
TEOC B/W <strong>to</strong> DEOC?<br />
What is the uplink and downlink B/W<br />
requirement at each SEOC, DEOC, ERC,<br />
DMI and ERV?<br />
It is unders<strong>to</strong>od that shared bandwidth is<br />
required, what shall be minimum<br />
bandwidth <strong>to</strong> be catered for bidding<br />
purpose<br />
It is suggested <strong>to</strong> have BER <strong>of</strong> <strong>10</strong>e-4 or<br />
better for voice, VC and Data.<br />
Also suggested <strong>to</strong> have end <strong>to</strong> end delay<br />
(latency) <strong>to</strong> be ≤ 2000 milliseconds since<br />
VSAT network is involved.<br />
We understand 26 DEOC’s are required as<br />
per the list provided in Schedule XIV,<br />
There is a contradiction in the clauses<br />
mentioned.<br />
Please confirm the exact numbers <strong>of</strong><br />
DEOC’s <strong>to</strong> be considered for the bid.<br />
Opera<strong>to</strong>r has <strong>to</strong> provide<br />
bandwidth as described in the<br />
<strong>RFP</strong>. This requirement is worked<br />
out after considering concurrent<br />
user requirements.<br />
Up link from SEOC will be at 5.0<br />
Mbps and up links from remotes<br />
will be at 512 Kbps. Bandwidth<br />
will be directly leased by<br />
GSDMA from Antrix and bidder<br />
has no responsibility <strong>to</strong> provide<br />
satellite bandwidth.<br />
<strong>No</strong> change in specifications<br />
Please refer <strong>to</strong> revised <strong>RFP</strong>.
155<br />
94<br />
Pg. <strong>No</strong>. 94 /<br />
Schedule II / 2.6 /<br />
b<br />
The GSDR-ICTS is proposed <strong>to</strong> be<br />
a very reliable, wide area<br />
complex converged (voice, video<br />
and data) network system using<br />
multiple technologies<br />
(technology redundancies). An<br />
extremely reliable, flexible,<br />
secure, scalable, and portable<br />
(terrestrial / satellite) GSDR-ICTS<br />
network will cover:<br />
a. The <strong>State</strong> EOC (SEOC),<br />
b. DEOCs, (26)<br />
c. ERCs, (5)<br />
d. Portable VSATs (<strong>10</strong>)<br />
e. ERVs, (6)<br />
f. ESFs at <strong>State</strong> Head quarters,<br />
(14)<br />
g. ESFs at District Head quarters,<br />
h. TEOCs (29),<br />
i. Alert and Warning <strong>to</strong>wers (21),<br />
j. The National EOC (NEOC) and<br />
national level ESF (14) agencies<br />
using NIC network<br />
(responsibility <strong>of</strong> National<br />
Informatics Centre- NIC). The<br />
bidder will have <strong>to</strong> integrate<br />
with other networks within<br />
limits <strong>of</strong> Government<br />
regulations.<br />
There are a <strong>to</strong>tal <strong>of</strong> 26 DEOCs.<br />
Please refer pg 264 <strong>of</strong> existing<br />
<strong>RFP</strong> for details <strong>of</strong> DEOCs
156<br />
20<br />
Pg. <strong>No</strong>. 20 / 1.2.9 /<br />
c<br />
Connectivity with:<br />
• <strong>State</strong> Operation Centre<br />
(“SOC”); Central node <strong>of</strong> <strong>Gujarat</strong><br />
<strong>State</strong> Wide Area Network<br />
(“GSWAN”), Gandhinagar (1);<br />
• DEOCs (27);<br />
• ERCs (5);<br />
• TEOCs (29);<br />
• Portable VSAT systems (<strong>10</strong>);<br />
• Emergency Response Vehicles<br />
(6).<br />
We understand 29 TEOC’s are required as<br />
per the list provided in Schedule XIV,<br />
There is a contradiction in the clauses<br />
mentioned.<br />
Please confirm the exact numbers <strong>of</strong><br />
TEOC’s <strong>to</strong> be considered for the bid.<br />
29 TEOCs in <strong>to</strong>tal. Please refer<br />
corrigendum 2 for the list <strong>of</strong><br />
TEOCs
157<br />
94<br />
Pg. <strong>No</strong>. 94 /<br />
Schedule II / 2.6 /<br />
h<br />
The GSDR-ICTS is proposed <strong>to</strong> be<br />
a very reliable, wide area<br />
complex converged (voice, video<br />
and data) network system using<br />
multiple technologies<br />
(technology redundancies). An<br />
extremely reliable, flexible,<br />
secure, scalable, and portable<br />
(terrestrial / satellite) GSDR-ICTS<br />
network will cover:<br />
a. The <strong>State</strong> EOC (SEOC),<br />
b. DEOCs, (26)<br />
c. ERCs, (5)<br />
d. Portable VSATs (<strong>10</strong>)<br />
e. ERVs, (6)<br />
f. ESFs at <strong>State</strong> Head quarters,<br />
(14)<br />
g. ESFs at District Head quarters,<br />
h. TEOCs (29),<br />
i. Alert and Warning <strong>to</strong>wers (21),<br />
j. The National EOC (NEOC) and<br />
national level ESF (14) agencies<br />
using NIC network<br />
(responsibility <strong>of</strong> National<br />
Informatics Centre- NIC). The<br />
bidder will have <strong>to</strong> integrate<br />
with other networks within<br />
limits <strong>of</strong> Government<br />
regulations.<br />
29 TEOCs in <strong>to</strong>tal. Please refer<br />
corrigendum 2 for the list <strong>of</strong><br />
TEOCs
158<br />
255<br />
Pg. <strong>No</strong>. 255 /<br />
SCHEDULE XIII / 3<br />
/ a / 5<br />
5) Public Telephone links<br />
The Opera<strong>to</strong>r should ensure<br />
interconnectivity at all times<br />
(including disaster situations)<br />
between:<br />
• SEOC (1)<br />
• DEOCs (26);<br />
• ERCs (5);<br />
• TEOCs (25);<br />
• Portable VSAT systems (<strong>10</strong>);<br />
• Alert and message <strong>to</strong>wers and<br />
system <strong>to</strong> broadcast hazard<br />
warnings <strong>to</strong> public located in<br />
21villages and<br />
• Mobile Emergency Response<br />
Vehicles (“ERV”)<br />
There are a <strong>to</strong>tal <strong>of</strong> 26 DEOCs.<br />
Please refer pg 264 <strong>of</strong> existing<br />
<strong>RFP</strong> for details <strong>of</strong> DEOCs<br />
There are 29 TEOCs in <strong>to</strong>tal.<br />
Refer corrigendum 2 for details.<br />
Also refer revised <strong>RFP</strong> for details<br />
<strong>of</strong> TEOCs and DEOCs
159<br />
160<br />
161<br />
116<br />
Pg. <strong>No</strong>. 116 /<br />
SCHEDULE II / 1.8<br />
GSDR-ICTS will use VHF radio for<br />
establishing local area voice<br />
communication at the location<br />
<strong>of</strong> incident(s) in shortest time<br />
possible. The vehicle mounted<br />
VHF station will work as base<br />
station with raised antenna<br />
height at the location <strong>of</strong> incident<br />
for extending radio coverage.<br />
VHF based walkie talkie<br />
integration is planned at SEOCs<br />
and ERVs.<br />
The bidder must plan and design<br />
state-<strong>of</strong>-the-art wireless<br />
communications network which<br />
is reliable and field proven<br />
which is suitable for operations<br />
in extreme and harsh<br />
environmental conditions, on<br />
multiple frequencies and with<br />
ability <strong>to</strong> bridge for<br />
interoperable communication<br />
between various departments. 4<br />
first responders, ERVs and radio<br />
gateway at SEOC <strong>to</strong>gether will<br />
use 12 VHF frequencies in the<br />
range <strong>of</strong> 136-174 Mhz.<br />
General<br />
ERV- Telescopic Mast<br />
Please confirm the requirement <strong>of</strong> VHF<br />
communication system at SEOC / DEOC.<br />
As there is a static telephony setup<br />
proposed, what is the idea behind<br />
proposing VHF communication system at<br />
SEOC/ DEOC.<br />
Incase bidder has <strong>to</strong> propose VHF<br />
equipment’s at SEOC / DEOC, pls provide<br />
the quantities <strong>of</strong> Repeaters / Handhelds /<br />
Mobile / Static radios required.<br />
Bidder has <strong>to</strong> design state-<strong>of</strong>-the-art<br />
wireless communications network, which<br />
is possible only with digitization <strong>of</strong><br />
wireless comm. network and providing IP<br />
based critical communication system. As<br />
per the specifications it appears the<br />
standard analog system will also meet the<br />
criteria. Request clarity on the same and<br />
firm quantities <strong>of</strong> wireless equipment at<br />
DEOC / SEOC.<br />
Efficiency <strong>of</strong> the system can be increased<br />
by introducing better technology / latest<br />
products available. Can bidder optionally<br />
propose these systems as part <strong>of</strong> the<br />
proposal meeting the basic criteria <strong>of</strong> <strong>RFP</strong>?<br />
GSDMA can opt for these enhancements<br />
(if required).<br />
Pls specify the type <strong>of</strong> 40 ft Mast, is it<br />
Hydraulic / Electrical type.<br />
1) The VHF system will be used<br />
at disaster sites when the<br />
district administration staff will<br />
move <strong>to</strong> the site.<br />
2) <strong>No</strong> repeaters are essential as<br />
coverage will be limited <strong>to</strong> 5.0<br />
Kilometers<br />
3) <strong>No</strong> special consideration<br />
including cost margins in case<br />
bidder proposes "better" system<br />
Optional <strong>of</strong>fers will not be<br />
considered.<br />
Preferably electrical <strong>to</strong> minimize<br />
failures due <strong>to</strong> leakage in the<br />
hydraulic system
162<br />
163<br />
164<br />
165<br />
166<br />
167<br />
168<br />
169<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
General<br />
Pls provide contact details <strong>of</strong> SEOC for<br />
physical surveys.<br />
Is the proposed solutions / system should<br />
use the communication infra server<br />
available with the Authority.<br />
Is there any predefined communication<br />
format does exists with Authority or a<br />
specific proposal can be made.<br />
As unders<strong>to</strong>od, there can be various<br />
modes <strong>of</strong> Communication like VHF, VSAT,<br />
CDMA, GSM, and VOIP. Is it required <strong>to</strong><br />
bring all these on a common portable<br />
solution and do the s<strong>of</strong>t exchange<br />
between the various user with various<br />
communication links<br />
It is unders<strong>to</strong>od that from the RFQ that<br />
there will be various EOC under the<br />
scheme with specific role <strong>of</strong> operation.<br />
How does the EOC will have control on the<br />
ERS? Should it be connected <strong>to</strong> EOC? Is it<br />
through VSAT? Vendor can suggest<br />
alternate Technology like WiMAX or LTE.<br />
Communications link from ERVs <strong>to</strong><br />
EOCs/ERCs when GSWAN/all<br />
communication links fail, what is the<br />
alternate communication set up besides<br />
VSAT link?<br />
If in case the proposal is on wireless, is it<br />
the solution should work under one <strong>of</strong> the<br />
National Disaster frequency bands 380-<br />
400MHz, 406.1-430MHz, 440-470MHz,<br />
746-806MHz<br />
For Connectivity <strong>to</strong> the SEOC, from the<br />
local disaster area or from ERS will it be<br />
through VSAT using extended Ku Band<br />
.What is the required rate <strong>of</strong> throughput<br />
and uplink/downlink connectivity.<br />
Please refer <strong>to</strong> <strong>RFP</strong>.<br />
Yes<br />
Predefined communications<br />
format exists.<br />
The understanding is correct-<br />
VSAT connectivity is proposed.<br />
Alternate links can be<br />
established only in case other<br />
networks are operational post<br />
disaster.<br />
Only alternate link will be<br />
satellite phones or BGAN , which<br />
are <strong>to</strong> be provided by GSDMA<br />
<strong>No</strong>. The proposed band is<br />
standard band used by Police<br />
etc. 134-175 MHz<br />
Please refer <strong>to</strong> <strong>RFP</strong>. (512 Kbps<br />
up link from disaster site and up<br />
<strong>to</strong> 5.0 Mbps link from SEOC.
170<br />
171<br />
172<br />
173<br />
174<br />
General<br />
General<br />
General<br />
General<br />
2.5 Antenna system for ERVs<br />
should :<br />
• <strong>No</strong>t weight more than 80<br />
Kilograms including Ku Feed<br />
Controller<br />
The ERVs will have its own portable<br />
collapsible mast integrated in<strong>to</strong> the<br />
vehicle. What should be the main distance<br />
<strong>of</strong> communication the ERVs should<br />
establish with LOS and <strong>NO</strong>N LOS <strong>to</strong> cover<br />
the disaster area.<br />
As per <strong>RFP</strong> there is interoperability <strong>of</strong><br />
various communication devices, what kind<br />
<strong>of</strong> application logic should be adopted and<br />
who will give the guide lines for this<br />
application (SRS)<br />
Who will provide input data <strong>of</strong> source?<br />
What kind <strong>of</strong> format <strong>of</strong> data is available<br />
<strong>to</strong> be integrated in<strong>to</strong> s<strong>of</strong>tware logic and<br />
what kind <strong>of</strong> redundancy the s<strong>of</strong>tware<br />
should be provided, does the application<br />
s<strong>of</strong>tware should provide the infrastructure<br />
available like hospital, Ambulances, Doc<strong>to</strong>r<br />
etc near <strong>to</strong> disaster area.<br />
This may be please change <strong>to</strong>: Antenna<br />
system for ERVs should not weight more<br />
than 80 ± 5 Kilograms including Ku Feed<br />
Controller<br />
Area covering up <strong>to</strong> 5.0<br />
Kilometer radius. <strong>No</strong>n Los<br />
connectivity is not expected.<br />
Standard systems are available<br />
for interoperability between<br />
different communication<br />
systems. Please refer <strong>to</strong> OEM<br />
literature.<br />
Refer <strong>RFP</strong> which clearly define<br />
the scope <strong>of</strong> work for opera<strong>to</strong>r.<br />
SDRN and Geospatial database<br />
for pipelines etc. is available.<br />
Details <strong>of</strong> both are provided in<br />
the <strong>RFP</strong>. Question <strong>of</strong><br />
redundancy is left <strong>to</strong> the<br />
opera<strong>to</strong>r. Details <strong>of</strong><br />
infrastructure are already<br />
included in SDRN data base.<br />
Changed <strong>to</strong> "<strong>No</strong>minal weight <strong>of</strong><br />
antenna may be less than <strong>10</strong>0.0<br />
Kegs. Opera<strong>to</strong>r is responsible for<br />
proper installation <strong>of</strong> antenna<br />
system on ERV ro<strong>of</strong><strong>to</strong>p with<br />
necessary structural<br />
fortifications"
175<br />
Specifications PLL LNB:<br />
RF input Frequency Range:<br />
<strong>10</strong>.95 <strong>to</strong> 12.75 GHz<br />
There is no existing high stability LNB for<br />
the HUB which covers RX complete range:<br />
<strong>10</strong>-95-12.75GHz. One <strong>of</strong> the Sub bands<br />
needs <strong>to</strong> be define:<br />
a) <strong>10</strong>-95 - 11.7GHz<br />
b) 11.7 – 12.2 GHz<br />
c) 12.2 – 12.75 GHz<br />
LNBs are available that can<br />
cover whole band. However<br />
opera<strong>to</strong>r may choose <strong>to</strong> opt for<br />
limited band capability with<br />
provision <strong>to</strong> change LNBs in case<br />
satellite spectrum is in<br />
difffferent band. This is essential<br />
<strong>to</strong> ensure continuity <strong>of</strong> services<br />
during whole life span (at least<br />
<strong>10</strong> years) even if a satellite<br />
operating in different frequency<br />
band is allotted <strong>to</strong> GSDMA.<br />
176<br />
Specifications - 4 W BUC<br />
Output Freq Range: 13.75 –<br />
14.50 GHz<br />
Input Freq 950 – 1450 MHz<br />
The input freq range corresponds <strong>to</strong> 500<br />
MHz <strong>of</strong> BW so Output freq. range may be<br />
please change <strong>to</strong> 13.75 – 14.25 GHz and<br />
14.0 – 14.5 GHz<br />
Correction will be issued <strong>to</strong><br />
extend IF range from 950 <strong>to</strong><br />
2150 MHz<br />
177<br />
Specifications - 25 W BUC<br />
Output Freq Range: 13.75 –<br />
14.50 GHz<br />
Input Freq 950 – 1450 MHz<br />
The input freq range corresponds <strong>to</strong> 500<br />
MHz <strong>of</strong> BW so Output freq. range may be<br />
please change <strong>to</strong> 13.75 – 14.25 GHz and<br />
14.0 – 14.5 GHz<br />
Correction will be issued <strong>to</strong><br />
extend IF range from 950 <strong>to</strong><br />
2150 MHz<br />
178<br />
Environmental Specifications<br />
• Operational Temperature<br />
• Operational within tracking<br />
accuracy for Wind speeds<br />
• The operational temperature range<br />
asked is <strong>to</strong>o low. The Antenna comes with<br />
a special low temperature kit <strong>to</strong> support<br />
up <strong>to</strong> -30º C.<br />
• The operational wind speed within<br />
tracking accuracy may please change <strong>to</strong> –<br />
up <strong>to</strong> 95 Km/h.<br />
Both suggestions are accepted.<br />
Correction will be issued in <strong>RFP</strong>.
179<br />
180<br />
• Specification <strong>of</strong> chassis: To<br />
provide minimum operational<br />
area 5 meters long and 2.4<br />
Meter wide , diesel vehicle<br />
chassis, or cus<strong>to</strong>m trailer<br />
• "Dimensions (within +/- <strong>10</strong>% )"<br />
:Overall dimensions 7500mm X<br />
2500 mm or more<br />
• "Command Center operations<br />
area" :5000 X 2400 X 1800 mm.<br />
• "Minimum Ground: clearance"<br />
:350 mm<br />
The mentioned specifications <strong>of</strong> ERV are<br />
complied with only Defense Category<br />
Vehicle, which are not available for civilian<br />
purposes. <strong>No</strong>ne <strong>of</strong> the Commercially<br />
Available vehicle meets the specs. This<br />
may be please modifying the<br />
specifications <strong>to</strong> allow civilian vehicle <strong>to</strong><br />
be complied. Egg. Swaraj Mazda.<br />
1. Please clarify that “How<br />
communication between first responders<br />
such as police, disaster rescue forces, fire<br />
brigades that use wireless communication<br />
systems mostly equipment operating in<br />
Very High Frequency (“VHF”) band and<br />
administra<strong>to</strong>rs on terrestrial or satellite<br />
based Very Small Aperture Terminals<br />
(“VSAT”), should be possible with Voice<br />
over Internet Pro<strong>to</strong>col (“VoIP”) based<br />
unified communication system.”<br />
<strong>No</strong> change. GSDMA will provide<br />
end user certificate if necessary<br />
<strong>to</strong> procure defence qualified<br />
vehicle<br />
Any standard Universal<br />
Communications System will<br />
satisfy requirements. Please<br />
refer <strong>to</strong> OEM literature.
181<br />
182<br />
183 Page<br />
92<br />
184 Page<br />
92<br />
Section<br />
2.2:-<br />
Connecti<br />
vity and<br />
Internet<br />
working<br />
requirem<br />
ents<br />
Section<br />
2.3 :-<br />
Core<br />
Service<br />
Require<br />
ments<br />
Schedule II -<br />
GSDR-ICTS<br />
Technical<br />
Requirements<br />
Schedule II -<br />
GSDR-ICTS<br />
Technical<br />
Requirements<br />
Establish LAN at ERC and<br />
disaster location using wired or<br />
wireless medium<br />
Video / data analysis<br />
2. UNIVERSAL INTERFACE SYSTEEM (UIS)<br />
a) Will any other device other than<br />
Universal communication Interface be<br />
connected with the VSAT IDU (modem)<br />
over L AN (RJ 45) ports (i.e. IP interface)?<br />
Please confirm.<br />
b) Does UIS support SIP signaling for VoIP?<br />
[As UIS will convert wireless<br />
communication <strong>to</strong> Internet Pro<strong>to</strong>col (IP)<br />
format and VoIP Gateway will be installed<br />
at the SEOC, which means it supports SIP<br />
Signaling for VoIP] Please confirm?<br />
c) Will this box be connecting <strong>to</strong> VSAT<br />
Modem over LAN (RJ45) port for the<br />
communication between ERVs & SEOC on<br />
IP pro<strong>to</strong>col?<br />
d) Provide the specifications/capability<br />
details <strong>of</strong> this Universal Interface System.<br />
e) Schematic Diagram <strong>of</strong> Universal<br />
Interface system showing the traffic flow<br />
<strong>of</strong> VHF system and VSAT system.<br />
3. What should be the height <strong>of</strong> telescopic<br />
mast with portable VSAT system <strong>to</strong> install<br />
the Wireless antenna?<br />
Q: Do the Opera<strong>to</strong>r need <strong>to</strong> setup<br />
dynamically the fixed EOC at disaster<br />
location on demand in addition <strong>to</strong> the ERV<br />
set up at disaster locations? Please clarify<br />
with more details.<br />
Q: Need more details on Video / Data<br />
Analysis requirements.<br />
a) One more LAN port for<br />
videoconferencing, voice<br />
communication, data<br />
communication etc. is<br />
necessary,<br />
b) Yes<br />
c) Yes<br />
d) Please refer <strong>to</strong> page 259<br />
e) UIS is a standard solution<br />
available from many OEMs,<br />
hence this information is not<br />
included in the <strong>RFP</strong><br />
Around 5.0 Meters (16 feet) for<br />
coverage area <strong>of</strong> 2.0 KM radius<br />
<strong>No</strong>. ERV specifications only are<br />
<strong>to</strong> be satisfied.<br />
Video and data analysis is <strong>to</strong><br />
support decision making by<br />
updated status <strong>of</strong> disaster<br />
incidence.
185 Page<br />
94<br />
186 Page:<br />
<strong>10</strong>9<br />
187 Page:<br />
<strong>10</strong>9<br />
Section<br />
2.6 :-<br />
GSDR-<br />
ICTS<br />
Design<br />
Criteria<br />
Section<br />
1.4 :-<br />
District<br />
EOC<br />
Section<br />
1.4<br />
District<br />
EOC<br />
Schedule II -<br />
GSDR-ICTS<br />
Technical<br />
Requirements<br />
Annex I –<br />
Technical<br />
requirements at<br />
Emergency<br />
Operation Centers<br />
Facilities<br />
Annex I –<br />
Technical<br />
requirements at<br />
Emergency<br />
Operation Centers<br />
Facilities<br />
ESFs at <strong>State</strong> Head quarters, (14)<br />
All important Government<br />
<strong>of</strong>fices and other agencies<br />
including district level <strong>of</strong>fices<br />
<strong>of</strong> identified<br />
emergency support function<br />
agencies <strong>of</strong>fices will be<br />
connected <strong>to</strong> DEOC either on<br />
GSWAN<br />
backbone or through broadband<br />
internet connectivity.<br />
Limited call / dispatch<br />
management facility should be<br />
set-up <strong>to</strong> take over the<br />
responsibility from SEOC R <strong>to</strong><br />
DEOC (in case disaster occurs in<br />
the concerned district) during<br />
emergency situation for<br />
effective management <strong>of</strong> call<br />
handling.”<br />
Q: how much number <strong>of</strong> ESFs at District<br />
Head Quarter (DHQ) level <strong>to</strong> be connected<br />
<strong>to</strong> GSDR-ICTS?<br />
Q: Need <strong>to</strong> know the number <strong>of</strong><br />
Government <strong>of</strong>fices <strong>to</strong> be connected with<br />
DEOC?<br />
Do GSDMA will take care <strong>of</strong> this<br />
connectivity or Opera<strong>to</strong>r need <strong>to</strong> do this<br />
connectivity?<br />
Q: How many number <strong>of</strong> VoIP phone<br />
connectivity is required at DEOC?<br />
Total 14 at DHQ. However<br />
connectivity will be via GSWAN<br />
and other resources<br />
GSDMA will ensure connectivity<br />
via GSWAN or PSTN or Internet<br />
Two units will suffice.
188 Page:<br />
<strong>10</strong>9<br />
Section<br />
1.6<br />
District<br />
EOC<br />
Annex I –<br />
Technical<br />
requirements at<br />
Emergency<br />
Operation Centers<br />
Facilities<br />
1. TEOC would be interfaced<br />
with Existing GSWAN Network<br />
node at TEOC.<br />
2. Selected TEOC sites will be<br />
connected with respective<br />
DEOC using MPLS-VPN leased<br />
from licensed telecom service<br />
opera<strong>to</strong>r. MPLS-VPN is required<br />
where GSWAN connectivity<br />
doesn't exist. Such locations<br />
would not be more than 20 and<br />
the connectivity is required at<br />
128 KBPS<br />
3. Broadband connectivity<br />
subscribed from the service<br />
provider in the area as a<br />
redundant measure for data<br />
communication with the rest <strong>of</strong><br />
GSDR-ICTS network through a<br />
VPN.<br />
4. TEOC will utilize PSTN<br />
whenever it is available for<br />
communication with other<br />
GSDR-ICTS network<br />
<strong>No</strong>des<br />
Q: How many number <strong>of</strong> VoIP phone<br />
connectivity is required at TEOC?<br />
Two units will suffice.
189 Page:<br />
120<br />
Section<br />
1.2<br />
Technical<br />
Specificat<br />
ions for<br />
Incident<br />
Manage<br />
ment<br />
Applicati<br />
on<br />
Operatio<br />
nal<br />
Require<br />
ments<br />
for<br />
Incident<br />
Manage<br />
ment<br />
System<br />
(IMS)<br />
Annexure III -<br />
Detailed technical<br />
specifications <strong>of</strong><br />
important subsystems<br />
1.3)Relevant geospatial data<br />
using GIS layers <strong>to</strong> indicate<br />
location <strong>of</strong> the event, with<br />
his<strong>to</strong>rical context (whether<br />
similar event has occurred in the<br />
past at the place or nearby<br />
areas)<br />
Q: Need <strong>to</strong> know more details about<br />
His<strong>to</strong>rical Context/data <strong>to</strong> integrate with<br />
IMA.Will the his<strong>to</strong>rical context/data<br />
available from SDC server?<br />
Existing his<strong>to</strong>rical GIS layers if<br />
any will be available from<br />
GSDMA. Opera<strong>to</strong>r has <strong>to</strong> archive<br />
all future incidences in<strong>to</strong><br />
his<strong>to</strong>rical data base.
190 Page<br />
121<br />
Section<br />
1.2<br />
Technical<br />
Specificat<br />
ions for<br />
Incident<br />
Manage<br />
ment<br />
Applicati<br />
on<br />
Operatio<br />
nal<br />
Require<br />
ments<br />
for<br />
Incident<br />
Manage<br />
ment<br />
System<br />
(IMS)<br />
Annexure III -<br />
Detailed technical<br />
specifications <strong>of</strong><br />
important subsystems<br />
1.17) The system should support<br />
- All Vendors should ensure that<br />
proposed GIS platform (s)<br />
comply <strong>to</strong> OGC standards such<br />
as WMS, WPS, WFS, WCS etc.”<br />
Q: Opera<strong>to</strong>r need <strong>to</strong> integrate the existing<br />
GIS system with proposed IMA or need <strong>to</strong><br />
modify the existing GIS System? Need<br />
more details on the scope work with<br />
respect <strong>to</strong> GIS platform integration with<br />
IMA?<br />
Existing GIS system is either<br />
based on ESRI or open<br />
standards. Opera<strong>to</strong>r has <strong>to</strong><br />
integrate the data in<strong>to</strong> his<br />
system.
191 Page<br />
121<br />
192 Page<br />
136<br />
Section<br />
1.2<br />
Technical<br />
Specificat<br />
ions for<br />
Incident<br />
Manage<br />
ment<br />
Applicati<br />
on<br />
Operatio<br />
nal<br />
Require<br />
ments<br />
for<br />
Incident<br />
Manage<br />
ment<br />
System<br />
(IMS)<br />
Section<br />
1.5 Alert/<br />
Warning<br />
Announc<br />
ement<br />
System<br />
Annexure III -<br />
Detailed technical<br />
specifications <strong>of</strong><br />
important subsystems<br />
Annexure III -<br />
Detailed technical<br />
specifications <strong>of</strong><br />
important subsystems<br />
1.16) The system should have<br />
capabilities <strong>of</strong> creating the alert<br />
content for disseminating <strong>to</strong> end<br />
users. It should also generate<br />
CAP compliant warning<br />
messages for external<br />
broadcasting organizations like<br />
Radio, TV etc.<br />
Annexure III - Detailed technical<br />
specifications <strong>of</strong> important subsystems<br />
; full page<br />
Q: Need more details/list <strong>of</strong> Broadcasting<br />
organizations <strong>to</strong> be interfaced <strong>to</strong><br />
broadcast CAP alert messages.<br />
Q: Is there any real time processed data<br />
coming from other ESFs (Seismic, Chemical<br />
leak warning, etc) need <strong>to</strong> be processed<br />
for generating alert warning command?<br />
Please provide more details.<br />
Please assume up <strong>to</strong> <strong>10</strong> each<br />
broadcasting organizations <strong>of</strong><br />
radio and TV. List is not essential<br />
<strong>to</strong> design the system.<br />
Data may come real time/ quasi<br />
real-time and alerts will be<br />
generated based on the SoP<br />
provided by GSDMA.
193 Page<br />
136<br />
Section<br />
1.5 Alert/<br />
Warning<br />
Announc<br />
ement<br />
System<br />
Annexure III -<br />
Detailed technical<br />
specifications <strong>of</strong><br />
important subsystems<br />
Operation <strong>of</strong> the system:<br />
1.4) Warning messages and<br />
Instructions pertaining <strong>to</strong><br />
specific disasters will be directly<br />
sent through appropriate<br />
medium like wireless (VHF),<br />
GSM / CDMA network or<br />
satellite media from the <strong>State</strong><br />
Emergency Operation canter<br />
(SEOC) or corresponding DEOC<br />
<strong>to</strong> audio amplifiers at warning<br />
<strong>to</strong>wers for broadcasting <strong>to</strong> local<br />
population<br />
As per Schedule II - GSDR-ICTS<br />
Technical Requirements Section<br />
2.7 High levels <strong>of</strong> Availability<br />
Connectivity matrix <strong>to</strong> provide<br />
necessary redundancy :<br />
mentioned that the Alert &<br />
warning Towers main<br />
connectivity shall be through<br />
GSM(cell phone) and the backup<br />
connectivity shall be through<br />
Satellite Phone (Satellite phone<br />
will be procured by GSDMA).<br />
Additional backup connectivity<br />
medium has not mentioned.<br />
Q: Need clarification on the Alert and<br />
Warning Tower connectivity.<br />
Does the opera<strong>to</strong>r need <strong>to</strong> consider the<br />
VHF System connectivity as back-up for<br />
Alert and Warning Tower?<br />
Bidder may design AWS <strong>to</strong><br />
satisfy specifications and<br />
reliability. Choice <strong>of</strong> technology<br />
and its cost effectiveness is left<br />
<strong>to</strong> the bidder.
194 Page<br />
84<br />
Section<br />
1.2<br />
Project<br />
Impleme<br />
ntation<br />
Schedule I A –<br />
Project<br />
Management<br />
The GSDR-ICTS Opera<strong>to</strong>r shall:<br />
The Opera<strong>to</strong>r shall obtain all<br />
necessary approvals/<br />
clearances from concerned<br />
authorities / departments, as<br />
applicable, including: 1.DoT/<br />
TEC/ TRAI/ BSNL for network<br />
installation and operations.<br />
2. From Wireless Planning<br />
Commission (WPC) wing and<br />
Standing Advisory Committee<br />
for Frequency Allocation<br />
(SACFA), as required, for use <strong>of</strong><br />
Radio/ Microwave/ Wireless<br />
links and/or any related<br />
equipment.<br />
3. From local authorities (like<br />
Municipalities, PWD, HPSEB<br />
etc.), as required, including<br />
laying their own cables, mast<br />
erection, etc.<br />
Q: Please confirm that all government<br />
approvals and clearances will be taken by<br />
GSDMA<br />
GSDMA has obtained VSAT<br />
service license and will apply for<br />
wireless radio license based on<br />
system <strong>of</strong>fered by the opera<strong>to</strong>r.<br />
However all other licenses are<br />
<strong>to</strong> be obtained by the opera<strong>to</strong>r.<br />
GSDMA will extend support in<br />
this effort.
195 Page<br />
<strong>10</strong>3<br />
Section<br />
1.3.4<br />
SEOC -<br />
Audio<br />
Visual<br />
and<br />
Miscellan<br />
eous<br />
Services<br />
Annex I –<br />
Technical<br />
requirements at<br />
Emergency<br />
Operation Centers<br />
Facilities<br />
<strong>State</strong> Emergency Operation<br />
Center building at Gandhinagar<br />
has several identified rooms/<br />
sections marked for potentially<br />
Emergency Operations<br />
management activities. Spaces<br />
equipped with AV/Multimedia<br />
systems should allow an event<br />
from one space <strong>to</strong> be distributed<br />
<strong>to</strong> another space within the<br />
facility and vice versa. As a<br />
result, one space equipped<br />
with audio and video capture<br />
components could become<br />
virtual extensions <strong>of</strong> another<br />
space throughout the facility<br />
and will allow participants <strong>to</strong><br />
partake in an event<br />
accordingly. All rooms will<br />
have ceiling or wall mounted<br />
speakers for receiving alerts<br />
and<br />
messages in addition <strong>to</strong> a video<br />
screen suitable for the size <strong>of</strong><br />
the room.<br />
Q: Please confirm if we could invite<br />
GSDMA <strong>of</strong>ficials <strong>to</strong> vendor’s project sites<br />
<strong>to</strong> demonstrate some <strong>of</strong> the implemented<br />
features listed for NCNC DEMO or,<br />
whether the location for NCNC DEMO will<br />
entirely be SEOC, Gandhinagar<br />
<strong>No</strong>, unless it is absolutely<br />
essential. Final decision on the<br />
vendor's submission on this<br />
issue will be taken by technical<br />
evaluation committee.
196 Page<br />
29<br />
Section<br />
2.2.11<br />
Eligibility<br />
<strong>of</strong><br />
Bidders<br />
INSTRUCTIONS<br />
TO BIDDERS<br />
<strong>No</strong>twithstanding anything <strong>to</strong><br />
the contrary contained herein,<br />
in the event that the Bid Due<br />
Date falls within three months<br />
<strong>of</strong> the closing <strong>of</strong> the latest<br />
financial year <strong>of</strong> a Bidder, the<br />
Bidder shall ignore such financial<br />
year for the purposes <strong>of</strong> its Bid<br />
and furnish all its information<br />
and certification with reference<br />
<strong>to</strong> the 5 (five) years or 3 (three)<br />
years or 1 (one) year, as the case<br />
may be, preceding its latest<br />
financial year. For the avoidance<br />
<strong>of</strong> doubt, financial year shall, for<br />
the<br />
purposes <strong>of</strong> Bid hereunder,<br />
mean the accounting year<br />
followed by the Bidder in the<br />
course <strong>of</strong> its<br />
normal business.<br />
It is submitted, as discussed during pre-bid<br />
conference that all Projects completed till<br />
the submission <strong>of</strong> Bid will be considered<br />
for eligibility and evaluation as long as<br />
appropriate completion document is<br />
provided.<br />
Suggestion is accepted. The<br />
completition certificate needs <strong>to</strong><br />
be provided
197 Page<br />
45<br />
Section<br />
3.3<br />
Evaluation <strong>of</strong><br />
Commercial Bids<br />
Evaluation <strong>of</strong> Commercial Bids<br />
The bidders from different states, union<br />
terri<strong>to</strong>ries, SEZs etc. will be required <strong>to</strong><br />
pay VAT applicable for their states, interstate<br />
taxes and/or Central <strong>State</strong> Tax (CST)<br />
as applicable and are going <strong>to</strong> differ from<br />
case <strong>to</strong> case. It is therefore requested that<br />
Commercial (Price) comparison be done<br />
for arriving at inter-se ranking excluding<br />
the taxes and duties so as <strong>to</strong> provide a<br />
level playing field <strong>to</strong> all bidders. The taxes<br />
paid and added <strong>to</strong> vendor’s billing in any<br />
case flow back (pass through) <strong>to</strong> the<br />
Government and hence should be<br />
excluded (Net <strong>of</strong> Taxes) for comparison for<br />
ranking. Commercial comparison will be<br />
“Net <strong>of</strong> Taxes” in order <strong>to</strong> remove<br />
disparity between tax differences between<br />
states/UT<br />
The suggestion is not accepted.<br />
Evaluation will be done only on<br />
QGR value.
198 Page<br />
201<br />
199 Page<br />
245<br />
6.7.3<br />
Evidence<br />
<strong>of</strong><br />
Insuranc<br />
e Cover<br />
Emergen<br />
cy<br />
Response<br />
Vehicle<br />
(ERV):<br />
ARTICLE VI -<br />
PROTECTION AND<br />
LIMITATIONS<br />
SCHEDULE X<br />
:SERVICE<br />
WINDOW<br />
All insurances obtained by the<br />
Opera<strong>to</strong>r in accordance with<br />
this Article 6.7 shall be<br />
maintained with insurers on<br />
terms consistent with good<br />
industry practice. Within 15<br />
(fifteen) days <strong>of</strong> obtaining any<br />
insurance cover, the Opera<strong>to</strong>r<br />
shall furnish <strong>to</strong> GSDMA,<br />
notarised true copies <strong>of</strong> the<br />
certificate(s) <strong>of</strong> insurance,<br />
copies <strong>of</strong> insurance policies and<br />
premia payment receipts in<br />
respect <strong>of</strong> such insurance, and<br />
no such insurance shall be<br />
cancelled, modified, or allowed<br />
<strong>to</strong> expire or lapse until the<br />
expiration <strong>of</strong> at least 45 (forty<br />
five) days after notice <strong>of</strong> such<br />
proposed cancellation,<br />
modification or non-renewal<br />
has been delivered by the<br />
Opera<strong>to</strong>r <strong>to</strong> GSDMA.<br />
SCHEDULE X :SERVICE WINDOW<br />
Please provide indicative asset book value<br />
<strong>of</strong> GoG property for the purpose <strong>of</strong><br />
insurance.<br />
Should the emergency response vehicle<br />
have a micro BTS with satellite backhaul<br />
for providing cellular coverage in times <strong>of</strong><br />
emergency? If yes please give detailed<br />
specifications (technology GSM, UMTS, no<br />
<strong>of</strong> users, cell range etc).<br />
Opera<strong>to</strong>r is responsible <strong>to</strong> insure<br />
equipment facilities supplied<br />
and not GoG property.<br />
The BTS is not specified for ERV.<br />
However the bidder can provide<br />
BTS based solution <strong>to</strong> provide<br />
capability for<br />
intercommunication between<br />
disaster response forces at<br />
disaster locations and decision<br />
makers at DEOC, SEOC etc.<br />
major requirement is voice and<br />
Short messaging<br />
communications as such GSM<br />
2G will suffice. Range will be 2<br />
Kilometers.
200 Page<br />
248<br />
201 Page<br />
92<br />
202 Page<br />
92<br />
203 Page<br />
97<br />
204 Page<br />
16<br />
Section<br />
3:-<br />
Detailed<br />
tests<br />
4.<br />
Systems<br />
installed<br />
in<br />
Emergen<br />
cy<br />
Response<br />
Vehicle<br />
2.1<br />
Introduct<br />
ion<br />
2.2<br />
Connecti<br />
vity and<br />
Internet<br />
working<br />
requirem<br />
ents<br />
2.7 High<br />
levels <strong>of</strong><br />
Availabili<br />
ty<br />
1.2.5<br />
<strong>State</strong><br />
EOC-<br />
Concept<br />
<strong>of</strong><br />
Operatio<br />
n<br />
SCHEDULE XI<br />
ACCEPTANCE<br />
TESTS AND<br />
PROCEDURE<br />
Schedule II -<br />
GSDR-ICTS<br />
Technical<br />
Requirements<br />
Schedule II -<br />
GSDR-ICTS<br />
Technical<br />
Requirements<br />
Schedule II -<br />
GSDR-ICTS<br />
Technical<br />
Requirements<br />
1.2 Emergency &<br />
Disaster<br />
Management<br />
(DM)<br />
Tests will be conducted <strong>to</strong><br />
check:<br />
Videoconferencing capability<br />
Universal interface<br />
VHF base station<br />
Operation <strong>of</strong> telescopic Antenna<br />
<strong>to</strong>wer<br />
Operation and rating <strong>of</strong> backup<br />
power including genera<strong>to</strong>r<br />
Operation <strong>of</strong> VSAT antenna for<br />
au<strong>to</strong> tracking and au<strong>to</strong>-locking<br />
on satellite<br />
Operation <strong>of</strong> VSAT for data,<br />
voice and video transmission<br />
6. Secure and controlled access<br />
<strong>to</strong> sensitive areas in SEOC<br />
building.<br />
High speed Internet<br />
connectivity <strong>of</strong> 8 Mbps data<br />
rate at SEOC <strong>to</strong> support<br />
Information Management<br />
Services<br />
9. <strong>No</strong>de:-Alert and Warning<br />
<strong>to</strong>wers<br />
Main Connectivity:-GSM (cell<br />
phone) Back up:-Satellite Phone<br />
The key fac<strong>to</strong>rs for success <strong>of</strong> a<br />
coordinated emergency<br />
response depends on –<br />
Redundancy, Scalability and<br />
interoperability <strong>of</strong> Information<br />
and Communication Technology<br />
(ICT) systems.<br />
Should the emergency response vehicle<br />
have a micro BTS with satellite backhaul<br />
for providing cellular coverage in times <strong>of</strong><br />
emergency. If yes please give detailed<br />
specifications (technology GSM, UMTS, no<br />
<strong>of</strong> users, cell range etc).<br />
“Secure and controlled access <strong>to</strong> sensitive<br />
areas in SEOC building” - Is access control<br />
at various EOC’s a part <strong>of</strong> the requirement.<br />
If yes please give detailed specifications<br />
“High speed Internet connectivity <strong>of</strong> 8<br />
Mbps data rate at SEOC <strong>to</strong> support<br />
Information Management Services”- Is<br />
redundant link from one more opera<strong>to</strong>r<br />
required?<br />
“Alert and Warning <strong>to</strong>wers GSM (cell<br />
phone) – Should the alert and warning<br />
<strong>to</strong>wers have Video displays which should<br />
be fed by a DTH system?<br />
Should the SEOC also be redundant?<br />
Should there be a Backup SEOC which<br />
takes over if the Main SEOC fails due <strong>to</strong><br />
various reasons?(With reference <strong>to</strong> SEOC)<br />
Backhaul for BTS via VSAT for<br />
long distance communications is<br />
essential in case this solution is<br />
<strong>of</strong>fered by the bidder. For other<br />
points please refer <strong>to</strong> response<br />
<strong>to</strong> preceding query.<br />
Yes. Standard biometric access<br />
control will meet the<br />
requirements.<br />
<strong>No</strong>.<br />
<strong>No</strong>.<br />
Redundant SEOC is not planned<br />
at the moment. However the<br />
bidder needs <strong>to</strong> propose a<br />
suitable disaster recovery site<br />
[Ref page 254 <strong>of</strong> existing <strong>RFP</strong>]
205 Page<br />
17<br />
206 Page<br />
17<br />
207 Page<br />
98<br />
208 Page<br />
255<br />
209 Page<br />
<strong>10</strong>3<br />
1.2.6<br />
Brief<br />
descripti<br />
on <strong>of</strong> the<br />
project<br />
1.2.6<br />
Brief<br />
descripti<br />
on <strong>of</strong> the<br />
project<br />
2.9<br />
Deploym<br />
ent &<br />
Response<br />
Times<br />
SCHEDUL<br />
E XII<br />
DELIVER<br />
ABLES<br />
1.3.3<br />
SEOC<br />
connecti<br />
vity and<br />
facilities<br />
1.2 Emergency &<br />
Disaster<br />
Management<br />
(DM)<br />
1.2 Emergency &<br />
Disaster<br />
Management<br />
(DM)<br />
Schedule 2<br />
SERVICE<br />
AGREEMENT<br />
Annex I –<br />
Technical<br />
requirements at<br />
Emergency<br />
Operation Centers<br />
Facilities<br />
Interaction within these<br />
Stakeholders will be via voice,<br />
data and videoconferencing and<br />
the proposed infrastructure will<br />
be useful for these activities.<br />
The IMS will also provide<br />
dynamic information on status<br />
<strong>of</strong> disaster resources, tracking <strong>of</strong><br />
personnel, equipment and<br />
systems necessary for post<br />
disaster response.<br />
Installation and commissioning<br />
<strong>of</strong> local and wide area<br />
communication using the ERV<br />
should be<br />
completed within 2 Hours <strong>of</strong><br />
reaching the destination. Bidder<br />
shall design ERV for quick<br />
transportation and deployment<br />
under all weather conditions.<br />
The design <strong>of</strong> transportable<br />
terminal should support self<br />
sustainability (including fuel for<br />
genera<strong>to</strong>r) for at least 72 hours<br />
<strong>of</strong> continuous operation.<br />
Alert and message <strong>to</strong>wers<br />
and system <strong>to</strong><br />
broadcast hazard warnings <strong>to</strong><br />
public located<br />
in 21 villages<br />
1.3.3 SEOC connectivity and<br />
facilities<br />
What is the priority <strong>of</strong> services?<br />
How is the tracking <strong>of</strong> personnel<br />
provisioned? Is it live, GPS based or is it<br />
manual update based?<br />
It is mentioned that in deployment <strong>of</strong> ERV,<br />
both local area as well as wide area<br />
communication needs <strong>to</strong> be set up at the<br />
locations <strong>of</strong> incidents. What should be the<br />
range <strong>of</strong> operation <strong>of</strong> local wireless<br />
networks?<br />
Can the Alert <strong>to</strong>wers be controlled from<br />
any DEOC or is it by the DEOC located in<br />
the same district <strong>of</strong> Alert Tower?<br />
What will be the connectivity between<br />
SEOC and NICNET/ National Network<br />
Backbone? What is the interface? What<br />
will be the link? Will this link have any<br />
redundancy?<br />
Priority is in the following order<br />
1) Voice,<br />
2) data and<br />
3) videoconferencing<br />
Personnel tracking will be done<br />
manually (persons will report<br />
their position and any changes<br />
<strong>to</strong> nearest EOC or SEOC)till GPS<br />
based location data is freely<br />
available from GSM opera<strong>to</strong>rs<br />
Local network will be up <strong>to</strong> 5.0<br />
kilometers in case <strong>of</strong> VHF radios<br />
and up <strong>to</strong> 2.0 Kilometers in<br />
cases <strong>of</strong> BTS (GSM network)<br />
By the DEOC located in the same<br />
district.<br />
IP / Ethernet. NICNET will be<br />
linked at SDC, which is already<br />
linked via redundant OFC links.<br />
National EOC / backbone will be<br />
linked via Disaster Management<br />
Support (DMS) VSAT network.<br />
<strong>No</strong>t part <strong>of</strong> opera<strong>to</strong>r's<br />
responsibility.
2<strong>10</strong> Page<br />
98<br />
211 Page<br />
16<br />
2.9<br />
Deploym<br />
ent &<br />
Response<br />
Times<br />
1.2.4<br />
Emergen<br />
cy<br />
Resource<br />
Centers<br />
(ERCs)<br />
Schedule II -<br />
GSDR-ICTS<br />
Technical<br />
Requirements<br />
SECTION – 1:<br />
Overview ; 1.2<br />
Emergency &<br />
Disaster<br />
Management<br />
(DM)<br />
Vendor will be required <strong>to</strong><br />
deploy emergency response<br />
vehicle (ERVs) and establish<br />
communication system (both<br />
local areas as well as wide area)<br />
at the locations <strong>of</strong> incidents (or<br />
as conveyed by GSDMA or its<br />
authorized <strong>of</strong>ficial from time<br />
<strong>to</strong> time). The ERV should<br />
reach the assigned location<br />
from the time orders for<br />
movement are received, within<br />
travel time calculated @ an<br />
average speed <strong>of</strong> 50 KM / Hour<br />
(e.g. within 4 hours when ERV<br />
has <strong>to</strong> travel 200 Kilometers <strong>to</strong><br />
reach disaster site). Above<br />
mentioned<br />
speed is applicable for normal<br />
and mo<strong>to</strong>r-able road conditions<br />
and time will be adjusted<br />
upwards in case<br />
<strong>of</strong> inferior road conditions.<br />
Regional ERCs have been<br />
established at strategic five<br />
locations in the state for speedy<br />
response in terms<br />
<strong>of</strong> post disaster search and<br />
rescue operations and will be<br />
well equipped with emergency<br />
resources for this<br />
purpose. ERCs will also be<br />
responsible for relief operations.<br />
Facilities will also be used as<br />
regional<br />
training centers.<br />
Whether the mobile nodes (ERV) should<br />
have communication-on-move feature?<br />
What are the five locations where ERC<br />
needs <strong>to</strong> be installed? (Refer section 1.2.4)<br />
Opera<strong>to</strong>r need not provide<br />
communications on the move.<br />
GSDMA will procure Sat-phones<br />
for use while on move for<br />
communication.<br />
ERC Locations are included in<br />
<strong>RFP</strong> / Corrigendum 2
212 Page<br />
<strong>10</strong>9<br />
213 Page<br />
116<br />
1.6<br />
Taluka<br />
EOC<br />
1.9 Alert<br />
and<br />
Warning<br />
System<br />
Annex I –<br />
Technical<br />
requirements at<br />
Emergency<br />
Operation Centers<br />
Facilities<br />
Annex II –<br />
Infrastructure and<br />
other facilities<br />
1. TEOC would be interfaced<br />
with Existing GSWAN Network<br />
node at TEOC.<br />
2.Selected TEOC sites will be<br />
connected with respective<br />
DEOC using MPLS-VPN leased<br />
from licensed telecom service<br />
opera<strong>to</strong>r. MPLS-VPN is required<br />
where GSWAN connectivity<br />
doesn't exist. Such locations<br />
would not be more than 20 and<br />
the connectivity is required at<br />
128 KBPS<br />
3.Broadband connectivity<br />
subscribed from the service<br />
provider in the area as a<br />
redundant measure for data<br />
communication with the rest <strong>of</strong><br />
GSDR-ICTS network through a<br />
VPN.<br />
4.TEOC will utilize PSTN<br />
whenever it is available for<br />
communication with other<br />
GSDR-ICTS network <strong>No</strong>des<br />
Total <strong>of</strong> 21 siren <strong>to</strong>wers will be<br />
controlled and managed by<br />
SEOC or by concerned DEOC(s)<br />
as per the list enclosed.<br />
Whether the TEOCs are having VSAT<br />
connection?<br />
Alert & warning system<br />
It is mentioned that “Total <strong>of</strong> 21 siren<br />
<strong>to</strong>wers will be controlled and managed by<br />
SEOC or by concerned DEOC(s) as per the<br />
list enclosed”;<br />
We assume that no control is needed at<br />
TEOCs & ERVs (configuration <strong>of</strong> sirens etc),<br />
but can issue alerts. Pls confirm.<br />
<strong>No</strong><br />
Confirmed.
214 Page<br />
116<br />
215 Page<br />
136<br />
216 Page<br />
<strong>10</strong>0<br />
1.9 Alert<br />
and<br />
Warning<br />
System<br />
1.5 Alert/<br />
Warning<br />
Announc<br />
ement<br />
System<br />
Annex II –<br />
Infrastructure and<br />
other facilities<br />
Annexure III -<br />
Detailed technical<br />
specifications <strong>of</strong><br />
important subsystems<br />
A strong building / or a suitable<br />
structure more than 30 feet<br />
height or a <strong>to</strong>wer/mast <strong>of</strong> 30<br />
Feet height above ground level<br />
(<strong>to</strong> be provided by the opera<strong>to</strong>r<br />
in case suitable building /<br />
structure is not available) shall<br />
be used <strong>to</strong> install siren / public<br />
address system.<br />
It is mentioned that “The bidder<br />
will have <strong>to</strong> design VHF radio<br />
network if the solution is based<br />
on VHF radios. One radio base<br />
station per alert and warning<br />
<strong>to</strong>wer (<strong>to</strong>tal 21) and one base<br />
station per DEOC in which the<br />
vulnerable villages are located<br />
are required (<strong>to</strong>tal 3). Number<br />
<strong>of</strong> repeaters will depend upon<br />
regional <strong>to</strong>pography and<br />
proposed radio equipment<br />
power, height <strong>of</strong> <strong>to</strong>wers etc.”<br />
It is mentioned that “Captive<br />
VSAT communication network is<br />
<strong>to</strong> be set-up <strong>to</strong> operate in Ku-<br />
Band frequency including Hub at<br />
Gandhinagar.”<br />
Kindly indicate the tentative number <strong>of</strong><br />
30ft <strong>to</strong>wers<br />
We assume that AWS runs on GSM, but<br />
VHF is an optional mode <strong>of</strong><br />
communication. Please confirm.<br />
We suggest that for bandwidth<br />
requirement <strong>of</strong> mere 5 Mbps, a dedicated<br />
Hub setup is not required. The same may<br />
be put on a Shared Hub network. GSDMA<br />
may apply for special COTM license with a<br />
permission <strong>to</strong> work on Shared Hub. This<br />
will reduce the cost implication <strong>of</strong> the<br />
overall project and will facilitate optimized<br />
solution <strong>to</strong> GSDMA. Please confirm<br />
Consider all 21 locations for<br />
<strong>to</strong>wers.<br />
AWS can run on any technology<br />
but should meet reliability and<br />
other specifications.<br />
Transportable and portable<br />
VSATs are not allowed in shared<br />
Hub services; hence GSDMA has<br />
opted for captive hub.<br />
Necessary funds are allocated<br />
<strong>to</strong>wards cost <strong>of</strong> captive hub.
217<br />
218<br />
219<br />
Qualificat<br />
ion<br />
restrictio<br />
n<br />
Qualificat<br />
ion<br />
restrictio<br />
n<br />
Addition<br />
188 4.4 Tax Taxation<br />
The Video Conferencing Solution OEM<br />
must be in the “Strong Positive” in latest<br />
Gartner’s “Market Scope for Telepresence<br />
and Group Video<br />
Systems” report. The OEM must be<br />
pr<strong>of</strong>itable in last 3 financial years.<br />
Documentary evidence for the same<br />
should be provided. It is common practice<br />
in Government <strong>of</strong> <strong>Gujarat</strong> <strong>to</strong> use Gartner<br />
reports as a reference and allow only<br />
OEMs in the leadership quadrant <strong>of</strong> its<br />
magic quadrant. This will still bring 2-3<br />
OEMs in each category and create healthy<br />
competition<br />
The VoIP and Call Center OEM must be in<br />
Leaders Quadrant <strong>of</strong> latest Gartner Magic<br />
Quadrant. The OEM must be pr<strong>of</strong>itable in<br />
last 3 financial years. Documentary<br />
evidence for the same should be provided.<br />
Please clarify whether Purchaser will<br />
provide form "C" / "D" in this reference.<br />
<strong>No</strong> change:<br />
However technical evaluation<br />
committee may give due weight<br />
age <strong>to</strong> performance <strong>of</strong> OEM<br />
<strong>No</strong> change:<br />
Solution design having OEMs<br />
belonging <strong>to</strong> lead quadrant will<br />
be given weightage during<br />
technical evaluation.<br />
GSDMA will not provide Form<br />
“C”/”D”
220<br />
43<br />
Clause<br />
3.2.2<br />
Detailed Technical<br />
Criteria<br />
Detailed Technical Criteria<br />
a. Detailed technical criteria will<br />
be used <strong>to</strong> evaluate technical<br />
bids <strong>of</strong> only those bidders who<br />
have passed Pre-Qualifications<br />
criteria.<br />
b. Marks will be allotted <strong>to</strong> the<br />
bids based on quality and<br />
specifications <strong>of</strong> ICT systems and<br />
applications <strong>of</strong>fered by the<br />
bidder (sole or consortium) as<br />
well as his partners or<br />
subcontrac<strong>to</strong>rs<br />
EOC Design and Implementation<br />
Projects (including Crisis mgmt.<br />
application, Audio Video<br />
systems, communication<br />
networks but excluding civil<br />
works) - 15 Marks<br />
If a bidder (System Integra<strong>to</strong>r) is proposing<br />
an IMS solution and the application meets<br />
the criteria <strong>of</strong> being deployed in 3 or more<br />
government agencies in an<br />
EOC/ROC/Command Center environment<br />
will the bidder be qualified <strong>to</strong> get these<br />
marks? Essentially we are seeking<br />
clarification if IMS solution providers can<br />
provide their applications as OEM <strong>to</strong><br />
multiple qualified Bidders and provide the<br />
necessary marks for that clause <strong>to</strong> each<br />
bidder. We would request the government<br />
<strong>to</strong> kindly allow this because DSS is a very<br />
critical aspect <strong>of</strong> this bid and there are<br />
only a handful <strong>of</strong> s<strong>of</strong>tware vendors who<br />
focuses on providing such solutions in this<br />
domain. This will enable more System<br />
Integra<strong>to</strong>rs the opportunity <strong>to</strong> submit<br />
responses for this <strong>RFP</strong><br />
Confirmed. However the bidder<br />
shall produce a back <strong>to</strong> back<br />
contract with the technology<br />
partner <strong>of</strong> subcontrac<strong>to</strong>r<br />
221<br />
86 1.8 Training<br />
There will not be more than 30<br />
mock drills over 5 year BOOT<br />
period.<br />
Approx 30 mock drill over 5 years will be<br />
require huge resources, however in <strong>RFP</strong><br />
scope <strong>of</strong> mock drills is not clarified exactly,<br />
in this reference we would request you <strong>to</strong><br />
elaborate more.<br />
- At how many locations mock drills will be<br />
done at a time?<br />
- Partial or full system mock drills?<br />
- What would be role / support from<br />
purchaser <strong>to</strong> make mock drill success?<br />
- Time line <strong>of</strong> every mock drill?<br />
Maximum number <strong>of</strong> mock drill<br />
/ exercise will be 6 or less per<br />
year.2 mock drill per year will be<br />
<strong>State</strong> wide and 4 will confined <strong>to</strong><br />
1-8 districts. Based on readiness<br />
<strong>of</strong> the National EOC, GSDMA<br />
may plan an yearly mock drill<br />
with the participation <strong>of</strong><br />
national EOC, <strong>State</strong> EOC, 8<br />
district EOC , 2 ERC and 2 ERV
222<br />
203<br />
Clause<br />
7.2<br />
Breach and<br />
Rectification /<br />
Termination<br />
Operation & Maintenance Phase<br />
Our understanding is that 50% <strong>of</strong> the QGR<br />
(O&M QGR) shall be<br />
paid within 15 days prior <strong>to</strong> the Quarter<br />
ending and the penalties if any shall be<br />
calculated and notified <strong>to</strong> the opera<strong>to</strong>r<br />
within a week time after the quarter<br />
ending. Please confirm.<br />
We request for modification <strong>of</strong> payment<br />
terms since this project request huge<br />
capital investment.<br />
50% <strong>of</strong> the payment shall be<br />
made within 15 days after the<br />
quarter ends<br />
We request GSDMA <strong>to</strong> release capital<br />
expenditure <strong>of</strong> the project at the AT stage<br />
and Operational expenditure <strong>to</strong> be equally<br />
distributed quarterly.<br />
223<br />
187 Article IV Payment Terms<br />
The Opera<strong>to</strong>r is not entitled <strong>to</strong><br />
be paid by GSDMA during this<br />
phase. Payment shall only be<br />
made after successful<br />
completion <strong>of</strong> AT i.e. once the<br />
Operation & Maintenance Phase<br />
is commenced.<br />
Our request:-<br />
1. Divide the payment terms in<strong>to</strong> capex<br />
and opex<br />
2. Mobilization Advance : <strong>10</strong>% <strong>of</strong> overall<br />
value <strong>of</strong> the contract (i.e fees)<br />
3. Mile s<strong>to</strong>ne based payment :<br />
a. 20% on SRS sign <strong>of</strong>f<br />
b. 20% on Delivery <strong>of</strong> material (phase<br />
wise/location wise)<br />
c. 20% on Installation, Commissioning and<br />
Configuration <strong>of</strong> equipment (phase<br />
wise/location wise)<br />
d. <strong>10</strong>% on UAT (phase wise/location wise)<br />
e. <strong>10</strong>% on FAT /Go-Live<br />
4. <strong>10</strong>% <strong>of</strong> capex along with opex cost will<br />
be paid in 20 equal installments<br />
<strong>No</strong> Change
224<br />
225<br />
220 1.2<br />
220 1.2<br />
1.2 Transfer <strong>of</strong><br />
Assets<br />
1.2 Transfer <strong>of</strong><br />
Assets<br />
a. The Opera<strong>to</strong>r shall transfer all<br />
the Assets on the last day <strong>of</strong> the<br />
Exit Management Period<br />
(“Transfer Date”) <strong>to</strong> GSDMA at<br />
zero value (INR 1) in case <strong>of</strong><br />
expiry <strong>of</strong> the Agreement, and in<br />
case <strong>of</strong> termination <strong>of</strong> the<br />
Agreement, at a fixed value<br />
which is equivalent <strong>to</strong> INR<br />
20,00,00,000/- (Indian Rupees<br />
Twenty Crores) less INR<br />
1,00,00,000/- (Indian Rupees<br />
One Crore) for each quarter or<br />
part there<strong>of</strong>, being the period<br />
from the Implementation Phase<br />
Completion Date / Go – Live till<br />
the Transfer Date.<br />
If GSDMA exercises the option<br />
<strong>to</strong> purchase the s<strong>of</strong>tware for<br />
operating the hardware and<br />
systems, GSDMA shall pay <strong>to</strong> the<br />
Opera<strong>to</strong>r on the Transfer Date<br />
for transfer <strong>of</strong> such s<strong>of</strong>tware for<br />
operating the hardware and<br />
systems, such sum in<br />
accordance with Schedule VI. If<br />
GSDMA exercises the option <strong>to</strong><br />
purchase Proprietary S<strong>of</strong>tware,<br />
the Proprietary S<strong>of</strong>tware shall<br />
be licensed <strong>to</strong> GSDMA in<br />
accordance with the Schedule VI<br />
and Schedule VIII.<br />
In case <strong>of</strong> termination Bidder request<br />
payment for all the Hardware /S<strong>of</strong>tware<br />
Licenses delivered and services rendered<br />
till that day along with Hardware orders<br />
especially for this project and in Transit<br />
GSDMA will make the payment <strong>of</strong> all<br />
unpaid amount against the asset on the<br />
date <strong>of</strong> transfer <strong>of</strong> asset based on the<br />
capex and Opex<br />
<strong>No</strong> Change<br />
<strong>No</strong> Change<br />
226<br />
<strong>10</strong>8 1.4<br />
District EOC,<br />
TEOC, Village, ERC<br />
How many workstation need <strong>to</strong> be<br />
planned for each DEOC, TEOC and Village?<br />
DEOC - 5, TEOC - 1
227<br />
116 1.8<br />
Pg <strong>No</strong> 116 / Sec<br />
<strong>No</strong> 1.8 / Cl <strong>No</strong><br />
VHF Radio<br />
Systems<br />
The bidder must plan and design<br />
state-<strong>of</strong>-the-art wireless<br />
communications network which<br />
is reliable and field proven<br />
which is suitable for operations<br />
in extreme and harsh<br />
environmental conditions, on<br />
multiple frequencies and with<br />
ability <strong>to</strong> bridge for<br />
interoperable communication<br />
between various departments. 4<br />
first responders, ERVs and radio<br />
gateway at SEOC <strong>to</strong>gether will<br />
use 12 VHF frequencies in the<br />
range <strong>of</strong> 136-174 Mhz.<br />
As per NDMA Guidelines 2012 “Network<br />
must have adequate mobility and<br />
transportability with last mile connectivity<br />
in wireless mode; preferably micro-cellular<br />
whether Tetra or GSM / CDMA based.<br />
Mobility could be road, rail, air and<br />
waterways based.”<br />
Last mile connectivity shall be based on<br />
Mission critical communication technology<br />
specifically designed <strong>to</strong> operate in<br />
standalone and networked mode during<br />
disaster situation. TETRA digital<br />
communication system is preferred, which<br />
is based on TDMA and provide IP based<br />
interfaces <strong>to</strong> interconnect all other legacy<br />
networks.<br />
Some <strong>of</strong> the advantages <strong>of</strong> TETRA system<br />
are<br />
- Frequency Economy, TDMA 4 Timeslots<br />
per carrier<br />
- Fast Group calls (less than 300 millisec)<br />
- Full duplex / Hald Duplex / Emergency<br />
calls<br />
- SDS & Packet data (Ideally suited for<br />
SCADA telemetry applications, such as<br />
remote activation <strong>of</strong> siren systems etc<br />
- Multi agency operations can be smoothly<br />
configured and handled, especially during<br />
disaster operation Police, Ambulance, Fire<br />
departments perform rescue and relief<br />
operations and an integrated & hassle free<br />
communication can be facilitated by<br />
TETRA.<br />
Addition - “The VHF equipments<br />
and their installations will be<br />
MIL (Military) standard<br />
compliant.”
228<br />
139 Annex IV<br />
Pg <strong>No</strong> 139 / Sec<br />
<strong>No</strong> – Annex IV<br />
Additional Details<br />
/ Cl <strong>No</strong> 1.1 GIS<br />
System<br />
Background<br />
GSDMA, as part <strong>of</strong> industrial<br />
safety, requested the various oil<br />
and gas players in the state <strong>of</strong><br />
<strong>Gujarat</strong> <strong>to</strong> furnish data <strong>of</strong> their<br />
pipelines, which are traversing<br />
through <strong>Gujarat</strong>. In this regards<br />
data has been received from<br />
most companies operating in<br />
the state <strong>of</strong> <strong>Gujarat</strong>.<br />
BISAG Developed GIS based<br />
system for all the pipelines<br />
carrying Crude Oil, Natural Gas<br />
or Refinery Products within the<br />
state <strong>of</strong> <strong>Gujarat</strong> from an<br />
industrial and chemical disaster<br />
mitigation point <strong>of</strong> view.<br />
System Details<br />
This system is Desk<strong>to</strong>p based<br />
system working on Micros<strong>of</strong>t<br />
Frame work 2.0 and above and<br />
has been developed in VB.NET<br />
<strong>to</strong>ols.<br />
The s<strong>of</strong>tware that has been used<br />
<strong>to</strong> create the database and the<br />
application is open source<br />
s<strong>of</strong>tware (map window). The<br />
geo-spatial database is in .shp<br />
format. The system is ready for<br />
deployment<br />
Expectation from bidders<br />
For the decision support system,<br />
the data captured through SDRN<br />
network needs <strong>to</strong> be created in<br />
<strong>to</strong> various layers and added on<br />
<strong>to</strong> the system that is currently<br />
being deployed. The design <strong>of</strong><br />
the system should be in<br />
consultation with GSDMA<br />
The information available with GSDMA is<br />
<strong>to</strong> be integrated with an cus<strong>to</strong>mized<br />
application.<br />
Pls confirm where this integration is <strong>to</strong> be<br />
built I.e Incident Management Application<br />
or in the Information Management Portal<br />
System(IMPS) or with Call<br />
takers/dispatcher application<br />
Incident management<br />
application.
We understand that the GIS Database will<br />
be made available in s<strong>of</strong>tcopy format by<br />
GSDMA.<br />
But please provide the List <strong>of</strong> features for<br />
which data will be provided.<br />
229<br />
263 <strong>No</strong>te<br />
Resources <strong>to</strong> be provided by<br />
GSDMA are GIS data base with<br />
different layers <strong>of</strong> information<br />
regarding available<br />
infrastructure<br />
We also understand that many <strong>of</strong> these<br />
data will be inter-related but not linked in<br />
a readily usable way. For example, two<br />
sets <strong>of</strong> data a) ward wise population and<br />
b) areas impacted by flood need <strong>to</strong> preprocessed<br />
<strong>to</strong> find out how much<br />
population is actually impacted by flood.<br />
Whether this type <strong>of</strong> data-preprocessing is<br />
involved in the project scope. If yes, we<br />
need details <strong>of</strong> all the data <strong>to</strong> be made<br />
available.<br />
Please clarify.<br />
Refer revised <strong>RFP</strong><br />
230<br />
143 1.4<br />
The data from the SDRN will<br />
need <strong>to</strong> be integrated with the<br />
GIS system in different layers for<br />
decision support. Such design<br />
needs <strong>to</strong> be performed in<br />
consultation with GSDMA<br />
Kindly provide details <strong>of</strong> the layers in<br />
which the SDRN data is <strong>to</strong> be linked.<br />
Does the SDRN data and GIS layers have a<br />
common field or a spatial context is <strong>to</strong> be<br />
established.<br />
For better requirement understanding<br />
kindly provide a sample database.<br />
The details regarding the SDRN<br />
database has been provided in<br />
the existing <strong>RFP</strong>. The bidders are<br />
free <strong>to</strong> look at the same.<br />
231<br />
If the bidder is an Indian company with an<br />
international parent company, can the<br />
parent company’s technical and financial<br />
qualifications be utilized for the bid<br />
Yes
232<br />
233<br />
234<br />
235<br />
20 Pt 1.2.9<br />
95 2.6<br />
255 Pg 255<br />
<strong>10</strong>7<br />
1.3.5/<strong>10</strong><br />
7<br />
GSDR-ICTS Design<br />
Criteria<br />
SCHEDULE<br />
XIII/SEOC/Informa<br />
tion Technology<br />
systems<br />
1.3.5 Architecture<br />
<strong>of</strong> Call / Dispatch<br />
center<br />
The Project will be implemented<br />
on a BOOT (Built, Operate, Own<br />
and Transfer) basis and the<br />
Opera<strong>to</strong>r will be responsible <strong>to</strong><br />
provide, install, test and<br />
commission the ICTS<br />
infrastructure and applications<br />
and will operate and manage<br />
supplies / systems and services<br />
under the scope defined in this<br />
<strong>RFP</strong> for a period <strong>of</strong> five (5) years<br />
from the date <strong>of</strong> commissioning<br />
as per the terms and conditions<br />
<strong>of</strong> the Services Agreement<br />
GSWAN backbone will be used<br />
for inter and intra organizational<br />
day-<strong>to</strong>-day operations with<br />
VSAT network as fallback<br />
communication backbone<br />
available 24*7<br />
The MPLS VPN is planned as<br />
fallback network for GSWAN<br />
(MPLS-VPN should interconnect<br />
SEOC (1), DEOCs (26), TEOCs<br />
(29) and ERCs (5)<br />
VoIP gateway for up <strong>to</strong> 500<br />
users and VoIP phones (8)<br />
Interactive Voice Response (IVR)<br />
system should be installed <strong>to</strong><br />
<strong>of</strong>fer access and <strong>to</strong> provide<br />
self service options <strong>to</strong> users<br />
a) It is requested that the equipment be<br />
considered under CAPEX. This is requested<br />
so that all bidders are on the same page.<br />
In the BOOT Model the cost shall depend<br />
on bidder’s assumption in forecasting<br />
situations wherein equipment gets<br />
damaged beyond repairs or is washed<br />
away during floods.<br />
b) It is requested that the supplies be<br />
treated under OPEX and on actual.<br />
pl. confirm GSWAN shall have largely 2<br />
failover i.e. VSAT and MPLS, However this<br />
network also have their failover<br />
mechanism. Guidelines on failover<br />
covering complete scenario shall be<br />
appreciated. Also, How shall they operate<br />
when all networks are live<br />
Each IP Phone requires a corresponding<br />
license in the PBX. Does this mean that he<br />
IP PBX at SEOC should be licensed for and<br />
ready for 500 users from day one. How<br />
many IP Phones should be provided from<br />
day one all 500<strong>No</strong>s? Or as per the <strong>to</strong>tal<br />
quantity <strong>of</strong> the current <strong>RFP</strong>.<br />
Suggestion : Pl specify the number <strong>of</strong> IVR<br />
ports as 30/60<br />
a) Decision on project<br />
implementation on BOOT basis<br />
is final and there will be no<br />
change.<br />
b) Cost <strong>of</strong> supplies is <strong>to</strong> borne by<br />
the opera<strong>to</strong>r as it is impractical<br />
<strong>to</strong> verify and effect payments at<br />
actuals, hence <strong>No</strong> change<br />
conditions<br />
Priority <strong>of</strong> various networks is<br />
provided in the <strong>RFP</strong> . Switching<br />
should take place when the<br />
existing network resource fails.<br />
Please provide licenses for all<br />
500 users from day one<br />
30 ports
236<br />
237<br />
<strong>10</strong>7<br />
1.3.5/<strong>10</strong><br />
7<br />
1.3.5 Architecture<br />
<strong>of</strong> Call / Dispatch<br />
center<br />
<strong>10</strong>9 1.4/<strong>10</strong>9 District EOC<br />
238 Deliverab<br />
les<br />
239<br />
240<br />
255<br />
259 7<br />
SCHEDUL<br />
E XIII -<br />
What is an ATA<br />
Information<br />
Technology<br />
systems<br />
SCHEDULE XIII<br />
DELIVERABLES/ER<br />
V<br />
External emergency call centers<br />
operated and managed by other<br />
agencies (<strong>10</strong>8, industrial<br />
emergency, health, fire, police<br />
etc) will be interfaced with the<br />
SEOC call center.<br />
DEOC network infrastructure<br />
will support VoIP phones and<br />
Conference station directly and<br />
all the IP phones <strong>to</strong> be<br />
registered with GSDR-ICTS<br />
network<br />
NA<br />
NA<br />
Universal communication<br />
interface (using s<strong>of</strong>t clients and<br />
VoIP switching matrix) <strong>to</strong> bridge<br />
VHF networks <strong>of</strong>: Police, Fire<br />
brigade, National Disaster<br />
Rescue Force (NDRF) and<br />
Revenue department operating<br />
in 136 <strong>to</strong> 174 MHz frequency<br />
band<br />
Can we have a <strong>to</strong>tal number <strong>of</strong> external<br />
call centers? <strong>No</strong> .<strong>of</strong> simultaneous calls<br />
required at the time <strong>of</strong> Emergency?<br />
Specifications <strong>of</strong> VOIP phones &<br />
conference phones are not mentioned in<br />
<strong>RFP</strong>. Pl mentions the same.<br />
In the deliverables section <strong>of</strong> the tender at<br />
DEOC & other locations VoIP phones are<br />
asked with ATA. Please let us what is<br />
expected.<br />
Point b. Asks for e-mail services. Is it<br />
expected <strong>to</strong> provide Email exchange<br />
solution? If yes for how many users?<br />
S<strong>of</strong>t phones need <strong>to</strong> be provisioned. If yes<br />
, pl specify on qty.<br />
External emergency call center<br />
may be limited <strong>to</strong> "ten" in<br />
number.<br />
Specifications are not essential<br />
as bidder is expected <strong>to</strong> <strong>of</strong>fer a<br />
reliable VoIP phone with<br />
standard facilities.<br />
ATA option is accepted but is<br />
not compulsory. Bidder may<br />
<strong>of</strong>fer VoIP phones.<br />
Information is included in the<br />
<strong>RFP</strong>.<br />
Total system requirement as<br />
well as ports are specified in the<br />
<strong>RFP</strong>:
241 Page 259<br />
Sr # 7<br />
242 118-<br />
119<br />
1.2<br />
ERV / Equipment<br />
and systems at<br />
each ERV<br />
Information<br />
Management<br />
Portal System<br />
Universal communication<br />
interface (using s<strong>of</strong>t clients and<br />
VoIP switching matrix) <strong>to</strong> bridge<br />
VHF networks <strong>of</strong>: Police, Fire<br />
brigade, National Disaster<br />
Rescue Force (NDRF) and<br />
Revenue department operating<br />
in 136 <strong>to</strong> 174 MHz frequency<br />
band. Provision is <strong>to</strong> be made<br />
for 2 (two) R F channels per<br />
network and 2 VoIP channels on<br />
MPLS-VPN and VSAT (<strong>to</strong>tal 12<br />
ports)<br />
The system should support<br />
menus driven by statically<br />
defined role-based access<br />
control for various stake holders<br />
as per requirements <strong>to</strong> access<br />
information regarding status <strong>of</strong><br />
disaster (s)<br />
Please clarify is the physical interface<br />
required at the ERV for the integrating<br />
with Police. Fire brigade, NDRF and<br />
Revenue Department at the ERV? If yes,<br />
will GSDMA provide the physical ports<br />
from these agencies at ERV? Suggestion is<br />
that these integration be done at SEOC or<br />
DEOC. Please clarify.<br />
The actual roles and stake holders need <strong>to</strong><br />
be clearly defined. Will GSDMA give<br />
complete list <strong>of</strong> Roles and Users where<br />
they define the Role and the users <strong>of</strong> that<br />
role.<br />
Interface with other VHF<br />
networks is via UCI and not<br />
directly.<br />
Details will be provided <strong>to</strong><br />
selected bidder (opera<strong>to</strong>r).
243 118-<br />
119<br />
244<br />
1.3<br />
Information<br />
Management<br />
Portal System<br />
118 Annexure III<br />
The system should support:<br />
• Syndicated content from news<br />
feeds (RSS)<br />
• External web-based<br />
applications with options <strong>to</strong><br />
launch in popup window, display<br />
in iFrame and content<br />
syndication via web clipping<br />
• For JDBC/ODBC<br />
• For web services (SOAP, WSDL<br />
and UDDI)<br />
• for Web Services for<br />
Interactive Applications (WSIA)<br />
• free text searches<br />
• structured searches driven by<br />
metadata<br />
• management <strong>of</strong> content from<br />
multiple reposi<strong>to</strong>ries<br />
• In-place editing <strong>of</strong> content<br />
• Content conversion (e.g. Word<br />
<strong>to</strong> HTML)<br />
• Widely used operating<br />
systems and web browsers<br />
• Industry standard database<br />
management systems and<br />
• Widely used direc<strong>to</strong>ry servers<br />
Lot <strong>of</strong> this is general s<strong>of</strong>tware feature<br />
what is the actual requirement is not<br />
known? Can you clarify what they would<br />
want <strong>to</strong> do here.<br />
<strong>RFP</strong> defines the technical specifications for<br />
an Incident Management Portal system. Is<br />
this portal going <strong>to</strong> replace the GSDMA<br />
website or somehow connected <strong>to</strong> it?<br />
Please clarify so bidders can allocate<br />
necessary time/budget for such<br />
integration.<br />
Overall requirements are<br />
defined. Details specifications<br />
are indicative and are <strong>to</strong> be used<br />
for design purpose.<br />
<strong>No</strong>.<br />
IMSP and GSDMA website will<br />
operate independently.
Our understanding:<br />
1) The one <strong>of</strong> the most important<br />
component is Incident Management<br />
System,<br />
2) Experience in Finance has no relevance<br />
<strong>to</strong> GSDMA requirement & asking Project<br />
experience in Defense or Finance<br />
organization would only may restrict other<br />
prospective bidders.<br />
3) Experience <strong>of</strong> defense should be<br />
defined as Command & Control room<br />
rather than <strong>No</strong>C.<br />
245<br />
41<br />
Clause<br />
3.2.1<br />
Pre-Qualification<br />
Criteria<br />
(D)The bidder must have<br />
experience <strong>of</strong> implementing at<br />
least one project related <strong>to</strong>:<br />
Emergency Operations Centre or<br />
Network Operations Centre<br />
experience Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations ) in<br />
Projects with over 50 WAN<br />
nodes for Defense or Finance<br />
organization<br />
We understand that GSDMA is re-floating<br />
the said <strong>RFP</strong>, where the said ask was quite<br />
logical and we would request GSDMA <strong>to</strong><br />
amend the said clause as same as<br />
mentioned below, GSDMA may reduce /<br />
remove the project value for better<br />
participation.<br />
“The Bidder must have experience <strong>of</strong><br />
implementing atleast one project related<br />
<strong>to</strong>:-<br />
- Tactical Operations Center (TOC) or<br />
- Emergency Operation Center (EOC) or<br />
- Fusion Center or<br />
- Defense Command Center successfully<br />
completed with any <strong>State</strong><br />
Government/Central Government/PSU in<br />
India or a government organization<br />
anywhere in the world in last 5 years, <strong>of</strong><br />
value more than Rs <strong>10</strong> crores.<br />
The bidder must have<br />
experience <strong>of</strong> implementing at<br />
least one project related <strong>to</strong>:<br />
Emergency Operations Centre or<br />
Network Operations Centre<br />
experience Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations ) in<br />
Projects with over 50 WAN<br />
nodes for Defense/Finance<br />
organization/Central or <strong>State</strong><br />
Government<br />
The scope <strong>of</strong> above project should<br />
include implementation <strong>of</strong> EOC project or<br />
deployment <strong>of</strong> Incident Management<br />
Application or Crisis Information<br />
Management System.
246<br />
247<br />
41<br />
&<br />
43<br />
Clause<br />
no 3.2.1<br />
Clause<br />
<strong>No</strong>. 3.2.2<br />
Pre Qualification<br />
Criteria<br />
Detailed Technical<br />
Criteria<br />
The bidder must have<br />
experience <strong>of</strong> implementing at<br />
least one project related <strong>to</strong>:<br />
Emergency Operations Centre or<br />
Network Operations Centre<br />
experience Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations ) in<br />
Projects with over 50 WAN<br />
nodes for Defense or Finance<br />
organization<br />
Network Operations Centre<br />
experience (Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations) in<br />
Projects with over <strong>10</strong>0 WAN<br />
nodes<br />
41 General Connectivity Cost<br />
For Network Operation Center, in<br />
eligibility condition the requirement is <strong>of</strong><br />
50 WAN nodes, while in technical criteria<br />
it is asked <strong>10</strong>0 WAN nodes, both are <strong>to</strong>o<br />
high,<br />
We request GSDMA <strong>to</strong> kindly reduce the<br />
same <strong>to</strong> 25 nos. at both the clauses.<br />
Bidder is responsible for provision <strong>of</strong> all<br />
kind <strong>of</strong> connectivity required at various<br />
location including obtaining the licenses,<br />
permission etc. from various agencies.<br />
However we understand that any cost <strong>of</strong><br />
licenses obtained from regula<strong>to</strong>ry<br />
authority for use <strong>of</strong> frequencies, satellite<br />
bandwidth charges, Internet / lease line<br />
Bandwidth and other telecom services<br />
from the licensed service providers shall<br />
be borne by GSDMA and paid directly, on<br />
actual basis, <strong>to</strong> the concerned authority&<br />
bidder need not have <strong>to</strong> include the said<br />
cost in their QGR / costing, Kindly confirm.<br />
The bidder must have<br />
experience <strong>of</strong> implementing at<br />
least one project related <strong>to</strong>:<br />
Emergency Operations Centre or<br />
Network Operations Centre<br />
experience Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations ) in<br />
Projects with over 50 WAN<br />
nodes for Defense/Finance<br />
organization/Central or <strong>State</strong><br />
Government<br />
Satellite bandwidth and VSAT<br />
license is GSDMA's responsibility<br />
including cost. Rest <strong>of</strong> it is<br />
opera<strong>to</strong>r's responsibility and <strong>to</strong><br />
be included in QGR
248<br />
81 1.1<br />
General<br />
Requirements<br />
The design <strong>of</strong> GSDR-ICTS<br />
infrastructure capabilities would<br />
be characteristically “fail safe<br />
(reliable)”, scalable and should<br />
be 24*7*365 operational under<br />
all Disaster Conditions. DRC for<br />
SDC where database servers <strong>of</strong><br />
GSDR-ICTS are located is <strong>to</strong> be<br />
proposed by the bidder. The<br />
DRC site should have required<br />
level <strong>of</strong> security <strong>to</strong> maintain<br />
confidentiality and security <strong>of</strong><br />
government data bases<br />
We request GSDMA <strong>to</strong> provide the inputs<br />
/ information about<br />
1) Minimum requirement for DRC Site.<br />
2) What kind <strong>of</strong> redundancy level,<br />
scalability etc. Required <strong>to</strong> be<br />
provisioned?<br />
3) DR location should be within or outside<br />
<strong>Gujarat</strong>?<br />
4) What about the connectivity? Who will<br />
bear the cost <strong>of</strong> connectivity? We<br />
understand all the connectivity’s (GSWAN<br />
or VSAT or leased line) would be borne by<br />
GSDMA and bidder need not have <strong>to</strong><br />
include the said cost in their QGR /<br />
costing.<br />
As <strong>of</strong> now - SDC DR site will be<br />
used in the beginig, as the DR<br />
site is up, running with<br />
connectivity already in place.
249<br />
250<br />
228,<br />
229<br />
&<br />
182<br />
260 9<br />
Clause<br />
no.1.8<br />
&<br />
Clause<br />
<strong>No</strong>. 2.6<br />
Terms <strong>of</strong> Payment<br />
Acceptance <strong>of</strong><br />
Implementation<br />
Phase<br />
Alert and Warning<br />
System<br />
In addition <strong>to</strong> the routine audits,<br />
security audit and<br />
implementation audit <strong>of</strong> the<br />
system shall be done once each<br />
year, the cost <strong>of</strong> which shall be<br />
borne by the Opera<strong>to</strong>r. Such<br />
audits shall be conducted<br />
through a Third Party Agency.<br />
The cost <strong>of</strong> any audits and<br />
inspections, other than security<br />
and implementation audits, shall<br />
be shared equally by the Parties.<br />
The security audi<strong>to</strong>r will be<br />
appointed through a<br />
transparent process, through a<br />
committee which shall include a<br />
representative <strong>of</strong> the Opera<strong>to</strong>r.<br />
The cost <strong>of</strong> any audits and<br />
inspections, other than security<br />
and implementation audits, shall<br />
be shared equally by the Parties.<br />
The security audi<strong>to</strong>r will be<br />
appointed through a<br />
transparent process, through a<br />
committee which shall include a<br />
representative <strong>of</strong> the Opera<strong>to</strong>r.<br />
Remote control system based<br />
on DTH, or GSM, and VHF radio<br />
system (1)<br />
We understand that all the cost <strong>of</strong><br />
<strong>No</strong>minated agency & Third Party agency <strong>to</strong><br />
perform the Acceptance Testing and<br />
Certification, routine audits, security audit<br />
and implementation audit <strong>of</strong> the system<br />
etc. would be borne by GSDMA, kindly<br />
confirm.<br />
1. Kindly elaborate Remote Control<br />
System based on DTH.<br />
2. Bidder will provision for Inmarsat<br />
satellite terminal while design the system<br />
however Permission, procurement and<br />
operating cost <strong>of</strong> Inmarsat satellite<br />
terminal shall be borne by GSDMA. Kindly<br />
confirm<br />
Ref page 228 <strong>of</strong> existing <strong>RFP</strong><br />
Routine audits, security audit<br />
and implementation audit <strong>of</strong> the<br />
system etc. would be borne by<br />
GSDMA<br />
Ref page 182 <strong>of</strong> existing <strong>RFP</strong> “<br />
The Opera<strong>to</strong>r shall coordinate<br />
with GSDMA and the nominated<br />
agency for performing the<br />
Acceptance Testing and<br />
Certification. The cost <strong>of</strong> the<br />
services provided by Testing<br />
Agent shall be borne by<br />
GSDMA.”<br />
All connectivity and bandwidth<br />
charges will be borne by<br />
GSDMA, including for satellite<br />
phones (Inmarsat).
251<br />
252<br />
42 Clause d<br />
Pre qualification<br />
Criteria<br />
42 Eligibility Criteria<br />
Emergency Operations Centre or<br />
Network Operations Centre<br />
experience Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations ) in<br />
Projects with over 50 WAN<br />
nodes for Defense or Finance<br />
organization<br />
The bidder must have<br />
experience <strong>of</strong> implementing at<br />
least one project related <strong>to</strong>:<br />
Emergency Operations Centre or<br />
Network Operations Centre<br />
experience Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations ) in<br />
Projects with over 50 WAN<br />
nodes for Defense or Finance<br />
organization<br />
Change required;<br />
Emergency Operations Centre or Network<br />
Operations Centre experience (WAN,<br />
Security, managing E-mail services,<br />
Internet services etc., for 24x7 operations<br />
) in Projects with over 50 WAN nodes for<br />
Defense or Finance organization.<br />
Kindly relax the criteria as TCIL has done<br />
similar mission critical work for police<br />
department, Delhi.<br />
We request <strong>to</strong> relax the Eligibility Criteria<br />
as .<br />
The bidder must have experience <strong>of</strong><br />
implementing at least one project related<br />
<strong>to</strong>:<br />
Emergency Operations Centre or Network<br />
Operations Centre experience Mission<br />
Critical, WAN, LAN, Security, managing E-<br />
mail services, Internet services etc., for<br />
24x7 operations ) in Projects with over 50<br />
WAN nodes for Government Organization<br />
or PSU or Telecom organization or<br />
Defense or Finance organization<br />
The bidder must have<br />
experience <strong>of</strong> implementing at<br />
least one project related <strong>to</strong>:<br />
Emergency Operations Centre or<br />
Network Operations Centre<br />
experience Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations ) in<br />
Projects with over 50 WAN<br />
nodes for Defense/Finance<br />
organization/Central or <strong>State</strong><br />
Government<br />
The bidder must have<br />
experience <strong>of</strong> implementing at<br />
least one project related <strong>to</strong>:<br />
Emergency Operations Centre or<br />
Network Operations Centre<br />
experience Mission Critical,<br />
WAN, LAN, Security, managing<br />
E-mail services, Internet services<br />
etc., for 24x7 operations ) in<br />
Projects with over 50 WAN<br />
nodes for Defense/Finance<br />
organization/Central or <strong>State</strong><br />
Government
253<br />
254<br />
132<br />
150<br />
Annexure III -<br />
Detailed technical<br />
specifications <strong>of</strong><br />
important subsystems:<br />
Components and<br />
capability<br />
requirements for<br />
ERV: Video<br />
Teleconferencing<br />
with any node on<br />
network, Voice<br />
Communications<br />
with Multiple<br />
redundancy, UHF,<br />
VHF<br />
1.6 <strong>No</strong>minal<br />
specifications for<br />
Multipoint Control<br />
Unit<br />
Addition requested<br />
4) Video Support: H.263, H.264<br />
Up <strong>to</strong> 60 frames / second<br />
All resolutions between QCIF <strong>to</strong><br />
<strong>10</strong>80p<br />
To have tighter integration & better<br />
interoperability, we suggest having IP<br />
Interoperability and Collaboration System,<br />
video conferencing & voice<br />
communication systems from the same<br />
OEM. This will ensure one click integration<br />
between all these devices.<br />
The Video Conferencing Equipment you<br />
have asked for with support <strong>of</strong> 720p only<br />
and not <strong>10</strong>80p. Hence in line with the<br />
overall solution, we request you change<br />
this <strong>to</strong> 720p. Also the current clause is<br />
specific <strong>to</strong> one OEM. Hence we request<br />
you <strong>to</strong> make the clause as following <strong>to</strong><br />
allow competition:<br />
4) Video Support: H.263, H.264<br />
Up <strong>to</strong> 60 frames / second<br />
All resolutions between QCIF <strong>to</strong> 720p<br />
“As far as possible - in order <strong>to</strong><br />
have better IP Interoperability<br />
and Collaboration System, video<br />
conferencing & voice<br />
communication systems should<br />
be from the same OEM".<br />
Basically quality <strong>of</strong> solution be<br />
based on - homogeneity <strong>of</strong> the<br />
products included in combo.<br />
“All resolutions between QCIF <strong>to</strong><br />
720p “. Refer revised <strong>RFP</strong>
255<br />
150<br />
1.6 <strong>No</strong>minal<br />
specifications for<br />
Multipoint Control<br />
Unit<br />
9) Conferencing capability: Up<strong>to</strong><br />
<strong>10</strong>0 video and audio<br />
participants in a single<br />
conference without cascading<br />
The <strong>to</strong>tal number <strong>of</strong> VC rooms asked for in<br />
the <strong>RFP</strong> is less than <strong>10</strong>. Even if you have<br />
multiparty conference with other<br />
locations like all the district collec<strong>to</strong>rs (28<br />
districts) in case <strong>of</strong> disaster, still the <strong>to</strong>tal<br />
participants required on MCU in a single<br />
conference will not be more than 40.<br />
Hence Keeping the buffer and future<br />
scalability, we request you <strong>to</strong> make this as<br />
60 participants in a single conference. Or<br />
allow cascading <strong>to</strong> achieve <strong>10</strong>0<br />
participants in a single conference. Also<br />
<strong>10</strong>0 video and audio participants in a<br />
single conference are specific <strong>to</strong> one OEM.<br />
Hence we request you <strong>to</strong> amend this<br />
clause as: "Up-<strong>to</strong> 60 video and audio<br />
participants in a single conference without<br />
cascading" OR "Up-<strong>to</strong> <strong>10</strong>0 video and audio<br />
participants in a single conference with<br />
cascading"<br />
"Conferencing capability: Up-<strong>to</strong><br />
40 video / audio participants in<br />
a single conference without<br />
cascading." Refer revised <strong>RFP</strong><br />
256<br />
151<br />
1.6 <strong>No</strong>minal<br />
specifications for<br />
Multipoint Control<br />
Unit<br />
11) Interface and data rate<br />
capability<br />
# <strong>10</strong>/<strong>10</strong>0/<strong>10</strong>00 Mb interface<br />
# 64 Kbps <strong>to</strong> 6 Mbps conference<br />
data rates<br />
Even Full High Definition <strong>10</strong>80p Video<br />
Conferencing also requires less than 2.5<br />
Mpbs bandwidth. Your Video<br />
Conferencing Units asked are 720p High<br />
Definition, which requires around 1.5<br />
Mbps. Hence you do not need the data<br />
rate <strong>to</strong> be 64 Kbps <strong>to</strong> 6 Mbps. Hence we<br />
request you <strong>to</strong> make this as: "64 Kbps <strong>to</strong> 4<br />
Mbps".<br />
Specification changed <strong>to</strong> :<br />
Interface and data rate<br />
capability<br />
# <strong>10</strong>/<strong>10</strong>0/<strong>10</strong>00 Mb interface<br />
# 64 Kbps <strong>to</strong> 4Mbps conference<br />
data rates
257<br />
118<br />
Annexur<br />
e III<br />
Section<br />
1.1<br />
Sr. <strong>No</strong>. - 1.4<br />
Technical<br />
Specifications for<br />
Incident<br />
Management<br />
Portal<br />
Sr. <strong>No</strong>. - 1.6 & 1.7 The systems<br />
should Provide Secure Socket<br />
Layer support for HTTPS (webbased<br />
front-end) & LDAP<br />
(direc<strong>to</strong>ry server). The systems<br />
should Provide clear separation<br />
<strong>of</strong> the user registry<br />
(authentication and group<br />
membership) from the user<br />
reposi<strong>to</strong>ry (user attributes);<br />
although they may be<br />
configured <strong>to</strong> the same<br />
persistent s<strong>to</strong>re<br />
The requirement is more in context <strong>of</strong><br />
“active direc<strong>to</strong>ry”. However, we are open<br />
<strong>to</strong> having web based database <strong>to</strong> manage<br />
these details and maintain roles and users.<br />
Please clarify if web based database would<br />
be acceptable?? AD is a Micros<strong>of</strong>t<br />
platform feature, wherein Sl. <strong>No</strong>. 1.4<br />
mentions clearly various Java based<br />
applications support. Require clarification.<br />
Alternate solutions will be<br />
accepted.<br />
JAVA Requirement is for services<br />
on mobile platform. Opera<strong>to</strong>r<br />
may <strong>of</strong>fer suitable platform so<br />
that <strong>of</strong>ficials responsible for<br />
disaster management can access<br />
various s<strong>of</strong>tware applications,<br />
alert messages etc from mobile<br />
platform<br />
258<br />
259<br />
118<br />
118<br />
Annexur<br />
e III<br />
Section<br />
1.1<br />
Annexur<br />
e III<br />
Section<br />
1.1<br />
Sr. <strong>No</strong>. - 1.4<br />
Technical<br />
Specifications for<br />
Incident<br />
Management<br />
Portal<br />
Sr. <strong>No</strong>. - 1.4<br />
Technical<br />
Specifications for<br />
Incident<br />
Management<br />
Portal<br />
Sr 1.<strong>10</strong> The systems should<br />
Provide for non-intrusive<br />
moni<strong>to</strong>ring <strong>of</strong> key activities and<br />
resources, such as sessions,<br />
threads, database connections,<br />
caches, memory , etc<br />
Sr. <strong>No</strong> 1.12 The systems should<br />
Facilitate the creation <strong>of</strong><br />
multiple portal sites on one<br />
instance with each site having<br />
its own URL, look and feel,<br />
pages, users and groups, and<br />
search index. Application should<br />
support Integration services <strong>to</strong><br />
allow access <strong>to</strong> disparate data,<br />
applications, news feeds and<br />
Web services<br />
Web based Application built on JEE, .NET<br />
or PHP platforms would take care <strong>of</strong> all<br />
the points identified here including -<br />
sessions, threads, database connections,<br />
caches, memory, etc.<br />
Please confirm, if Java be the desired<br />
technology platform?? This query is linked<br />
with sl. <strong>No</strong>. 1.4 where ‘active direc<strong>to</strong>ry’<br />
feature requirements have been asked.<br />
Please clarify.<br />
The Apps portal would be a CMS based<br />
structure. What would be the Web Portal<br />
space allocation for the CMS? If any space<br />
limitation <strong>to</strong> be intimated now.<br />
Alternate solutions / platforms<br />
will be accepted. However<br />
please ensure that required<br />
interactivity specifications are<br />
satisfied.<br />
This is part <strong>of</strong> design solution<br />
proposed by the bidder. To<br />
meet requirements for IMPS
260<br />
261<br />
262<br />
118<br />
143<br />
Annexur<br />
e III<br />
Section<br />
1.1<br />
1.3. NC<br />
NC Demo<br />
Sr. <strong>No</strong>. - 1.4<br />
Technical<br />
Specifications for<br />
Incident<br />
Management<br />
Portal<br />
c. Information<br />
Management<br />
Portal System:<br />
146 4 Video Wall LCD Video Wall<br />
Sr <strong>No</strong> 1.14 The systems should<br />
Provide integrated views across<br />
diverse and distributed<br />
information sources, including<br />
query optimization and<br />
integrated caching<br />
Bi-lingual (English and <strong>Gujarat</strong>i)<br />
format<br />
What is meant by “provide integrated<br />
views across diverse and different<br />
database sources”?? What kind <strong>of</strong><br />
database sources being referred here??<br />
Does it refer <strong>to</strong> ‘non-relational’ databases<br />
like Hadoop, Map-reduce, <strong>No</strong>SQL, etc or<br />
data like Big Data which may be collated<br />
from variety <strong>of</strong> sources?? Please note<br />
query optimization is a feature <strong>of</strong> the<br />
relational database, <strong>to</strong> be used for the<br />
IMS.<br />
Please clarify if both the English & <strong>Gujarat</strong>i<br />
contents are <strong>to</strong> be displayed <strong>to</strong>gether on<br />
the portal ?? or the viewer / user would<br />
select “Language options” and the portal<br />
would display particular language only. For<br />
bi-lingual, if any NLTR based language<br />
scripts / s<strong>of</strong>tware, (Unicode compliant), <strong>to</strong><br />
be provided or the Vendor is free <strong>to</strong> use<br />
any Bilingual s<strong>of</strong>tware for integration??<br />
(Please note that non-conformity <strong>of</strong> the<br />
scripts, may lead <strong>to</strong> future bi-lingual<br />
format issues at the time <strong>of</strong> integration <strong>of</strong><br />
information from variable external sources<br />
and databases!!)<br />
Pl considers DLP Video Wall instead <strong>of</strong> LCD<br />
Video Wall. We recommend DLP Video<br />
Wall due <strong>to</strong> the following reasons:<br />
• Long life with very low maintenance<br />
• Seamless large screen with seam gap<br />
263<br />
264<br />
265<br />
85 1.4 INSTALLATION<br />
117 1.1<br />
116 1.9<br />
Passive<br />
Networking<br />
General<br />
Specification<br />
The Opera<strong>to</strong>r shall not cause<br />
any damage <strong>to</strong> Government<br />
buildings /other premises and<br />
property and shall be liable for<br />
their res<strong>to</strong>ration in case <strong>of</strong> any<br />
damage. Trenches, path-cutting<br />
etc. will be back-filled and<br />
res<strong>to</strong>red <strong>to</strong> the original<br />
condition immediately after<br />
laying <strong>of</strong> the conduit/ cable. The<br />
Opera<strong>to</strong>r shall plug conduits and<br />
entrance holes where the<br />
cabling has been installed with<br />
suitable sealing material<br />
GSDMA will be responsible for<br />
laying and Installation <strong>of</strong> OFC<br />
cable between SEOC and<br />
existing SDC.<br />
The opera<strong>to</strong>r will be responsible<br />
for:<br />
1) Laying <strong>of</strong> the OFC within SEOC<br />
for the Gig network backbone.<br />
A strong building / or a suitable<br />
structure more than 30 feet<br />
height or a <strong>to</strong>wer/mast <strong>of</strong> 30<br />
Feet height above ground level<br />
(<strong>to</strong> be provided by the opera<strong>to</strong>r<br />
in case suitable building /<br />
structure is not available) shall<br />
be used <strong>to</strong> install siren / public<br />
address system.<br />
All the fiber laying and connectivity is <strong>to</strong><br />
be provided by GSDMA till inside the<br />
telecom room <strong>of</strong> SEOC,DEOC,TEOC or<br />
Village rooms.<br />
So for all fiber connecting <strong>to</strong> each <strong>of</strong><br />
SEOC,DEOC's, TEOC's and villages<br />
trenching ducting and conducting and<br />
backfilling <strong>of</strong> the same will be carried out<br />
the the GSDMA vendor who will be laying<br />
the fiber optic cables. Pease clarify with<br />
our understanding<br />
Request <strong>to</strong> clarify SEOC gig network back<br />
bone route from SEOC covering which are<br />
all locations.<br />
Kindly indicate the tentative number <strong>of</strong><br />
30ft <strong>to</strong>wers.<br />
Assumptions are correct in<br />
respect <strong>of</strong> cables connecting<br />
SEOC. Wired networks at DEOC<br />
and TEOC will be leased from<br />
telecom opera<strong>to</strong>rs and are not<br />
part <strong>of</strong> opera<strong>to</strong>r's<br />
responsibilities.<br />
Connectivity from SEOC is<br />
explained in the <strong>RFP</strong>.<br />
Consider mast for all locations in<br />
the solution.
266<br />
136 1.5/1.4<br />
The bidder will have <strong>to</strong> design<br />
VHF radio network if the<br />
solution is based on VHF radios.<br />
One radio base station per alert<br />
and warning <strong>to</strong>wer (<strong>to</strong>tal 21)<br />
and one base station per DEOC<br />
in which the vulnerable villages<br />
are located are required (<strong>to</strong>tal<br />
3). Number <strong>of</strong> repeaters will<br />
depend upon regional<br />
<strong>to</strong>pography and proposed radio<br />
equipment power, height <strong>of</strong><br />
<strong>to</strong>wers etc.<br />
We assume that AWS runs on GSM, but<br />
VHF is an optional mode <strong>of</strong><br />
communication<br />
VHF technology is not the<br />
choice <strong>of</strong> GSDMA. However in<br />
case bidder wants <strong>to</strong> opt for this<br />
technology then responsibility<br />
for repeaters etc. is on the<br />
bidder. However bidder will be<br />
responsible for additional costs<br />
involved.<br />
267<br />
268<br />
116 1.9<br />
Alert & warning<br />
system<br />
116 1.9 General<br />
Total <strong>of</strong> 21 siren <strong>to</strong>wers will be<br />
controlled and managed by<br />
SEOC or by concerned DEOC(s)<br />
as per the list enclosed<br />
A strong building / or a suitable<br />
structure more than 30 feet<br />
height or a <strong>to</strong>wer/mast <strong>of</strong> 30<br />
Feet height above ground level<br />
(<strong>to</strong> be provided by the opera<strong>to</strong>r<br />
in case suitable building /<br />
structure is not available) shall<br />
be used <strong>to</strong> install siren / public<br />
address system<br />
We assume that no control is needed at<br />
TEOCs & ERVs (configuration <strong>of</strong> sirens etc),<br />
but can issue alerts .<br />
Kindly indicate the tentative number <strong>of</strong><br />
30ft <strong>to</strong>wers.<br />
Only SEOC and concerned DEOC<br />
will be equipped with this<br />
functionality.<br />
All location will need mast.
269<br />
270<br />
271<br />
136 1.5<br />
<strong>10</strong>8 1.3.6<br />
<strong>10</strong>9 1.6<br />
Alert and Warning<br />
Room (AWR)<br />
Pg <strong>No</strong> <strong>10</strong>9 / Sec<br />
<strong>No</strong> 1.6 / Cl <strong>No</strong><br />
Taluka EOC<br />
The bidder will have <strong>to</strong> design<br />
VHF radio network if the<br />
solution is based on VHF radios.<br />
One radio base station per alert<br />
and warning <strong>to</strong>wer (<strong>to</strong>tal 21)<br />
and one base station per DEOC<br />
in which the vulnerable villages<br />
are located are required (<strong>to</strong>tal<br />
3). Number <strong>of</strong> repeaters will<br />
depend upon regional<br />
<strong>to</strong>pography and proposed radio<br />
equipment power, height <strong>of</strong><br />
<strong>to</strong>wers etc.<br />
Alert & Warning should be<br />
possible at any time <strong>of</strong> the day.<br />
Hence people should be geared<br />
up for 24*7*365. Connectivity<br />
with various broadcasting media<br />
for issuing text and audio alerts<br />
should be available <strong>to</strong> persons<br />
responsible <strong>to</strong> issue warnings.<br />
Common Alerting Pro<strong>to</strong>col (CAP)<br />
based warning system should be<br />
set-up for easy interface with<br />
public broadcasting media<br />
(including TV channels, AM and<br />
FM radios etc.)<br />
Broadband connectivity<br />
subscribed from the service<br />
provider in the area as a<br />
redundant measure for data<br />
communication with the rest <strong>of</strong><br />
GSDR-ICTS network through a<br />
VPN.<br />
We assume that AWS runs on GSM, but<br />
VHF is an optional mode <strong>of</strong><br />
communication<br />
Pls specify the methodology <strong>to</strong> interface<br />
with public broadcasting media.<br />
Will it be over telephone / Video<br />
recordings / Public Radios.<br />
Taluka EOC will be connected <strong>to</strong> DEOC<br />
thru GSWAN / MPLS-VPN.<br />
Broadband connectivity is required for<br />
Internet purpose only, if yes do we need<br />
<strong>to</strong> facilitate firewalls and spywares in the<br />
proposed PC.<br />
Assumption is correct.<br />
Messages will be sent using<br />
public telecom network<br />
including telephones, fax and<br />
Internet<br />
Yes
272<br />
273<br />
274<br />
275<br />
114 1.5<br />
141 1.3<br />
Pg <strong>No</strong> 114 / Sec<br />
<strong>No</strong> 1.5 / Cl <strong>No</strong><br />
Portable VSAT<br />
System<br />
139 1.1 Annexure-IV<br />
121<br />
1.2/<br />
Sr.<strong>No</strong>./<br />
1.14<br />
A telescopic mast <strong>to</strong> mount<br />
wireless network antenna and<br />
electrical hoisting mechanism<br />
for the mast should be provided<br />
with the system.<br />
Integration <strong>of</strong> GIS based static<br />
(legacy data) with dynamic<br />
information / data transmitted<br />
from disaster sites<br />
This system is Desk<strong>to</strong>p based<br />
system working on Micros<strong>of</strong>t<br />
Frame work 2.0 and above and<br />
has been developed in VB.NET<br />
<strong>to</strong>ols.<br />
The s<strong>of</strong>tware that has been used<br />
<strong>to</strong> create the database and the<br />
application is open source<br />
s<strong>of</strong>tware (map window). The<br />
geo-spatial database is in .shp<br />
format. The system is ready for<br />
deployment<br />
The system should provide<br />
scalability features and support<br />
`load balancing, high availability<br />
& disaster recovery. It should<br />
allow up-<strong>to</strong> <strong>10</strong>0 concurrent<br />
users performing queries and 50<br />
concurrent updaters.<br />
What is the size <strong>of</strong> the proposed<br />
telescopic mast<br />
Is there any requirement <strong>of</strong> integration <strong>of</strong><br />
hardcopy maps?<br />
If yes Kindly provide the details <strong>of</strong> various<br />
types <strong>of</strong> maps in terms <strong>of</strong> their <strong>to</strong>tal<br />
number, type (s<strong>of</strong>t copy -raster/vec<strong>to</strong>r<br />
/hard copy), size & scale.<br />
Will this system be used as source <strong>of</strong> GIS<br />
data? If yes does it have the capability <strong>of</strong><br />
handling real time queries/updates? Does<br />
the current GIS system support concurrent<br />
users and exposes web services?<br />
How many simultaneous users are<br />
anticipated for GIS Application? An<br />
estimate is required so as <strong>to</strong> suggest the<br />
hardware and infrastructure requirements<br />
for deploying the solution.<br />
40 Feet as already mentioned in<br />
the <strong>RFP</strong>.<br />
<strong>No</strong>.<br />
Opera<strong>to</strong>r has <strong>to</strong> update current<br />
system <strong>to</strong> meet IMS<br />
requirements.<br />
Already mentioned in the <strong>RFP</strong>.
276<br />
277<br />
278<br />
121<br />
1.5<br />
1.2<br />
1.2/<br />
Sr.<strong>No</strong>./<br />
1.22<br />
1.5 Portable VSAT<br />
system<br />
1.2.6 Brief<br />
description <strong>of</strong> the<br />
project<br />
The system with ability <strong>to</strong> be<br />
receive, compile, s<strong>to</strong>re and<br />
analyze data on rainfall, flood,<br />
water level, wind speed and<br />
direction, earth shake,<br />
temperature, cyclone<br />
progression provided by various<br />
Government / <strong>No</strong>n-Government<br />
agencies will be preferred<br />
Vendors may <strong>of</strong>fer 1 meter<br />
nominal diameter antenna<br />
Communication between first<br />
responders such as police,<br />
disaster rescue forces, fire<br />
brigades that use wireless<br />
communication systems mostly<br />
equipment operating in Very<br />
High Frequency (“VHF”) band<br />
and administra<strong>to</strong>rs on terrestrial<br />
or satellite based Very Small<br />
Aperture Terminals (“VSAT”),<br />
should be possible with Voice<br />
over Internet Pro<strong>to</strong>col (“VoIP”)<br />
based unified communication<br />
system<br />
What would be the format <strong>of</strong> the stated<br />
data on rainfall, flood, water level, wind<br />
speed and direction, earth shake,<br />
temperature, cyclone progression<br />
provided by various Government / <strong>No</strong>n-<br />
Government agencies?<br />
Does the GIS system need <strong>to</strong> be integrated<br />
with the data.<br />
The antenna required in Portable VSAT is a<br />
au<strong>to</strong> pointing antenna or is it a Manual<br />
antenna?<br />
UNIVERSAL INTERFACE SYSTEM (UIS)<br />
a) Will any other device other than<br />
Universal communication Interface be<br />
connected with the VSAT IDU (modem)<br />
over L AN (RJ 45) ports (i.e. IP interface)?<br />
Please confirm.<br />
b) Does UIS support SIP signaling for<br />
VoIP? [As UIS will convert wireless<br />
communication <strong>to</strong> Internet Pro<strong>to</strong>col (IP)<br />
format and VoIP Gateway will be installed<br />
at the SEOC, which means it supports SIP<br />
Signaling for VoIP] Please confirm?<br />
c) Will this box be connecting <strong>to</strong> VSAT<br />
Modem over LAN (RJ45) port for the<br />
communication between ERVs & SEOC on<br />
IP pro<strong>to</strong>col?<br />
d) Provide the specifications/capability<br />
details <strong>of</strong> this Universal Interface System.<br />
e) Schematic Diagram <strong>of</strong> Universal<br />
Interface system showing the traffic flow<br />
<strong>of</strong> VHF system and VSAT system.<br />
GSDMA will match interface<br />
requirements <strong>of</strong> the system<br />
proposed by bidder.<br />
Au<strong>to</strong> pointing and au<strong>to</strong> tracking<br />
a) One more LAN port for<br />
videoconferencing, voice<br />
communication, data<br />
communication etc. is<br />
necessary,<br />
b) Yes<br />
c) Yes<br />
d) Please refer <strong>to</strong> page 259<br />
e) UIS is a standard solution<br />
available from many OEMs,<br />
hence this information is not<br />
included in the <strong>RFP</strong><br />
R Bannerji<br />
CEO, GSDMA