bid for supply, installation and commissioning of …...with new generation switches, switch fabrics...

Page no./clause no

Item RFP Specs/Clause

1 Section: 5 Technical

Specifications Page no. 38

Switch Performance: Switch should support minimum 80 Gbps per slot

switching bandwidth with minimum 255 Mpps forwarding rate for IPV4 & IpV6, There should not be any performance

degradation in case of any switching/routing engine failure.

They have requested to modify the specification as: Switch should support minimum 80 Gbps per slot switching bandwidth with minimum 255 Mpps

forwarding rate for IPV4 & IpV6, There should not be any drop in above mentioned performance in case of any switching/routing engine failure.

They have also provided justification for the same as follows:With new generation switches, switch fabrics provide active-active switching to ensure better

performance in normal working conditions.In case of failure, the available fabrics shall ensure the required performance is met. As active and redundant switch engine is old technology and is

specific to OEM, they have requested to modify the specifications accordingly

Accepted: The revised clause to be read as "Switch should support minimum 80 Gbps

per slot switching bandwidth with minimum 255 Mpps forwarding rate for IPV4 & IpV6,

There should not be any drop in above mentioned performance in case of any

switching/routing engine failure.



Layer 3 Features: The Switch should support 128K IPV4 & IPV6

Routes & 100K Multicast Routes for IPV4 & IPV6

They have requested to modify the specification as: The Switch should support 128K IPV4 & 64K IPV6 Routes including Multicast Routes for IPV4 &

IPV6

They have also provided justification for the same as follows:IPv6 packets are having 4x times the size of an IPv4 packet. This limits the same switch memory to

have less number of IPv6 routes. Also, Unicast and multicast routing table shall be shared in switches and hence request to specify the multicast routing table to be part of the combined

routing table.Also the 128 K IPv4 & IPv6 route & 100 K multicast entries are vendor specific and will limit our participation. Request to modify the IPv6 routes count and multicast routing

specification accordingly.

Accepted: The revised clause to be read as "The Switch should support 128K IPV4 &

64K IPV6 Routes including Multicast Routes for IPV4 & IPV6"



General / Physical Requirements: Switch should support minimum 48 Gbps per slot switching bandwidth with

minimum 110 Mpps forwarding rate. There should not be any performance degradation in case of any


They have requested to modify the specification as: Switch should support minimum 48 Gbps per slot switching bandwidth with minimum 110 Mpps forwarding rate. There should not be any drop in above mentioned performance in case of any

switching/routing engine failure

They have also provided justification for the same as follows:With new generation switches, switch fabrics provide active-active switching to ensure better

performance in normal working conditions.In case of failure, the available fabrics shall ensure the required performance is met. As active and redundant switch engine is old technology and specific

to OEM, they have requested to modify the specifications accordingly


per slot switching bandwidth with minimum 150 Mpps forwarding rate. There should

not be any drop in above mentioned performance in case of any

switching/routing engine failure"

4 Layer 3 Requirements: Shall have basic Routing-Static IP routing and

RIP v1/v2, hardware enabled advance IP routing protocols like OSPF, OSPFv3, BGPv4, RIPng and policy based routing,

Multicast routing features like PIM-SM, PIM-DM and PIM-SSM, multicast features like PIM RP accept filter, PIM

neighbor filter, multicast route limit, multicastmultipath and IGMP v1, v2, v3

They have requested to modify the specification as: Shall have basic Routing-Static IP routing and RIP v1/v2, hardware enabled advance IP routing

protocols like OSPF, OSPFv3, BGPv4, , RIPng and policy based routing, Multicast routing features like PIM-SM, PIM-DM and PIM-SSM, multicast features like PIM RP accept filter, PIM neighbor filter,

multicast route limit, multicast multipath or ECMP and IGMP v1, v2, v3

They have also provided justification for the same as follows:Multicast Multipath is vendor specific capability. Request to modify the same with industry standard

Equal-cost multipath feature

Accepted: The revised clause to be read as "Shall have basic Routing-Static IP routing and RIP v1/v2, hardware enabled advance

IP routing protocols like OSPF, OSPFv3, BGPv4, , RIPng and policy based routing,

Multicast routing features like PIM-SM, PIM-DM and PIM-SSM, multicast features like PIM RP accept filter, PIM neighbor filter,

multicast route limit, multicast multipath or ECMP and IGMP v1, v2, v3"

5 Layer 3 Requirements: Should support minimum 128 K IPv4 & IPv6 route & 32 K multicast entries.

Response to Queries

Bid for Supply, Installation and Commissioning of Active Network Switches and other Network Components for Gujarat Sachivalaya Campus Area Network (GSCAN) and to Integrate the same with existing GSWAN Infrastructure

Sr. No.

RFP Reference Query/Suggestion from Bidders Response to Bidders

They have requested to modify the specification as: Should support minimum 16 K IPv4 & 8K IPv6 route including multicast entries

They have also provided justification for the same as follows:IPv6 packets are having 4x times the size of an IPv4 packet. This limits the same switch memory to

have less number of IPv6 routes. Aggregation switch does not need the scalability as in core/distribution switch. Also, Unicast and multicast routing table shall be shared in switches and

hence request to specify the multicast routing table to be part of the combined routing table. accordingly. Also the 128 K IPv4 & IPv6 route & 32 K multicast entries are vendor specific and will

limit our participation. Request to modify the routes count and multicast routing specification

Accepted: The revised clause to be read as: Layer 3 Features: Switch should support

32K IPv4, 32K IPv6 unicast & 32K multicast routes for both IPV4 & IPv6.

RU Distribution

Switch

Building Aggregation

Switch

Section: 5 Technical


1 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 6 Section: 5 Technical


General / Physical Requirements: Switch should have minimum 24

10/100/1000 Base-T ports. withadditional 4 Nos. of SFP Based ports and additional 2

stacking ports with all accessories for stacking purpose

They have requested to modify the specification as: Switch should have minimum 24 10/100/1000 Base-T ports. with additional 2 Nos. of SFP Based ports and additional 2 dedicated stacking ports with all accessories for stacking purpose. Optional:

Uplink ports shall be upgradeable to 10G in future

They have also provided justification for the same as follows:As the requirement mentions, each switch needs Two (2) 1G Single Mode (SM) SFPs. Request to

modify the 1G SFP slots per switch to two Nos. Also optionally suggest to make these ports upgradeable to 10G in future, to provide investment protection

Accepted: The revised clause to be read as "Switch should have minimum 24 10/100/1000 Base-T ports. with

additional 2 Nos. of SFP Based ports and additional 2 dedicated stacking ports with

all accessories for stacking purpose"



Performance Requirements: Switch should have minimum 168 Gbps

switching bandwidth capacity (Gbps)per switch

They have requested to modify the specification as: Switch should have minimum 136 Gbps switching bandwidth capacity (Gbps) per switch

They have also provided justification for the same as follows:With the ports asked for on this switch (24 x Gig-T, 4 x Gig SFP, 2 x Stacking Ports) the total full-duplex performance requirement is 24 x 2 Gbps + 4 x 2 Gbps + 40 Gbps = 96 Gbps. To consider two 10G ports in future, this can be increased to 136 Gbps. The mentioned specification is not

matching on a fixed configuration switch with the given port count. Also 168 Gbps switching bandwidth is propritory to OEM. Request to modify the specification accordingly

Accepted: The revised clause to be read as : Performance

Requirements: Switch should have minimum 136 Gbps switching bandwidth capacity (Gbps) per

switch

8 Article 23: Evaluation

Methodology Page no.24

SI Capability Evaluation

5. Proposed OEM in latest Gartner Magic Quadrant for Enterprise

LAN Infrastructure for last three consecutive yearsLeader's Quadrant in last three consecutive years - 15

marksNot in Leader's Quadrant in last three consecutive years - 0

marks

They have requested to modify the specification as: Proposed OEM in latest Gartner Magic Quadrant for Enterprise LAN Infrastructure for last three

consecutive yearsLeader's/Visionary Quadrant in last three consecutive years - 15 Marks

Challangers Quadrant in last three consecutive years - 10 MarksAny Other Quadrant - 0 Marks

They have also provided justification for the same as follows:Request to kindly relax the clause and consider clause as this is restricting only two OEM's to have

advantage.

Accepted. The revised clause to be read as: "Proposed OEM in latest Gartner Magic

Quadrant for Enterprise LAN Infrastructure for all the three consecutive years

Leader's Quadrant in all three consecutive years - 15 marks

Visionary/Challenger/Niche Quadrant in all the three consecutive years - 8 marks

Not in Gartner's Quadrant in all the three consecutive years - 0 marks"

9 Switch Features: The Switch should support hot-swappable fan

trays & power supplies & should be supplied with 1:1 power supply. One power supply should be able to run the

switch in case any power supplyfails.

They have requested to modify the specification as: The Switch should support hot-swappable fan trays and power supplies & should be supplied with

N+N redundant power supply.

They have also provided justification for the same as follows:Different OEM's have different architecture and may require more than one power supply to run the Complete chassis. Hence request to kindly relax the clause. Also consider N+N redundancy instead

of 1+1 redundancy.

Accepted: The revised clause to be read as: The Switch should support hot-swappable

fan trays & power supplies & should be supplied with N:N power supply. One power supply should be able to run the switch in

case any power supply fails."

10 Switch Features: The Switch should support 1 Gbps , 10 Gbps & 40 Gbps interfaces

They have requested to modify the specification as: The Switch should support 1 Gbps & 10 Gbps interfaces

They have also provided justification for the same as follows:Asked support of 40Gbps interface is not aligned with the switch performance, per slot bandwidth

and network architecture. Hence request to kindly remove the same.

Accepted: The revised clause to be read as: Switch Features: The Switch should support 1 Gbps , 10 Gbps interfaces

11 Switch Performance: Switch should support minimum 80 Gbps per slot



They have requested to modify the specification as: Switch should support minimum 80 Gbps per slot switching bandwidth with minimum 833 Mpps forwarding rate for IPV4 & IpV6, There should not be any performance degradation in case of any


They have also provided justification for the same as follows:Chassis should have 7 slots for Line/payload slots where per slot bandwidth is 80Gbps. Total for 7

slots = 80*7=560Gbps = 833 Mpps for IPv4 and IPv6 (1Gbps=1.488Mpps). Request to kidly consider the same .

Not Accepted. As per Bid.

Floor Access Switch



RU Distribution

Switch

2 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 12 Layer 3 Features: Shall have basic Routing-Static IP routing, RIP

v1/v2, RIPng, policy based routing, hardware enabled advance IP routing protocols OSPF, OSPFv3, BGPv4, IGMP V1, V2, V3, MLD V1, V2, PIM-SM, PIM-DM , PIM-SSM etc

They have requested to modify the specification as: Shall have basic Routing-Static IP routing, RIP v1/v2, RIPng, policy based routing, hardware

enabled advance IP routing protocols OSPF, OSPFv3, IGMP V1, V2, V3, MLD V1, V2, PIM-SM, PIM-DM , PIM-SSM etc

They have also provided justification for the same as follows:Based on the network architecture, all the swiches would be placed in LAN environment, Thus BGP

is not required. Request to kindly remove the same.

BGP is normally required at the WAN Gateway Router/Switch.


13 Layer 3 Features: Should support MPLS VPN, MPLS mVPN (Multicast

VPN), MPLS Class of Service (CoS), VRF-Aware Services (Telnet, ICMP, Syslog), VPLS with minimum VRF support

upto 8K

They have requested to remove the clause

They have also provided justification for the same as follows:Request to kindly remove the clause and allow leading OEM's to participate.

MPLS not required here and is normally required at the WAN Gateway Router/Switch, while making own MPLS Cloud.

Clause stands deleted

14 Availability: Switch should have the capability to extend the control plane across two active switches making it

a virtual chassis, enabling interconnected switches to be managed as a single common fabric with one IP address with support for stateful switch over in case of a failure of

the Active Fabric/Supervisor.



The required feature is not supported by all OEM's on chassis based switches.


15 Availability: The Virtual switch should support the fabric/Controller in one chassis as the Active

fabric/Controller and the fabric/Controller in the other chassis as the Standby supervisor




Accepted: The revised clause to be read as:The switches should support

virtualization where the fabric/Controller in one chassis act as the Active

fabric/Controller and the fabric/Controller in the other chassis as the Standby

supervisor or equivalent technologies like Virtual Router Redundancy Protocol ( VRRP ) to increases the availability and reliability

of the network.

16 Interface Requirements: The switch should have minimum 12 10-Gigabit

Ethernet Ports spread across multiple line cards for card level redundancy, 40 no’s of 1G Fiber (SFP based) ports

spread across multiple line cards for card level redundancy.

They have Requested for ClarificationKindly clarify if we need to populate the SFP's for mentioned interfaces or SFP count mentioned in

Form F-1 on page 47 is final?

Also clarify is the populated interfaces need to be non-blocking wirepeed.

Accepted: The revised clause to be read as: Interface Requirements: The switch should have minimum 12 10-Gigabit Ethernet Ports spread across multiple line cards for card level redundancy, 40 no’s of 1G Fiber (SFP based) ports spread across multiple line cards for card level redundancy. All 1G& 10G ports should work on line rate.In RU distribution switches, 10G SFP's needs to be factored separately. SI/Bidder need to check 10G port availability of SDC Core Switch.

17 General / Physical Requirements: The Switch should support hot-swappable

power supplies & should be supplied with 1:1 power supply. One power supply should be able to run the switch

in case any power supply fails.

They have requested to modify the specification as: The Switch should support hot-swappable power supplies & should be supplied with N+N power

supply.


of 1+1 redundancy.

Accepted: The revised clause to be read as: The Switch should support hot-swappable

fan trays & power supplies & should be supplied with N:N power supply.






Switch

3 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 18 General / Physical Requirements: Switch should support minimum 48 Gbps per slot switching bandwidth with



They have requested to modify the specification as: Switch should support minimum 48 Gbps per slot switching bandwidth with minimum 357

Mpps forwarding rate for IPv4 and IPv6. There should not be any performance degradation in case of any switching/routing engine failure.


slots = 48*5=240Gbps = 357 Mpps for IPv4 and IPv6 (1Gbps=1.488Mpps). Request to kidly consider the same performance for IPv4 and IPv6 as IPv6 protocols are asked in the specification

and performance in Distribution switch is mentioned for both IPv4 and IPv6.


per slot switching bandwidth with minimum 150 Mpps forwarding rate. There should

not be any drop in above mentioned performance in case of any

switching/routing engine failure"

19 General / Physical Requirements: The proposed switch should support Net flow or J-flow or S-Flow.

They have requested to modify the specification as: The proposed switch should have Net flow or J-flow or S-Flow from day 1. If the same is supported

through additional modules then two modules to be provided for redundancy.

They have also provided justification for the same as follows:Request to kindly consider Flow monitoring from day 1 with proper redundancy to ensure that it is

highly available and can be used without any commercial impact.

As per RFP

20 Layer-2 Requirements: Shall have 32,000 MAC addresses They have requested to modify the specification as: Shall have 64,000 MAC addresses

They have also provided justification for the same as follows:Asked MAC addresses are very less and not aligned with the asked performance parameters. Hence

request to kindly consider 64,000 MAC addresses.

As per RFP


RIP v1/v2, hardware enabled advance IP routing protocols like OSPF, OSPFv3, BGPv4, , RIPng and policy based

routing, Multicast routing features like PIM-SM, PIM-DM and PIM-SSM, multicast features like PIM RP accept filter,

PIM neighbor filter, multicast route limit, multicastmultipath and IGMP v1, v2, v3


protocols like OSPF, OSPFv3 , RIPng and policy based routing, Multicast routing features like PIM-SM, PIM-DM and PIM-SSM, multicast features like PIM RP accept filter, PIM neighbor filter, multicast

route limit, multicast multipath and IGMP v1, v2, v3




Accepted: The revised clause to be read as "Shall have basic Routing-Static IP routing and RIP v1/v2, hardware enabled advance

IP routing protocols like OSPF, OSPFv3, BGPv4, , RIPng and policy based routing,

Multicast routing features like PIM-SM, PIM-DM and PIM-SSM, multicast features like PIM RP accept filter, PIM neighbor filter,

multicast route limit, multicast multipath or ECMP and IGMP v1, v2, v3"


They have Request for clarificationPlease clarify if 32 K multicast routes asked are for IPv4 and IPv6?

Revised Clause to be read as: Layer 3 Features: Switch should support

32K IPv4, 32K IPv6 unicast & 32K multicast routes for both IPV4 & IPv6.

23 Availability: Switch should have the capability to extend the control plane across two active switches making it a virtual chassis, enabling interconnected switches to be managed

as a single common fabric with one IP address with support for stateful switch over in case of a failure of the

Active Fabric/Supervisor.

They have Requested to remove the clause

Request to kindly remove the clause and allow leading OEM's to participate.



24 Security Requirements: Should be able to shut down Spanning Tree

Protocol Port Fast-enabled interfaces when BPDUs are received to avoid accidental topology oops

They have requested to modify the specification as:Should be able to shut down Spanning Tree Protocol Port interfaces when BPDUs are received to

avoid accidental topology loops

They have also provided justification for the same as follows:Fast-enabled interfaces are specific and not supported by all leading OEM's, hence request to kindly

relax the clause and consider standard interfaces.

Accepted. Revised clause to be read as:Security Requirements: Should be able to shut down Spanning Tree Protocol Port

enabled interfaces when BPDUs are received to avoid accidental topology oops





4 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 25 Interface Requirements: Fourteen (14) 10G ports spread across multiple

line cards for card level redundancy, Forty (40) no of 1G SFP based ports & Eight (8) 1GE ports spread across

multiple line cards.




Clause modified as: Interface Requirements: Four(4) 10G ports spread across multiple line cards for card level redundancy from day 1 and scalable to 12 for future use , Forty (40) no of 1G SFP based ports & Eight (8) 1GE ports

spread across multiple line cards. 10G & 1G ports should work on line rate.

10G SFP is not required to be supplied currently for Building Aggregation Switches.

Once fiber cabling modification is completed, GoG will procure 10G SFP's on

need basis.






They have requested to modify the specification as:Switch should have minimum 24 10/100/1000 Base-T ports. With additional 2 Nos. of SFP Based

ports and additional 2 stacking ports with all accessories for stacking purpose

They have also provided justification for the same as follows:Two SFP based ports are more than enough to suffice the requirement, even if we consider

redundant uplink from each switch. Hence request to kindly consider the same.

As above.Floor Access Switch

5 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 27 General / Physical Requirements: Switch should be 1 RU rack mountable in nature, stackable with 40Gbps of

throughput with minimum of 4 switches in a stack with single IP management.

They have requested to modify the specification as:Switch should be 1 RU rack mountable in nature, stackable with 40Gbps of throughput with

minimum of 9 switches in a stack with single IP management.

They have also provided justification for the same as follows:For better scalability and easy management, it is recommended to have minimum 9 Switches in a

tack with single IP management.

Accepted: The revised clause to be read as "Switch should be 1 RU rack mountable in

nature, stackable with 40Gbps of throughput with minimum of 8 switches in

a stack with single IP management."

28 General / Physical Requirements: The switch should have IPV4 & IPv6

support from day one

They have requested to modify the specification as:The switch should have IPV4 & IPv6 support from day one. Basic Static Routing, RIP, RIPnG from

day 1 and upgradable to OSPF, OSPFv3, PIM and MLD in future.

Request to kindly consider Basic routing like Static Routing, RIP, RIPnG from day 1 to ensure no commercial impact while using the same and upgradable to OSPF, OSPFv3, PIM and MLD in future

to ensure no hardware change in future while enabling the same.


29 Performance Requirements: Switch should have minimum 168 Gbps


They have requested to modify the specification as:Switch should have minimum 88 Gbps switching bandwidth capacity (Gbps) per switch

They have also provided justification for the same as follows:For standard 24 port switch with 2 x 10G uplink ports, the switching bandwidth should be 24x2 +

2x2x10 = 48+40=88 Gbps

As above.

30 Performance Requirements: Switch should have minimum 40 Mpps

throughput per switch

They have requested to modify the specification as:Switch should have minimum 65 Mpps throughput per switch

They have also provided justification for the same as follows:For standard 24 port switch with 2 x 10G uplink ports, the throughput should be 88/2*1.488 = 65

Mpps

Accepted. The Revised Clause to be read as: Switch should have minimum 65 Mpps


31 Layer-2 Requirements:Should support IEEE 802.1Q VLANencapsulation and up to 250 active

VLANs per switch

They have requested to modify the specification as:Should support IEEE 802.1Q VLAN encapsulation and up to 1000 active VLANs per switch

They have also provided justification for the same as follows:Asked VLAN's are very less. Hence considering future scalability, it is recommended to have

minimum 1000 VLAN's

Accepted. The Revised Clause to be read as: Layer-2

Requirements : Should support IEEE 802.1Q VLAN encapsulation and up to

1000 active VLANs per switch

32 Layer-2 Requirements: Switch should support link aggregation for minimum 8 GE ports and minimum 40 LAG

groups.

They have requested to modify the specification as:Switch should support link aggregation for minimum 8 GE ports and minimum 24 LAG groups.

They have also provided justification for the same as follows:In a 24 port switch even if we make each LAG of 2 ports, then we can have total 12 LAG's. Even if we consider 100% scalability, the total number of LAG's required would be 24. Hence request to

kindly consider the same.

Accepted. The Revised Clause to be read as: Layer-2

Requirements: Switch should support link aggregation for minimum 8 GE ports and

minimum 24 LAG groups.

33 Interface Requirements: Two (2) 1G Single Mode (SM) SFP should be supplied with the switch

They have Requested for Clarification

Kindly clarify if we need to populate the mentioned SFP's or SFP count mentioned in Form F-1 on page 47 is final?

This is as per Form F-1

34 Article 42: Installation

Requirements Page no.35

Clause no. 42.2

The necessary Civil & Electrical work has to be carried out by the Vendor.

The GOG will not reimburse any cost towards the same. The Vendor need

to take necessary permission if require from concern authority.

On Page 15 it is written that "GoG will provide all civil, electrical, passive infrastructure". Request for clarification.

No civil work is required. If required, electric work and Lan cabling is required

to be carried out.



6 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 35 QoS Features: Shall have strict priority queuing or high strict priority queue, QoS/Security ACLs

Shall have strict priority queuing or high strict priority queue, minimum 64K or above QoS/Security ACLs

Security ACL plays a vital role in the network.There would be a lot of traffic generated from building access & building aggregation layer switches towards SDC Core switches. RU distribution switches

act as aggregation point where on an average 12-16 Building aggregation switches would get terminate. Rather than forwarding all traffic towards SDC core, it is highly advisable to filter traffic at

RU distribution layer. They have requested to add the suggested clause.

As per RFP




The switch should have minimum 20 10-Gigabit Ethernet Ports spread across multiple line cards for card level redundancy, 40 no’s of 1G Fiber (SFP based) ports spread across multiple line cards for

card level redundancy.

There would be a lot many numbers of building access & aggregation switches intern get connect to RU distribution switches. To handle such huge amount of data, RU distribution switches must

have more number of 10G ports.

As above.

37 Addition Requested: Switch Security: Switch should support Data Confidentially & Integrity

Justification: MACsec, defined in 802.1AE, provides MAC-layer encryption over wired networks by using out-of-band methods for encryption keying. The MACsec Key Agreement (MKA) Protocol

provides the required session keys and manages the required encryption keys.

Accepted: The clause stands as "Security Requirements: Switch should support Data

Confidentially & Integrity"

38 Addition Requested: Switch Security: Switch should be EAL2 certified

Justification: The Evaluation Assurance Level of an IT product or system is a numerical grade assigned following the completion of a Common Criteria security evaluation.The increasing

assurance levels reflect added assurance requirements that must be met to achieve Common Criteria certification. The intent of the higher levels is to provide higher confidence that the system's

principal security features are reliably implemented.

Addition accepted: The clause stands as " Security Requirements: Switch should be

EAL2 or higher certified "

39 Addition Requested:Security Requirements: Switch should support Data Confidentially & Integrity



Accepted: The clause stands as "Security Requirements: Switch should support Data

Confidentially & Integrity"

40 Security Requirements: Switch Should support VLAN Based, Port Based

ACLs.

Switch Should support VLAN Based, Port Based & Time based ACLs

Justification: Time-based ACLs are useful when you want to restrict traffic based on the time of day. For example, you might employ time-based ACLs if you want to only allow web surfing during a

particular time of day or allow access to a particular server only during work hours.

As per RFP

41 Addition Requested: Security Requirements: Switch should be EAL2 certified






42 General / Physical Requirements: Switch should be 1 RU rack mountable

in nature, stackable with 40Gbps ofthroughput with minimum of 4 switches in a stack with

single IP management.

Switch should be 1 RU rack mountable in nature, stackable with 64 Gbps of full duplx throughput with minimum of 8 switches in a stack with single IP management.

Justification: There would be a need of stacking more than 4 switches into a single stack to connect more number of users/end machines.

As above.



RU Distribution

Switch




Switch



Floor Access Switch

7 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 43 General / Physical Requirements: Switch should support external

redundant power supply

Switch should support internal/ external redundant power supply

Justification: Internal redundant power supply is always better than external ones. With external redundant power supply external power source also needs to be provisioned that comes with an

additional cost.

Clause modified as: General / Physical Requirements: Switch should support

external/internal redundant power supply

44 Security Requirements: Switch Should support VLAN Based, Port Based

ACLs.




As per RFP

45 Addition Requested: Switch should be EAL2 certified






46 Section 2: Eligibility Criteria

Page no. 8

Clause no. 14

No Consortium will be allowed. The bidder must meet all the eligibility criteria by itself

Consortium with in Group Companies Should be allowed Not Accepted. As per Bid.







marks

They have requested to modify the specification as: Proposed OEM in latest Gartner Magic Quadrant for Enterprise LAN Infrastructure for last three

consecutive yearsLeader's/Visionary Quadrant in last three consecutive years - 15 Marks

Challangers Quadrant in last three consecutive years - 10 MarksAny Other Quadrant - 0 Marks

They have also provided justification for the same as follows:Request to kindly relax the clause and consider clause as this is restricting only two OEM's to have

advantage.

As above.



switch in case any power supplyfails.

They have requested to modify the specification as: The Switch should support hot-swappable fan trays and power supplies & should be supplied with

N+N redundant power supply.


of 1+1 redundancy.

As Above


They have requested to modify the specification as: The Switch should support 1 Gbps & 10 Gbps interfaces

They have also provided justification for the same as follows:Asked support of 40Gbps interface is not aligned with the switch performance, per slot bandwidth


As Above

50 Switch Performance: Switch should support minimum 80 Gbps per slot



They have requested to modify the specification as: Switch should support minimum 80 Gbps per slot switching bandwidth with minimum 833 Mpps forwarding rate for IPV4 & IpV6, There should not be any performance degradation in case of any



slots = 80*7=560Gbps = 833 Mpps for IPv4 and IPv6 (1Gbps=1.488Mpps). Request to kidly consider the same .

As Above



RU Distribution

Switch

8 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 51 Layer 3 Features: Shall have basic Routing-Static IP routing, RIP v1/v2, RIPng, policy based routing, hardware

enabled advance IP routing protocols OSPF, OSPFv3, BGPv4, IGMP V1, V2, V3, MLD V1, V2, PIM-SM, PIM-DM ,

PIM-SSM etc

They have requested to modify the specification as: Shall have basic Routing-Static IP routing, RIP v1/v2, RIPng, policy based routing, hardware enabled advance IP routing protocols OSPF, OSPFv3, IGMP V1, V2, V3, MLD V1, V2, PIM-SM, PIM-DM , PIM-

SSM etc




As Above


VPN), MPLS Class of Service (CoS), VRF-Aware Services (Telnet, ICMP, Syslog), VPLS with minimum VRF support

upto 8K




As Above







As Above

54 Availability: The Virtual switch should support the fabric/Controller in one chassis as the Active





As Above







As Above

56 General / Physical Requirements: The Switch should support hot-swappable



They have requested to modify the specification as: The Switch should support hot-swappable power supplies & should be supplied with N+N power

supply.


of 1+1 redundancy.

As Above

57 General / Physical Requirements: Switch should support minimum 48 Gbps per slot switching bandwidth with



They have requested to modify the specification as: Switch should support minimum 48 Gbps per slot switching bandwidth with minimum 357

Mpps forwarding rate for IPv4 and IPv6. There should not be any performance degradation in case of any switching/routing engine failure.


slots = 48*5=240Gbps = 357 Mpps for IPv4 and IPv6 (1Gbps=1.488Mpps). Request to kidly consider the same performance for IPv4 and IPv6 as IPv6 protocols are asked in the specification

and performance in Distribution switch is mentioned for both IPv4 and IPv6.

As Above






Switch

9 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 58 General / Physical Requirements: The proposed switch should support Net flow or J-flow or S-Flow.

They have requested to modify the specification as: The proposed switch should have Net flow or J-flow or S-Flow from day 1. If the same is supported

through additional modules then two modules to be provided for redundancy.

They have also provided justification for the same as follows:Request to kindly consider Flow monitoring from day 1 with proper redundancy to ensure that it is

highly available and can be used without any commercial impact.

As Above

59 Layer-2 Requirements: Shall have 32,000 MAC addresses They have requested to modify the specification as: Shall have 64,000 MAC addresses

They have also provided justification for the same as follows:Asked MAC addresses are very less and not aligned with the asked performance parameters. Hence

request to kindly consider 64,000 MAC addresses.

As Above



routing, Multicast routing features like PIM-SM, PIM-DM and PIM-SSM, multicast features like PIM RP accept filter,

PIM neighbor filter, multicast route limit, multicastmultipath and IGMP v1, v2, v3


protocols like OSPF, OSPFv3 , RIPng and policy based routing, Multicast routing features like PIM-SM, PIM-DM and PIM-SSM, multicast features like PIM RP accept filter, PIM neighbor filter, multicast

route limit, multicast multipath and IGMP v1, v2, v3




As Above


They have Request for clarificationPlease clarify if 32 K multicast routes asked are for IPv4 and IPv6?

As Above


as a single commonfabric with one IP address with support for stateful switch over in case of a failure of the Active Fabric/Supervisor.

They have Requested to remove the clause



As Above



They have requested to modify the specification as:Should be able to shut down Spanning Tree Protocol Port interfaces when BPDUs are received to

avoid accidental topology loops

They have also provided justification for the same as follows:Fast-enabled interfaces are specific and not supported by all leading OEM's, hence request to kindly

relax the clause and consider standard interfaces.

As Above

64 Interface Requirements: Fourteen (14) 10G ports spread across multiple






As Above






They have requested to modify the specification as:Switch should have minimum 24 10/100/1000 Base-T ports. With additional 2 Nos. of SFP Based

ports and additional 2 stacking ports with all accessories for stacking purpose

They have also provided justification for the same as follows:Two SFP based ports are more than enough to suffice the requirement, even if we consider

redundant uplink from each switch. Hence request to kindly consider the same.

As Above





Floor Access Switch

10 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 66 General / Physical Requirements: Switch should be 1 RU rack mountable in nature, stackable with 40Gbps of

throughput with minimum of 4 switches in a stack with single IP management.

They have requested to modify the specification as:Switch should be 1 RU rack mountable in nature, stackable with 40Gbps of throughput with

minimum of 9 switches in a stack with single IP management.

They have also provided justification for the same as follows:For better scalability and easy management, it is recommended to have minimum 9 Switches in a

tack with single IP management.

As Above

67 General / Physical Requirements: The switch should have IPV4 & IPv6

support from day one

They have requested to modify the specification as:The switch should have IPV4 & IPv6 support from day one. Basic Static Routing, RIP, RIPnG from

day 1 and upgradable to OSPF, OSPFv3, PIM and MLD in future.



As Above



They have requested to modify the specification as:Switch should have minimum 88 Gbps switching bandwidth capacity (Gbps) per switch

They have also provided justification for the same as follows:For standard 24 port switch with 2 x 10G uplink ports, the switching bandwidth should be 24x2 +

2x2x10 = 48+40=88 Gbps

As Above



They have requested to modify the specification as:Switch should have minimum 65 Mpps throughput per switch

They have also provided justification for the same as follows:For standard 24 port switch with 2 x 10G uplink ports, the throughput should be 88/2*1.488 = 65

Mpps

As Above



11 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 70 Layer-2 Requirements:Should support IEEE 802.1Q VLANencapsulation and up to 250 active

VLANs per switch

They have requested to modify the specification as:Should support IEEE 802.1Q VLAN encapsulation and up to 1000 active VLANs per switch

They have also provided justification for the same as follows:Asked VLAN's are very less. Hence considering future scalability, it is recommended to have

minimum 1000 VLAN's

As Above

71 Layer-2 Requirements: Switch should support link aggregation for minimum 8 GE ports and minimum 40 LAG

groups.

They have requested to modify the specification as:Switch should support link aggregation for minimum 8 GE ports and minimum 24 LAG groups.

They have also provided justification for the same as follows:In a 24 port switch even if we make each LAG of 2 ports, then we can have total 12 LAG's. Even if we consider 100% scalability, the total number of LAG's required would be 24. Hence request to


As Above

72 Interface Requirements: Two (2) 1G Single Mode (SM) SFP should be supplied with the switch

They have Requested for Clarification


As Above


Page no.7

Clause no. 4

The bidder should have demonstrableexpertise and experience in executing at least ONE project

inGovernment/PSU/Corporate for Network Integration /

Systems Integration in last five years each value more than 10 Crs in India.

The scope should include Supply,Installation and Commissioning of

Campus Area Network Infrastructureincluding Data Switches

They have requested to allow the Bidder to showcase multiple project experiences amounting to INR 10 Cr

Please see the revised bid.

74 Existing Network

Infrastructure

Figure 2: Low Level Existing Network Setup with Switch Model for New Sachivalaya

Please explain the current physical connectivity of the ground floor access switch to the 2nd floor Aggregation switch as the diagram shows that it is connected to 3 switches.

RFP is self explanatory

75 Existing Network

Challenges:

Current Fiber Optic Connectivity in the backbone is done through Fiber

transceivers due to non-availability of connecting Fiber Modules directly on the switches. GSCAN is facing connectivity issues because of the failure of these

transceivers. The failure of these transceivers could cause major downtime in the network. Upgradation of the

switches in the network with support for connecting fiber optics directly into the switches would eliminate the need for transceivers & hence reduce downtime in the network

& provide higher SLA to the network.

As per the current solution, SFPs(Small Form Factor Pluggable) will be required in switches for connecting the LC Patch cords. The ref. to the transceivers failure is a bit ambiguous , is GOG

referring to Fibre to Copper Converter as existing Transceivers?

RFP is self explanatory

76 Dimension Data recommends 10Gig connectivity even from Access switches to Bldg Aggregation switches. Would GOG consider this recommendation?

As per RFP

77 Each Building aggregation switch will be connected with 2 different RU switches in form a redundant RING

architecture over 10G, also every building aggregation switch will have redundant 10G links towards North & South bound Building aggregation switch to provide

additional layer of redundancy. Also keeping in mind future scalability sufficient a minimum no of 12 10G ports should be available from day one in the chassis so that whenever

required in future, GoG does not have to spend much except the transceiver costs.

Would multiple Bldg Agg switches will be connected to each other?

To provide additional level of redundany to individual building aggregation switches,

GoG may go for a ring architecture by connecting multiple building aggregation

switches in future on need basis.

Section 3: Scope of Work

Page no. 12

Proposed Network

12 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 78 Article 13: Bid Security/Earnest Money Deposit Page no. 21

Clause 13.1 The Bidder shall furnish, as part of the Bid, a Bid security for the amount of

Rs.36,00,000/- by demand draft, in favor of Gujarat Informatics Ltd.,

payable at Gandhinagar/Ahmedabad in India in a separate envelope. The

un-priced bid will be opened subject to the confirmation of valid Bidsecurity.

They have requested to also accept EMD in the form of Bank Guarantee, as it solves the same purpose and also proves the financial credibility of the Bidding organization


79 1. Past Project Experience of executing System Integration Projects

in last five years of the value INR 10 Cr from Government /PSU/Corporate customers in India.

They have requested to reduce the value of the previous project experiences to INR 5 Cr.

They have requested to accept projects that are under progress / under implementation also.


80 3. Turnover in each of last three financial years the last being

financial year ending March 2013

They have requested that, Bidders having Turnover of more than INR 500 Cr in 2 of the last 3 financial years should also be given full marks (15 Marks)


81 4. Profit in each of last three financial years the last being financial

year ending March 2013

They have suggested that Bidders having profits in each of the last 3 financial years should be given full marks (15 Marks). Irrespective of the Amount of Profit


82 Article 32: Taxes & Duties Page

no.28

Vendor is liable for all taxes and duties etc. They have requested that any change (increase / decrease) in Taxes and duties to be applicable mutually. i.e GIL to pay the Bidder any difference of amount due to increase in taxes, and similarly,

The Bidder shall discount the differential amount arising due to reduction in Taxes.


83 Article 38.2: Operational

Penalties Page no.32

They have requested to cap the operational penalties at the value of the PBG. Not Accepted. As per Bid.

84 Article 47: Limitation of

Vendor's Liability Page no.36

Notwithstanding anything contained in the Contract, Vendor’s liability

will be only for actual direct damages and shall be capped and limited to

double the charges or the amounts paid or due and payable to Vendor for

the Services that are the subject of the claim.

They have suggested to cap the Vendor's liability at the value of the contract. Not Accepted. As per Bid.

85 2. Building Aggregation switch - 64 nos. Why 64 bldg-agg switches are required? While floor access switches are only 19. Is this a typo? Please let us know to prepare the BOM.

As per RFP

86 6. Gigabit Ethernet SFPs* Please let us know why Gibabit SFPs(GLC-T) are required when the connectivity is over fiber and the Aggregation switch natively also supports Rj-45 ports.

To connect building access switches to building aggregation switches residing on

the same floor, Ethernet could be an option.

87 5. Multi mode SFPs* Please let us know if these Multimode SFPs will be used at the access switch side? We assume that the distance between the access switch and an Aggegation switch will not be more than 500 mts.

Depending upon distance between building access & building aggregation switches &

available fiber type, multimode SFP's would be required.

88 New proposed Clause - Site Not Ready In order to enable the Supplier to commence work and meet its obligations under the contract, we request GIL to provide physical possession of the site and access thereto, and making the site ready

complete in all respect.

We suggest that the Supplier should not in any manner be liable for any delay under the terms of this contract, if such delay is attributable to Purchaser’s failure to make the site ready within seven

(7) days of Supplier’s direction in this regard.

Depending upon circumstances, end-user department may cosider on merit.

Article 23: Evaluation



Section 6: Schedule of Requirement Page no.47

13 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 89 New Proposed clause - Deemed Acceptance We suggest that the goods / software which require acceptance test shall be deemed accepted for the purpose of release of payment and for start of the warranty period and otherwise, on occurrence

of any one of following events, whichever occurs earliest:

a. if GIL fails to conduct or does not provide a written notice of any rejection / confirmation of acceptance test, within seven (7) days from the date of Test readiness notification by the Supplier,

or

b. if GIL puts the material into operational / productive/ normal use prior to acceptance test.

c. if goods / software have been installed but, due to reasons beyond the control of the Supplier, it has not been possible during a period of three (3) days from the date of notice by the Supplier, to

proceed with the acceptance tests.


90 High Capacity 10 Gig Backbone link between RU Distribution & SDC core

switches.

Will this be Day one requirement or future requirement? Connectivity between RU distribution switches & SDC core switches are on 10G currently. We expect to have 10G connection between new RU switches & SDC core switches.

91 Each block will have fiber cabling extended till 5th floor where new building aggregation layer switch will be

provisioned.

Our understanding is that the fibre cabling is not in vendor's scope and will be provided by GoG. Please confirm this understanding.

yes

92 The bidder should pro-actively monitor the health of equipments installed.

Our understanding is that this would be done using GOG provided management tools. Please confirm this understanding. Does bidder have to provide any tool for management? In case bidder needs to factor for the Management tool, please let us know the number of deivces to be managed

using the tool.

No tool has to be separately quoted by the bidder. However, bidder should actively

monitor the health status of all to be deployed devices using existing tool.

93 Section 3: Scope of Work

Page no. 15

Site Preparation:

The Successful bidder is solely responsible for Site preparation as

per the local requirements. GoG will provide all civil, electrical, passive infrastructure.

Since GoG will be providing all civil, electrical , passive infrastructure, what is expected from bidder in terms of Site preparation?

Vendor has to carry our the required electric work & LAN cabling.

94 Article 13: Bid Security/Earnest Money Deposit Page no. 21

Clause no. 13.1

The Bidder shall furnish, as part of the Bid, a Bid security for the amount of




They have requested that Bid Security be allowed in form of Bank Guarantee instead of Demand Draft.


95 Article 25: Notification of

Award & Signing of Contract

Page no. 25

Clause 25.2 Within Six (6) working days of receipt of the Contract Form, the successful

Bidder shall sign and date the Contract and return it to the GOG/GIL. The contract Performance guarantee has to be

submitted within seven (07)working days of receipt of award. The Bank guarantee

(Performance) shallbe equal to 10% of the value of contract. The Bank

Guarantee shall be valid for duration of 180 days beyond the expiry of contract.

We are ok with the clause. However, we would like to submit that Article 13.4 on Page 22 of the RFP mentions that failure to sign the Agreement in time would lead to forfeiture of the Bid Security. In

view of this clause, we request that "Six (6) working days" be ammended to "Six (6) working days or as mutually agreed at time of Contracting".

We also request that GoG provide us with a copy of the Agreement so that we have more clarity on the Agreement to be signed as this would lead to less lead time to sign the Agreement.


96 Article 32: Taxes & Duties

Page no. 28

Vendor is liable for all taxes and duties etc. Noted. Our prices will be exclusive of Taxes and Duties and all Taxes and Duties would be extra as applicable. We would mention the Taxes and Duties applicable as required in the Form F-1 of the

RFP. Please confirm.


97 Article 36: Payment Terms

Page no. 29

On receipt of deliveries FOR destination And Successful Installation, commissioning, Integration & acceptance -

70%On Successful UAT and FAT - 30%

They have requested that GoG/ GIL consider the following payment terms:* 80% on delivery of the equipment

* Balance 20% on successful installation, commissioning, integration & acceptance.


Section 3: Scope of Work

Page no. 13

Proposed Network

14 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 98 Article 38: Penalty Clause Page no. 31

Clause 38.2 The Bidder shall be responsible for maintaining the desired performance and availability of the system/services.

Vender should ensure the prompt service support during Guarantee period. If complain is made before 4 pm of the

working day, the same should be attended & resolved within 24 hours.

We understand that Hardware replacement has to be NBD (Next Business Day) from the time the hardware is declared faulty/ dead. But any isses would need to be addressed and resolved within

24 hours. Please confirm.


99 Clause 42.1 The Vendor needs to pull necessary cables up to required place, using

approved PVC Piping/Channel/RF/CAT5 or CAT6 Cable.

Please elaborate on this point. This should be GOG scope

Vendor has to carry our the required electric work & LAN cabling.

100 Clause 42.2 The necessary Civil & Electrical work has to be carried out by the Vendor.



This statement is clashing with statement on which says that "GoG will provide all civil, electrical, passive infrastructure". Please clarify.

This should be GOG scope

No civil work is required. If required, electric work and Lan cabling is required

to be carried out.


Vendor's Liability Page no. 36





They have requested that this clause be ammended to the following:"Regardless of the nature of claim, Vendor’s aggregate liability for direct damages under this

Contract shall not exceed the charges paid by Customer to Vendor for the individual product or service (or, 12 months charges, in the event of recurring payments) that is the subject of claim. The above limit on liability shall not apply to damages for bodily injury (including death) and damage to

real property and tangible personal property for which Vendor is legally liable. Under no circumstances shall Vendor be liable for indirect, consequential, incidental or special damages, loss of/damage to, data, loss of profits and business and any third party claim, even if Vendor has been

advised of possibility of such damages."


102 Layer 3 Features: Shall have strict priority queuing or high strict priority queue, QoS/Security ACLs

Shall have strict priority queuing or high strict priority queue, minimum 64K or above QoS/Security ACLs

Justification: Security ACL plays a vital role in the network.There would be a lot of traffic generated from building access & building aggregation layer switches towards SDC Core switches. RU

distribution switches act as aggregation point where on an average 12-16 Building aggregation switches would get terminate. Rather than forwarding all traffic towards SDC core, it is highly

advisable to filter traffic at RU distribution layer. hence we request to add the suggested clause.


103 Interface Requirements: The switch should have minimum 12 10-Gigabit Ethernet Ports spread across multiple line cards for card level redundancy, 40 no’s of 1G Fiber (SFP

based) ports spread across multiple linecards for card level redundancy.



Justification: There would be a lot many numbers of building access & aggregation switches intern get connect to RU distribution switches. To handle such huge amount of data, RU distribution

switches must have more number of 10G ports.

As above.

104 Addition Requested: Security : Switch should support Data Confidentially & Integrity



As above.





As above.

Article 42: Installation

Rerquirements Page no. 35

Section 5: Technilcal


RU Distribution

Switch

15 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 106 Security Requirements Addition Requested: Switch should support Data Confidentially & Integrity



As above.

107 SecurityRequirements: Switch Should support VLAN Based, Port

Based ACLs.




As above.





As above.

109 General / PhysicalRequirements: Switch should be 1 RU rack mountable in

nature, stackable with 40Gbps of throughput with minimum of 4 switches in a stack with




As above.

110 General / PhysicalRequirements: Switch should support external

redundant power supply



additional cost.

As above.

111 Security Requirements: Switch Should support VLAN Based, Port Based ACLs.




As above.





As above.

113 1. RU Distribution switch2. Building Aggregation3. Floor Access switch

Please provide the location for installation of the switches within the campus In Sachivalaya Campus

114 4. Single Mode SFPs*5. Multi mode SFPs*

10G SFP and 1G SFP ? 10G SFP between RU distribution switch & SDC core switch using single mode.

Multimode SFP to be used between RU distribution switch & building aggregation

switch115 Section 6:

Schedule of Requirement Page no.53

Note 2: Successful Vendor will have to supply/provide goods with an Invoice

from a place located within State of Gujarat

This may not be possible as we don't have billing from Gujarat. Note 2: It is recommanded that Successful Vendor can supply/provide goods with an

Invoice from a place located within State of Gujarat.


Page no. 29



Please chaange to "On receipt of deliveries FOR destination - 70%; Installation/commissioning and acceptance - 20%; Within 30 days of successful acceptance test - 10%"


Section 6: Schedule of Requirement Page no.47




Switch



Floor Access Switch

16 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 117 Article 34: Warranty Terms

Page no. 29

The Vendor shall warrantthat every work executed under the contract shall be free

from all defectsand faults in material, workmanship etc. for a period of

Five years for fromthe date of Acceptance test.

Please consider warranty start date from the date of delivery of Goods at Gandhinagar. Because the installation of equipments and getting FAT depends on the site readiness.


118 Article 13: Bid Security/Earnest Money Deposit

Page no. 21

Clause 13.1 The Bidder shall furnish, as part of the Bid, a Bid security for the amount of




We request you to also accept EMD in the form of Bank Gaurantee (BG) from any scheduled/commercialized bank along with the draft BG format of same to be shared.


119 Article 32: Taxes & Duties Page

no. 28

Vendor is liable for all taxes and duties etc. We request you to consider and pay any future variation in statutory levies as per the then prevailing rates.

As above.

120 Article 35: Performance

Guarantee Page no. 29

Clause 35.2 The performance guarantee will be in the form of bank guarantee for the

amount equal of 10% of the value of the Order / LOI towards faithful

performance of the contract obligation, and performance of the

equipments during Warranty period. In case of poor and unsatisfactory

field services, GoG shall invoke the PBG.

Can we issue PBG valid for one year and then renew it on yearly basis till completion of five years or warranty period


121 Clause 35.3 The Performance Guarantee shall be valid for a period of 180 days

beyond Warrantee period and shall be denominated in Indian Rupees

and shall be in the form of an unconditional Bank Guarantee issued by all Public Sector Banks and private

banks namely IDBI Bank, UTIBank, HDFC Bank, ICICI Bank and scheduled bank namely

KalupurCommercial Co-Operative bank having branch in

Gandhinagar\Ahmedabad in the format provided by GoG to be

submitted Within 7 working days of receipt of award.

The Performance Guarantee shall be valid for a period of 180 days beyond Warrantee period and shall be denominated in Indian Rupees and shall be in the form of an unconditional Bank

Guarantee issued by all Public Sector Banks and private banks namely IDBI Bank, UTI Bank, HDFC Bank, ICICI Bank and scheduled bank namely Kalupur Commercial Co-Operative bank having branch in Gandhinagar\Ahmedabad in the format provided by GoG to be submitted Within 15

working days of receipt of award.


122 Article 40: Project

Implementation Page no. 32

Clause 40.3 The Vendor will implement the project strictly as per the plan approved

by GoG. The Vendor shall install and implement the proposed system at

such locations as may be selected by GoG within 120 days from the date of

the Agreement, which will be considered as a ‘Kick Off’ date.

The Vendor shall install and implement the proposed system at such locations as may be selected by GoG within 180 days from the date of the Agreement, which will be considered as a ‘Kick Off’

date.


123 Section 3: Scope of Work Page

no.15

Site Preparation: The Successful bidder is solely responsible for Site preparation as per the local

requirements. GoG will provide all civil, electrical, passive infrastructure.

124 Article 42: Installation

Requirement Page no. 35

The necessary Civil & Electrical work has to be carried out by the Vendor.



Both clause are contradictory, Please clarifyVendor has to carry our the required

electric work & LAN cabling.

17 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 125 Article 23: Evaluation

Methodology Page no. 24




marks

Proposed OEM in latest Gartner Magic Quadrant for Enterprise LAN Infrastructure for last three consecutive years Leader's/Visionary Quadrant in last three consecutive years - 15 Marks;

Challangers Quadrant in last three consecutive years - 10 Marks; Any Other Quadrant - 0 Marks

Request to kindly relax the clause and consider clause as this is restricting only two OEM's to have advantage.

As Above

126 3. Turnover in each of last three financial years the last being

financial year ending March 2013

Average Turnover in last three financial years the last being financial year ending March 2013 Please see the revised bid.

127 4. Profit in each of last three financial years the last being financial

year ending March 2013

Average Profit in last three financial years the last being financial year ending March 2013 Please see the revised bid.



switch in case any power supply fails.

The Switch should support hot-swappable fan trays and power supplies & should be supplied with N+N redundant power supply.

Different OEM's have different architecture and may require more than one power supply to run the Complete chassis. Hence request to kindly relax the clause. Also consider N+N redundancy instead

of 1+1 redundancy.

As above


The Switch should support 1 Gbps & 10 Gbps interfacesAsked support of 40Gbps interface is not aligned with the switch performance, per slot bandwidth


As above

130 Switch Performance: Switch should support minimum 80 Gbps per slot switching bandwidth with minimum 255

Mpps forwarding rate for IPV4 & IpV6, There should not be any performance degradation in case of any


Switch should support minimum 80 Gbps per slot switching bandwidth with minimum 833 Mpps forwarding rate for IPV4 & IpV6, There should not be any performance degradation in case of any


Chassis should have 7 slots for Line/payload slots where per slot bandwidth is 80Gbps. Total for 7 slots = 80*7=560Gbps = 833 Mpps for IPv4 and IPv6 (1Gbps=1.488Mpps). Request to kidly

consider the same .

As above

131 Layer 3 Features: Shall have basic Routing-Static IP routing, RIP

v1/v2, RIPng, policy based routing, hardware enabled advance IP routing protocols OSPF, OSPFv3, BGPv4, IGMP V1, V2, V3, MLD V1, V2, PIM-SM, PIM-DM , PIM-SSM etc

Shall have basic Routing-Static IP routing, RIP v1/v2, RIPng, policy based routing, hardwareenabled advance IP routing protocols OSPF, OSPFv3, IGMP V1, V2, V3, MLD V1, V2, PIM-SM, PIM-

DM , PIM-SSM etc

Based on the network architecture, all the swiches would be placed in LAN environment, Thus BGP is not required. Request to kindly remove the same.


As above

132 Layer 3 Features:: Should support MPLS VPN, MPLS mVPN (Multicast VPN), MPLS Class of Service (CoS), VRF-Aware Services (Telnet, ICMP, Syslog), VPLS with minimum VRF

support upto 8K

Request to remove the clause



As above


as a single common fabric with one IP address with support for

stateful switch over in case of a failure of the Active Fabric/Supervisor.




As above

134 Availability:The Virtual switch should support the fabric/Controller in one chassis as the Active

fabric/Controller and the fabric/Controller in theother chassis as the Standby supervisor




As above

Section 5: Technical

Specification Page no. 38

RU Distribution

Switch

18 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 135 Interface Requirements: The switch should have minimum 12 10-Gigabit


spread across multiple linecards for card level redundancy.

Request for Clarification

Kindly clarify if we need to populate the SFP's for mentioned interfaces or SFP count mentioned in Form F-1 on page 47 is final?


As above

136 Section 5: Technical


General / Physical Requirements: The Switch should support hot-swappable



The Switch should support hot-swappable power supplies & should be supplied with N+N power supply.

Different OEM's have different architecture and may require more than one power supply to run the Complete chassis. Hence request to kindly relax the clause. Also consider N+N redundancy instead

of 1+1 redundancy.

As above.

137 General / Physical Requirements: Switch should support minimum 48 Gbps per slot switching bandwidth with

minimum 110 Mpps forwarding rate. There should not be any

performance degradation in case of any switching/routing engine failure.

Switch should support minimum 48 Gbps per slot switching bandwidth with minimum 357Mpps forwarding rate for IPv4 and IPv6. There should not be any performance degradation in case

of any switching/routing engine failure.

Chassis should have 5 slots for Line/payload slots where per slot bandwidth is 48Gbps. Total for 5 slots = 48*5=240Gbps = 357 Mpps for IPv4 and IPv6 (1Gbps=1.488Mpps). Request to kidly

consider the same performance for IPv4 and IPv6 as IPv6 protocols are asked in the specification and performance in Distribution switch is mentioned for both IPv4 and IPv6.

As above

138 General / Physical Requirements: The proposed switch should support Net flow or J-flow or S-Flow.

The proposed switch should have Net flow or J-flow or S-Flow from day 1. If the same is supported through additional modules then two modules to be provided for redundancy.

Request to kindly consider Flow monitoring from day 1 with proper redundancy to ensure that it is highly available and can be used without any commercial impact.

As above

139 Layer-2 Requirements: Shall have 32,000 MAC addresses Shall have 64,000 MAC addresses

Asked MAC addresses are very less and not aligned with the asked performance parameters. Hence request to kindly consider 64,000 MAC addresses.

As above



routing, Multicast routingfeatures like PIM-SM, PIM-DM and PIM-SSM, multicast features like PIM RP accept filter, PIM neighbor filter,

multicast route limit, multicastmultipath and IGMP v1, v2, v3

Shall have basic Routing-Static IP routing and RIP v1/v2, hardware enabled advance IP routing protocols like OSPF, OSPFv3 , RIPng and policy based routing, Multicast routing features like PIM-

SM, PIM-DM and PIM-SSM, multicast features like PIM RP accept filter, PIM neighbor filter, multicast route limit, multicast multipath and IGMP v1, v2, v3

Based on the network architecture, all the swiches would be placed in LAN environment, Thus BGP is not required. Request to kindly remove the same.


As above


Request for clarification

Please clarify if 32 K multicast routes asked are for IPv4 and IPv6?

As above

142 Availability: Switch should have the capability to extend the control plane across two active switches making

it a virtual chassis, enabling interconnected switches to be managed as a single common

fabric with one IP address with support for stateful switch over in case of a failure of the Active Fabric/Supervisor.




As above



Should be able to shut down Spanning TreeProtocol Port interfaces when BPDUs are received to avoid accidental topology loops

Fast-enabled interfaces are specific and not supported by all leading OEM's, hence request to kindly relax the clause and consider standard interfaces.

As above


Switch



19 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 144 Interface Requirements: Fourteen (14) 10G ports spread across multiple




Kindly clarify if we need to populate the SFP's for mentioned interfaces or SFP count mentioned in Form F-1 on page 47 is final?


As above






Switch should have minimum 24 10/100/1000 Base-T ports. With additional 2 Nos. of SFP Based ports and additional 2 stacking ports with all accessories for stacking purpose

Two SFP based ports are more than enough to suffice the requirement, even if we consider redundant uplink from each switch. Hence request to kindly consider the same.

As above

146 General / Physical Requirements: Switch should be 1 RU rack mountable

in nature, stackable with 40Gbps ofthroughput with minimum of 4 switches in a stack with


Switch should be 1 RU rack mountable in nature, stackable with 40Gbps of throughput with minimum of 9 switches in a stack with single IP management.

For better scalability and easy management, it is recommended to have minimum 9 Switches in a tack with single IP management.

As above

147 General / Physical Requirements: The switch should have IPV4 & IPv6 support from day one

The switch should have IPV4 & IPv6 support from day one. Basic Static Routing, RIP, RIPnG from day 1 and upgradable to OSPF, OSPFv3, PIM and MLD in future



As above



Switch should have minimum 88 Gbps switching bandwidth capacity (Gbps) per switch

For standard 24 port switch with 2 x 10G uplink ports, the switching bandwidth should be 24x2 + 2x2x10 = 48+40=88 Gbps

As above



Switch should have minimum 65 Mpps throughput per switch

For standard 24 port switch with 2 x 10G uplink ports, the throughput should be 88/2*1.488 = 65 Mpps

As above

150 Layer-2 Requirements: Should support IEEE 802.1Q VLANencapsulation and up to 250 active

VLANs per switch

Should support IEEE 802.1Q VLAN encapsulation and up to 1000 active VLANs per switch

Asked VLAN's are very less. Hence considering future scalability, it is recommended to have minimum 1000 VLAN's

As above

151 Layer-2 Requirements: Switch should support link aggregation for minimum 8 GE ports and minimum

40 LAG groups.

Switch should support link aggregation for minimum 8 GE ports and minimum 24 LAG groups.

In a 24 port switch even if we make each LAG of 2 ports, then we can have total 12 LAG's. Even if we consider 100% scalability, the total number of LAG's required would be 24. Hence request to


As above

152 Interface Requirements: Two (2) 1G Single Mode (SM) SFPshould be supplied with the switch



As above


Methodology Page no. 24


LAN Infrastructure for last three consecutive yearsLeader's Quadrant in last three consecutive years

6. Bidder's Association with the Proposed OEM in terms ofExpertise and Certification on the Technology Offered

consistently in last 3 years

Should say Gartner or Equivalent study; Cisco and HP Only are in the Leaders Quadrant. Please remove this point as Gartner is never considered in govt tender. Gartner says it is based on

Gartner perception and NOT fact! Request you to include all vendors in Gartner quadrant. This will ensure that marginal/sub-standard vendors will not qualify

As above

Floor Access Switch



20 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 154 Switch Features: The switch should support new technologies like MPLS, EoMPLS/Metro Ethernet in

hardware with firmware upgrade only without upgrading the switching fabric and line modules.

Requesting you to relax the points saying that - Not a relevant feature on enterprise switches. Needed on the WAN side OR on the 6513

As per RFP

155 Switch Performance: The switch should have in-built capability for the

below functionalities using features likeSflow/Netflow etc :

• Voice-over-IP (VoIP), video network monitoring• SLA Monitoring

• Network performance monitoring &performance visibility

• IP Service network health readiness orassessment

• Edge- to –edge network availability monitoring• Troubleshooting of network operation

Requesting you to relax the points saying that - SLA Monitoring or equivalent; IP service network health readiness or assessment OR equivalent

Switch Performance: The switch should have in-built capability for the

below functionalities using features likeSflow/Netflow etc :

• Voice-over-IP (VoIP), video network monitoring

• SLA Monitoring• IP Service network health readiness or

assessment or equivallent• Edge- to –edge network availability

monitoring• Troubleshooting of network operation




Only one vendor in industry can provide you this feature / technology so requesting you to delete the said point

As above

157 Availability:The Virtual switch should support the fabric/Controller in one chassis as the Active


Only one vendor in industry can provide you this feature / technology so requesting you to delete the said point

As above


VPN), MPLS Class of Service (CoS), VRF-Aware Services (Telnet, ICMP, Syslog), VPLS withminimum VRF support upto 8K

Please relax this point saying that - Please reduce VRF from 8k to 400 as 8k VRF is specific to one vendor. Please delete Multicast VPN as this is a WAN technology and is not needed on the

distribution switch

As above




Please revise this point to read as 12 wirespeed distributed forwarding 10G ports and 40 nos of wirespeed distributed forwarding 1G fiber ports.

As above

160 Layer 3 Requirements: Have VRF-Lite for L3 virtualization with minimum

64 or above VRF-Lite instances from day one

Please reduce VRF-Lite support to 16 from 64 as 64 is specific to a vendor. 16 VRF-Lite is more than enough

As per RFP


as a single common fabric with one IP address with support for stateful switch over in case of a failure of the

Active Fabric/Supervisor.

Specific to one vendor. Please delete. As above

162 General / Physical Requirements: Switch should have minimum 24



Suits a particular vendor. Requesting you to relax this point saying - 24 10/100/1000 Base-T ports with additional 4 Nos. of 1G/10G ports for uplinks / stacking purpose with all accessories for

stacking. Interface requirement according to specification is only 2 1G ports.

As above



Requesting you to relax this point saying - Switch should support non-blocking architecture, wirespeed with 128Gbps switching bandwidth capacity per switch.

As above



RU Distribution

Switch




Switch



Floor Access Switch

21 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 164 Section 3: Scope of Work

Centralized monitoring and management Request you to give details about the existing monitoring tool deployed Details can be provided at the time of installation

165 The RU Distribution switches will be connected via multiple 10G uplinks to SDC Core Switches which is Cisco Catalyst

6513-E running in Virtualized Switching System architecture that is providing network stability, availability

& throughput.

Are these cisco 6500 switches already deployed? If yes , what are the line cards configured? Do these line cards support 10G modules?

6500 Switches as SDC core are already installed with 16 no of 10G ports. There

are 2 such switches at SDC.

166 Passive Work Kindly clarify passive cabling scope of work This has been clarifed in pre-bid167 Section 5:

Technical Specifications Page no. 40

RU Distribution

Switch

Interface Requirements: The switch should have minimum 12 10-Gigabit



Please clarify the exact number of ports /line cards required in distribution switch. As above




Switch

Interface Requirements: Fourteen (14) 10G ports spread across multiple



Please clarify the exact number of ports /line cards required in distribution switch. As above


Page no. 29



Request you to change Payment Terms as :70% on Delivery,30% on Installation commissioning and Integration


170 Submission Date Request you to give atleast 15 days for submission after prebid response Please see the revised bid.171 Section 2:

Eligibility Criteria Page no. 8

Bidder should not be under a declaration of ineligibility for corrupt and fraudulent practices issued by Government of

Gujarat or any of the PSU in the State of Gujarat.

We declare:"Wipro Limited is not under declaration of ineligibility for corrupt and fraudulent practices issued by

Government of Gujarat or any of the PSU in the State of Gujarat."

As per RFP

172 Section 3: Scope of Work Page

no.15

Site Preparation: - The Successful bidder is solely responsible for Site preparation as per the local

requirements. GoG will provide all civil, electrical, passive infrastructure.

Request GIL to consider: Customer hereby agrees to make the site ready as per the agreed specifications, within the agreed timelines. Customer agrees that Wipro shall not be in any manner be liable for any delay arising out of Customer's failure to make the site ready within the stipulated

period, including but not limited to levy of liquidated damages for any delay in performance of Services under the terms of this Agreement.

As above

173 Warranty Support: - The bidder shall be responsible for the 24x7 warranty support during the entire warranty period of

5 years.

We request GIL to kindly amend as below:The bidder shall be responsible for the 24x7 warranty support during the entire warranty period of 5

years with 4hours response time on-site. Bidder to also furnish the warranty/care-pack activation certificate along with the support-backlining confirmation letter from the respective OEM on their

company letterhead to be submitted by the Bidder along with the Bid.

Bidder has to furnish the warranty/care-pack activation certificate along with the

support-backlining confirmation letter from the respective OEM on their company

letterhead to be submitted by the Bidder along with the Bid.

174 Article 11: Bid Price Page no.

21

Clause no. 11.2

Offered price should be inclusive of all applicable taxes and levis

applicable such as Excise, Sales Tax, Service Tax, Octroi (If applicable),

Packing/ Forwarding, Insurance, FOR destination (any where in the

Gujarat state).

The Price offered here is exclusive of taxes, all taxes & duties will be charged extra as per the current rate of taxation in force. Any increase in taxes and duties will be passed on to customer.

Any change in statutory taxes, duties and levies shall be borne by the customer on sufficient documentary proof is submitted by the Wipro.


175 Clause no. 11.5

Unit rates should be quoted separately for each item. Quantities can be

increased or decreased by GoG and bidder has to supply deviated

quantities at the rates prescribed and approved by the GoG in the tender

document.

1. It should be restricted to +/-10% maximum of the quantity quoted as per RFP.2. Wipro agrees to provide the increased quantity at the same terms and conditions. However

additional prices shall be charged for the goods supplied over the contracted quantity.


22 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 176 Article 14: Period Validity of Bids

Page no. 22

Clause 14.1 Bids shall remain valid for 180 days after the date of Bid opening

prescribed by GOG / GIL. A Bid valid for a shorter period shall be

rejected as non-responsive.

Wipro will quote with a bid validity of 180 days from the date of submission of the BID. However, the prices mentioned in the tender will be capped at the USD-Re conversion rate prevailing on the due date of submission. Any currency movement amounting to over 1.5% in USD-Re conversion will be charged as actual and revised rates will be submitted at the time of award of contract in the event

of Wipro being awarded the contract.


177 Article 30: Assignment & Sub Contracts Page no. 22

The Vendor shall notify the GoG in writing of all subcontracts awarded

under the Contract Agreement. Such notification shall not relieve the

Vendor from any liability or obligation under the Agreement. The Vendor

shall fully indemnify GoG for any claims/damages whatsoever arising out of the Sub contracts.

Request GIL to amend as below: The Vendor shall notify GoG in writing of all subcontracts awarded under the Contract Agreement. Such notification shall not relieve the Vendor from any liability or obligation under the Agreement.



Page no. 29



We request GIL to kindly amend the same as below:80% payment upon delivery of material on-site

20% payment upon installation & Project Installation Report sign-off


179 Article 38: Penalty Cluase

Page no. 30

We request GIL to kindly cap the total penalty including LD if any, to 2% of order value and not beyond.


180 Article 40: Project

Implementation Page no. 32

Clause 40.4 Wipro will deliver the material within 12weeks from the date of the receipt & acceptance of firm Purchase order duly sealed and signed by the authorized signatory. Further, Wipro will complete the implementation within 8weeks from the date of material delivery on-site subject to all the site pre-requisites being met by the customer prior to material delivery and all the necessary approvals on

downtime etc. being provided by the customer in-line with the detailed implementation plan submitted by Wipro during the project kick-off meeting in the event of award of contract

please see the revised bid.

181 Clause 40.15

In the event of the delay in delivery of contracted services or services is

not satisfactory the GoG may procure goods from else ware as prescribed

in bid and Vendor shall be liable without limitations for the difference

between the cost of such substitution and the price set forth in the contract

for the goods involved i.e. at the risk and cost of the Vendor.

Vendor shall be required to bear only the Excess Cost for procurement of goods and/or services similar to those undelivered. The Term “Excess Cost” as referred herein shall mean cost at which alternative arrangements shall be providing the undelivered goods and/ or services of equivalent specification to the Purchaser under this project minus the cost on which the Vendor agreed to

provide the undelivered goods and/or services under this project. Provided further that the Vendor shall not be liable to Excess Cost in excess of (ten) 10 percent of the price of undelivered goods or

services for which such option is exercised by the Purchaser.


182 Article 48: Risk of Loss Page no. 36

Risk of loss of equipment shall pass on to GoG at the time it is handed

over to the designated carrier for shipment to GoG site. The Vendor shall however provide for transit insurance on

GoG’s behalf till delivery to GoG site.

The risk, title and ownership of the products shall be transferred to the customer upon dispatch of such products to the customer

Noted


Vendor's Liability Page no. 36





Notwithstanding anything contained in the Contract, Vendor’s maximum aggregate liability will be only for actual direct damages and shall be capped and limited to double the charges or the

amounts paid or due and payable to Vendor for the Services that are the subject of the claim. All indirect and consequential damages shall be excluded.


184 Form E: FORMAT FOR BID LETTER

FORM

In case of breach of any tender terms and conditions or deviation from bid specification other than already

specified as mentioned above, the decision of GIL Tender Committee

for disqualification will be accepted by us.

Request GIL to delete the clause. Not Accepted. As per Bid.

23 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 185 Site Not Ready: To be added in the RFP & ContractCustomer hereby agrees to make the site ready as per the agreed specifications, within the agreed timelines. Customer agrees that Wipro shall not be in any manner be liable for any delay arising

out of Customer's failure to make the site ready within the stipulated period, including but not limited to levy of liquidated damages for any delay in performance of Services under the terms of

this Agreement.

As above.

186 Savings Clause: To be added in the RFP & ContractBidder’s failure to perform its contractual responsibilities, to perform the services, or to meet agreed service levels shall be excused if and to the extent Bidder's performance is effected ,

delayed or causes non-performance due to Customer's omissions or actions whatsoever.

As per RFP

187 Deemed Acceptance: To be added in the RFP & ContractServices and/or deliverables shall be deemed to be fully and finally accepted by Customer in the event when Customer has not submitted its acceptance or rejection response in writing to Bidder

within 15 days from the date of installation/commissioning or when Customer uses the Deliverable in its business, whichever occurs earlier. Parties agree that Bidder shall have 15 days time to

correct in case of any rejection by Client.

As per RFP

188 Layer 3 Features: Shall have strict priority queuing or high strict priority queue, QoS/Security

ACLs

Request GIL to consider: Shall have strict priority queuing or high strict priority queue, minimum 64K or above QoS/Security ACLs

Justification: Security ACL plays a vital role in the network. There would be a lot of traffic generated from building access & building aggregation layer switches towards SDC Core switches. RU

distribution switches act as aggregation point where on an average 12-16 Building aggregation switches would get terminate. Rather than forwarding all traffic towards SDC core, it is highly advisable to filter traffic at RU distribution layer. Hence, we request GIL to add the suggested

clause.

As Above

189 Interface Requirements: The switch should have minimum 12 10-Gigabit Ethernet Ports spread across multiple line cards for card level redundancy, 40 no’s of 1G Fiber (SFP

based) ports spread across multiple linecards for card level redundancy.



Justification: There would be a lot many numbers of building access & aggregation switches intern get connect to RU distribution switches. To handle such huge amount of data, RU distribution

switches must have more number of 10G ports.

As Above

190 Switch: Security: Addition Requested: Switch should support Data Confidentially & Integrity



As Above





As Above


Specifications: Page no. 39

RU Distribution

Switch

24 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 192 Switch: Security Requirements: Addition Requested: Switch should support Data Confidentially & Integrity



As Above

193 SecurityRequirements: Switch Should support VLAN Based, Port

Based ACLs.




As Above





As Above

195 General / PhysicalRequirements: Switch should be 1 RU rack mountable in

nature, stackable with 40Gbps of throughput with minimum of 4 switches in a stack with single IP

management.



As Above

196 General / PhysicalRequirements: Switch should support external redundant

power supply



additional cost.

As Above

197 Security Requirements: Switch Should support VLAN Based, Port Based ACLs.




As Above





As Above

199 Section2 : Eligibility Criteria

Page no. 7

3. The bidder must have positive networth and should be profit making for each of the last three financial years as

on 31st March, 2013.

We request GIL to change the clause as Bidder should have a positive networth in each of the last three financial years, Bidder

Relevant pages from Bidders to provide Audited Annual Report or Certificate from Auditor

As per RFP


Page no. 29

On receipt of deliveries FOR destination And Successful Installation, commissioning, Integration & acceptance --

70 % On Successful UAT and FAT 30%

We request GIL to accept the changes in clause as below: PAYMENT TERMS: On delivery --70%

Successful Installation, commissioning, Integration & acceptance -- 20% On Successful UAT and FAT -- 10%





Switch



Floor Access Switch

25 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 201 If the Operator fails to complete the Supply / Installation / Commissioning / Acceptance within the time period (s) specified in the implementation plan, GoG may, without

prejudice to its other remedies under the Agreement, levy as Penalties, a sum equivalent to 1 % of the algebraic sum of the cost of the non-executed portion of the equipments

installed at that particular site / sites, for each week or part thereof of delay, until actual delivery of performance. The maximum penalty for delay shall not exceed 10% of

the algebraic sum of the cost for the equipments installed at that particular site. If the delay continues beyond 20

weeks, GoG may terminate the Agreement.


202 Operational Deficiencies shall apply: Site / Location Penalty after 24 to 48 hrs (delay of 24 hrs or part) --Rs.10,000/ Penalty beyond 48 hrs with a

cap of 10% of order value Rs.20,000/-Per each subsequent day (to a max cap of 5% of the order value)


203 New Proposed Clause : Change of taxWe request GIL to accept the changes in clause as below:

In case any national or state statute or any local law or regulation or by-law of any duly constituted authority is changed or comes into force which results in extra costs/tax in relation to the

provision of the Goods/Services, the consequential effect shall be to the account of the Owner and the same shall be borne by the Owner. We request NTPC to accept the same as the changes in the

taxes by government is not know to the bidder at the time of bidding.


204 New Proposed Clause: Termination: We request GIL to accept the changes in clause as below:

Without prejudice to any rights that have accrued to the Bidder, the Bidder may terminate this agreement by giving written notice to the NTPC , if NTPC commits a material breach of any term of the SPC and fails to remedy that breach within a period of 30 days after being notified in writing to

do so.


205 New Proposed Clause: Deemed Acceptance We request GIL to accept the changes in clause as below:

The hardware/software which requires acceptance test shall be deemed to be accepted, for the purpose of release of payment and for start of the warranty period and otherwise, on occurrence of

any one of following events, whichever occurs earliest:a. if Owner fails to conduct or attend the acceptance test or does not provide a written notice of any

rejection/confirmation of acceptance test, within one month from the date of test readiness notification by the Bidder, or

b. if Owner puts the hardware/ software into operational/ productive/ normal use prior to successful acceptance test.


206 New Proposed Clause: Site Not Ready: We request GIL to accept the changes in clause as below:

In order to enable the Bidder to commence work and meet its obligations under the contract, NTPC shall be responsible for providing access to the site, and also all other areas reasonably required for

the proper execution of the scope of work of the Bidder and making the site ready complete in all respect in accordance with the Bidder’s specifications for site readiness. NTPC agrees that the

Bidder shall not in any manner be liable for any delay in supply of deliverables under the terms of the SPC or GPC, if such delay is attributable to NTPC’s failure to make the site ready within seven

days of the Bidder’s direction in this regard.


Article 38: Penalty Clause

Page no. 29

Penalties for delay in implementation: If the Operator fails to complete the Supply / Installation / Commissioning / Acceptance within the

time period (s) specified in the implementation plan, GoG may, without prejudice to its other remedies under the Agreement, levy as Penalties, a sum equivalent to 0.5 % of the algebraic sum

of the cost of the non-executed portion of the equipments installed at that particular site / sites, for each week or part thereof of delay, until actual delivery of performance. The maximum penalty for

delay shall not exceed 5% of the algebraic sum of the cost for the equipments installed at that particular site. If the delay continues beyond 20 weeks, GoG may terminate the Agreement by giving

a notice period of 30 days Operational Deficiencies shall apply:Penalty after 24 to 48 hrs (delay of 24 hrs or part)

Rs.5,000/-per day Penalty beyond 48 hrs with a cap of 10% of order valueRs.10,000/-Per each subsequent day (to a

max cap of 5% of the order value)

26 of 27

Page no./clause no


Response to Queries


Sr. No.


RU 207 Section 2: Eligibility Criteria

Page no. 7

3. The bidder must have positive networthand should be profit making for each of thelast three financial years as on 31st March,

2013.

Since RFP is asking about positive net worth, we request you to remove profitability part and change clause to The bidder must have positive networth


Page no. 7

3. The bidder must have positive networthand should be profit making for each of thelast three financial years as on 31st March,

2013.

They have requested have to wave off the clause.Not Accepted. As per Bid.

27 of 27

bid for supply, installation and commissioning of …...with new generation switches, switch fabrics...

Documents