ANNEXURE B
Filetype:
pdf
Filesize: 573092
ANNEXURE B
Clarifications to the queries raised by the prospective bidders in TENDER NO.
MM/TX/042006/000302 issued on 17.04.2006 relating to Supply of 200 KC MPLS based IP
TAX Equipment
S.
No.
Clause
No.
Query Clarification
1.
Section IV,
Pt. II, H,
Clause
2.18
Please clarify which provider provided the
equipment of the existing IP backbone.
Query not related to this
tender. Interworking with
the system will be within
the scope of the
standards / specifications
mentioned in the tender.
2.
Section IV,
Pt. II, H,
Clause
2.23
Please clarify which provider provided the
equipment of the existing IN Network.
Query not related to this
tender. Interworking with
the system will be within
the scope of the
standards / specifications
mentioned in the tender.
3.
Section IV,
Pt. II, H,
Clause
2.19
Which sites will be respectively covered by two
IP domain, please give us detailed information.
Please refer Tender
document.
4.
Section IV,
Pt. II, H,
Clause
2.15.1
Whether the two Softswitch need Disaster
Recovery or not?
No.
5.
MTS
Clause
14.9(i)
Kindly confirm does NMS at two sites need to
be configured with redundancy, or only at NOC
site?
As per tender document, NMS shall be able to
manage 30SS+6000TG+60AS+60SG+all LWS,
which is a very large network. Please kindly
clarify whether NMS need to be configured
according to that or not?
The modified clause is as
follows:
There shall be a Network
management Centre
(NMC) for the IP TAX
network. The NMC shall
be common for the two
IP TAX domains with
the remote terminals
spread across the
country. The NMC to be
deployed shall be as per
TEC GR No. GR/NMS-
01. The hardware and
software of the element
Managers shall be as
defined in this tender.
Hardware and software
will be provided to
manage 4 Softswitches,
50 Trunk Media
Gateways, 4
Announcement Servers,
8 Signaling Gateways,
LAN switches at all the
nodes of the IP TAX
network. The eMS as
part of the NMC shall
support
SNMP/XML/Java as
North Bound interface
for integration with the
NMS in near future
supporting the complete
FCAPS.
6.
MTS
Clause
14.9(ii)
Kindly clarify whether the primary node should
be Chennai and New Delhi.
DR is not required. Main
node will be at Chennai.
7.
MTS
Clause
18.0
Kindly clarify whether vendor should provide a
LIC equipment to monitor the whole IP TAX
system, or just provide the monitor interface in
our network in order to be monitored by the
existing LIC of BSNL?
Clause is clear. The
solution will be required
to be interfaced with the
existing Monitoring
Centre of BSNL.
8.
MTS
Clause
14.9(i)
What’s the work mode between the two NMSs
in Chennai and New Delhi, should they be
Master/Standby or loading sharing on normal
circumstance?
Refer reply at Sl. No. 6.
9.
Section III
Clause 7.2
& Section
IV Part II
Clause
2.37
No. of trainees/Week not mentioned and even at
the same time if the training is carried outside
India will BSNL will take the cost of BSNL
Staff?
Clause is self
explanatory.
10.
Section
VII Part II
Cost of one Resident Engineer for one year.
This varies for different place, kindly confirm
the location.
Chennai.
11.
Section XI
Kindly provide the specifications for the NTP
Server.
NTP server is not to be
quoted. The existing
NTP server of BSNL will
have to be interfaced.
12.
Section XI
Kindly provide the specifications for the
firewall.
Refer Tender document
and TEC GR.
13.
Section XI
Kindly provide the specifications for the Line
printer (132 C).
Refer Annexure-I.
14.
Section XI
Kindly provide the specifications for the Line
printer (Laser Jet).
Refer Annexure-I.
15.
Section XI
Kindly provide the details and specifications of
the required tools and tester.
Refer Tender document.
16.
MTS
Clause 25
Kindly provide the details and the quantity of
SS7 analyzer.
Quantity – 2 Nos.
Specifications – As per
TEC GR.
18.
Section
II/Clause 2
Can the wholly owned Indian subsidiary of
foreign OEM (of the tendered items) Submit the
credentials of the parent company to meet this
clause?
Yes please.
19.
Section II,
IV Clause
2
Refer Section-II, Clause no. 2 (eligible bidder)
it says that lead bidder should have a turnover
of INR 1000 million for last two years.
In Section IV Part II Clause no. 2.1 also
mentioned that Softswitch manufacturers
should have a minimum turnover of telecom
equipment of at least INR 1000 Million in each
of last two financial years.
Clause No. 2.3 also indicates that manufacturer
of the equipment other than Softswitch should
have annual turnover of at least INR 500
Million.
Hence as per tender requirement turnover of all
the different partners have to be qualified
individually along with experience clause.
We request you to amend these clauses to any
one of the bidders namely lead bidder/soft
switch manufacturer/other equipment
manufacturer like Media Gate ways should
have turnover of INR 1000 Million in the last 2
years.
If this clause is not amended, it may result in
many good companies not able to participate.
Request is regretted
please.
20.
Section
II/Clause 2
Is it sufficient if the bidder submits the MOU
with the suppliers of Soft Switches, Trunking
Media gateways, signaling gateways,
announcement server and NMS?
Yes please.
21.
Section
II/Clause
10.1 (V)
Type Approval Certificate (TAC) issued by
Telecom Engineering Centre (TEC) or
Technical Specification Evaluation certificate
(TSEC) issued by QA or proof of having
applied for TAC/TSEC (copy of Form B)
whichever is applicable.
As the supplied equipment has to undergo
validation at BSNL site, we presume that this
clause is not mandatory. Kindly confirm.
Yes please. Clause 2.10
of Section IV Part II
supercedes these clauses.
22.
Section
II/Clause
10.1 (vi)
Inspection Certificate issued by BSNL (QA) for
execution of Educational/Commercial Order if
applicable.
As High Sea Sales is allowed as per the terms
of the tender, we presume that this is not a
Yes please.
mandatory clause. Kindly confirm.
23.
Section
II/Clause
10.4
The offered product has to be type approved.
For this purpose, the supplier shall submit a
sample type for evaluation. The sample would
be evaluated for its ability to meet the technical
specifications, manufacturability, reliability,
testability, ease of installation, maintainability
etc. Necessary documents to substantiate these
attributes will have to be submitted at the time
of application for approval by the supplier for
obtaining type approval.
1. We understand that this is applicable
only for the successful bidder. Kindly
confirm.
2. Is this clause applicable for imported
equipment?
Yes please. This clause is
applicable for successful
bidder only. This is
equally applicable for
imported equipment.
24.
Section
IV/K
Project Import benefit.
We understand that this clause is not applicable
for the indigenous equipment. Kindly confirm.
Yes please.
25.
MTS
Clause
14.11
Announcement in Class 4 application are
limited and can be offered as in-built
announcement server in the MGW.
By having a central announcement server,
BSNL is extending the calls right upto the
central Announcement server and hence
consuming precious bandwidth. We recommend
a distributed built in announcement server with
the MGW may be considered wherein the
announcements can be delivered at the point of
interconnection of trunks. The announcement in
these can be managed from centralized EMS
locations and the changes/feeding of
announcements can be carried out from the
centralized locations. This will have
considerable advantages for BSNL as compared
to the centralised location. This will have
considerable advantages for BSNL as compared
to the centralized server where the bearer traffic
has to flow to a central location consuming
precious bandwidth. Request BSNL to allow
both integrated announcement servers with the
MGW and standalone Announcement servers.
No change in Tender
requirement.
26.
MTS
Clause
14.11 (vi)
As per BSNL. Announcement server should
support H.248v1 upgradable to H.248v2.
However the current technology trends show
that in future SIP will be most popular and
widely deployed protocol between the
Softswitch and announcement server or for that
matter any external resource. We hence suggest
that protocol between the switch and
Protocol between
Softswitch and
Announcement Server
can be H.248 ver 2 or
SIP.
announcement server should be either H.248v2
or SIP.
27.
MTS
Clause
14.11
As per BSNL Announcement Server should
support IVRS functionality. However the
requirement as per this tender is for Toll
switches and subscribers are not directly
connected to this network. IVR primarily being
needed in a class 5 scenario, we suggest that
BSNL should relax the requirement of IVRS on
the announcement servers or ask for it as an
optional item.
IVRS functionality in
Announcement server is
not required.
28.
SGW GR
Clause
2.3.1(v)
As per GR, the signaling gateway needs to
support M2PA. M2PA is required to be
supported only by STPs. However BSNL has
already deployed STPs and M2PA functionality
would not be required to be supported by the
signaling gateways. We would hence request
BSNL to relax the requirement of M2PA.
No change in
requirement.
29.
SGW GR
Clause 2.0
As per the GR, the signalling GW needs to
support STP functionality. Please clarify as to
why would need to support STP functionality
when BSNL has standalone STPs deployed in
the network. This would lead to duplication of
STP functionality in the signaling gateway
which is not likely to be used. We therefore
recommend that the STP functionality
requirement from the signaling gateway may be
relaxed.
No change in
requirement.
30.
SGW GR
Clause
2.10.3
As per the GR, signaling gateway needs to
support 500 signalling links. BSNL is requested
to define the actual number of signaling links
which are required to be engineering on the
signaling gateways. 500 signalling links in a
signaling gateway in the STP architecture
followed by BSNL is very high. We therefore
recommend it may be reduced.
The initial capacity of
SS7 links in the
Signaling Gateway
would be 100. The
capacity would be
expandable to support the
maximum capacity as
indicated in the TEC GR.
31.
SGW GR
Clause 2.6
On line transfer of billing information is
required from Signalling Gateway. However
since signaling gateway does not process calls
but only carries signaling information.
Signalling gateway can not generate CDRs and
requirement for interface from signaling
gateway to billing server should be deleted.
No change in
requirement.
32.
MTS
For dimensioning of SIP interface between the
2 soft-switches. Please provide the %age of
total traffic flowing from one Softswitch
domain to the other Softswitch domain. Please
specify if the GE interface to be provided on the
TMG should be of type Sx.
Intra Domain – Intra
Media Gateway calls-
5%
Intra Domain – Inter
Media Gateway calls-
45%
Inter Domain Calls -
50%
33.
MTS
Clause
14.8(v)
Please specify if the GE interface to be
provided on the TMG should be of type Sx.
All the Media Gateways
are to be provided with
Gig E Sx interface in
1+1, 2+2 or 3+3
configuration (depending
upon traffic calculations).
LAN Switch shall be
provided with
complimentary interface.
34.
SST GR
Clause
2.1.6 and
2.8.1.1.
CCS7
Please clarify that you need is only ITU-T
Q.767 ISUP from the Softswitch.
Refer Tender document.
35.
SST GR
Clause
2.1.6
International ISUP Support of ETSI and ANSI?
Why do we need both? Do we assume one
only? Which one?
No change in Tender
requirement.
36.
Section-V
SOR
40 KC model of Media Gateway not available
in GR. Do we assume two 20KC Media
gateways.
Yes. However, higher
capacity Media Gateway
can also be quoted.
37.
MTS
Clause
18.0
BSNL is requested to clarify specify what is
expected for LIS requirements. Is it providing 8
fanned out calls for the 240 simultaneous
monitored calls?
Refer Tender document
and clarification above.
38.
MTS
Clause
13.1
Average holding time of 60 seconds is too lows.
As the calls rates are declining, the average call
hold times are increasing. Request BSNL to
look into the average holding time values and
revise it to 90 sec. or 120 sec. as per the traffic
pattern.
No change in
requirement.
39.
MTS
Clause
14.2
IP Centrex is a class 5 service which will enable
to provide specialized services within group. IP
Centrex services as per the open standards
architecture specified by 3GPP should be
provided through an Application server. Apart
from the basic application server to provider the
features there could be requirement of web
portal servers for the efficient management of
the features and service by the user himself.
Since all these are related to pure class 5
environment, we suggest this may be kept out
of the scope of this tender. However,
compliance to support external feature servers
(applications servers) on SIP interface as per the
standards may be asked to ensure that at a later
date BSNL is at liberty to procures the class 5
feature server (with IP Centrex functionality)
from any vendor of choice and not get restricted
No change in
requirement.
to the vendor supplying class 4 NGN.
40.
MTS
Clause
14.6
(xii)(i)
As management and signaling information are
processed by different modules in
Softswitch/SGW/TMG which may have
different IP interfaces of their own, and the
clause should be flexible to provide either
separate or a common IP interface for
management and signaling information. Also a
different VLAN can be established for signaling
& management information using port based
VLANs easily.
No change in
requirement.
41.
MTS
Clause
14.7(viii),
14.8(ix)
In an actual network, SGW and MGW can be
synchronized with using timing signal from TD
interfaces (E1/STM-1), As there is necessity to
have a common clock across the network and
even today the clock for complete SDH and
TDM infrastructure of BSNL is common. It is
imperative that the same clock should
mandatorily be used. In case of failure of this
clock, internal holdover clock, even though it
may be of lower stratum, will be able to hold
for a reasonable time. The above condition of
L2 clock shall be relaxed.
No change in
requirement. If integrated
Stratum-2 clock is not
supported, external co-
located Stratum-2
equipment shall be
quoted.
42.
MTS
Clause
14.8(vi)
In a C4 network, bearer traffic may preferable
be carried out on a different data network to
isolate it from signaling/management. As
management signaling Softswitch/SGW/TMG,
which may have different IP interfaces of their
own, the clause shall be relaxed for vendor as
per his design to support separate IP interfaces
for bearer. Management and signalling
information. Also a different VLAN can be
established for signaling and management
information using port based VLANs easily.
No change in
requirement.
43.
MTS
Clause 25
Table 3
For E1 & STM-1 is it possible to use option I &
II per city wise or can be used in totality.
Equipment is to be
supplied either as per
Option-I or Option-II.
However, in case of
Option-II SDH
Multiplexers are to be
supplied for all the TDM
links coming from PSTN
side.
44.
MTS
The requirement of common EMS server shall
be relaxed. Running of EMS application of two
different applications from same server may
affect performance, however it can be
integrated at NMS level
No change in
requirement.
45.
MTS
Clause 25
As per option 1, STM-1 is required in
Bangalore while as per clause 14.8(iv), the
The requirement in
Table-3 is final.
Table 3
same is not indicated. Please clarify.
46.
MTS
Clause
14.11 (ii)
Announcement server being one entity, it will
be difficult to support two SS. Also since
minimum one AS has been asked for 1 SS
domain, this condition shall be relaxed.
No change in Tender
requirement.
47.
MTS
Clause 25:
Table 3
Where are the Technical specs for traffic
parameters of Signalling
Gateways/Softswitch/Media Gateway? Should
we refer GR? Or there is separate MTS?
Refer Tender document
and clarifications.
48.
MTS
clause 1.0
Since the NMS/EMS is not service effecting we
request BSNL to relax the DR requirements.
The DR requirements can become a operational
nightmare if not properly defined. Also since
the required redundancy is met with the cluster
configuration, we recommend that DR
requirement should be removed.
Refer reply at S. No. 6.
49.
MTS
Clause
14.9(i)
The tender requirements for the Softswitches,
Trunk Media Gateways etc… are far below than
what is mentioned. BSNL should ascertain the
scalability of the NMS / EMS rather than
seeking the equipment dimensioned for such
high requirements. BSNL may ensure standard
north bound interfaces from EMS / NMS to
protect the investment made in this procurement
presuming multiple vendors would be there in
future. We recommend the EMS/NMS
hardware be dimensioned as per the tender
requirements and should have the scalability of
the requirements mentioned.
Refer reply at S. No. 5.
50.
MTS
Clause
14.9(v)
Instead of defining the cluster architecture the
uptime requirement may be specified and leave
the architecture to the vendor.
No change in Tender
requirement.
51.
MTS
clause 14.9
(ix) (xii)
(xiv)
Since the NMS/EMS is not service effecting we
would request if BSNL could relax the DR
requirements. The DR requirements. The DR
requirements can become a operational
nightmare if not properly defined.
Refer reply at S. No. 6.
52.
NMS GR
Since BSNL already has a NMS to monitor the
MPLS network, these clauses need to be
relaxed.
Refer reply above please.
53.
Section-II,
Clause
10.1(vi)
As per section II, clause 10.1(vi) TAC or proof
of having applied for TAC (form B) is one of
the eligibility documents WHILE as per section
IV, Part II, 2.10(a) L1 bidder has to offer
equipment for validation after issuance of PO-1.
We understand only L 1 bidder has to offer
equipment for validation after issuance of PO-1
& Form B is not required as one of the bidder’s
eligibility documents.
Refer clarification above
please.
54.
Section IV,
Is validation material part of supply material?
Yes
Part II,
clause 2.10
sub clause
(a)
i.e. after Validation the same material will be
deployed?
55.
Section IV
Clause
2.23, Part
II
Which company does the SCPs of IN service
existing in the BSNL network belong to? Please
kindly provide the model of them.
Query not related to this
tender.
56
MTS 14.10
Please clarify whether 5 nos. or 6 nos. of
1000SX interface needs to be quoted.
5+1 on two different
modules in different slots
57
Section XI
Please clarify whether we need to quote two
LAN switches or two pairs of module
requirement.
LAN switches to be
dimensioned as per
requirement and
Minimum 2 Nos. should
be quoted. Refer Tender
document also.
58
MTS
clause 13.1
Since the tender is for clause 4 application,
please clarify the Call Mix model and the
average call holding time. For e.g. cases like
incomplete dialing will be blocked at the Class
5 node serving the call and hence has no
relevance for calculation.
Refer Tender document
and the clarification
above please.
59
Please clarify the % mix of G711 and G729
vocoders. Since the network is going to evolve
as the core network for carrying various types
of traffic (wire line/ wireless), best voice quality
needs to be ensured at the core of the network
and therefore it may be advisable to have all the
codec’s configured as G711 for best voice
quality. Alternatively, to provide flexibility to
BSNL, the requirement may be restated as the
vocoder pools should provide at least 50%
G711 (or G729) capacity.
All the ports shall be
configurable for any
combination of G.711
and G.729. Refer
clarification above also.
60.
As per TEC GR, the TMG has been asked for
providing 5% extra DSP resources and N+1
redundancy of the vocoders. Generally the
vocoders are pooled resources and hence 5%
extra DSP requirement is more than sufficient
for meeting redundancy requirements. Hence
we request BSNL to ask for either N+1
configuration or 5% extra DSPs, not both.
No change in Tender
requirement.
61.
Signaling
Gateway
As we understand, BSNL is already in the
process of deploying a standalone signaling
network based on SSTPs, that are also working
as signaling gateways. To avoid duplication of
resources, we request BSNL to make the
Signaling Gateway functionality as optional.
No change in Tender
requirement.
62.
DMTS
clause
Please specify if the hardware also needs to be
provided for the requirement of 30
Refer clarification above.
14.9(i)
Softswitches, 6000 TMG, 60 announcement
servers and 60 signaling gateways, or just the
software licenses need to be provided for this
quantity. We request BSNL to ask for the
expansion prices for the hardware while the
software may be procured for the full quantities.
63.
DMTS
clause 14.9
(xvi)
For the NMS, database server is supposed to be
separated from Application server. We request
BSNL to allow the flexibility for database
server to be integrated with the application
server. This will result in performance
improvement and less chances of failure
because of network outages. Secondly, the
requirement for providing 4 processors should
be considered in reference to the latest
generation of dual core servers. In case of dual
core processors, each processors provides the
performance worth two processors and even
there are two oracle licenses that are needed for
each such dual core processor. Hence in case of
such offering, minimum requirement should be
to provide two dual core processors, expandable
to 4.
No change in
requirement.
64.
DMTS:
clause
14.11
Announcement servers: We request BSNL to
consider announcement servers integrated with
the Trunk Media Gateways, as per the TMG
GR. This will result in efficient utilization of
network resources as the calls do not need to
traverse through the whole network for the
announcements. Also there will be many
languages that would have to be supported and
each TMG location might need a different
language for announcement. In case of
announcement server, integrated with TMG, the
whole architecture becomes very simple and
there is also substantial bandwidth saving.
No change in
requirement.
65.
Section IV,
Part II,
Clause 2.6.2 describes that Batteries are to be
supplied along with the power plant. However,
the duration of Battery backup is not provided.
Please provide the battery backup time.
Refer MTS.
66.
As BSNL is planning two large softswitch
domains each supporting a large number of
Trunk Media Gateways, it is unacceptable to
loose service due to a softswitch site failure e.g.
failure of softswitch nodes, applications, links
to connecting equipment or IP network links
etc. Hence the Softswitch in a single IP domain
shall support a fully distributed configuration
where the softswitch nodes are distributed over
two physical sites, providing geographical
No change in
requirement.
redundancy such that either one of which can
control the entire switch if the other site is lost.
In a multi-site configuration, the switch shall
continue to operate upon a single failure of any
component that is available in a redundant pair.
When a switchover occurs on a redundant
component, the switch shall preserve stable
calls. Hence, it may be worthwhile to consider
the two controllers to be geographically
redundant.
67.
NMS GR
As per NMS GR, GR/NMS-01/01.JUL.2005 the
NMS for IP TAX needs to manage the transport
network (IP/MPLS) also. This means that the
NMS for IP TAX will have to manage the
routers, LAN switches, Firewall etc. that
constitute BSNL’s IP/MPLS network. All these
requirements are outside the scope of supply as
per the tender document. Also as we understand
all these equipment are already installed and
integrated to constitute BSNL’s IP/MPLS
network. We also understand that BSNL has
already installed a NMS for the management of
these network elements, and conforming to the
NMS GR. As it is suggested by the TMN
architecture, the EMS layer should talk to the
NMS layer, we request BSNL to ask the bidder
to only supply the Element Management
System (EMS) with appropriate North bound
interfaces and APIs so that this EMS can be
interfaced with already deployed NMS under
MPLS/NIB project.
NMC will control the
NEs supplied in this
tender. Refer to the
clarification at S. No. 5
also.
68.
Sec. II.
Clause 2
Kindly confirm our understanding that the letter
of support requested from OEMs is not
necessary for the peripheral equipment like
PCs, printers, Battery etc. The letter of support
from OEMs is only necessary for core buildings
blocks i.e. soft switch, Trunking Media
Gateways , Signaling Gateway, Billing
Interface and NMS.
Yes please.
69.
Sec. II.
Clause
10.1(vi)
This clause states that eligible bidders have to
submit the Type Approval Certificate issued by
TEC or proof of having applied for TAC (Copy
of Form B) as part of the bid. However, Clause
2.10 section IV mentions that the successful
bidder has to make the equipment physically
available for validation within eight(08) weeks
from the placement of Purchase Over by BSNL.
Please confirm our understanding that Clause
2.10 Section IV prevails over Clause 10.1 (vi),
Section II.
Refer clarification above
please.
70.
Clause
14.1(ii)
and 1.1of
MTS:
As per the clause 1.1 , the soft switches will be
New Delhi and Chennai . As per clause 14.1.ii,
the soft switches will be at Chennai and
Kolkatta. Please clarify about the location of
soft switches.
New Delhi & Chennai
71.
Clause 1.1
and 14.1
(iv),
14.7(i) of
MTS
As per the clause 1.1, the secondary node with
Signally Gateways(SGW) will be New
Delhi,Chennai, Bangalore and Kolkatta. As per
clause 14.1.ii and iv, the secondary node with
Signally Gateway will be Bangalore and
Kolkatta, Chennai. Please clarify about the
location of secondary node and number of
Signalling Gateways.
Refer Schedule of
Requirement.
72.
Clause
14.2 of
MTS and
clause2.36
Section
(IV):
Kindly note that MTS does not specify any
configuration details required for working out
the IP Centex solution.
In view of the above you are requested to
provide us the following details:
Configuration details for IP Centex
subscribes for which system needs to be
configured.
Which type of IAD’s /CPG’s needs to be
included for providing the IP centrex
connectivity alongwith the subscribes
interfaces at each IAD/CPG.
Please provide us the specifications against
which IAD’s/CPG’s and IP clients need to
be offered.
Basic Centrex features as
per Clause no. 2.2.1 of
TEC GR on IP Centrex.
(GR/IPC-01) shall be
demonstrated as part of
validation. The validation
configuration shall
consist of external
provisioning and
authentication system
(PAS) as defined in TEC
GR capable of supporting
100 centrex groups with
each group consisting of
200 members.
73.
Clause
14.8(vi) of
MTS
As per the mentioned clause “There shall be a
common IP interface for carrying control and
management traffic , VoIP traffic etc”.
Based on our worldwide experience and the
RFP’s received from various operators “The
interfaces for control & management traffic
need to be separated from the VoIP payload
traffic because of high priority traffic”.
Also the TEC specification for media gateways
indicated separate interface for control and
management traffic.
The separate interfaces for payload and
signaling from Media Gateways will terminate
at L2/3switch. The L2/L3 switch will aggregate
the payload and the signaling traffic and
provide a single physical interface to the NIB
router however, the payload and signaling can
be routed on different VLANs for QoS
purposes.
So this clause should be modified to be in line
with TEC specifications for separate IP
No change in
requirement.
interface a for control, Management and VoIP
traffic.
74.
For the calculation of battery and power plant
please specify the ultimate capacity of media
gateways locations.
Refer TEC GR.
75.
Clause14.9
(i) of
MTS:
As per clause 14.9 (i) of MTS we understand
that the offered Network Management Server
should be scalable to support 30 Soft switches
,6000 Media Gateways , 60 Announcements
Severs ,LAN switches and 60 Signaling
Gateways is required in future. However the
NMS configuration is to be offered based for
current network node specified against this
tender.
Refer clarification above.
76.
Clause2,
section
VII, part-I
As per our understanding, delivery schedule
mentioned in clause 2.10 of section IV is not in
line with this clause. Kindly amend this clause
accordingly.
Clause 2.10 of Section
IV will prevail over
Clause 2, Section VII,
Part I.
77.
As per the requirement of IP TAX tender, two
IP domains need to be deployed in the BSNL
network. For the dimensioning of SIP-I
interfaces between the soft switches of two
domains please provide the traffic, going from
one domain to another.
Refer clarification above.
78.
Clause
2.12.b,
section IV
part II:
AMC agreement states that AMC value will be
discounted @15% for the purpose of evaluation
whereas in clause no.F.2.12 b, it is mentioned
as 12%. Please clarify.
12%
79.
Clause
2.11 ,
Section IV:
The time frame allotted for the post validation
deliveries, installation and commission of 12
weeks is too short keeping in view the number
of sites involved, we request BSNL to amend
the delivery period to 24 weeks after successful
validation.
No change in
requirement.
80.
Clause 2.5
Section IV
part II:
We understand that the bidder shall provide
operation and maintenance support from
regional centers instead of each Media Gateway
locations. The first level of maintenance at all
the sites (with test equipments) will be done by
BSNL engineers during the warranty period.
Please confirm.
Yes please.
81.
Clause
2.6.1
Section IV
Part II:
The scope of billing in the offered network is
not clearly defined. Please clarify the
integration of billing in the solution
Refer Tender document
and MTS.
82.
Clause
2.30,
section IV:
Please specify the codec mix for dimensioning
the Trunk Media Gateway.
Refer clarification above
and TEC GR.
83.
Clause
We understand that the responsibility for QoS is Vendor shall be
2.34
Section IV
limited to the NGN equipment that we would be
quoting under the scope of this Tender. The
MPLS backbone responsibility is beyond this
scope. Kindly confirm??
responsible for
controlling the part of
end-to-end QoS for the
equipment supplied by
them.
84.
Clause
4(vii),
Annexure-
III, section
IV
Please confirm that only Office reports that
need to be customized are covered under the
scope of this clause.
The clause is clear.
85.
Clause
14.7(iv) of
MTS:
Please provide the dimensioning parameters of
signaling Gateways as follows:
a. number of narrowband signaling
links=…………..
b. Signaling link load per link=……….
c. Number of MUS/sec=…………..
d. Number of GTT/sec=……………
e. Number of IN transaction
/sec=…………….
Number of signalling
links to be provided
presently per Signaling
Gateway is 100. The
Signaling Gateway will
be scalable to 500 links
as specified in GR.
The signalling handling
capacity of Signalling
Gateway will be as per
GR.
However, STP capability
is also required in
Signaling Gateway. The
STP capacity shall be
provided for 1000 MSUs
per second, 300 GTTs
per second and 200 IN
transactions per second.
86.
Clause
14.11 (iii)
of MTS
Please confirm that Mediation device is not
required and we only need to supply the supply
the billing interface?
Yes.
87.
Refer to
clause 14.9
NMS (i), We propose that proposed NMS shall
be capable of managing 50% more than the
current network elements requirements , as it
shall increase the cost unnecessarily. In case of
further expansion of the network, NMS shall
offer the scalability to manage the additional
networks elements, please confirm.
Refer clarification above.
88.
Refer to
clause 14.9
NMS(i)&(ii),We understand to NMS shall
comply with TEC GR SD/NMS/02-01 Feb
2005, please confirm.
Refer Tender document.
89.
Refer to
clause 14.9
(viii),
We request BSNL to also allow the option of
tape drives for the database backup, please
confirm.
No change in
requirement.
90
Section IV,
Part II,
Clause
TAC or copy of Form B has been asked as part
of the offer. However since only the L1 bidder
will need to get the equipment validated,
Refer clarification above
please.
10.1, 10.4
TAC/Form B will not be required to be
submitted. Please clarify.
91.
Section IV,
Part II,
clause A
2.3
Kindly confirm that the core building blocks for
the purpose of certificates are
1. Softswitches ,
2. Signaling gateways,
3. Trunk Media Gateways,
4. NMS Servers
Refer NIT/ clause 2,
Section II
92.
Section IV,
Part II,
Clause D
2.10 (c)
and (d)
Tests for load capacity of 4 million BHCA and
overload of 6 million BHCA need significant
time in terms of arrangements and actual tests
etc, as a we request BSNL consider adding six
weeks for such tests.
No change in
requirement.
93.
Section IV,
Part II,
Clause
2.25
BSNL to confirm that the Reliability and
stability tests of 3 months shall be performed
after the completion of the validation period
when actual load exceeds 50%.
Yes.
94.
Section IV,
Part II,
Clause
2.27
There is no such clause 7 in Special Conditions
of Contract. Please clarify.
The phrase “Clause 7
above” appearing in
Clause 2.27 of Part II of
Section IV of bid
document will be read as
“Clause 2.10 above”.
95
Section IV
Part II
Clause
2.14
We understand that the optional items are
compulsory to quote, please confirm if they will
be considered for the purpose of ranking the
bidders.
The quotations for the IP
Centrex feature will form
part of evaluation. (Also
refer Clause 2.36 of Part
II of Section IV of bid
document.)
96
Section XI
Section XI of the Bill of Material inverter is
shown at all locations. Further, as per Clause 11
(k) of the MTS inverters are required for Media
Gateway locations. Please clarify.
Inverters are required at
Media Gateway
locations.
97
Section IV
Part II
Clause 2.3
and
Annexure-
II S. No. 1
The experience asked under clause 2.3: The
equipment being provided through the
manufacturers of equipment other than the Soft
Switch, for the core building blocks is six
months and the experience asked is ONE year
under Annexure-II S. No. 1. We request BSNL
to change the statement in Annexure-II to six
months in pursuance to clause 2.3 (Sec IV).
Annexure-II, Section-IV
in S. No. 1, 06 (six)
months may please be
read in place of one year
98.
Section IV
Part II
Clause D
2.10 (c)
Since the equipment required for conducting the
load test is very expensive and large in number
we request that the load testing should be
carried out at the vendor’s lab in the presence of
the BSNL validation team. Please clarify.
Vendor will have an
option to demonstrate
this test in his lab.
99.
Section IV,
Clause 1.0
ii) and (H)
2.15.1
Clause 1.0 ii) asks for H.248 ver 2 as the
protocol between TMG and Softswitch while
clause 2.15.1 asks for H.248 ver 1 (upgradeable
to ver 2 within one year of PO). Please clarify if
H.248 ver 2 is to be
provided from first day
itself as per Clause 1.1
(ii) of Section IV Part II
clause 2.15.1 can be taken as the final one for
this requirement.
of bid document.
100.
Section
VII
NTP server in Price Schedule is asked for at
two places Pt no 4(f) and Pt no (15). We
understand that it should not appear under Point
no. 15. Please clarify.
Refer clarification above
please.
101.
Clause 11
MTS
As per the GR power plant with 100 amp
module the ultimate capacity has to be
considered for 1500 or 300 amps. Please
confirm.
Refer Tender document.
102.
Clause 11
MTS
As per the TEC GR/SMP-01/05 JAN 2005
remote monitoring and battery health check up
is optional. Pls confirm whether it is provided
or not.
It is optional.
103.
Clause 11
(j) MTS
No supplier is available in India with a type
approved UPS above 15 KVA with TEC GR
No. G/UPS-01/02/July 2002. Please clarify.
The requirement for UPS
of above 15 KVA is not
anticipated as per normal
dimensioning.
104.
Clause
14.1 ii
The clause mentions Chennai and Kolkata as
primary nodes. It should be Chennai and Delhi
as primary nodes. Please clarify.
Yes.
105.
Clause
14.1 iii
As per this clause, TMG will be connected to
PE router directly using GE interface but figure
4 shows LAN switch. Please clarify.
Refer Tender document.
106.
Clause
14.2 MTS
We understand that 100 centrex groups with
200 members each should be supported by the
IP based centrex to be offered. Please confirm.
Basic Centrex features as
per Clause no. 2.2.1 of
TEC GR on IP Centrex.
(GR/IPC-01) shall be
demonstrated as part of
validation. The validation
configuration shall
consist of external
provisioning and
authentication system
(PAS) as defined in TEC
GR capable of supporting
100 centrex groups with
each group consisting of
200 members.
107.
Clause
14.7 iv
MTS
We understand that the initial capacity of SS7
links in the Signaling Gateway would be 100
expandable to support the capacity as indicated
in the TEC GR. Please confirm.
The initial capacity of
SS7 links in the
Signaling Gateway
would be 100. The
capacity would be
expandable to support the
maximum capacity as
indicated in the TEC GR.
108
14.8 (iv)
MTS
As per this clause STM-1 interface are to be
supported on TMGs supplied at New Delhi,
Mumbai, Kolkatta and Chennai only. However,
The requirement is as per
Table 3.
in Table 3 option I under clause no. 25, it is
asked for in Bangalore as well. Please clarify.
109.
14.8 (ix)
MTS
For TMGW the tender should allow Stratum-2
clock or Stratum-3 clock. BSNL is requested to
modify the sentence accordingly.
Refer clarification above.
110.
14.9 (i)
MTS
As we understand that BSNL is looking for an
NMS capable of controlling at least 30 Soft
switches and 6000 Media gateways, 60
Announcement Servers, LAN switches and 60
Signaling Gateways. Kindly clarify if we need
to dimension the NMS for the present
requirements, however scalable to the above
mentioned capacities.
Refer reply at S. No. 5.
111.
14.9 (i)
Considering that NMS disaster recovery is
required at New Delhi site the qty of UPS in
(line item Q of high level BOM) New Delhi is
not specified. Please clarify.
Refer reply at S. No. 6.
112
14.9 (xxiii)
& Section
XI
In the DMTS, the NTP server is requested on
the NMS platform. Now that 2 NMS platforms
(New Delhi and Chennai) are being asked for,
please clarify the exact no. of NTP servers
required as it is only indicated against Chennai
NMS site.
Refer reply at S. No. 6.
113.
14.11 vi)
MTS
As per the tender document, BSNL has asked
for H.248 ver 1 protocol to be used between the
Soft Switch and the Announcement servers,
which should be upgraded to H.248 ver2 after 1
year of P.O. However, the current technological
trends shows that in future SIP will be the most
popular protocol. We suggest that BSNL,
should stipulate that the protocol between
Softswitch and Announcement Server can also
be SIP.
Protocol between
Softswitch and
Announcement Server
can be H.248 ver 2 or
SIP.
114.
15.1 MTS
For Voice Performance and Protocol Analyser,
please note that a new TEC GR has been issued
vide Ref no. GR/DCS-09/03 Feb 2006 whereas
old GR/DCS-09/02 Aug 2003 has been referred
to in MTS. Please confirm whether we need to
submit our compliance to the new GR or the old
one mentioned in the MTS.
The compliance to the
new GR is to be
furnished.
115.
Clause
15.4 MTS
Does it imply that with each media gateway 2
printers (one of these to be heavy duty) have to
be supplied but as per the high level BOM only
one printer is to be provided at each TMG
locations. Pls clarify. We understand that in
addition to the above requirement 2 nos.
printers for administrative purpose have to be
supplied at NMS location Chennai column of
the High level BOM.
Printers are to be
provided as per High
Level BOM.
116.
Clause 25
We understand that the bidder needs to provide Yes please.
MTS
only 2 nos. of SS7 analyzers in line with 2 nos.
of Voice Protocol and Performance Analyser
and Voice Quality Analyser each as mentioned
in the MTS. Please clarify.
117.
Section II
Clause 4
Whether in case of the lead bidder having
teaming agreements with OEMs of the Basic
Building Blocks, the Annual Turnover criteria
for last 02 years should be added together as a
sum total of turnovers of the Team member i.e.
the lead bidder with the OEMs.
Request is regretted
please.
118.
Section II
Clause
10.3
What type of documentary evidence is required
for establishing proveness of the system
offered.
Refer Section IV of
Tender document.
119.
Section II
Clause 34
Whether the Telecom Technology Centre of
Govt. of India (under Ministry of
Communications & IT), as a lead bidder, shall
be exempted form submitting the No Relative
Certificate for the full time Directors appointed
by Govt. of India.
No please
120.
Clause
14.9 (xxiii)
What version of NTP server is required? Refer
clarification
above
please.
121.
Clause 7.2
MTS
Will spare parts include every individual card of
NGN Hw components to be stored at each site?
Atleast one card of each
type will be included in
the spares.
122.
Section XI
The location of Firewall is not mentioned.
Chennai
123.
Clause
14.11 (v)
MTS
What is the meaning of circuit group
termination here.
The clause is clear.
124.
Part II, 1.1-i. Q.1912.5 refers to SIP-I that is a
more standard version of SIP-T. What standard
does BSNL require compliance for- SIP-T if it
is not Q.1912.5? IETF SIP RFC3372 is a
guideline document and does not specify exact
SIP-T flows as does Q.1912-5.
Refer TEC GR.
125.
Part II, 2.22; Does the class 5 switch need to
comply with TISPAN and ITU standards for
IMS compliance? IMS compliance refers to
having P-CSCF, I-CSCF, S-CSCF, SLF, BGCF,
HSS, etc. If so what are the specifications being
referred to?
No change in
requirement.
126.
Part II, 2.23; what specification is required for
IN interconnection CS1 or CS2?
Refer TEC GR. Presently
the SCP is at IN-CS1.
The equipment to be
supplied shall be
upgradeable to IN-CS2
as and when required, at
no extra cost.
127.
Part II, 1.1; Do the two main sites (New Delhi
and Chennai) require complete geographical
redundancy (all components including FCAPS
and SS7 Signaling network elements)?
No change in
requirement.
128.
For IP interconnection to other carriers will
BSNL use H.323 or OSP besides SIP? If so
what version of H.323 is required?
H.323 is not required.
129.
For IP interconnection, what are the specifics of
Border Gateway requirements ? Have the
requirements been updated from the previous
GRs regarding IMS IBCF functionality? Also is
the Border Gateway required to be integrated
with the softswitch especially for provisioning
and routing functionality?
No change in
requirement.
130.
What is the proportion of compressed (G.729)
to uncompressed (G.711) calls per Media
gateway site?
Refer clarification above.
131.
Sec II, Cl
10 v, vi
This clause requires TAC/TSEC or QA
certificate as an eligibility criteria. In view of
the fact that the IP TAX is a new technology,
vendors will not have the TAC/QA certificates.
Hence, we kindly request BSNL to relax this
clause.
Refer clarification above
please.
132.
Sec II, Cl
10 v, vi
In the absence of the TAC/TSEC or QA for the
NGN equipments, we request BSNL to allow
the TAC/TSEC of D-TAX equipment (since the
requirement is for transit network) for meeting
the eligibility criteria.
Request ids regretted
please.
133.
Clause 32 ,
Tender
Document,
Section II
As we understand the offered equipment will be
deployed in BSNL network after doing the
successful validation however in this clause
BSNL has specified that the supplier can be
disqualified if the offered equipment do not
perform in the field. Since the equipment is
already validated by BSNL so we request to
kindly remove this clause.
No change in
requirement.
134.
Clause
2.21
Tender
Document
BSNL has asked the support of inter working of
offered soft switch with BSNL existing H.323
based VoIP network (optional) however the
same is not the part of the Schedule of
Yes please.
, Section 4
, Part 2
requirements , so kindly confirm whether the
same is mandatory to be offered as the part of
the commercial offer.
135.
Clause
2.22
Tender
Document,
Section 4,
Part 2
BSNL has asked for the soft switch capable of
supporting the class 5 features as and when IP is
introduced in the Access Network. We
understand that the HW/SW required for class 5
is not the part of the present offering. Kindly
confirm.
Refer Tender document.
136.
Clause
2.34
Tender
Document
, Section
IV Part 2
The end to end QoS will depend on the offered
Network elements supplied by the bidder and
BSNL existing NIB network (IP Routers &
MPLS nodes). The offered equipment will be
implemented and provided as per the standards
defined in the tender, MTS and GR documents
however the implementation of the QoS in the
backbone network will be the prime
responsibility of the BSNL or the vendor
supplying the backbone network. Kindly
confirm our understanding.
Refer clarification above.
137.
Sec VI, Cl
19
The clause requires compliance to Environment
testing by DoT QA (QM 333). We request
BSNL to kindly consider the reports/certificate
of any other equivalent standards/certification
as being done in other projects. Kindly confirm.
No change in
requirement.
138.
MTS :
Clause
Number
1.1, bullet
3
The clause mentions that the NMS is to be set
up with a disaster recovery (DR) site. The High
Level BOQ given as part of Section XI of the
bid document has no mention of the DR for
NMS. As per MTS BSNL has asked for
clustering at primary NMS location, which will
provide redundancy. Since the redundancy is
met within a cluster so we recommend that DR
is not required. Kindly confirm?
Refer clarification above
please.
139.
MTS :
Clause
Number
1.1, bullet
4
As we understand, BSNL has asked for 2
announcements servers in each IP domain for
redundancy. However, as per our experience, in
transit network the transit nodes generally
release the End of Selection (ISUP-EoS) on
basis of which the local exchange plays an
announcements.
The requirement of Standalone Announcement
server is more envisaged in class 5 IP Network
for which TISPAN and 3GPP has defined the
architecture as per the IMS standards.
Hence we request to kindly allow the vendors to
offer an announcement server which can be co-
located/integrated with the soft-switch. Kindly
confirm.
No change in
requirement.
140.
MTS :
Kindly clarify whether the maintenance spares
During AMC period
Clause
Number
7.2
and consumables can be provided at the
centralized location of each IP domain or the
same is to be provisioned at each location.
supplier will maintain
spares as per Clause 9
and 13 of Annexure III.
Quantity of spares is to
be worked out as per
clause no. 2.6.3 Section
IV, Part II or as per MTS
whichever is higher. This
quantity is to be rounded
up to the next integer.
The spares are to be
provided for all network
elements, such as
Softswitch, Trunk Media
Gateway, Signaling
Gateway, LAN Switch,
NMS elements,
Announcement Server,
UPS (excluding battery),
for all type of control
cards, switch fabric,
interface cards and power
supplies.
141.
MTS :
Clause
Number
13.1
As part of the call mix, we request BSNL to
kindly specify the traffic mix also i.e. intra IP
domain, inter IP domain so that dimensioning
can be done accordingly.
Refer clarification above.
142.
MTS :
Clause
Number
14.2
In this clause BSNL has asked for IP Centrex
features as a part of IP transit network. Please
note that IP Centrex and other multi media
applications have been deployed as part a Class
5 network for which the network topology has
been defined by TISPAN & 3GPP (mobile) in
the IMS architecture.
As we understand the BSNL is already in
process of coming with a tender on class 5
application with IP access so we recommend
BSNL to kindly include the IP centrex
requirements in class 5 tender and remove the
same from IP based transit network. Kindly
confirm.
No change in
requirement.
143.
MTS :
Clause
Number
14.8, v
We request BSNL to clarify if the Gigabit
Ethernet interfaces can be provided the N+1
redundancy (with N =1) as this will reduce the
number of interfaces towards PE router? The
redundancy shall be provided using different
modules. Kindly confirm.
No change in
requirement.
144.
MTS :
Clause
Number
The clause requires Layer 2 stability clock to be
supplied along with the MGW. We would like
BSNL to clarify if a stand alone Layer 2
Refer clarification above
please.
14.8, ix
stability clock, can be provided to meet this
criteria.
145.
MTS :
Clause
Number
14.9
This section stipulates separate EMS and NMS
platforms along with a separate DB server, with
each platform running on a cluster of servers.
We'd like to bring to the attention of BSNL that
most vendor will be able to support EMS, NMS
and DB on a single platform on a cluster of
servers. Separate EMS and NMS will be
required only when the IP TAX solution
consists of network elements like Softswitch,
MGW, SGW, announcement server etc from
multi vendors, where each node will require a
separate EMS platform with northbound
interface towards the NMS layer. For the
bidders providing the end-to-end solution, the
EMS/NMS and DB can be integrated into a
single server cluster. Hence we request BSNL
to kindly preferably accept the integrated NMS
for the network elements provided by same
vendor. Kindly confirm.
Refer clarification above
please.
146.
MTS :
Clause No.
14.11 , (ii)
In this clause BSNL has asked the simultaneous
control of the same announcement server by 2
soft switches however as per the H.248 gateway
control protocol it is not permitted to register
the gateway simultaneously to the multiple
(two) soft switches. In order to do the same the
gateway (announcement server) needs to be
partitioned/decomposed into multiple gateways
and then the same can be parented to multiple
soft switch nodes. So instead of doing the
logical partition of the same gateway at the one
physical location we recommend BSNL
strategy to place a standalone announcement
server at each IP domain. Hence in view of
above we request BSNL to kindly remove this
requirement.
No change in
requirement.
147.
MTS :
Clause
Number 18
As per this clause, we understand that the
requirement is to monitor 240 calls
simultaneously by max. 8 agencies per IP
domain. Kindly confirm.
Yes please.
148.
MTS :
Clause
Number 18
Kindly confirm whether the LIM equipment is
also the part of the offering ?
Equipment for lawful
interception is to be
provided. However,
monitoring center is not
in the scope of the
tender.
149.
MTS
Clause 24
We request BSNL to kindly issue us a
document specifying the Validation scope so
that the right testing equipment and competence
Validation schedule is to
be submitted by the
bidder. The scope of
can be assured for carrying the validation
activity.
validation will include all
technical requirements as
specified in the tender,
GRs and MTS.
150.
MTS :
Clause
Number 25
We request BSNL to kindly allow the vendors
to provide the electrical E1 interfaces through
the combination of STM 1 and ADM .
Refer clarification above
please.
151.
GR/SST-
01, Cl
3.2.17
Do we need to propose Least cost routing as
specified in clause no 3.2.17 of GR/SST-01.
Kindly clarify? If yes then kindly provide the
information on the number of CDR per day to
be handled by the LCR solution in the network
?
Quotes for LCR is
optional.
152.
MGW
GR/TMG-
01/01 July
2003
Chapter 3
Clause 3.2
(iii) ,
Clause 3.4
(vi)
The clause requires that 5% codec be
provisioned extra. As codec resources have
been asked for 100% of calls (successful as well
as unsuccessful) hence we request BSNL to
remove the additional requirement of 5% of
codec's . Kindly confirm.
No change in
requirement.
153.
TMGW
GR/TMG-
01/01.JUL
Y 2003 –
Clause No.
3.3
As per this clause BSNL has asked to offer the
Media gateway’s of various capacities (4000
circuits to 20,000 circuits). As discussed during
the vendor forum dated 9
th
May 2006 BSNL has
asked to provision the DSP as per the G.729
codec’s and the bandwidth calculations as per
the G.711 codec’s thus ensuring the possibility
of any types of call mix. Reference to the table
enclosed please note that for cat D and cat E
types media gateway the number of Gigabit
Ethernet interfaces for connecting the IP
backbone network exceeds 1 hence we request
BSNL to kindly allow the vendors to provide 2
media gateways to cater the requirements of cat
D and cat E type media gateways.
The DSPs are to be
dimensioned for 100%
G.729 codecs and the
bandwidth calculations
for 100% G.711 codecs.
For category D & E
TMGs, the n
umber of
Gigabit Ethernet interfaces
from TMG can be 3+3.
Also refer clarification
above.
MGW
Types
A B C
D
E
Descriptio
n - Ports
4000 8000 12000 16000 20000
Number of
E1's
134 267 400
534
667
Max
STM-1 in
1 MGW
6 10 14 18 22
TS in E1
32 32 32
32
32
BW for
G.711
with 10ms
sampling
time and
silence
suppressio
n
76 76 76
76
76
No. Of
Gig
required
on G.711
1 1 1
2
2
154.
MTS,
clause 1.2
Table1
We request BSNL to allow option of offering 2
media gateways to cater for Category E media
gateway requirements.
The bidders are required
to quote as per
modularity of the
equipment available with
them and those specified
in the tender.
155.
MTS –
Clause No.
14.2
Please provide the dimensioning details i.e. No.
of subscribers, mean holding time, traffic per
subscriber for dimensioning the IP Centrex
system.
Refer clarification above.
156.
MTS –
Clause No.
14.8 (ix)
As per this clause BSNL has asked the
requirement of Layer 2 stability clock ,
preferably integrated , in the Trunk Media
Gateway. Most of the media gateways available
commercially do not have support of Stratum 2.
Hence, we request BSNL to kindly allow
external synchronization unit for providing
Stratum 2 clock stability or allow Stratum 3
stability in the media Gateways
Refer clarification above
please.
157.
MTS –
Clause No.
14.8 (ix)
We understand BSNL has already established
the stratum 2 synchronization network
synchronizing the other network elements at all
the level 1 TAX. So we suggest that the existing
SSU can be re-used to synchronize the Media
Gateway for achieving Stratum 2 clock
stability. This will provide a uniform
synchronization across the network. Kindly
confirm.
Refer clarification above
please.
158.
Tender
Document
– Clause
No. 2.10, c
We request BSNL to kindly allow the vendors
to carry and demonstrate the load test in the
vendor’s test lab as the generation/simulation of
such a huge BHCA need specific competence
and external hardware/software . So we request
Refer clarification above.
BSNL to kindly carry out this test at the
proposed venue suggested by the bidder. Kindly
confirm.
159.
Tender
Document
– Clause
No. 2.25
As discussed in the vendor forum we
understand that the 50% loading for 3 months
can be carried once the complete network (as
per PO1 and PO2) has been deployed and we
understand that the same is not part of the
validation activity scheduled to be completed
after issuance of PO1 as defined in clause 2.10.
Kindly confirm
Yes please.
160. Bid
Clause
2.15.2
As per MTS clause 2.15.2, the Softswitch
should comply to SIP_T initially and SIP_I
within one year of the PO. Since both the
Softswitches would be from the same
technology the vendors should be allowed to
support SIP or SIP_T at present and SIP_I in
the future.
The request is regretted
please.
161.
MTS
clause 13-
Dimensio
ning
For dimensioning of SIP interface between the
2 soft-switches, please provide the %age of
total traffic flowing from one Softswitch
domain to the other Softswitch domain.
What is the call distribution between
Intra MG, Inter MG, Intra Domain, Inter MG-
Inter Domain.
Considering the community of interest and the
dialling pattern in different networks, we
recommend the following call distribution
parameters:
Intra MG: 40%
Inter MG, Intra Domain: 20%
Inter MG-Inter Domain.: 40%.
Refer clarification above.
162. MTS 14.1 Clause is referring to Figures 1,2,3,4.
No figures are given as part of MTS, Please
provide same
The figures are attached.
163. MTS
clause
14.2
Please specify
IP Centrex is required for how many
subscribers?
Is Media Server Required as part of offer? If
Yes, what are parameters like average
announcement time, etc.
If any other hardware like console etc is being
envisaged?
What are the interfaces required?
Refer clarification above.
164. MTS
Clause
14.6 (xii)
As per the clause the call and message handling
resources in the Softswitch will act in load
sharing mode ......... in the solution
We request BSNL to provide option in form of
Load sharing or Active/Standby provided call
state model is maintained.
The resources referred to
in this clause and 14.7
(vii) of MTS will be
available in pool and act
in load sharing mode. In
case of failure of one of
the entities in the pool /
overload condition, the
load will be distributed to
the remaining entities.
The solution may also be
designed with resources
available in
Active/Standby mode
with full duplication of
resources in 1+1
configuration.
165. MTS
Clause
14.7 (iv)
The Signalling Gateways to be deployed in the
IP TAX network shall be supplied with the
following interfaces however it shall be
expandable to support the capacity as indicated
in the TEC GR for the signaling capacity.
E1 as per G.703 :10 no.
Please clarify as how many Signalling Links
are required
Refer clarification above.
166. MTS
Clause
14.8 (iv)
This clause asks for STM-1o @1550nm. Please
clarify whether BSNL requires Sx or Lx on
1550nm.
Sx
167. MTS
Clause
14.9
It is suggested that BSNL uses the existing
NMS system deployed in MPLS and NI
network for managing the EMSs supplied in
this network
Refer clarification above
please.
168. MTS
Clause
14.9(i)
The tender requirements for the
Softswitches(30), Trunk Media Gateways
(6000), AS (60), Signalling GW (60) etc…(are
far below than what is mentioned. BSNL should
ascertain the scalability of the NMS / EMS
rather than seeking the equipment dimensioned
for such high requirements. BSNL may ensure
standard north bound interfaces from EMS /
NMS to protect the investment made in this
procurement presuming multiple vendors would
be there in future. We recommend the
EMS/NMS hardware be dimensioned as per the
tender requirements and should have the
scalability to the requirements mentioned.
Refer clarification above.
169. MTS
clause
18.0
BSNL is requested to clearly specify what is
expected for LI requirements. Is it providing 8
fanned out calls for the 240 simultaneous
monitored calls ?
Also please clarify if the 240 calls are to be
monitored per M. Gateway or per domain?
Refer clarification above.
Maximum 240 calls per
domain will be there
which will be sent to 8
LEAs. However, all these
240 calls may be
intercepted from one
Media Gateway also.
170. SGW GR As per the clause, it shall be possible to extract
No change in
Clause
2.2.2
and process the signalling information from
64kbit/s signalling links multiplexed on a 2048
kbit (ITU-T G.703) links. The SG shall be able
to extract signalling information which can be
on at least 16 time slots (except time slot 0).
For redundancy and failover, each SG is
connected to at least 2 standalone STPs (SSTP).
It is recommended that there should be a
diversity of E1s carrying the signaling links and
hence set a limit of 8 signalling links per E1.
Max 8 SLs per E1
requirement.
171. SGW GR
Clause
2.1.6
Please define how many signalling links are
required per E1 for High Speed Signalling links
It will be 2 Mbps as per
Q.703.
172. SST GR
clause
2.3.5
As per the clause, it shall be possible for a
Softswitch to act as primary Softswitch and
secondary Softswitch. Secondary Softswitch
shall be re-configurable to control the media
gateways originally controlled by a primary
Softswitch by loading office data from a remote
NMS, in case of failure of primary Softswitch.
Please clarify as same SS is supposed to act as
primary & secondary for other domain. In such
case it will require extra hardware to support
primary SS MGWs.
Yes. However, each
Softswitches is to be
dimensioned for full 4
MBHCA and 6 MBHCA
in overload condition.
173. SST GR
Clause
2.3.6
As per clause 2.3.6 of Softswitch GR, the
Softswitch is required to support 6M BHCA. As
per the network requirement of BSNL for the
200KC tender, the requirement of 6Million is
too high. The BHCA required per Softswitch
required in the network will not exceed 4
Million even after taking into consideration full
expandability of the network. Hence BSNL
should not ask for a BHCA of more than 4
Million which would be more in line with the
network architecture and the call load in the
network.
No change in
requirement.
174 SST
GR
Clause
2.8.3
As per the clause the Softswitch should support
CS1 with CS2 functionality in the future.
However as per the NGN architecture, the
protocol defined between the Softswitch and IN
is SIP. SIP is the technology that would be used
in the future for all interactions between
Softswitch and SCP. We hence recommend that
BSNL agrees for SIP as an alternate to CS1 for
IN-Softswitch interface
No change in
requirement. Refer
clarification above also.
175. SST GR
Clause2.1.
Transport over TCP and UDP shall be provided
for H.248/Megaco & SIP- T protocols.
No change in
requirement.
7
TCP is a Connection Oriented protocol.
Using them in network will result in clogging
of the network due to window sizing and
acknowledge messages. In our solution H.248
and SIP-T both use UDP currently.
176. SST GR
Clause 2.5
As per the clause, the Softswitch shall be able
to control 200 MGs. However as per the traffic
statistics and given the BHCA capacities of the
softswitch, the SSW cannot control more than
35 Media Gateways.
Assuming 4K as the capacity of the Media
gateway (which is the smallest MG as per the
MGW GR clause 3.3), 60sec as CHT and 0.7erl
traffic per trunk, a Softswitch of 6Million
BHCA can control only 35 Media gateways.
hence we strongly recommend that this
requirement of controlling 200 MGs per MGC
is illogical and hence may be relaxed for this
tender.
Softswitch should be
capable of controlling
200 TMGs.
177. SST GR
Clause
3.2.1.7
Please note that LCR functionality is not
required for NLD operations specially since
BSNL has their own backbone. Since LCR is
more applicable to ILD operations, it is
suggested that LCR requirement may be made
optional.
Quotes for LCR is
optional.
178. TMG GR
Clause
3.7.3
………...The MGW shall also monitor traffic
given over the voice paths over LSPs to initiate
the process of bandwidth increase/decrease of
an LSP.
MGW doesn't control LSPs, it will only mark
the packets.
The MGW shall also
monitor traffic given
over the voice paths and
generate required quality
deterioration alarms.
179. TMG GR
Clause
3.10
NTP: It shall synchronize to the NTP (Network
Time Protocol) server available in the network
and use this timing information for time
stamping of all protocol messages including
NTP.
If MGW is to be synchronized with NTP then
there shall be no need of L2 Clock.
Refer clarification above
please.
180 Clause
A
2.1.0, 2.3
Section
IV
The requirements (a) turnover of INR 1000
Million over last two years for the bidder (b) an
additional requirement of 1000 INR for soft-
switch manufacturers and (c) additional
requirement of INR 500 million over the last
two years for the media Gateway / core block
manufacturers is very stringent. As a
consequence of this requirement many
manufacturers do not qualify for the bidding in
Refer clarification above
please.
the IP TAX tender. We request BSNL to relax
this requirement as it was also relaxed in earlier
tender vide clarification no 55 page 12 issued
last time for the IP TAX tender. BSNL has
replied that “Lead Bidder should have a
turnover of INR 1000 million including
principal of Soft switch manufacture.”
We request BSNL to confirm that the above
clarification holds good for this time as well.
181. NIT
It is mentioned in the NIT that the “Purchase
Preference Policy is applicable for this tender.”
You are requested to please clarify as what is
Purchase Preference Policy and what is the
scope of its applicability?
Purchase Preference is
not applicable in this
tender.
182. Clause
7(c)
Section II
There are 20 TEC GRs which are required to be
complied in the Tender. As you are aware that
making the soft copies and submit the
compliance of each and every clause of these
GRs makes the entire process lengthy and also
increase the size of the bid. Instead, bidder
should be allowed to submit one undertaking /
compliance statement for each and every GR
mentioning that “We comply each and every
clause of TEC GR No. xyz”. You are requested
to please allow that same. Over and above
Statement of Deviation, if any, shall be required
to be submitted.
Request is regretted
please.
183. Clause
10(v)
Section II
TAC / TSEC
As we all are aware that this is a new and latest
technology for which no Purchase Order is yet
placed by BSNL in past and being a new
technology there is no vendor who has the TAC
or TSEC for the product as of now. This tender
is not only for one item but the successful
vendor is required to supply multi products.
Keeping in view the above facts you are
requested to please waive the condition of TAC
/ TSEC and also Form B. However, after
opening of bids the successful bidders should
go for the validation instead of TEC/TSEC.
This will make the tender process bit easy and
will allow a healthy competition.
Refer clarification above
please.
184. Clause
10.4
Section II
We understand that only successful bidders are
required to submit the samples and it is not a
pre-requisite to submit the bid. You are
requested to please clarify the same.
Yes please.
185. Clause
19.3
Section II
You are requested to clarify as whether the
financial bids will be opened on the same day or
it is a 2 stage bid.
Refer Section IV.
186. Clause 6
It has been observed that in many cases after
Request is regretted
Section
IV Part I
signing the MOU and participating in the tender
with any Technology Provider than they go
back with their commitments. You are
requested to please allow Indian Bidders to
change the Technology even after opening the
Bids with a condition that the changed
technology shall be a technically and
commercially approved.
please.
187. Clause D
2.10
Section
IV Part II
i) You are requested to please clarify as on how
many bidders the orders will be placed.
ii) We suggest that orders shall be placed on 2
lowest and technically qualified bidders.
i) The clause is self
explanatory.
ii) Request is regretted
please.
188. Clause E
2.11
Section
IV Part II
Delivery Period
You are requested to please clarify the exact
period as the same is not clear in the tender
document. We suggest and request that the
delivery period shall be 8 months commencing
from the date of issuance of Purchase Order not
the APO. Please clarify.
Request is regretted
please.
Annexure-I
Line Printer
Print Speed
24 p.p.m.
Fonts True
Type
Processor
RISC based (with atleast 250 MHz
Clock)
Memory
16 MB (minimum)
Duty Cycle, Pages / month
150,000
Paper Trays
4
Media Type
Shall support legal, letter, A4 size, 132 C
Resolution 1024X1024
dpi
The printer shall be compatible with MS Windows 95 or higher version, Windows NT 4 or
higher, MS DOS, UNIX & UNIX derivative like SOLARIS, HP-UX etc.
Laser Jet
Print Speed
10 p.p.m.
Fonts True
Type
Processor
RISC based (with atleast 250 MHz
Clock)
Memory
10 MB (minimum)
Paper Trays
2
Media Type
Shall support legal, letter, A4 size
Media Size Customization
3X5 inch to 8.5X14 inches
Resolution 1200X1200
dpi
The printer shall be compatible with MS Windows 95 or higher version, Windows NT 4 or
higher, MS DOS, UNIX & UNIX derivative like SOLARIS, HP-UX etc.
