Page 1 of 193 Scaling up of IT infrastructure installed under R-APDRP to whole DHBVN and UHBVN REQUEST FOR PROPOSAL (RFP) for selection of ‘IT Implementation Agency’ to assist the Haryana Discoms (DHBVN and UHBVN) for implementation of IT infrastructure For further details, please visit the website: www.dhbvn.com Purchaser: Dakshin Haryana Bijli Vitran Nigam Ltd On Behalf of Dakshin Haryana Bijli Vitran Nigam Limited Uttar Haryana Bijli Vitran Nigam Limited RFP Identification No: TER-03/RAPDRP/2014 Single Stage – Double Envelope Selection Procedure The last date for submission of RFP is 07/10/14 (01:00 PM) This document is meant for the exclusive purpose of RFP and shall not be transferred, reproduced or otherwise used for purposes other than that for which it is specifically intended.
Transcript
Page 1 of 193
Scaling up of IT infrastructure installed under R-APDRP to whole
DHBVN and UHBVN
REQUEST FOR PROPOSAL (RFP)
for selection of ‘IT Implementation Agency’ to assist the Haryana Discoms
(DHBVN and UHBVN) for implementation of IT infrastructure
For further details, please visit the website:
www.dhbvn.com
Purchaser: Dakshin Haryana Bijli Vitran Nigam Ltd
On Behalf of
Dakshin Haryana Bijli Vitran Nigam Limited
Uttar Haryana Bijli Vitran Nigam Limited
RFP Identification No: TER-03/RAPDRP/2014
Single Stage – Double Envelope Selection Procedure
The last date for submission of RFP is 07/10/14 (01:00 PM)
This document is meant for the exclusive purpose of RFP and shall not be
transferred, reproduced or otherwise used for purposes other than that for
which it is specifically intended.
Page 2 of 193
CONTENTS
1.0. About Discoms ........................................................................................................ 4
*Data as on 31st March’2013. Current % growth per annum for consumers is 7.5%.
1.2.2. UHBVN Profile
Sr. No Circle Name Consumers Sub-Division
Offices
Other Offices
Unit Nos. Nos. Nos.
1 Ambala 184932 7 3
2 Kurukshetra 146204 4 1
3 Karnal 163819 12 3
4 Panipat 262711 5 1
5 Kaithal 152603 8 2
6 Yamunanagar 160122 7 1
7 Jhajjar 235645 8 2
8 Sonepat 185480 9 3
Sr. No Circle
Name Consumers
Sub-
Division
Offices
Other
Offices
Unit Nos. Nos. Nos.
1 Hisar 365904 13 0
2 Gurgaon 233902 10 5
3 Faridabad &
Palwal 144280 8
0
4 Bhiwani 249690 12 3
5 Sirsa 208450 9 3
6 Narnaul 148147 7 3
7 Rewari 168746 6 2
8 Jind 196652 9 1
Total 1715771 74 17
Page 6 of 193
Sr. No Circle Name Consumers Sub-Division
Offices
Other Offices
Unit Nos. Nos. Nos.
9 Rohtak 249823 5 6
Total 1741339 65 22
*Data as on 31st March’2014. Current % growth per annum is 7.5% for consumers
2.0. About the Project
2.1. About RAPDRP
The Government of India in 10th Plan started Accelerated Power development and
reforms program for reforms in distribution with following objective:-
Reduction of AT&C losses
Bring about Commercial viability
Reduce outages & interruptions
Increase consumer satisfaction
Considering the need for continuity and to rein in the losses of the utilities, need was
felt to continue the initiative of APDRP in 11th plan which was termed as R-APDRP.
On review of the status and benefits achieved of APDRP, it was felt that to have
sustainable distribution business, it is essential to give impetus to IT enabling of the
sector on an integrated platform. The IT platform shall assist in capturing and
validating the energy and revenue model to gather in a transparent manner with
accuracy.
Also, considering the difficulties of domain expertise in IT area of the utilities and the experiences the utilities had, it was considered necessary to prepare SRS template, which shall provide the IT infrastructure for drawing the baseline data while addressing the need of IT back bone in the area of distribution business process to capture the benefits of the investments on sustainable basis.
RAPDRP (Part A) is under implementation in total 36 towns of UHBVN and DHBVN
to meet following objectives
a) Establishing base line data for accurate measurement of losses.
b) Improving customer services which include projects for establishment of IT
Infrastructure & deployment of applications like Meter Data Acquisition, GIS
based electrical asset mapping and consumer indexing, Meter Reading, Billing,
Page 7 of 193
Collections, MIS, Energy Audit, New Connection, Disconnection, Customer
Care Services, Web self-service etc.
Under the RAPDRP (Part A) scheme, the following IT Infrastructure Setup has been
envisaged in DHBVN:
1. Establishment of Data Center at Hissar
2. Establishment of Disaster Recovery Center at Panchkula
3. Establishment of a Common Centralized Call Center for both Utilities at
Gurgaon for seating capacity of 100 with a Toll Free No..
4. Providing all the following modules and systems:
a. Meter Data Acquisition System
b. Energy Audit
c. New Connection
d. Disconnection & Dismantling
e. GIS based Customer Indexing and Asset Mapping
f. GIS based integrated Network Analysis Module
g. Centralized Customer Care Services
h. Management Information System (MIS)
i. Web Self Service
j. Identity and Access Management System
k. System Security Requirement
l. Development of Commercial Database of Consumers
m. Metering
n. Billing
o. Collection
p. Asset Management
q. Maintenance Management
r. Document Management System
s. Mail / Messaging System
t. Enterprise Management System and Network Management System
u. Antivirus & Firewall System
v. Data Warehouse System with MIS application
5. AMR Implementation
6. DGPS based GIS Survey for all towns coming under the R-APDRP scheme
7. Establishment of LAN, MPLS-VPN and other networking in all the identified
towns of both the DISCOMs
8. Facility Management Services for 5 years from the “Go-Live” Date of Project
a. Integration, as envisaged in G1 section under 3.10 paragraph of SRS
Document, with existing applications.
Page 8 of 193
9. Data Migration for following applications as envisaged in section G1 under 3.9
paragraph of SRS, but not limited to
a. Metering
b. Billing
c. Collection
d. New Connection
e. Disconnection and Dismantling
f. Asset Management
g. Maintenance Management
Solution component mapping with business functions as implemented in RAPDRP is
legally domiciled in ________________________________
____________________________________________, (hereinafter “the Guarantor”)
which expression shall unless repugnant to the context thereof include his successors,
heirs, assigns have agreed to give the Supplier a security:
THEREFORE WE hereby affirm that we are Guarantors and responsible to you, on
behalf of the Supplier, up to a total of
____________________________________________________ and we undertake
to pay you without protest and demur, upon your first written demand declaring the
Supplier to be in default under the Contract, without cavil or argument, any sum or
sums within the limits of ______________________ as aforesaid, without your
needing to prove or to show grounds or reasons for your demand or the sum specified
therein.
This security is valid until _________ hours of the ___________________ day of
__________________, _____.
Page 107 of 193
Name
In the capacity of
Signed
Duly authorized to sign the security for and on behalf of
Date
Page 108 of 193
Appendix Un-priced BOM
Category Sub
Category Type/Discription Unit
Quanitity to be
supplied Make Model
Hardware for Sub Division Office Infrastructure for Non RAPDRP areas
Switches Layer II Switch
Nos.
Routers
Router for MPLS/ VPN Network
Nos.
Cabling System
Cables, Jacks etc.
Nos. Workstation / Equipment Cords
Nos.
IP Telephony IP Phone Nos.
UPS and Battery System
UPS for Subdivision offices 5 kVA Nos. UPS for Other offices 3 KVA
Workstation PCs, Printers & Others
Workstation PC (With Computer chair &table) Nos. Bar Code Readers Nos. Laser Jet Printers for cashiers Nos. Multipurpose Network Printer Nos.
Additional Components
Anti Virus Nos
Windows CAL Nos
Exchange CAL Nos
Metering Infrastructure
Metering Infrastructure GPRS Modem Nos.
Bandwidth for DHBVN and UHBVN
Page 109 of 193
Item Description Type Unit Total
Quantity Make
Bandwidth for Sub division offices
Network Connectivity - Primary Link - MPLS - VPN for 4 years (2 MBPS)
For 4 Years MBPS
Network Connectivity - Secondary Link - for 4 years (512 KBPS)
For 4 Years MBPS
Bandwidth for other offices
Network Connectivity Charges for Primary link for3 years(512 kbps)
For 4 years MBPS
Bandwidth for DC and DR
Item Description Type Unit Total
Quantity Make
Total bandwidth Requirement at DC (Secondary)
For 4 Years MBPS
Total bandwidth Requirement at DR (Primary)
For 4 Years MBPS
Total bandwidth Requirement at DR (Secondary)
For 4 Years MBPS
Additional Replication Bandwidth DC-DR Primary
For 4 Years MBPS
Additional Replication Bandwidth DC-DR Secondary
For 4 Years MBPS
Additional Internet Bandwidth DC Primary
For 4 Years MBPS
Additional Internet Bandwidth DC Secondary
For 4 Years MBPS
Additional Internet Bandwidth DR Primary
For 4 Years MBPS
Additional Internet Bandwidth DR Secondary
For 4 Years MBPS
Bandwidth for DHBVN and UHBVN
SIMS Type Unit Qunatity Make
No.
of
Years
Nos. Rs.
GPRS Sim (Consumer Meters) Nos. 4
Page 110 of 193
Appendix A- Mandatory Technical Specifications As per applicability to Part A and Part B of the project, ITIA should provide
documentary proof of compliance of following specification. Where it is not possible to
submit any certified proof for the same, ITIA shall self-certify that it would comply with
the specification during implementation or provide justification that specification is not
applicable to its scope of work.
Table 1: (i) Mandatory Technical Specifications for Part A of the project
A Solution Specifications Validation
Through
(Certificate/
Document/ Self
Certify)
Available/
Not
available
A.1 The solution must be as defined in
Section 9.0. i.e. Scope of Work of RFP.
In case of any conflict with any provision
relating to the SRS document and the
RFP document, the provisions of the
RFP document shall prevail for all intents
and purposes.
Self-Certificate
(ii) Mandatory Technical Requirements for Part B of the project
A Solution Specifications Validation
Through
(Certificate/
Document/ Self
Certify)
Available/
Not
available
A.1 The solution must be as defined in
Section 9.0. i.e. Scope of Work of RFP.
In case of any conflict with any provision
relating to the SRS document and the
RFP document, the provisions of the
RFP document shall prevail for all intents
and purposes.
Self-Certificate
B Hardware Technical Specifications
B.1 The hardware solution shall meet the
performance criteria specified in the
contract.
Certificate
Page 111 of 193
A Solution Specifications Validation
Through
(Certificate/
Document/ Self
Certify)
Available/
Not
available
In case the offered hardware does not
meet the performance criteria, the
supplier must provide additional
equipments or upgrade the equipments
without any additional cost to the utility.
B.2 The supplier shall submit the data sheets
for each of the hardware model detailing
the specifications of the hardware.
Document
B.3 The hardware models shall be supported
by the hardware OEM for a minimum
period of next four years.
Self-Certify from
OEM
C Mandatory Requirements of OEM for
Hardware
C.1 The OEM vendor shall have ISO
9001:2000 and ISO 14000 certifications. Certificate
C.2
The OEM vendor shall have an annual
turnover more than Rs. 250 crores from
hardware business in each of the last
three financial years.
Document & Self
Certify
C.3
The OEM vendor shall have at least one
service center within the State with
sufficient infrastructure.
Self Certify with
address details
Page 112 of 193
Appendix B- Technical Specifications Mandatory Technical Specifications: Only applicable for Part B of the project.
Below sheet has to be filled by the bidder as its response to technical
specifications requirements and to be submitted along with the bid, in a CD (in
duplicate)
The hardcopy of the same should necessarily be submitted along with the
technical bid submission
1.0 VPN/ MPLS Wide Area Network
Number Description/Requirement
Supplier Response
(Compliant/Non Compliant)
1.1 General Guidelines
1.1.1
WAN shall be a TCP/IP based network on a high-performance packet forwarding
technology that integrates the performance and traffic management capabilities of data link layer (Layer 2) switching with the scalability, flexibility, and performance of network
1.1.2 The WAN will be built to incorporate any open standards available as per Open Systems Interconnection (OSI) model. The network should support seamless transformation and integration of protocols.
1.1.3 The WAN has to upgrade the network infrastructure/software to support new protocols adopted by Internet community as a continuous process without any additional cost. For
example, migration from IPv4 to IPv6 as and when the transition is required
1.1.4 WAN must use the hardware devices, such as Internet routers, terminal servers, Internet systems that interface to Ethernets, or datagram-based database servers, which support
open standards and have open Network Management System (NMS) support for monitor
1.1.5 WAN network equipment should have Ipv4 and IPv6 features.
1.1.6 WAN shall have the capability to run IP routing protocols like OSPF (Open Shortest Path Find) version 2, OSPF v3, RIP v2, RIPng, OSPF over demand circuit, IS-IS, BGP4
1.1.7 WAN may run any routing protocol (like OSPF, BGP) depending on the individual design criteria of the WAN. It is mandatory that the network should allow interaction between
multiple routing protocols for keeping a unified network reach ability table across
1.1.8 While two routing protocols are interacting to exchange routing updates, there should be
the capability to selectively filter certain routes for security reasons
1.1.9
WAN should be capable to provision IP multicast based services. The same would require the capability of running industry standard IP multicast protocols like Protocol Independent Multicast (PIM) Sparse Mode and Dense Mode, Multicast OSPF (MOSPF),
multicast BGP (MBGP) and DVMRP
1.1.10 WAN should have the multicast group management capability through Industry standard
protocols like Internet Group Management Protocol (IGMP) version 1, 2 and 3
1.1.11
The voice networking of WAN should be based on IP and should be designed in such a
way that a central call processing system is able to service phones at remote locations. WAN should have the voice conferencing solution deployed based on industry standard protocols
1.1.12 All communications happening over the various links within the WAN should be encrypted using standard protocols like IPSec, 3DES & AES to ensure highly secure communication
1.1.13 WAN should have adequate device for performing intelligent packet filtering, URL filtering, context based access control, blocking of malicious contents to maximize security
1.1.14 All equipments proposed shall ensure optimum throughput to take care of the connectivity requirements of the network including minimum bandwidth requirement and scalability in bandwidth
1.1.15 All networking equipments proposed shall support SNMP
1.1.16
The capacity of the links at various tier of WAN will be up gradable subject to actual
usage and utilization for the particular channel. The Bidder shall be responsible for regular monitoring of bandwidth utilization and generating reports at regular interval
Page 113 of 193
1.2 WAN for Circle and Division offices
1.2.1 All connectivity of distant locations will be directly to the Data centre
1.2.2 The proposed network has to be on a minimum 2 Mbps VPN connectivity
1.2.3 The various offices like circles, divisions and various other offices as per the requirement of the utility will be connected to Data Centre via VPN cloud of the Service Provider
1.2.4
The uplink WAN connection will terminate in a networking device, which will be
connected to the switch via security equipment, which will ensure the fully secure enterprise VPN.
1.3 WAN for Sub division offices
1.3.1 The Sub divisional Head Quarters would be connected to the Data centre through minimum 2 Mbps VPN connectivity from service provider along with ISDN line as back up connectivity
1.4 Authentication
1.4.1 RADIUS, including Challenge/Response
1.4.2 LDAP
1.4.3 Native local user database
1.4.4 Active Card (RADIUS)
1.5 Encryption
1.5.1 SSL v2.0, 3.0
1.5.2 TLS 1.0 (RFC 2246)
1.5.3 IPsec (AES)
1.6 Granular Auditing and logging
1.6.1 User sign-in and sign-out
1.6.2 Session timeouts, including idle and maximum length session timeouts
1.6.3 User file requests, uploads, downloads, etc.
1.6.4 User connects and disconnects via clientless telnet/SSH function
1.6.5 Web requests, every HTML request. Java Applet socket commands, etc.
1.6.6 Bytes transferred for client/server application requests
1.6.7 The SSL VPN box should log for : User/admin authentication success /failure, access
1.6.8
Number of simultaneous users at each one hour interval (logged on the hour), gateway
address, session ID, session time, and cause of termination, Any changes to the system, Session timeouts, including idle and maximum length session timeouts
1.7 End point security: (This facility would be deployed as and when required)
1.7.1 Native Host check before permitting access to the resources including without having any preloaded agent on the end point PC.
1.7.2
Pre-Specified checks such as Antivirus update, Spyware, Ports check, process check,
File check, Registry check, Software version check like antivirus version and custom checks based on user flexibility.
1.7.3 Authentication parameter including username password, digital certificates, RSA token.
1.8 Access Privilege Management
1.8.1
The SSL VPN should permit access to a user based on : Dynamic Authentication: Source IP, Network Interface (internal/external), Digital
certificate, Endpoint Security - Host Checker/Cache Cleaner, User Agent (Browser), Sign-in URL SSL version and cipher
1.9 Role Definition
1.9.1
The following can be used to determine the identity of the user - User name - User attribute(s)
- Certificate attribute(s) - Groups (static, dynamic)
1.9.2
Role Mapping based on Simple expressions (AND Based) combining identity plus
restrictions: - Source IP - Digital certificate Endpoint Security
- Host Checker/Cache Cleaner - User Agent (browser) - Time of Day
- Login Time Authentication Type (e.g. dual factor) - Network Interface (external/internal)
1.9.3 Role mapping rules can by dynamically or periodically evaluated upon administrator's configuration changes and upon demand
1.10 Performance, High Availability and Scalability
Page 114 of 193
1.10.1 The SSL VPN solution should support hardware-based SSL acceleration for RC4, 3DES and AES encryption.
1.10.2 The SSL VPN solution should support software based compression for all traffic (HTTP, file, client/server application) enabling rapid response times even at very high concurrent
user loads
1.10.3 Support for High Availability of SSL VPN appliance
1.10.4 The SSL VPN units that are part of a cluster communicate session and database information among them for stateful failover. Stateful synchronization should be done for configuration, policy, profile, and session
1.11 Single Sign-on
1.11.1 Standards-based interface for extensive integration with password policies in directory stores (LDAP, Active Directory, NT, etc.)
1.11.2 Ability to pass user name, credential and other customer defined attributes to the authentication forms of other products (HTTP POST)
1.11.3 Ability to pass user name, credential and other customer defined attributes as header variables
1.11.4 Cookie Based, Basic Auth (W3C)
1.11.5 Support for multiple host names from the same appliance, as well as support for multiple customisable sign-in pages
1.11.6 Modes of operation: Clientless –Browser based Client : For client server access
1.11.7 Full Network access should also be supported with end point security.
2.0 IMPLEMENTATION PLAN
Number Description/Requirement
Supplier
Response (Compliant/Non
Compliant)
2.1 General
2.1.1 All network drops will be a dual drop of Category 6 rated cable. This configuration will support current application and present an additional growth capability.
2.1.2 The network drops will be terminated in compliance with Category 6 or higher specifications to two RJ45 jacks and labeled with IDF No., Panel No. (where applicable) and jack ID numbers.
2.1.3 All cable that runs back to cable telecom closets will be terminated on a Category 6 rated patch panel, clearly labeled for each jack
2.1.4 The cabling contractor should provide cable certification reports and warranty statements to verify each Category 6 drop.
2.1.5 Copper/UTP Category 6 cable runs exceeding 295 feet will be deemed unacceptable, as
they would be out of specification with regard to the EIA/TIA 568x specification
2.1.6
The maximum permitted horizontal distance is 90 meters (295’) with 10 meters (33’)
allowed as the total cumulative length for patch cables, jumpers cords, etc. (Total maximum length not to exceed 100 meters)
2.1.7 Horizontal cables are Category 6 or (XL-7) or higher rated 4-Pair /100 Ohm UTP cables
2.1.8 Copper cabling must have all four pairs terminated and pairs must not be split between jacks.
2.2 Required Installation Practices To Be exercised By The Contractors
2.2.1 Cable and cable bundles will not be attached to any electrical wiring or light fixtures, nor will its vertical deflection allow it to come in contact with ceiling grids, HVAC mechanical controls, fluorescent light fixtures, or drainage line piping.
2.2.2 All cables terminating at the distribution frame will be vertically straight with no cables crossing each other from twelve inches the ceiling area to the termination block
2.2.3
All MDF/IDF tie and station cable bundles will be combed and bundled to accommodate
individual termination block rows. Each cable or cable bundle will be secured to both the distribution frame and the structure to which the frame anchor points placed a maximum of nine inches apart starting at the center of the top of the termination block
2.2.4 For any given MDF/IDF, a horizontal and vertical alignment for all mounting hardware will
be maintained, providing a symmetrical and uniform appearance to the distribution frame
2.2.5 Contractor will firmly secure any surface mount device, including station cable
termination plates/jacks
Page 115 of 193
2.2.6 MDF/IDF, station cables, and tie a cable refers to distribution frames and cabling located inside the building as defined in any scope of work. All station cables in offices or work
areas will be installed behind the wall or inside provided floor or duct channels
2.2.7 Station cables will terminate on jacks as per the system requirements or specified by owner. All terminations will be made to Category 6 standards. It is the responsibility of
the Contractor to understand and comply with these requirements
2.2.8
IDF/MDF termination racks and panels will be mounted vertically or horizontally (if any
required) with a uniform spacing between each row of panels and jacks. Cable management will be mounted on the top, sides, and front as required to provide a symmetric
2.2.9
All Node Desk Top Station Cables shall meet the following criteria : • Category 6 Plenum cables will be installed for all interior environments. • All patch and station will be terminated on panduit Category 6 rated RJ45 jacks.
• All patch and station cables will be kept to a minimum length in order to keep the channel distance within the 100meter specification, as set by the EIA/TIA. • All data cable installations shall meet Category 6 Standards from the originating IDF to
the furthest remote cable termination point
Supplemental equipment refers to the different types of hardware, brackets racks and attachments required installing the cabling in the Data center complex distribution system
per these specifications.
2.2.10
All IDF/MDF wall mount racks shall include at minimum: - Vertical front and back cable management along watch side of rack
- Horizontal cable management at top of rack and every 48-72 jacks, or 72 port panel, thereafter. - Horizontal rack-mount surge protector including 12ft. cord for standard household
220V/15A power, On/Off switch, circuit breaker, and minimum 6 standard Multipurpose AC outlets. (To be installed in racks housing electronic equipment.)
2.2.11
All IDF/MDF floor mount racks will include at minimum :
- Secure attachment to building floor at bottom - Secure attachment to wall via ladder attachment to rack - Vertical front and back cable management along each side of rack
- Horizontal cable management at top of rack and every 48-72 jacks, or 72 port panel, thereafter. - Horizontal rack-mount surge protector including 12ft. cord for standard household
220V/15A power, On/Off switch, circuit breaker, and minimum 6 standard Multipurpose AC outlets. (To be installed in racks housing electronic equipment.)
2.2.12
• All IDF/MDF floor mount racks will include at minimum: - Access for mobility and service needs. - Leveling feet/pads for stability when not being serviced
- Vertical front and back cable management inside each rack - Adequate ventilation mechanism, including top-mount exhaust fans - Horizontal cable management inside of and at top rack and every 48-72 jacks, or 72
port panel, thereafter. - Horizontal rack-mount surge protector including 12ft. cord for standard household 220V/15A power, On/Off switch, circuit breaker, and minimum 6 standard Multipurpose
AC outlets. (To be installed in racks housing electronic equipment.)
2.2.13
The Contractor will provide a complete and final location table and spreadsheet indicating all wall jack locations including the following information: jack numbers, room
number, wall orientation per jack number North, South, East, or West, or Power Pole if applicable), landmark orientation and distance. Cable Installation through the floor will be released to meet applicable codes
2.2.14 The cabling system is not considered Category 6 complaint unless all cabling components satisfy the requirements for Category 6 UTP installation practices and certified
2.2.15 All UTP shall be installed according to the TIA/EIA standard regarding color codes,
labelling and documentation
2.2.16 The amount of untwisting when terminating Cat 6 jacks or panels is according to EIA/TIA parameters for Category 6 installations
2.2.17 The bend radii should not be less than the specification set by the EIA/TIA for Category 6 installations
2.2.18
Conduit or duct may be required for some projects. Any wire molding required shall be of
the non-adhesive-backed type using metal fasteners for attachment. Wall molding must be installed for all exposed cabling in marked areas
Upon completion, the Contractor will provide the following documentation:
2.2.19
1. A document indicating the MDF and IDF cable count assignments. § Test results of all cable plans and distances between MDF, IDF, and MDF/IDF to Station Termination locations.
2. An updated cabling location table indicating: § Cable drop label/Identifier § Location of each drop by room number/location point.
§ Location of each drop by north, south, east, or west wall, or power pole where applicable § Location of each drop by orientation/permanent landmark in the room
Page 116 of 193
§ A corresponding cross-reference for each drop identifying the source IDF/MDF identifier
§ A corresponding cross-reference for each drop identifying the source IDF/MDF building(s) § A corresponding cross-reference for each drop identifying the source IDF/MDF floor
§ A corresponding cross-reference for each drop identifying the source IDF/MDF room number § All information contained in the cabling location table will be delivered to owner via both
hard-copy/paper and electronic format. § One hard copy of each updated cabling location table will be pasted in the location-wiring closet (IDF/MDF), attached to or inside the rack or enclosure.
§ All documentation becomes the property of owner. § All document costs must be itemized and included in the quoted price for each project. 3. An updated floor-plan providing visual identification of the drops or IDFs added for the
installation (s) at the site : § Owner will provide, where/when a available, a floor-plan for the purpose of updating
owner drawings. § If a floor-plan does not exist for a site, contractor should create a reasonably accurate
hand-drawn floor—plan of the building and floors to be affected by the installation, attaching accurate dimension and orientation markings.
2.3 Fiber Optic Installation Requirements
2.3.1 Fiber optic cable shall be tight-buffered construction, all dielectric, with no metallic components of any kind. Outer cable sheath construction will be of NEC 8300 Rated OFNP (PLENUM) Jacket- Flame retardant material.
2.3.2 Each buffer tube within a cable must be color coded with none of the same colors appearing in one cable. Each fiber within a buffer tube must be color coded with none of the same colors appearing in the same buffer tube.
2.3.3 Jumpers will be premium performance two-fiber dual sub-unit cable, OFNR or OFNP
classified round type for routing inside cabinet spaces.
2.4 Terminations/ Connections / Splicing
2.4.1 Entire cable runs will be installed in one continuous length from bulkhead connector to bulkhead connector, including coiled loops, without splices or repairs.
2.4.2 Individual mated connector pair loss will be less than or equal to 0.20 dB.
2.4.3 All fiber distribution panels will have plastic dust caps on each unused fiber termination.
2.4.4 Multimode fiber patch cables will be terminated with ‘ST’ connectors and in accordance
with industry standards
2.4.5 Bulkhead distribution cabinets must have phenolic labels showing cable numbers and far end location for each cable terminated in the cabinet.
2.4.6 Cable installation shall meet all manufacturer specifications for tensile loading, bend radius, and vertical rise. All pulls involving a winch must be monitored for tension and cannot exceed the maximum tensile rating.
2.4.7 Lubricants may be used to facilitate pulling of cables but the lubricant must not be harmful to the cable, the raceway or humans
2.4.8 A swivel-pulling head must be used on all pulls to prevent twisting of the cable as it is
pulled into place.
2.4.9 Fiber-optic cable and inter-ducts installed in a cable but the lubricant must not be harmful to the cable tray should be fastened to the tray with UV resistant tie wraps at loft
intervals.
2.4.10 Each time a cable enters a cabinet or junction box it must be securely tied down with cable ties
2.4.11 No individual exposed fibers will be permitted.
2.4.12 Cable entrances into equipment or cabinets must be protected with insulated bushings or grommets.
2.4.13 A minimum of ten feet of extra cable should be coiled as a service loop at the end of
each run
2.4.14 Two, one-meter lengths of cable, cut from each reel of cable supplied, will be provided to owner as permanent retention samples. These samples are to be neatly tagged with the
manufacturer’s cable numbers, serial number, and reel number.
Page 117 of 193
3.0 Local Area Network
Number Description/Requirement
Supplier
Response (Compliant/Non
Compliant)
3.1 LAN Network setup should be planned for high-speed connectivity to the servers, with
non-blocking design
3.2 LSN should be able to handle congestion of traffic and manage the bandwidth available during peak load
3.3 The network equipment shall be highly reliable providing 99.99% uptime
3.4 The reliability should be provided at the levels including cabling infrastructure, active components, on link level, redundant cabling
3.5 The bidder shall identify the point of failures in active component; define multiple logical paths, load balancing and QOS implementation.
3.6 Reference Standards for Ethernet Switches should comply with IEEE, RFC’s and standards accordingly for features specified against different switches as specified in
RFP document
3.7 References and standards for Structured Cabling system should be compliant with standards specified in RFP document
4.0 Cabling System and Component Specifications
Number Description/Requirement
Supplier
Response (Compliant/Non
Compliant)
4.1 Specifications of UTP Cabling System
4.1.1 The specification of UTP Cabling system should be meet standards as specified below:
i Type Unshielded twisted pair cabling system, TIA / EIA 568-B.1 addendum Category 6 Cabling system
xiii Grounding 2 Nos. of earthing lugs, pre-loaded
xiv Cable Management rings
Front and rear cable management rings, pre-loaded
xv # of 6-port / 12-port
adapter plates 4 / 4 Max.
xvi Fiber optic patch panel
Wall mounted Fiber optic patch panel
xvii Dimension 12cmX10cmX38cm (HXDXW)
xviii # of fibers 24
xix # of OSP Cables for
termination Minimum 2
xx # of 6-port / 12-port adapter plates
4 / 4 Max.
4.2.4 The specification of Fiber Optic Adapter plates should be meet standards as specified below:
i Fiber Optic adapter plate
6-port, SC-Style, SM & MM
ii Attenuation Max of 0.75 dB per mated pair
4.2.5 The specification of Fiber Optic Patch cord should be meet standards as specified below:
i Fiber Optic Patch
cord SC-SC, SM &MM
ii Insertion Loss Less than 0.5db
iii Return Loss More than 50 db
Page 121 of 193
5.0 Switches
Number Description/Requirement
Supplier Response
(Compliant/Non
Compliant)
5.1 General
5.1.1
All active LAN components such as switches, offered shall be of the same
Make/manufacturer and shall be covered under same back-up guarantee from the same OEM, to ensure full compatibility, inter-working and inter-operability.
5.1.2 The minimum no of switches offered shall be as follows
1) Layer II switch – 1no
5.2 Common to all switches
5.2.1 All switch chassis shall be modular & rack mountable
5.2.2 The chassis configuration shall provide to 3 free slots for future expansion after full port module configuration and with redundant switch fabrics, control modules, CPU cards and its operating Software /Supervisors
5.2.3 The chassis shall provide shared memory architecture and hot swappable modules.
5.2.4 The chassis should support interfaces for 100BASE-FX, 10/100 BASE-TX,
10/100/1000BASE-T , 1000BASE-SX,-LX, and long haul (-LX/LH, -ZX) full duplex.
5.2.5 All the ports on the Switch shall be offered with requisite connecting cables and Trans-receivers, if any for termination on Jack/Patch Panel.
5.2.6 The switch should support the following protocols:
i IEEE 802.3ad Link Aggregation or Equivalent IEEE 802.1p (Priority Queues)Gateway Load balancing protocol Hot standby routing protocol
ii
Auto negotiation for link speed negotiation IEEE 802.1Q VLAN Tagging/Trunking IEEE
802.1d multiple Spanning Tree group, A minimum of 20 instance of spanning tree groups is desired on layer 3 chasis.
iii Should provide for fast convergence of spanning tree.
iv
IEEE 802.3ad Link Aggregation or equivalent should provide for at least 8 ports grouped in single logical link. Link aggregation shall be supported from other switches or across
the similar chassis. Servers and Switches connectivity from switch should be configurable on load sharing layer2 link aggregation. Switch shall also provide configuration for port mirroring and 9000 byte jumbo Frame support for Gigabit ports
v IEEE 802.1w -Quick Convergence Spanning Tree
vi IEEE 802.1S-Multiple Instances of Spanning Tree
vii IEEE 802.3u Fast Ethernet
viii IEEE 802.3x Flow Control
ix IEEE 802.3z Gigabit Ethernet
x Multi-Homing Support, Multicast Support & Multicast must be supported at Layer 2 in
hardware so that performance is not affected by multiple multicast instances
5.2.7 Switch should have policy based quality of services
i
Switch should support traffic classification based on Layer2, Layer 3 and Layer 4 parameters like ingress port, Ether Type (IP/IPX), VLAN ID, IP (RFC 2474 and RFC 2475)protocol type, Source IP addresses, Destination IP addresses, Source TCP/UDP
ports, Destination TCP/UDP ports
ii QoS based on classification, marking, prioritization and scheduling
iii
Bandwidth Engineering & Management – Per Port Minimum, Black-hole (Blocking), excess bursting, shaping Support for L3/L4 filtering capabilities for inter VLAN traffic, VTP for VLAN management, Private & Dynamic VLAN support, High Priority Transmit
Queuing, Support for multiple WRED drop thresholds per queue
Page 122 of 193
iv QoS-based forwarding based on IP precedence
v QoS implementation should support all 64 DiffServ Code Points (DSCP) and all 4 DiffServ Classes. QOS support for 8 hardware queues per port. Strict priority and Weighted priority mechanisms for queuing and scheduling
vi IEEE 802.1p User Priority should be supported IEEE802.1p to DiffServ mapping also needs to be supported. Diffserv,IGMP
5.2.8 Switch should have following management features :
i At least 5 levels of Management access to the switch for http, rlogin, telnet, snmp, rsh
access to the switch.
ii SNMP Support: RFC1157 SNMP v1/v2c
iii TFTP Upload/Download
iv Port Mirroring: Port to Port, VLAN to VLAN, Bi-Directional
v RMON: 4 Group (Statistics, Alarm, Events, History), on every port, no impact to performance
vi Switch must be remotely managed with SSH support via one telnet session for all module configuration
vii Should have functionality to add new features by upgrading only the central switching processor
viii Switch should support Remote SPAN feature to direct traffic from remote switch to the
snooping device connected to central switch
ix Policy Based Management
x Provisioned and Dynamic Policies at Layers 1-4 for QoS and Security
xi Real Time Multi-Port Statistics
xii Mac/IP Address Finder
xii Device and Port Groupings for Navigation and Policy Management
xiv Private and Enterprise MIB
5.2.9 Switch should have following security features:
i should provide for User level security – Discard unknown MAC addresses on the switch.
ii Layer 3 /4 Access Control Lists (ACLs) standard and extended Support for IEEE 802.1x authentication for edge control against denial of service attacks and other management control policy.
iii Security (User Access): Internal DB/External RADIUS /TACACS+, Support for IPSec protocol support, Configuration Change Tracking, System Event Logging, Syslog
5.2.10
Packet filtering at the Network IP filtering using “deep” packet filtering with level should
be supported support for Layer 4 parameters and even content based filtering. RADIUS authentication needs to be supported for switch access.
5.3 Switches
5.3.1 The switch should support 10/100 Mbps Ethernet ports.
5.3.2 The switch should support Gigabit Ethernet ports on fiber or copper
5.3.3 The switch should have the support for 10-Gigabit Ethernet ports
5.3.4 The switch shall support WDM (Wave Division Multiplexing) for Optical networking
5.3.5 The switch shall support FAN redundancy & switch fabric redundancy
5.3.6 The vendor should indicate 1. The back plane speed of the offered switch 2. Port densities Support
Page 123 of 193
3. Switching Latency 4. L3 forwarding rate
5. No. of MAC Addresses supported 6. No of VLAN supported
5.4 Layer II Switch
5.4.1 The switch should support 10/100 Mbps Autosensing UTP Ports and 1000 Mbps Gigabit
Ethernet 1000BaseSX ports.
5.4.2
The vendor should indicate 1. The back plane speed. of the offered switch
2. Port densities Support 3. Switching Latency 4. L3 forwarding rate
5. No. of MAC Addresses supported 6. No of VLAN supported
6.0 Routers
Number Description/Requirement
Supplier
Response (Compliant/Non
Compliant)
6.1 System features
6.1.1
The Routers shall be compatible with Owners existing Wide Area Network. The Wide
Area Links are planned for 2Mbps or higher Bandwidth capacity on leased circuits from ISPs (BSNL, MTNL etc.)
6.1.2 Equipped with Redundant Power Supply Unit (RPSU)
6.1.3 Routers shall be configurable and manageable through local console port, http interface, NMS software and as well through Telnet
6.2 Features of Central Router For MPLS/ VPN Network
6.2.1 Support for Layer 3 MPLS VPN connection.It shall support PPP /Frame Relay transport over MPLS.
6.2.2 In-built monitoring and diagnostics to detect failure of hardware
6.2.3 LED/LCD indication for monitoring Operational status of each module
6.2.4 Configuration Changes without Rebooting
6.2.5 High MTBF & low MTTR
6.2.6 Rack Mountable on to 19"Racks
6.2.7 Chasis should have the following specification:
i
Shall be provided with configurable slots for interface Modules. All the modules in the
Router shall be Hot Swappable Module
ii Provided with Redundant Power Supply Unit. Single Power supply should support fully loaded Chassis
iii Provided with high speed Redundant CPU with distributed /Shared Memory architecture
iv Dual Flash support. It shall be possible to upgrade the FLASH to enhance the router software functionality
6.2.8 128 MB DRAM, 16 MB FLASH Memory
6.2.9 RS 232 I/F Console Port
Page 124 of 193
6.2.10 LAN Port: 8 Port of 10/100/1000BaseT and 8 Port 1000Base X ports
6.2.11
32 Serial ports with synchronous speed up to 2Mbps and with interface support for V.35, V.24 Ports (to be interfaced to leased circuits or SCPC / MCPC available on Multiplexer).
2x 4nos. of G.703 Ports 75 Ohm. 2x 4port ISDN PRI channelised E1 interfaces for 120 Ohm G.703 I/f . Additional Module/Modules for 8 Serial Port as Spare
6.2.12
I/f Cable: for all the WAN ports Connector Cable for connecting to SCPC / MCPC’s/leased E1- V.35 Port (DB25 Connector) shall be prepared as per Pin Details to
be given by owner
6.2.13 Sufficient free slots to accommodate additional 16 (min.) Serial Ports
6.2.14 TCP/IP, IPversion6 support, NAT Support as per 1631
BGP4 with CIDR implementation as per RFC 1771. The implement should be compliant as per RFC1745 that describes BGP4/IDRP IP OSPF interaction. It shall provide Policy routing to enable changes to normal routing based on characteristics of Network traffic.
ISIS protocol support
6.2.16 Bridging & Tunneling Transparent, Spanning Tree Algorithm, Auto Learning Protocols: L2TP, PPTP capability
6.2.17
WAN Protocols: Frame Relay (LMI & Annex.D & ITU Annex A), PPP (RFC1661), Multi-link PPP (RFC1717), HDLC/LAPB, Frame Relay support shall include Multi-protocol encapsulation over Frame relay based on RFC1490, RFC 1293 for Inverse Arp/IP, DE bit
support
6.2.18 Should have following features for Network management:
i
SNMP, SNMPv2 support with MIB-II. and SNMP v3 with and Security authentication. Implementation control configuration on the Router to ensure SNMP access only to
SNMP Manager or the NMS work Station.
ii Asynch. Serial Port. RMON 1 & 2 support using service modules for Events, Alarms, History.
iii Shall support multilevel access.
iv Shall be Manageable from any Open NMS platform.
v Shall support for telnet,ftp,tftp and web enabled Management.
vi Should have debugging facility through console.
vii
Authentication support shall be provided via RADIUS (Remote Authentication Dial-IN User Service), AAA support, PAP/CHAP, 3DES/IPsec encryption with hardware based encryption services using VPN module.
viii IP Fire Services via Firewall Module. IDS Services via Service Modules
6.2.19 It should have the following Optimization features:
i
Data Compression for both header and payload to be supported for X.25, Frame Relay and Leased/Dial-up WAN Links. Dial restoral on lease link failure Dial on demand or congestion, Load Balancing.
ii
Support for S/W downloads and quick boot from onboard Flash. Online software re-configuration to implement changes without rebooting. Should support Network Time Protocol for easy and fast synchronization of all Routers
6.2.20 It should have the following QoS Support features:
i
RSVP (Resource Reservation Protocol as per RFC 2205), IGMP (Inter Group Management Protocol Version 2 as per RFC 2236, Multicast Routing support DVMRP, MOSPF, MBGP, etc. Policy routing ( It shall be possible to affect the normal routing
process for specific mission critical traffic through specified alternate routes in the network.
ii
A class based scheduling, Priority Queuing mechanism that shall provide configurable
minimum Bandwidth allocation to each class and IP Precedence.
Page 125 of 193
iii
Congestion Avoidance – Random Early Detection (RED). Support for Differentiated
Services as per RFCs 2474, 2475, 2598 & 2597
6.2.21 720 Gbps Backplane
6.2.22 Switching Performance: 30MPPS upgradeable to 400Mpps
6.3 Requirements for Router at each Utility Office
6.3.1 Flash: Default 8MB and maximum 72MB
6.3.2 SDRAM: Default 64MB and maximum 320MB
6.3.3 Console Port: RS 232 I/F
6.3.4 LAN port requirements as per SRS Document
i Two fixed 10/100M high speed Ethernet ports
ii Two fixed high-speed synchronous ports
iii One Port ISDN BRI-S/T interface
iv One AUX
6.3.5
Network Protocol: TCP/IP and support for IPversion6 . Shall provide IP address
Management via NAT Support as per RFC 1631
6.3.6
Routing Protocols: RIPv2, OSPFv2 (RFC1583 & RFC 1793), OSPF on demand, BGP, BGP4 with CIDR implementation as per RFC 1771. The implement should be compliant
as per RFC1745 that describes BGP4/IDRP IP OSPF interaction. It shall provide Policy routing to enable changes to normal routing based on characteristics of Network traffic. ISIS protocol support.
6.3.7 Bridging & Tunneling Protocols: Transparent, Spanning Tree Algorithm, Auto Learning L2TP, PPTP capability
6.3.8
WAN Protocols: Frame Relay(LMI & Annex.D & ITU Annex A), PPP (RFC1661), Multi-link PPP (RFC1717), HDLC/LAPB, Frame Relay support shall include Multi-protocol encapsulation over Frame relay based on RFC1490, RFC 1293 for Inverse Arp/IP, DE bit
support
6.3.9 Should have following features for Network management:
i
SNMP, SNMPv2 support with MIB-II. and SNMP v3 with and Security authentication. Implementation control configuration on the Router to ensure SNMP access only to
SNMP Manager or the NMS work Station.
ii Asynch. Serial Port. RMON 1 & 2 support using service modules for Events, Alarms, History.
iii Shall support multilevel access.
iv Shall be Manageable from any Open NMS platform.
v Shall support for telnet,ftp,tftp and web enabled Management
vi Should have debugging facility through console.
vii
Authentication support shall be provided via RADIUS (Remote Authentication Dial-IN User Service), AAA support, PAP/CHAP, 3DES/IPsec encryption with hardware based
encryption services using VPN module.
viii IP Fire Services via Firewall Module. IDS Services via Service Modules
6.3.10 It should have the follwing optimization feature:
i
Data Compression for both header and payload to be supported for X.25, Frame Relay and Leased/Dial-up WAN Links. Dial restoral on lease link failure Dial on demand or congestion, Load Balancing.
Page 126 of 193
ii
Support for S/W downloads and quick boot from onboard Flash. Online software re-configuration to implement changes without rebooting. Should support Network Time
Protocol for easy and fast synchronization of all Routers
6.3.11 It should have following features for QoS
i
RSVP (Resource Reservation Protocol as per RFC 2205), IGMP (InterGroup Management Protocol Version 2 as per RFC 2236, Multicast Routing support DVMRP,
MOSPF, MBGP etc. Policy routing ( It shall be possible to affect the normal routing process for specific mission critical traffic through specified alternate routes in the network.
ii A class based scheduling, Priority Queuing mechanism that shall provide configurable minimum Bandwidth allocation to each class and IP Precedence.
iii Congestion Avoidance – Random Early Detection (RED). Support for Differentiated Services as per RFCs 2474, 2475, 2598 & 2597.
6.3.12 32 Gbps Backplane
6.3.13 Switching Performance: 100 Kpps upgradeable to 400 Kpps
6.4 Requirements for Router at Internet Gateway
6.4.1 Integrated Firewall and IDS similar to that for Core switch
6.4.2 Support for Layer 3 MPLS VPN connection
6.4.3 In-Built monitoring and diagnostics
6.4.4 LED/LCD indication for monitoring Operational status of each module
6.4.5 Configuration Changes without Rebooting
6.4.6 High MTBF & low MTTR
6.4.7 Rack Mountable on to 19"Racks
6.4.8 Chasis as per SRS Document
6.4.9 128 MB DRAM, 16 MB FLASH Memory
6.4.10 RS 232 I/F Console Port
6.4.11 LAN Port: 8 Port of 10/100/1000BaseT and 8 Port 1000Base X ports
6.4.12 I/f Cable
6.4.13 Sufficient free slots to accommodate additional 16 (min.) Serial Ports
6.4.14 TCP/IP, IPversion6 support, NAT Support as per 1631
6.4.15 Routing Protocol support as per the SRS Document
6.4.16 WAN Protocol support as per the SRS Document
6.4.17 Network Management Capabilities as in the SRS Document
6.4.18 Optimization Features as in the SRS Document
6.4.19 QoS Support as per SRS Document
6.4.20 720 Gbps Backplane
6.4.21 Switching Performance: 30MPPS upgradeable to 400Mpps
Page 127 of 193
7.0 IP PHONES
Number Description
Supplier Response
(Compliant/Non
Compliant)
7.1 IP Phone
7.1.1 10/100BASE-T Ethernet connection through an RJ-45 interface for LAN connectivity
7.1.2 Differentiated Services Code Point (DSCP) tagging
7.1.3 Support for G.711µ, G.711a and G.729a/b audio compression codecs.
7.1.4 Software upgrade supported using a Trivial File Transfer Protocol (TFTP) server
7.1.5
Voice activity detection, silence suppression, comfort-noise generation, and error
concealment.
7.1.6 H.323 / SIP Support.
7.1.7 Inline Power (7.5W), 802.1af POE (15.4W) and Power Adapter Options for power.
7.1.8 Inline power and optional AC to DC power adapter.
7.1.9 Pixel-based display.
8.0 Anti Virus Solution
Number Description
Supplier Response
(Compliant/Non
Compliant)
8.1 Technical Specifications for Antivirus at desktops
8.1.1 The antivirus solution should provide enhanced antivirus protection for desktops.
8.1.2 Should have a Centralized Management Console
8.1.3 Should be a Single, Configurable Installation with centralized configuration & policy management.
8.1.4
Should have a Common Distribution Mechanism via combination of push & pull
Technology for better BW management
8.1.5
Should have logical group based on IP addresses (Subnets). Should support integration
with Active directory for directory structure of computers for better management
8.1.6 Should be support Multi-Platform OS Support
8.1.7 Should support Policy Enforcement
8.1.8 Should have Common, Extensible Scanning Engine
8.1.9 Should have Configurable Scanning. Should have the ability to control the amount of CPU resources dedicated to a scan process
Page 128 of 193
8.1.10
Should have Unknown Virus Detection & Repair. Should have behavioral & Heuristic scanning to protect from unknown viruses. Should have buffer overflow protection
integrated with AV scan engine for protection from threats/exploits that uses buffer overflow
8.1.11 Should have Compressed File Detection and Repair
8.1.12 Should have Research Centers for proper updates as well as technologies to support the outbreak
8.1.13 Should have 24*7 Global Technical Support
8.1.14 Should ensure security policy enforcement by integrating and centralizing installation, deployment, management & updating
8.1.15
Should conserve n/w b/w by updating virus definitions with incremental updates. Should support daily update for definition files. Size of daily update should be optimal and in the range of 10-12MB
8.1.16 Should be able to support the Platforms of desktops of the utility
8.1.17 Anti-Virus Software must have the capability to detect and clean Virus
8.1.18
Should be able to detect new classes of viruses by normal virus definition update
mechanisms
8.1.19
Should provide common definitions for all operating systems supported & across all
product ranges.
8.1.20 Should be able to update definitions & scan engine on the fly, without a need for reboot or stopping of services on servers.
8.1.21 Should be able to add files, folders or extensions to an exclude list so that they are not scanned on access.
8.1.22 Should enable automatic submissions of unknown/suspected virus samples to vendor and automatic response/delivery of the cure.
8.1.23 Should allow for incremental virus definition and scan engine updates.
8.1.24 It should recognize a missed event on a machine, which was switched off, and restart the same when machine is turned on.
8.1.25 The anti-virus software should be able to automatically detect and update definitions and scan engine form the nearest Distributed repository in the network.
8.1.26 Should be able to set and monitor client server configuration remotely.
8.1.27 Should be able to lock down all anti-virus configurations at the desktop.
8.1.28
Should be able to optionally make the client user interface invisible for transparent
protection.
8.1.29 User should be prevented from being able to uninstall the anti-virus software.
8.1.30
Must be able to distribute new and update anti-virus software, virus definitions and configuration files automatically to clients and servers from a central location (Clients
need not login to the central server to download the updates)
8.1.31 Should be able to view all servers and clients from one console.
8.1.32
Should be able to initiate virus sweeps remotely (central command to scan all machines
in case of an outbreak Should support folder/directory/share lockdown centrally to contain virus outbreak. Should support blocking of files based on their name to stop
8.1.33 Should be able to perform manual or scheduled virus scans on individual computers remotely.
8.1.34 Must provide centralized event logging to locate and cure virus problems.
8.1.35 Alerts on virus activity should be passed on to administrator
8.1.36 OS INSTALLER SUPPORT- should be incorporated for a standards-based installation. Should support installation of software package in both format OS Installer & EXE file
Page 129 of 193
8.1.37 Should enables administrators to identify which machine has generated a threat that is spreading by an open file share (for example, Nimda or CodeRed).
8.1.38
Should enable administrators to easily move clients (who have changed departments, for example) from one physical parent server to another simply by dragging and dropping through the central management console.
8.1.39 Should store event data generated while a client is disconnected from the corporate network and forwards it when the client reconnects.
8.1.40 Should enables administrators to launch an immediate LiveUpdate session on single or multiple clients during an outbreak.
8.1.41 Should enable administrators to select the events that clients forward to their parent servers and those secondary servers forward to primary servers.
8.1.42
Should extends virus, worm, and Trojan horse detection capabilities to include certain
non-virus threats, such as Sypware, Trackware, Adware, Dialers, Joke Programs, Remote Access, and Hack Tools, which can be used with malicious intent.
8.1.43
Should scan the body text and attachments of incoming e-mail messages that are
delivered through POP3 / IMAP mail clients
8.1.44 Auto Protect should be loaded on system startup, and then unloaded on system shutdown to help protect against viruses, such as Fun Love.
8.1.45 Should scan in-memory processes on disk for threats. If a threat is detected, the running process can be terminated
8.1.46 Should have enhanced protection from Spyware and Adware, including: Real-time protection to reduce the risk of Spyware reaching the system.
8.1.47 Should automatic remove Spyware and Adware for easy disposal of security risks.
8.1.48
Should have Side-effect repair to clean up registry entries, files, and browser settings
after hard-to-find Spyware infection.
8.1.49 Should have enhanced tamper protection that guards against unauthorized access and attacks, protecting users from viruses that attempt to disable security measures.
8.2
TECHNICAL SPECIFICATIONS - ANTIVIRUS PROTECTION FOR MICROSOFT
EXCHANGE
8.2.1
Should support Windows 2000 Server/Advanced Server/Datacenter (Service Pack 3),
Windows 2003 Standard/Enterprise/Datacenter, Microsoft Exchange 2000 (Service Pack 3) and Microsoft Exchange 2003
8.2.2 Should provide a comprehensive solution consisting of multi-level anti-spam, rules-based content filtering and antivirus.
8.2.3 Should be able to control spam more effectively by having multiple score assignment to every spam message with heuristics anti-spam detection
8.2.4
Should allow messages to be handled appropriately based on the heuristics-assigned
spam score with multiple spam disposition options.
8.2.5 Should incorporate intelligent, rules-based content filtering to prevent unwanted content from entering and confidential information from leaving the network.
8.2.6 Should minimize false positives by creating a trusted sender Whitelist.
8.2.7 Should bypass heuristic anti-spam & RBL (Real-time Blacklist) for certain recipients with recipient Whitelist.
8.2.8 Should eliminate the entire message automatically with Mass Mailer Cleanup, not just attachments generated by mass mailer worms.
8.2.9
Should update automatically with new virus definitions from internet to keep your
protection up-to-date.
8.2.10 Should protect against new viruses without requiring re-installation of software, helping to reduce the cost of ownership.
8.2.11
Should automatically filter out emails with inappropriate attachment names, extensions,
or content, reducing traffic on your Microsoft Exchange servers
8.2.12 Should have an alternate to automatically update all of the Microsoft Exchange Servers from an internal virus definition server that will pick up updates from internet.
8.2.13 Should provide immediate protection for new mailboxes and public folders.
8.2.14
User/Group Based Rules - User/Group based rules should provide the ability to assign
rules to only apply to a certain group of users or create global rules with exceptions. Users and groups can be taken from active directory or they can be entered using full email addresses or wild cards
8.2.15 Attachment Content Scanning – Should scan for content contained within most file types including Microsoft Office documents, Adobe Acrobat, text, RTF, and database files.
8.2.16
True-file Typing for Multimedia and Executables – Should block/Quarantine multimedia
and/or executable files based on true file type (regardless of file extension). One of the following dispositions should be applicable: delete attachment, delete message, quarantine file, or log only
Page 130 of 193
8.2.17
Simplified Content Rule Interface – The interface for creating content filtering rules should ease the process of creating custom rules. Match lists should be added and
edited within the content filtering pages. Rules should include content to match on and exceptions within the interface to better display the intent of a rule
8.2.18
Generate Reports across Multiple Servers— Should kick-off reports on each individual
server from a central location and then browse to individual servers to view the report
8.2.19
Should be able to view a summary of activity and information for all Microsoft Exchange servers that are managed within a group, including consolidated spam and anti-virus
data, from the home page.
8.2.20
Expanded Protection against Security Risks— Should have the ability to detect expanded threats such as joke ware, Spyware, Adware and other non-viral risks.
Separate dispositions should be applicable to detected security risks including delete file, delete message, quarantine and log-only
8.2.21
Auto-generated Summary Reports— Should create a summary report of all activity on a single Microsoft Exchange server, and automatically generate the report at a given date and time.
8.2.22
Auto-generated Email Report– Once a report is generated; it should be automatically
delivered to specified recipients.
8.2.23 Graphical Reports– Reports should be generated that include charts and graphs to provide a clear picture of virus, filtering, and spam activity within an organization.
8.2.24
Should have different log database for detection event and product. Should provide multiple scanning options like – proactive scanning, Background scanning, Transport level scanning. Should provide scanning of nested archived files for atleast 30 times
9.0 Hardware for AMR based data logging system
Number Description
Supplier Response
(Compliant/Non
Compliant)
9.1 Modems for AMR System
9.1.1 Interface capability with RS232 cable
9.1.2
Should be capable of operating on Three phase supply drawn from the Meter input itself.
Auxiliary Power supply will not be acceptable.
9.1.3
The operating voltage range for the modem should be 90 V ac P-P to 440 V ac P-P, so that the modem can be used on both HT & LT Trivector Meters. How ever the modem
should also be capable of operating on single phase 230 V, 50 Hz power supply. The modem sh
9.1.4
The Modem should be capable to transfer the entire data of Trivector Meter in less than
10 Minutes after connection is made assuming there is no line disturbance.
9.1.5
The Modem should be supplied with power cable, antenna with co-axial cable of suitable length, RS 232 connecting cable, mounting adopter etc. and should be complete in all
respects.
9.1.6 Sealing: The modem should cover and body should have arrangement for sealing. In addition to this, the SIM card holder cover should also have arrangement for sealing.
9.1.7
The Modem should have flexible external antenna to enable placement of the antenna at
the location of strongest signal inside the Metering Cubicle.
9.1.8
Outage Notification: In the event of an outage, the modem should be able to initiate
separate call or send SMS to predefined number to notify the outage event with data and time of occurrence and restoration.
9.1.9
In the event of an outage, the modem should be able to initiate separate call or send
SMS to predefined number to notify the outage event with data and time of occurrence and restoration.
9.1.10
The Modem should act a completely transparent channel i.e. the Commands
received from Sub Division Data acquisition server should be conveyed to meter and data from meter should be conveyed to Sub division data acquisition server without any change
9.1.11
Data collection from meter should take place only after connection is established between Data acquisition server and Meter. Data should not reside in the modem before the time of transmission to Sub division server, to avoid chances of tampering of data
Page 131 of 193
9.1.12 The Modem should be capable of operating with SIMs of local GSM/CDMA Service provider in the area.
9.1.13 Data enabled SIM card will be provided by the utility and monthly SIM charges will be borne by the utility.
9.1.14 Modem should be capable for continuous working for 24 hours every day under field conditions, even when enclosed in Metering Cubicles at Consumer sites.
9.1.15 Software shall have facility for Auto-Scheduler to enable automatic / Unattended data collection during night hours.
9.1.16
GSM /GPRS/EDGE Modems and SIM cards Specifications as per the below
requirements:
i GSM Modem shall be suitable for long duration data transmission and shall be protected from external interference of systems working at different bands.
ii
Mechanical Specifications :- Modem should be a compact model housed in a polycarbonate / engineering plastic / Metallic enclosure. The modem should comply with IP55 degree of protection
iii
Environmental Specifications :- The Modem shall meet the following environmental specifications : - Ø Storage Temperature : -20 degrees to +70 degree Celsius
Ø Operating Temperature: -10 degrees to +60 degree Celsius Ø Humidity:- 95% RH ( Non - Condensing)
iv
Communication Capabilities: -
Ø Modem should be Dual Band modem capable of operating at 900 and 1800 MHz GSM transmission. Ø Modem should support both Data and SMS transmission. It should have both GSM
and GPRS/EDGE features.
v
Interface :- Ø Modem should have an RS232 Interface through a 9 pin or 15 pin D type Connector
for connection to Meter. Ø The SIM interface should be a 3 V Interface in accordance with GSM 11.12 phase 2 with an retractable SIM cardholder, which should be fully inserted inside the modem. The
holder opening should have a sliding cover with provision for sealing after placing of the SIM card. The modem shall accept the standard SIM Card. Ø Modem should have a SMA Antenna connector
vi
Power :- Ø Maximum Power Output should be 2 W at 900 MHz (Class 4) and 1W at 1800 MHz
(Class 1). Ø The RF functionalities should comply with the GSM phase II/II+ compliant, EGSM 900/GSM 1800 recommendation. Ø VA Burden of the Modem should not exceed 3.5 VA during data communication
§ Modem should use standard AT Command set (GSM 07.05, GSM07.07) for settings of the modem. § TCP/IP stack access via AT commands
§ Internet Services : TCP, UDP, HTTP, FTP, SMTP, POP3 § Max. Baud Rate: for GSM Operation - 9600 bits/sec
ix
CSD Data transmission features :- § Data circuit asynchronous, and non transparent upto 14.4 Kb/s § V.110
§ USSD Support
x
GPRS Data transmission features :- § GPRS Class B Multi slot class 12 or class B Multi slot class 10
§ Packet channel support : PBCCH § Coding Schemes: CS1 to CS4 compliant with SMG32 (Release97)
xi
EDGE Data transmission features :-
§ EDGE (EGPRS) Multi slot class 12 or Multi slot class 10 § Mobile station Class B § Modulating and coding schemes : MCS 1 to 9
§ Packet channel support : PBCCH
xii SMS Features: - § Text and PDU§ Point to point (MT/MO)§ Cell broadcast
xiii
Operational Indicator :- The Modem should have separate LED indications for transmit data, received data, carrier detects and Power ON, etc. to indicate Power on position and to indicate the availability of signal at the place of installation
9.1.17 CDMA Modems and SIM cards Specifications as per the below requirements:
i Communication Capabilities
Modem should be Dual Band modem capable of operating at
800 and 1900 MHz CDMA transmission. Modem should support both Data and SMS transmission.
Page 132 of 193
ii Power Supply Input Power (90V~310V A.C.) with 6KV Surge tested AC Power supply
iii Mechanical Specifications
Modem should be a compact model housed in a polycarbonate / engineering plastic / Metallic enclosure. The modem should comply with IP55 degree of protection.
Modem shall be suitable for long duration data transmission and shall be EMI/EMC tested for protection from external interferences.
iv
Environmental
Specifications
The Modem shall meet the following environmental specifications : -
Ø Storage Temperature : -20 degrees to +70 degree
Celsius
Ø Operating Temperature: -10 degrees to +60 degree Celsius
Ø Humidity:- 95% RH ( Non - Condensing)
v Interface
§ RS-232 Serial supporting remote control by AT Commands
§ SMA Antenna connector,
§ RUIM SIM Card Holder
vi Packet Data Features
CDMA2000 1xRTT, up to 153.6K bps forward & reverse channels
vii
Circuit Switched
Data IS-95A, IS-95B up to 14.4K bps
viii Data features Data circuit Asynchronous and non transparent up to 14.4 kbps auto baud rate
ix Operating Frequencies
§ TX:824-849 MHz,RX:869-894 MHz for 800 MHz CDMA
§ TX:1850-1910 MHz,RX:1930-1990 MHz for 1900 MHz CDMA
x RF Power
§ 600mW (EIRP Nom.) for 800 MHz CDMA
§ 400mW (EIRP Nom.) for 1900 MHz CDMA
xi Maximum TX Power: +23.0dBm Min.
xii Receiver Sensitivity >-104dBm
xiii Frequency Stability < ± 2.5 PPM
xiv SMS features
§ Supports Text and PDU mode
§ Point to Point &
§ Cell Broadcast
xv LED Indications Visual LED display for Power, Rx/Tx and Network
xvi SIM Connector Standard 3V SIM receptacle
xvii Antenna Flexible Antenna options
Page 133 of 193
10.0 Work Station
Number Description
Supplier Response
(Compliant/Non
Compliant)
10.1 Hardware Requirements
10.1.1 Architecture
i) Type Desktop PC
ii) Orientation
Vertical Tower Type or Ultra Small /Small Form Factor Desktop Type With
Mechanical Locking Arrangement for the CPU Cover/casing
iii) Bus type /
architecture PCI
10.1.2 Processor
i) CPU CHIP Dual Core Processor or higher
ii) Processor internal clock speed 3 GHz or higher
iii) Planer clock speed / FSB 1600 MHz or higher
iv) L2 Cache 4 MB or higher
10.1.3 Memory
i) Memory (RAM) 4 GB (2 nos. of 2 GB DIMMs)
ii) Memory (RAM) max expandability 4 GB or more
iii) RAM speed 1600 MHz or higher
iv) RAM slots total 4 or more (in Dual Channel; 2DIMMS /channel or more)
v) RAM type Non ECC DDR3
vi) Packaging DIMM
10.1.4 Board
Mother Board OEM Mother Board with OEM logo embossed on the Mother board
Revision Level
Management agent should show the
revision level
10.1.5 FDD Capacity NOT REQUIRED- DELETED
10.1.6 HDD
i) Size & Make 500 GB @ 7200RPM or better, Sync Transfer Rate 3 GBPS
ii) Hard disk controller Integrated SERIAL ATA II
iii) HDD Exp Option Option to add 2nd Serial ATA HDD-Required
10.1.7 Graphics subsystem
i) Type built-in on the chipset
ii) Video RAM Shared
iii) Resolution 1024x768 or better
iv) Graphics bus interface Integrated Graphics Media accelerator
SATA Implemented OEM make or equivalent ( any other make offered to be specified)
10.1.12 Ports and Interfaces
i) Parallel ports 1 (EPP/ECP bidirectional)
ii) Serial Port 1
iii) Serial ATA Interface 4
iv) Parallel ATA IDE
Interface with UDMA 33 1
v) USB Ver 2.0
At least 8 out of
which 2 on front
vi) Mouse 1
vii) Keyboard 1
vii) Graphic Media Accelerator Display 1
ix) Audio stereo input 1
x) Audio stereo
output 1
xi) Microphone 1
10.1.13 Expansion options
i) Slots
a) PCI Slots Conventional
2 Free Slots Minimum
b) PCI Express xl Slot
1 Free Slot Minimum
c) PCI Express xl6
Slot
1 Free Slot
Minimum
ii) 3.5 inch bays -accessible 1 or more
iii) 3.5 inch bays -
not accessible 1 or more
iv) 5.25 inch bays -accessible 2 or more
10.1.14 Manageability & Standards
i) WLP 2.0 Yes
ii) Plug & Play Yes
iii) Power management
features ACPI 1.0 Yes
iv) EPA Energy Star compliant Yes
10.1.15 Security features
i) Boot sequence
control Yes
ii) Diskette boot inhibit Yes
iii) Power on/ Boot password Yes
iv) Configuration Password Optional
iv) Setup password Yes
10.1.16 Audio
i)ADDA
Integrated 4
channel High Definition audio
ii) Sampling Rate
5 KHz to 44 KHz
or better
Page 135 of 193
iii) Synthesizer 4 channel or better
iv) Internal
Speakers
To be provided -
1.5 W Minimum
10.1.17 Network Connectivity
a)Type
Integrated Gigabit N/W
Connection Ethernet
b) Support type
Wake on LAN
support
c) Connector RJ45
10.1.18 OS
a) MS WINDOWS, b) Linux with x- window or
c) Mac OS
Latest version preloaded
a)Recovery CDs containing all required drivers and patches
b)OS CDs/DVDs with License declaration and
c) Documentation on media for Lic.
S/W Patches
Ensure that all software (OS & applications) supplied is licensed and
includes supply of all patches, updates, and bug-fixes during the warranty and extended support period if any.
10.1.19 Warranty
Minimum 3 Years Comprehensive
OEM on-site warranty (NEXT Business DAY
resolution) for all components (H/W and OS)
supplied including re-loading and re-
configuration of all s/w and device drivers, if
required.
10.1.20 CERTIFICATION
a) Windows Certified
Compliance Required ( In case supplied with Window OS)
b) LINUX ready Certified Compliance Required,
c) Mac OS certified
Compliance Required ( In case supplied
with Mac OS)
10.1.21
Manageability
Features * (All related Client Licenses as
applicable to be provided)
a) Tools for asset Tracking including
serial number tracking of system, manufacturer name
& model, board, CPU, memory, monitor, HDD with
details of NIC, OS Etc to be provided by OEM
Required,
Compliance to be demonstrated
b) OEM health monitoring/
diagnostic tools
Required, Compliance to be
demonstrated
c) Monitoring & Pre
failure alerts for the Hard Disk
Required, Compliance to
be demonstrated
10.1.22 Physical Security Hood Sensor
Required.
Compliance to be demonstrated
Page 136 of 193
10.1.23
Additional
Information to be provided by bidder BIOS Type To be indicated by bidder
10.1.24 Power Supply Power Supply Wattage
To be indicated by bidder (But not less than 150W)
10.2 Computer Table and Chair Requirement
10.2.1 Computer tables ( W.stations ) of approx size of 900 x 600 x 750mm ( Height ) with 19mm thick commercial board finished with approved laminate on top having one pull out keyboard tray on telescopic channel for smooth movement along with Seperator glass
8/10mm thick of size 2' x 1'-6" Duly supported on Glass – D, PIN - UP Board with soft board and approved fabric ( 24" x 36" )and Pencil drawer of size 300 x 225mm on telescopic channel with drawer lock. The running table should be individually supported
by 19 mm thick commercial board. All the exposed surface should be finished with approved laminate and internal surfaces with enamel paint / polish etc as reqd and as per the Site Engineer Instructions. The tables should be constructed in a manner that if
required it can be used seperately and individually or joined together without affecting the asthetics
10.2.2 Ergonomic height adjustable revolving Computer Chair with armrest. Five pronged Nylon
base with 60 mm double castors. Seat and back made of polyurethane foam on 12 mm hot pressed ply duly upholstered with low pilling and permeable fabric. Overall height of the chair – 95 to 105 cm.
11.0 Printers
Number Description
Supplier Response
(Compliant/Non Compliant)
11.1 Hardware Requirements
11.1.1
Laser Jet Printer
A) Type Monochrome Laser
B) First copy out time 10 sec
C) Speed 15 ppm or higher
D) Resolution 600x600 dpi
E) Make& Model To be indicated by bidder
F) Misc.
Built-in memory of 2 MB and maximum upgradeable memory up
to 2 MB and connectivity with USB port.
11.2 Multi Function Printer
11.2.1
Functions Print, Copy, Scan, fax
Print Resolution upto 600 x 600 x 2 dpi or higher, Image Resolution Enhancement technology
Print Speed Black (Letter): 26 ppm or higher; First Page Out: As fast as 10 sec
Scan Features
Instant on scanner, 35-page Automatic Document Feeder
(ADF), OCR software in box
Scan Type Flatbed, ADF
Scan Resolution
Enhanced: Upto 19,200 dpi or higher; Hardware: Upto 1200 x
1200 dpi or higher; Optical: Upto 1200 dpi or higher
Scan Speed 15 ppm or higher
Scan Size ADF (MAXIMUM) 8.5 x 14 in (216 x 356 mm)
Scan File Format JPEG, TIF, BMP, GIF, PDF, PNG
Page 137 of 193
Copy Resolution Black (Text): Upto 600 x 600 dpi or higher; Black (Graphics): Up to 1200 x 1200 dpi or higher
Copy Speed 15 cpm or higher
maximum number of copies minimum 99 copies
Copy reduce/enlarge settings 25 to 400%
Copier settings
Upto 99 multiple copies, Collation, Reduce/Enlarge from 25% to
Fax speed dialing, max numbers 120 numbers or higher
fax modem 33.6 kbps or higher
Fax memory 400 pages or higher
Fax features
Auto Fax Reduction Supported, Auto Redial, Fax Delayed Sending, Distinctive Ring Detection Supported, Broadcast Locations: 119 Locations
Fax Forwarding, Fax Phone Tam Interface Supported, Polling (Poll To Receive Only); Fax Telephone Mode Supported, Junk
Fax Barrier,Speed Dials, PC Interface Supported.
Duty Cycle(monthly) Up to 8,000 pages or higher
Connectivity Hi-Speed USB 2.0 port, 10/100 Ethernet network port
Network capabilities 10/100 Ethernet; Network Ready: Standard (built-in Ethernet)
Standard memory 128 MB or higher
Duplex print options Automatic
Media type and capacity ADF: Minimum 35 sheets; Minimum 250 sheets on main tray
Media sizes
Priority feed tray: minimum: 3 x 5 in; maximum: 8.5 x 14 in;Main
tray: minimum: 3 x 7.4 in; maximum: 8.5 x 14 in;Standard media sizes: A4, letter and Legal
Type of Media Bond Paper, Transparency Sheets, Envelopes, Labels cards
Printing Languages PCL 6, PCl 5, postscript
Vendor to provide drivers for supporting all the required OS and vandor will also provide Guaranteed output per laser, Catridge output with 5%, Coverage on letter size, paper in normal mode, cost of cartridges, power requirement, suggested UPS capacity (VA) &
type (online or offline), make and model.
Total
Page 138 of 193
12.0 UPS AND BATTERY SYSTEM
Number Description
Supplier
Response (Compliant/Non Compliant)
12.1 600 VA Line Interactive Intelligent UPS for workstation in the places other than at data center should meet the following requirements: Not
i Capacity 600 VA Line Interactive
ii Back up Time 10 Minutes on 450 VA Continuous Load; Overload capacity: 125% of required capacity for at least 1 Minute
iii Input Voltage 170 V to 270 V, 50 Hz + 5%
iv Output Voltage 198 to 250 (on line), 230 + 5% (On Battery) Automatic Voltage Regulation
Refer to B, Technical Specifications for details. Document is provided with the bid
document as Annexure B- Mandatory Technical Specifications which is to be
submitted with technical proposal for Part B of the project.
Please respond to each specification in following format.
Technical Specifications of Hardware
No Description/Requirements Supplier
Response Remarks
DETAILS SUPPLIER RESPONSE
BIDDER’S NAME
ADDRESS
CONTACT (S), TITLE (S), TELEPHONE (S), E-
MAIL ID (S)
NAME OF THE CHAIRMAN/ MD/ CEO/
PARTNERS
NATURE OF OWNERSHIP
DATE OF INCORPORATION OF
COMPANY/ENTITY
HEADQUARTER LOCATION
OTHER OFFICE LOCATIONS, FUNCTIONS AND
PERSONNEL STRENGTH
NUMBER OF EMPLOYEES BY FUNCTION
Implementation
Sales
Support
Quality Assurance
Administrative
Management
SIZE OF TEAM FOR THE PROPOSED
SOLUTION
LOCATION OF SUPPORT CENTERS FOR
PROPOSED SOLUTION
OTHER BUSINESSES
Page 160 of 193
The response in column “Supplier Response“ for the hardware requirements
should be as follows
Compliant
Non - Compliant
Please note that the rating as per the above scale is to be entered in the "Supplier
Response" column, and column titled “Remarks” is to be used for commenting on
aspects related to the functional specification. Bidders have to fill on two columns
("Supplier Response" & “Remarks”).
Please mention the detailed specification of hardware equipment and system
software (operating system, database etc.) including manufacturer, technical
details etc. The bidders should provide details of required system software like
operating system , database for solution and utilities in following format :-
Details of Hardware Offered
Product details No. of
installations
Make and Model Version and year of release
Kindly attach the data sheets for the offered products.
D.2.3 Approach and Methodology
The following table elaborates various requirements within A&M:
i. Understanding of Purchaser and its requirement with clear
mention of the deliverables
ii. Details of proposed methodology
iii. Project Team Structure
iv. Resource planning and estimation
v. Risk planning
vi. Detailed work plan with timelines
D.2.3.1 Understanding of Utility and its requirement
Bidder should depict complete understanding of the as-is system of the Utility
based on the information provided in the Bid Document. It should also require to
list down all the deliverables that has been planned as a part of the overall project
with timelines. Also provide details of prior interaction with Utility, if any.
Page 161 of 193
D.2.3.2 Details of proposed methodology
Please provide details of methodology followed by your organization in successfully
implementing similar projects. Also highlight the special steps that your
organization/ consortium intends to take in order to ensure that the change from
current system to proposed one will be smooth and effective.
D.2.3.3 Project Team Structure
In this section please provide detail of the team that would be deployed by your
organization to execute the project. Please provide details of the team structure in
the following format:
Proposed Project Team Structure
Name of
Staff
Position
Assigne
d
Interna
tional
or
Domes
tic
Fir
m
Employ
ment
status
with the
firm (Full
time/
Associat
e)
Educatio
n
(Degree,
Year,
Institutio
n)
Area of
Expertise
and number
of years of
relevant
experience
Task
Assigne
d
A.
PROFESSIO
NAL STAFF
B.
SUPPORT
STAFF
D.2.3.4 Resource planning and estimation
Bidder shall provide detailed staffing schedule of the professional and support
staff in the following format:
For Professional Staff the input should be indicated individually; for Support Staff it
should be indicated by category (e.g.: IT administrator, field survey staff etc.).
Months are counted from the start of the assignment. For each staff indicate
separately staff input for off-site and on-site work.
Page 162 of 193
Proposed Resource Planning and Estimation
N
O.
NAME OF STAFF POSITI
ON
STAFF INPUT
IN
WEEK
S
W
1
W
2
W
3
W
4
W
5
….
.
TOTA
L
A.
PROFESSIONAL
STAFF
B. SUPPORT
STAFF
D.2.3.5 Risk planning
Bidder shall assess underlying risks in implementation of the Project and detail out
the methodology to mitigate them. It may include development of a risk
assessment matrix indicating severity of the risk, chance of its occurrence and its
mitigation approach.
D.2.3.6 Detailed work plan with timelines
Please refer Appendix J for the format.
D.2.4 Project Experience
Bidder shall provide details of projects with application modules and other
requirements (as mentioned in Eligibility Criteria, Section 7.0.) which have been
successfully completed during the last 3 financial years.
Please do not supply the names of clients who are no longer using your
product/system.
Bidders need to submit the details as per the format in the table provided. Necessary
supporting documents should be attached with RFP:
Page 163 of 193
Details of Project Experience
SI.
No
Name
of
project
Brief Scope
necessarily
including role
played by
Bidder,
modules
implemented,
sector
classification
Owne
r of
Proje
ct
assig
nment
(Clien
t
name)
Cost
of
assig
nment
Date
of
Award
ed
comm
encem
ent
Date
of
compl
etion
Was
assign
ment
satisfa
ctorily
comple
ted
Was it
a
Power
Sector
Project
? (Y/N)
Provid
e Detail
Please provide separate client details for bidder & each consortium member
(Implementation partner, product Supplier, WAN/bandwidth/Internet service
provider etc.)
D.2.5 Team details (CVs)
Use the following format for key personnel who would be involved in the project.
Please include details of team members proposed to implement the project, install
or manage hardware, install and manage LAN/WAN and related equipments etc.,
please ensure that the CV has a maximum length of 3 pages.
In case of replacement of Supplier personal from the project team, Supplier is
required to submit to the nominated Utility personal the CV of the new person with
equivalent or better education qualification and relevant professional experience
who will be joining the team and get in duly approved. The new person can start
working in the project only after his/her CV has been approved by the Utility.
Format of Curriculum Vitae
1. PROPOSED POSITION:
2. NAME OF FIRM AND ITIA ROLE (SI/NSP/GSP/MDASP)
3. NAME OF STAFF:
4. DATE OF BIRTH: NATIONALITY
:
5. EDUCATION:
Page 164 of 193
YEAR DEGREE/EXAMINATION INSTITUTE/BOARD
6.
MEMBERSHIP OF
PROFESSIONAL
ASSOCIATIONS:
7. OTHER TRAINING:
8. COUNTRIES OF WORK
EXPERIENCE:
9. LANGUAGES:
LANGUAGE SPEAKING READING WRITING
10. EMPLOYMENT RECORD:
FROM TO EMPLOYER POSITIONS HELD
13.
11. DETAILED TASKS ASSIGNED:
12. WORK UNDERTAKEN THAT BEST ILLUSTRATES YOUR CAPABILITY TO
Certification:
I, the undersigned, certify that to the best of my knowledge and belief, this CV
correctly describes me, my qualifications, and my experience. I understand that any
wilful misstatement described herein may lead to my disqualification or dismissal, if
engaged.
Signature of authorised representative of the staff Date:
Full name of authorised representative:
Page 165 of 193
D.2.6 Firm Detail
Bidder shall provide details of CMM/CMMI and ISO certification along with the
details of net-worth and turnover for the past three audited financial years in the
following format:
Firm Detail
DETAILS FY011-12 FY12-13 FY13-14
NET-WORTH
TURN-OVER
LEVEL OF CMM/CMMI
CERTIFICATION (YES/NO)
ISO CERTIFICATION (YES/NO)
Audited financial reports and copy of the certificates supporting the above need to
be submitted as proof.
D.2.7 Facility Management Services Plan
The detail plan for FMS shall be given in accordance with the Section G5 of SRS
Document in accordance with the scope of work defined for Part B of the project.
D.2.8 Project Management Practices
Please provide high-level details of the project management practices that will be
followed to manage the project. The project management practices would include
(but not be limited to) details of:-
Bidder must provide details of how they envisage the contract being managed
including principles such as (but not limited to) joint planning and control
mechanisms; regular and active review meetings; Project management of
individual work streams and overall program management of the entire service;
Performance reporting
Bidder should outline their proposed governance structure and designate a
Service Manager to co-ordinate their activities and provide a focal point of
contact to whom Utility can refer on any matter concerning the service.
Reporting lines and decision-making powers within the bidder’s organization
must be explained
Reporting formats and templates that would be followed by the bidders
Outline the proposed escalation procedures in the event that issues arise.
Page 166 of 193
D.2.9 Quality Assurance
Quality of service - Suppliers must provide details of their proposed approach
to quality assurance to ensure the quality of services in accordance with clause
19 of Section G1 of SRS Document. This should include:
Responsibility of quality of service;
How the supplier will ensure quality service is provided;
How quality will be measured
Does your company (and consortium partner) have any quality certification /
Assessment? If so, please provide your responses for the following:
Details of Certification
DESCRIPTION BIDDER’S
RESPONSE
Certification / Assessment Name
Who issued the certification/assessment?
When was the certification/assessment obtained?
Does this certification/assessment process involve periodic reviews
and observations/ remarks after such review? If so, please provide
details and specify when your company is due for its next quality
review?
Please specify your company’s process for product development and
enhancements
D.2.10 Documentation
Please provide a list of all user documents that will be provided along with the
software package. This must include the following minimum documents:
System and administration manuals
Technical support handbook
User Manuals;
Error Messages and their Meanings;
Training Manuals;
Analysis & Design Manuals with the relevant data flow diagrams, entity
relationship diagrams, schemas etc.;
Additions/ changes to the documents after upgrades; and
Operations Manuals.
Page 167 of 193
D.2.11 Deviations Sheet
Only “non-material deviations” (which means only those deviations that do not
qualify as material deviations as defined in ITB clause 3.2, Section 5.5 of bid
document) will be considered by the purchaser. Please describe all the non-
material deviations w.r.t Terms and conditions described in the General conditions
of contract, Section 10.0. & Special conditions of contract, Section 11.0..
If bidder desires to take any non-material deviation from the terms & conditions of
the tender, it should be mentioned specifically in this deviation sheet. Unless such
deviations are mentioned in this deviation sheet, the same will not be taken into
consideration.
Format for Deviations
Tender Clarifications – Terms and Conditions
Sl.
No.
Tender Reference
(Section / Clause
number )
Details of Clauses
/ Section needing
deviation
Deviation proposed
Except aforesaid deviations, the entire order, if placed, shall be executed in
accordance with specifications and any other conditions, variations/deviations etc.
if found, elsewhere in this proposal should not be given any consideration while
finalizing the tender.
It is not mandatory to consider and accept the deviation mentioned on deviation
sheet proposed by the bidder.
Note:- Continuation sheet of like size & format may be used as per bidder’s
requirement wherever necessary.
Page 168 of 193
D.3 Price proposal
Bidders are requested to provide cost for each of the Project Area in the
subsequent formats. The Bidders should take a note of following points while filling
the Price proposal.
1 Bidder will be responsible for payment of Taxes (including local entry taxes),
duties, cess, charges etc, including taxes, duties, cess, charges etc, to be paid
by the Supplier pre- or post-delivery. Such taxes, duties, cess, charges etc, if
not explicitly mentioned in the following tables, but applicable under law, should
be included in the Quote under “Any other levies” column.
2 The Bidder will provide Tax rates assumed for the calculation at the time of
proposal for each item in notes to respective table.
3 Please refer to GCC Clause 13.2 and the SCC for Price adjustments due to
change in Tax rates (including local entry taxes), duties, cess, charges etc.
4 Purchaser reserves the right to deduct and pay to the government authorities
the taxes at applicable rates from the price payable to the supplier.
5 The unit prices mentioned for various components should be the same for all
Project Areas. In case of any discrepancy among unit prices of various Project
Areas, the lowest unit price of equipment mentioned for any Project Area shall
prevail.
6 Utility proposes upgrade of centralized Data Centre which is located in the
Project Area(s) defined in the Appendix F (List of offices for WAN connectivity).
D.3.1 Project Area with Data Centre & Customer Care Centre
Bidder should refer Section 9, Scope of Work to fill in following information:
Name of Project Area
Number Subdivision Offices under the Project
Area:-
Number of Other Offices under the Project Area:-
Bidder should define quantity and unit price which includes FOB, Freight &
Insurance, Excise Duty, CST/VAT and any other levies for each item listed below
in the following format.
Price Details are to be provided as per attached Price annexure. Bid Forms in
Price Annexure are to be used as mentioned below:-
Page 169 of 193
Bid Form
No.
Bid Form Description
I This form is to be used for providing the price proposal of application changes,
Data Migration and Document Scanning for selection of ITIA for Part A of the
project
II This form is to be used for providing the price proposal for Part B of the project
for Selection of ITIA
III This form is to be used for providing the FMS Charges for Part B of the project
IV This form is to be used for Total Cost of Project i.e. Part A and Part B including
FMS. Evaluation will be done on the total cost of project.
Page 170 of 193
Appendix E- Evaluation Methodology Alternate bids are not allowed
Only bids from empanelled (by the nodal agency) bidders shall be evaluated.
Bidders are required to submit technical and commercial bid in two parts i.e.
separately for Part A and Part B of the project but financial evaluation of the
bid shall be done after aggregating total price quoted for both Part A and
Part B of the project as well as for both the DISCOMS.
The evaluation team will thoroughly review the proposals submitted by
various bidders / consortiums for Part A and Part B of the project separately.
The broad evaluation will be based as following:-
Technical Proposal: 50% Weight
Price Proposal: 50% Weight
Pre-demo meetings will be conducted with all the bidders
Each of the bidder will be requested to demonstrate the product and
services.
The technical evaluation will commence post the demonstrations
Based on multiple parameters, the evaluation team will calculate the
technical evaluation score for each Supplier at the end of this phase
Utility, in observance of best practices, shall:
Maintain the bid evaluation process strictly confidential
Reject any attempts or pressures to distort the outcome of the evaluation,
including fraud and corruption
Strictly apply only and all of the evaluation and qualification criteria
specified in the Bid document
E.1 Single-Stage: Two-Envelope Bidding Procedure
In the Single-Stage: Two-Envelope bidding procedure, Bidders should submit two
sealed envelopes simultaneously, one containing the Technical Proposal and the
other the Price Proposal, enclosed together in an outer single envelope. Initially, only
the Technical Proposals are opened at the date and time advised in the Bidding
Document. The Price Proposals remain sealed and are held in custody by the
Purchaser. The Technical Proposals are evaluated by the Purchaser. No amendments
or changes to the Technical Proposals are permitted. The objective of the exercise is
to allow the Purchaser to evaluate the Technical Proposals without reference to price.
Bids of Bidders which do not conform to the mandatory requirements may be termed
as non-responsive and will not be evaluated further. Following the approval of the
Page 171 of 193
technical evaluation, and at an address, date and time advised by the Purchaser, the
Price Proposals are opened in public. The Price Proposals are evaluated and,
following approval of the price evaluation, the Contract is awarded to the Bidder whose
Bid has been determined to be have scored maximum in the composite formula as
defined below:
Total Score = 50% x Technical Proposal Score + 50% x Price Proposal Score
E.2 Evaluation and Comparison of bids
Initially the Supplier’s responses are reviewed for compliance with the Commercial
terms and conditions. The Suppliers who fail to comply with any of the commercial
terms and conditions mentioned may be termed as non-responsive and will not be
evaluated further. For those Suppliers who have qualified the commercial terms and
conditions Technical evaluation will be conducted followed by the Price-Bid
evaluation. The Suppliers who qualify the minimum technical requirement will be
considered for the price-bid evaluation. The price bids will remain sealed until the
technical evaluation is complete.
Technical Evaluation
The technical bid has a weightage of 50%. Technical evaluation will happen in two
stages.
Stage-1: Preliminary Evaluation
In stage-1, the following shall be confirmed: Deviations, Submission of Bank
Guarantee, Acceptance of terms and conditions, Acceptance to scope of work and
compliance to mandatory technical requirements (as mentioned in Appendix A). In
case the bid doesn’t meet all the mandatory requirements, the bid shall be termed as
non-responsive and will not be evaluated further
Stage-2
The distribution of weights shall be as follows:
Distribution of weights for bid evaluation
No Description Weight
A Technical Proposal 50
1 Approach & Methodology 8
2 Project Experience 24
3 Team Details (CV) 10
4 Firm Details 8
B Price Proposal 50
Total Marks 100
Details for each of the above parameters is as mentioned subsequently.
Page 172 of 193
A. Technical Proposal: Following is the methodology which shall be used to
evaluate the various parameters under the technical proposal.
A.1 Technical solution Evaluation
Score for Technical Evaluation
No Description Maximum
Score
i) Appendix B No Marks
Appendix B is the minimum requirement (and hence mandatory)
for the Utility and needs to be supplied as per the specifications.
In case the bidder decides to take any deviation, the same has to
be clearly mentioned under the deviations (D.2.11). Utility shall
decide if the same is acceptable or not. In case the same is not
acceptable, the bid shall be rejected and financial bid of the bidder
shall not be opened.
Bidder’s self-response to the solution (refer A.1 above) shall be as per the manner as
indicated in Appendix-B.
A.2 Approach & Methodology
This section shall be assigned 8 marks.
A.3 Project Experience: Shall be assigned 24 marks. The distribution of marks shall
be as follows:
Indian Power Utilities Experience in Billing (9 marks)
Indian Power Utilities Experience in Consumer Indexing (4 marks)
Project Specific Experience (4 marks)
IT Experience: Application Modules implemented (7 marks)
A.4 CV: Shall be assigned 10 marks. Following is the list of categorization of
requirement of personnel:
Meter Data Acquisition/ Energy Audit
Billing/Collection/New Connection/Disconnection
Web Self Service/ Security/ MIS
Page 173 of 193
A.5 Firm details: Shall be assigned 8 marks. The distribution of marks shall be as
follows:
i. Cumulative Turn-Over in the last 3 financial years (2.0 marks)
ii. Level of CMM/CMMI certification (2.0 marks) or ISO certification
(2.0 marks)
iii. No. of locations in India (2 marks)
For qualifying, Supplier should comply with all mandatory technical
requirements of Appendix B. In case the bidder has taken any deviation in
Appendix B, utility shall decide whether the same shall be acceptable or not.
Final score will be calculated by summation of weighted score in Section A.2,
A.3, A.4 and A.5. Bidders need to score a minimum score of “35” out of 50 in the
technical evaluation; else the bid shall be termed as non-responsive and will not
be evaluated further.
B. Price-Bid Evaluation
The Price-Bid evaluation is done only for those bids which are responsive and which
have a Final Technical score which is more than or equal to the minimum score for
technical proposal mentioned in sub-section A above.
Financial evaluation of the bid shall be done after aggregating total price quoted for
both Part A and Part B of the project as well as for both the DISCOMS. The net cost
quoted will be calculated as simple addition of all the cost mentioned in the price
proposal (Clause D.3, Appendix D). The price proposal score shall be calculated with
following formula:
Price proposal score = (LP/FP)*50, where
LP: Lowest Price offer; FP: Firm’s Price
C. Total Score
Total score shall be calculated as below:
Total Score = Technical Proposal Score + Price Proposal Score
The bid with the highest overall score will be awarded the project.
CVC Guidelines will be followed regarding the issue of price negotiations with L1
bidder.
Page 174 of 193
Price Details are to be provided as per attached Price annexure. Bid Forms in
Price Annexure are to be used as mentioned below :-
Bid Form
No.
Bid Form Description
I This form is to be used for providing the price proposal of application changes,
Data Migration and Document Scanning for selection of ITIA for Part A of the
project
II This form is to be used for providing the price proposal for Part B of the project
for Selection of ITIA
III This form is to be used for providing the FMS Charges for Part B of the project
IV This form is to be used for Total Cost of Project i.e. Part A and Part B including
FMS. Evaluation will be done on the total cost of project.
D. Checklists
Please submit a copy of this section with cover letter while submitting the proposal.
Documents for Part A and Part B of the project to be submitted separately.
D.1.1 Mandatory forms that needs to be submitted
Check List for Mandatory Forms
S.No. Item Furnished
1 Documents against eligibility criteria Yes/ No
2 Bid Security Yes/ No
3 One original copy duly signed- Technical Proposal Yes/ No
4 Four copies of Technical Proposal - Hard copies Yes/ No
5 Five copies of Technical Proposal - Soft copies Yes/ No
6 One original copy duly signed- Price proposal Yes/ No
7 Four copies of Financial Proposal - Hard copies Yes/ No
8 Five copies of Financial Proposal - Soft copies Yes/ No
9 Proof of turnover and networth for the last three audited
financial years of Bidder, consortium member (if any) and sub-
contractors
Yes/ No
10 CV of key personnel in suggested format Yes/ No
11 Proposed SLA template Yes/ No
12 Filled-in copy of Bidding forms (Section 8.0.) Yes/ No
13 Receipt of purchase of tender Yes/ No
Page 175 of 193
D.1.2 Compliance checklist
Check List for proper Documentation & Compliance
S.No. Item Furnished
1 Please confirm you agree to all clauses specified in the
Section 5.0., ITB
Yes/ No
2 Please confirm you have submitted all the mandatory forms
specified in Appendix D (Technical & Financial Proposal)
Yes/ No
3 Please confirm you have noted the bid submission deadline
specified in Section 6.0., Bid Data Sheet.
Yes/ No
4 Please confirm you have noted that the performance security
will be furnished within time period as specified in Section 5.0.,
ITB Sub Clause 5.5.
Yes/ No
5 Please confirm you have provided all document proof to
substantiate you qualifying the eligibility criteria as mentioned
in Section 7.0.
Yes/ No
6 Please confirm you have complied with the proposed solution
architecture specified in SRS Document
Yes/ No
7 Please confirm you have complied with all services specified in
the scope of services mentioned in Section 9.0.
Yes/ No
8 Please confirm that you comply with all clauses specified in the
General Conditions of Contract specified in Section 10.0.
Yes/ No
9 Please confirm that you comply with all clauses specified in the
Special Conditions of Contract specified in Section 11.0.
Yes/ No
10 Please confirm that all goods (software and hardware) and
services have been included in the price proposal and is
complete in all respects without any deviation/ missing items
Yes/ No
11 Please confirm that you have not submitted any alternate
proposal
Yes/ No
12 Please confirm that you have noted the SLA guidelines and
penalty clauses applicable as specified in Appendix C.
Yes/ No
13 Please confirm you have provided sufficient Bid security in
proper form as specified in clause 5.3, Section 5.0. ITB
Yes/ No
14 Please confirm you have responded to all mandatory technical
specification given in Appendix A
Yes/ No
15 Please confirm you have responded to all technical
specifications (applications) given in the Appendix B
Yes/ No
16 Please confirm that you have checked the final quote provided
in Appendix D (Price Proposal)
Yes/ No
Page 176 of 193
Appendix G- Bidder Queries
Format for Bidder Queries
Sr. no. RFP Clause No. RFP Page No. Description of Query Suggestion by Bidder
Appendix F – Geographical & Administrative Information Following is the list of project area which are included under the scope of work
Geographical & Administrative Information of all the Project Areas in DHBVN
General Description Detail
Name of town with HQ Hisar
Name of town with Data Centre Hisar
Name of Town with Disaster Recovery Centre Panchkula
Name of town with Customer Care Centre Gurgaon
*Data as on 31st March’2013. Current % growth per annum is 7.5% for consumers.
Sr. No Circle
Name Consumers
Sub-
Division
Offices
Other
Offices
Unit Nos. Nos. Nos.
1 Hisar 365904 13
2 Gurgaon 233902 10 5
3 Faridabad &
Palwal 144280 8
4 Bhiwani 249690 12 3
5 Sirsa 208450 9 3
6 Narnaul 148147 7 3
7 Rewari 168746 6 2
8 Jind 196652 9 1
Total 1715771 74 17
Page 177 of 193
Geographical & Administrative Information of all the Project Areas in UHBVN
General Description Detail
Name of town with HQ Panchkula
Name of town with Data Centre Hissar
Name of Town with Disaster Recovery Centre Panchkula
Name of town with Customer Care Centre Gurgaon
Sr. No Circle Name Consumers Sub-Division
Offices
Other Offices
Unit Nos. Nos. Nos.
1 Ambala 184932 7 3
2 Kurukshetra 146204 4 1
3 Karnal 163819 12 3
4 Panipat 262711 5 1
5 Kaithal 152603 8 2
6 Yamunanagar 160122 7 1
7 Jhajjar 235645 8 2
8 Sonepat 185480 9 3
9 Rohtak 249823 5 6
Total 1741339 65 22
*Data as on 31st March’2014. Current % growth per annum is 7.5% for consumers.
Page 178 of 193
Appendix H – List of Manuals/Business Processes to be converted into electronic form The following manuals/business processes need to be converted into electronic form
List of Manuals/ Business Process to be converted into Electronic Form in
DHBVN and UHBVN
Name of the
application/
business
process that
requires
data
migration
into the
proposed
application
Type (Stand
alone
application/
Integrated
application/
Manual
Business
Process)
If
Integr
ated,
what
are
the
other
applic
ations
integr
ated
with
this?
Databas
e
(Access,
SQL
etc.)
Data Format
(Access
Table, Paper
forms, Excel
Sheets etc.)
Data
mirrorin
g/
replicati
on
needed
?
Comments
MIS Manual
Business
Process
None None Paper YES Data Migration
required
Energy
Audit
Manual
Business
Process
None None Paper YES Data Migration
required
Billing Stand Alone
Application
(SAS)
None SQL
Server
Table,
Paper, Excel
YES Data Migration
required
Metering Stand Alone
Application
(SAS)
None SQL
Server
Table,
Paper, Excel
YES Data Migration
required
Collection Stand Alone
Application
(SAS)
None SQL
Server
Table,
Paper, Excel
YES Data Migration
required
New
Connection
Stand Alone
Application
(SAS)
None SQL
Server
Table,
Paper, Excel
YES Data Migration
required
Disconnecti
on
Stand Alone
Application
(SAS)
None SQL
Server
Table,
Paper, Excel
YES Data Migration
required
Enforcemen
t And
Manual None Paper, Excel YES Data Migration
required
Page 179 of 193
Name of the
application/
business
process that
requires
data
migration
into the
proposed
application
Type (Stand
alone
application/
Integrated
application/
Manual
Business
Process)
If
Integr
ated,
what
are
the
other
applic
ations
integr
ated
with
this?
Databas
e
(Access,
SQL
etc.)
Data Format
(Access
Table, Paper
forms, Excel
Sheets etc.)
Data
mirrorin
g/
replicati
on
needed
?
Comments
Respective
Assessment
Meter Data
Acquisition
Stand Alone
Application
None Table,
Paper, Excel
YES Integration
required
Asset
Managemen
t /
Maintenanc
e
Managemen
t
Stand Alone
Application
None Table,
Paper, Excel
YES Integration
required
Web Self
Service
Stand Alone
Application
None Oracle Table, Excel YES Data Migration
required
Page 180 of 193
Appendix I – Estimated Manpower Requirement
ITIA to deploy manpower for both Part A and Part B of the project, as per requirement
and as per Clause 7.0 of Section G.5 of SRS document keeping in view of project
completion time.
In addition to this following is the list of minimum number of resources required to be
deployed for Part B of the project upto the completion of FMS period by the bidder
under various roles:
Estimated Manpower Requirement (Part B)
Resource Type Nos.
Project Manager per utility 2
Team Leaders per Circle per Utility 18
Page 181 of 193
Appendix J– Expected Implementation Schedule
The bidders for Part A and Part B are expected to complete the implementation for DHBVN and UHBVN within 12 months and 8 months respectively for both the parts from the date of award of contract by the DHBVN and UHBVN. The effective date for Part-B will be reckoned two month prior to effective date of go-live of pilot towns.
Pilot is the first project area (consisting of the data center) that goes live in a utility. It
is expected to complete the enterprise-wide implementation for all the other identified
project areas with-in 12 (Twelve) calendar months as per below given schedule:
Project Part/ Month
Aw
ard
of
Co
ntr
act
to P
art
A
I II III IV
Aw
ard
of
co
ntr
act
to P
art
B
V VI
Go
Liv
e i
f P
ilo
t A
reas
VII VIII IX X XI XII
Go
Liv
e o
f all P
roje
ct
Are
as
Part A
Part B
ITIA for Part A is expected to complete all application changes and their deployment
within 4 months of award of contract. Contract for Part B will only be awarded when
ITIA for Part A will complete all application changes and their deployment. Complete
rollout in the remaining approved Operation Circles will be done in the next six months
at the rate of 3 Circle per Two months per DISCOM (DH & UH).
Facilities Management Services post successful completion of acceptance tests shall
be provided for a period of four years from the date of completion of acceptance test.
Bidder shall submit a detail Gantt chart as per along with the following implementation
schedule (Schedule for Part A and Part B of the project to be provided separately.
Bidders shall drill down these activities into sub/sub-sub activity in the chart. The chart
shall also detail out time and resource effort required to execute each activity. The
detailed bar charts for all the work activity shall however, be discussed and agreed to
by the successful Bidder with the owner before start of the execution of work.
Page 182 of 193
Expected Implementation Schedule for Part A
Activity/ Sub Activity Start
Date Weekly Plan
End
Date
W1 W2 W3 W4 W5 …
1 System Study and approval from owner
2
Mobilization at site with establishment of
site office, requisite resource deployment
etc.
3
Development of applications with
Acceptance / Performance test-data
migration
4 Data Migration
5 Scanning of Documents
Expected Implementation Schedule for Part B
Activity/ Sub Activity Start
Date Weekly Plan
End
Date
W1 W2 W3 W4 W5 …
1 System Study and approval from owner
2
Mobilization at site with establishment of
site office, requisite resource deployment
etc.
3
Creation of IT Infrastructure at Other Utility
offices viz. Division, Circle etc. (In a phased
manner for associated completed Circle)
4
Integration of entire IT infrastructures
created at Sub division offices, Electrical
sub stations and other utility offices with
Acceptance / Performance test
5 Facility Management Services (FMS)
Page 183 of 193
Appendix K- Abbreviations
The abbreviation mentioned in the document has been expanded hereunder:
Abbreviation Meaning
AMR Automated Meter Reading
B/W Black & White
BDS Bid Data Sheet
BG Bank Guarantee
CEO Chief Executive Officer
CIO Chief Information Officer
CST Central Sales Tax
CTI Computer Telephony Integration
CV Curriculum Vitae
DNS Domain Name Server
EMS Enterprise Management System
ExW Ex-Works
FMS Facility Management Services
FoB Freight on Board
GCC General Conditions of Contract
GIS Geographical Information System
GIS Geographical Information System
GoI Government of India
GPS Geographic Positioning System
GSP GIS Solution Provider
HQ Head Quarter
HT High Tension
ICB International Competitive Bidding
INR Indian Rupee
IP Internet Protocol
IPR Intellectual Property Rights
Page 184 of 193
Abbreviation Meaning
IST Indian Standard Time
IT Information Technology
ITB Instructions to Bidders
ITC IT Consultant
ITIA IT Implementation Agency
LAN Local Area Network
LDAP Lightweight Directory Access Protocol
LoI Letter of Intend
LP Lowest Prize
LT Low Tension
MBC Metering Billing Collection
MD Managing Director
MDASP Meter Data Acquisition Solution Provider
MoP Ministry of Power
MTR Motor Transport Receipt
NIT Notice Inviting Tender
NSP Network Solution Provider
OEM Original Equipment Manufacturer
OS Operating System
PC Personal Computer
PFC Power Finance Corporation
RAPDRP Restructured Accelerated Power Development Reforms Programme
RFP Request for Proposal
RFQ Request for Qualification
SAN Storage Area Network
SCC Special Conditions of Contract
SI System Integrator
SLA Service Level Agreement
Page 185 of 193
Abbreviation Meaning
SRS System Requirement Specifications
T/O Turnover
TS Technical Section
UPS Uninterrupted Power Supply
VAT Value Added Tax
VPN Virtual Private Network
WAN Wide Area Network
Page 186 of 193
Appendix: Price Bid Format
Bid Form I
BID FORM I
Category Sub Category Type/Discription Unit
Total Tax Amount (Rs.)
Total Cost (Rs.)
Application Implementation cost (Application develeopement, Integration, Testing and Training For DHBVN and UHBVN)
Application development
cost
Application Implementation cost (Application develeopement, Integration, Testing and Training) (For DHBVN and UHBVN)
Data Migration Cost(For DHBVN & UHBVN) Data
Migration Data Migration Cost(For DHBVN & UHBVN)
Scanning
Scan Charges Scan Charges for 3 years at each sub division (For DHBVN and UHBVN)
3457114 Pages to be scanned
No. of
pages
Total Cost
Page 187 of 193
Bid Form II
BID FORM II
Category Sub Category Type/Discription Unit Quanitity to be
increased/required
FOB (per
unit)
Freight & Insurance
(per unit)
Excise
Duty
Excise Duty (per
unit)
CST/
VAT
Sales &
other taxes (per
unit)
Any
other levies (per
unit)
Total Cost (per
unit)
Total
Cost
Rs. Rs. % Rs. % Rs. Rs. Rs. Rs.
Hardware for Sub Division Office Infrastructure
for Non RAPDRP areas
Switches Layer II Switch Nos. 139
Routers Router for MPLS/ VPN Network
Nos. 139
Cabling System Cables, Jacks etc. Nos. 139
Workstation / Equipment Cords
Nos. 139
IP Telephony IP Phone Nos. 278
UPS and Battery System UPS 5 kVA Nos. 139
Workstation PCs, Printers & Others
Workstation PC (Computer chair, table, UPS, MS Office
Latest version etc.) Nos. 973
Bar Code Readers Nos. 278
Laser Jet Printers Nos. 278
Multipurpose Network
Printer Nos. 139
Page 188 of 193
Hardware for Other Office Infrastructure for Non RAPDRP areas
Switches Layer II Switch Nos. 39
Routers Router for MPLS/ VPN Network
Nos. 39
Cabling System Cables, Jacks etc. Nos. 39
Workstation /
Equipment Cords Nos. 39
UPS and Battery System UPS 5 kVA Nos. 39
Workstation PCs, Printers & Others
Workstation PC (Computer chair,
table, UPS, MS Office Latest version etc.) Nos. 117
Multipurpose Network
Printer Nos. 39
Additional Components for Non RAPDRP areas (as per no. of PCs)
Anti Virus Nos 1090
Windows CAL Nos 1090
Exchange CAL Nos 1090
Additional Hardware for Sub Division Office Infrastructure for RAPDRP areas
Workstation PCs, Printers & Others
Workstation PC (Computer chair, table, UPS, MS Office
Latest version etc.)
Nos. 190
Additional Hardware for Sub Division Office Infrastructure
for RAPDRP areas
Workstation PCs, Printers & Others
Workstation PC (Computer chair, table, UPS, MS Office
Latest version etc.)
Nos. 100
Additional Components for RAPDRP areas (as per no. of PCs)
Anti Virus Nos 290
Windows CAL Nos 290
Exchange CAL Nos 290
Page 189 of 193
Metering Infrastructure
Metering Infrastructure
GPRS Modem Nos. 40240
Project Management Charges
PMC Project Management Cost
Total Infrastructure Cost 0
Bandwith Cost for DHBVN and UHBVN
Item Description Type Unit Quantity FOB (per unit)
CST/ VAT
Sales &
other taxes (per
unit)
Total
Cost (per unit)
Total Cost
Rs. % Rs. Rs. Rs.
Bandwidth Charges for Sub division offices
Network Connectivity - Primary Link - MPLS - VPN for 4 years
(2 MBPS)
For 4 Years per annum per location 556
Network Connectivity -
Secondary Link - for 4 years (512 KBPS)
For 4 Years per annum per location 556
Sub Total
Bandwidth Charges for other offices
Network Connectivity Charges for Primary link for3 years(512 kbps)
For 4 years per annum per location 156
Sub Total
Total Bandwidth Cost for Offices in DHBVN and UHBVN
Page 190 of 193
Bandwidth for GPRS Modems
Recurring Cost Type Unit Qunatity FOB (per unit)
No.
of
Years
CST/VAT
Taxes
&
Duties*
(per
unit)
Total
(per
unit)
Total
Nos. Rs. % Rs. Rs.
GPRS Sim Rental (Consumer Meters) Nos. 40240 4
GPRS Sim Rental -
Bandwidth Cost for DC and DR
Item List Total Bandwidth
requirement Charges per year (Including Tax)
No. of Years
Total Cost
Total bandwidth Requirement at DC (Primary) 16.00 4
Total bandwidth Requirement at DC (Secondary) 16.00 4
Total bandwidth Requirement at DR (Primary) 16.00 4
Total bandwidth Requirement at DR (Secondary) 16.00 4
