Page 1 of 62 Clarifications set nos.1-8 to the Bidding Documents for
”Network Improvement for Data Centers (in two lots) (RAMP/4)”
NATIONAL AGENCY FOR FISCAL ADMINISTRATION
REVENUE ADMINISTRATION MODERNIZATION PROJECT
„Network Improvement for Data Centers (in two lots) (RAMP/4)”
Clarifications to the Bidding Documents
Set nos. 1-8 updated on February 29th, 2016
Ref. No. / Question/Request for Clarification / Answer/Clarification / Ref. BD clause/provision / Clarification or Amendment1 / From our understanding, the two communication and protection systems described in Lot1 and Lot2 are an evolution of the current system operating in The National Agency for Fiscal Administration Datacenter (reference page 158, 189 etc.). To fully understand the requirements referring to integration with the existent system and to make sure the financial offer will cover all the required elements, please provide the full architecture together with the detailed description of the current running system. / The existing infrastructure is described in Section VI Technical Requirements, 1.1 for Lot 1:
- 2 (two) F5 Networks Big-IP 2200s (one device for each site), with GTM, feature-set, in the existing Application Services Front-End Layer – two device slots free for upgrades in each equipment chassis
- 2 (two) F5 Networks Viprion 2400 (one chassis for each site) with 2150 model blades (two per chassis) with the LTM/ASM/APM feature-set, in the existing Application Services DMZ Layer; / Page 158, 189
Section VI Technical Requirements, Par. 1.1, Par. 8.9.21 / Clarification
The detailed configuration for each site (Primary Data Center and Secondary Data Center) is:
Item
No. / Category / Manufacturer
Product Number / Equipment or Software Name / Qty
1. / Equipment
Hardware / F5-VPR-LTM-C2400-AC / F5 VIPRION 2400 Local Traffic Manager Chassis (4 x Slots, Dual AC Power Supplies) / 1
2. / Equipment
Hardware / F5-VPR-LTM-B2150 / F5 VIPRION 2150 Blade (32 GB Memory, SSD, 8 x SFP+ Ports with 2 x 10GBASE-SR Transceivers included) / 2
3. / Equipment
Hardware / F5-UPG-SFP-R / BIG-IP & VIPRION SFP 1000BASE-SX Transceiver (Short Range, Field Upgrade) / 6
4. / Equipment
Hardware / F5-ADD-VPR-ROUTING / F5 VIPRION Advanced Routing Module (RIP, OSPF, BGP, IS-IS, BFD) / 1
5. / Software License / F5-ADD-VPR-VCMP-2400 / F5 VIPRION Virtual Clustered Multiprocessing License for 2400 Chassis / 1
6. / Software License / F5-ADD-VPR-SEC-C2400 / F5 VIPRION Security Bundle for 2400 Chassis (Application Security Manager, Access Policy Manager, Max SSL, Max Compression, 500 Concurrent VPN Users) / 1
7. / Software License / F5-ADD-VPR-USER-25K / F5 VIPRION Add-on Licence for APM (25000 Concurrent VPN Users) / 1
8. / Software License / F5-ADD-VPR-USER-5K / F5 VIPRION Add-on License for APM (5000 Concurrent VPN Users) / 1
9. / Equipment
Hardware / F5-GTM-2000S / F5 BIG-IP 2200s DNS (8 GB Memory, Global Traffic Manager, DNSSEC, Advanced Routing) / 1
10. / Equipment
Hardware / F5-UPG-AC-400W / F5 BIG-IP Single AC Power Supply for 4200v/4000s/2X00s (400 W, Field Upgrade) / 1
11. / Software License / F5-EM-4000-R / F5 Enterprise Manager 4000 (License for 8 Devices) / 1
12. / Software License / F5-ADD-EM-AVR / F5 Enterprise Manager 4000 Centralized Analytics (License for 8 Devices) / 1
and Technical Requirement 8.9.21 for Lot 2:
- 2 (two) Cisco Nexus 7710 modular switch chassis, per site, configured with 10 (ten) equipment slots, out of which 7 (seven) equipment slots are free for future upgrades;
- 2 (two) Cisco Nexus 7700 Supervisor 2 Enhanced (N77-SUP2E), for each chassis;
- Cisco NX-OS Release 6.2 for Nexus 7700 Series (N77S2K9-62) and Nexus 7700 LAN Enterprise License (N77-LAN1K9) licenses;
- 3 (three) Cisco Nexus 7700 10 Slot Chassis 220Gbps/Slot Fabric Module (N77-C7710-FAB-2), for each chassis;
- 1 (one) Cisco Nexus 7700 F3-Series 48 Port 1/10GbE (N77-F348XP-23) line-card, for each chassis;
- 12 (twelve) Cisco 10GBASE-SR SFP+ Module (SFP-10G-SR=),for each N77-F348XP-23 line-card.
The detailed configuration for each site (Primary Data Center and Secondary Data Center) is:
Item
No. / Category / Manufacturer
Product Number / Equipment or Software Name / Qty
1 / Equipment
Hardware / N77-C7710 / Nexus7700 C7710 (10 Slot) Chassis / 1
2 / Equipment
Hardware / N77-F348XP-23 / 1/10 Gbps Ethernet Module / 1
3 / Equipment
Hardware / N77-SUP2E / Supervisor Module-2 / 1
4 / Equipment
Hardware / N77-SUP2E / Supervisor Module-2 / 1
5 / Equipment
Hardware / N77-C7710-FAB-2 / Fabric card module / 1
6 / Equipment
Hardware / N77-C7710-FAB-2 / Fabric card module / 1
7 / Equipment
Hardware / N77-C7710-FAB-2 / Fabric card module / 1
8 / Equipment
Hardware / N77-AC-3KW / Nexus7700 C7710 (10 Slot) Chassis Power Supply / 1
9 / Equipment
Hardware / N77-AC-3KW / Nexus7700 C7710 (10 Slot) Chassis Power Supply / 1
10 / Equipment
Hardware / N77-AC-3KW / Nexus7700 C7710 (10 Slot) Chassis Power Supply / 1
11 / Equipment
Hardware / N77-C7710-FAN / Nexus7700 C7710 (10 Slot) Chassis Fan Module / 1
12 / Equipment
Hardware / N77-C7710-FAN / Nexus7700 C7710 (10 Slot) Chassis Fan Module / 1
13 / Equipment
Hardware / N77-C7710-FAN / Nexus7700 C7710 (10 Slot) Chassis Fan Module / 1
14 / Equipment
Hardware / N77-C7710 / Nexus7700 C7710 (10 Slot) Chassis / 1
15 / Equipment
Hardware / N77-F348XP-23 / 1/10 Gbps Ethernet Module / 1
16 / Equipment
Hardware / N77-SUP2E / Supervisor Module-2 / 1
17 / Equipment
Hardware / N77-SUP2E / Supervisor Module-2 / 1
18 / Equipment
Hardware / N77-C7710-FAB-2 / Fabric card module / 1
19 / Equipment
Hardware / N77-C7710-FAB-2 / Fabric card module / 1
20 / Equipment
Hardware / N77-C7710-FAB-2 / Fabric card module / 1
21 / Equipment
Hardware / N77-AC-3KW / Nexus7700 C7710 (10 Slot) Chassis Power Supply / 1
22 / Equipment
Hardware / N77-AC-3KW / Nexus7700 C7710 (10 Slot) Chassis Power Supply / 1
23 / Equipment
Hardware / N77-AC-3KW / Nexus7700 C7710 (10 Slot) Chassis Power Supply / 1
24 / Equipment
Hardware / N77-C7710-FAN / Nexus7700 C7710 (10 Slot) Chassis Fan Module / 1
25 / Equipment
Hardware / N77-C7710-FAN / Nexus7700 C7710 (10 Slot) Chassis Fan Module / 1
26 / Equipment
Hardware / N77-C7710-FAN / Nexus7700 C7710 (10 Slot) Chassis Fan Module / 1
2 / “The Lot 1 Supplier must configure the equipment supplied to meet the requirements stated above and integrate it with the Purchaser’s existing systems/technologies, including but not limited to: The common support infrastructures (server room access control and monitoring, general power supply and room-level air conditioning etc.);”,
Please describe the existent datacenter space, power supply and air conditioning systems, as well as their current load (utilization level). Same question regarding the Lot 2. / The electrical requirements are described in the technical specifications (for example page 180 for Lot 2 under 5. General Technical Requirements). All data, electrical, and other interconnects to achieve a fully functioning Site-specific Subsystem must be provided by the Supplier.
The Primary Data Center and the Secondary Data Center have electrical power connections that provide the following standard voltage ranges and frequency ranges: 220v +/- 20v, 50Hz +/-2Hz, 2 (two) independent electrical power connection for each Industry Standard Server Rack Cabinet.
All active equipment hosted must include and, respectively accept, standard rack power plugs and interconnects:
– 6A IEC 60320 C13/C14;
– 16A IEC 60320 C19/C20;
– 32A IEC 60309 (or equivalent) connectors.
The active equipment is hosted in standard 19-inch Industry Standard Server Rack Cabinets server rack cabinet (which is typically 42 units in height, 19-inch wide, and 36 inches deep, as described in IEC 60297 Mechanical structures for electronic equipment - Dimensions of mechanical structures of the 482,6 mm (19 in) series), with grounding and “in row” cooling.
The data center environmental control in the Primary Data Center and the Secondary Data Center complies with the ASHRAE Standards, for the respective categories.
Safety: Unless otherwise specified, all equipment must operate at noise levels no greater than 75 decibels. All electronic equipment that emits electromagnetic energy must be certified as meeting US FCC class B or EN 55022 and EN 61000, or equivalent, emission standards.
Accommodation of the equipment on premise will be determined after the contract is awarded. / Page 180
Section VI Technical Requirements, 5. General Technical Requirements for Lot 2
3 / Regarding the Section VI – Technical Requirements, page 157,
“Lot 2 – Datacenter Fabric Subsystem (including “Access” and “Distribution” equivalent functional components, or Layers, and a Network Management and Orchestration Component) together with Datacenter Core Subsystem (including core datacenter-core network Communication Services Layer and network Communication Security Layer)”
and also Section VI – Technical Requirements, page 182:
“For each site, the “Access” and “Distribution” functional components and a Network Management and Orchestration component must be supplied and configured to implement a Datacenter Fabric Subsystem that must: Provide a dual-layer architecture, with the “Access Layer” component equivalent to the Leaf Layer in a two-stage (Charles) Clos type network and the “Distribution Layer” component respectively equivalent to the Spine Layer;”,
Please explain if the needed infrastructure is a 3 layer Access, Distribution, Core Network or a Leaf – Spine one. Also, please provide further information about the requested “[...] Leaf Layer in a two-stage (Charles) Clos type network” and its relevance in the current Bid. For the interested bidders to fully understand the Beneficiary’s request please provide a graphical architecture of the requested components and the way they are integrated, together with the existent components and the requested components from Lot 1. / The technical solution should be a non-blocking network. For this reason we require a leaf-spine clos type network or equivalent. The integration of the supplied solution is the responsibility of the Supplier. The existing infrastructure is described in the Technical Requirements 8.9.21. The picture provided is for illustration purposes only.
/ Page 157
Section VI Technical Requirements / Clarification
4 / Regarding the Technical Training Services
Does the Beneficiary provide a classroom for the training, together with the needed projector, computers and stationery needed or they are Supplier’s responsibility also? If the latter is true, where is the desired location for the training? There will be people travelling from outside of the city where the training will be held who will need hotel booking? Is this also the Supplier’s responsibility? / The Purchaser will provide a classroom for the training, together with the needed projector, computers and stationery needed. / Page 45
ITB 16.2 (c)
Page 167
Section VI Technical Requirements, Par. 2.4. Technical Training Services / Clarification
5 / Regarding the Section VI – Technical Requirements, page 181:
“The Datacenter Fabric Subsystem and Datacenter Core Subsystem, comprising integrated Subsystems for the 2 (two) datacenter sites, must be supplied and configured to: [...] 6.3 Implement features for complex communication architectures, including multicast traffic management and Multiprotocol Label Switching (MPLS); [...] 6.6 Provide native support for OSI Layer 2 datacenter interconnection protocols that: Do not rely on Multi Protocol Label Switching (MPLS) / Virtual Private LAN Service (VPLS);”,
Please confirm if the MPLS protocol is required or not. / Technical Requirement 6.3 states that MPLS must be included, while TR 6.6 states that there should also be support for Layer 2 datacenter interconnection protocols that do not rely on MPLS.
The MLPS protocol is required.
Support for Layer 2 datacenter interconnection protocols that do not rely on MLSP is also required. / Page 181
Section VI Technical Requirements,
Chapter 6. Architecture – Datacenter Fabric Subsystem and Datacenter Core Subsystem,
Par. 6.3 and Par. 6.6 Technical Requirements / Clarification
6 / Please provide network topology diagram? / The current network topology is a dual-layer architecture, with the “Access Layer” component equivalent to the Leaf Layer in a two-stage (Charles) Clos type network and the
“Distribution Layer” component respectively equivalent to the Spine Layer.
See the answer to question 3. / N/A / Clarification
7 / WAN connectivity and design? / See answer to question no. 3 and the Annex I in the Amendment. / N/A / Clarification
8 / For DCI interconnect – do you expect to have more than 3 sites?
/ No. The Datacenter Fabric Subsystem and Datacenter Core Subsystem must be delivered comprising integrated Subsystems for the 2 (two) datacenter sites.
In the future - the number of sites to be interconnected is 3 (three): Primary Data Center, Secondary Data Center and Data Warehouse Data Center. / Page 187
Section VI. Technical Requirements / Clarification
9 / What is strategy around automation / virtualization – OpenStack or any other SDN type of tech on horizon? / The current strategy around automation / virtualization is to integrate with major virtualization solutions (e.g., VMware, Microsoft HyperV, Oracle VM, OpenStack) and to integrate with network overlay technologies such as Network Virtualization, using at least Generic Routing Encapsulation (NVGRE) and Virtual Extensible LAN (VXLAN). / Page 187
Section VI. Technical Requirements / Clarification
10 / FCoE mandatory part of design or other options acceptable?
/ Yes – Fiber Channel over Ethernet is mandatory, because this is the protocol in use today at NAFA. IP/Ethernet and Fiber Channel over Ethernet (FCoE) are used in a consolidated switch fabric between existing servers and storage.
Replacement of this protocol is not acceptable. / Page 187
Section VI. Technical Requirements / Clarification
11 / Intergrade with major virtualization solutions (VMware, Hyper-V, OpenStack) – what level of integration is required? / Integration with the major virtualization solution (e.g. VMWare, Hyper-V, OpenStack) is needed to implement server to storage connections for all the major operating systems used by NAFA (Linux – all major distributions, Microsoft Windows, IBM AIX – different releases, all in use today). / Page 187
Section VI. Technical Requirements / Clarification
12 / For Datacenter Core Subsystem must allow 80 Tbps for each site – what is the relation between DC Core and DC Fabric? Are they connected?
/ Yes. The DC Core and the DC Fabric are interconnected. / Page 187
Section VI. Technical Requirements / Clarification
13 / Implement features for complex communication architectures, including multicast traffic management and Multiprotocol Label Switching (MPLS – more details please? Use case?
/ See the answer to question no. 5 above. / Page 187
Section VI. Technical Requirements / Clarification
14 / Is FCoE an absolute condition to be met ? Can it be iSCSI as SAN connectivity?
/ Yes. Fiber Channel over Ethernet (FCoE) is an absolute condition to be met, because of compatibility with the existing configuration, which is using IP Ethernet and Fiber Channel over Ethernet (FCoE). / Page 187
Section VI. Technical Clarification Requirements / Clarification
15 / Is NETCONF protocol mandatory management protocol?
/ YES – NETCONF is the mandatory network management protocol. NETCONF is the network configuration protocol in place, used by NAFA. / Page 187
Section VI. Technical Requirements / Clarification
16 / Can be accepted alternative encapsulations besides VxLAN, ie SPB? / The only encapsulations requested is VxLAN, because this is the encapsulation used today in the NAFA Data Centers.
No other encapsulation - like Shortest Path Bridging (SPB) – is accepted as an alternative. / Page 187
Section VI. Technical Requirements / Clarification
17 / Referring to the following request from Section II – Bid Data Sheet (BDS):
,,ITB 6.1. (c) If the Bidder proposes to use Subcontractors for the provision of certain key services, written agreements by the proposed firms to provide these services in case of contract(s) resulting from this bidding are required for the following types/categories of services: all installation, configuration, testing, warranty repair, and technical support services.”
We understand that the implementation team may contain experts that are subcontractor’s employees. In this case, each expert will present declaration of availability.
Please, confirm our understanding. / The subcontractor agreements shall be made with the subcontracted party. If the subcontracted party is a firm, then the firm must provide the agreement. If the subcontracted party is an individual, then the individual must provide the agreement. / Bid Data for ITB 6.1(c) / Clarification
18 / Referring to the following specifications found in Form 3.3.6. Personnel Capabilities:
,,For specific positions essential to contract management and implementation (and/or those specified in the Bidding Documents, if any), Bidders should provide the names of at least two candidates qualified to meet the specified requirements stated for each position. The data on their experience should be supplied on separate sheets using one Form 3.5.6a for each candidate.
Bidders may propose alternative management and implementation arrangements requiring different key personnel, whose experience records should be provided.”
Considering that the Bidding Documentation doesn’t require at least two candidates qualified to meet the specified requirements stated for each position, we understand that the implementation teams will maintain the following minimum composition specified in the Technical Requirements (containing a prime candidate for each position):
,,The Lot 1 Supplier must establish and maintain an Implementation Team with the following minimum composition, experience and certifications:
1 (one) Implementation Team-Leader;
1 (one) or more Datacenter Network Security Specialists.”
,,The Lot 2 Supplier must establish and maintain an Implementation Team with the following minimum composition, experience and certifications:
1 (one) Implementation Team-Leader;
3 (three) or more Datacenter Networking Specialists;
1 (one) or more Datacenter Network Security Specialists.”
We ask you kindly to confirm our understanding. / Agreed. The minimum personnel requirements are specified in the Technical Requirements (as cited above). The bidders may disregard the instruction associated with the sample form to provide two candidates. / Sample Forms – Form 3.3.6 / Clarification
19 / Referring to the following specifications found in Form 3.3.5. Financial Capabilities:
A copy of the audited balance sheets shall be attached.
Attach audited financial statements—including, as a minimum, profit and loss account, balance sheet, and explanatory notes—for the period stated in the BDS for ITB Clause 6.1 (a) (for the individual Bidder or each partner of a Joint Venture).
If audits are not required by the laws of Bidders' countries of origin, partnerships and firms owned by individuals may submit their balance sheets certified by a registered accountant, and supported by copies of tax returns,
Given that in the Bid Data Sheet (BDS) there is no qualification request related to the Bidder’s turnover, we consider that it is satisfactory to submit the completed form, without audited financial statements attached.
We ask you kindly to confirm our understanding. / Agreed. The financial qualification criteria are specified in the Instructions to Bidders / Bid Data Sheet. The bidders may disregard the instruction associated with the sample form to provide audited statements. / Sample Forms – Form 3.3.5 / Clarification
20 / Referring to the following specifications found in Forms 3.3.2 General Information Systems Experience and 3.3.2a Joint Venture Summary:
All individual firms and all partners of a Joint Venture must complete the information in this form with regard to the management of Information Systems contracts generally. The information supplied should be the annual turnover of the Bidder (or each member of a Joint Venture), in terms of the amounts billed to clients for each year for work in progress or completed, converted to Euro (€) at the rate of exchange at the end of the period reported.