tamil nadu fibrenet corporation ltd (tanfinet) · 2020. 11. 5. · tamil nadu fibrenet corporation...

TANFINET Corporation Corrigendum _009

Tamil Nadu FibreNet Corporation Ltd (TANFINET)

Selection of Master System Integrator for Survey, Supply, Installation, Commissioning and Operation &

Maintenance of Optical Fibre Network (OFN) in Tamil Nadu under BharatNet Phase- II

Tender Reference: NIT_TANFINET_002_Corrigendum_009

Corrigendum No. 09 for Package A, B, C & D

Date:05 Nov 2020

Tamil Nadu FibreNet Corporation Ltd.,

807, 5th floor, Chengalvaraya Naicker Maaligai,

Anna Salai

Chennai – 600 002

Phone: 044-28888230

e-mail: [email protected]

Website: www.tanfinet.tn.gov.in

Confidential 1


S.No Clause No. Page No. Existing Clause Clarification sought Corrigendum / Clarrifications

1 Corrigendum

08_4.5.1 Sl.

No. III 3 ,4 &5

136 TEC/GR /TX/PON-02/01/ May 2013 With latest

amendments

TEC/GR/TX/PON-02-01/May 2013 is

superseded by TEC-GR-FA-PON-002-02-

NOV-18. 2013 GR is obsolete and no state

body or BBNL has referred this GR after Nov

2018. Hence kindly request to use the NEW

GR rather than using the OLD GR.

TEC/GR /TX/PON-02/01/ May 2013 With

latest amendments will be accepted

2 Corrigendum

08_6.2.5

146 For seamless integration of State level EMS /

NMS / OSS with BBNL's domain specific

BBNL NMS, the State's EMS / NMS / OSS

shall support e-ToM based external interfaces

in each functionality. The following external

interface mechanism is expected from State's

OSS.

(i) APIs using RESTful webservices

(ii) Notifications using JMS services to Apache

Active MQ middleware

(iii) Both the above interfaces shall contain

XML Objects using JAVA

Kindly inculde the support of TM-814 CORBA

NBI Interface as well which is asked in all

BBNL and State Tenders. Hence kindly

include TM814 CORBA interface and CDOT

NMS has integrated the CORBA interface as

part of BBNL GPON Tender and is running

successfully in the BBNL NOC at Bengaluru

and Delhi.

RFP Conditions prevail. Minimum functional

requirements have been detailed based on

network requirement. MSI / SIs to propose

Suitable Solution based on functional

requirement meeting the specification &

SLAs as defined in the Tender

3 Corrigendum

08_6.5.1

150 One spare PON card at each OLT to be

provisioned (N+1)

The OLT requested is not a chassis based

OLT and this clause contradicts the

requirement of Corrigendum 003

To be read as: In case of 4 Port Mini OLT:

The offered OLT should be expandable to

support additional 4 x GPON interfaces for 4

port OLT.

In-case of 8 Port Mini OLT, no spare PON

card at each OLT to be provisioned (N+1)

The Survey guidelines: Clause 6.5.1 Sl. No.

32, 34 & 35 Stand deleted.

4 Sl.No. 83 of

GPON

Specifications

Page No. 37

623 For Sl.No. 83 of GPON Specifications Page

No. 37 the clarification was " We understand

that proposed GPON solution should comply

with TEC GR as mentioned in this clause and

No TSEC/TAC is required.

The response provided by TANFINET is "Yes

the Understanding is correct "

"We would like to double confirm that for

GPON solution the product has to be complied

to the GR mentioned in the

tender/corrigendum and no TSEC/TAC is

required.".

Please confirm.

Refer Part 1 of Corrigendum

Confidential 2



5 5.2.27 35 Support for the Building Integrated Timing

Supply (BITS), 10 MHz and 1 pulse per

second (1PPS) interfaces. Supports

synchronous Ethernet (SyncE) and IEEE-1588

functionalities, and Shall act as the source for

network clocking for TDM, SDH and

SONET and SyncE interfaces. In addition to

the timing services

1588/SynCE features have to work end to end

in the telecom network. The ONT

requirements do not mention the need for

1588/SyncE. Having 1588/SyncE in the OLT

does not serve the intended purpose unless

the ONTs are capable of recovering the

1588/SYNCE clocks. Moreover the timing

requirements are removed in the

corrigendum008. Since timing requirements

are removed in the Corrigendum this clause

dosnt serve the purpose. Moreover None of

the State/BBNL GPON tenders have

requested this feature. Request kindly to

remove the clause.

Support for Building Integrated Timing



synchronous Ethernet (SyncE) or NTP, and

shall act as the source for network clocking

for TDM, SDH and

SONET and SyncE interfaces in addition to

the timing services

6 5.2.75 37 The OLT shall be designed to Operate at 210-

250 V ac

Dual Redundant Power supplies

Operating temperature: 0 to 65 centigrade

As per TEC GR GPON 2018 the operating

temperature specified is 0 to 50 degrees and

is the requirement in all State/BBNL GPON

Tenders. We kindly request you to modify the

clause as per TEC GR

RFP conditions prevail

7 5.2.48 35 ITU-T G.987.1: XG-PON, General

requirements

Not applicable for TANFINET GPON network

as there is no XGPON interfacess to be

delivered as UNI/Subscriber interface .

Moreover the Corrigendum 008 has

mentioned that the proposed requested

equipment for revenue villages is only GPON.

hence kindly requesting to remove the

same.This is not removed in the

Corrigendum008

Deleted

8 5.2.49 35 ITU-T G.987.2: XG-PON, Physical media

dependent (PMD) layer specification









Corrigendum008

Deleted

Confidential 3



9 5.2.50 35 ITU-T G.987.3: XG-PON, Transmission

convergence (TC) specifications







hence kindly requesting to remove the same.

This is not removed in the Corrigendum008.

Deleted

10 5.2.51 35 ITU-T G.988: XG-PON, ONU management

and control interface (OMCI) specification









Corrigendum008

Deleted

Confidential 4



11 7 - Bid

Evaluation -

7.19 (Point no

6)

Sr. No. 19 of

Corrigendum 8

57 of tender

and 10 of

Corrigendu

m 8 dated

29.10.20

Note 2: All the tender items as per Part 4 –

Annexure 12 of Corrigendum_008 (If

applicable) shall have valid Type Approval

Certificate (TAC) from Telecom Engineering

Centre (TEC), New Delhi or Technical

Specification Evaluation Certificate (TSEC)

from Quality Assurance Circle, BSNL,

Bengaluru, against the respective technical

specifications of this Tender. In case any of the

quoted models does not have TAC/TSEC then

it should be applied for TSEC to Quality

Assurance Circle, BSNL, Bengaluru or to TEC,

New Delhi for the model against the technical

specifications, at least one day before the

opening of the tender. The registration number

allotted for the TSEC purpose by Quality

Assurance Circle, BSNL, Bengaluru or for TAC

purpose by TEC, New Delhi shall be submitted

along with the bid. However, only type-

approved products as per above specifications

shall be accepted which shall have to be

obtained before issuing Work Order by the

purchaser.

Please refer Part 4 Annexure 9 - Technical

Specification for 96F UG OFC issued is

same as per Technical specification of

BSNL Tender No. MM/BN II/OFC/T-680/2020

dated 11.03.2020. Please confirm that

TSEC obtained by the OEMs of the Bidder

against Tender no. MM/BN II/OFC/T-

680/2020 dated 11.03.2020 issued by BSNL

shall be acceptable to supply & participate

against this tender.


12 1.4.11 Video

Wall with

Controller

63 Minimum 34560x 4320 pixels, based on Laser

DLP Rear projection technology

34560 X 4320 Pixels is specific to only One

OEM & Propriteary .Request you to Consider

Minimum ( Full HD ) or better so that other

OEM Can Participate in tender & have Fair

tendering Process

Pre Bid responses released on 29.10.2020

Refers corrigendum Part 4 but same is

missing


13 1.4.11 Video

Wall with

Controller

63 To Add - Specifications for Video wall Display

is not there

Laser Based Video wall in 70" Full HD or

better with Minimum onscreen brightness of

700 Nits



missing


Confidential 5



14 1.4.11 Video

Wall with

Controller

63 To Add - Specifications for Video wall Display

Controller is not there

Controller should be based of Intel Xeon Octa

Core 2 Ghz with Minimum 8 Inputs with 32GB

RAM & 1 TB HDD



missing


15 1.4.11 Video

Wall with

Controller

63 Please clarify the Dimensions available at site

for Video wall Placement in terms of Width &

height

Please clarify the Dimensions available at site

for Video wall Placement in terms of Width &

height as currently only resolution is

mentioned which is not correct way for arriving

the BOQ



missing

Will be shared with the successful bidders

for their respective packages post award

16 Warranty 6.20.2 -

Warranty

&

2.16 - MAF

from OEM

Package A

B C D

Corrigendu

m 8 Page 8

6.20 Warranty

6.20.2 The respective OEM shall provide

technical Support, spares and service support

as prepurchased for the supplied equipment

for a period of 7 years from the date of Go-Live

as per tender terms.

6.20.9 During the warranty period, the

Bidder(s) shall provide all product(s) and

documentation updates, patches/fixes, and

version upgrades within 30 days of their

availability and should carry out installation and

make operational the same at no additional

cost to Purchaser. Beyond the O&M period of

3 years, the OEMs have to the extend the

required support and warranty with respect to

all product(s) and documentation updates,

patches/fixes, and version upgrades within 30

days of their availability and should provide

technical support for installation and make

operational the same at no additional cost to

Purchaser.

We understand that TANFINET require

Warranty with spare for 7 years from the date

of Go-live. However 3 years of O & M onsite

support, starting from date of Go-Live would

be provided by respective MSI/SI. The offsite

extended warranty with spare for additional 4

years shall be provided by respective OEMs.

Please clarify whether the warranty required

with spare replacement for extended 4 years

or not.


Confidential 6



17 Annexure 4

1.5 (1.5.1)

S-NOC

Corrigendu

m_008

Page no.35

MSI shall provision for (on rotational shift

basis) in the S-NOC room of approximately

3000 Sq ft. The MSI shall provide the

necessary infrastructure such as furniture,

fixtures, PSTN phones, other services with the

following per Workstation:

o Data- 4 ports

o Voice- 2 ports

o Raw Power- 2 Nos., 5/ 15 Amps

o UPS Power- 3 Nos., 5/ 15 Amps

Please specify the dimension (Height x Width

x Breadth) for the Centralized Operation

Centre along with the Provisional Data &

Voice Points counts for the other parts like

Coneference Room, Reception Area, Material

Handling Room etc. (as we have considered

10 Work stations and respective Data & Voice

Points at S-NOC)



18 1.5.13 Rack

42U

Point IX and X

PACKAGE

A - PART 4

Page : 77

Power Distribution Unit 2 nos - 06/16 Amp

universal socket-6 socket- single pole / screw

Mountable / 32 Amp MCB / Alternating Current

– Indicator – Black Fine Tex. – Assembly

Intelligent PDU (iPDU) should come with

C13/C14 , C19/C20 compatible sockets and

not in Universal socket

Kindly confirm bidder should consider iPDU

with C13/14 and C19/20 Sockets instead of

Universal socket


19 1.26.5.3

Earthing

PACKAGE

A,B,C & D -

PART 5

Page : 63

The BPSC/VPSC or any other Government

building where the nodes are to be located

may or may not have the earthing facilities.

Hence the Purchaser has proposed to install

standard earthing in all the nodes. In case of

the Block, Super GP and Type 1 GP, there

shall be Body earthing and UPS earthing and

in case of Type 2 GPs there shall be Body

earthing only.

we understand that Body Earthing and UPS

earthing at Block level is required & body

earthing at all GP location & Revenue villages

is required. Kindly confirm

Yes, the understanding is correct

20 2.34 Form 34

– Un-Priced

Bill of Material

IV : Radio

Infrastructure

Point : 1&2

PACKAGE

A - PART 3

Page : 59

1 : Supply, installation, testing and

commissionig of RF equipment (Outdoor and

Indoor) at Block including all accessories i.e.

Mast, cabling, earthing, etc. QTY : 12

We understand the Qty. asked is count of GP

& In case if 1+1 HOT-Standby Redundancy is

required. it should be 24 Links for 12 GPs.

Please confirm

The clause is self-explanatory

Confidential 7



21 1. Scope of

Work

Point : 1.1.3

PACKAGE

A - PART 2

Page : 03

Primary objective of BharatNet project is to

provide connectivity of 1 Gbps at each Gram

Panchayat in case of wired media and 100

Mbps, scalable to 1Gbps if the connectivity is

through radio. The scope of work for the MSI &

SIs shall include survey, supply, installation,

testing, commissioning, operations and

maintenance

during the period of the contract of the end-to-

end network infrastructure including all active

and passive network components, from Block

to Gram Panchayat.

Reference: TEC/GR/R/ISM-MOD-001/04.MAR

2016

As Per TEC GR the throughput is 100 Mbps.

so we understad that required maximum

throughput is 100 Mbps

Kindly Confirm


22 7 - Bid

Evaluation

7.1.11

PACKAGE

A -

Page:58

The TSEC obtained by the OEMs of Bidder(s)

for the various tenders floated by BBNL/BSNL

in the last two years shall be acceptable for the

items which are part of this Tender provided

that the technical specifications remain

unchanged. In case of OFC, any change in

source of raw material shall be subject to fresh

TSEC process of QA. The Routers shall have

the certifications as mentioned in Part 4:

Technical Requirement Specifications

Technical Specifications.

Please confirm that the TSEC obtained by the

OEMs of Bidder(s) for the various tenders

floated by BBNL/BSNL in the last two years

shall be acceptable for the items which are

part of this Tender provided that the technical

specifications remain unchanged


23 1.8.2

Online UPS

(1 KVA)

( Sr. No. 1)

PACKAGE

A -

Page:311

Capacity : 1KVA/900W As per industry standard 0.8PF is preferred

upto 3kva UPS rating. We request to modify

as "1KVA /900W to be replace with 1KVA

/800W".

Kindly confirm


24 1.8.2

Online UPS

(1 KVA)

( Sr. No. 10)

PACKAGE

A -

Page:311

Output Voltage:200/208/220/230/240Vac shall

be available with +/-1% regulation in battery

mode

We request to modify the Output voltage as

per Indian Conditions, generally the nominal

output voltages required is 220/230/240VAC.

Nominal voltage of 200V / 208V A, which is

not required as far as Indian Power supply is

concerned. Please modify the voltages.

Kindly confirm


Confidential 8



25 1.8.2

Online UPS

(1 KVA)

( Sr. No. 12)

PACKAGE

A -

Page:311

Output Power factor :0.9 As standard industrial practice design for small

rating like 1KVA Online UPS is based on

0.8PF . Howver with 0.9PF is optional

available. So please confirm whether the

capacity requirement is w.r.t 0.8 PF for 800W

or w.r.t 0.9 PF for 900W.

Kindly confirm


26 1.8.2

Online UPS

(1 KVA)

( Sr. No. 24)

PACKAGE

A -

Page:312

Charger:

Min. 15 amp inbuilt (for any future expansion of

back-up time). Charger shall be settable for

1/2/4/6/8/10/12/14 A ratings as per the need of

battery charging

We request to add as Charger should be 10 %

of battery rating AH.

Kindly confirm


27 1.8.2

Online UPS

(1 KVA)

( Sr. No. 25)

PACKAGE

A -

Page:312

Environmental Parameter:

(a).Operating temperature range:

0-40 deg C with full load @ 0.9PF. Later

de-rating applicable upto 50 deg C

.9 PF to be replaced with .8PF aaccording to

the Sr. 12 of specifications. Please modify

Kindly confirm


28 1.8.2

Online UPS

(1 KVA)

( Sr. No. 27)

PACKAGE

A -

Page:312

b)

Fault Indication (On LCD):

Bus start fail, Bus over & under, Inverter soft

start failure, Inverter voltage high & low,

Inverter output short, Battery voltage high &

low, charger output short, over temperature,

overload, charger failure, over input current,

over input current, battery not connected, over

charge, EPO enable, Programmable output

enable.

We request to remove over input current (As

over input current protection is availble in UPS

via miniature breaker and electronic

protection.)


29 1.8.2

Online UPS

(1 KVA)

( Sr. No. 28)

PACKAGE

A -

Page:313

Manufacturer

Manufacturer - > ISO 9001, TL 9000, ISO

14001 & OHSAS 18001 (ISO & OHSAS for

Indian Operation of OEM only) . CE, FCC,

certificate of compliance from indian certifying

agency

(TL 9000: Deleted as per Corrigendum_008.

TL9000 certification is applicable for telecom

products only.)

We request you to replace OSHAS 18001 with

ISO 45001.

Please confirm.


Confidential 9



30 1.8.1 Online

UPS

(6 KVA).

Sr.No 9

PACKAGE

A -

Page:307

Nominal Voltage :

200/208/220/230/240 VAC

We request to modify the Output voltage as

per Indian Conditions, generally the nominal

output voltages required is 220/230/240VAC.

Nominal voltage of 200V / 208V A, which is

not required as far as Indian Power supply is

concerned. Please modify the voltages.

Kindly confirm


31 1.8.1 Online

UPS

(6 KVA).

Sr.No 9

PACKAGE

A -

Page:307

Overall Efficiency (AC to AC) - Online (Double

Conversion):

Online Mode 92%, eco mde .98%

We request you to modify the online mode

efficicency to 94% (Higher efficiency is

referred for above 3kva UPS rating to save

energy consumption.)

Kindly confirm


32 1.8.1 Online

UPS

(6 KVA).

Sr.No 52

PACKAGE

A -

Page:307

Noise Level should reduce with Load

(Mandatory) :

< 50 dbA at 1 meter distance

Request for changes Noise Level should

reduce with Load (Mandatory) : < 55 dbA at 1

meter distance

(As per industry standard for 6kva UPS noise

will be 55 db)

Kindly confirm


33 1.4.10

Online UPS

(60kVA)

Sr. No 9

PACKAGE

A -

Page:278

Total Harmonic Distortion at 100% Non-Linear

Load :

< 3% for non-linear load

We request to modify as "< 2% (linear load), <

5% (non-linear load3)"

Please clarify


34 1.4.10

Online UPS

(60kVA)

Sr. No 13

PACKAGE

A -

Page:278

Over Load Rating:

125% for 10 minutes 150% for 60 seconds

We request to modify as

<105%, long time; <110%, ≤1hr; <125,

≤10min; <150, ≤1min

Please clarify


35 1.4.10

Online UPS

(60kVA)

Sr. No

20,21,22,23,24

PACKAGE

A -

Page:279

The UPS should have Battery Management

feature for:

Periodic Battery Test

Controlling Charging Time and Current

Increase in Battery Life

Protection : Battery low Cut-off without

draining current

Request you to confirm Whether Additional

monitoring System Required or As per Battery

OEM standard battery OEM standard

Please clarify


Confidential 10



36 1.4.10

Online UPS

(60kVA)

Sr. No

32,33,34,35,36

,37,38

PACKAGE

A -

Page:280

Compliance:

CE Certificate - EN 62040-1-2 EN 62040-2

Class A IEC 61000-4-2 Level 4 IEC 61000-4-3

Level 3 IEC 61000-4-4 Level 4 IEC 61000-4-5

Level 4 IEC 61000-4-6

We request to modify Compliance as

"UPS system has designed & manufactured in

accordance with the following international

standards.

IEC EN 62040-1-2 general & safety req;

IEC EN62040-2 EMC requirements;

IEC EN62040-3 operating requirements;

Surge withstandability EN61000-4-5, level3"

Please clarify


37 Bid Evaluation

7.1.11 Note 2

10 Note 2: All the tender items as per Part 4 –

Annexure 12 of Corrigendum_008 (If

applicable) shall have valid Type Approval

Certificate (TAC) from Telecom Engineering

Centre (TEC), New Delhi or Technical

Specification Evaluation Certificate (TSEC)

from Quality Assurance Circle, BSNL,

Bengaluru, against the respective technical

specifications of this Tender. In case any of the

quoted models does not have TAC/TSEC then

it should be applied for TSEC to Quality

Assurance Circle, BSNL, Bengaluru or to TEC,

New Delhi for the model against the technical

specifications, at least one day before the









purchaser

Please clarify whether we can submit TSEC /

QF 103 obtained by OEMs of Bidder(s) for

the various tenders floated by BBNL/BSNL in

the last two years and TSEC/ QF103 obtained

against previous tender reference floated by

TANFINET shall be acceptable for the BoQ

items which are part of this Tender provided

that the technical specifications remain

unchanged. QF103 with registration number

alloted for the TSEC purpose by Quality

Assurance circle, BSNL Bengaluru can be

submitted along with bid.


Confidential 11



38 BOQ_2182

02

Provide GST in % (B) The calculation of GST is in price bid format is

not correct. For example, for 18% GST, the

formula is taking 0.18% only. Request to make

necessary changes in the price bid format.

Only figure is to be put in the column for

GST without the percentage symbol

39 Definition No.

14 & 15

Response

to Prebid

queries

1421/Page

353

Capex Value-70% of the Grand Total cost

Opex Value - 30% of the Grand Total cost

Corrigendum: It is exclusive of GST / Taxes

There is a contradiction in the corrigendum

clauses, as per price bid format and the note

given in the price bid, the quoted price should

be inclusive of GST wherea in prebid

response query no. 1421, it says the capex

and opex should be exclusive of GST.

Request clarification on this.


40 Note 4,

Instructions to

fill the

Financial Bid:

84 The quoted prices should be inclusive of all

Taxes, Duties & Levies except GST. GST shall

be paid as per actual.

There is a contradiction in the corrigendum

clauses, as per price bid format and the note

given in the price bid, the quoted price should

be inclusive of GST wherea in prebid

response query no. 1421, it says the capex

and opex should be exclusive of GST.

Request clarification on this.


41 7.1.15 12 The Financial bids of technically qualified

Bidder(s) alone shall be opened for Financial

bid evaluation. The number of packages that

will be awarded to a bidder is one for this

project subject to the provisions of 7.1.15 (iii)

Bidder(s) desirous of bidding for more than a

Package shall record the preference order on

the Bid Format while populating the Financial

Bid Form.

There is no provision in financial bid to record

the preference, however Form P4 is given to

submit the preference list. We understand the

the preference list be submitted as per Form

P4 only.

Please confirm.


42 2.37 63 Form P2- Financial Bid Do we need to submit two price bid one at

given in Form 2 wherein details of HSN/ SAC

code is asked and another file which is to be

uploaded on the portal and doesn’t have

HSN/SAC code column. Please confirm.

Yes, the understanding is correct, All

Financial Bid forms to be uploaded in .RAR

folder and to be uploaded as part of

Financial Bid

Confidential 12



43 NA BOQ_218202(Excel File) Do we need to submit two price bid one at

given in Form 2 wherein details of HSN/ SAC

code is asked and another file which is to be

uploaded on the portal and doesn’t have

HSN/SAC code column. Please confirm.

Yes, the understanding is correct, All

Financial Bid forms to be uploaded in .RAR

folder and to be uploaded as part of

Financial Bid

44 BOQ_218202 SOR Item

no. 1

Element Management System for UPS

Element Management System for GPON

Element Management System for IP-MPLS

Routers

Do we need supply the EMS of Router, GPON

& UPS in HA, in Active-Passive at SDC for S-

NOC similar to GIS solution. Please confirm.

Please also provide the detailed specification

of EMS H/W.


45 6.20.2 -

Warranty

8 The respective OEM shall provide technical

Support, spares and service support as pre-

purchased for the supplied equipment for a

period of 7 years from the date of Go-Live as

per tender terms.

We understand the OEM warranty support to

be provided for 7 years post Go-Live, please

clarify the following ponts:

1. Post O&M of 3 years, warranty support to

be covered by OEM directly and there would

not be any engagement of MSI during this

period.

2. Cost of addtional 4 years warranty, post

O&M period of 3 years to be includeded in the

financial bid.

Please confirm.


46 Definition No.

14

5 80% of the Total Project Cost (CAPEX +

OPEX)

We are not clear on this clarifcation. Please

elaborate the break of 80% and 20%, and its

implications on the financial bid.


47 Definition No.

15

5 20% of the Total Project Cost (CAPEX +

OPEX)

We are not clear on this clarifcation. Please

elaborate the break of 80% and 20%, and its

implications on the financial bid.


48 134,

Annexure-

12

TEC/GR /TX/PON-02/01/ May 2013 With latest

amendments

TEC/GR/TX/PON-02-01/May 2013 is

superseded by TEC-GR-FA-PON-002-02-

NOV-18. 2013 GR is obsolete and no state

body or BBNL has referred this GR after Nov

2018. Hence kindly request to use the NEW

GR rather than using the OLD GR.


Confidential 13



49 6.2.5 146 For seamless integration of State level EMS /






OSS.






Kindly inculde the support of TM-814 CORBA

NBI Interface as well which is asked in all

BBNL and State Tenders. Hence kindly

include TM814 CORBA interface and CDOT

NMS has integrated the CORBA interface as

part of BBNL GPON Tender and is running

successfully in the BBNL NOC at Bengaluru

and Delhi.







50 32 150 One spare PON card at each OLT to be

provisioned (N+1)

The OLT requested is not a chassis based

OLT and this clause contradicts the

requirement of Corrigendum 003




port OLT.



The Survey guidelines: Clause 6.5.1 Sl. No.

32, 34 & 35 Stand deleted.

51 5.2.27/ Corrigendu

m 3, Page

35

Support for the Building Integrated Timing







the timing services

1588/SynCE features have to work end to end

in the telecom network. The ONT

requirements do not mention the need for

1588/SyncE. Having 1588/SyncE in the OLT

does not serve the intended purpose unless

the ONTs are capable of recovering the

1588/SYNCE clocks. Moreover the timing

requirements are removed in the

corrigendum008. Since timing requirements

are removed in the Corrigendum this clause

dosnt serve the purpose. Moreover None of

the State/BBNL GPON tenders have

requested this feature. Request kindly to

remove the clause.






for TDM, SDH and


the timing services

Confidential 14



52 5.2.75 Corrigendu

m 3, Page

37

The OLT shall be designed to Operate at 210-

250 V ac

Dual Redundant Power supplies

Operating temperature: 0 to 65 centigrade

As per TEC GR GPON 2018 the operating

temperature specified is 0 to 50 degrees and

is the requirement in all State/BBNL GPON

Tenders. We kindly request you to modify the

clause as per TEC GR



m 3, Page

36

ITU-T G.987.1: XG-PON, General

requirements









Corrigendum008

Deleted


m 3, Page

36

ITU-T G.987.2: XG-PON, Physical media

dependent (PMD) layer specification









Corrigendum008

Deleted


m 3, Page

36

ITU-T G.987.3: XG-PON, Transmission

convergence (TC) specifications







hence kindly requesting to remove the same.

This is not removed in the Corrigendum008.

Deleted

Confidential 15




m 3, Page

36

ITU-T G.988: XG-PON, ONU management

and control interface (OMCI) specification









Corrigendum008

Deleted

57 Responseto

Queries_Cl

arifications_

29_10_2020

Serial No.

165

One Time Site Preparation cost for all Civil &

Electrical Works including proper earthing at

GP & Block

We understand that the L1 bidder will do the

survey for the site fitment. Howeber it is not

possible to estimate the GP & Block

requirement at bid stage.

Therefore you are requested to specify brief

site requirement so that bidders can estimate

the cost on same specifications and

requirements.


58 BOQ_218202 SOR Item

no. 1

Element Management System for UPS

Element Management System for GPON

Element Management System for IP-MPLS

Routers

You are requested to kindly provide the

specifications & features set of various EMS

asked in this RFP.

MSI / SIs to propose Suitable Solution

based on functional requirement meeting

the specification & SLAs as defined in the

Tender

59 PART 4 -

Annexure 10

4.3.4

131 FDMS Specs for 96Fibre : Preloaded SC-PC

as per TEC GR TX/OFJ-01/05 NOV 2009 - 48

Nos

We need 96 nos of preloaded adaptors for 96

Fibre FDMS Module but it is given as 48 Nos

in the requirements. Please confirm and also

clarify whether it is Simplex or duplex.




Tender

60 PART 4 -

Annexure 12

4.5.1

135 Fibre Patch Cords (1M, 3M, 5M, 10M) Please confirm the connector (SC-PC/SC-

APC) , Fibre categoty(G652D/G657A1) and

Connector type (Simplex/Duplex) for the all

the Patch Cords .




Tender

Confidential 16



61 Tender

Schedule – Sr.

No 16

12 Last Date of Submission Request you to extend the due date of

submission of tender at least by 3 weeks

Since clarifications/ corrigendum have been

issued on 29th October, 2020,we need 1-2

weeks' time to study the changes/

corrigendum and to incorporate /modify our

Bid so.

(2) Due to COVID-19 pandemic restrictions, all

required movements become sluggish, hence

delaying our Tender preparation works

including estimation of the project costs, which

includes OEM/ Vendor Supply cost inputs, site

overheads, etc.


62 clause

no.1.4.5 EMS

in HA -

Helpdesk -

Part 4

36 The proposed solution shall be based on

industry standard best practice framework&

must be certified with eleven commonly used

ITIL Processes.

Dilute the reference to eleven process of ITIL.

The Software Assessor provides for 3

categories of validating the products with

process adoption namely Gold, Silver and

Bronze under product software endorsement

scheme. Axelos certifies products in addition

to certified partners such as Pink elephant and

GLENFIS AG.

We have certified our product with GOLD

certification having 5 processes which we

believe are very relevant to the Helpdesk. The

process we have certified are Incident

Management, Problem Management, Event

Management, Change Management and

Service and Asset Management.


63 Tender

Schedule – Sr.

No 16

12 Last Date of Submission Request you to extend the bid submission

date by atleast 2 weeks i.e. from existing

11.11.2020 to 25.11.2020.


Confidential 17



64 Technical

Specifications

Core Router , Switches , Block Router’s and

GP router’s

Current specification is favouring to single

OEM. During pre bid meeting which was

conducted without consultant, We raised

queries related to restrictive clauses, technical

specifications and other designing related

issue but none of our queries addressed in

corrigendum. Current restrictive clause other

leading and Domestic OEM to participate and

also not allowing a level playing field across

the OEM’s.


65 Technical

Specifications

Network Design The design of Network are not matching with

interface and performance of products, current

network design are favouring to a single OEM

product. The architecture planned and the

specifications which has been mentioned is

blocking from Day-1 which will degrade the

network performance. This points is raised in

pre bid meeting and agreed by conveyer of

Pre bid meeting.


66 Site Survey Site Survey - SNOC we wish to conduct site survey for SNOC

along with Block and GP to estimate the

efforts and conditions .



67 corrigendum 8

, Annexure-9,

Clause no

1.4.1. 3

Page No.

123 of Part -

4

Marking for user’s identification on all type of

OFC (24F ADSS OFC Type-2A, 48F ADSS

OFC Type-2A & 96F Ribbon type OFC) is to

be printed on sample cables during obtaining

TSEC.

For this we require the “ user identification

name”.

Hence we would request TANFINET to kindly

arrange to clarify our query and provide the

user identification name please.



Confidential 18



68 Tender

Schedule – Sr.

No 16

12 Last Date of Submission With reference to your corrigendum 8 and

Response to the queries dated 29th of

October 2020 against your tender enquiry

number NIT_TANFINET_002 dated

03.10.2020, as total number of responded

queries are very large it is required more time

to study the same .

Considering time required to study the

queries and corrigendum we request you

kindly extend the last date of submission of

Bid from present last day at-least by 10 days.


69 Bidders

Experience

: Supporting

Documents

required for

Annexure 2:

Package A, B,

C & D –

Section 7,

Clause No 4 &

5,

Page No 13

to Page No

25 as per

Corrigendu

m.

Bidders Experience: Supporting Docuements

Satisfactory Completion Certificate issued &

signed by the competent authority of the client

entity along with the supporting documents

such as work order/purchase order clearly

highlighting the scope of work, bill of material

and value of the contract/ order.

or

For On-going projects, part completion

certificate for the desired quantity, along with

the supporting documents clearly highlighting

the scope of work, bill of material and value of

the contract / order.







or

For On-going projects, a self certification from

the bidder citing "part completion" clearly

indicating the quantity of IP MPLS

equipements supplied along with the

supporting documents clearly highlighting the

scope of work, bill of material and value of the

contract / order.


signed by the competent authority of the

client entity along with the supporting

documents such as work order/purchase

order clearly highlighting the scope of work,

bill of material and value of the contract/

order.

or

For On-going projects, a self certification to

be submitted stating completion of the

desired quantity, along with the supporting

documents clearly highlighting the scope of

work, bill of material and value of the

contract / order.

The above is applicable for Package A,

B, C & D – Corrigendum_08 - Annexure 1

(Section 7), Sl. No 3 & 4,

Confidential 19



70 Part1, Clause

7.1.10

Page No

35,

106,205,25

9,384,564,6

67,690 as

per

Response

to Queries.

Aggregate Pre-Qualification requirements

Note 1: In case a bidder is bidding for multiple

packages, the minimum turnover & project

experience requirement shall be the aggregate

of the specified requirement in this Tender. In

case of bidding for multiple packages where

the turnover / experience is less than the

aggregate specified; the minimum value

package shall be excluded.

In Case the bidder is bidding for multiple

packages, the minimum turnover and project

experience requirement shall be as stipulated

in the pre-qualification requirements on the

respective package only.


71 1.4.1 Package

A, B, C & D

Clause 5.41

Page No 26

to Page No

34 as per

Corrigendu

m &

Page No 6

as per

Corrigendu

m .

Mobilization Advance

Specific request of Bidder and Against

submission of BG of 110% of mobilization

advance. Simple Interest as notified in clause

5.41 shall be levied, if the 1st mile stone as per

clause 9.2/9.3 is not delivered within the

scheduled time frame.

Specific request of Bidder and Against

submission of BG of 110% of mobilization

advance.


Confidential 20



72 1.4.1 Package

A, B, C & D

Clause 5.41

Page No 26

to Page No

34 as per

Corrigendu

m &

Page No 6

as per

Corrigendu

m .

Mobilization Advance

Mobilization advance (Up to 10% of Capex

cost) shall be secured against irrevocable

Bank Guarantee and shall be recovered along

with interest @15% in the subsequent bills

payable. If the Bidder(s) wishes to avail the

mobilization advance, then they shall submit

an additional Bank Guarantee from a

Nationalised Bank of value 110% of the

mobilization advance for 1 year and 6 Months

from the date of Go-live as per act and rules.

Corrigendum

Mobilization advance (Up to 10% of Capex

cost) shall be secured against irrevocable

Bank Guarantee and shall be recovered in the

subsequent bills payable as per payment

terms. If the Bidder(s) wishes to avail the

mobilization advance, then they shall submit

an additional Bank Guarantee from a



from the date of sanction of the mobilization

advanceas per act and rules.

Interest Free Mobilization advance (Up to 10%

of Capex cost) shall be secured against

irrevocable Bank Guarantee and shall be

recovered in the subsequent bills payable as

per payment terms. If the Bidder(s) wishes to

avail the mobilization advance, then they shall

submit an additional Bank Guarantee from a



from the date of sanction of the mobilization

advanceas per act and rules.


73 2.2 Annexure

5-2.2.1 1.11.9

High level

Network

Diagram – TN

BharatNet

42 In these tenders the IP-MPLS is used

between Block and GP and GP to village

GPON is used. In the diagram on page 42 (2.2

Annexure 5-2.2.1 1.11.9 High level Network

Diagram – TN BharatNet) OLT is shown at GP

and ONT is shown at Village. The details here

in the clause show OLT at block and GPON at

GP. Please clarify.

Similar details for the survey report is

requested for Block to GP where in this case

Routers are used in place of GPON.

OLT to be placed at GP & ONT to be placed

at GP. In-case a village is closer to a block,

the OLT maybe placed at the Block. MSI /

SIs to propose suitable solution based on

detailed on-ground survey

Confidential 21



74 Technical

Specifications


GP router’s

We would like to bring your notice that the

current Tender specifications for

IP/MPLS routers (Core Router, Aggregation

(Block) and Access (GP)) Routers

are favouring only one particular OEM.


75 Technical

Specifications

The router should be CE 2.0 or higher certified

/ TEC-GR: TEC/GR/IT/TCP-006/01/AUG-16 or

higher TEC certifications

We would like to bring your notice again that

CE 2.0 is outdated, CE 3.0 is relevant

certification. CE only signifies layer 2 services

while TANFINET is building a IP/MPLS

network with latest features like segment

routing, etc making CE certification irrelevant.

However, if CE 3.0 is required for qualification,

OEM should should be time for certification till

delivery

The router should be CE 2.0 or higher

certified or TEC-GR: TEC/GR/IT/TCP-

006/01/AUG-16 complied. This is applicable

for Corrigendum_08_Clause Nos. 4.1 - Sl

No. 13, 14 & 15

76 Technical

Specifications


GP router’s

TEC/GR/IT/TCP-006/01/AUG-16 is only for

aggregation/edge/core routers. And there is no

mention of specification of access routers

(GP) in TEC-GR. Please provide TEC-GR for

access router and OEM should be given time

for certification till delivery

The router should be CE 2.0 or higher

certified or TEC-GR: TEC/GR/IT/TCP-

006/01/AUG-16 complied. This is applicable

for Corrigendum_08_Clause Nos. 4.1 - Sl

No. 13, 14 & 15

77 Technical

Specifications


GP router’s

In GP routers the number of interfaces asked

are 6*10G + 16 * 1G with system capacity of

60GBps. To support these many interfaces 76

GBps system capacity is required. In GP

router for ring connectivity max 2x10G

interfaces are needed and another 2 may be

factored for up-link/downlink connectivity. 6nos

10G (with 16x 1G) with 60 GBps throughput is

not matching the interface and system

throughput requirement and to the best of our

knowledge only one OEM is having such

product for GP location. Plus this will increase

the cost of the project substancially.







Confidential 22



78 6.2.5 146 For seamless integration of State level EMS /






OSS.






WE understand that standard ITU TM-814

CORBA NBI interface is also accepted as NBI

Interface from EMS.

Please note that ITU TM-814 CORBA NBI

interface is asked in all BBNL and State

Tenders. Hence kindly include TM814 CORBA

interface and CDOT NMS has integrated the

CORBA interface as part of BBNL GPON

Tender and is running successfully in the

BBNL NOC at Bengaluru and Delhi.







79 5.2.27 35 Support for the Building Integrated Timing







the timing services

Since the timing requirements are removed in

the Corrigendum, we kindly request the

tendering authority to remove or make this

clause as an optional requirement.






for TDM, SDH and


the timing services

80 5.2.48;

5.2.49;

5.2.50 &

5.2.51

35 ITU-T G.987.1: XG-PON, General

requirements;

ITU-T G.987.2: XG-PON, Physical media

dependent (PMD) layer specification;

ITU-T G.987.3: XG-PON, Transmission

convergence (TC) specifications &

ITU-T G.988: XG-PON, ONU management

and control interface (OMCI) specification.

Since there is no XGPON interfaces to be

delivered as UNI/Subscriber interface, we

kindly request the tendering authority to

remove this clause

Deleted

Confidential 23



81 Sr. No. 19 10 of

NIT_TANFI

NET_002_C

orrigendum

_008

Note 2:All the tender items e.g. UPS,

Batteries, Rack, FDMS, OFC (If applicable)

shall have valid Type Approval Certificate

(TAC) from Telecom Engineering Centre

(TEC), New Delhi or Technical Specification

Evaluation Certificate (TSEC) from Quality

Assurance Circle, BSNL, Bengaluru, against

the respective technical specifications of this

Tender. In case any of the quoted models

does not have TAC/TSEC then it should be

applied for TSEC to Quality Assurance Circle,

BSNL, Bengaluru or to TEC, New Delhi for the

model against the technical specifications, at

least one day before the opening of the tender.

The registration number allotted for the TSEC

purpose by Quality Assurance Circle, BSNL,

Bengaluru or for TAC purpose by TEC, New

Delhi shall be submitted along with the bid.

However, only type-approved products as per

above specifications shall be accepted which

shall have to be obtained before issuing Work

Order by the purchaser.

Since specification of 96F Metal Free Ribbon

Optical Fiber Cable with Double HDPE Sheath

(G.652.D Fiber) are similar with

specifinactions mentioned in BSNL tender No.

CA/NOFN/OFC/T-609/2017 dated 15/12/2017

or MM/BN-II/OFC/T-680/2020 dated

11/03/2020, the QF-103 and TSEC issued

against BSNL tender CA/NOFN/OFC/T-

609/2017 dated 15/12/2017 or MM/BN-

II/OFC/T-680/2020 dated 11/03/2020 is also

acceptable for eligibility and / or supply of

cable against this tender. Please confirm.


Confidential 24



82 Sr. No. 19 10 of

NIT_TANFI

NET_002_C

orrigendum

_008

Note 2:All the tender items e.g. UPS,

Batteries, Rack, FDMS, OFC (If applicable)

shall have valid Type Approval Certificate

(TAC) from Telecom Engineering Centre

(TEC), New Delhi or Technical Specification

Evaluation Certificate (TSEC) from Quality

Assurance Circle, BSNL, Bengaluru, against

the respective technical specifications of this

Tender. In case any of the quoted models

does not have TAC/TSEC then it should be

applied for TSEC to Quality Assurance Circle,

BSNL, Bengaluru or to TEC, New Delhi for the

model against the technical specifications, at

least one day before the opening of the tender.

The registration number allotted for the TSEC



Delhi shall be submitted along with the bid.

However, only type-approved products as per

above specifications shall be accepted which

shall have to be obtained before issuing Work

Order by the purchaser.

Kindly confirm detailed procedure for

converting &/or endorsement during supplies

against QF-103 / TSEC procured against

BSNL tender CA/NOFN/OFC/T-609/2017

dated 15/12/2017 or MM/BN-II/OFC/T-

680/2020 dated 11/03/2020 to TANFINET

tender, if required.


83 12,11,11,11 Corrigendu

m 08-

16,19,22,25

The Sole Bidder or Lead Bidder, each

members of the consortium should have valid

ISO 9001:2008/ ISO 9001:2015 and ISO

27001 for Quality Management System which

should be valid as on bid submission date.

The Sole Bidder or Lead Bidder

should submit Copy of valid

certificate

Please confirm if the requirement of ISO9001

and ISO27001 is applicable to all the

members of consortium (including the lead

bidder) OR is it to be met by the Sole/Bidder

only?

The supporting documents, as on date, asks

the documents of Lead/Sole bidder only.

To be Read as: The Sole Bidder or Lead

Bidder should have valid ISO 9001:2008/

ISO 9001:2015 and ISO 27001 for Quality

Management System which should be valid

as on bid submission date.

Confidential 25



84 1

25

Part3-4

Part3-5

Earnest Money Deposit

Template for Security Deposit (SD) bid security

form

Please clarify if the template for Security

Desposit

(Form 27 which is actually perfomance bank

guarantee/Security Deposit format, to be used

by the succesful bidder later)

needs to be submitted at the time of bid

submission, especially when Earnest Money

Deposit (EMD) Form-26 is anyway getting

submitted with the bid?

All forms to be submitted

85 Form 34 Part3-57 to

61

Unpriced Bill of Material format The number of the Form 34 is getting repeated

twice (earlier it is used for "self Declaration on

on-Tampering"). Please check and correct.

Normally, the unpriced bill of material is the

copy of the Financial bid MINUS the pricing

information, while the Make/Model information

can be asked in another form. Kindly check

and advise accordingly.

A typo error. To be corrected accordingly.

Unpriced Bill of Material format with make &

model to be submitted along with Technical

Bid.

Confidential 26



86 Corrigendum 8

1.3.1 Package

A: Section 7

Serial No 3

14 The Sole/ Lead bidder or any one of the

Consortium Members/ Technology Partner

should have an experience as per the below

mentioned scope of work in the last 3 years

Financial Years i.e year ending 31st March

2020

“Experience of Implementation and

Maintenance of at-least one Network

Operations Centre / Security Operations

Centre / Integrated Command & Control

Centre constituting of NMS/EMS/OSS/BSS

along with integration & management of

minimum 100 IP-MPLS nodes in India.”

Supporting documents to be submitted:

The Sole/ Lead Bidder or any one of

Consortium members / Technology Partner:

Completion Certificate issued & signed by the

competent authority of the client entity along

with the supporting documents such as work

order/purchase order clearly highlighting the

scope of work, bill of material and value of the

contract/ order.

or






As per the supporting documents required,

ongoing project are allowed. We understand

that experinece ending 31st March 2020 is a

typo error and bidder can submit completion

certificate for the desired scope for the peiod

after 31st March 2020 till the date of

submission of the bid also.


Confidential 27



87 Corrigendum 8

1.3.1 Package

A: Section 7

Serial No 4

1.3.2 Package

B: Section 7

Serial No 4

1.3.3 Package

C: Section 7

Serial No 4

1.3.4 Package

D: Section 7

Serial No 4

14

18

21

24

Bidders Experience:

The Sole Bidder or Lead Bidder or any one of

the Consortium members should have

successfully completed Cumilative projects for

Supply & implementation of minimum 250 IP-

MPLS nodes for Telecom / ICT / IT projects in

India in the last 3 Financial Years i.e year

ending 31st March 2020“

Supporting documents to be submitted:

The Sole/ Lead Bidder or any one of

Consortium members:







or






As per the supporting documents required,

ongoing project are allowed. We understand

that experinece ending 31st March 2020 is a

typo error and bidder can submit completion

certificate for the desired scope for the peiod

after 31st March 2020 till the date of

submission of the bid also.


88 Sec-9 73 Penalties Since this is an important requirement for

balanced risk approach for enabling the

contractor submit an optimized bid. Request

you to reconsider the following:

"The penalties shall be applicable only on the

following milestones:

a. End-to-End connectivity of 30% GPs,

b. End-to-End connectivity of 50% GPs,

c. End-to-End connectivity of 90% GPs

d. End-to-End connectivity of 100% GPs"


Confidential 28



89 Sec-9 73 Penalties Since it is a turnkey project, request you to

reconsider inclusion of the following clause

which shall incentivise the contractor to work

on catch up plan, for which contractor will

have to incur extra cost:

"Penalty amount due to the missed milestones

shall be imposed only once after reconciliation

at the time of Project Go-Live. In case the MSI

completes the Project Go- Live deliverables on

time, the penalties accumulated till then shall

not be imposed. "


90 Definitions-

Point 15

4 Opex Value: 30% of the Grand Total cost There is still a contradiction between S.No.

1&2 at Pg 5 in the “corrigendum”, which

mentions CapEx:Opex ratio as 80:20 of Grand

Total Cost and S.No. 1 in “Response to

Queries” document which mentions OpEx as

5% p.a of the CapEx .

Please clarify.


91 10.3.3.5 78 The penalties shall be calculated monthly and

shall be paid quarterly

While this requirement was agreed in the

corrigendum of previous RFP, the current

corrigendum doesn’t address this. Request

you to reconsider the following:

"Since the SLA targets are monthly, penalty

amount should be calculated at monthly gross

revenue of O&M instead of QGR, else there

will be a multiplier effect during penalty

calculation. Alternately, the SLA targets shall

be quarterly and penalty shall be applicable on

QGR."


Confidential 29



92 10.3.3.1 78 SLA Penalty Capping:

The penalties for each of the above

parameters shall be exclusive.

While the following requirement of capping

SLA penalty has been addressed in the

corrigendum, we understand that 25% of Total

Opex value refers to Total Quarterly OpEx

Value. Please let us know if this

understanding is not correct.

"Since the penalty is supposed to act as a

detterent and also in line with other BharatNet

tenders, we request that the clause is

amended as follows: The penalties for each of

the above parameters shall be exclusive but

the overall penalties shall not exceed 20% of

the quarterly OpEx value"


93 Sec-15-

Payment

Schedule

71 1 Year after go live (Payment shall be made

after adjustment of the Mobilization Advance

given to the Bidder(s)

We request you to reconsider the following

requirement since this has cashflow

implications for the bidder, which increases

the cost of capital and hence loading of the

bid:

"In order to improve the cashflow for the

bidder and in line with other BharatNet

tenders, we request that the last 10% payment

is released with the previous milestone against

submission of Bank Guarantee equal of 10%

of CapEx of the respective package."


Confidential 30



94 1.27.1 379 Note: In case of depth below 1.2m, instructions

as per latest EI and instructions for protection

etc. will be followed.

Assuming that the standard depth required is

165 cm and the rate approved is Rs.100/- for

the standard depth, then as per the above

formula, for a depth of 100 cm the rate worked

out is

Rate Applicable = 100X0.75 = Rs.75/- per

running meter

Actual amount to be paid = (100/165) X75 =

Rs.45.455/- per running meter

Since this clause leads to penalizing the

contractor twice, it needs to be amended such

that if a penalty is levied, pro-rata payment

shall not be applicable. Please reconsider


95 1.02 BOQ_2182

06

Element Management System for GPON Request to please provide the EMS

Specification. Also please confirm do we need

to provide EMS in HA (1+1) mode or

standalone (1) mode.




Tender

96 2.15 BOQ_2182

06

Formed OFC Dead End & Termination Fittings

@ 5 per km (Wedge Type)- Dead End

Termination / Tensioning clamp assembly for

the poles having cable angle deviation above

25 deg or at tension point/poles. (2 No-

Anchoring clamp, 1 No-Pole Bracket, 1.5 Mtrs-

Stainless Steel Strap, 2 Nos-Buckles) @ 3 per

km --- (Wedge Type - Type 3) : LOT

We request you to please add the actual

Quantity requirement in line with suspension

qunaity for project. currently in BOQ the Qty is

mentioned as LOT - 1 number. Incase if the

quantity to be quoted is as per LOT, then

kindly clarify how the invoicing will be done


97 Corrigendum

No. 08 for

PACKAGE A,

B, C & D :

II Passive

infrastructure

135 Sr No , 11 , 12 , 13 & 14 : FDMS

TEC GR No - GR/FDM-01/02 APR 2007 With

latest amendments

We understand that for all FMS we need to

follow the specification shared on 4.3

Annexure 10 as these are the Rack mounted

FDMS. Please confirm.


98 Corrigendum

No. 08 for

PACKAGE A,

B, C & D :

5.2 Point 5.

34 Optical Link Terminal No. Of Subscribers per

GPON port support is 64

In Corrigendum no clarity on GPON SFP type

shared. Please confirm the SFP Type for

bidding purpose.




Tender

Confidential 31



99 Corrigendum

No. 08 for

PACKAGE A,

B, C & D :

5.2 Point 6

34 The FTTx platformshall be modular, with

minimum of 40Gbps switching capacity.

In Corrigendum-003 no clarity on GPON OLT

Specification, while in corrigendum-008, page

no. 142 specs has been changed from TEC

GR No. GR/PON-01/02 APRIL 2008 to

TEC/GR /TX/PON-02/01/ May 2013. If it so

then it will be a pizza box OLT & no spare card

can be installed? Kindly confirm our

understanding


100 NIT_TANFINE

T_002_

Corrigendum_

008

150 One spare PON card at each OLT to be

provisioned (N+1)

In Corrigendum-003 no clarity on GPON OLT

Specification, while in corrigendum-008, page

no. 142 specs has been changed from TEC

GR No. GR/PON-01/02 APRIL 2008 to

TEC/GR /TX/PON-02/01/ May 2013. If it so

then it will be a pizza box OLT then how spare

card can be installed? Please confirm the

requirement of Spare card as in 4 port & 8 port

Pizza OLT there is no free slot available to

install spare card also box is pre assembled 1

U chassis.




port OLT.



101 1.13.7

S.No.2

12 of

Part-2

OEM/Vendor will provide Element Manager for

supplied hardware equipment.

We asssume that Element Management

System Software will be provided by Package-

B,C,D System Integrators respectively and

Hardware related to that S/W will be provided

by Package-A MSI. Please clarify.

The SIs of Package B,C & D to supply &

implement the required sofware and

hardware along with all supporting

accessories at NOC for the Element

Management System as part of the Bill of

Material for their respective packages

102 S.No. 2.15 &

2.16

2 of Price

Schedule

Price Schedule of Package-A

Formed OFC Dead End Fittings & Formed

OFC Suspension Fittings

Suspension fittings is asked for Nos. required,

whereas Price of Dead End fittings is asked

for 1 Lot. Does LOT mean Per Km or total

fiber quantity of that particular package? Pl

clarify.

To normalize the Price bid without ambiguity

on LOT asked, request you to ask the total

quantity instead of Lot for Dead End Fittings.


Confidential 32



103 1.4 Annexure-

3 - S.No.5

27 of

Corrigendu

m-8

Against Supply of Material on project store for

next two months as required in Block -

Payment Milestone against Material is 50% of

the Work Order Value towards Delivered

material for the respective Block (Payment

shall be made after adjustment of the

Mobilization Advance given to the Bidder(s)

balance of mobilization advance, if any

shall be adjusted in the subsequent bills).

As deduction of mobilization advance from the

Payment milestone of 50% of the work order

value towards delivered material in a block

would be a burden to the SIs , we request you

to kindly adjust the Mobilization advance in the

last payment to be released to the SIs.


104 S.NO.1.1.9

and 1.1.6 of

Part-1 queries

5 and 6 of

Corrigendu

m-8

New Clause - The Purchaser shall place the

work orders on the MSI / SI, blockwise, paced

in accordance with execution of the works.

5.17 Security Deposit (SD)

5.17.1 The successful Bidder is required to

furnish unconditional, Irrevocable Bank

Guarantee for 5% of the value of the work as a

guarantee for the performance of the Contract

within 15 days of issue of Letter of Acceptance

from any Nationalised Bank drawn in favour of

Managing Director, TANIFNET Corporation.

From these two clauses we understand that

as Work orders are placed blockwise, Security

Deposit is required to be furnished for 5% of

the blockwise value of work. Please confirm if

our understanding is correct.


105 1.4.5

Centralized

Helpdesk

253 The proposed solution shall be based on

industry standard best practice framework&

must be certified with eleven commonly used

ITIL Processes.

We request you to kindly remove the ITIL

certification process as it favours only a

particular OEM and does not allow larger

participation in the bid.

With reference to the DIPP and PMA

guidelines, kindly remove the the ITIL

certification process to allow Indian

organizations to participate in the tender


Confidential 33



106 Bidders

Experience


the Consortium members should have

successfully completed Cumilative projects for

Supply & implementation of minimum 250 IP-

MPLS nodes for Telecom/ ICT/ IT Projects in

India in last 3 years Financial Years i.e year

ending 31st March 2020.

if a Sole Bidder or Lead Bidder or any one of

the consortium member has a Purchase Order

for more than 1000 IP-MPLS nodes, for

Telecom / ICT / IT projects in India which was

issued in FY 2019-20 be allowed to be eligible

to bid. Bidder as part of documentary evidence

can provide Copy of Purchase Order detailing

the quantities of IP-MPLS nodes to be

supplied then the Bidder will be considered

meeting the Bidders Experience for IP-MPLS

nodes and can participate in the Tender in the

capacity of Sole Bidder or Lead Bidder or any

one of the Consortium member.


107 7.1.9 (4)

Minimum

Eligibilty

Criteria

[ Package-A/

B/C & D]

56 of all the

4 packages


the Consortium members should have an

experience as per the below mentioned scope

of work in last 3 years from the date of

publishing of RFP “Experience in Supply,

implementation & commissioning at least 250

IP-MPLS nodes for Telecom / ICT / IT projects

in India in the last 3 years from the date of

publishing of RFP”

We understand a certifate confirming

implementation & commissioning of IP-MPLS

nodes in the last three financial years will be

acceptable against this requirement

irrespective of the date of issue of Purchase

order and date of supply. Please confirm


108 7.1.9 Minimum

Eligibilty

Criteria

[ Package-A/

B/C & D]

Corrigendu

m No. 08 for

PACKAGE

A, B, C & D

dated 29th

October,

Page 16,

Package A,

Point 12



ISO 9001:2008/ ISO 9001:2015 and ISO



Is ISO 27001 required for all the parties

including each consortium partner or any one

of the partner is fine. We request you to make

it for any one of the party in the overall

consortium for wider participation.






Confidential 34



109 7.1.9 Minimum

Eligibilty

Criteria

[ Package-A/

B/C & D]

Corrigendu

m No. 08 for

PACKAGE

A, B, C & D

dated 29th

October,

Page 19,

Package B,

Point 11



ISO 9001:2008/ ISO 9001:2015 and ISO













110 7.1.9 Minimum

Eligibilty

Criteria

[ Package-A/

B/C & D]

Corrigendu

m No. 08 for

PACKAGE

A, B, C & D

dated 29th

October,

Page 22,

Package C,

Point 11



ISO 9001:2008/ ISO 9001:2015 and ISO













111 7.1.9 Minimum

Eligibilty

Criteria

[ Package-A/

B/C & D]

Corrigendu

m No. 08 for

PACKAGE

A, B, C & D

dated 29th

October,

Page 25,

Package D,

Point 11



ISO 9001:2008/ ISO 9001:2015 and ISO













Confidential 35



112 All 2. Tender

Schedule

13. EMD

EMD must be submitted in the form of

unconditional & irrevocable Bank Guarantee

(BG) issued by Nationalised Bank valid for a

minimum period of 180 days from the date of

tender opening as per format mentioned in the

RFP on stamp paper of value required under

law duly signed by authorized representative of

Bank:

Request you to modify the clause as:-



(BG) issued by Nationalised Bank/Scheduled

Commercial Bank valid for a minimum period

of 180 days from the date of tender opening

as per format mentioned in the RFP on stamp

paper of value required under law duly signed

by authorized representative of Bank:

To be read as:-



(BG) issued by Nationalised

Bank/Scheduled Bank valid for a minimum

period of 180 days from the date of tender

opening as per format mentioned in the RFP

on stamp paper of value required under law

duly signed by authorized representative of

Bank:

113 Bid Evaluation

7.1.11 Note 2

10 In case any of the quoted model does not have

TAC/TSEC then it should be applied for TSEC

to Quality Assurance Circle, BSNL Bengaluru

or to TEC, New Delhi for the model against the

technical specifications atleast one day before









purchaser.”

Does OFC manufacturer need to apply TSEC

with BSNL for 96F UG OFC cable against the

tender specifications given in Annexure 9

(4.2.1) in corrigendum 008 and submit the

registration number along with bid ?


Confidential 36



114 Bid Evaluation

7.1.11 Note 2

10 In case any of the quoted model does not have

TAC/TSEC then it should be applied for TSEC

to Quality Assurance Circle, BSNL Bengaluru

or to TEC, New Delhi for the model against the

technical specifications atleast one day before









purchaser.”

If OFC manufacturer need to apply fresh

TSEC , please clarify and confirm whether

TSEC applied against tender specifications in

NIT_TANFINET_002_Corrigendum_008 dated

29.10.2020 for any one of the package is

applicable for all packages( A B C and D).

Also please confirm the submission of

registration number allotted for the TSEC



Delhi against any one of the package is

acceptable for other packages in bid

evaluation.


115 Clause No:

7.1.11, Page

No: 58 of RFP

&

S.No 648 of

Response to

Queries /

Clarifications

NIT_TANFINE

T_002_PACK

AGE A, B, C &

D, Page No:

175

32 The TSEC obtained by the OEMs of Bidder(s)

for the various tenders floated by BBNL/BSNL

in the last two years shall be acceptable for

the items which are part of this Tender

provided that the technical specifications

remain unchanged.

Refer the attached document of BSNL QA

document(For TSEC Approval Process), any

TSEC is valid for a period of 3 year. The same

can be referred at

http://www.qa.bsnl.co.in/tsec/tsec-

manual.pdf (page no 9)

Request you to kindly revise the clause as

."The TSEC obtained by the OEMs of

Bidder(s) for the various tenders floated by

BBNL/BSNL in the last three years shall be

acceptable for the items which are part of this

Tender provided that the technical

specifications remain unchanged."

Also, tenders floated for same specifications

aganist the GR for any project should be

acceptable.

To be read as: The TSEC obtained by the

OEMs of Bidder(s) for the various tenders

floated by BBNL/BSNL in the last three

years shall be acceptable for the items

which are part of this Tender provided that

the technical specifications remain

unchanged.

Confidential 37

Corrigendum_009

TANFINET Corporation Bidder’s sign and Seal

Addendum GIS mapping of

OFC Routes for BharatNet

for Package A, B, C & D

Corrigendum_009


Table of Contents

This document describes the process ...................................................................................... 40

1. Annexure A ...................................................................................................................... 40

1.1 Scope and Specifications .................................................................................................................................. 40

1.2 Process for Uploading of GIS and Data Verification .............................................................................. 41

1.3 Guidelines for data uploading and validation:......................................................................................... 41

2. Annexure B ...................................................................................................................... 44

2.1 Guidelines for Submitting GIS Data for GPON Technology ................................................................ 44

2.2 Fields for the BBNL ABD Layer ...................................................................................................................... 44

3. Annexure C ...................................................................................................................... 50

3.1 Guidelines for Submitting GIS Data for IP/MPLS Technology .......................................................... 50

3.2 OLT/ Block Router Layer ................................................................................................................................. 50

3.3 OLT/ Block Router Layer ................................................................................................................................. 52

3.4 OFC Layer ................................................................................................................................................................ 53

3.5 Joint Layer .............................................................................................................................................................. 54

3.6 RI Layer .................................................................................................................................................................... 55

3.7 Landmark Layer ................................................................................................................................................... 56

Corrigendum_009


This document describes the process For mapping the entire assets on the OFC route e.g. OLT/ Block Router, ONT/ GP Router, Joint, Splitter, Route Indicators, Landmark, Cable Sections and OFC etc. on the GIS platform of BBNL/NIC for laid or being laid by PIA (Project implementing Agency) against work order by SIA (State implementing Agency) for BharatNet Phase-II state led model.

1. Annexure A

1.1 Scope and Specifications

1.1.1 Accuracy: Meter level accuracy (1 to 3 meters)

1.1.2 Format: .shp format with mapping on GCS projection system with WGS 84 datum.

1.1.3 Base Map for validation: NIC Base map.

1.1.4 Codification and Layer structure will be provided by BBNL/NIC. Attached as Annexure

– B for the states using GPON Technology and Annexure – C for the states using

IP/MPLS Technology.

1.1.5 Uploading of geo tagged site images of designated locations of specified size e.g.

500 kb. The Mobile App developed/to be developed by BBNL/NIC can also be used

wherever requirement. Photos taken from site shall be optimized by the tool itself as

per requirement.

1.1.6 Calibration: PON OTDR readings (To be provided by PIA) for calibration on each end

of OLT, Splitter, Joint and ONT along with the coil length on each side.

1.1.7 Interval of readings: The coordinates of landmarks like Culverts, Bridges/ nallah,

water bodies, cross roads, railway crossings, flyovers and public places like

temples/mosques, bus-stop, PHC, Post office, School/College, shops etc. to be

captured along with the route indicators (RI), cable joints, splitters etc. along the cable

routes. One additional reading in the middle of the two manholes / RI should be

recorded in the already laid network. Recordings are necessarily to be made at every

fiber turn, bend along the route, road/railway crossings, culverts, diversion etc.

Sufficient recordings at short intervals on the curvature of the route shall be made

such that it should be mapped on GIS properly.

1.1.8 Overhead or Underground alignment, type of execution (HDD, OT, Aerial etc.).

1.1.9 Location of various assets like FPO/SJC/BJC, OLT, ONT, Manholes, Joint Chambers,

Splitters, FTBs, FDMS route indicators etc. with geo-tagged images.

1.1.10 Count of terminated and spare fibers, loop, make and size of cable deployed, Optical

test results for each fibre with the help of already recorded data by SIA and its fiber

laying contractors. Port wise fibre built up and termination details. PON OTDR

readings of FPOIs, Splitters and ONTs.

1.1.11 Route marker details: Cement/electronic Route Marker (Lat-Long) details Route

Marker Identification.

1.1.12 Road features: Length, width and type (RCC, Kuchha, pakka etc.) variation in width of

road in meters taking offset from the centre of the road may be obtained from ABDs

already available with PIA.

1.1.13 Other Operators/Utility: Presence of underground OFC of other operators, utility

pipes, transmission cable etc. to be captured wherever possible.

1.1.14 RoW: Railway authority, NH, forest authority and any other authority limits along with

OFC path shall be obtained from existing ABDs available with PIA/SIA.

Corrigendum_009


1.1.15 For point feature like poles, sewerage man holes, other utility chambers,

transformers, bore well etc. shall be captured as a point.

1.1.16 For all the utilities above ground viz. Poles, Manholes, and telecom nodes like BTS

and telephone exchanges etc. details shall be recorded in a corridor of 50m (25m on

either side of the road centerline of ROW of road whichever is more).

1.1.17 To and/or from direction to village, town, city etc. shall be recorded for all roads.

1.1.18 The Geo Coordinates of all road KM stones shall be recorded and shown using

symbol provided.

1.1.19 The Geo Coordinates of all property boundaries with in the corridor shall be recorded

and shown in drawing.

1.1.20 Collection of data (Custodianship of GPON equipment, location of school, college,

hotels, post office, other Govt. offices, key contacts in GP etc.) in each Gram

Panchayat and other important locations. Contact numbers of all the above Offices to

be obtained

1.2 Process for Uploading of GIS and Data Verification

1.2.1 Engineering Survey of routes and uploading of data in GIS format (Shape Format) of

OFC connectivity from existing OFC FPOI to respective ONTs in Gram Panchayats

(GPs) where cable is already laid or being laid. (FPOI if applicable)

1.2.2 Uploading the Block wise / OLT wise data on GIS platform. BBNL/NIC shall provide

on line tool and base maps for uploading and optimizing the captured data and

information including fibre built up and termination details.

1.2.3 Validation of uploaded data shall be done in three stages:

1.2.3.1 First Stage: The contractor shall upload and verify the Block wise/ OLT wise data

in the tool.NIC shall provide its base map to the contractor for validating and

normalization of data.

1.2.3.2 Second Stage: Second level validation shall be done by SIA/BBNL State units.

1.2.3.3 Third Stage: Third level validation shall be done by NIC.

1.2.4 If the data correction is required at any of the stage mentioned above, the same may

be sent to the previous stage for necessary correction. The contractor shall correct

and upload the data again.

1.2.5 The contractor may edit/correct the data uploaded by them and submit for validation

for next stage. After submission of data to next stage, the editing feature shall be

freezed for contractor. The editing window shall be re-opened for contractor if some

data correction is required at later stages.

1.2.6 NIC shall explore the automated workflow and pendency dash-boarding for the above

process including generation of Auto-SMS and Email to the concerned approving

authority.

1.3 Guidelines for data uploading and validation:

1.3.1 Registration of Users:

1.3.1.1 Contractor: The Contractor User is allotted a set of OLTs from a Block and is allowed to

edit the features only within those OLTs. The Contractor User is created by entering their

details such as User Name, Password, Name, Address, E-Mail, selecting the State, District

and Block from drop down lists, and by selecting the OLTs from a list within which he/she is

allowed to edit.

Corrigendum_009


1.3.1.2 PIA and BBNL: PIA shall validate the data uploaded by the Contractor and after PIA

approval, the data shall be forwarded to BBNL PMU for next stage validation. The PIA/State

and BBNL State Users shall be created by selecting the State from a drop down list and

entering their other details.

1.3.1.3 NIC: The State User of NIC makes observations on the validations made by the BBNL

State User. The NIC State User is also created by selecting the State from a drop down list

and entering their other details.

1.3.2 Uploading and Editing of Data:

The editing module is available for the respective editing users, and the workflow of the module is as

follows:

1.3.2.1 The editor will be prompted to select an OLT from a drop down list of all the OLTs that are

allotted to that particular user.

1.3.2.2 Secondly, the user will choose any one of the following layers to upload, from a drop down

list: OLT, ONT, Splitter, Joint, OFC, RI and Landmark.

1.3.2.3 On selecting the layer for upload, the user can now upload a shape file using the upload

form provided in the module.

1.3.2.4 On uploading the shape file, the data will be checked to see if the selected OLT features in

that particular layer based on OLT code, if there are features present, those features will be

purged from the layer, and the newly uploaded data will be added to the layer.

1.3.2.5 In case the OLT does not have any features in that layer, then the data will be added

directly to the editing layer.

1.3.2.6 The contractor shall also upload the geo tagged images of OLT, ONT, Splitters and other

important BharatNet assets.

1.3.2.7 Each Layer will have a sample structure, which has to be followed while preparing the

shape file for upload. This sample structure will be available for download through the

module.

1.3.3 Workflow Automation and Dashboards:

The status module is available for the all users to monitor the complete status of the OLTs under each

state including the dashboard of validation workflow. The module will function as described below:

1.3.3.1 To see the pendency status, the User will first select the District from his State from a drop

down list.

1.3.3.2 The Blocks from the selected drop down list are populated in another drop down, from

which the User can select his desired Block.

1.3.3.3 On Selection of the block, the Statistics will be displayed for the following parameters,

a. Total OLTs and ONTs in Block

b. OLTs and ONTs for which data has been uploaded

c. OLTs and ONTs for which the data has been accepted on validation

d. OLTs and ONTs for which the data has been rejected on validation

e. History and current status of pendency in workflow

f. View observations from NIC

1.3.3.4 For the PIA/State User, on click of the Statistics of OLTs for which data has been uploaded,

a list displaying the OLTs uploaded by the contractor is displayed.

1.3.3.5 For the BBNL State User, on click of the Statistics of OLTs for which data has been

accepted by PIA, a list displaying the OLTs approved is displayed.

1.3.3.6 For the NIC State User, on click of the Statistics of OLTs for which data has been accepted,

a list displaying the OLTs validated by the BBNL State User is displayed.

Corrigendum_009


1.3.3.7 On selecting any of the OLTs from the aforementioned lists, the User is directed to the

Validation Module.

1.3.3.8 Auto SMS / Email shall be sent to the concerned user to do the necessary changes.

1.3.3.9 OLT Name and Code to be shared by NIC and the same may be uploaded to the BBNL

website.

1.3.4 Validation Module after Data uploading by contractor:

1.3.4.1 Contractor User

a. The contractor may edit/upgrade the data uploaded by them based on requirement

before submission for next level validation by PIA. The Contractor shall furnish the

necessary changes as suggested by PIA/BBNL/NIC from later stages.

1.3.4.2 PIA/ BBNL State User

a. The user will have to select any one of the layers (OLT, ONT, Splitter, Joint, OFC, RI,

and Landmark) to be validated for the selected OLT.

b. A Grid showing a list of the features that have been added by the contractor for that

particular layer is displayed.

c. The grid has the following fields,

i. User Name of the Editing User who added the feature

ii. Time Stamp of when the feature was added.

iii. Layer Important fields used to identify the feature.

iv. Accept/Reject button.

d. On accept, the data is added to the main layer from the editing layer and sent to next

stage.

e. On reject, the data is sent back to the contractor user along with the remarks.

1.3.4.3 NIC User

a. The user shall select any one of the layers (OLT, ONT, Splitter, Joint, OFC, RI, and

Landmark) to be observed for the selected OLT.

b. A Grid showing a list of the features that has been validated by the BBNL State User for

that particular layer is displayed.

c. The grid has the following fields,

i. User Name of the Editing User who added the feature

ii. Time Stamp of when the feature was added.

iii. Layer Important fields used to identify the feature.

iv. “Observations” button.

d. NIC User shall accept or reject the request based on his observations. If NIC user

accepts the data, the uploaded data shall be considered correct and approved for future

use. If NIC User rejects the data, on clicking “Observations”, the NIC User can enter the

observations he/she has made for that particular feature and sent it back for necessary

corrections.

Corrigendum_009


2. Annexure B

2.1 Guidelines for Submitting GIS Data for GPON Technology

2.1.1 List of Layers to be shared:

2.1.1.1 OLT

2.1.1.2 ONT

2.1.1.3 Joints

2.1.1.4 Splitter

2.1.1.5 Route Indicator (RI)

2.1.1.6 OFC

2.1.1.7 FPOI (if existing fibre is being used)

2.1.1.8 Landmarks

2.1.2 The schema of the data for each layer is enclosed herewith. All the layers should

conform to the given schema.

2.1.3 The Network and route assets in layers I-VI & VII (if exits) listed above should be

topologically error free i.e. OFC line should pass through the all the point assets

except Landmarks.

Note: Below table formats are for reference only. All the values are indicative.

2.2 Fields for the BBNL ABD Layer

2.2.1 OLT Layer

OLT Layer

SN Field Type GPON Description

1 Name String OLT Name

2 Type String Asset Type (OLT)

3 Asset_Code String OLT Code

4 NMSOLT_CD String NMS OLT Code

5 Blk_Name String Block Name

6 Blk_Code String Block Code

7 Dt_Name String District Name

8 Dt_Code String District Code

9 St_Name String State Name

10 St_Code String State Code

11 Lat Double Latitude

12 Long Double Longitude

13 Coil_Len Double Coil Length

14 Remarks String if any

15 Obs String Observation

16 status String Editing Status/It should be blank

Corrigendum_009


OLT Layer

SN Field Type GPON Description

17 olt_ip String IP address of OLT

18 geo_photo String Photo with geolocation

19 vendor String

20 phase String phase 1/2

21 model String BBNL/EPC/STATE/PPP

22 Technology String IP/MPLS or GPON

2.2.2 ONT Layer

ONT Layer

SN Field Type Description For GPON

1 Name String ONT Name

2 Type String GP,BHQ, Horizontal ONT

3 Asset_Code String ONT Code

4 LGD_Code String LGD Code for Location

5 Location String Location Name of ONT

6

Loc_Type

String

School, College, GP,PANCHAYAT BHAWAN

etc

7 OLT_Code String OLT Code

8 NMSOLT_CD String NMS OLT Code

9 NMSONT_CD String NMS ONT Code









18 Coil_Len Double Coil Length

19 Remarks String BBNL Remarks

20 Obs String NIC Observations

21 status String Editing Status/It should be blank


23 Ont_mac_id String Mac Id of ONT

24 Otdr_len Double Length in meters

Corrigendum_009


ONT Layer


25 Conn_str String PIC-PON-ONT ID

26 Ont_sr_no String Device serial no.

27 Olt_block String Block code of OLT

28 backhaul String OFC Sat


30 phase String 1, 2

31 Route_code String

2.2.3 Joint Layer

JOINT Layer


1 Name String Joint Name

2 Type String BJC/SJC

3 Asset_Code String Joint ID for NMS

4 Location String Location Name

5 Loc_Type String Location Type

6 OLT_code String OLT Code









15 rd_Offset Double Offset from Middle of the Road

16 coil_2_ont Double Length Towards ONT

17 coil_2_olt Double Length Towards OLT



20 status String Editing Status/ It should be blank



23 PHASE String 1 or2

Corrigendum_009


2.2.4 FPOI Layer

FPOI Layer


1 Name String FPOI Name








9 Type String Joint or Splitter







16 OLT_code String NIC OLT Code

17 Asset_Code String Joint/Splitter ID

18 Loc_type String School, College, GP, etc

19 fpoi_id String Id of FPOI

20 OTDR-Len/

OTDR_Reading

String PoN OTDR reading at FPOI from

OLT

21 OLT_IP String IP Address of OLT connected to

22 Geo_photo String Photograph of FPOI with

Geotagging


24 status String Editing Status

Note: In case of existing fibre being used then FPOI layer also to be inserted

2.2.5 Splitter Layer

Splitter Layer

Corrigendum_009


SN Field Type Description

1 Name String Splitter Name

2 Type String S2,S4,S8,S16

3 Asset_Code String Splitter ID


5 OLT_Code String NIC OLT Code


















23 fiber_pos String Lett/ Right of the r

24 direction String To wards GP or Block

25 Phase String 1 or 2

2.2.6 OFC Layer

OFC Layer


1 Name String OFC Route name

2 Type String Leased/Incremental

3 Asset_Code String Segment Code




Corrigendum_009


OFC Layer



8 CS String Cable Section

9 Seg_Length Double Route length

10 Start_Node String Starting Asset

11 S_Coil_Len Double Starting Coil Length

12 End_Node String Ending Asset

13 E_Coil_Len Double Ending Coil Length

14 num_fibre String 6/12/24/48/96




18 traverse String FIBRE POSITION e.g. 'U' For Underground, 'O'

for Overhead

19 fiber_pos String Lett/ Right of the road


21 phase String 1, 2

22 Route_code String

2.2.7 Landmark Layer

Landmark Layer


1 Name String Landmark Name

2 Type String Asset Type

3 OLT_NAME String OLT Name












Corrigendum_009


Landmark Layer




17 fiber_pos String Lett/ Right of the r


19 rd_offset String Offset from centre of the Road

20 phase String 1 or 2

3. Annexure C

3.1 Guidelines for Submitting GIS Data for IP/MPLS Technology

3.1.1 List of Layers to be shared:

3.1.1.1 Block Router

3.1.1.2 GP Router

3.1.1.3 OFC

3.1.1.4 Joints

3.1.1.5 Route Indicator (RI)

3.1.1.6 Landmarks

3.1.2 The schema of the data for each layer is enclosed herewith. All the layers should

confirm to the given schema.

3.1.3 The Network and route assets in layers I-V listed above should be topologically error

free i.e. OFC line should pass through the all the point assets except Landmarks.

3.2 OLT/ Block Router Layer

OLT/ Block Router Layer

SN Field Type GPON Description IP/MPLS Description

1 Name String OLT Name Block Router Name

2 Type String Asset Type (OLT) Block Router

3 Asset_Code String OLT Code Block Router Code e.g. Block

Code + "L1" i.e.3608L1

4 NMSOLT_CD String NMS OLT Code NMS Block Router Code

5 Blk_Name String Block Name Block Name

6 Blk_Code String Block Code Block Code

7 Dt_Name String District Name District Name

8 Dt_Code String District Code District Code

9 St_Name String State Name State Name

10 St_Code String State Code State Code

11 Lat Double Latitude Latitude

Corrigendum_009


OLT/ Block Router Layer

SN Field Type GPON Description IP/MPLS Description

12 Long Double Longitude Longitude

13 Coil_Len Double Coil Length Coil Length

14 Remarks String if any if any

15 Obs String Observation Observation

16 status String Editing Status/It should be blank Editing Status/It should be blank

17 olt_ip String IP address of OLT IP Address of Block Router

18 geo_photo String Photo with geolocation Photo with geolocation

19 vendor String

20 phase String phase 1/2 2

21 model String BBNL/EPC/STATE/PPP STATE

22 Technology String IP/MPLS or GPON IP/MPLS

OLT/ Block Router DATA TABLE SCHEMA 2 For IP/MPLS Technology only

SN FIELD NAME FIELD VALUE Description For IP/MPLS

1 ASSET_CODE 3608L1 BlockCode + “ L”+ 1,2… Depending on the

Number of Block Routers in the Block

2 ROUTER_TYPE Router type

3 COUNT_GP 113 GP Count Total connected with Block

Router

4 OFC_LEN 150.25 OFC length total km in the

block

5 PORT40G1 Desc Description

6 ADJCNT_B1 3609L1 Adjacent Block1 (asset code of the device

connected)

7 DIRCTN_B1 WEST Direction

8 PORT40G2 Desc Description


connected)

10 DIRCTN_B2 SOUTH(SOUTH-

EAST)

Direction

11 port40G3 Desc Description


connected)

13 DIRCTN_B3 SOUTH Direction

14 ROUTER_MAKE Router_maker name

Corrigendum_009


OLT/ Block Router DATA TABLE SCHEMA 2 For IP/MPLS Technology only


1 ASSET_CODE 3608L1 BlockCode + “ L”+ 1,2… Depending on the

Number of Block Routers in the Block

2 PR_CODE 3608L1PR1 Physical ring 1/2/3/4 code

3 GP_COUNT_RING 33 GP Count of Ring-1/2/3/4

4 PR_PORT_A 1G0/1/0/0 Start Point Router Port No.

5 PR_PORT_B 1G0/1/0/3 Start Point Router Port No.

6 PR_PORT_C 1G0/1/0/4 Start Point Router Port No.

7 PR_PORT_D 1G0/1/0/2 Start Point Router Port No.

3.3 OLT/ Block Router Layer

ONT / GP Router Layer

SN Field Type Description For GPON Description For IP/MPLS

1 Name String ONT Name GP Router Name

2 Type String GP,BHQ, Horizontal ONT GP,BHQ, Horizontal Conn

3 Asset_Code String ONT Code GP Router Code

4 LGD_Code String LGD Code for Location LGD Code for Location

5 Location String Location Name of ONT Location name of GP Router

6 Loc_Type String School, College,

GP,PANCHAYAT BHAWAN

etc

School, College,

GP,PANCHAYAT BHAWAN etc

7 OLT_Code String OLT Code Block Router Code

8 NMSOLT_CD String NMS OLT Code NMS Block Router Code

9 NMSONT_CD String NMS ONT Code NMS GP Router Code









18 Coil_Len Double Coil Length Coil Length

19 Remarks String BBNL Remarks BBNL Remarks

20 Obs String NIC Observations Observations

21 status String Editing Status/It should be Editing Status/It should be

Corrigendum_009


ONT / GP Router Layer

SN Field Type Description For GPON Description For IP/MPLS

blank blank

22 olt_ip String IP address of OLT IP Address of Block Router

23 Ont_mac_id String Mac Id of ONT Mac Id of GP Router

24 Otdr_len Double Length in meters Length in meters

25 Conn_str String PIC-PON-ONT ID Router Port Details

26 Ont_sr_no String Device serial no. Router Serral Number

27 Olt_block String Block code of OLT Block Code of Block Router

28 backhaul String OFC Sat OFC Sat


30 phase String 1, 2 2

31 Route_code String RING PR CODE

ONT/ GP Router DATA TABLE SCHEMA 1 For IP/MPLS Technology only


1 ASSET_CODE 122841N1 LGDCODE + N1 (For GP),

B+BlkCode+N1 (for BHQ) e.g.B3608N1

2 ROUTER_TYPE Router type

3 GPROUTER_IP 10.128.66.109 IP address of GP router

4 ADJ_RING If connected to another ring, the ring code

5 ADJ_ONT_CODE Asset code of the ADJECENT router on the

other ring

6 HOSTNAME BNB-MGI- LOMI-

GSARDH1

Host Name

7 ROUTER_HIG LOW Router High/Low

8 EQUIPMENT 2109 Equipment ID number

9 ROUTER_MAK Router maker name

10 FROM 122843N1 From GP LGD Code+GPR

11 FROM_PORT 1G0/1/0/0 1G 0/1/2 & for 10Gig it will 10G

12 TO 122842N1 To GP LGD Code+GPR

13 TO_PORT 10G0/0/12

14 LR_code 3608L1LR1 Logical ring code

3.4 OFC Layer

OFC Layer

SN Field Type Description Description For IP/MPLS

1 Name String OFC Route name OFC Route name

2 Type String Leased/Incremental Leased/Incremental

Corrigendum_009


OFC Layer


3 Asset_Code String Segment Code Asset_Code + RING 1- 3608L1F1001

& For RING 2- 3608L1F2001

4 OLT_Code String OLT Code Block router code




8 CS String Cable Section Cable Section

9 Seg_Length Double Route length Route length

10 Start_Node String Starting Asset Starting Asset

11 S_Coil_Len Double Starting Coil Length Starting Coil Length

12 End_Node String Ending Asset Ending Asset

13 E_Coil_Len Double Ending Coil Length Ending Coil Length

14 num_fibre String 6/12/24/48/96 NO OF FIBRES E.G. 48/96/…288

15 status

String

Editing Status/ It should be

blank

Editing Status/ It should be blank


17 Obs String NIC Observations NIC Observations

18 traverse String FIBRE POSITION e.g. 'U'

For

Underground, 'O' for

Overhead

FIBRE POSITION e.g. 'U' For

Underground, 'O' for Overhead

19 fiber_pos String Lett/ Right of the road Lett/ Right of the road

20 direction String To wards GP or Block To wards GP or Block

21 phase String 1, 2 2

22 Route_code String RING PR CODE 3608L1PR1,

blk2blk code 3608L1_3609L1,

ADJ blk code

3608L1PR1_3609L1PR3

3.5 Joint Layer

JOINT Layer


1 Name String Joint Name Joint Name

2 Type String BJC/SJC BJC/SJC

3 Asset_Code String Joint ID for NMS Block router code+ "RJ1001" :

JOINT in RING 1 with Code

001

4 Location String Location Name Location Name

5 Loc_Type String Location Type Location Type

6 OLT_code String OLT Code Block router code

Corrigendum_009


JOINT Layer










15 rd_Offset Double Offset from Middle of the Road Offset from Middle of the Road

16 coil_2_ont Double Length Towards ONT Length Towards GP

17 coil_2_olt Double Length Towards OLT Length Towards Block router



20 status String Editing Status/ It should be

blank

Editing Status/ It should be

blank

21 olt_ip String IP address of OLT IP address of Block router

22 Otdr_len Double Length in meters Length in meters

23 PHASE String 1 or2 2

3.6 RI Layer

RI Layer

SNo Field Type Description Description For IP/MPLS

1 Name String RI NAME RI NAME

2 Type String Asset Type Asset Type as "RI"










12 rd_Offset Double Offset from centre of the Road

13 CS String Cable Section Cable Section



16 coil_len String if any if any

Corrigendum_009




19 fiber_pos String Lett/ Right of the r Lett/ Right of the r


21 phase String 1 or 2 2

22 Route_code String 3608L1RI1 RING PR CODE 3608L1PR1,

blk2blk code 3608L1_3609L1,

ADJ blk code

3608L1PR1_3609L1PR3

3.7 Landmark Layer

Landmark Layer

SNo Field Type Description Description For IP/MPLS

1 Name String Landmark Name Landmark Name

2 Type String Asset Type Landmark Type

3 OLT_NAME String OLT Name Block Router Name














17 fiber_pos String Lett/ Right of the r Lett/ Right of the r


19 rd_offset String Offset from centre of the Road Offset from centre of the Road

20 phase String 1 or 2 2