Preamble to NIT/TANFINET/001/PACKAGE-A/PACKAGE-B/

PACKAGE-C/ PACKAGE-D dated 05.12.2019

“BharatNet” project funded by Government of India is a prestigious project for the State
of Tamil Nadu. This project envisages connecting the Blocks to Gram Panchayats
(GPs) across the State by establishing an Optical Fiber Cable network system.
Tamil Nadu is a pioneer in leveraging various ICT technologies for efficient, effective
and transparent delivery of services to the citizens at their doorsteps. BharatNet, a
comprehensive and highly reliable fibre network across the State, would integrate with
various Govt Networks like National Knowledge Network (NKN) , Tamil Nadu State
Wide Area Network (TNSWAN) and Police Network (CCTNS) and facilitate in service
delivery across various platforms by the State Government to the rural population
thereby bridging the “Digital Divide”.

TANFINET Corporation has published the tender on 05th December 2019 and
conducted pre-bid meeting on 21.02.2020. During, the pre bid meeting, TANFIENT
has received queries from all bidders which includes System Integrators, OEMs and
OFC manufacturers. Pre-Bid queries received are consolidated and processed for
response in the form of Corrigendum.

In the meantime, the Department of Telecommunications, Government of India, has

fixed a stringent target period to complete the project in Tamil Nadu by March 2021.
To reap the benefits from the proposed digital infrastructure for the welfare of common
man in the villages, implementation of the project within the stipulated timeline is very
much essential for the State.

While the process of finalizing the tender and selection of the System Integrators (SI)
for the project was in progress, unexpectedly the entire nation has come under Lock
Down due to pandemic COVID-19.
BharatNet facilitates implementation of a comprehensive State controlled network
which will ensure effective communication across all villages even during calamities.
Currently, Tamil Nadu have a State controlled connectivity infrastructure only up to
Block level which itself is grossly insufficient to meet the administrative needs of the
Government. Lack of connectivity from Block to village level would hamper the activity
of the State administration in mitigating any natural disaster specified in the Disaster
Management Act, 2005.

Govt of Tamil Nadu would need an effective communication infrastructure to mitigate

COVID-19 or any other Disaster defined under Disaster Management Act, 2005.
Considering the communication infrastructure requirement as the sole consideration,
implementing BharatNet project in Tamil Nadu within the Project Execution Period (8
months execution +1 Month Go-live) will be the only solution to mitigate the effects of
any such Disaster in future.

The State is moving towards a situation where communication would be a

life-line requirement for delivery of Government services like Health, Agriculture,
Education , Social welfare, Policing Services, PDS etc., which cannot be dependent
on profit oriented private players and hence the State should have its own
infrastructure for delivery of essential services even during disasters like COVID-19.
A State-owned Digital Infrastructure at this stage would have been a force multiplier in
the efforts of the State in mitigating COVID-19.

Considering

(a) The fact that Tamil Nadu is the last State to implement BharatNet under
State-Led-Model,

(b) COVID- 19 crisis across the country,

(c) Amendment to the MOU issued by Government of India stipulating a

revised Project Execution Period (PEP) and the

(d) Queries received during the pre-bid meeting

Thus, it is imperative to revisit the existing tender conditions with regard to Technical,
Financial and other eligibility conditions and specify a revised Project Execution Period
(PEP) to ensure that project is completed within the stringent timelines so as to equip
the State to handle any such natural disasters and emergent situations in future by
invoking the power under Rule 17 of the Tamil Nadu Transparency in Tenders Rules
2000.

Accordingly, taking into account the deadlines specified in the revised MOU and the
emergent situation being faced by Tamil Nadu and the Nation with COVID-19, the
Project Execution Period (PEP) has been revised to
9 months (i.e 8 months execution +1 Month Go Live) starting from
1st June 2020. Implementing BharatNet project within the Project Execution Period
(8+1) months, will be a singular and signature service by TANFINET for Tamil Nadu
and for the Nation.

Hence, to establish a life-line Communication Digital Infrastructure in Tamil Nadu,

amendments to the existing eligibility, technical & financial conditions of the tender
document have to be undertaken.

Under these circumstances, suitable corrigendum has been prepared duly after
considering various factors like pre-bid queries, BBNL Guidelines, amendment to the
MoU issued by Department of Telecommunications, Govt of India on 4.3.2020 for
revised Project Execution Period (PEP) and the COVID-19 pandemic. The bidders are
therefore, requested to submit their bids based on the Tender dated 5.12.2019 and
the Corrigendum hereunder published.
 Annexure A & B
Corrigendum Proposed from Queries Received from prospective bidders in Pre-Bid Meeting & subsequently through e-
mails
Tender Ref No: NIT/TANFINET/001/PACKAGE-A/ B/C/D – Dated 05-12-2019
Tender Pag Claus Content of
Sno Document e No e No Clause Existing Clause Revised Clause
Annexure A Technical Scrutiny:
Technical scrutiny will be carried out by the
technical committee considering the
compliance sheet and support documents
provided by the bidder for the quoted network
components: -
The bidder has to qualify the technical
scrutiny for in order to proceed further.
Technical Presentation:
1. The qualified bidder has to show up a
technical presentation to the technical
committee about his approach and
way forward in implementation.

Common Proof of Concept (POC)

Guidelines 1.POC (Proof of Concept) should be offered
Regarding by the bidder and POC evaluation will be
Compliance conducted by the Technical Committee as a
of part of the technical evaluation process. The
Page Equipment/S POC arrangements shall be made by bidder
1 11 B ystem New inclusion within one week of notice from tendering

4/28
authority. Financial bid will be opened after
evaluation of the technic bids and successful
completion of POC only.

2.In case POC is not successful the bidder

will be disqualified for further process and his
financial bid will be rejected without assigning
any reason.

3. The charges for establishing POC has to

be bear by the bidder.

Procedure for POC:

POC will be conducted by all bidders as part

of the technical evaluation process at the
Technical Bid stage. POC will be required to
demonstrate the proposed solution and all
the proposed network components from
respective OEMs. The bidders shall establish
a fully operational demo site at any location,
or a lab setup chosen as per his convenience
using the same network products
offered/mentioned in his technical bid.
Bidder shall demonstrate the same Make and
Model as submitted in technical bid for each
equipment. Any deviation from this needs to
be approved by TANFINET. Bidders will be

5/28
 required to give demonstration of the
envisaged solution (PoC) to Purchaser as per
the test cases below
The date and time of technical presentation
and PoC shall be informed to individual
bidders by TANFIENT. Each bidder shall be
given a time slot of two hours for technical
presentation. Additional time shall not be
given for either Technical presentation or
PoC.

EMS for Network Elements shall

support northbound open
Enterprise interfaces such as SNMP/ EMS for Network Elements shall support
Management CORBA/XML or any other northbound open interfaces such as
Page System protocols for integration with the SNMP/RESTFUL/CORBA/XML or any other
2 33 1.2.3 NMS. protocols for integration with the NMS.
Annexure A NOC and
Internet
Router Operating temperature: 5 to 40
Page Sectio Specifications degrees with Humidity – 10% to Operating temperature: 0 to 45 degrees with
3 15 n C, 4, 90% Non-Condensing. Humidity – 10% to 85% Non-Condensing.
Annexure A The proposed solution should be The EMS for BSS/OSS & NMS can be
Hyper in the leader’s quadrant by latest implemented with standalone servers and
Converged FY18/19 Gartner Report for storage instead of Hyper Converged
Page Sectio Infrastructure Hyper Converged Infrastructure. Devices. Specification mentioned below for
4 20 nc all components.

6/28
 Annexure A 1. Aerial OF Cable (ADSS
Cable): 24 pair ADSS on
power lines: As per TEC GR
No. TEC/GR/TX/OFC-
022/02/MAR-17 with latest
amendments if any. (Type
2A)
2. Aerial OF Cable (ADSS
Cable): 48 pair ADSS on
power lines: As per TEC GR
No. TEC/GR/TX/OFC-
022/02/MAR-17 with latest
amendments if any. (Type 2A) 1. Aerial OF Cable (ADSS Cable): 24 Fiber
3. Underground (OFC Cable): ADSS on power lines: As per TEC GR No.
96 pair ADSS on power lines: TEC/GR/TX/OFC-022/02/MAR-17 with
As per TEC GR No. latest amendments if any. (Type 2A)
TEC/GR/TX/OFC- 2. Aerial OF Cable (ADSS Cable): 48 Fiber
022/02/MAR-17 with latest ADSS on power lines: As per TEC GR No.
amendments if any. TEC/GR/TX/OFC-022/02/MAR-17 with
4. Underground (OFC Cable): latest amendments if any. (Type 2A)
144 pair ADSS on power 3. Underground (OFC ribbon Cable): 96
lines: As per TEC GR No. Fiber : As per TEC GR No.
Technical TEC/GR/TX/OFC- TEC/GR/TX/OFC-022/02/MAR-17/ , TEC
Specification 022/02/MAR-17 with latest GR No. TEC/GR/OFC-05/02/Mar 2006
- Package B, amendments if any. with latest amendments if any.
5 55 II C&D

7/28
 Annexure B Cable loops are to be provided
Installation for future maintenance purposes
Cable Loop / at regular spacing. (As per
storage / Joint guidelines of BBNL, Annexure B- Cable loops for overhead is 10 mtrs in both
Closure Instruction of Aerial and UG the direction and 20 mtrs in both the
36 6.4 Cable implementation) directions for underground.

1) All components mentioned under Section C& D should be provided with compliance Yes/No as mentioned below with
supporting document.

Make Offered:
Model Offered:
Pg. No in
Compliance
S. No. Parameter Minimum Specifications Supporting
Yes/No
Doc.
.

8/28
2) Section C- Component -6) HCI is replaced with below mentioned components.

Server

Make Offered:
Model Offered:
S. Compliance
Parameter Minimum Specifications Pg. No in Supporting Doc.
No. Yes/No
Latest series/ generation of 64 bit x86/
equivalent processor(s) with 14 or higher
Cores
1. Processor Processor speed should be minimum 2.4
GHz
Minimum 2 processors per each physical
server
2. RAM For workload: As per the requirement
1. 2 X 10GbE LAN ports for providing
Ethernet connectivity
Network 2. Dual-port 16Gbps FC HBA for providing
3.
interface FC connectivity
Optional: 2 X 20GbE converged interface
(for both ethernet ad FC) or better
Power
4. Dual Redundant Power Supply
supply
RAID
5. As per requirement/solution
support

9/28
Make Offered:
Model Offered:
S. Compliance
Parameter Minimum Specifications Pg. No in Supporting Doc.
No. Yes/No
Licensed version of 64 bit latest version
Operating
6. of Linux/ Microsoft® Windows based
System
Operating system)
7. Form Factor Blade
Shall support Industry standard
8. Virtualization virtualization hypervisor like Hyper-V and
VMWARE.

Blade Chassis

Make Offered:
Model Offered:
Compliance
S. No. Minimum Specification Pg. No in Supporting Doc.
Yes/No
Minimum 6U size, rack-mountable, capable of
1 accommodating minimum 8 or higher hot pluggable
blades
Dual network connectivity of 10 G speed for each
blade server for redundancy shall be provided or
2
converged interconnects for both ethernet and FC
connectivity in redundancy

10/28
Make Offered:
Model Offered:
Compliance
S. No. Minimum Specification Pg. No in Supporting Doc.
Yes/No
Backplane shall be completely passive device. If it is
3 active, dual backplane shall be provided for
redundancy.
Have the capability for installing industry standard
flavours of Microsoft Windows, and Enterprise Red
4
Hat Linux OS as well as virtualization solution such
as VMware and Hyper-V.
USB ports shall be available in chassis, can be
5 internal or external, which can be shared by all the
blades allowing remote installation of software
6 Minimum 1 USB port
Minimum 4x10 G ethernet interface and 2x16 Gbps
Fibre Channel module for connectivity to the
7 external Fibre channel Switch and ultimately to the
storage device or converged interface with minimum
4x10 G and 2x8G FC ports in each interconnect
Hot plug/hot-swap redundant power supplies to be
8
provided, along with power cables
Power supplies shall have N+N. All power supplies
9
modules shall be populated in the chassis.
Required number of PDUs and power cables, to
10 connect all blades, Chassis to Data Centre power
outlet.
11 Hot pluggable/hot-swappable redundant cooling unit

11/28
Make Offered:
Model Offered:
Compliance
S. No. Minimum Specification Pg. No in Supporting Doc.
Yes/No
Provision of systems management and deployment
12 tools to aid in blade server configuration and OS
deployment
Blade enclosure shall have provision to connect to
display console/central console for local
13
management such as troubleshooting,
configuration, system status/health display.
Single console for all blades in the enclosure, built-
14
in KVM switch or Virtual KVM features over IP
Dedicated management network port shall have
15
separate path for remote management.

SAN Switch

Make
Offered:
Model
Offered:
Minimum Compliance
S. No. Parameter Pg. No in Supporting Doc.
Specifications Yes/No
1 Power Specification 200-240V, 50-60
Hz
2 Operating temperature range 0° to 40° C

12/28
Make
Offered:
Model
Offered:
Minimum Compliance
S. No. Parameter Pg. No in Supporting Doc.
Specifications Yes/No
3 Operating Relative Humidity 10 to 90% relative
range (non-condensing) humidity
4 Total no. of ports on the Total no. of ports
proposed switch on the proposed
switch 48 with 24
ports populated
with
the interfaces
and required
licenses
5 Throughput of each FC port Throughput of
each FC port
16Gbps
6 Support for 4/8/16 Gb/s HBAs Yes
Protocol Supported
7 FC Yes
8 FCP Yes
9 FC-AL/ FC-AL-2 Yes
10 Designed for high availability Yes
with no Single Point of Failure
Power Supply
11 Hot Swappable Power supply Yes
proposed

13/28
Make
Offered:
Model
Offered:
Minimum Compliance
S. No. Parameter Pg. No in Supporting Doc.
Specifications Yes/No
12 The switch should have Yes
redundant power supply
Cooling Fans
13 Hot Swappable Cooling Fans Yes
proposed
14 (N+1) redundant Cooling Yes
Fans proposed
15 Capability for streaming the Yes
data in multiple paths with
Optimization algorithms for
streaming data through
shortest available path.
16 Capabilities for cascading of Yes
switches
17 Non-disruptive firmware Yes
update
18 End to end performance Yes
monitoring
19 Capability to interface with Yes
host based adapters (HBA) of
multiple OEM, supporting
multiple Operating System
including but not limited to
AIX, HP-UX, Linux, Solaris,
Windows, etc.

14/28
Make
Offered:
Model
Offered:
Minimum Compliance
S. No. Parameter Pg. No in Supporting Doc.
Specifications Yes/No
Zoning and security
20 Support for hardware - Yes
enforced zoning
21 Policy based security and Yes
centralised fabric
management
22 Support for Encrypted Yes
password
23 Support for PKI Digital Yes
certificates
24 Support for FCAP/DH-CHAP Yes
authentication
25 Support for RADIUS, SSL / Yes
HTTPS, SSH, SNMP V3
Support for Hardware based trunking
26 Compatibility with proposed Yes
network devices
27 Compatibility with proposed Yes
servers
28 The system should not be an Yes
end of life / end of service
product.

15/28
 Primary Storage

Make Offered:

Model Offered:

S. Compliance
Parameter Minimum Specifications Pg. No in Supporting Doc.
No. Yes/No
Solution/
1 IP Based/iSCSI/FC/NFS/CIFS
Type
Storage Capacity should be considered
as per the design requirement (usable,
after configuring in offered RAID
configuration)
RAID solution offered must protect against
2 Storage double disc failure.
To store all types of data (Data, Voice,
Images, Video, etc)
Disk type: SAS and SSD drives
Storage system capable of scaling
vertically and horizontally
Rack mounted form-factor
Hardware
3 Modular design to support controllers and
Platform
disk drives expansion
At least 2 Controllers in active/active mode
The controllers / Storage nodes should be
4 Controllers upgradable seamlessly, without any
disruptions / downtime to production
workflow for performance, capacity

16/28
Make Offered:

Model Offered:

S. Compliance
Parameter Minimum Specifications Pg. No in Supporting Doc.
No. Yes/No
enhancement and software / firmware
upgrades.

RAID
5 RAID 1+0 and 6
support
Minimum 64 GB of useable cache across
all controllers. If cache is provided in
6 Cache additional hardware for unified storage
solution, then cache must be over and
above 64 GB.
The Storage System should be able to
Redundancy protect the data against single point of
7 and High failure with respect to hard disks,
Availability connectivity interfaces, fans and power
supplies
All the necessary software (GUI Based) to
configure and manage the storage space,
RAID configuration, logical drives
Management allocation, snapshots etc. are to be
8 provided for the entire system proposed.
software
Licenses for the storage management
software should include disc
capacity/count of the complete solution

17/28
Make Offered:

Model Offered:

S. Compliance
Parameter Minimum Specifications Pg. No in Supporting Doc.
No. Yes/No
and any additional disks to be plugged in
in the future, upto max capacity of the
existing controller/units.
A single command console for entire
storage system.
Should also include storage performance
monitoring and management software
Should provide the functionality of
proactive monitoring of Disk drive and
Storage system for all possible disk
failures
Should be able to take "snapshots" of the
stored data to another logical drive for
backup purposes
The storage array must have complete
cache protection mechanism either by de-
Data
9 staging data to disk or providing complete
Protection
cache data protection with battery backup
for up to 4 hours

18/28
 Secondary Storage

Make Offered:

Model Offered:

S. Compliance
Parameter Minimum Specifications Pg. No in Supporting Doc.
No. Yes/No
Secondary Storage
(Archival/Backup) can be on any
media such as Disks, Disk
systems, etc. or its combination.
(so as to arrive at lower cost per
TB)
May or may not use de-
1. Solution/Type
duplication technology
Disk type: SAS/ NL SAS
Compatible with primary storage
Must use latest stable
technology platform, with
support available for next 7 to 10
years.
To store data as required, to
meet the archival requirement
2. Backup Size
for different type of
data/information
Rack mounted, Rack based
3. Hardware Platform
Expansion shelves

19/28
Make Offered:

Model Offered:

Must include backup/archive

4. Software Platform
application portfolio required

Retrieval time for any data

stored on secondary storage
should be max. 1 hours for
critical data & 2 hours for other
5. Retrieval Time data. This would be taken into
account for SLA calculation.
(Critical data means any data
needing urgent attention by the
Authority).

3) Section D- Component- 4)-c Lock & Key - Two lock is required for each PoP. One door located at the training hall should be
locked always. 3 keys for each lock. Lock details: Maxed Globe Pressing Padlock 2 Inch Safety Lock or equivalent.

4) Section II- Technical Specification Package B,C & D- 3) Carrier Ethernet switch removed.

20/28
5) Section D: 3) Technical Specifications for 1.0 kVA ONLINE UPS System

S No Parameter Existing clause Revised Clause

1 Capacity 1 KVA/ 900W 1 KVA/ 900W
Input power factor
5 0.99 0.98 at full load
correction
1Ph,L-N+PE (160 to 280 Vac
1Ph,L-N+PE (160 to 300Vac on full load &
on full load & shall support
shall support upto 110Vac for 60% load). UPS
upto 110Vac for 60% load).
6 Input configuration Shall have inbuilt OVCD protection. The input
UPS Shall have inbuilt OVCD
range from 110 to 300V must be settable by
protection. The input range
end user
from 110 to 280V.
To be deleted. Repeated
7 PF >= 0.99
point.
220/230/240Vac shall be
200/208/220/230/240Vac shall be available
10 Output Voltage available with +/-1%
with +/-1% regulation in battery mode
regulation in battery mode
12 Output Power factor 0.9 0.8
Minimum 10A X 3 nos - Indian Socket inbuilt
to the UPS back. One of these O/p Socket Minimum 10A X 3 nos - Indian
17 Output Connection shall be Programmable with settable time so Socket inbuilt to the UPS
as to increase the back-up time for critical back.
load
21 Port USB, RS 232, RJ45 USB/ RS 232 and RJ45
23 Battery backup 1.0 kVA - 60 minutes (Min VAH 2340) 1.0 kVA - 60 minutes

21/28
S No Parameter Existing clause Revised Clause
Min. 15 amp inbuilt (for any future expansion
of back-up time). Charger shall be settable for Suitable for 1 hour battery
24 Charger
1/2/4/6/8/10/12/14 A ratings as per the need backup
of battery charging
Operating temperature 0-40 deg C with full load @ 0.9PF. Later de-
25.a 0-40 deg C with full load
range rating applicable upto 50 deg C
Indication required -> Over Temperature,
Indication required -> Over
Load on Battery, Battery on Charge, Battery
Temperature, Load on
25.b Other low, Mains on Fan Speed control (as per load
Battery, Battery on Charge,
& room temp) shall be possible
Battery low, Mains on.
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
Bus start fail, Bus over & under, Inverter soft temperature, overload,
start failure, Inverter voltage high & low, charger failure, over input
Inverter output short, Battery voltage high & current, over input current,
low, charger output short, over temperature, battery not connected, over
27.b Measurements (On LCD)
overload, charger failure, over input current, charge, EPO enable.
over input current, battery not connected,
over charge, EPO enable, Programmable All the Fault indication
output enable. mentioned in the RfP is not
required to be shown on the
LCD. However, all the Fault
indications mentioned in the
RfP should reflect through
alarms and LED indications
etc.

22/28
S No Parameter Existing clause Revised Clause
Inverter voltage & frequency, Frequency
converter, ECO mode, ECO voltage range,
Inverter voltage & frequency,
Bypass setting, Bypass voltage range,
Frequency converter, ECO
Autonomy limitation setting, Battery total Ah
mode, ECO voltage range,
setting, Charger current, Bypass frequency
Bypass setting, Bypass
27.c Settable data range, Programmable outlet, Programmable
voltage range, Charger
outlet setting, Charger boost & float voltage
current, Bypass frequency
setting, EPO logic setting, Isolation
range, Charger boost & float
transformer O/P (if applicable in design of
voltage setting "
OEM), Display setting for autonomy,
Acceptable input voltage range.
Manufacturer - > ISO 9001,
Manufacturer - > ISO 9001, TL 9000, ISO ISO 14001 & OHSAS 18001
14001 & OHSAS 18001 (ISO & OHSAS for (ISO & OHSAS for Indian
28 Manufacturer Indian Operation of OEM only) . Factory Operation of OEM only) .
calibration lab of manufacturer shall be NABL Factory calibration lab of
accredited in India manufacturer shall be NABL
accredited in India

23/28
6) Section D: 2) Technical Specifications for 2.0 kVA ONLINE UPS System

S No Parameter Existing clause Revised Clause

1 Capacity 2.0 KVA / 1800 W 2.0 KVA / 1600 W
Input power factor
5 0.99 0.98 at full load
correction
1Ph,L-N+PE (160 to 280
1Ph,L-N+PE (160 to 300Vac on full load & Vac on full load & shall
shall support upto 110Vac for 60% load). support upto 110Vac for
6 Input configuration UPS Shall have inbuilt OVCD protection. 60% load). UPS Shall have
The input range from 110 to 300V must be inbuilt OVCD protection.
settable by end user The input range from 110 to
280V.
To be deleted. Repeated
7 PF >= 0.99
point.
220/230/240Vac shall be
200/208/220/230/240Vac shall be available
10 Output Voltage available with +/-1%
with +/-1% regulation in battery mode
regulation in battery mode
12 Output Power factor 0.9 0.8
Minimum 10A X 3 nos - Indian Socket inbuilt
to the UPS back. One of these O/p Socket
17 Output Connection shall be Programmable with settable time so As per design
as to increase the back-up time for critical
load
21 Port USB, RS 232, RJ45 USB/ RS 232 and RJ45
23 Battery backup 2.0 kVA - 60 minutes (Min VAH 2340) 2.0 kVA - 60 minutes
Min. 15 amp inbuilt (for any future Suitable for 1 hour battery
24 Charger
expansion of back-up time). Charger shall backup

24/28
 be settable for 1/2/4/6/8/10/12/14 A ratings
as per the need of battery charging
Operating temperature 0-40 deg C with full load @ 0.9PF. Later de-
25.a 0-40 deg C with full load
range rating applicable upto 50 deg C
Indication required -> Over Temperature,
Indication required -> Over
Load on Battery, Battery on Charge, Battery
Temperature, Load on
25.b Other low, Mains on Fan Speed control (as per
Battery, Battery on Charge,
load & room temp) shall be possible
Battery low, Mains on.
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
Bus start fail, Bus over & under, Inverter soft temperature, overload,
start failure, Inverter voltage high & low, charger failure, over input
Inverter output short, Battery voltage high & current, over input current,
low, charger output short, over temperature, battery not connected, over
27.b Measurements (On LCD)
overload, charger failure, over input current, charge, EPO enable.
over input current, battery not connected,
over charge, EPO enable, Programmable All the Fault indication
output enable. mentioned in the RfP is not
required to be shown on the
LCD. However, all the Fault
indications mentioned in the
RfP should reflect through
alarms and LED indications
etc.
Inverter voltage & frequency, Frequency Inverter voltage &
27.c Settable data converter, ECO mode, ECO voltage range, frequency, Frequency
Bypass setting, Bypass voltage range, converter, ECO mode, ECO

25/28
 Autonomy limitation setting, Battery total Ah voltage range, Bypass
setting, Charger current, Bypass frequency setting, Bypass voltage
range, Programmable outlet, Programmable range, Charger current,
outlet setting, Charger boost & float voltage Bypass frequency range,
setting, EPO logic setting, Isolation Charger boost & float
transformer O/P (if applicable in design of voltage setting "
OEM), Display setting for autonomy,
Acceptable input voltage range.
Manufacturer - > ISO 9001,
Manufacturer - > ISO 9001, TL 9000, ISO ISO 14001 & OHSAS
14001 & OHSAS 18001 (ISO & OHSAS for 18001 (ISO & OHSAS for
28 Manufacturer Indian Operation of OEM only) . Factory Indian Operation of OEM
calibration lab of manufacturer shall be only) . Factory calibration
NABL accredited in India lab of manufacturer shall be
NABL accredited in India

26/28
7) NMS Integration:

1. Requirement of API parameters

Regarding the Integration of State NMSs with Bharat Net UNMS, the following APIs are required from State NMS.
APIs covering all relevant parameters of following modules as monitored by state NMS. Only relevant processed data
should be sent to NMS. The raw data from lower layers should not be sent. Detailed API wise documents should be shared by
state NMS. If any other parameter, other than proposed to be shared by state NMS is needed to be monitored and integrated with
UNMS, the same will be informed.

Sl No. Module Parameters must include but may not be limited to

1 Inventory Type, unique name(NMS level), location and status of network elements, State /
District / Block / GP Availability* (in terms of % uptime- daily, monthly), reason for
down NEs(due to power, fibre, hardware issue, temperature etc.)

2 Fault Root cause alarms indicating affected services/locations (API for pulling both –
such pending alarms at any point of time and cleared alarms for a duration). The
alarm info shall also have alarm instance number(ID), alarm name, category,
severity, occurrence time at NE, affected NE entity, clearance time at NE(for
cleared alarms). The same alarm instance ID should be mentioned in both
occurrence and clearance information for a particular alarm. The NMS_LOG_TIME
and NMS_CLEAR_LOG_TIME also shall be shared.
Note: Only Root Cause alarms which are Service Affecting including alarms which
bring the NE down shall be shared after applying due grace period and RCA for
confirmation of fault existence.
3 Configuration Software versions, ports configuration at SNI/UNI sides, Available bandwidth
4 Trouble Ticket TT number indicating Network Element and fault ( alarm name ), TT Raised Time,
TT Status, Aging, present assignee

27/28
 5 Performance Management PM parameters of any requested monitored elements/interface, daily Bandwidth
utilization for all State / District / Block / GPs
6 Service / Connection Services / connections configured, their type, BW configured, Date of creation/
Inventory modification, service status, subscriber, Location and NE Details
7 GIS Please suggest the ways data can be shared from state GIS with BBNL GIS
8 SLA SLA definitions, violations

*- the algorithm used to calculate should be shared. This will be reviewed in order to maintain uniformity amongst all NMSs.
Apart from these the notification structure for informing the near real time change in status of NEs, root cause alarms etc. should
be made available. All integration will be done on basis of LGD codes which will be shared by BBNL statewise shortly.

2. NBI interface required for integration

i) Rest (XML, JSON) APIs for sharing the Data between State Lead NMS to UNMS
ii) API description document from vendor specific NMSs from State lead NOCs.
iii) Details for JMS based Notifications for status /events /alarms/ updation at UNMS.
iv) Domain/vendor specific NEs/devices parameter details which are monitored/managed
at State level NOCs.
v) Inventory additions/deletions/changes and configuration changes shall be reported through APIs as well as real time JMS
notifications with timestamp.

28/28