“Attachment-1”
SECTION 7 (Technical Specifications of NFV Enabled IP Based International Gateway Exchange in Bangladesh on Turn-Key Basis)
Table of Contents “Attachment-1” ...... 1 Table of Contents ...... 2 SUB-SECTION 1 ...... 5 Tender in Brief ...... 5 SUB-SECTION 2 ...... 8 Scope of the Work ...... 8 SUB-SECTION 3 ...... 29 General Requirement of NFV Enabled IP Based IGW ...... 29 SUB-SECTION 4 ...... 33 NFV and Cloud Requirement for IGW ...... 33 SUB-SECTION 5 ...... 44 Environments and other Requirements ...... 44 SUB-SECTION 6 ...... 47 Requirement of Media Gateway Controller and Signalling Functions ...... 47 SUB-SECTION 7 ...... 52 Requirements of Media Gateway ...... 52 SUB-SECTION 8 ...... 57 Requirements of Gateway Router, LAN Switch, Firewall, Session Border Controller and Intrusion Detection System ...... 57 SUB-SECTION 9 ...... 74 Requirements of the Charging Facilities ...... 74 SUB-SECTION 10 ...... 79 Requirements of the Signaling, Protocols and Interfaces ...... 79 SUB-SECTION 11 ...... 81 Requirements of the System Functions, Facilities and Supervisions ...... 81 SUB-SECTION 12 ...... 89 Requirements of the System Observation and Measurement Facilities ...... 89 SUB-SECTION 13 ...... 96 Requirements of the Operation and Maintenance Facilities ...... 96 SUB-SECTION 14 ...... 118 Requirements of the Power Plant and Air-Conditioning Facilities ...... 118 SUB-SECTION 15 ...... 123
NFV_IGW_Attachment-1&2 Page 2/185
Technical Specifications for Test Equipment (To Be Quoted Optionally ...... 123 SUB-SECTION 16 ...... 131 Requirements of the Short Message Service Gateway (To Be Quoted Optionally) ...... 131 SUB-SECTION 17 ...... 135 Requirements of Ancillary Facilities ...... 135 SUB-SECTION 18: Deviations and Reservations...... 139 Annex 1.1: Capacity Requirements of the Media Gateway Controller ...... 142 Annex 1.2: Capacity Requirements of Media Gateway ...... 143 Annex 1.3: Capacity Requirements of each Gateway Router ...... 144 Annex 1.4: Capacity Requirements of each LAN Switch at Moghbazar ...... 145 Annex 1.5: Capacity Requirements of each Firewall ...... 146 Annex 1.6: Capacity Requirements of each SBC ...... 147 Annex 1.7: Format for Maintenance Support during Guarantee Period ...... 148 Annex 1.8: Format for Annual Maintenance Support after Guarantee Period ... 152 Annex 1.9: Declaration on Observance of Ethics ...... 156 Annex 1.10: Declaration of Joint Liability ...... 157 Annex 1.11: Bond for Spares ...... 158 Annex 1.12: Bond for Expansion Guarantee ...... 159 Annex 1.13: List of Material Deviation ...... 160 FORM A: Grand Summary Price of the Bid ...... 162 FORM B.1: Summary Price for Media Gateway Controller (MGC) ...... 163 Form B.2: Summary Price for Media Gateway (MGW) ...... 164 Form B.3: Summary Price for COTS Server ...... 165 Form B.4: Summary Price for Router, LAN Switch, Firewall, Session Boarder controller and Intrusion Detection System ...... 166 Form B.5: Summary Price for BTRC Monitoring Facilities and LI Connectivity Facilities ...... 167 Form B.6: Summary Price for Network Management System ...... 168 Form B.7: Detail List and Price for other Equipment ...... 169 Form B.8: Detail List and Price for other Service ...... 170 Form B.9: Summary Price for DC Power and Air Conditioner Equipment ...... 171 Form B.10: Summary Price for Auxiliary Installation Equipment ...... 172
NFV_IGW_Attachment-1&2 Page 3/198
Form C.1: Detail List and Price for All Individual Items/Parts of Media Gateway Controller (MGC) ...... 173 Form C.2: Detail List and Price for All Individual Items/Parts of Media Gateway (MGW) ...... 174 Form C.3: Detail List and Price for All Individual Items/Parts for COTS Server . 175 FORM C.4: Detail List and Price for All Individual Items/Parts of Router, LAN Switch, Firewall, Session Boarder Controller and Intrusion Detection System ..176 Form C.5: Detail List and Price for All Individual Items/Parts of BTRC Monitoring Facilities and LI Connectivity Facilities ...... 177 Form C.6: Detail List and Price for All Individual Items/Parts of Network Management System ...... 178 Form C.7: Detail List and Price for All Individual Items/Parts of Other Equipment ...... 179 Form C.8: Detail List and Price for all individual items of Other Services ...... 180 Form C.9: Detail List and Price for all individual items/Parts of DC Power and Air Conditioner Equipment ...... 181 Form C.10: Detail List and Price for all individual items/Parts of Auxiliary Installation Equipment ...... 182 Form D.1: Detail List and Price for Mandatory Maintenance Spares for 02 (Two) Years ...... 183 Form D.2: Detail List and Price for Consumable Item for 02 (Two) years ...... 184 Form D.3: Detail List and Price for Installation Materials ...... 185 Form D.4: Detail List and Price for Recommended Maintenance Spares for Buffer Stock ...... 186 Form D.5: Detail List and Price for Tools and Testers and other Equipment ..... 187 Form D.6: Detail List and Price for Station Furniture ...... 188 Form D.7: Detail List and Price for Security and Surveillance System ...... 189 Form E.1: Price Quotation for all Optional item ...... 190 FORM E.2: Quotation for Future Order ...... 191 Form F: Manufacturer‟s Information of Equipment, Accessories and Country of Origin Declaration ...... 192 Form G: Clause by Clause Compliance Schedule ...... 193 Form H: List of Certificates attached with ...... 194 “Attachment-2” ...... 195
NFV_IGW_Attachment-1&2 Page 4/198
SUB-SECTION 1
Tender in Brief
1.1 Introduction
The technological advancement in the field of telecommunication has brought new generation and advanced technologies in the International Long distance Telecommunication System (ILDTS) services along with traditional Time Division Multiplex (TDM) facilities. Technologies related to Internet Protocol (IP), Network Function Virtualization (NFV) and cloud succeeded in proliferating popularity due to its compatibility with different IP networks for Telecommunication services like audio, video, SMS and MMS services throughout the world. Presently, BTCL is providing all overseas voice services without redundant node. So, single point failure on International Gateway (IGW) core network can bring catastrophe and negative impact in overseas communications. On the other hand, only one NGN based IGW has been commissioned on February, 2014. Therefore, BTCL needs redundant/load sharing IP based IGW to provide international voice services smoothly. Bangladesh government has the vision to materialize digital connectivity to ensure that information and communication technology (ICT) related services are available to everyone. As a part of Bangladesh government, BTCL intends to purchase NFV enabled IP based international gateway (IGW) for strengthening digital connectivity and digital services in compliance with ILTDS policy. The system shall be compatible with prevailing Mobile Number Portability (MNP) devices and equipment installed at BTCL IGW1, Mohakhali and BTCL ANS Gateway at Mogbazar to offer MNP services as per BTRC guidelines
1.2 Objectives The objectives of “Supply, Installation, Testing and Commissioning of NFV Enabled IP based International Gateway Exchange in Bangladesh on Turn- Key Basis” are as follows:
a) To Install and Commission NFV enabled IP based international gateway and its related equipment to ensure smooth and ubiquitous international voice, video, SMS, MMS and MNP services.
NFV_IGW_Attachment-1&2 Page 5/198
b) To provide lawful interception (LI) facilities to Bangladesh Telecommunication Regulatory Commission (BTRC) for monitoring purpose. 1.3 Targets and Output of the Project
The followings are the targets and outputs of NFV based IGW project which will be implemented by Bangladesh Telecommunications Company Limited (BTCL):
a) Installation and commissioning of hardware and software for different sub- systems of NFV enabled IP based International gateway and its related core network equipment, storages, servers, Data communication equipment and Network Management System (NMS) b) To provide TDM and IP based overseas services through IGW c) To establish necessary connectivity and configuration with existing and newly installed IOS, billing platform, MNP and Transmission systems at Mohakhali and Moghbazar. d) To provide necessary training to build up a technical team for this field. e) To provide lawful interception access to BTRC. 1.4 Required Goods The list of goods to be procured under this project is given below. However, the bidder shall quote any additional hardware and/or software (including license) for successful implementation of the tender:
a) One IP based VNF IGW at Moghbazar Telephone Bhavon as shown in Annex 1.1 to handle following types of international calls and Services
i) International direct dialed voice and Video calls from PSTN/ PLMN,
ii) International voice and video calls for MNP subscribers,
iii) International fax calls,
iv) International Toll-free calls,
v) Home Country Direct Service calls,
vi) Roaming calls to and from Mobile phones (Post-paid and pre-paid),
vii) ISDN calls and
viii) International Short Message Service (SMS).
NFV_IGW_Attachment-1&2 Page 6/198
b) One Media Gateway at Moghbazar Telephone Exchange Building having required capacity as shown in Annex 1.2.
c) Network Management Systems, Session Border Controllers, Gateway Routers, Firewalls, LAN Switches etc. and others ancillary items.
d) Lawful Interception and Monitoring facilities as per IGW License Guideline and directives provided by BTRC in this regard.
e) CDR transfer and monitoring facilities from BTCL to BTRC, IOF and BTCL Billing premises as per IGW License Guideline and directives provided by BTRC.
f) DC/AC Power supply for the systems at Moghbazar site.
g) Air-Conditioning equipment and its related necessary facilities at Moghbazar site.
h) Necessary tools, Tester and other equipment.
i) Furniture
j) Documentation.
1.5 List of Services As mentioned the sub-sequent sub-sections, The bidder shall provide at least the following services (but not limited to):
a) Project Management; b) Survey, Network Planning and Design Services; c) Installation, Testing and Commissioning services; d) Factory Premises Acceptance Test (FPAT); e) Provisional Acceptance Test; f) Final Acceptance Test; g) Factory Training; h) Local Training; i) Maintenance support during 02 (Two) years guarantee period; j) 01 (one) year maintenance support after guarantee period; k) Balancing, Integration and Configuration of Supplied equipment/system, interworking with existing system MNP equipment/devices, existing and newly proposed IOS and IGW;
=== End of Sub-section 1 ===
NFV_IGW_Attachment-1&2 Page 7/198
SUB-SECTION 2
Scope of the Work
2.1 Introduction
a) BTCL intends to purchase NFV enabled IP-V6 based IGW. The IGW platform shall be installed at Moghbazar Telephone Exchange Bhavon, Dhaka with one TDM media gateway at same location. This switching system will provide interconnections among the Interconnection Operator Switch (IOS) and overseas carriers. The system should be compatible with existing mobile number portability (MNP) facilities, equipped with Lawful Interception (LI) facilities and should be able to send operational, measurement and CDR data to BTRC, Law Enforcement Agencies (LEA) and associated Billing Center(s).
Required hardware and software shall be procured to install NFV enabled IP based IGW platform. The bidder shall propose all the required hardware, Software, Licenses and Spares to implement the work on turn-key basis. This platform shall have many added values in terms of
i) Virtualization of service platform and infrastructure
ii) Easy operations and maintenance.
iii) Centralized Maintenance
iv) Simplified integration
v) Reduced power consumptions
Proposed BTCL NFV enabled IP Based IGW platform has been given in Section 8 (Drawings) as shown in Figure 8.2 and capacity requirements have been given in Annex 1.1 to Annex 1.6. The bidder shall follow those requirements to ensure Virtual Network Function (VNF), Hardware and Cloud OS & Orchestration etc. Necessary goods and services under this tender have been mentioned in sub- sections 1.4 and 1.5 respectively of this document. b) As applicable, the Bidder shall integrate the solution with existing BTCL‟s multi- vendor and multi-protocol networks and network management systems and customize the setup to satisfy BTCL‟s network modeling, planning and simulation
NFV_IGW_Attachment-1&2 Page 8/198
requirements, in order to provide pro-active assurance, rapid troubleshooting, network scalability and trend analysis.
2.1.2 Unless otherwise described in the Technical Specifications, the scope of provision shall cover surveying, designing and drawing, manufacturing, supplying, installing, testing and commissioning of equipment and material and its related facilities on “Full Turn-Key” basis.
2.1.3 The Bidder shall explain, in a separate and self-explanatory document with his/her offer, the process of expansion from the initial equipped capacities to the final capacities of the elements.
2.1.4 Detail Technical Specifications of various components of the required system/service are given in subsequent sub-sections of this document.
2.1.5 The bidder shall note that, until and unless a specific work, equipment or service is defined as “Optional”, all the works, equipment and services listed in various sub-sections of this document shall be deemed to be “Mandatory”. If the bidder disagrees, to provide any or many items of mandatory works, equipment or services, its bid shall automatically become “Non-Responsive”.
2.1.6 Installation of transmission equipment between the location of the system to be purchased and BTRC / LEA premise is not within the scope of this work. However the successful bidder shall responsible for proper interfacing with the transmission equipment and end to end testing and commissioning.
2.1.7 The bidder shall supply all necessary spare parts and consumables to be used during installation, testing and commissioning and operation of the systems, up to the end of Guarantee Period. The bidder shall submit a list according to Form D1, D2, D3 and D4 of technical part. The submission of such list is mandatory and failure to submit shall be regarded as “Non Compliance”.
2.2 Supply and Installation of “Raised Floor” in the Switching, OMC and NOC Rooms The materials for such works shall be moisture proof, termite proof and non- inflammable
and must not be harmful to the system and its personnel. The minimum size of such works
shall be total 26 x 21 square feet for Equipment and 28 x 19 square feet for NOC and OMC Room.
Moreover, the following criteria must be satisfied:
NFV_IGW_Attachment-1&2 Page 9/198
a) Size : (60 cm * 60 cm) ± 20%
b) Weight : > 2.8 kg per sq. feet
c) The metallic stands supporting the „raised floor tiles‟ shall be fixed with floor by strong
adhesive. But the actual area shall be finalized during BOQ negotiations.
2.3 Supply and Installation of “False Ceiling” in the Switch, OMC and NOC room at Moghbazar. The materials for such works shall be moisture proof and termite proof and must not be harmful to the system and its personnel. The approximate size of equipment room shall be 26 x 21 square feet. On the other hand, approximate size of OMC and NOC Room shall be 28 x 19 square feet. But the actual area shall be finalized during Bill of Quantity (BoQ) negotiations. The Ceiling of Switch, OMC and NOC rooms should be covered with standard False Ceiling. The material used for false ceiling shall be of Gypsum design board with minimum 9 mm thickness and 2 Ft x 2 Ft length and width. The Gypsum shall be ceiling mount and there shall be aluminum frame which includes cross rails, channels and channels jointers etc.
2.4 Aluminum-Glass Partitions Supply and Installation of "Aluminum-Glass partitions" of adequate sizes to separate the switch Room, OMC Room and NOC room.
2.5 Lighting Facility Supply and installation of adequate „Lighting Facility‟ for switch, OMC and NOC rooms (at least seven lighting set). Battery room and power room (at least two lighting set). Each of the lighting set shall have at least two fluorescent tubes.
2.6 Emergency Lights Supply and Installation of adequate “Emergency Lights” in Equipment, OMC and NOC rooms. The exchange batteries shall be used as back-up power for this purpose.
2.7 Electrical Grounding All the equipment installed under this purchase has to be connected with existing grounding point at BTCL site. The bidder shall examine prevailing grounding system and different testing parameters. If grounding rods and necessary equipment is required, the bidder shall supply and install those provisions for the
NFV_IGW_Attachment-1&2 Page 10/198
safety of the equipment under this purchase. Failure/Disagreement shall be treated as “Material Deviation”.
2.8 Lightning and Surge Protection Facility Supply and Installation of adequate “Lightning and Surge Protection Facility” for all equipment.
2.9 Fire detection and fire fighting Facility Supply and Installation of adequate “Fire detection and fire fighting Facility” for all equipment at Moghbazar switch, OMC and NOC room.
2.10 Alarm Bell The bidder shall Supply and install external high-dB level alarm bell at Moghbazar. The bells are to be triggered by system's emergency alarms and are to be powered by exchange no-break power source. Each bell has to be fitted at a place from where sound can be heard easily from the building security duty- point.
2.11 Building Modification for Switch, OMC and NOC Rooms The proposed switch room area is approximately 26 x 21 square feet. The switch room was used for earlier old version TDM switch. The bidder shall dismantle existing equipment of the switch room which includes (but not limited to) old switching equipment, Digital distribution frame (DDF), Optical distribution frame (ODF), Digital Cross-connect equipment etc. and keep those materials at BTCL‟s designated place as per direction of concern division/unit. On the other hand, the proposed NOC and OMC room area is approximately 28 x 19 square feet. The bidder shall visit the proposed Switch, OMC and NOC room before submission of the bid. BTCL concern unit will assist to visit the spot. The bidder shall make necessary survey and shall also be entirely responsible to make necessary changes.
If any modification of existing floor, walls, false ceilings and glass partition are required or any other new materials are required for this installation, the Bidder shall bear all related costs (including finish painting and proper cleaning). But the actual size/area shall be finalized during BOQ negotiations. Any disagreement shall be considered as “Major Deviation”.
NFV_IGW_Attachment-1&2 Page 11/198
2.12 Station AC Power Wiring with Low Tension Switchgear (LTS) The Contractor shall install standard “Station AC Power Wiring” at Moghbazar for all the equipment to be installed under this purchase. The wiring shall start from the station AC power, bus bar of BTCL, which will be connected to a LTS provided by the Contractor. The capacities of the wiring shall be at least 200% of the calculated present total requirement of power for all equipment.
2.13 Tools and Testers and Other Equipment The Bidder shall supply a separate list and shall quote, according to "Form D.5" for all essential “General Tools and Testers” for proper operation and maintenance of the system. Failure to quote for this item shall be treated as “non compliance” and it shall be considered that the bidder proposes to supply any and all tools and testers, as fixed up by BTCL during contract negotiation, “free of charge” to BTCL.
The list (Form D.5) must include (but not limited to) the following tools and Tester:
a) Set of required specific tools and testers for all equipment : 1 (one) Set
b) Digital Multi-meter (with clamp-on facility for AC/DC current measurement): 1(one)
c) Optical Power meter with minimum 20 Km Laser source (with common wavelength detectors, range +30 dBm to -70 dBm and standard interface) for power/attenuation/fiber continuity test: 01 (One)
d) External Hard Drive with USB 2.0/3.0 Ports (High quality, well-known/reputed brand (minimum 4 TB): 02 (two) Nos.
2.14 Station Furniture a) O & M Furniture
The Bidder shall supply necessary Station O & M furniture for OMC room. The furniture should be of high quality steel/wood/fiber and the standard and specification of these items are mentioned in Sub-Section 13 of this document. The bidder shall fill Form D.6. Failure to quote Form D.6 for furniture item shall be considered as “non-compliance” and it shall be considered that the bidder proposes to supply any number of this item “free of charge” to BTCL.
NFV_IGW_Attachment-1&2 Page 12/198
b) Storage Cabinet
The Bidder shall supply necessary storage cabinets from country or abroad. The cabinets shall have good design and shall be made with good quality steel and must have enough space to accommodate station spares and operation manual. Failure to quote for this item shall be considered as “non-compliance” and it shall be considered that the bidder proposes to supply any number of this item “free of charge” to BTCL.
2.15 Mandatory Maintenance Spare Parts and Consumables to be used before end of Guarantee Period The Bidder shall supply all necessary spare parts and consumables used during installation, testing and commissioning and operation of the systems, up to 02 (two) years during Performance Guarantee Period. The bidder shall quote such list as per Form D.1, D.2 and D.3.
If the bidder disagrees/fails to quote Form D.1, D.2 and D.3, the bid shall be considered as “Major Deviation”.
2.16 Recommended Maintenance Spares for Buffer Stock
a) BTCL reserves the option to buy maintenance spares during flow and availability period in any quantity it deems fit and necessary. b) The bidder shall quote recommended maintenance spares according to Form D.4. Such quotation is mandatory and failure to quote shall be regarded as “Non compliance” and it shall be concluded that the bidder intends to give any number of all spares to BTCL at totally “free of cost”. c) The list shall include at least 2 (two) units of all possible replaceable items/ cards/ modules (as the case may be) for all equipment and systems covered by this purchase. d) Though contracting for such spares will be optional/ discretionary choice for BTCL, the total price of the list will be added during comparative evaluation of the financial bid. e) If the bidder fails to include any item/ card/ module in the supplied list, while during the life-time of the equipment requirement of such an item/ card/ module becomes imperative, the bidder shall have to supply any required number of such item/ card/ module totally “free of charge” to BTCL.
NFV_IGW_Attachment-1&2 Page 13/198
2.17 Spare Parts Guarantee The Bidder shall provide a separate guarantee (as per format in Annex 1.11) to the effect that, he shall guarantee the flow and availability of all spare parts and units without major design changes for at least 8 (eight) years from “the date of effect” of the Provisional Acceptance Certificate (PAC). If, within this period, there is any major design change or stoppage of production of supplied equipment, the bidder shall bear all the costs related to provision of alternate solutions.
If the bidder disagrees to the format of the guarantee, as shown in Annex 1.11, the bid shall be considered having “Material Deviation”
2.18 Expansion Guarantee The Bidder shall provide a separate guarantee (as per format in Annex 1.12) to the effect that, he/she shall guarantee the flow and availability of all equipment, materials and services required for any subsequent expansion of its offered equipment for at least 8 (eight) years from “the date of effect” of the Provisional Acceptance Certificate (PAC). If, within this period, there is any major design change or stoppage of production, the bidder shall bear all the costs related to provision of alternate solutions.
If the bidder disagree to the format of the guarantee, as shown in Annex 1.12, the bid shall be considered having “Material Deviation”.
2.19 Maintenance Support 2.19.1 Maintenance Support during Guarantee Period
a) As part of its Turn-key contractual liabilities, the bidder shall provide, for all the equipment covered by this purchase “Maintenance Support during Performance Guarantee Period”; the general terms & conditions of the support being described in brief in Annex – 1.7 attached with this document.
b) The bidder‟s disagreement to providing this formatted service shall be considered as “Material Deviation”.
c) Bidder shall include in his/her offer prices for this service. Failure to quote shall be treated as “non compliance” and it shall be considered that the bidder proposes to provide this "free of charge" to BTCL
d) The supports shall start from the date of cutover into commercial service of the first equipment/ system purchased under this contract.
NFV_IGW_Attachment-1&2 Page 14/198
e) The period of the service shall continue uninterrupted for 02 (Two) calendar years from “the date of effect” of the last Provisional Acceptance Certificate (PAC) of the contract.
f) Whole contract price for Maintenance Support services during Guarantee Period will be paid in 04 (four) equal payments on half yearly basis and shall be paid by the bank half yearly upon submission by the contractor a “Certificate for Completion of Maintenance Assistance” after the end of each half year to support its claim. Such a completion certificate shall be issued by Project Director or assigned officer of BTCL upon completion of the relevant program(s).
g) For payments of the services in foreign currency, BTCL shall open a separate irrevocable Letter of Credit (L/C) in favor of the contractor, one for each year of the service period.
h) The payment in Bangladesh Taka for the services will be made by crossed cheques by the relevant office of BTCL. However, the option for opening of Local L/C shall also be open.
2.19.2 01 (One year) Annual Maintenance Support after Guarantee Period a) As part of its Turn-key contractual liabilities, the bidder shall provide unconditional and irrevocable “Annual Maintenance Support after Performance Guarantee Period”. At the end of guarantee period, annual maintenance support shall continue for 01 (one) year. Initially BTCL will make a contract for 01 (one) year; however the bidder shall guarantee that if so BTCL desires, the period of such support can be extended, on yearly contract basis, for at least 05 (Five) years. The general terms & conditions of the support have been described in brief in Annex -1.8 attached with this document. b) The period of the first year term of this service shall deem to have started from the date of end of the Performance Guarantee Period. c) The bidder‟s disagreement to providing this formatted service shall be considered as “Material Deviation”. d) Bidder shall include in his offer prices for this service. Failure to quote shall be treated as “non compliance” and it shall be considered that the bidder proposes to provide this "free of charge" to BTCL.
NFV_IGW_Attachment-1&2 Page 15/198
e) The payment in Bangladesh Taka for the services will be made by crossed cheques by the relevant office of BTCL. However, the option for the opening Local LC shall also be open. f) Payment will be made on receipt of proper invoices of the contractor accompanied by the copy of the “Certificate for Successful Completion of Maintenance Assistance Services.” g) 50% (Fifty percent) of service amount for each year shall be paid at the end of each half yearly period of Maintenance Services period.
2.20 Duration of Performance Guarantee Period 2.20.1 The bidder‟s offer shall include an overall “Performance Guarantee Period” for the whole equipment covered by this purchase. This period shall deem to have started from the cut-over of the first equipment into commercial service and last for 02 (Two) calendar years from “the date of effect” of the last PAC of the contract.
2.20.2 During the period of this Guarantee, the bidder shall offer all material, equipment, services and Maintenance support as described in relevant clauses for “Spare Parts and consumables” and “Maintenance Support up to Performance Guarantee Period”. Bidder(s) refusal to offer the guarantee specified in this clause shall be treated as “Material Deviation”.
2.21 Testing Services Three (03) types of tests shall be performed during execution of the contract. i.e. Factory Premises Acceptance Test (FPAT), Provisional Acceptance Test (PAT) and Final Acceptance Test (FAT).
2.21.1 Factory Premises Acceptance Test (FPAT) a) Testing at manufacturer‟s premises, to be termed as “Factory Premises Acceptance Test (FPAT)”, shall be carried out (on random sampling basis) for all type of equipment to be supplied under this purchase. b) A team comprising of BTCL Engineers will check the equipment in order to ascertain their conformity with tender requirement, contract and BoQ specifications before shipping of the equipment. The FPAT shall include all tests as per relevant ITU-T and/or other relevant recommendations.
NFV_IGW_Attachment-1&2 Page 16/198
c) A certificate shall be signed by BTCL engineer(s) upon completion of factory test at site of manufacturer‟s premises, which will be termed as “Factory Premises Acceptance Test Certificate”.
d) The details of test program shall be as follows. If the bidder does not agree to this basic minimum format, its disagreement or deviation shall be considered as “Major Deviation”.
i) Number of BTCL Engineers : 03 (Three) to be nominated from BTCL
ii) Number of working days : 07 (Seven)
iii) Per diem charge to BTCL : US$ 120 (one hundred twenty) per Engineers day (including holidays in between) per person
iv) Other facilities : 1) Local Transportation
2) Standard Accommodation
3) Medical Services (if required)
4) Institutional facilities
5) Travel Insurance
6) Both way Full-fare Air Ticket
The bidder may propose more number of such FPAT or may propose extended periods for such FPAT, if necessary.
2.21.2 Provisional Acceptance Test (PAT) a) Before acceptance of the installed system/ equipment, BTCL representatives shall carryout, on site, detailed tests of all equipment to ascertain their inter- working ability with relevant equipment of the other manufacturers, working reliability, concurrence to the agreed technical and other specifications, inventory checking of installed equipment etc. Such tests shall be termed as “Provisional Acceptance Test (PAT)”. Prior to commencement of such tests, the contractor
NFV_IGW_Attachment-1&2 Page 17/198
shall submit a proposed procedure for the PAT to be subsequently passed by BTCL.
b) PAT Team will be formed by General Manager (M&O) or Project Director of the project with the approval of Managing Director, BTCL. On completion of installation and self-testing of any system/ equipment, the Bidder shall submit three (03) copies of self-test results to BTCL and offer that system/ equipment is ready for Provisional Acceptance Test (PAT). Supplier shall give 15 (Fifteen) days prior written notice of the date on which he will be ready to execute PAT, hereinafter referred to as “PAT Ready Date”.
c) BTCL shall start such tests as soon as possible upon receipt of the request. The bidder may, upon agreement by the both parties offer PAT for any part or parts of the total system. Such request for the partial PAT may also be asked for by BTCL. d) The bidder shall be totally responsible for the arrangement of all equipment, consumables, test gears and measuring equipment required for the PAT. e) The bidder‟s engineer shall be liable to make necessary arrangement to complete any kinds of tests requested by BTCL PAT members during PAT procedure. f) In addition, the bidder has to provide per-diem costs to the PAT engineers as per following:
For whole System:
i) Number of BTCL Engineers of PAT : 5 (five) team for all equipment sites covered by this purchase : 6 (Six)
ii) Number of days allowed for per : 10 (Ten) working days per diem charge person
iii) Per diem charge to BTCL PAT : Taka 2000/- per day per members person
iv) Other facilities : Transportation
However, the bidder shall note that, if necessary, any or all PAT can continue for more than the above scheduled period; but, in such cases, the bidder shall not be liable to pay per-diem for those additional days.
NFV_IGW_Attachment-1&2 Page 18/198
2.21.3 Successful Bill Run Test (SBT) a) During PAT, The SBT will be started in details with random cross-checking of the authenticity, accuracy and mathematical correctness of various Call Data Record (CDR)s generated by the system through the running of bills and billing cycles in its Billing Centre. SBT will be carried out by PAT team.
b) Such checking will involve all types of billing CDRs covered by the system scope including (but not limited to) “Local Inter-connect Billing”, “National Inter- connect Billing” and “International Inter-connect Billing”.
c) Such checking for inter-connect billing will be carried out with relevant inter- connect partners.
d) If and only if, the results of each of the check events show errors by the billing system to be below 0.1% (zero point one percent), the Bill Run Test shall be considered as successful; and such event will be termed as “Successful Bill Run (SBR)”.
e) If and only, SBR happens for at least 03 (three) local and/ or distant-end partners, the event in a duty cycle (15 days) will be considered as “Successful Bill Run Test (SBT)”.
f) PAT team shall complete such two SBTs within 01 (one) month. In the event of completion of Two (02) of such SBTs and successful completion of PAT, the system shall become eligible for issuance of PAC.
2.21.4 Issuance of PAC
a) After completion of SBT, the PAT team shall check the compliance statement of the bidder and the contract. Compliance statement of the bidder & the contract conditions shall be implemented/ fulfilled with full satisfaction of BTCL.
b) PAT team shall check the quality of the installation materials which must be standard & world class and with full compliance to technical specification. If non- standard installation materials are used, the bidder shall be awarded 5 (five) penalty points for each separate item which shall be considered only for PAC issuance purpose. For installation material, any international standard will be acceptable.
c) PAT team shall check the quality of the installation works which shall be standard and with full satisfaction to BTCL. If the overall installation work is non-standard &
NFV_IGW_Attachment-1&2 Page 19/198
not satisfactory, the bidder shall be awarded 5 (five) penalty points which shall be considered only for PAC issuance purpose.
d) Penalty points as per the technical specification shall be awarded to the bidder for each of the incomplete or partially completed works listed during PAT and SBT for PAC issuance purpose.
e) If the total penalty points awarded by the bidder are equal or more than 25 (twenty five), PAC shall not be issued.
f) The bidder will be given 30 (thirty) working days for the completion of the works pointed out by PAT team.
g) If it is found in PAT that, the contractor deviated in one or many items which has got a weight of “Critical Deviation” and/or “Material Deviation” according to the technical specification of tender document, then BTCL is free to put the whole system into commercial operation without issuing PAC for the whole system or part of system as applicable.
Any disagreement or deviation shall be treated as “Material Deviation”
h) The bidder shall take all necessary action for cut over of the system on the date fixed up by BTCL irrespective of PAC whether issued or not.
i) After such kind of cut over, if the bidder improves/completes the pending works, the penalty points regarding issuance of PAC will be recalculated accordingly. If the total penalty points become less then 25 (twenty five), PAC shall be immediately issued in favor of the Bidder by issued under the signature of General Manager (Development Coordination) or by Project Director of the project with the recommendation of Provisional Acceptance Test (PAT) team and with the approval of Managing Director, BTCL.
j) If Provisional Acceptance Certificate is not issued within 30 (Thirty) working days in spite of the penalty points regarding issuance of PAC is less than 25 (Twenty Five), then the Provisional Acceptance Certificate (PAC) will be deemed to have been issued by BTCL and shall be equivalent in all respect to a Certificate issued by BTCL.
k) For any clause or clauses declared by the bidder to be “not complied” during submission of the bid and which have already been agreed in writing by BTCL in
NFV_IGW_Attachment-1&2 Page 20/198
any subsequent document, the awarding of such penalty points will not be applicable.
l) “Non-Compliance” or “conditional compliance” of any of the above clause or sub clause shall be treated as “Material Deviation”.
m) For avoiding any complexity regarding issuance of PAC, The bidder shall carefully and sincerely fill up the compliance statement keeping in mind the technical ability of the offered system to meet the requirements of the technical specification
2.21.5 Final Acceptance Test (FAT) a) After successful completion of the PAT and cut-over of the system, the Engineers of the Bidder will take prompt necessary steps to remove all types of faults and replace all types of faulty equipment at the cost of the supplier. At the end of 02 (two) years “Performance Guarantee Period”, the overall performance of all equipment will be reviewed and this review shall be termed as “Final Acceptance Test (FAT)”.
b) Supplier shall give 15 (Fifteen) days prior written notice of the date on which he/she will be ready to execute FAT, hereinafter referred to as “FAT Ready Date”. With such notice the contractor shall submit a declaration that all the pending items found during PAT (if any) has been resolved successfully. Otherwise such notice will not be considered.
c) FAT Team will be formed under the signature of General Manager (M&O) with the approval of Managing Director, BTCL or Project Director of the project.
d) The review shall include (but not limited to) the required working reliability and performance standards of the equipment to meet tender specifications, the bidder‟s responsiveness to resolve all shortcomings mentioned in PAT reports and the bidder‟s removal of all pending and outstanding faults or shortages encountered during the Performance Guarantee Period for the Contract. When this FAT becomes due, the bidder shall make an official request to BTCL for starting of the FAT and BTCL shall start the FAT within one month after receipt of the request from the bidder.
e) The bidder shall be responsible for arrangement of all equipment, consumables, test gears and measuring equipment required (if any) for such review tests.
NFV_IGW_Attachment-1&2 Page 21/198
f) In addition, the bidder has to provide per-diem costs to FAT engineers as per following:
For whole System:
i) Number of BTCL Engineers of FAT : 5 (five) team for all equipment sites covered by this purchase : 6 (Six)
ii) Number of days allowed for per : 5 (Five) working days per diem charge person
iii) Per diem charge to BTCL FAT : Taka 2000/- per day per members person
iv) Other facilities : Transportation
However, the bidder shall note that, if necessary, any or all FAT can continue for more than the above scheduled period; but, in such cases, the bidder shall not be liable to pay per-diem for those additional days.
g) After successful completion of FAT, Final Acceptance Certificate (FAC) will be issued under the signature of General Manager (Development Coordination) or by Project Director of the project, with the recommendation of Final Acceptance Test (FAT) team and with the approval of Managing Director, BTCL within 45 (Forty five) working days from the completion period
2.22 Training Course The Bidder shall provide the training to BTCL Engineering personnel. The curriculum shall be enough to facilitate transfer of technology for planning, designing, expanding, IP security, Internet of things (IoT) and proper operation and maintenance of all the systems covered by this purchase to BTCL engineering personnel. If the bidder does not agree to this basic minimum format, its disagreement or deviation shall be considered as a “Major Deviation”.
NFV_IGW_Attachment-1&2 Page 22/198
2.22.1 Factory Training Following generic areas should be included in the training program. Actual content of each item should, however, be customized to match with the architecture and solutions offered by the bidder.
This course module will cover at least the following broad topics:
NFV Architecture, its different sub-systems including different servers (storage, NMS), their working principle, Switching Essentials and Technologies, Network Design, Network Installation and Configuration, Protocols and Interfaces, Signalling Systems (SS7 and SIP), VoIP technologies and Issues, Network Management Systems and Tools, Service provisioning, Bandwidth monitoring and controlling, Database Management systems, Configuration, operation and management of billing and storage servers, Network risk and quality issues, IP security, IoT, troubleshooting of various sub-systems and servers of the purchase etc.
The details of this course module are given below:
i) Number of BTCL Graduate : 5 (Five) Engineers
ii) Number of minimum working : 15 (Fifteen) days
iii) Per diem charge to BTCL : US$ 120 (one hundred twenty) per Trainees day (including all holidays in between and travel days) per person
iv) Other facilities : 1) Local Transportation
2) Standard Accommodation
3) Institutional facilities for trainees
4) Medical Services (if required)
5) Travel Insurance
6) Both way Full-fare Air Ticket
NFV_IGW_Attachment-1&2 Page 23/198
2.22.2 Local Training The Bidder shall provide training in Bangladesh at BTCL premises. The details of the local training shall be as follows:
For all equipment:
a) Number of BTCL Graduate Engineers : 12 (Twelve)
b) Number of minimum working days : 15 (Fifteen)
c) Per diem charge to BTCL Trainees : BD Taka 1500/= (one thousand five hundred) per day per person for working days.
The course material should be the same as of the factory training.
2.23 Inter-connection between different ODF a) The Bidder shall be responsible for making inter-connection facility (including supply of all required material, optical fiber cables, connectors at both ends of inter-connecting cable and related service) between its own system ODF and BTCL‟s existing Switching/Transmission ODFs, IOS/IGWs Transmission ODFs in the same building (if applicable).
b) Probable requirements of the connectors, optical fiber cables, cable tray etc. should be checked during the survey, before the submission of the financial bid in the second stage, by the bidder.
2.24 Inter – working with the Existing Systems The Bidder shall be responsible to ensure that all the system covered by this purchase/work shall be able to inter-work with all the existing systems of BTCL and other relevant operators. The bidder shall make necessary survey and shall also be entirely responsible to solve any mismatch, if encountered.
The bidder shall also be responsible to ensure that the NGN-based exchanges, Mobile Number Portability (MNP) platform, already installed in BTCL‟s network and/ or the existing/ under installation IGW, IOS, IOF and Billing System can be inter-connected live/ on-line to the system to be supplied by the bidder. Bidder will be responsible to ascertain the necessity of additional hardware/ software/ modules and other materials at its own end and quote for such items in unit cost basis. All additional requirements of any new and/ or undefined cost shall be
NFV_IGW_Attachment-1&2 Page 24/198
entertained by the bidder. Any disagreement or deviation shall be treated as “Material Deviation”.
2.25 Installation Material The Bidder shall provide all installation material for all of the equipment covered by this purchase. The material shall include all type local material like fuel, power etc necessary to be used during installation and testing functions.
2.26 Installation and Commissioning Services The Bidder shall be responsible to provide all services related to installation, testing, commissioning and cut-over services for all equipment covered by this purchase.
2.27 Survey, Network Planning and Design Services a) As part of its turn-key responsibility, the successful bidder shall be responsible to provide all services related to installation survey, planning and design for all equipment/ system covered by this purchase.
b) A report shall be submitted to BTCL's relevant office after completion of that work.
2.28 Documentation a) The successful bidder shall supply at least (but not limited to) the following documents before PAT of each site.
i) Technical Documentation for all equipment of the Site: 1 set of hard copy and 1 set in CD/DVD.
ii) As-built installation drawings for all equipment: 1 set in CD/DVD and 1 set in hard copy.
iii) Station AC power wiring diagrams: 1 set in CD/DVD and 1 set in hard copy per site.
b) Detail technical document for Network Management Centre (NMC): 1 set in CD/DVD and 1 set in hard copy. c) Each O&M terminal should be accompanied with online documentation. d) Brief description of operation, maintenance and commissioning, routine and frequent tasks and step by step procedure to perform them: 1 set in CD/DVD and 1 set in hard copy.
NFV_IGW_Attachment-1&2 Page 25/198
2.29 Possibility of change in Scope of Work and BoQ The Bidder shall consider that, the size, number and location of nodes and other equipment and subsequently the total BoQ may change, depending upon the actual requirement during BoQ preparation with the successful bidder.
2.30 Prevalence of different clauses and Sub-Sections If, for any item, the contents of a Clause of any section contradict with the contents of any other Clause of the same or other section of the Tender Document, the prevalence of the Clause shall be as follows:
a) In all cases, regulations of “Procurement Policy of BTCL” as adopted from “Public Procurement Regulation 2008” shall prevail over this Tender Document. b) In case of different sections, Employer‟s requirements shall supersede other sections. c) In case of same section, next sub-sequent sub-sections shall supersede previous sub-sections. d) In case of same section, next Clause shall supersede previous Clause. e) In case of any corrections made by BTCL, corrections will prevail with its due position.
2.31 Unit Price for Future Orders a) The unit prices for all future orders for all equipment and services covered by this purchase shall be equal to or below the prices quoted in the original contracted offer.
b) The Bidder shall quote, with his offer, a detailed „Future Order Formula‟ separately for equipment and services in Form E2 and submit in the Financial Documents.
c) The new prices as per quoted future order formula shall become effective only for orders placed after Guarantee Period and up to the life time of all equipment/items and services as per BOQ under this purchase.
d) All parameters of the quoted formulae must be described clearly.
e) The effective unit price for any future order will be the lower one between the contract unit price for this tender and the price calculated on the basis of offered Future Order Formula.
NFV_IGW_Attachment-1&2 Page 26/198
f) Any disagreement/deviation/non-quotation will be treated as “Material Deviation”.
2.32 Project Management Service a) The Contractor shall provide all services related to Turnkey Implementation of all the works related to its contract.
b) The Contractor shall start a project office in Dhaka within two weeks after signing of the contract and such office shall be running till the end of the support period.
c) The office shall be headed by a “Project Manager” for the Contract, who shall have enough authority to represent the Contractor in Bangladesh for all affairs related to the Project and to give decisions regarding routine implementation affairs.
d) For the project works, the Contractor shall dispatch competent engineers during the installation and construction and support service works.
2.33 Additional Equipment needed for Turn-Key Completion For turn-key completion, if the bidder need any or many items which is not included in the BoQ forms, but mandatory for the turn-key completion and essential for installation, proper operation for the completeness and efficient performance of the proposed solution as an operating entity, the same shall be proposed by the bidder (if necessary, the bidder shall specify quantity and quote unit price), then bidder has to quote it in relevant form or form B.10 and C.10. Any claim during BoQ preparation is not accepted if the bidder did not quote any or many items in the relevant form or form B.10 and C.10. Any disagreement or deviation shall be treated as “Material Deviation”
2.34 Assurance of operation of Equipment The bidder shall assure that similar module/cards/unit/server/equipment shall run in similar or equivalent platform at another place without any restriction/blockage or condition. Any disagreement shall be treated as “Critical Deviation”.
NFV_IGW_Attachment-1&2 Page 27/198
2.35 Submission of BOQ of IGW and related Equipment
Besides Form PG4-3A or PG4-3B or PG4-3C, Bidder must submit Summary price and quote with Detail Bill of Quantity (BoQ) of all IGW equipment with ancillary items and related in Form C.x, which will be added and quoted in Form B.x and finally added and quoted in Form A. The forms are provided at the end of Section 7.
Any disagreement/deviation will be treated as “Critical Deviation”. 2.36 Quotation for Optional Items
The bidder shall quote optional item in “Form E1”. If bidder thinks other items may be beneficial for purchaser, those items also may quote in Form E1 but it will not be considered for technical or financial evaluation.
Any disagreement/deviation will be treated as “Major Deviation”. 2.37 Security and Surveillance System for Switch, NOC and OMC rooms The security and surveillance system shall have coverage of entire switch, NOC and OMC rooms. All equipment of Core, data communication, NMS, transmission mux, storage system, command terminals etc. shall be visible within this security and surveillance system. The bidder shall fill up form D.7 of this document. Specifications are mentioned in Clause 13.2.1.10 of Sub-Section 13.
Any disagreement/deviation will be treated as “Major Deviation”.
======End of Sub-Section 2 ======
NFV_IGW_Attachment-1&2 Page 28/198
SUB-SECTION 3
General Requirement of NFV Enabled IP Based IGW
3.1 Introduction The International Gateway (IGW) system should be connected with the IOS at one end and with Overseas Carriers at other end as per conditions of License Guidelines of IGW. The proposed system will allow PSTN/ PLMN/MNP telephone users to make international outgoing call as well as to receive incoming overseas calls. The connectivity with International carriers and IOS shall be through IP or TDM.
3..1.1 The general connectivity requirement is mentioned as shown in figure 8.2 in section 8. NFV enabled IP Based International Gateway components shown in the diagram may differ for different manufactures. If the functionality of one component is integrated with another one, bidder shall explain with necessary documents, how the mentioned capacity of that particular component is obtained.
33.1.2 There shall be installed one Media Gateway– MoghbazarTelephone Exchange, Moghbazar, Dhaka.
3.2 Factors for Dimensioning of Equipment 3.2.1 Mean Holding Time : 60 sec
3.2.2 Average Traffic per Trunk : 0.75 erlang
3.2.3 Average CCS7 Signaling load : 0.2 erlang
3.2.4 Concurrent Calls: 20000
3.2.5 Answer to Seizure Ratio: 25:100
3.2.6 Signaling in Trunks: As per requirements of the signaling stated in following sub- sections
NFV_IGW_Attachment-1&2 Page 29/198
3.2.7 Grade of Service The loss probability in busy-hour shall not exceed the following values at:
Normal load Overload
a) Incoming calls 1.0 % 5.0 %
b) Outgoing calls 0.1 % 3.0 %
3.2.8 Probability of Delay a) Incoming Response
For normal load : Greater than 1.0 sec shall not exceed 1.0 %
For over load : Greater than 1.0 sec shall not exceed 5.0 %
b) Switching Time
For normal load : Greater than 1.0 sec shall not exceed 1.0 %
For over load : Greater than 3.0 sec shall not exceed 5.0 %
3.2.9. System Occupancy a) The average occupancy of any common control equipment, processors and main memory shall not exceed 60% under normal load and 80% under overload condition.
b) The overload condition be defined as follows
i) Traffic in Erlangs : 120% of normal busy hour traffic load
ii) BHCA : 125% of normal busy hour traffic load
3.3 Interconnections of different Modules The bidder shall kindly note that, if for inter-connections of its different modules, there is requirement for additional resources, the quantities of such additional resource elements will be considered as extra to the requirements stated in the relevant quantities of items of the Annexes; and the bidder shall add those extra requirements in the relevant parts of the BoQ.
3.4 Redundant Firewall and Session Border Controller Redundant Firewall and Session Border Controller will be installed to protect Operation support system and Billing support system and other equipment and also to provide secure access/ connectivity for the remote user.
NFV_IGW_Attachment-1&2 Page 30/198
3.5 Network Management System One Network Management system (NMS) shall be installed for the management of the network. Bidder has to provide NMS and CDR Management solution as mentioned in Sub-Section 13 of this document.
3.6 The Connectivity for carrying calls should be of following types a) With the existing IOS node of BTCL/ Other IOS nodes in Bangladesh.
b) With the existing IGW node (ITX) of BTCL.
c) With overseas carriers via Submarine Cable (s), ITC or satellite
d) With the existing MNP nodes of BTCL
3.7 Facilities to be provided at BTRC a) Raw and mediated CDR transfer – Software and hardware at BTCL to push CDR and also to allow BTRC to pull CDR from BTRC end.
b) Necessary software at BTRC for O&M terminal.
c) Other services as per mentioned standards in the IGW License Guideline for Monitoring.
3.8 Facilities to be provided at LEA premise a) Raw and mediated CDR transfer – Software and hardware to push CDR from BTCL and/or pull CDR from LEA end
b) Call information and call content recording facilities as per requirement of National Monitoring Centre (NMC) - Software and hardware at BTCL and LEA end.
c) Other services as per mentioned standards in the IGW License Guideline for Lawful Interception.
3.9 Ensured End to End QoS The proposed network has to ensure end to end QoS to/ from overseas partners from/ to domestic operators. The bidder has to explain in detail about how this will be confirmed in the proposed network.
3.10 Media Interfaces The bidder shall responsible to make the Media interfaces compatible with different types of transmission equipment operating in different media.
NFV_IGW_Attachment-1&2 Page 31/198
3.11 O&M terminals Sufficient numbers of O&M terminals should be provided with licensed software. The hardware requirements shall be as per specifications stated in the following chapter. Bidder may propose for specifications if the specified one is not sufficient for efficient operation and better performance.
3.12 System Reliability The system shall a carrier grade system or equipment which designed for high reliability and overall availability of 99.999%.
=== End of Sub-section 3 ===
NFV_IGW_Attachment-1&2 Page 32/198
SUB-SECTION 4
NFV and Cloud Requirement for IGW
4.1 NFV Requirement 4.1.1 General
Proposed IGW shall be available on cloud environment. The Bidder shall provide their details plan to use the platform for the virtualized networks functions (VNFs). Requirements (but not limited to) are given in this sub- section. Deviation and disagreement of 4.1.1 clause (s) and related sub- clause (s) shall be treated as “Critical Deviation” unless other deviation mentioned.
4.1.1.1 The solution shall be based on open Cloud/NFV technologies and shall comply with open frameworks and standards to guarantee its future growth and assimilation into BTCL‟s IGW systems, e.g. ETSI, OPNFV, OpenStack Foundation, Linux Foundation and open APIs. NFV reference architecture is attached as shown in Figure 8.1 in Section 8.
4.1.1.2 The VNF/NFVI solution (hardware/software) shall run and Operating system shall be certified on OpenStack Linux foundation. The offered hardware should be COTS and shall support integrating 3rd party applications and Cloud OS.
a) Hardware Requirement of COTS Server i) The bidder shall have to submit complete specifications/brochure in details. ii) The hardware shall have expansion capability. A single chassis shall support multiple blades. iii) The hardware blade shall comprise of a series of processors and sufficient memory having capacity 100% more than present requirement. The bidder shall mention present capacity requirement clearly. iv) The hardware shall support at least GE/10GE switching v) The network board on blade shall support at least GE/10GE ports. vi) The bidder shall describe different features of the system to avoid or mitigate the risk of single component failure impacting on service.
NFV_IGW_Attachment-1&2 Page 33/198
vii) The hardware shall support Data Center Bridging (DCB) and shall work in converged network environment. viii) The hardware shall support Fibre Channel over Ethernet (FCoE) converged switching. ix) The compute node of hardware shall support one or more standard PCI card slots. x) The proposed NFV hardware system shall have independent maintenance management interface to avoid external attacks. xi) The blade shall support out of band diagnostics, which can be used to collect hardware failure information without operating system. xii) The bidder shall describe the features of the system used to avoid or mitigate the risk of single component failure impacting on service. b) Cloud OS Requirement i) The bidder shall provide a list of Hypervisors (e.g. VMware, KVM, etc.) which are supported by the Application. ii) The cloud OS shall have watchdog facility to meet telecom services with high reliability. iii) The cloud OS shall support automatic deployment and smooth upgrade capabilities. iv) The bidder shall provide a list of all the optimizations in virtualization layer to guarantee the low latency. v) The Cloud OS O&M module shall support management of physical devices, including servers, storage devices, and switches. Alarms, performance data, and device status information shall be reported in real time. The bidder shall provide screenshots of these functions. vi) The system shall have the ability to act as data center. The computing, storage, network resource will be encapsulated in virtual data center (VDC) environment. Users in VDC shall have the facility to use vCPU, vRAM, vLAN etc. by creating VMs to run their applications. vii) The bidder shall provide a health check tool to maintenance engineers for routine maintenance and generates health check reports for all system components to improve O&M efficiency. viii) The bidder shall submit a list of equipment (Hardware), Software and related services of COTS Equipment according to Form B.3.
NFV_IGW_Attachment-1&2 Page 34/198
4.1.1.3 The NFV platform shall have the following major components (but not limited to):
a) Virtualized Network Function (VNF): A VNF shall be composed of multiple internal components. One VNF can be deployed over one or multiple VMs.
b) Element Management System (EMS): The EMS shall perform the typical management functionality for one or several VNFs.
c) NFV Infrastructure (NFVI): The NFV Infrastructure shall have the totality of all hardware and software components which build up the environment in which VNFs are deployed, managed and executed.
d) Virtualized Infrastructure Manager(s) (VIM): Virtualized infrastructure managers shall perform resource management and shall also be responsible:
i) Inventory of software, computing, and storage and network resources dedicated to NFV infrastructure.
ii) Allocations of virtualization enablers, e.g., compute resources, storage, and relevant network connectivity.
iii) Management of infrastructure resource and allocation, e.g., increase resources to VMs, improve energy efficiency and resource reclamation.
e) Orchestrator: The Orchestrator shall be responsible of the orchestration and management of NFV infrastructure and software resources, and realizing network services on NFVI.
f) VNF Manager(s) (VNFM): A VNF Manager shall be responsible for VNF lifecycle management (e.g. instantiation, update, query, scaling and termination). Multiple VNF Managers may be deployed; a VNF Manager may be deployed for each VNF, or a VNF Manager may serve multiple VNFs.
g) Operations Support Systems (OSS)
The bidder shall follow OSS is described in clause 4.1.10.
4.1.1.4 Bidder shall insure that the VNF can be loaded, executed and moved across
different but standard NFVI points of presence in a multivendor environment.
NFV_IGW_Attachment-1&2 Page 35/198
4.1.1.5 The solution shall be based on Intel‟s X86 processors.
4.1.1.6 The solution shall be managed, provisioned and operated via NFVO.
4.1.1.7 The solution shall target as many of the following focus areas of value that shall be contrasted by the Bidder with traditional technologies.
4.1.1.9.1 Flexibility
a) No vendor lock-ins, e.g. rich/open ecosystem/interoperability b) Explore new innovations with lower risks
4.1.1.9.2 Streamline Operation
a) Maximum automation of provisioning/assurance, e.g. E2E lifecycle service orchestration (LSO) b) Mitigate human error, e.g. self-intelligent day-today operations c) Automatic capacity expansion/reduction, e.g. cloud elasticity
4.1.1.9.3 Care
Self-organizing network/service capabilities, e.g. self-configuration, self- optimization and self-healing functions.
4.1.2 Openness 4.1.2.1 The proposed solution shall be compatible with open-source cloud operating systems (OpenStack) and open-source VIM/MANO projects (OPNFV).
4.1.2.2 The proposed solution shall be fully compatible with KVM virtualization software.
Deviation shall be treated as “Material Deviation”
4.1.3 Performance 4.1.3.1 VNF software shall be properly designed for cloud environments in order to maximize the usage of parallel processing.
4.1.3.2 The proposed solution shall be compatible with carrier-grade clouds and should support hardware acceleration and awareness techniques such as:
a) Hyper Threading and vCPU b) Memory Ballooning c) NUMA 8 d) SR-IOV
NFV_IGW_Attachment-1&2 Page 36/198
4.1.3.3 Bidder shall provide their virtual resource requirements for the solution, e.g. number of VMs, and per VM: vMSS, vSBC, vIP, vCPU, vRAM, vNIC, storage, etc.
4.1.3.4 Bidder shall specify any known degradation in the performance of the VNF running on top of NFV cloud compared to running the solution in a dedicated appliance.
4.1.3.5 Bidder shall specify if the VNF runs with data plane and/or control plane traffic.
4.1.3.6 Bidder shall describe the underlying infrastructure requirements (compute, storage and networking) of the VNF so that it can be sized for a given performance target. If the requirements vary according to the usage or number of occupied IP/TDM ports, the bidder shall provide a table/matrix that describes the resources required for different usages and scenarios.
4.1.3.7 Bidder shall specify the maximum latency or maximum delay variation tolerated to reach the VNF performance target.
4.1.3.8 Bidder shall specify maximum rate of non-intentional packet loss tolerated to reach the VNF performance target.
4.1.3.9 Bidder shall specify maximum rate of non-intentional stable calls or sessions drops that won‟t affect the VNF performance target.
4.1.3.10 All configuration/customizing functions shall be performable online with minimum service outage.
4.1.3.11 Bidder shall specify any special hardware requirements that are essential to meet the performance target.
Any deviation and disagreement shall be treated as “Critical Deviation”
4.1.4 Elasticity 4.1.4.1 Bidder shall describe each component capable of parallel operation minimum and maximum range of instances as well as additional information such as the required compute, packet throughput, storage, memory and cache requirements for each component.
4.1.4.2 VNF shall support on-demand scaling. VNF shall be scaled out or in automatically according its workload, resource usage and policy
NFV_IGW_Attachment-1&2 Page 37/198
4.1.4.3 Ongoing service shall not be interrupted when the VNF is scaling in/scaling out
4.1.4.4 The bidder shall specify the time required (in minutes) of scale out and scale in. The bidder shall also describe the architecture and mechanism of scaling in details.
4.1.4.5 VNF shall be scaled according to service KPI that can be set service KPI policy by GUI. The bidder shall provide a list of supported service KPIs.
Any deviation and disagreement shall be treated as “Critical Deviation”
4.1.5 Fault monitoring and trouble shooting 4.1.5.1 When process error occurs within VM, it shall be restored without service interruption. There shall be an output in details containing information related to process location, cause of fault occurs and fault restoration.
4.1.5.2 When VM error occurs, it shall be restored without service interruption. There shall be an output in details containing information related to VM location, cause of fault occurs and fault restoration.
4.1.5.3 When board/blade/server error occurs, it shall be restored without service interruption. There shall be an output in details containing information related to board/blade /server location, cause of fault occurs and fault restoration.
4.1.5.4 For troubleshooting, the system should have the capability to correlate and filter the alarms and provide sufficient information to find root cause of the fault.
Any deviation shall be considered as “Material Deviation”
4.1.6 Element Management System (EMS) 4.1.6.1 For any VNF instance, the EMS should be able to collect performance related information regarding compute, storage and network resources for any managed VNF instance concerning the resource usage at the infrastructure level.
4.1.6.2 The EMS shall get the performance and service quality metrics from both the infrastructure and the VNFs.
NFV_IGW_Attachment-1&2 Page 38/198
4.1.6.3 The EMS shall report the information e.g. alarm, performance measurement etc. coming from infrastructure to the higher level OSS system (umbrella system) by northbound interface.
4.1.6.4 The virtualization layer alarm sent by EMS to the OSS system shall indicate the necessary information e.g. host name to help operator for fast troubleshooting.
4.1.6.5 The EMS shall support collecting alarm and running status from infrastructure layer and display on it.
4.1.6.6 The EMS shall collect the performance and fault information of CloudOS and COTS of related VNF. EMS shall also perform fault correlation analysis based on VNF fault and CloudOS /COTS fault information. The bidder shall describe the fault correlation mechanism.
Any deviation shall be treated as “Critical Deviation” 4.1.7 VNF Manager (VNFM) Management and Orchestration requirement and different features have been mentioned in Clause 13.5 in Sub-section 13 of this document. Relevant clause is applicable for VNFM. The VNF should be managed by a specific VNF manager that is capable of performing VNF instance life cycle management. Deviations and disagreement in each of the following clause shall be considered as “Major Deviation”:
4.1.7.1 The VNF manager should support automatic scaling based on requirements.
4.1.7.2 The Bidder shall specify the ability of VNFM to interface with multiple VNF implemented with different VIM technologies (i.e. VMware vCloud Director, OpenStack).
4.1.7.3 The Bidder shall specify the ability of the VNFM to interact with 3rd party NFVO and APIs in details.
4.1.7.4 The Bidder shall provide a detailed description of the supported functions by VNFM in each of the phases of the VNF lifecycle (e.g. VNF package on- boarding, VNF instantiation, VNF scale up/down/in/out, VNF termination etc).
4.1.7.5 The VNFM shall have ability to automatically deploy VNFs. The bidder shall describe the detailed procedure for the instantiation.
NFV_IGW_Attachment-1&2 Page 39/198
4.1.7.6 The Bidder shall specify affinity and anti-affinity constraints for the deployment of VNFs and/or VNF components.
4.1.7.7 The VNFM shall support automated and manual horizontal scaling of VNFs (scale in and out, scale up and down).
4.1.7.8 The VNFM shall support automated scaling of VNFs via service KPI. The Bidder shall provide KPI list on the VNF in details.
4.1.7.9 The VNFM shall support automatic backup and restoration capability. The Bidder shall provide procedure in details.
4.1.7.10 The VNFM shall support geo-redundancy, and Bidder shall provide the architecture in details (e.g. working in active-active or active-standby mode, data synchronization mechanism, procedure of failure detection, the expected recovery latency etc.).
4.1.7.11 The VNFM shall have user management and role management functionality.
4.1.7.12 Bidder shall provide software management functionality of VNFM (i.e VNFM can manage installation, verification and updation automatically)
4.1.7.13 The VNF instantiation function shall be able to instantiate two or more VNFs simultaneously.
4.1.7.14 The offered VNFM should support working independently with NFVO and VNFM shall manage the Life cycle of VNF independently.
4.1.7.15 Bidder shall specify the maximum number and con-concurrent number of VNFs that VNFM can manage in large scale scenarios.
4.1.7.16 Bidder shall specify the maximum capacity of VMs that VNFM can manage in large scale scenario.
4.1.7.17 The VNFM shall support system expansion smoothly without service interruption.
4.1.7.18 The VNFM shall support local HA design.
NFV_IGW_Attachment-1&2 Page 40/198
4.1.8 Reliability and Redundancy 4.1.8.1 The Cloud solution shall guarantee the carrier grade 99.999% reliability with high capacity, high resource utilization, scalability, easy operation and maintenance. The bidder shall describe various options, scenarios the architecture and mechanism in details.
4.1.8.2 VNF software shall be in tiers architecture, such as distributed load balance, stateless session processing, and distributed session DB are separated and located in different layers. The bidder shall describe VNF architecture clearly.
4.1.8.3 There shall be no single point failure in hardware level and all modules shall be in N+1 or 1+1 redundancy including computing, server, network and storage.
4.1.8.4 There shall be no single point failure in IaaS software layer.
4.1.8.5 VNF software shall support HA (high availability) independent of the infrastructure layer, which is in Active/Standby redundancy or load balancing, no single failure point, no stable service is lost in software module swapping. The bidder shall describe the architecture and mechanism of software HA in details.
4.1.8.6 VNF shall support POOL disaster recovery. When a site is faulty, services on the faulty site shall switch quickly to related network element VNFs in other normal sites through VNF POOL solution.
4.1.8.7 The Bidder shall be responsible for any apparent or non-apparent degradation caused by the offered equipment, affecting directly or indirectly the performance of any module in the offered System/Equipment (i.e. Hardware, Software, Application, database, and Operating System). The Bidder shall provide a full solution for this degradation and/or maximizing the capacity of the offered System (i.e. Hardware, Software, Application, Database and Operating System), at no additional cost to BTCL within 15 days of the first appearance of the degradation/problem. In solving this problem, the Bidder shall ensure full satisfaction of BTCL.
4.1.8.8 VNF shall support service KPIs monitoring and auto-healing to avoid NFVI Sub-health impacted service. When service KPIs of a module or a VNF falls
NFV_IGW_Attachment-1&2 Page 41/198
below the preset threshold, the system automatically restores the NE service according to the preset restoration policy and reports an alarm. The preset policy includes but is not limited to VM restart, reconstruction, and migration operations in few minutes. The bidder shall describe the mechanism of service KPIs monitoring and auto-healing in details.
4.1.8.9 No service interruption (No KPI and CDR loss) during fault of the disk arrays or when it disconnects with blades.
Any deviation/ disagreement shall be treated as “Material Deviation”.
4.1.9 Security 4.1.9.1 All required security measures and procedures shall be implemented on the offered System Network equipment in order to completely secure user traffic as well as network elements. However these measures shall not degrade the performance of the System /equipment. The Bidder shall provide the required patches/ development on the offered System to correct any vulnerability discovered, at no additional cost to BTCL.
4.1.9.2 Bidder shall offer necessary requirements to protect the whole NFV network as well as isolated network securely.
4.1.9.3 Default or Pre-defined accounts must be disabled or removed from the system.
4.1.9.4 Password protection shall include complexity check, at least 8 characters, against brute force , hide password on screen and Change password while first login.
4.1.9.5 Sensitive data shall be kept in secure storage with strong cryptograph algorithm e.g. AES-256/192/128.
4.1.9.6 Bidder shall offer strengthening Operating system and Database.
4.1.9.7 Remote access management SSH must support public key authentication.
4.1.9.8 Bidder shall protect Software Integrity from tampering.
4.1.9.9 The bidder shall describe management of Security Patches.
4.1.9.10 Bidder shall provide a mechanism to prevent against VNF monopolizing system resources and an assurance that other VNFs would be able to share same resources.
NFV_IGW_Attachment-1&2 Page 42/198
Any deviation and disagreement shall be considered as “Major Deviation”.
4.1.10 Operation Support System a) The Bidder shall describe in full the technical details of the proposed End-to- End OSS requirement and implementation (including different protocols & techniques) which must comply with the latest IT and Telecom standards on different protocol layers, on offered equipment (down to the module/sub- module). b) The offered Platform shall implement mechanisms and procedures (data integration including but not limited to: authentication, authorization, data request and collection and integrity protection) to safeguard the Platform and its users. The bidder shall detail the offered Platform‟s NBI, SBI & API capability. c) The Bidder shall provide detailed traffic flow diagrams with flow descriptions for each communication. d) The bidder shall specify the purposes of all Servers, Application Servers and Database Servers)/node located at different zones/segment. e) All nodes of the offered System shall have latest stable version/release of Operating Systems, patched and updated. f) Data stored in the database shall be encrypted and hashed/comma separated. g) The system shall support North Bound Interface and the South-Bound Interface facility. The bidder shall describe NBI, SBI and API in details.
Any deviation and disagreement shall be considered as “Major Deviation”.
=== End of Sub-section 4 ===
NFV_IGW_Attachment-1&2 Page 43/198
SUB-SECTION 5
Environments and other Requirements
5.1 Climatic Condition 5.1.1 The Bidder shall bear the full responsibility to ensure that the supplied equipment/system/server is capable of operating in Bangladesh environment without degradation. All of the supplied equipment must work satisfactorily under the following environmental conditions.
Table 5.1: Temperature and Humidity
Temperature Relative humidity Working for Working for Working for Working for long term short term long term short term +5 °C to +45°C 0°C to +55°C 5% to 85% 5% to 95%
5.1.2 Bidder shall specify environmental conditions for storage and transportation of equipment.
Deviation from these values shall be considered as “Major Deviation”.
5.2 Radio Emission and Interference The system shall be designed in such a way that the level for emission of radio frequency shall be within limits of relevant ITU-T recommendations. The system shall also be designed to work without any trouble in an environment, where radio interference is within the limits specified in relevant ITU-T recommendations
5.3 Physical Requirement All components of all of the equipment shall be of highest possible quality design and fully tropicalized to be used for continuous operation. The metal surface shall either be galvanized or painted by spray or plated with surface treatment. There shall be no sharp edges or projections. All power equipment and cables shall be protected with fuses of proper ratings. All equipment racks, sub-racks and slots shall be clearly marked in English letters for proper recognition. All equipment racks, sub-racks and slots shall also be provided with proper earthing and shall
NFV_IGW_Attachment-1&2 Page 44/198
be protected against any surge. The deviation shall be considered as “Major Deviation”.
5.4 Operating Voltage All the Media Gateway Controller, Signaling Gateway, Media Gateway, Session Border Controller, Gateway Router, LAN Switch, and Firewall equipment must operate satisfactorily on the nominal voltage of -48V DC and within a voltage range of -40 to -57 Volts DC. Deviation from these values shall be considered as “Material Deviation”. If the NMS server runs by DC power, that will be preferable to BTCL.
5.5 Guarantee for Hardware The Bidder shall guarantee that, the hardware of the system will run without any major technical hazard for at least up to 8(eight) years after the date of issuance of PAC. Deviation shall be considered as “Major Deviation”.
5.6 Guarantee for Software The Bidder shall guarantee that, all the Operating and Application Software of the system will run without any technical hazard for at least up to 8(eight) years after the date of effect of PAC. If any fault and/ or bug are detected within this period, the bidder shall correct these faults and debug the software at his/her own costs and at “free of charge” to BTCL. Bidder‟s refusal to agree to this guarantee shall be considered as “Material Deviation”.
5.7 License for Software License(s) of all the software for all equipment shall be for unlimited time. However, the bidder may propose the licensing renewal process in the bid. If no renewal process is mentioned in the offer, it will be considered that the license of all the software for all equipment is offered for unlimited time. Bidder‟s refusal to agree to this clause shall be considered as “Material Deviation”.
5.8 Language of Software The language of the instructions of the software shall be in English. Deviation shall be considered as “Material Deviation”.
NFV_IGW_Attachment-1&2 Page 45/198
5.9 Guarantee for Introduction of new Features 5.9.1 The bidder shall guarantee that, if BTCL requests for introduction of any new/ additional system features in the supplied system, the bidder shall try its best to do so.
5.9.2 The price for such new/ additional features shall be logical and realistic and shall be fixed up by mutual discussion.
5.10 Guarantee for up-gradation of Software Version 5.10.1 The Bidder shall guarantee that it will inform BTCL of all subsequent up-grades of the software version of the supplied system.
5.10.2 If the upgrade becomes mandatory for any expansion of the supplied system or addition/ modification of any prevalent feature, such software upgrades shall be done "free of charge" to BTCL.
5.10.3 If such upgrade becomes mandatory for proper operation and maintenance of the network in its present configuration and form, such upgrades, including supply of new software and hardware, shall be done "free of charge" to BTCL.
5.10.4 If any non-mandatory upgrade is done on request from BTCL, but does not involve any change or addition in hardware, the bidder, upon request from BTCL, shall install such upgraded software "free of charge" to BTCL.
5.10.5 If any non-mandatory software upgrade, to be done at the request of BTCL, involves any hardware change and/ or additional hardware, charges will be incurred for prices for the changed and/ or additional hardware and the new software. In such cases, the prices for such new and/ or additional hardware and software shall be fixed on mutual agreement and in consistent with the market prices prevalent at the time of such request.
Bidder‟s refusal to agree to the above sub-clauses 5.10.1 to 5.10.5 shall be considered as “Material Deviation”.
5.11 Bidder shall indicate parameters, which may degrade the performance of the offered equipment. Failure to give details such parameters shall be treated as “Major Deviation”.
=== End of Sub-section 5 ===
NFV_IGW_Attachment-1&2 Page 46/198
SUB-SECTION 6
Requirement of Media Gateway Controller and Signalling Functions
6.1 Introduction The Cloud based VNF Media Gateway Controller (MGC) is principally responsible for call control functions according to a call control model, signaling handling and also provides the control of the Media Gateways. The Media Gateway Controller shall handle call control and the spectrum of features offered to the network and to both IP subscribers and TDM subscribers.
6.2 Design Criteria 6.2.1 Media Gateway Controller (MGC) shall have at least (but not limited to) the following essential design elements:
(a) MGC should be highly reliable and highly stable with all the card level redundancy (Active-Standby/Hot-Swappable/Load-Sharing). It should be built around a hardware platform delivering carrier grade service.
(b) The critical components such as main processor board, communication board, power supply, system bus etc., must follow redundant design philosophy, and be able to support insertion / removal of components in „power on‟ condition with no effect impact to Call Server performance. The Bidder has to describe in detail, in his offer, to confirm design redundancy.
(c) The main call processing VM and service processing VM must be provided in 1+1 redundant configuration.
(d) Change-over from main to standby processor should not affect connected calls and calls under processing.
(e) Fast Ethernet ports/Gigabit Ethernet ports must be in redundant configuration.
(f) MGC should support NTP message trace and explanation for the operation and maintenance of the NTP. It is convenient to check the status of the NTP or to determine the cause of the NTP fault.
NFV_IGW_Attachment-1&2 Page 47/198
(g) The MGC should be able to periodic check for board memory to check the memory of all boards periodically. If it detects a reading and writing error in a section of a memory, it sends a fault alarm, along with the location of the board with memory fault, to the background. Software is used to control whether to enable this function.
(h) The MGC should be able to do background noise suppression implemented by the Media Gateway Controller conjunction with the Media Gateway to provide the voice quality enhancement technology to effectively improve quality of voice over the media gateway controller network.
(i) The MGC should the capable for preferential selection of voice codec modes in subscriber/trunk group calls by this function; operator can prefer the most appropriate voice code mode based on the actual needs and the actual situation of the bearer network.
(j) The MGC should have embedded Load Test for IP Bearer which can test whether IP bandwidth is enough for the traffic, especially while introducing a new International Carrier.
(k) The proposed system should have full functionality for Telephone Number Mapping (ENUM). Bidders shall explain in detail this functionality available in the offered system.
(l) The proposed system should have full functionality for Mobile Number Portability (MNP) and shall be compatible with BTCL‟s existing MNP platform. Bidders are requested to visit BTCL present MNP system located at Mohakhali and Moghbazar, Dhaka before submission of the bid. Bidders shall explain in detail this functionality available in the offered system.
Disagree or any deviation to the above sub clauses 6.2.1 (a) to 6.2.1 (l) shall be treated as “Material Deviation”.
6.3 Signaling Protocols (a) As a minimum the MGC shall affect call set-up control using MGCP and ITU-T H.248.1,2,7,12,14,20,23, 24,25,26 signaling to:
i) Media Gateways
ii) Others (bidder has to specify)
NFV_IGW_Attachment-1&2 Page 48/198
(b) The MGC shall provide ISDN signaling using IUA over the packet network to Trunk or Access Gateways supporting connection of ISDN PRI services.
(c) The Bidder shall specify all protocols supported by their solution and shall indicate which standards and/or RFCs (and which versions) their solution complies to.
(d) The MGC should be able to do MNP Query to existing NPDB by using SIP Protocol.
(e) MGC shall be able to affect call set-up and tear down between any of the following network elements:
i) IP phones or VoIP Soft clients with H.323 and SIP protocols
ii) ISUP/SIP Trunks supported on Media Gateways with recommendation of ITU Q.762, Q.763 and Q.764
iii) PRI Trunks supported on Media Gateways
iv) Tones/ announcements recorded on Media Gateways
(f) The MGC shall support, and be compliant to, White Book ITU-T Recommendations E.163 and E.164 addressing schemes.
(g) Proposed Cloud MSS shall have Routing capability based on Codec List, Protocol, LCR routing, HD Voice.
(h) Carrier access code based or dial around calls
Each of the deviation shall be treated as “Major Deviation”.
6.4 Synchronization 6.4.1 External Clock
The MGC shall support external clock synchronization either from dedicated 2 MHz clock signal or from a secondary signal (2 Mb/s). The secondary source shall be at least duplicated.
6.4.2 Clock Accuracy The internal clock used by the system shall be compliant to G.813 ITU-T standards.
NFV_IGW_Attachment-1&2 Page 49/198
6.4.3 Network Time Protocol The MGC should have the capability to keep time synchronization with the NTP server via NTP protocol following the standard IETF, RFC1305.
Each of the deviation shall be treated as “Material Deviation”.
6.5 BHCA Capacity The Bidder must provide the BHCA capacity of individual Voice Processing cards/ VMs on the Media Gateway Controller.
The deviation shall be treated as “Material Deviation”.
6.6 Voice Activity Detection Voice Activity Detection with silence suppression (transmission of silence packets) and insertion of comfort noise at far end support is required. Enhanced Packet Loss Compensation (PLC) algorithm should use to ensure voice quality even when frames are lost.
The deviation shall be treated as “Major Deviation”.
6.7 Final capabilities of the Media Gateway Controller The required capabilities of MGC are mentioned in Annex-1.1. Final capacities shall be achieved by inserting additional relevant cards and “in operation software Up-gradation” Shortage of quantities offered only for the present equipage of each item as in Annex-1.1, shall be treated as “Major Deviation”.
6.8 Protocol Processing Capability Minimum number of supported other side International/National/Local signaling point codes should be 256. The deviation shall be treated as “Material Deviation”.
6.9 Media Resource Service Media Resource Service required to provide the play tone and announcement which should be uniform with the MGC hardware platform.
6.10 Capacity Sharing Initially it is considered that 10% of the total calls would be TDM –TDM and rest 90% would be IP-TDM or TDM-IP calls. Among the IP calls 30% of the total would be H.323 calls and 70% with SIP-I/ SIP-T. The supplier shall provide
NFV_IGW_Attachment-1&2 Page 50/198
functionalities accordingly. Whenever BTCL requests the supplier to change the percentage of calls in a particular protocol the supplier shall arrange the functionality “Free of cost”. The deviation shall be treated as “Major Deviation”.
=== End of Sub-Section 6 ===
NFV_IGW_Attachment-1&2 Page 51/198
SUB-SECTION 7
Requirements of Media Gateway
7.1 Media Gateways (MGW) The Media Gateways act as gateway between the IP network and the TDM (Time Division Multiplexing)-based PSTN/PLMN. MGW shall also act as the bearer device in the integrated gateway exchange and is applicable to the interworking among the next generation network (NGN), IMS, global system for mobile communications (GSM), universal mobile telecommunications system (UMTS), code division multiple access (CDMA), and PSTN networks. The MGW provides the functions such as interworking of voice services, interworking of data services, announcement playing, and digit collecting. They are controlled by the Media Gateway Controller through the H.248, MGCP and/or MEGACO protocol. The MGW shall have the following capabilities:
7.1.1 Architecture The bidder shall provide Media Gateway which is capable to carry IP & TDM traffic.
7.1.2 Scalability The bidder should demonstrate an ability to supply a range of Media Gateways of scalable capacity to meet a range of deployment situations. The range should encompass Trunk gateway sizes from minimum requirement to maximum final requirement for any sites.
7.1.3 TDM Interfaces The Bidder shall clearly specify that the following interfaces are supported by offered MGWs to TDM networks:
Standard channelized STM-1
The deviation shall be treated as “Material Deviation”.
NFV_IGW_Attachment-1&2 Page 52/198
7.1.4 Packet Interfaces The Bidder shall clearly specify that the following interfaces are supported by the offered MGWs:
a) Fast Ethernet
b) Gigabit Ethernet
All packet interfaces have to be configured in 1+1 mode in at least two different cards. Any deviation shall be treated as “Material Deviation”.
7.1.5 Virtual Media Gateway The system shall be capable of creation and operation of virtual Media Gateway.
7.1.6 Signaling a) The MGW shall provide MGCP, H.248 /MEGACO signaling from the MGC to effect voice path connection across the core packet (IP) network. b) The MGW shall provide IUA (ISDN User Adaptation) to carry ISDN channel signaling information from connecting E1 PRI to the MGC. c) The MGW shall provide M2UA, M3UA or other protocols if necessary.
Each of the deviation shall be treated as “Major Deviation”.
7.1.7 Voice Processing 7.1.7.1 MGW shall provide (as a minimum) G.711 A-law, 723.1 and G.729 or G.729a, for the conversion of TDM voice to packet. The Bidder should indicate what packet sizes are supported with which codec and what other codec are supported with what packet sizes. At the same time the bidder should declare the compression techniques to reduce the packet size available in their system and compare the bandwidth requirement for different transport technologies (like FR, Ethernet, PPP etc.). Proposed Cloud MGW shall have capability of Self-Adaptation of G.711/ G.726 packet time.
7.1.7.2 The Bidder must provide the BHCA capacity of individual Voice Processing Cards on the MGW.
7.1.7.3 Echo cancellation meeting G.168 or G.165 standards with a minimum 32ms tail (The Bidders should indicate tail length supported).
NFV_IGW_Attachment-1&2 Page 53/198
7.1.7.4 Voice Activity Detection (VAD) with silence suppression and insertion of comfort noise at far end (e.g. G.729a Annex B).
7.1.7.5 The MGW shall provide Fax tones detection and transmission (T.38).
7.1.7.6 The MGW should be able to deliver tones and announcements to connected TDM trunks under instruction from the SS.
7.1.7.7 The MGW should be able to support IP QoS monitoring on jitter, delay and packet loss.
Each of the deviation shall be treated as “Major Deviation”.
7.1.8 Interface timing/clocking 7.1.8.1 The MGW shall have stable and accurate clock. The stability and accuracy of the clock shall be as follows.
Item Specifications
Minimum frequency Stratum-3 clock: ± 4.6 × 10-6 accuracy
Network Stratum-3 clock: The precision can be Pull-in range access synchronized to ± 4.6 × 10-6. parameters of Maximum the clock Stratum-3 clock: 5 × 10-10 /day frequency offset
Initial maximum Stratum-3 clock: < 2.5 × 10-8 /day frequency offset
7.1.8.2 Interface timing or clocking on MGWs shall have the flexibility to extract clock from external sources.
7.1.8.3 The internal clock used by the system shall be compliant to G.813 ITU-T standards.
NFV_IGW_Attachment-1&2 Page 54/198
Each of the deviation of the above requirements shall be treated as “Major Deviation”.
7.1.9 Reliability 7.1.1: Reliability specifications
Item Specifications
System availability in typical ≥ 99.999% configuration
MTBF ≥ 100000 hours
≤ 0.8 hours (excluding the MTTR preparation time)
Downtime < 5 minutes/year
Restart time < 10 minutes
Each of the deviation of the above requirements shall be treated as “Major Deviation”.
7.1.10 Required Capacity of Media Gateway The required capacity of Media Gateway has been mentioned in Annex-1.2. The Final capacity should be 100% more than that of the specified capacities. Final capacities shall be achieved by inserting additional relevant cards and “in operation software Up-gradation”. Shortage of quantities offered only for the Trunk capacity as in Annex-1.2, shall be treated as “Major Deviation”.
7.1.11 Performance Monitoring The MGW shall offer real time reporting of performance related information.
Any deviation shall be treated as “Major Deviation”.
7.1.11 Video Processing MGW shall provide (as a minimum) H.261, H.263, H.264 video codec to perform video calls from the date of putting the system in commercial service. The Bidder
NFV_IGW_Attachment-1&2 Page 55/198
should indicate what packet sizes are supported with which codec and what other codec are supported with what packet sizes. At the same time the bidder should declare the compression techniques to reduce the packet size available in their system and compare the bandwidth requirement for different transport technologies (like FR, Ethernet, PPP etc.)
=== End of Sub-Section 7 ===
NFV_IGW_Attachment-1&2 Page 56/198
SUB-SECTION 8
Requirements of Gateway Router, LAN Switch, Firewall, Session Border Controller and Intrusion Detection System
8.1 Gateway Router The Gateway Router shall have the following general characteristics and MEF certified. Any deviation shall be treated as “Material Deviation”.
8.1.1 Connectivity a) The Gateway Router shall support Packet over Synchronous Optical Network (POS), ATM, Gigabit/Fast Ethernet, and Channelized STM-1 interface types. The router shall support different interface speeds such as STM-1, STM-4, STM- 16 and STM-64. The router shall support different LAN Interfaces such as FE, GE and 10GE. Channelized STM-1 card should support DS3.
b) All the interface mentioned above should be supported in the same chassis offered in the bid
8.1.2 Management The management of the Router shall support the following:
a) Command Line Interface (CLI)
b) Extensive Simple Network Management protocol (SNMP) support including the Service Assurance Agent
8.1.3 General IP Features The Router shall be able to support the following general IP features. Any deviation shall be treated as “Major Deviation”.
a) Internet Protocol- RFC 791
b) Internet Control Message Protocol (ICMP) – RFC 792
c) IP Multicast
i) Internet Group Management Protocol (IGMP) – RFC 1112
ii) PIM dense mode, PIM sparse mode iii) Multicasting BGP (MBGP)
NFV_IGW_Attachment-1&2 Page 57/198
d) User Datagram Protocol (UDP) – RFC 768
e) Transmission Control Protocol (TCP) – RFC 793
f) Requirements for IPv4 Routers – RFC 1812
g) Telnet Protocol Specification – RFC 854
h) Network Timing Protocol (NTP) – RFC 1305
i) DHCP
8.1.4 Protocols The Gateway Router shall support the following protocols from the day one. Any deviation shall be treated as “Material Deviation”.
a) PPP
b) HDLC
c) Frame Relay
d) Multi-link PPP
e) Link Bundling for high speed links
f) Equal load sharing on all high speed links
g) support VPLS in accordance with Kompella and Martini mode
h) Network Address Translation
i) IP header Compression
j) Compressed RTP (cRTP)
k) GRE VPN
8.1.5 Routing The router shall support wire-speed packet forwarding for all packet sizes across all interfaces simultaneously. The routing features shall include the following. Any deviation shall be treated as “Major Deviation”.
a) Static Routing
b) BGP Features support - Route Target, Site of Origin, Route Refresh, ASN 1 Override, Outbound Route Filters (ORF), VPNv4 routes filtering based on route target, Inter-AS MPLS VPN model, and BGP route reflector functionality.
NFV_IGW_Attachment-1&2 Page 58/198
The other BGP Features to be supported are:
i) RFC1771 and 1772, BGPv4 ii) RFC1997, BGP Communities Attribute iii) RFC 2270: Using a Dedicated AS for Sites Homed to a Single Provider. iv) RFC 2385: Protection of BGP Session via the TCP MD5 Signature Option. v) RFC 2439, BGP Route Flap Damping vi) RFC 2796, BGP Route Reflection – An Alternative to Full Mesh IBGP vii) RFC 2918, Route Refresh Capability for BGP-4 viii) RFC 3065, Autonomous System Confederations for BGP ix) RFC 3107, Carrying Label Information in BGP-4 x) BGP Extended Communities Attribute xi) BGP4 Multi path support to enable load balancing between multiple exterior BGP peers from the same downstream router. xii) Exterior BGP multi-hop support-to-support load balancing between two EBGP peers connected by two or more links. xiii) Prefix List tracking and Control to enable network administrators to control peering requirements with exterior BGP peers. xiv) Policy Routing to enable flexibility in making changes to the normal routing process based on the characteristics of the traffic. xv) The router shall support minimum of 500 BGP peering and 800,000 IP routes c) The router shall support following OSPF protocol features:
i) OSPF V2 as per RFC 2328 ii) RFC1403, BGP-OSPF interaction iii) OSPF Not So Stubby Area (NSSA) RFC 3101 iv) RFC1850, OSPFv2 MIB v) RFC2370, Opaque LSA option vi) RFC 2740, OSPF for IPv6 vii) OSPF Stub Area viii) Traffic Engineering (TE) extensions to OSPF v2 (OSPF-TE) as per RFC 3630. ix) OSPF graceful restart
d) RIPv1 and RIPv2
e) IS-IS
NFV_IGW_Attachment-1&2 Page 59/198
f) MPLS
8.1.6 MPLS/VPN Features The router shall support the following MPLS/VPN features. Any deviation shall be treated as “Major Deviation”.
i) MPLS RFC 2547bis MPLS L3 VPN ii) MPLS E-LSP and MPLS Fast Re-Route iii) MPLS L2 VPN (Ethernet, VLAN, FR, PPP, HDLC, ATM over MPLS) iv) The router shall support 1000 VRF v) Scheduling/ queuing for 8 classes that provide configurable minimum bandwidth allocation to each class, based on 802.1p and IP TOS bits. vi) Mapping of 802.1p and IP TOS bits into MPLS EXP bits. vii) The router shall support mapping of 802.1q VLAN tags into MPLS labels. viii) RFC 3031, Multi-protocol Label Switching Architecture ix) RFC 3032, MPLS Label Stack Encoding x) LDP specification as per RFC 3036. xi) RFC 3270, Multi-Protocol Label Switching (MPLS) Support of Differentiated Services xii) RFC 3443, Time To Live (TTL) Processing in Multi-Protocol Label Switching (MPLS) Networks xiii) RFC 3469, Framework for Multi-Protocol Label Switching (MPLS)-based Recovery xiv) RFC 3564, Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering xv) ICMP Extensions for Multi-protocol Label Switching xvi) Dynamic MPLS LSP setup with signaling protocol shall be supported on all the router interfaces. xvii) Shall support LSP path optimization. When new LSPs are added, LSP re- optimization allows rerouting LSPs to follow a lower cost path with no data loss to existing traffic. xviii) The router shall support LSP Ping, LSP Trace route and L2VPN OAM functionalities.
NFV_IGW_Attachment-1&2 Page 60/198
8.1.7 Essential Features to support QoS An essential feature for Router is to support differentiated Quality of Service (QoS) for IP packets. The router must be able to deliver the following IP QoS to allow service providers to offer differentiated IP service plans to their subscribers. Any deviation shall be treated as “Major Deviation”.
i) Simple traffic classification (DSCP or TOS bits). The router shall support Low latency-Low Jitter for VOIP Class of service in addition to Assured Services and Best effort services. ii) Traffic Control iii) Traffic shaping iv) Congestion control based on Weighted Fair Queuing v) Congestion avoidance based on RED and Weighted RED vi) Support of DiffServ vii) Wire-speed complex traffic classification, hardware-based implementation viii) Hardware-based implementation of QOS, not affecting the forwarding performance ix) The router shall support SLA probes to monitor the packet loss, Jitter, latency parameter with Tier-1 Peering ISPs and also the downstream service providers and corporate customers. The frequency of checking and number of packets are configurable. The SLA parameter is able to collect by SNMP MIBs by the central performance Management software.
8.1.8 Other High Availability Feature Support required from day 1 a) Virtual Router Redundancy Protocol (VRRP)
b) Bi directional Failure Detection (BFD)
c) Graceful Restart and Non Stop forwarding for BGP, OSPF, ISIS
d) State-full switchover
e) 50ms switchover in case of node failure on an IP forwarding network.
Any deviation shall be treated as “Major Deviation”.
8.1.9 Security Features The Router shall provide the following security features. Any deviation shall be treated as “Major Deviation”.
NFV_IGW_Attachment-1&2 Page 61/198
8.1.9.1 Equipment Security
a) Ensuring hierarchical user authorities, preventing unauthorized configuration of equipment
b) Providing SSH, ensuring security for administrator accounts
c) Supporting the application of complex ACL policies on host ports, preventing illegal access to the equipment
d) Supporting host firewall, preventing various attacks originated by users.
8.1.9.2 Protocol Security
a) Supporting plain text authentication and MD5 authentication for common routing protocols, avoiding importing invalid routing information
b) Supporting SNMP V3
8.1.9.3 Security Auditing
a) Providing various security-related statistic information and system logs
b) Flow-based filtration
c) Flow-based redirection
d) Flow-based sampling
8.1.9.4 Hardware configuration and Performance Requirement
The Router shall have the following capabilities. Any deviation shall be treated as “Material Deviation”.
a) The Switching capacity shall be not less than 160Gbps full duplex (320 Gbps half duplex).
b) The Router shall support the forwarding rate of minimum of 150 million packet per second.
c) The router shall forward the packet on Line-rate on all the interfaces.
d) The router shall have at least 2 redundant DC power supply (-48V).
e) All interface modules shall support hot swapping.
f) Loss of the management link to the Network Management System must not affect the normal operation of the Router.
NFV_IGW_Attachment-1&2 Page 62/198
g) Ready for IPv6
h) The Router Processor shall be supplied with minimum of 2 GByte RAM and 512 MByte Flash memory expandable to 4 GByte RAM and 1 GByte Flash memory.
i) The processing and interface capabilities of the router should be able to be upgraded to the final capacity mentioned in the relevant clause with the same chassis offered in the bid.
j) The channelized STM-1 module shall support n*64kbps, E1 framing format .The channelized STM-1shall support DS3 framing also.
k) The router shall be supplied with 1+1 hot-standby redundancy of Control and Switch module. Failure of one Switch module shall not lead to:
i) Degradation in the performance of router.
ii) Degradation in any service levels.
iii) Reduction in switching capacity.
8.1.10 Required interface capacities The required interface capacities are mentioned in Annex-1.3. Final capacities shall be achieved by inserting additional interface cards/units and “in operation software Up-gradation”. Shortage of quantities of each interface offered in Annex- 1.3 shall be treated as “Major Deviation”.
8.2 LAN Switches There shall be two core LAN switches at Moghbazar site. Specifications for core LAN switches are described in the Clauses 8.2.1 to 8.2.7. Two more LAN switch shall be supplied. One is for CDR Management/ storage system and another one is for CDR and other data transfer to LEA/ BTRC. Clauses 8.2.8.x describe the specifications for these LAN switches. All the LAN Switches shall be MEF certified.
Any deviation shall be treated as “Material Deviation”.
8.2.1 General Features The LAN switch shall support the following general features. Any deviation shall be treated as “Major Deviation”.
a) Spanning Tree Protocol (IEEE 802.1d)
NFV_IGW_Attachment-1&2 Page 63/198
b) Rapid Spanning Tree Protocol (RSTP) (IEEE 802.1w)
c) Logical Link Control (IEEE 802.2)
d) Flow control (IEEE 802.3x)
e) TFTP (RFC 783), Telnet (RFC 854) f) it shall support Jumbo Frames
f) SNMP v1/v2/v3
g) Support for 802.1x
h) Multicast IGMP v2 snooping as per RFC 2236
i) Multicast group and source port filters
j) Rate limiting per port
k) Traffic Shaping per port
8.2.2 Network Protocol Feature The Core LAN switch shall support the following network protocol features. Any deviation shall be treated as “Major Deviation”.
a) All ports shall work on either half or Full duplex. The System shall support manual or auto negotiation feature for defining the half or Full Duplex mode of operation.
b) Shall generate Syslog and SNMP trap for all the events.
8.2.3 VLAN Features The Core LAN switch shall support the following VLAN features. Any deviation shall be treated as “Major Deviation”.
a) IEEE 802.1Q tagging and 802.1p traffic priority
b) IEEE 802.1w VLAN RSTP and IEEE 802.1s
c) VLAN shall be possible to be created among ports of different types
d) 4K VLANs (as per IEEE 802.1Q) shall be supported
e) Shall allow MAC/IP Address bound to a port/VLAN.
8.2.4 Routing Feature The Core LAN switch shall support the following routing features. Any deviation shall be treated as “Major Deviation”.
a) Static Route and Default Route
NFV_IGW_Attachment-1&2 Page 64/198
b) Open Shortest Path First (OSPF)
c) RIP version-1 and 2
d) Intermediate System- Intermediate System (IS-IS)
e) Border Gateway Protocol (BGP)
f) Multicast Features
g) Internet Group Management Protocol (IGMP) Snooping Version-1, Version-2 and Version-3 shall be supported.
h) Protocol Independent Multicast-Sparse Mode (PIM-SM) .
8.2.5 Security Features The Core LAN switch shall support the following security features. Any deviation shall be treated as “Major Deviation”.
a) Hierarchical management over the users and password protection
b) Supports the supplicant authentication compliant with IEEE 802.1x protocol
c) Support local and remote authentication dial-in user service (RADIUS) Authentication, Authorization and Accounting (AAA) schemes.
d) Supports only port based packet filtering
e) Support the simple text authentication and MD5 encrypted text authentication for routing protocols.
f) Support SNMP v3 encrypted authentication
g) Terminal Access User Security mechanism
h) Packet filter
i) The switch should supports identification authentication over the supplicants with standard Radius Server or local identification authentication.
j) Secured Shell (SSH)
8.2.6 Hardware Configuration and Performance Requirement The Core LAN switch shall support the following capacity and configuration features. Any deviation shall be treated as “Material Deviation”.
a) The switch shall support minimum of 30000 MAC address
NFV_IGW_Attachment-1&2 Page 65/198
b) The switch shall support minimum of 200 Gbps switching capacity and 100 million packets per second forwarding performance. The switch shall be supplied with 1+1 hot-standby redundant control and switching. Module and 1+1 hot- standby redundant DC (-48V) power supply modules.
c) The switch shall be supplied with minimum of 256 MB RAM and 32 MB Flash memory
d) The processing and interface capabilities of the switch should be able to be upgraded to the final capacity which is 100% more than that of the present requirement. Present capacities mentioned in the relevant clause(s) and Annex- 1.4 with the same chassis offered in the bid.
8.2.7 Required Interface Capacities of Switches The interface capacities of LAN switches are mentioned in Annex-1.4. Final capacities shall be achieved by inserting additional relevant cards/units and “in operation software up-gradation” Shortage of quantities only for the present offered capacities of each category of interface for each site as in Annex-1.4, shall be treated as “Major Deviation”.
8.2.8 LAN switches to connect PCs/Servers of CDR management/Storage system Specification for the LAN switches to be used to connect PCs/Servers of CDR management/Storage system and LEA/ BTRC CDR Transfer system. Two separate switches are needed.
8.2.8.1 General Features
a) Shall be located at Moghbazar Site b) Scalable and secure network management c) Network security through a wide range of authentication methods and data encryption technologies d) Network Admission Control based on users, ports, and MAC addresses e) Easy network configuration, Software updates, and troubleshooting f) QoS for traffic classification and shaping to prioritize various applications g) Single IP address, Syslog, and Simple Network Management Protocol (SNMP) h) Enhanced troubleshooting for link connectivity problems and cable diagnostics i) QoS and support for multicast services.
NFV_IGW_Attachment-1&2 Page 66/198
8.2.8.2 Security Features
a) Support of Identity Based Network Services (IBNS) in order to provide authentication, access control and security policy administration to secure network connectivity and resources. b) Support of 802.1x authentication standard to allow users to be assigned a VLAN upon authentication regardless of their connectivity to network which permits user mobility all over the network without any administrative overhead. c) Allow ACLs to be used to restrict access to sensitive portions of the network by denying packets based on source and destination MAC addresses, IP addresses, or TCP/User Datagram Protocol (UDP) ports in order to prevent DoS and other attacks. ACL lookups to be performed in hardware for forwarding performance not to be compromised when implementing ACL- based security. d) Support of DHCP snooping and IP source guard to prevent DHCP spoofing from non-trusted users e) Use of Port-Security feature to limit access on an Ethernet port based on the MAC address of the device. Prevention of MAC flooding attack by limiting total number of devices plugged into a switched port. f) Support of SSH version 2 and SNMP version 3 in order to encrypt network- management and administrative information g) Support of RADIUS authentication support h) Support of Different Levels of Authorization.
8.2.8.3 Quality of Services
a) Auto-Detection of IP Phones for automatic classification of Voice Traffic and egress queuing b) Switches should offer QoS features to ensure that network traffic is classified and prioritized and that congestion is avoided in the best possible manner. To implement QoS, the Switches should first identify traffic flows or packet groups, and then classify or reclassify these groups using the DSCP or 802.1p Class of Service (CoS) field. c) Switches should support more than two egress queues per port, to provide more control in assigning priorities for the various applications on the LAN. At egress, the switches should perform congestion control and scheduling,
NFV_IGW_Attachment-1&2 Page 67/198
the algorithm or process that determines the order in which queues are processed. d) Allocation of bandwidth based on Committed Information Rate (CIR) on a per port basis. Bandwidth should be allocated based on several criteria, including MAC source address, MAC destination address, IP source address, IP destination address, and TCP or UDP port number.
8.2.8.4 VLAN Features
a) Support of VLAN and 802.1q trunking protocol b) Support of 4,096 VLAN IDs c) Support of Up to 255 VLANs per switch d) Support of VLAN configuration distribution among different switches in the same domain
8.2.8.5 Additional Features
a) DHCP auto-configuration of multiple switches through a boot server which eases switch deployment.
b) Auto-sensing on each 10/100 port detects the speed of the attached device and automatically configures the port for 10 or 100 Mbps operation, easing switch deployment in mixed 10 and 100Mbps environments.
c) Auto-negotiating on all ports automatically selects half or full-duplex transmission mode to optimize bandwidth.
d) Dynamic Trunking Protocol (DTP) to help enable dynamic trunk configuration across all switch ports.
e) Port Aggregation Protocol (PAgP) to automate the creation of Fast Ether Channel groups or Gigabit Ether Channel groups to link to another switch, router, or server.
f) Link Aggregation Control Protocol (LACP) to allow the creation of Ethernet channeling with devices that conform to IEEE 802.3ad.
g) DHCP Server to enable a convenient deployment option for the assignment of IP addresses in networks that do not have a dedicated DHCP server.
h) Relaying DHCP Broadcast requests to the network DHCP server.
i) Support of SFP based 1000BASE-SX and 1000BASE-LX physical interface.
NFV_IGW_Attachment-1&2 Page 68/198
j) Automatic Medium-Dependent Interface Crossover (Auto-MDIX)
k) Unidirectional Link Detection(UDLD) Protocol support
l) Configuration rollback to provide the capability to replace the current running configuration with any saved Operating System Software configuration file.
m) DHCP auto install (Boot Host DHCP) and auto image update to allow the switch to download a configuration file and Operating System Software image automatically.
8.2.8.6 Hardware Configuration and Performance Requirement
The switch shall support the following capacity and configuration features.
a) The switch shall support minimum of 8,000 MAC address
b) The switch shall support minimum of 16 Gbps full duplex of switch capacity and 35 million packets per second forwarding performance based on 64 byte packet size
c) At least 40 Ethernet 10/100 and 4 GE optical (3SX+ 1 LX) port
d) The switch shall be supplied with minimum of 64 MB RAM and 32 MB Flash memory
8.3 Firewall 8.3.1 The Bidder has to support firewall to protect the NMS, BSS and other network elements and should also provide secure access/ connectivity for the remote users. The firewall shall be supplied with 1+1 redundancy to avoid single point of failure. The initial capacity of Firewall is given in Annex-1.5.
The firewall shall support the following features. Any deviation shall be treated as “Material Deviation”.
a) The firewall should protect the NMS and BSS network and also provides secure access/connectivity for the remote users. b) The Firewall shall protect systems from virus, worm, spyware, spam and possible other threats. The system should have dynamic intrusion detection and prevention capability. c) The firewall shall support IPSEC. d) The firewall shall support SSL in addition to IPSEC based VPN.
NFV_IGW_Attachment-1&2 Page 69/198
e) The system shall provide Failover Port connectivity between Primary and Secondary Firewall f) The system shall support DC Power Supply g) The firewall shall support robust stateful inspection firewall services h) The firewall shall support 802.1q-based VLAN support on the LAN Ports. i) The system shall provide flexible access-control capabilities for more applications, services, and protocols, with the ability to define custom applications and services. j) The firewall shall Support inbound/outbound ACLs for interfaces, time-based ACLs, and per-user/per-group policies. k) The firewall Appliance shall support in a secure Layer 2 bridging mode, providing rich Layer 2-7 firewall security l) The system should support AAA services via RADIUS, with support for redundant servers for increased AAA services resiliency m) The Bidder shall provide unlimited license for the VPN Client over Windows 98, ME, NT, 2000, XP, Sun Solaris; Intel-based Linux distributions for remote management and access requirement. n) Should Support OSPF dynamic routing o) The Firewall shall supports load balancing across equal-cost multipath routes p) The firewall shall also support native IPv6 network environments and applications. q) The firewall shall support SSHv2, telnet, HTTP/HTTPS, and ICMP-based management. r) The system support dynamic, static, and policy-based NAT, and PAT services s) The system shall support SNMP MIB for VPN flow statistics including tunnel uptime, bytes/packets transferred, etc. t) The system shall support H.323 NAT Traversal
8.3.2 The required capabilities are mentioned in Annex-1.5. Final capacities shall be achieved by inserting additional cards/units and “in operation software up- gradation”. Shortage of quantities offered only for the present capabilities of each item as in Annex-1.5, shall be treated as “Major Deviation”.
8.4 Session Border Controller (SBC) 8.4.1 Border Security Solution shall combine the ETSI TISAPN Border Gateway Function with the sophisticated Session Border Controller and firewall elements
NFV_IGW_Attachment-1&2 Page 70/198
of the Network Border Switch. It may provide services for the Signaling plane, the media plane, or combine these into a single package. The system shall have following features. Any deviation shall be treated as “Major Deviation”.
8.4.1.1 The SBC shall have 1+1 redundancy in the normal time. The change over on failure shall be smooth and should not be traffic affecting.
The Session Border Controller should support the following security features:
a) Split DMZ b) Bandwidth and QoS theft protection c) Session-aware firewall d) Topology-hiding e) Traffic policy f) DoS and DDoS detection and blocking g) Rogue RTP Protection h) SDTP authentication and confidentially i) TLS signaling authentication j) HTTPS/SSH management k) Smart Header Manipulation l) Service wise overload control
8.4.1.3 The SBC shall support following Codecs:
a) G.711 A-Law/ µ-Law b) G.723.1 5.3/6.3 kbps c) G.723.1 Annex A- (Silent suppression) d) G.729 A, B, AB e) IMS TISPAN A-BGF/C-BGF with H.248 Support f) Codec Relay/Pass through
i) Video/Multimedia
ii) EVRC, EVRC-B
iii) AMR, AMR-WB
g) G.711/G.7xx transcoding h) EURC i) ILBC j) T.38
NFV_IGW_Attachment-1&2 Page 71/198
8.4.1.4 The SBC shall provide transcoding capability, supporting transcoding between all supported codec and packet size combinations.
8.4.1.5 The SBC shall support multiple protocols as follows: a) SIP ( I / T ) b) H.323 c) H.248 d) MGCP
8.4.1.6 The SBC shall support
a) GE/FE interface to packet-based network
b) At least 800M bit/s throughput.
c) At least 2 GE.
d) IPv4 and IPv6 interworking
e) Detecting and analyzing various intrusion, like Worm detection, Protocol
decoding, Log storm handling, Protocol filtering and misreporting handling etc.
8.4.1.7 The SBC shall allow dynamic switching of vocoders during mid-call or on a call- by-call basis. This will allow the VoIP system to respond to available bandwidth conditions in real time.
8.4.1.8 The system shall preferably support mechanisms such as piggyback, where different voice information to the same destination is multiplexed into a single packet. This ensures that the header overheads are significantly reduced.
8.4.1.9 The SBC shall support Voice Activity detection (VAD), with silence suppression and Comfort Noise Generation (CNG).
8.4.2 The Session Border Controller (SBC) shall be able to handle 20,000 Concurrent calls from the Day 1 of operation. Any deviation shall be treated as “Material Deviation”.
8.4.3 The Session Border Controller shall be able to support system logs:
a) Packet loss event b) Abnormal traffic event c) System configuration change event
NFV_IGW_Attachment-1&2 Page 72/198
8.4.4 If there are any limitations of configuring number of trusted IP addresses, bidder shall specify the limitations. The system shall support more than 250 addresses. Initially 70% of which is SIP-I/T and 30% is H.323. If during operation, it is found that the mix of IP trunk is different from above, the bidder has to adopt that mix without any charge. Any deviation shall be treated as “Material Deviation”.
8.4.5 The SBC should be able to be monitored by the unified NMS with the IGW.
8.4.6 The final capacity shall be 100% more than that of the present capacity. Final capacities shall be achieved by inserting additional cards/ units and “in operation software up-gradation”. Shortage of quantities offered only for the present capabilities as in 8.4.2, shall be treated as “Major Deviation”.
8.5 Intrusion Detection System (IDS)
Bidder has to offer equipment to detect and protect the Network from any intrusion. The capacity of the IDS has to be determined and proposed by the Bidder so that the offered equipment is capable of protecting the proposed network with final capacity. Any deviation shall be treated as “Material Deviation”.
8.5 The required capacities of SBC are mentioned in Annex-1.6.
=== End of Sub-Section 8 ===
NFV_IGW_Attachment-1&2 Page 73/198
SUB-SECTION 9
Requirements of the Charging Facilities
9.1 Introduction The proposed Media gateway controller shall perform the charging of the voice traffic (for all types of calls) passed through each of the IP/TDM circuit in any or all circuit groups of Trunk Gateways. The charging shall be based on Call Detailed Records (CDR). The system shall provide complete and comprehensive software and hardware facilities for supporting Charging and Accounting functions.
9.2 Call Detailed Recording (CDR) facility 9.2.1 The System must be capable of recording detail data of all completed calls (both incoming and outgoing) for each of the circuit in any or all circuit groups. The following data (but not limited to) shall be recorded and any deviation shall be treated as “Major Deviation”. Absence of this CDR facility shall be treated as “Material Deviation”.
a) Node (MGW) Identity
b) Record Number
c) Circuit Group Identity by name and/or number
d) Calling party's National Number
e) Calling party type
f) Re-directing subscriber‟s National Number
g) Original Calling party‟s number
h) Called party's Number (all of the digits dialed)
i) Called party type
j) Charging Status of the call (Chargeable or Non-chargeable)
k) Traffic Type
l) Date of call connection and disconnection
NFV_IGW_Attachment-1&2 Page 74/198
m) Time of call connection and disconnection
n) Chargeable Duration of the call
o) Number of meter pulses
p) Length indicator of A and B Party
q) Transit/ reroute indicator
r) Conference indicator
s) Cause for output
t) Origination point code (TDM calls)
u) Destination point code (TDM calls)
v) Origination IP (SIP calls)
w) Destination IP (SIP calls)
x) Type of seizure
y) Cause for output
z) Abnormal Call release indicator
aa) Currency factor
bb) Price of the call
cc) Incoming Route Identifier
dd) Outgoing Route Identifier
9.2.2 Activation of the above records shall not be by default for any circuit or circuit group. The system shall have the capability to activate or deactivate any of the above recording in any circuit and/ or circuit group by commands. Deviation shall be treated as “Minor Deviation”.
9.2.3 The language of these records shall be English. Deviation shall be treated as “Material Deviation”.
9.2.4 The records will be continually saved in the central storage device (Hard Disk) by the system in a pre-fixed regular period and sequence. Sufficient buffer space shall be reserved in the Hard Disk for saving at least 20,000,000 of such individual records. Negative deviation of this value up to 50% shall be treated as
NFV_IGW_Attachment-1&2 Page 75/198
“Minor Deviation”, negative deviation above 50% shall be treated as “Major Deviation” and absence of such buffer shall be treated as "Material Deviation".
The system shall be configured to generate a "major alarm" when 80% of such buffer has been filled. Deviation shall be treated as “Major Deviation” but the absence of such alarm facility shall be treated as "Material Deviation"
9.2.5 The records will be specially protected (from erasure or corruption) against system shutdown, power failure, electro-magnetic interference, electrical and lightning surges, fault conditions, illegal access and wrong commands. At the same time the system must follow redundant design philosophy. The Bidder has to describe in detail, in his/her offer, to confirm design redundancy. Deviation shall be treated as “Material Deviation”.
9.2.6 Facilities shall be provided to dump the contents (up to any or many number of records) of such records anytime to the back-up devices by command. Such dump may be titled as "Circuit CDR Dump". Multiple dumping of the same records shall be allowed. Absence of dumping facility shall be treated as “Material Deviation”. 9.2.7 There should be automatic dumping facility using FTP or any other suitable protocol to pull the records from the Billing Centre, Law enforcement Agencies and BTRC facilities as per IGW License guidelines. Storage of dumping server shall have minimum capacity to store 1 year raw data of CDR. Storage shall have SSD type disk and shall support RAID. Connectivity of Storage Server shall be as shown in Figure 8.3. Absence of such dumping facility shall be treated as “Material Deviation”.
9.2.8 After confirmation of the completion of such dump, all the dumped records are to be automatically deleted from the storage devices (Hard Disks) in order to create space for new entries. Deviation shall be treated as “Major Deviation”.
9.2.9 The bidder shall also provide Windows-based software in any of the Control Console for reading and/or de-coding (if required) of the Circuit CDR Dump and printing outputs (for any, many or all circuits/ circuit groups) in tabular formats. Failure to provide such facility shall be treated as “Material Deviation”.
9.2.10 The Bidder, in its technical proposal, will give detail of its standard format of the Call Data Record (CDR) dump in the CD and will also provide sample printout of
NFV_IGW_Attachment-1&2 Page 76/198
such data. Failure to provide the format or printout shall be treated as “Major Deviation”.
9.3 Content based routing and Charging The system should support content based routing and Charging. Failure to provide such facility shall be treated as “Major Deviation”.
9.4 Interconnect Charging a) The purpose of the Interconnect Charging function shall be to provide an Operator with data in order to enable the settlement of accounts between operators. The function shall comprise national and international accounting. The function shall provide the possibility of generating a detailed output (CDR) or a bulk output (number of answered calls, duration and number of charge units). It shall be possible to perform accounting at the outgoing side, the incoming side, or both sides for a call. For routes that are treated in the same way from an accounting point of view, it shall be possible to define types, and to group them in an arbitrary way. b) It shall be possible to define “accounting classes”, for the collection of different types of accounting data, separate for incoming and for outgoing accounting. Data shall be recorded per accounting class. Accounting data shall be recorded on counters. The capacity of the counters, number of calls, conversation time and number of charge units, shall be stated. The counters shall not be reset at output of data. It shall also be possible to have accounting on the received and/or sent charge units on a per accounting class basis, that is, an accounting class shall collect either generated and received charge units, or only received charge units. The recording of conversation time and number of charge units shall commence at B-answer and terminate at disconnection of the call. Failure to provide such facility shall be treated as “Major Deviation”.
9.10 Ability to Store Failed CDR The system shall have ability to store failed calls detailed records (CDR) for every incoming/outgoing calls to/from any destination for operation, maintenance and fault diagnosis purpose. This CDR would be stored on the system storage for at least 15 days. After the specific period the CDRs would be removed from the system storage automatically or manually. Failed CDR shall be Stored in readable format. It is necessary to have online or offline decoders to translate
NFV_IGW_Attachment-1&2 Page 77/198
stored data into intelligible formats (in English) for proper understanding. Any disagreement or deviation shall be treated as “Critical Deviation”.
=== End of Sub-Section 9 ===
NFV_IGW_Attachment-1&2 Page 78/198
SUB-SECTION 10
Requirements of the Signaling, Protocols and Interfaces
The system shall support the following related protocols/signaling and interfaces for the PSTN/PLMN connectivity and Protocols for NFV system.
10.1 Inter-Node Signaling The following inter-node signaling capabilities shall be provided in the system. Absence and deviation (both) shall be considered as “Material Deviation”.
10.1.1 Common Channel Signaling No. 7 (CCS7)
The CCS7 Signaling shall be based on ITU-T White Book or later version of recommendations. Moreover, it shall be backward compatible with Blue Book variants prevailing in Bangladesh. The prospective Bidder shall make his own survey about versions or sub-sets used, if any, in BTCL.
10.1.2 ISDN PRA Signaling
The system shall support full version of ISDN Primary Rate Access (PRA) Signaling on ITU-T E1 as per ITU-T recommendation.
10.2 NGN Protocol The system must support the following protocols:
10.2.1 H.248/ MEGACO protocol for communication between Media Gateway Controller and Gateways, according to the following standards:
a) ITU-T H.248 Gateway Control Protocol (identical to IETF RFC3015 updated with RFC3525 : MEGACO Protocol)
b) RFC2327 : Session Description Protocol (SDP)
Any deviation shall be considered as “Material Deviation”
10.2.2 SIP-I protocol for interworking with other Media Gateway Controller, according to the following standard:
a) ITU-T Recommendation Q.1912.5
Any deviation shall be considered as “Material Deviation”
NFV_IGW_Attachment-1&2 Page 79/198
10.2.3 SIP protocol for the control of the residential gateways, according to the following standards:
a) IETF Recommendation RFC 3261
b) IETF Recommendation RFC 3262
Any deviation shall be considered as “Material Deviation”
10.2.4 SS7 over IP based on SCTP (SIGTRAN) according to the following standards and/or the later one for similar functions:
a) IETF Recommendation RFC 3331 – (M2UA)
b) IETF Recommendation RFC 3057 – (IUA)
c) IETF Recommendation RFC 3332 – (M3UA)
Any deviation shall be considered as “Material Deviation”
10.2.5 The system should be able to support ISUP variants of different countries. During operation if it is found that any common variant is not available in the system, the bidder has to adopt the variant free of charge.
10.2.6 Packet based Multi media communication system H.323 Full Featured Terminals Protocol suite.
Any deviation shall be considered as “Material Deviation”
=== End of Sub-Section 10 ===
NFV_IGW_Attachment-1&2 Page 80/198
SUB-SECTION 11
Requirements of the System Functions, Facilities and Supervisions
11.1 Switching System Functions The NFV based IGW switching system shall have the flexibility to use for switching purpose the following functions. The system shall allow changes to be done by commands.
11.1.1 Translation Function Any deviation (each of them) shall be treated as “Material Deviation”.
a) Digit Storing Capacity
The system shall have the facility to receive, store and send digit information of:
i) Minimum 15(fifteen) digits for ISD calls, excluding trunk prefix “00”
ii) Minimum 15(fifteen) digits for EISD calls, excluding trunk prefix “012”
b) Analysis of Dialed Number
The system shall be capable of analyzing mixed number length for various types of calls. The inter-digit pause may be as high as 5 secs. The maximum and minimum digits required for routing and charging shall be programmable on site conditions and changeable by commands.
c) Digit Re-translation The system shall be capable of changing all of the received digits to a completely re-translated number, to be sent forward for further processing. The re-translation digits shall be programmable on site and changeable by commands. d) Partial Digit Re-translation
The system shall be capable of changing any number of digits (both or either leading or last digits) from the received digits, to re-translate as a new number, to be sent forward for further processing. The re-translation digits shall be programmable on site and changeable by commands.
NFV_IGW_Attachment-1&2 Page 81/198
e) Digit Deletion
The system shall be capable of deleting any number of digits (both or either leading or last digits) from the received digits, to be sent forward for further processing. The number of digits to be deleted shall be programmable on site and changeable by commands.
f) Digit Insertion
The system shall be capable of inserting any number of digits (both or either at front or after) to received digits, to be sent for further processing. The digits to be inserted shall be programmable on site and by commands.
g) Digit Re-generation
The system shall be capable of re-generate any number of received digits, to be sent forward for further processing. The number of digits to be regenerated shall be programmable on site and changeable by commands.
h) Flexibility to adapt to changed numbering plan
The system shall have the flexibility to easily adapt to any change in the present national numbering plan.
11.1.2 Traffic Routing Functions The system shall have the flexibility to route outgoing, incoming and transit traffic on analysis of variations in calling line identity, numbering and subscriber category. Any deviation shall be treated as “Material Deviation”.
11.1.3 Alternate Routing Functions a) Overload Alternate Routing
The system shall have the possibility to provide automatic alternate routing in traffic overload conditions. The alternate routing for each route shall be at least (but not limited to) 5(five).
b) Load-Sharing Alternate Routing
The system shall have the capability to provide automatic alternate routing for traffic by load-sharing mode.
c) Incoming Route Alternate Routing
NFV_IGW_Attachment-1&2 Page 82/198
The system shall have the capability to provide automatic alternate routing for transit traffic by identification of the incoming route of the call.
d) Time-dependant Alternate Routing
The system shall have the capability to provide automatic alternate routing for traffic by identifying the day of the week and time of the day both independently and in conjunction.
e) Calling Line Identity Alternate Routing
The system shall have the capability to provide automatic alternate routing for calls to same called number by identification of the calling party number.
Any deviation (each of them) shall be treated as “Major Deviation”.
11.1.4 Proportionate Routing The system shall provide the ability to route outgoing calls of a single access code to multiple destinations on proportionate call-sharing basis. The number of destinations (selected either by multiple re-translated access codes or telephone nos. or/ and multiple trunk routes) and the proportion of dispersion of calls between them shall be field-designated. Any deviation (each of them) shall be treated as “Major Deviation”.
11.1.5 Rejection of Incoming Calls The system shall have the capability to reject termination and/or block processing of incoming calls via any route by:
a) Identifying the incoming route number
b) Identifying the Number of the Calling party
c) Identifying whether the call is transit or not
d) Identifying the called party number
Any deviation (each of them) shall be treated as “Major Deviation”.
11.1.6 Rejection of Transit Calls The system shall have the capability to reject termination and/or block processing of incoming calls via any route by :
a) Identifying the called party number
b) Identifying leading digits of the destination number
NFV_IGW_Attachment-1&2 Page 83/198
c) Identifying the outgoing route number
11.1.7 Tones and Announcements The system shall have the following capabilities:
a) Provide embedded tones and announcement functions b) Register announcements to be played. c) Capability to broadcast the supported announcements. d) Request the gateways to play tones and announcements.
Any deviation (each of them) shall be treated as “Major Deviation”.
11.2 Various Facilities The system shall be capable to provide (but not limited to) at least the following facilities. The system shall have the capability to flexibly assign a combination of various system facilities to any or all of the subscribers. Initiation, activation, withdrawal or changes in assignment shall be done through specific commands.
11.2.1 Wrong Number Processing The system shall have the capability of routing wrong dialed numbers or prefixes to dedicated announcements. This shall be a default feature to all of the subscribers. The calls to the announcement will be non-charging. Relevant backward signals shall be sent in case of incoming calls from other exchanges. Deviation shall be treated as “Material Deviation”.
11.2.2 Local Interception Service
The system shall have the possibility to divert all incoming calls to a subscriber or group of subscribers to any local interception centre. Deviation shall be treated as “Minor Deviation”.
11.2.3 Trunk Barred Access The system shall have the possibility to put call barring discriminations on any incoming circuit group or on any subscriber to access any specified outgoing routes. Deviation shall be treated as “Major Deviation”.
NFV_IGW_Attachment-1&2 Page 84/198
11.2.4 Call Gapping The system shall have the possibility to put the function of limiting the number of calls to any outgoing route or destination. Deviation shall be treated as “Minor Deviation”.
11.2.5 Non Chargeable Line The system shall have the possibility, upon receipt of relevant backward signals, to suppress charging on calling subscriber.
11.2.6 Reverse Chargeable Number The system shall provide possibility to assign parameters to any or many subscribers so that, for any incoming call to that number(s), the system will send relevant backward signals to the originating exchange for non-charging the originating number and shall generate charge meter pulses on the terminating number. The generation of charge meter pulses shall depend upon analysis of the A-number received.
11.2.7 Shared Traffic Loading The system shall have the possibility to provide sharing of traffic load to a particular destination. The sharing shall be activated in any or both of the following modes and deviation shall be treated as “Minor Deviation”.
a) Load Sharing Routing
b) Call Sharing Routing
11.2.8 Switching System Supervision The system shall be provided with the following (but not limited to) supervision services. Absence of any such facility shall be treated as "Material Deviation".
11.2.8.1 Fault Detection and Recognition
The system shall have the provision of automatic detection of abnormal operation and shall be able to recognize the causes to divide into definite "error" (for degradation of software performance) and "fault" (for degradation of hardware). Deviation shall be treated as “Major Deviation”.
NFV_IGW_Attachment-1&2 Page 85/198
11.2.8.2 System Reconfiguration
The system, upon detection and recognition of error and/ or fault, shall be able to automatically reconfigure itself in order to:
a) Switch the faulty equipment out of service
b) Generate a fault message with detailed physical location of the faulty
equipment
c) Start the automatic diagnosis protocol
d) Record and print the results of the diagnosis test
e) Switch the stand-by equipment into service
f) Generate relevant alarm message
Deviation shall be treated as “Major Deviation”.
11.2.8.3 Fault/ Error Reporting
The system, upon detection and recognition of error and/ or fault, shall generate relevant alarm message giving the exact date and time, reason and probable location of the fault. The software shall provide facilities for simultaneous recording of such messages in system's primary memory and in any or many printers/ consoles. Deviation shall be treated as "Major Deviation".
11.2.9 Trunk Supervision The system shall be equipped with appropriate software to continually supervise operational condition of trunks. On detection of failures and faults, relevant trunks will be automatically blocked. Minor and Major alarm conditions will be triggered when pre-set threshold levels of blocked circuit numbers are crossed. These thresholds shall be pre-set, for individual trunk circuit groups, by commands. Deviation shall be treated as “Major Deviation”.
11.2.10 Traffic Supervision and Control The system shall be equipped with appropriate software to continually supervise at least the following aspects of traffic conditions:
a) Abnormal increase in originating and incoming calls
b) Heavy traffic congestion on any trunk circuit group
NFV_IGW_Attachment-1&2 Page 86/198
c) Overload in call processing equipment
Overload control procedures shall be automatically activated and relevant alarm messages shall be generated. Deviation shall be treated as “Major Deviation”.
11.3 Fault Diagnosis Protocol The system shall be equipped with necessary software programs to test all the software and hardware packages of the system. The testing can be initiated :
a) Automatically, on periodic intervals to test all the packages, and
b) Automatically, upon detection of any fault or trouble, or
c) Manually, by commands
The results of the test shall indicate, as exactly as possible, the physical location of the suspected package/ card. Deviation shall be treated as “Major Deviation” but the absence of such facility shall be treated as "Material Deviation".
11.4 System Restart The system shall be provided with the following restart facilities:
a) Automatic restart in case of faults which relate to interruption of call processing functions
b) Manual restart, by command, in case recovery is not possible with automatic restart
c) Manual restart, by operation of some hardware switches, when manual restart by command is not possible
d) Manual restart, when it is necessary to upgrade system software
Deviation from (a) to (d) shall be treated as “Major Deviation”.
e) Cold restart, in case of complete power shutdown.
Deviation (e) shall be treated as “Critical Deviation”.
NFV_IGW_Attachment-1&2 Page 87/198
11.5 Trunk Circuit Testing 11.5.1 The system shall be equipped with automatic and manual test facilities for checking proper functioning and localizing faults on trunk circuits. The facilities shall be accessed by commands.
11.5.2 The system shall be equipped with an Automatic Answering Number to terminate test calls and shall have the following features.
a) To automatically answer a test request b) To send a test tone c) To automatically clear the test request after 10 seconds
Absence of such facility shall be treated as “Major Deviation”.
11.6 Signaling Trace facility The system shall be equipped with an on-line real call signal tracing facility for the ITU-T R2, DSS1 and CCS7 ISUP White Book Signaling. Such facility should also be available for Sigtran and broadband signaling, such as H.248, H.323, SIP (I / T) and MGCP. It is necessary to have online or offline decoders to translate received data into intelligible formats (in English) for proper understanding. If this facility is not in built in proposed system, the bidder may include separate equipment for this. Absence of such test facility and any deviation from the features shall be treated as “Critical Deviation”
=== End of Sub-Section 11 ===
NFV_IGW_Attachment-1&2 Page 88/198
SUB-SECTION 12
Requirements of the System Observation and Measurement Facilities
12.1 Traffic Load Observation The system shall have facilities to continually observe traffic load in the network itself and network elements. The results of such observations will be recorded and printed after pre-set period. At least (but not limited to) the following counters will be provided. The required counters will be activated and deactivated by commands. Absence of Traffic Load Observation facility shall be treated as "Material Deviation" and any deviation (each of them) from the following counters shall be considered as “Minor Deviation”.
12.1.1 For the Media Gateway Controller a) Node-wise number of total Incoming calls presented.
b) Node-wise number of total Outgoing calls presented.
c) Node-wise number of total internal calls presented.
12.1.2 For every circuit group under IP MGW/MGW a) Number of Inward calls presented b) Number of Outward calls presented c) Total call duration (in minutes) for incoming calls d) Total call duration (in minutes) for outgoing calls e) Total incoming traffic in erlang f) Total outgoing traffic in erlang g) Total Traffic in the circuit group in erlang h) Number of circuits engaged for incoming calls i) Number of circuits engaged for outgoing calls j) Number of circuits in use k) Number of equipped circuits l) Number of unavailable circuits m) Percentage of Inward busy circuits n) Percentage of Outward busy circuits o) Number of incoming seizures refused
NFV_IGW_Attachment-1&2 Page 89/198
p) Number of outgoing seizures refused q) Total number of refused seizures r) Total number of successful calls s) Percentage of refused incoming calls (due to no auxiliary equipment) t) Percentage of refused incoming calls (due to terminating subscriber busy) u) Percentage of refused incoming calls (due to other reasons) v) Percentage of refused outgoing calls (due to no circuit) w) Percentage of refused outgoing calls (due to other reasons) x) Percentage of successful Incoming calls y) Percentage of successful Outgoing calls z) Number of simultaneous seizure on both-way circuit group aa) Total number of calls to signaling terminals (MFCS/ MFCR/ CC7 handler)
12.1.3 For an access code prefix and routing a) Number of calls to access code prefix b) Number of calls to access routing c) Number of calls to first choice routing d) Number of calls to second choice routing e) Number of calls to third choice routing f) Number of completed calls g) Number of failed calls due to calling subscriber h) Number of failed calls due to called subscriber i) Number of calls failed due to originating node/exchange j) Number of calls failed due to forward node/exchange k) Causes of the failed calls
12.1.4 For a destination a) Observation of call distribution
b) Observation on causes of call failure
12.1.5 Programming for Traffic Observation The system shall allow field programming of the format for different traffic data observations. The selection and activation, de-selection and deactivation, printout time, circuit groups, counters and other parameters shall be executed by commands. At least (but not limited to) the following basis of programming features shall be allowed:
NFV_IGW_Attachment-1&2 Page 90/198
a) Half-hourly basis
b) Hourly basis
c) Two-hourly basis
d) Twelve-hourly basis
e) Daily basis
f) Weekly basis
g) Monthly basis
h) Circuit group basis
i) All circuit groups basis
j) Selected counters basis
k) All counters basis
l) Any mixture of the above basis
12.1.6 Saving of Traffic Data Output a) The system shall allow saving of any or many sets of traffic observation data output to system's primary memory
b) The system shall allow subsequent shifting of those data to secondary memory devices
c) Enough buffer shall be provided in the primary memory device to store data output for dumps equivalent to 48(forty eight) complete dump sets for all available traffic counters
d) Whenever, any portion of the records in the primary memory is shifted to secondary memory, that portion shall automatically be deleted from the primary memory
e) The system shall generate a "minor alarm" and "major alarm" whenever the content of the buffer has exceeded 75% and 85% respectively
NFV_IGW_Attachment-1&2 Page 91/198
f) If records in the primary memory are not shifted to secondary memory and the buffer becomes full, the system shall generate an alarm message and start over- writing on "first-in first-out (FIFO)" basis.
12.1.7 Printing of Traffic Data Output a) The system shall allow printing of the output of different traffic data in intelligible tabular formats
b) The bidder shall find out BTCL's exact requirements during implementation of the contract.
12.2 Real Time Sample Observation of Calls in circuit group under IP MGW/MGW The system shall allow real-time observation of calls for any or many circuit group. The observation shall include at least (but not limited to) the following events for all the calls made through that circuit group(s). The observation shall be activated (including provisions for pre-selection of events and related time- periods for observation) by command and shall be continued until deactivated by command again or the period has ended. Absence of this observation facility shall be treated as "Major Deviation" and any deviation (each of them) from the following listed events shall be treated as "Minor Deviation".
a) Start Time of observation
b) End Time of Observation
c) Identity of the circuit group
d) Total number of Call attempts through the circuit group
e) Signaling used, for each call
f) Calling party number, for each call
g) Digits dialed by the calling party, for each call
h) Routing code used, for each call
i) Access or translation code used, for each call
j) Duration of conversation, for each call
k) Total Number of successful calls
NFV_IGW_Attachment-1&2 Page 92/198
l) Total Duration of all calls, in minutes
m) Total traffic, in erlang
n) In case of uncompleted calls, the cause of failure
12.3 Observation of Calls Transferred to any device The system shall allow observation of calls transferred to any device, like announcement. The observation shall include at least (but not limited to) the following events. The observation shall be activated (including provisions for pre- selection of events and related time-periods for observation) by command and shall be continued until deactivated by command again or the period has ended. Absence of this observation facility shall be treated as "Major Deviation" and any deviation (each of them) from the following listed events shall be treated as "Minor Deviation".
a) Calling party directory number b) Calling party circuit (for incoming calls) c) Cause of call forwarding d) Signaling code used
12.4 Observation of Traffic Load on Signaling Links a) Signaling Link number b) Signaling Device number c) Number of bytes of TSM units transmitted on line for the first time d) Number of bytes of TSM units received on line for the first time e) Number of 128 TSM blocks transmitted on line for the first time f) Number of 128 TSM units received on line for the first time g) Number of TSM received with false CRT h) Number of TSM lost due to blockage on level 2 emit buffer i) Number of forced retransmission cycles violating threshold N1 j) Number of forced retransmission cycles violating threshold N2
12.5 Real Time Observation of Signaling during call setup The system shall allow real-time observation of traffic in signaling links. The observation shall include at least (but not limited to) the following events. The observation shall be activated (including provisions for pre-selection of events) by command and shall be continued for all subsequent calls until deactivated by
NFV_IGW_Attachment-1&2 Page 93/198
command again. Absence of this observation facility shall be treated as "Major Deviation" and any deviation (each of them) from the following listed events shall be treated as "Minor Deviation".
a) Signals interchanged during call setup phase b) Signals interchanged up to called party answer phase c) Signals interchanged during the complete call
12.6 Measurement of Traffic Volume in Erlang The system shall allow statistical measurement of traffic volume in any, many or all trunk or circuit groups under IP MGW/MGW. The measurement shall include at least (but not limited to) the following type of output. The measurement function shall be activated (including provisions for pre-selection of types and related time-periods for measurement) by command and shall be continued until deactivated by command again or the period has ended. Absence of this measurement facility shall be treated as "Major Deviation" and any deviation (each of them) from the following listed events shall be treated as "Minor Deviation".
a) Total originating traffic b) Intra-Office traffic c) Total terminating traffic d) Total outgoing traffic e) Total incoming traffic f) Outgoing traffic per route g) Incoming traffic per route h) Outgoing traffic per destination i) Outgoing traffic per circuit group
12.7 Measurement of Traffic Volume in Packets The system shall allow statistical measurement of traffic volume at any point in the IP network. There shall also be facility to observe the packet loss occurred in the IP network. Absence of such facility shall be treated as “Major Deviation”.
NFV_IGW_Attachment-1&2 Page 94/198
12.8 Measurement of Bandwidth Utilization The system shall allow statistical measurement of bandwidth utilization of the IP network. The measurement shall be done at any point of the network. Absence of such facility shall be treated as “Major Deviation”.
12.9 Requirements of Call Monitoring System Monitoring system must be provided to monitor traffic generated by different customers in E1, STM1 and IP bandwidth level. Provision of listening with headgears and recording audio and video should be there at least from ten points simultaneously at both locations. The system shall also monitor modified CLI or symptom of modified CLI, false supervision Alarm, dead air calls, network effective ratio (NER) and Post dialing delay (PDD). Monitoring system when put to operation must not generate signal degradation. Absence of such system shall be treated as “Material Deviation”.
=== End of Sub-Section 12 ===
NFV_IGW_Attachment-1&2 Page 95/198
SUB-SECTION 13
Requirements of the Operation and Maintenance Facilities
13.1 Introduction The system should include a centralized Network Management System (NMS) for proper operation and maintenance of all the systems covered by this purchase. The bidder shall also integrate existing network elements of IGW1 located at Mohakhali, existing IOS located Moghbazar and newly proposed IOS at Mohakhali. At the same time some of the O&M terminals are to be extended to BTRC premise for monitoring purpose. The NMS shall include all necessary hardware and software to be installed on a complete turn-key basis including design, installation, testing and commissioning. The bidder shall visit existing IGW and IOS and connected NEs before submit the final bid. The NMS shall have the following characteristics.
13.2 Network Management System (NMS) 13.2.1 Hardware/System Requirements of NMS 13.2.1.1 Server System
The NMS shall be equipped with high quality server system in duplicated configuration. One server shall be located at Mohakhali and other shall located Moghbazar along with two display panels at both locations. The NMS can be shared with same server of Cloud/NFV Core System. There shall be availability of Management & Orchestration service for this NMS system. The Operating Software shall be run on the latest version of Cloud OS certified on Linux OpenStack (Red Hat Openstack preferable). The NMS shall have unified monitoring capability for both VNF & NFVi The internal network architecture shall be Ethernet LAN. The deviation shall be treated as “Material Deviation”.
NFV_IGW_Attachment-1&2 Page 96/198
13.2.1.2 Memory Devices
a) The NMS system shall have SSD Hard drive in raid configuration as the primary memory system or shall share the storage system of Cloud/NFV Core System. At least 2 (two) numbers of external DVD re-writable Drives/Magneto Optical Drives shall be provided to act as the secondary memory device.
b) The capacity of each of the hard drive in the RAID shall be at least 4 (four) TB and the number of drives in the RAID shall be at least 3(three).
The deviation shall be treated as “Major Deviation”.
13.2.1.3 Server and Operator Terminals
a) Each of the Server Terminal shall be from internationally reputed Brand and complete in all aspects to work as PC and shall be equipped with LED Monitors (at least 24” Full HD), SS Hard Drive (at least 2 TB), RAM (at least 16 GB), DVD Drive and 2.5 inch Portable USB-Mass Storage device (at least 240 GB), Sufficient numbers of USB-2.0/3.0 Ports (at least 4), Optical USB Mouse. The operating voltage should be 230 V AC ± 10%, 50 Hz.
b) Each of the Operator Terminal shall be from internationally reputed Brand and equipped with at least Core-i7 Processor, 8th Generation, LED Monitors (at least 19”, Full HD), SS Hard Drive (at least 1TB), RAM (at least 8 GB), Re- Writable DVD Drive, Sufficient numbers of USB-2.0/3.0 Ports (at least 4), Optical USB Mouse. The operating voltage should be 230 V AC ± 10%, 50 Hz.
c) Portable Service console shall be used for configuration and testing of local ports of different equipment, remote measurement, testing and operation. The console would be Laptop Computer from internationally reputed brand with at least Core-i7 processor 8th Generation, at least 13”), SS Hard Drive (at least 1TB), RAM (at least 8GB), Re-Writable DVD Drive, Sufficient numbers of USB- 2/3.0 Ports (at least 3), Sufficient serial Ports, Network Interface Card (10/100/1000 Base-T, RJ 45, supported protocols TCP/IP, UDP), Slim size, Weight less than 1.2 Kg, Battery backup 5 hours. The commercial input voltage should be 230 V AC ± 10%, 50 Hz.
The deviation shall be treated as “Major Deviation”.
NFV_IGW_Attachment-1&2 Page 97/198
13.2.1.4 All the Terminals shall accompanied with Licensed Windows Operating System of latest version, Licensed Anti Virus Software of latest version, necessary drivers for different ports and peripherals, Product Documentation, application software and other standard companions. The licensing period of any software shall not expire until the lifetime of respective equipment for which it was provided expires. All the operating systems, Antivirus, divers, documentation, applications shall be provided in CDs or DVDs so that in case of any kind of failure, the maintenance personnel of BTCL can easily install the software and services and make them functional.
The deviation shall be treated as “Major Deviation”.
13.2.1.5 The bidder shall supply O&M and service terminals at BTCL Premise per following requirement:
a) O&M Control Console - 4 (Two)
b) Service Observation Console - 2 (One)
c) Test Console - 2 (One)
d) CDR Management and Accounting - 2 (Two)
e) Portable Service Console - 2 (Two)
If the bidder fails to quote any or many items described, it shall be treated as “non compliance” and it shall be considered that the bidder proposed to supply any number of such items “free of charge” to BTCL.
13.2.1.6 The bidder shall supply Monitoring terminals at BTRC Premise as per following requirement
a) O&M Control Console - 1 (One)
b) Service Observation Console - 2 (Two)
c) CDR collection - 2 (Two)
13.2.1.7 Tables and Chairs for Consoles and Terminals
The Bidder shall provide Tables and Chairs for Servers, Consoles and O&M Terminals. The furniture shall be comfortable and shall be of aesthetic choice. The specifications of the Chairs and the Tables will be as follows:
NFV_IGW_Attachment-1&2 Page 98/198
a) Chair (12 Nos.)
U Shaped tubular cantilever Structural fixed type armed chair made of 35mm diameter & 1.2mm thick mild steel tube. 50mm thick Foam cushioning seat and back rest fixed on 12mm thick ply wood and covered with best quality Rexene upholstery. The Seat of the chair will be fixed with main structure by MS tube in bottom. All surface of MS chemically de-rusted, zinc phosphate coated and oven-baked electrostatic powder paint finish. Sledging armrests are Foam cushioning with Rexene upholstery on well-seasoned wood. 11 (Eleven) PVC stoppers to be used with leg base to keep the structure or floor scratch free.
i) Size : seat-L-460, W-500, Back-H-420, L-460, and over all ii) Height : 880mm iii) Standard : ISO 9001:2008 iv) Identification mark : Hologram and Monogram Sticker of manufacturer v) Packing : Poly Pack.
b) Table (12 Nos.)
Front decorated executive table with full longitude constructed with 16 and 25mm thick MFC board, Ply wood, PVC pasting writing pad, SS tube, Aluminum foil sheet, aluminum foil edging strip, PVC edging and with necessary hardware is to be supplied. The Table shall contain triangular shaped working top constructed with double layer solid 16+16mm thick MFC board with PVC edging on upper top and aluminum foil strip edging on lower top. 690x400x16mm triangular shaped Rexene pasted writing pad fixed on working top. Table constructed with fully knock down facility.
i) Size: Appropriate for 2 (Two) personnel ii) Standard: ISO 9001:2008 iii) Identification mark: Hologram and Monogram Sticker of manufacturer. iv) Packing: Carton Pack.
Actual Number shall be final during BoQ negotiation. If the bidder fails to quote, it shall be treated as “non compliance” and it shall be considered that
NFV_IGW_Attachment-1&2 Page 99/198
the bidder proposed to supply any number of such items “free of charge” to BTCL.
13.2.1.8 Wide Screen Display Panel : 02 (Two)
The supply shall include 02 (two) Wide Screen LED Panels (of minimum size 1.5 m x 0.9 m) of the connected network at Moghbazar and Mohakhali and the screen shall be mounted on wall. The screen shall
a) Show the real-time alarm status of the related nodes by easily distinguishable color scheme. b) The screen shall show different measurement and operational data in graphical format provided by the NMS system. c) The display screen should be rugged and industrial nature and should be able to work 24/7 in the required environmental condition specified in this document earlier. d) The LED screen should consist of the Visual Display Unit, Display Controller and Management Software. The panel management software shall allow switching the video streams. e) The operators whose systems are on the same Ethernet should be able to work on the large screen sitting at their own position with their own WIN PC‟s / OWS‟s keyboard and mouse. f) The screen shall be of high graphics resolution with flicker free image.
The deviation shall be treated as “Major Deviation”.
13.2.1.9 Laser Printer: 02 (Two) Nos.
Printer shall have the following specifications and each lot shall be connected with the LAN of the NMS.
i) Functions: Print, Copy, Color Scan (Multifunction) ii) Processor: Minimum 400 MHz or higher iii. Print Speed: Copy: Minimum 32ppm (A4), 16 ppm (A3), Resolution: 600 x 600dpi (Minimum); Print: 32 ppm (A4), 16 ppm (A3), Resolution: 600 x 600dpi (Minimum); Scan: 22 ipm (A4, 300 dpi x 300 dpi) iv) Scan Features: TWAIN, WIA compatible v) Supported File Format (Scan): PDF / Searchable PDF / Compact PDF, BMP, JPEG, TIFF
NFV_IGW_Attachment-1&2 Page 100/198
vi) RAM: 192 MB or higher vii) Interface: 1 Hi-Speed USB 2.0/3.0, built-in Fast Ethernet 10/100 network port viii) Network Protocol: TCP/IP v4/v6 ix) Paper support: A4, letter, legal, executive, envelopes etc. x) Paper tray: 250-sheet multipurpose tray 1, 250-sheet tray 2; optional 500- sheet tray 3,100-sheet face-down output bin xi) Power Supply: 220 - 240V AC, 50 / 60Hz xii) OS supported Microsoft® Windows® 7 (32-bit/64-bit), Windows® 8 (32- bit/64-bit), Windows® 10 (32-bit/64-bit), Windows® Server 2008 (32-bit/64- bit), Windows® Server 2012 (32-bit/64-bit), Mac OS X, Linux
Deviation of each feature of clause shall be treated as “Major Deviation”.
13.2.1.10 DVR, CCTV/IP Camera, HDD and Monitor The specifications for the security and surveillance system are as follows: i. DVR [16 port USB supported, AD/DC Adaptor, internationally recognized/well-known brand]: 01 No. ii. 4 TB HDD [USB supported, minimum 300 Mbps data transfer rate, internationally recognized/well-known brand]: 02 Nos. iii. CC Camera/IP camera [ Minimum 4 MP, 30 meter range, 800 DPI, HD quality, internationally recognized brand including Adaptor and connectors]: 10 Nos. iv. LED Monitor [Minimum 19”, HD quality, Internationally recognized brand]: 01 No Deviation of each feature of clause shall be treated as “Major Deviation”. 13.2.1.11 Scanner (2 Nos.) The specifications for the scanner will be as follows:
i) Country of manufacture: To be mentioned by the bidder ii) Resolution: 4800 x 9600 dpi or higher iii) Enhanced: Up to 999999 dpi iv) Paper Size: A4
NFV_IGW_Attachment-1&2 Page 101/198
v) Technology: CCD vi) Bit Depth/Pixel: 96 bit or higher vii) Light Source: LED Technology viii) Type: Flatbed, One-pass color and monochrome ix) Connectivity: USB interface x) Compatible Operating Systems: xi) Microsoft® Windows® 7 (32-bit/64-bit), Windows® 8 (32-bit/64-bit), Windows® 10 (32-bit/64-bit), Windows® Server 2008 (32-bit/64-bit), Windows® Server 2012 (32-bit/64-bit), Mac OS X, Linux
Deviation of each feature shall be treated as “Major Deviation”.
13.2.1.12 Projector (01 Nos)
Bidder shall provide High quality, well-known/reputed brand and Standard interface projector having the following criteria (but not limited):
a) Multimedia Interface: HDMI, USB, VGA, Video, Micro SD Card, Audio in&out b) Light Source Life time : Minimum 20, 000 Hours c) Contrast: 100000:1 d) Screen Size/ Project Distance: 50"-200" Inch/1.5-15m e) Screen Mode: Widescreen f) Projector Power Consumption: 100 watts(Max)
13.2.1.13 Inverters The supply shall include necessary inverters for all equipment of the NMS, if needed. The dimensioning of the inverters shall be as the criteria specified in Sub-Section 14, Clause 14.4 and shall use the exchange‟s - 48V DC as source power. The deviation shall be treated as “Major Deviation”.
13.2.2 Software Requirements of NMS 13.2.2.1 Software Capability
The software(s) shall be modular in structure and shall be capable of merging new files and programs with existing files at the site without any interruption of service in the following cases. Deviation form such capability shall be considered as “Material Deviation”.
a) Expansion or change of MGW capacity
NFV_IGW_Attachment-1&2 Page 102/198
b) Loading of new software patches or changes of program version
c) Changes and employment of new service features and facilities
d) Permanent or temporary withdrawal of any existing hardware
e) Changing of any hardware for maintenance or up-gradation purpose
13.2.2.2 Password Protection The main features and data of the software shall be protected by multi-level password control. Modification of the Network data and Subscriber configuration data shall also be protected by passwords. The system password will not be erased or corrupted during system re-boot and/ or redundant server switchover or for any other reasons. Deviation shall be considered as “Material Deviation”.
13.2.2.3 Immunity against propagated faults All modules of the Software shall be immune against propagation of faults from any other software or hardware modules and shall be protected against any mutilation of data. The faulty software module shall also not propagate its own fault to any other software or any hardware modules. Deviation shall be considered as “Material Deviation”.
13.2.2.4 Records of all executed commands shall be kept in log files and these files shall be stored in system hard disk. Any deviation shall be considered as “Major Deviation”.
13.2.2.5 System and Alarm Messages The software shall be capable of recognizing different system degradation, alarm and fault conditions and generate appropriate spontaneous messages. The relevant output messages must be in English; deviation shall be considered as “Material Deviation”.
13.2.2.6 Real time Bandwidth utilization Facility should be there to allow to view online graphical and statistical Bandwidth utilization for IGW and IOS located at Moghbazar and Mohakhali. This will be password protected and will show up-link bit rate, down-link bit rate, packet drop rate etc. The administrator of the system can view the total
NFV_IGW_Attachment-1&2 Page 103/198
usage as well usage of individual user/link as a super user. Absence of such facility shall be treated as “Material Deviation”.
13.2.3 Functional Requirements of NMS 13.2.3.1 The NMS shall have the capability to support the following management functions for all elements connected with the system:
a) Fault Management
b) Configuration Management
c) Accounting Management
d) Performance Management
e) Security Management
f) Capacity and Planning Engineering Tool
g) Network Loading and Simulation Tool
All the management functionalities shall be implemented in the NMS as a set of interactive application components using client-server architecture and can be vertically and horizontally integrated.
13.2.3.2 The NMS should support the following: a) Graphical Unit Interface (GUI)
b) Real-time alarm display and collection
c) Card/circuit level diagnosis
d) Interface line status monitoring, both subscriber lines and network interface.
e) Performance monitoring and traffic measurement.
f) Network/NE configuration management.
g) Routing table management
h) SNMP-based network management interface(s) to support third party network management system.
i) Adaptive to ITU-T Q3/CMIP.
NFV_IGW_Attachment-1&2 Page 104/198
j) Latest version of the Windows, Certified cloud/NFV based OS or any management system available.
k) Implementation of software patches and releases on the NGN nodes remotely.
13.2.3.3 Basic Features and Capabilities
The NMS shall provide:
a) Preferably Application Program Interface (API) for all network elements regardless of Brand and Model.
b) End-to-End tracing function that can report combination of signaling message over all nodes in IOS/IGW network under supervision.
b) Configuration planner for simplifying the task of future network planning and configuration.
c) Automatic copy of configurations at device, cards, and ports level to the customer information database system within the NMS.
d) Network Integrity check at the network, device, card, and port levels.
e) End to end path management.
f) Advance alarm management setting for priorities and types.
g) Multiple network managers support with different access authorities.
h) Network element status displayed by colors.
i) Graphical User and user-friendly interface with online help.
j) Identification of problems through event correlation. It should intelligently correlate events into high level alarms, immediately pinpointing the root cause of network problems.
k) Web-based user interface.
l) Scalable architecture
NFV_IGW_Attachment-1&2 Page 105/198
13.2.3.4 Fault/Alarm Management The NMS shall support (but not limited to) the following fault and alarm management capabilities:
a) Detected errors/unusual network behavior should be isolated and controlled.
b) Results of errors/unusual network behavior should be displayed in graphical and tabular form.
c) Alarm facilities should permit the easy identification and correction of faulty element.
d) Alarms should have a status of active, deferred, or cleared and should be in active state when first received.
e) The severity of the alarm, full alarm message and time of delivery should be available for display and are logged in the alarm database.
f) The administrator should be able to set various thresholds for alarm reporting, including filtering by severity, number of occurrences within a given period and interval between occurrences.
13.2.3.5 Configuration Management The Configuration Management should initialize and close down manage objects, collect information on demand about the current condition of the network, obtain announcements of significant changes in the condition of the network, and change the configuration of the Network and the Network Elements.
The NMS should support (but not limited to) the following configuration management capabilities:
a) Complete configuration of all network devices, cards, and ports for connection establishment and complete control of the network.
b) Graphical User Interface for configuring all system devices, cards, and ports.
c) Web-based Graphical User Interface for remote configuration management for all system devices, cards, and ports.
d) The NMS should have an automatic backup configuration facility.
NFV_IGW_Attachment-1&2 Page 106/198
13.2.3.6 Accounting Management The NMS should support, (but not limited to) the following accounting management capabilities:
a) Track resources consumed
b) Enable accounting limits to be set and tariff schedules have to be associated with the use of resources.
c) Enable accounting data to be combined where multiple resources are involved to achieve a given communication objective.
d) Providing and accessing logs of accounting data.
13.2.3.7 Performance Management The NMS should support, but should not be limited to the following performance management capabilities:
a) Monitor network throughput and real-time Bit Error Rate must be supported.
b) Set thresholds for various variables, such as error rates or link utilization.
c) Continuous background diagnostics during system uptime are required for early detection of fault conditions and timely activation of alarms.
d) Log and save all or defined events for present and future reference.
e) All man-machine interfaces shall be in a Graphical User Interface.
13.2.3.8 Security Management The NMS should support (but not limited to) the following security management capabilities:
a) Secure access between network elements and the network manager.
b) The system should incorporate security measures against unauthorized personnel to access the office data/programs and entering of commands.
c) Several access levels according to the order of their influence on program performance should be identified with the corresponding password.
Each deviation of the above requirement shall be treated as “Major Deviation.”
13.3 Lawful Interception
NFV_IGW_Attachment-1&2 Page 107/198
The system must meet LI compliance according to –
a) TS 101 331 Telecommunications security; Lawful Interception (LI); Requirements of Law Enforcement Agencies;
b) ES 201 158 Telecommunications Security; Lawful Interception (LI); Requirements for Network Functions;
c) ES 201 671 Telecommunications Security; Lawful Interception (LI); Handover
Interface for the Lawful Interception of Telecommunications Traffic (revised version);
d) TR 101 943 Telecommunications Security; Lawful Interception (LI); Concepts of Interception in a Generic Network Architecture;
e) TR 101 944 Telecommunications Security; Lawful Interception (LI); Issues on IP Interception;
13.3.1 The LI facility shall include necessary hardware and software for a) Management system for interception
b) Mediation system
c) Delivery systems
13.3.2 The Lawful Interception Facility shall be capable handover of a) Administrative Information (HI1)
b) Intercept related Information (HI2)
c) Content of Communication (HI3)
13.3.3 E1s shall be used to transfer HI3 payload to the National Monitoring Centre (NMC).
13.3.4 LI Monitoring shall be invisible to subscribers and to the staff(s) operating the network.
13.3.5 Minimum number of activated warrants is 1500
13.3.6 Minimum number of mediated interception request 150
NFV_IGW_Attachment-1&2 Page 108/198
Bidder shall explain his/her proposal-with diagram, system capacity, integration plan etc. and provide a compliance statement to relevant ETSI/ ITU-T/ IETF recommendations. Deviation of the above requirement shall be treated as “Substantially Non-responsive”
13.4 CDR Management 13.4.1 The supply shall include latest industrial standard hardware and necessary Licensed Software to provide the following services:
a) Download CDRs to a PC hard disk,
b) Processing these data into suitable format for billing server input
c) Saving raw-data into DVD / Portable USB-Mass Storage device
The Bidder must agree that actual mediation and configuration shall be finalized during implementation.
13.4.2 The Bidder shall install Software and Hardware for Online CDR transfer to the billing centre, BTRC, LEA premise or designated places instructed by BTCL. Bidder shall propose their solution in this regard. The solution shall include (but not limited to) List of hardware and Licensed Software, Furniture, Transmission Requirement, data flow diagram, system interconnection diagram etc.
The deviation shall be treated as “Major Deviation”.
13.5 Management & Orchestration Requirement If the NMS is shared with same server of Cloud/NFV Core System. The proposed solution shall comply with ETSI, OPNFV, OpenStack Foundation and open APIs defined management & orchestration in GS NFV-MAN 001 and later. Bidder shall:
a) Describe their NFVO solution architecture. b) Describe their VNFM solution architecture. c) Describe the security architecture and security policies of their solution. d) Provide information of interfaces e) The proposed solution shall support separate G-VNFM and S-VNFM. Any disagreement shall be treated as Critical Deviation.
NFV_IGW_Attachment-1&2 Page 109/198
13.5.1 NFVO Features
a) The proposed solution shall support multiple VIMs and manage virtual resources. b) The proposed solution shall support tenant/user management (role and domain management). c) The proposed solution shall support VNFD and package management, which means managing installation, verification and update from NFVO d) The proposed solution shall support NS configuration parameters modification with GUI during instantiation and update and scaling. e) The NFVO shall use http and https protocol to connect with VIM. f) The proposed solution shall support cross-layer RCA with VNF/VM/NFVI. g) The proposed solution shall support log unified management of VNF/VM/NFVI/VNFM. h) The proposed solution shall support Network Service lifecycle management function. i) The proposed solution shall support graphical design tool to simplify NSD/VNFD creation. j) The proposed solution shall support ETSI TOSCA. k) Bidder shall describe how to perform performance monitoring in proposed NFVO. l) The proposed solution shall support policy management functionality in NFVO. m) The proposed solution shall support coordinate scaling in/out for VNFs in NFVO. n) The proposed solution shall support manage hybrid network of VNF and PNF. o) The proposed solution shall support disaster recovery for VNFs. p) Bidder shall describe how to perform fault detection and processing in proposed Management and Orchestration system. q) Bidder shall provide information about 3rd party VNF integration. r) The proposed solution shall support 3rd party VNFs no less than 22+. s) The proposed solution shall support integrate with SDN of other vendors. t) The proposed solution shall support QoS policy management. u) The proposed solution shall support fault diagnosis/fault demarcation of NFVO.
NFV_IGW_Attachment-1&2 Page 110/198
v) The proposed solution shall support upload the VNFD template, VNF image package and VNF software package in FTP/SFTP mode. w) The proposed solution shall support display the IaaS resource pool by layer, the capacity information can be displayed by region, cluster, and host.
Any deviation and disagreement shall be considered as “Major deviation”
13.5.2 G-VNFM Features
a) The proposed solution shall support multiple VIMs from different vendor. b) The proposed solution shall support VNF healing. c) The proposed solution shall support scale up and scale down. d) The proposed solution shall provide VNFD and VNF package management functionality. e) The proposed solution shall be able to provide VNF lifecycle operation granting request function. f) The proposed solution shall be able to instantiate VNF using the on-boarded VNFD. g) The proposed solution shall support HOT. h) The proposed solution shall support SSH interface for VNF configuration. i) The proposed solution shall describe the supported based on VNF KPI of VNF scaling. j) The proposed solution shall support VNF upgrade/update k) Fluctuation of traffic load on VNF could cause repeated scaling out and scaling in. The Bidder shall describe how to prevent this problem. l) The proposed solution shall be able to terminate VNF, release associated NFVI resources and return them to NFVI resource pool. m) The proposed solution shall be able to provide VNF performance monitoring function for scale. n) The proposed solution shall provide a policy engine for scaling. o) The proposed solution shall instantiate two or more VNFs simultaneously. p) The proposed solution shall support ETSI TOSCA to describe VNFD. q) Bidder shall describe how to perform coordinated maintenance with EMS. r) The offered VNFM should support working independent with NFVO, VNFM manage the Life cycle of VNF independently.
NFV_IGW_Attachment-1&2 Page 111/198
Any deviation and disagreement shall be considered as “Major deviations”
13.5.3 Capacity & Licensing
a) The proposed solution must be licensed by vCPU of managed VNFs. b) The proposed solution must support On-demand purchase G-VNFM. c) The proposed solution max capacity for managed VMs must no less than 500. d) The proposed solution shall support disaster recovery for NFVO and VNFM. e) The proposed solution shall support local HA design. f) The proposed solution shall support disaster recovery for VNFM.
Any deviation and disagreement shall be considered as “Critical deviation”
13.5.4 Expandability
The proposed solution shall support system expansion smoothly without service interruption.
13.5.5 The proposed solution shall have the following features:
a) The proposed solution shall include monitoring data collection, unified data management and data presentation across VNF, Cloud OS and COTS, Unified monitoring facilitates operator to have a holistic view of NFV and enables operator to find out the issues timely. b) The proposed solution shall be trying to make NFV operations as automatic as possible thus to reduce mean-time-to-resolve and improve operations efficiency. c) The proposed solution shall build unified internal model for object and relationship to store alarm, performance, and topology resource data. Unified data mediation guarantees rapid integration of alarm, performance and resource data across VNF and NFVI. d) The proposed solution shall ensure that Policies are provided to take action based on multiple inputs and validations, in order to prevent impact to services or solove the problem. e) The proposed solution shall ensure that all Policies can be made either fully automated or manual intervention.
NFV_IGW_Attachment-1&2 Page 112/198
f) The proposed solution shall ensure that the progress and outcome of Policy execution can be displayed, which shall include detailed reasons for failure if the execution fails in part or in its entirety. g) The proposed solution shall ensure that all Policy execution is completely auditable and traceable to the system and/or user executing the policy. h) The proposed solution shall correlate VNF Instance-related events/faults with NFVI performance measurement and faults/events information & report the events/faults to the supplier OSS, please describe. i) The proposed solution shall correlate VNF Instance-related events/faults with NFVI performance measurement and faults/events information for Scale up- down VNF instances, i.e. increase or reduction of the VNF capacity (CPU, memory etc.) j) The proposed solution shall correlate VNF Instance-related events/faults with NFVI performance measurement and faults/events information for Scale in- out – i.e. Adding/removing VM instances k) The proposed solution shall correlate VNF Instance-related events/faults with NFVI performance measurement and faults/events information for Self- healing of VNF instance (assisted or automated) l) The proposed solution shall trigger corrective action based on alarms generated at the NFVI & VM/VNF layer m) The proposed solution shall support alarm correlation in upper layer OSS system to consolidate alarms raised in the NFV: i) Combine alarms associated with a VNF or VM
ii) Display root cause of associated alarms (rather than display individual alarms separately).
n) The proposed solution shall support to mine new alarm rules (RCA, flapping etc.) through Machine Learning. o) The proposed solution shall have the capabilities of the Assurance to the 3rd party compatibility p) The proposed solution shall adjust the use of resources automatically by monitoring the VNF&NFVI. q) The proposed solution shall collect and analyse logs from the managed object for problem location during system running.
NFV_IGW_Attachment-1&2 Page 113/198
Any deviation and disagreement shall be considered as “Major deviation”
13.5.6 Fault Management
a) The proposed solution shall be able to collect fault information of Hardware Resources (compute, storage, and networking), Software resources (hypervisors), and virtualized resources (VMs) and to forward faults/events information to the upper layer OSS. b) The proposed solution shall support real-time pushing alarm feature. The alarm will display on the monitoring view in time once collected, and user can locate the fault. c) The proposed solution shall support present and manage the node of different lay in DC by topology. The topology contains VNF, VM, HOST and network. It can display the alarm on topology and update automatically. And also the topology can be edit manually. Add, delete or copy any NE or group are allowed. d) The proposed solution shall support visualize the object (Cluster, host, data storage, network, etc.). e) The proposed solution shall support alarm enrichment, alarm compression, alarm correlation to minimize the active alarms for operations and maintenance (O&M) team‟s processing. f) The proposed solution shall provide the capability of historical event/alarm repository to keep data persistence. g) The proposed solution shall support all of events shall be processed into a consolidated form which includes all of relevant event/alarm information like date, time, severity, unique identifying number, user defined component identifier, detailed alarm description including probable cause and impact. h) The proposed solution shall provide the capability of event/alarm compression for de-duplication processing. It shall support different types of compression mechanisms to process repetitive events. i) The proposed solution shall provide the capability of automatic event/alarm processing. It can be used to trigger automation processes to improve operation efficiency j) The proposed solution shall provide topology-based Root Cause Analysis (RCA) and correlation to directly locate the fault causes when a group of NFVI&VNF faults/events occurs.
NFV_IGW_Attachment-1&2 Page 114/198
k) The proposed solution shall provide the capability of real-time/historical event/alarm query according to different conditions like severity, occurrence time, key words in the event/alarm summary, etc. l) The proposed solution shall provide list-based and topology-based event/alarm view. The event/alarm lists are used to present the detailed information of events. The location and distribution of events can be presented on network topology maps. m) The proposed solution shall provide various event/alarm operations like order dispatching, event/alarm acknowledgement or clear, through the user interface. n) The proposed solution shall provide various event/alarm indications like sound, color, etc. Any deviation and disagreement shall be considered as “Major deviation”
13.5.7 Performance Management
a) The proposed solution shall support end to end network performance data monitoring, including the collection, monitoring, measurement, analysis, and reporting network performance or quality. b) The proposed solution shall be able to collect performance data of Hardware Resources (compute, storage, and networking), Software resources (hypervisors), and virtualized resources (VMs) and VNF to forward performance data to the upper layer OSS. c) The proposed solution shall have big data processing capabilities. d) The proposed solution shall support report customization ability. Support user to define different service report template according to service scenario and generate report automatically. Including historical reports, historical comparison reports and so on in order that users can compare, analyze and deal with performance issues, and also support regularly sent the result to the designated staff. e) The proposed solution shall be capable of building user defined reports from the full range of available counters, pre-defined KPIs and user defined metrics. The report functionality shall be built without the need for programming languages. f) The proposed solution shall provide a variety of report types to reach different service scenarios demand, including: tables, line charts, bar charts, column charts, pie charts, area charts etc.
NFV_IGW_Attachment-1&2 Page 115/198
g) The proposed solution shall be possible to provide drill down features from the aggregated views down to the sub-element detailed view h) The proposed solution shall be able to regularly generate reports or immediately generate report based on user demand. Support to generate reports by setting regular tasks, and support to send to the designated person/role by Email / SMS or uploaded to an FTP server. i) The proposed solution shall provide report customization function, users can customize report templates according to business demand, and can share the created report to make sure other users can access the report, and also can define new reports based on the defined report template. j) The proposed solution shall store raw metrics and aggregated metrics for a configurable period of time. By default raw metrics shall be retained for at least 30 days and daily aggregated metrics for 13 months. k) The proposed solution shall support the following aggregation operators, including but not limited to: i) Sum ii) Average iii) Maximum iv) Minimum v) Busy hour. l) The proposed solution shall support aggregation of metrics over time periods including 15 mins, hourly, daily, weekly and monthly. m) The proposed solution shall support to define alarm thresholds for critical, major, minor, warning and clear conditions for either KPIs or counters. Support to change the colors of each of the alarm conditions. n) The proposed solution shall enable performance thresholds to be set on a per- managed-object or per-managed-object-type basis o) The proposed solution shall provide threshold configuration function, support to configure static and dynamic thresholds for each indicator. p) The proposed solution shall support user-defined performance monitoring Dashboard, for near real-time monitoring of network performance, in order to fulfill the accordingly monitoring tasks. q) The proposed solution shall provide homepage configurable function, support user to set the configured Dashboard to be homepage
NFV_IGW_Attachment-1&2 Page 116/198
r) The proposed solution shall support static/dynamic object group for monitoring and reporting s) The proposed solution shall support when creating a report or dashboard, user can find the target objects by rich filter conditions such as by name, id, attributes. Any deviation and disagreement shall be considered as “Major deviation”
13.5.8 Scalability and Availability
a) The Supplier shall detail the strategy adopted for managing the impact of component failure or processor overload. The effect of failures/overload on established traffic connections shall be defined. b) The proposed solution shall support the system recovery. c) The proposed solution shall support HA and DR solution. d) The proposed solution shall support micro-service multi-instance cluster deployment, automatic horizontal scaling, and load balancing. e) The proposed solution shall be cloud native, metadata driven, and micro service enabled to build one robust and scalable assurance platform. f) The proposed solution shall support unified south command set framework to send command to EMSs and devices for diagnosing, collecting and routing inspection, and the protocol type support at least MML, TELNET, SSH and TL1 etc. g) The proposed solution shall support a web-based graphical user interface for operational or administration purposes. h) The system shall support distributed and scalable deployment, provide the recommended deployment scenarios for different scale. Users can deploy flexibly according to the network scale; and support smooth upgrade and expansion in accordance with changes in network size, to meet diversified delivery requirements of different business scenarios. The deviation shall be treated as “Major Deviation”
Any deviation and disagreement shall be considered as “Major deviation”
=== End of Sub-Section 13 ===
NFV_IGW_Attachment-1&2 Page 117/198
SUB-SECTION 14
Requirements of the Power Plant and Air-Conditioning Facilities
14.1 Introduction The offer shall include necessary power plant and air-conditioning equipment for operation of the Switching system. The details of such power plant facilities are listed below. Any negative deviations of the described specification and requirement shall be treated as “Critical Deviation”.
14.2 Battery
a) The offer shall include necessary battery sets to provide back-up DC power source to run the system during AC mains failure at Moghbazar. The Bidder in his offer shall use the detail breakdown of its DC power requirement, as given by him in the bid offer. The required back-up time shall be 8 Hrs and the number of sets shall be 2 (two). The calculation for minimum capacity requirement of the battery shall be as follows:
i) Total DC Amps requirement of the system at busy-hour load = l1
ii) Total DC Amps requirement for Inverters = l2
iii) Total Exchange load = l1 + l2 = le in Amp iv) Total reserve DC Amps requirement = 20
v) Total DC Load = le + 20 = ltm in Amp vi) Allowable maximum discharge = 70 %
vii) Total Required Back-up Capacity = 8 x ltm = lbm in AH
viii) Total Required battery capacity = lbm / 0.7 = lcm in AH
ix) Capacity of each Set of Battery = mcm = lcm / 2 in AH)
The Bidder shall give the above details of battery dimensioning. Failure to give detail breakdown shall be treated as “non compliance".
b) The Batteries shall be vented, lead-acid type from country or abroad. The abnormal fall in terminal voltage shall generate visual and audible alarm facilities and required alarm loops to the exchange OMM shall be connected. c) The minimum guaranteed life-cycle of the batteries must be at lest 5(five) years.
NFV_IGW_Attachment-1&2 Page 118/198
d) Each of the battery sets must be provided with two independent (one at the rectifier-end and the other at the battery-end) circuit-breakers of adequate capacities which will allow complete disconnection of the battery set during all any required O&M function. e) Moreover both of the battery sets shall be connected to the rectifier through a common circuit-breaker of adequate capacity which will allow complete disconnection of both of the battery sets during any required O&M function. f) In order to protect the exchange equipment as well as the battery in case of dropping of the DC voltage below a certain level, the rectifier connection to the battery sets must be provided with a device for disconnecting the battery sets as soon as such levels arrive. g) Provisions must be available to detect the battery-voltage and other parameters from the exchange. h) All of the exposed parts of the terminals in each cell of the battery-sets will be provided with adequate oxidation-proof covers. i) Provisions shall be provided in the battery-room for an inter-locked exhaust-fan which will turn-on whenever any of the battery sets goes into boost-charge mode. j) Provisions shall be made for adequate acid-proof tiles in the places of battery mounting. k) The charging-current at 10 hrs charging rate for the battery sets, as supplied shall be carried-over to calculation for rectifier requirement.
14.3 Rectifier
a) The offer shall include necessary rectifier modules to provide DC power source to run the system and to charge the back-up batteries. The Bidder in his offer shall give a detail breakdown of its DC power requirement and the charging current for the back-up batteries at 10 hrs charging rate. The calculation for capacity requirement of the rectifier set shall be as follows:
i) Total DC Amps requirement of the system at busy-hour load = l1
ii) Total DC Amps requirement of the Inverters = l2 iii) Total Charging Amps for the quoted batteries at 10 hrs charging rate =
l3
iv) Total Exchange load = l1 + l2 + l3 = le v) Reserve = 10 %
vi) Required Capacity = 1.1 x le = lr
NFV_IGW_Attachment-1&2 Page 119/198
vii) Reserved Capacity for other systems = 20 amps
viii) Total Required capacity = lr + 20 = ltr Amp
ix) Capacity of each Rectifier Module = mc
x) Number of required modules = ltr / mc = Nr (rounded up to the next integer value)
xi) Number of modules to be supplied = Nr + 1
xii) Capacity of the Rectifier Racks = Nr + 4 xiii) Number of spare Rectifier modules to be supplied = 2
The Bidder shall give the above details of rectifier dimensioning. Failure to give detail breakdown shall be treated as “non compliance”.
b) The Rectifiers shall be electronic switch-mode type with automatic redundancy control and charging control functions. The control panel shall provide visual and audible alarm facilities and required alarm loops to the exchange OMM. c) Each of the rectifiers shall be provided with circuit-breakers (both in AC and DC side) of adequate capacity and shall allow full isolation from the source and the load. d) The Rectifier Rack (or Frame) shall be provided with circuit-breakers (both in AC and DC side) of adequate capacity and shall allow full isolation from the source and the load. If the all of the rectifiers are taken-out of service, provisions shall be there for automatic diversion of the load to battery. e) The rectifier rack shall contain one or more DC distribution panel consisting of circuit-breakers of different capacity. The number of such breakers shall be such that it will be at least 100% redundant from the quantity destined to be used for the present capacity of the switch in site. f) The nominal Input voltage for rectifiers shall be 380V +20%-25%, 50Hz, 3 phase, 4-wire.
14.4 Inverter a) The offer shall include necessary DC to AC inverter modules to provide AC power source to the equipment which require AC supply. The exchange back-up batteries shall be used as the source power. The Bidder in his offer shall give a detail breakdown of AC power requirement (in VA) of the hardware listed below. The calculation for capacity requirement of the inverter shall be as follows: i) Total AC Volt Ampere (VA) requirement for above hardware at busy-hour
load = le
NFV_IGW_Attachment-1&2 Page 120/198
ii) Reserve = 10 %
iii) Required Capacity = 1.1 x le = lr VA iv) Reserved Capacity for other systems = 500 VA
v) Total required capacity = lr + 500 = lt VA
The Bidder shall give the above details of inverter dimensioning. Failure to give detail breakdown shall be treated as “non compliance” and in such case BTCL shall draw its own conclusion.
b) The Inverters shall be electronic switch-mode type with automatic redundancy control functions. The control panel shall provide visual and audible alarm facilities and required alarm loops to the exchange OMM. c) Each of the inverter shall be provided circuit-breakers (both in AC and DC side) of adequate capacity and shall allow full isolation from the source and the load. d) The Inverter Rack (or Frame) shall be provided circuit-breakers (both in AC and DC side) of adequate capacity and shall allow full isolation from the source and the load. If the all of the inverters are taken-out of service, provisions shall be there for automatic diversion of the load to incoming commercial AC supply.
14.5 Air-conditioner
a) The offer shall include necessary air-conditioning unit for the exchange and OMC Rooms. The Bidder in his/her offer shall give a detail breakdown of its air- conditioning unit requirement The parameters of calculation for present capacity requirement (Cr) of the air-conditioning unit shall be as follows:
i) Approximate Area of the equipment room is (21 x 26) sq. feet. Separate OMC and NOC room is (28 x 19) sq. feet. Equipment room, OMC room and NOC shall require appropriate capacity of Air conditioning system ii) Average outside temp (in summer) : 38° C iii) Average room temp to be maintained: 22° C iv) Equipment Capacity to be supplied : 2 x present requirement (Cr) v) Number of Air-con units : N + 1 b) The Air-con system shall be equipped with a common control unit providing all the necessary control and monitoring functions. The control panel shall provide
NFV_IGW_Attachment-1&2 Page 121/198
visual and audible alarm facilities and required alarm loops to the exchange OMM. c) Each of the Air-con unit shall be equipped with an independent circuit-breaker of adequate capacity. d) Each of the Air-con unit shall be connected to its independent water-drain and there shall be enough drainage out of the switch room. e) All of the equipment rooms must be equipped with at least 3(three) numbers of temperature sensors connected with the control-panel of the Air-cons. f) For Exchange room the value of N in above item a (v) should be at least 2 (two).
g) Specification of the Air-conditioning equipment i) Type : Split, with remote control ii) Automatic Control Panel (ACP) : N +1 redundancy iii) Power : 230V, 50 Hz, 1- phase or
400V +10% -20%, 50Hz, 3- phase.
h) The bidder shall visit the switch /equipment room, OMC and NOC room before submit the final bid. The bidder will communicate with BTCL concern division/unit in this regard and respective unit will assist to visit the specified place (Switch OMC and NOC room).
=== End of Sub-Section 14 ===
NFV_IGW_Attachment-1&2 Page 122/198
SUB-SECTION 15
Technical Specifications for Test Equipment (To Be Quoted Optionally
15.1 General Bidder shall propose test equipment and special tools for installation, operation and maintenance testing of the equipment. The minimum suggested testing equipment and the required quantity are given below. The bidder may quote any other equipment required. Actual quantity of all testing equipment shall be decided during BoQ finalization.
15.1.1 All test equipment shall be from well-reputed manufactures with guarantee for calibration and repair maintenance services preferably in Bangladesh for a period of 10 years from the date of signing of agreement.
15.1.2 The contractor shall supply complete Licensed software in CD/DVD including operating system, Instruction, Operation and User manuals for the test equipment.
15.1.3 a) The contractor must submit document/brochure of test equipment with adequate technical details and description of different module software option available for the offered test equipment
b) The quotation must clearly mention which module and software option had been included in the offer, so that BTCL clearly evaluate whether the offer meets BTCL specification.
Any Deviation will be considered as “Critical Deviation”.
15.1.4 The features and or other items of the proposed test equipment shall at least meet (but not limited to) the mentioned technical specifications of the specified test equipment. It should be noted that, test equipment is very vital for maintenance, so quality should not be compromised for all proposed test equipment.
NFV_IGW_Attachment-1&2 Page 123/198
15.2 Protocol/Network Analyzer To trace signaling between different TDM and IP nodes and to monitor network performances BTCL requires a protocol analyzer under this purchase. The analyzer should be of portable type and will provide easy access to network nodes. Detail requirements of the analyzer are described in subsequent clauses.
15.2.1 The following features must be included:
a) Battery and Battery Charger with necessary cables, minimum backup time 3 hours b) Protective Bag.
15.2.2 The analyzer should include at least the following packages:
a) VoIP Analyzer b) PSTN Analyzer c) ISUP Testing d) ISUP / TCAP Decodes e) SIP Testing and Generation f) SIP-T Testing g) H.323, MGCP, Megaco Testing and Generation h) Binary Megaco Testing i) Multi-Gateway Support for Megaco and MGCP j) Media Testing k) Voice Quality Testing l) M3UA Support for ISUP and TCAP m) H.263 Video Testing Package n) Percentage of IP packet loss
15.2.3 The analyzer should support at least the following test suites:
a) H.323
Terminal/Gate-Keeper based on ETSI TIPHON TS 101 804 (H.225.0)
Originating/Terminating Endpoint based on ETSI TIPHON TS 101 890 (H.245)
NFV_IGW_Attachment-1&2 Page 124/198
b) SIP
User Agent, Proxy, Registrar, Redirect Server based on ETSI TIPHON TS 102 027
c) MGCP
Media Gateway Controller, Media Gateway based on:
Packet Cable TGCP-MG-CTP PKT-CTP-TGCPMGD08-030103
Packet Cable TGCP MGC and Call Flows CTP PKTCTP-TGCP-MGC-CF-D05- 030103
Megaco/H.248–Media Gateway Controller, Media Gateway based on ETSI TIPHON TS 101 889
d) SS7 ISUP
ISUP Call Processing based on:
ITU-T Q.784.1, July 1996
ITU-T Q.785.2, March 1999
ETSI EN 300 356-35 v.3.1.2, September 2000
ETSI EN 300 356-32 v.3.0.4, September 2000
15.2.4 The analyzer should support (or comply with) the following specifications:
a) H.323
ITU-T H.323 Version 2, February 1998
ITU-T H.323 Version 3, September 1999
ITU-T H.323 Version 4, November 2000
ITU Implementer‟s Guides July 1999, March 2000, December 2000, October 2002
b) SIP
IETF RFC 2246 (TLS Protocol)
IETF RFC 2543 (SIP: Session Initiation Protocol)
NFV_IGW_Attachment-1&2 Page 125/198
IETF RFC 2976 (SIP INFO Method)
IETF RFC 3261 (SIP: Session Initiation Protocol)
IETF RFC 3262 (Reliability of Provisional Responses in SIP)
IETF RFC 3264 (An Offer/Answer Model with the Session Description Protocol (SDP))
IETF RFC 3265 (SIP-Specific Event Notification)
IETF RFC 3268 (AES Cipher suites for TLS)
IETF RFC 3310 (HTTP Digest Authentication Using Authentication & Key Agreement )
IETF RFC 3311 (SIP UPDATE Method)
IETF RFC 3323 (Privacy Mechanism for SIP)
IETF RFC 3325 (SIP Asserted Identity)
IETF RFC 3326 (Reason Header Field for SIP)
IETF RFC 3428 (SIP Message Extension)
IETF RFC 3515 (SIP Refer Method)
IETF RFC 3546 (Transport Layer Security (TLS) Extensions)
IETF RFC 3903 (SIP: Session Initiation Protocol Extensions)
IETF RFC 4168 (Stream Control Transmission Protocol (SCTP))
IETF RFC 4475 (Session Initiation Protocol (SIP) Torture Test Messages)
c) SIP-T
IETF RFC 2046 (Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types)
IETF RFC 3204 (MIME media types for ISUP and QSIG Objects)
IETF RFC 3372 (Session Initiation Protocol for
Telephones (SIP-T): Context and Architectures)
NFV_IGW_Attachment-1&2 Page 126/198
IETF RFC 3398 (ISUP to SIP Mapping)
IETF RFC 3578 (ISUP Overlap Signaling to SIP)
d) MGCP
IETF RFC 2705 (Media Gateway Control Protocol (MGCP))
IETF RFC 3435 (MGCP 1.0)
e) Packet Cable
PKT-SP-TGCP-I01-991201
PKT-SP-EC-MGCP-I03-010620
f) Megaco/H.248 (Binary and Text Encoding)
IETF RFC 3015 (Megaco Protocol Version 1.0)
IETF RFC 3525 (Gateway Control Protocol)
ITU-T H.248, June 2000
ITU-T H.248.1, March 2002
ITU-T H.248.1, May 2002
ITU-T H.248.1 v2 Corrigendum 1, March 2004
g) Multi-Protocol Label Switching (MPLS)
IETF RFC 3032 (MPLS Label Stack Encoding)
h) SS7 ISUP
ITU-T Q.763, December 1999
NTT/TTC JT-Q.701 - 704, April 1992
NTT/TTC JT-Q.707, November 1990
NTT/TTC JT-Q.761 - 764, November 1999
NTT/TTC JT-Q.850, November 1996
UK ISUP
NFV_IGW_Attachment-1&2 Page 127/198
i) M3UA Transport
IETF RFC 3332 (SS7 MTP3-User Adaptation Layer)
j) SCCP Protocol Support
ITU Q.711, March 2001
ITU Q.712, July 1996
ITU Q.713, July 1996
ITU Q.714, May 2001
ITU Q.715, July 1996
ITU Q.716, March 1993
11. TCAP Protocol Support
ITU-Q.771, June 1997
ITU-Q.772, June 1997
ITU-Q.773, June 1997
ITU-Q.774, June 1997
ITU-Q.775, June 1997
12. SCTP Protocol Support
IETF RFC 2960 (Stream Control Transmission Protocol), 2000
IETC RFC 3257(SCTP Applicability Statement), April 2002
IETF RFC 3309 (Stream Control Transmission Protocol (SCTP) Checksum Change), 2002
k) Voice Media
IETF RFC 2327 (SDP: Session Description Protocol)
IETF RFC 2833
ETF RFC 3550 (RTP)
IETF RFC 3551 (RTP A/V Profile)
NFV_IGW_Attachment-1&2 Page 128/198
ITU-T G.729 Annex A, November 1996
ITU-T G.723.1, March 1996
ITU-G.711, November 1998
ITU-T G.726
AMR-NB
AMR-WB
l) Voice Quality
ITU-T P.862, February 2001
ITU-T G.107, March 2003
m) Video Telephony
ITU-T H.263 / H.263+
IETF RFC 2429 (H.263+)
IETF RFC 3261 (SIP: Session Initiation Protocol)
IETF RFC 2327 (SDP: Session Description Protocol)
IETF RFC 3550 (RTP)
IETF RFC 3551 (RTP A/V Profile)
Microsoft AVI file format – Audio Video Interleaved
15.2.5 The analyzer should support the following Interfaces:
a) Signaling and Trunk Interface Circuit Card (STI) i) 10/100BaseT Ethernet ii) DS3 iii) Quad DS1/E1 iv) 100 bus to DSP Resource b) Wideband Trunk Interface (WTI) i) WTI OC-3 or STM-1
2,016 channels per board
NFV_IGW_Attachment-1&2 Page 129/198
Supports simultaneous TDM media
ii) WTI RTP
Supports 4,000 simultaneous RTP streams with media per board
Electrical Gigabit Ethernet interface
iii) WTI for Signaling
VoIP signaling with RTP analysis
Gigabit Ethernet interface
iv) WTI T1/E1
240 (E1) simultaneous calls per card, Scales to 6 boards for a total 1,440 (E1) timeslots per system
All the test procedures must be stated clearly in the operating manual of the protocol Analyzer. Bidder must demonstrate all test bed preparations, testing during local training of the protocol analyzer to BTCL engineer. The bidder shall quote the unit price of the test equipment. Each deviation from the requirements stated under Clause-15 shall be treated as “Major Deviation”
15.3 Bidder shall propose required set of specific tools and testers for all equipment to run IGW platform smoothly.
-- End of Sub-Section 15 --
NFV_IGW_Attachment-1&2 Page 130/198
SUB-SECTION 16
Requirements of the Short Message Service Gateway (To Be Quoted Optionally)
16.1 Introduction International Short message services (SMS) would also be routed through International Gateway Exchanges (IGW). BTCL, therefore, needs to procure and set up a Short Message Service (SMS) Gateway. Detail requirements of the SMS Gateway are described in the subsequent clauses.
16.2 Functional requirement The SMS Gateway will be responsible for routing the SMS traffics of SMS Gateways of IOS/ICX and overseas operators. After receiving SMS from an SMS Gateway it will route it to its destination. The forwarding may be based on number segments of the network operators. Response of the destination SMSC/Gateway will then be sent back to the source SMS Gateway.
16.3 Interfaces All the interfaces the bidder offers in his solution will be based on open and standard interface and protocol. The protocol between IGW SMS Gateway and Gateway of IOS/ICX operator would be SMPP (Short Message Peer to Peer) or any other open standard protocol that provides bidirectional interface to implement submission and delivery of short messages. The physical layer connectivity between the IGW Gateway and IOS/ICX Gateway shall be TDM interface. Any disagreement or deviation shall be treated as “Critical Deviation”.
16.4 Network Connectivity The proposed SMS Gateway must be able to support connection with at least 16 (Sixteen) GSM, CDMA, CDMA (WLL) operators, SMSC/ Gateways and ICX operators. Estimated Number of SMS to be processed per second will be at least 250 for originating and 250 for terminating. Length of an SMS would be 160 characters at maximum.
Bidder must make necessary survey to learn about the SMPP (or other protocol interfaces) versions and the physical layer interfaces used by the network
NFV_IGW_Attachment-1&2 Page 131/198
operators mentioned in the table. Bidder should note that it any mismatch (if occurs) during the connection implementation with the SMSC/Gateways, it has to be solved by them. Any disagreement or deviation to this should be treated as “Critical Deviation”
16.5 Software Capability The system software(s) shall be modular in structure and shall be capable of merging new files and programs with existing files at the site without any interruption of service in the following cases.
a) Expansion or change of Capacity b) Loading of new software patches or changes of program version c) Changes and employment of new service features.
Deviation from such capability shall be considered as “Critical Deviation”.
16.6 Redundancy & Protection against failure 16.6.1 The SMS Gateway must follow redundant design philosophy. There shall be no degradation of service during fault condition in any one or more of the system modules or servers. Change-over from main to standby modules or Servers should not affect system‟s performance. Any deviation of the above item shall be treated as “Critical Deviation”.
16.6.2 The system should be of fault tolerant design. It will have the facility for automatic, manual and cold restart. The automatic restart shall be initiated by appropriate fault conditions and manual restart shall be activated either by MML command or system reset. The restart procedure will be as follows:
a) The system shall use memory elements resident inside the system to start the recovery protocol. b) If recovery is not possible from resident memories, the system shall read relevant files from one or any of the primary storage devices (Hard Disk Drive). c) If primary storage devices are finally inaccessible due some reason, the recovery protocol shall automatically seek to read files from secondary storage device. The Bidder may propose an alternate system for back-up.
The bidder in his bid shall explain the restart procedure for its system in detail. Any Disagreement or deviation should be treated as “Major Deviation”.
NFV_IGW_Attachment-1&2 Page 132/198
16.7 Alarm Supervision The system shall be provided with supervision software to continually check the normality of hardware and software. In case of any error, trouble, fault or failure an appropriate "alarm indication" shall be generated. The indication shall be notified by printed messages and by visual & audible means. Appropriate procedures shall be applied to cancel audible alarms. All alarm indications may be classified into the following categories and any deviation shall be treated as “minor”.
a) "CRITICAL" - indicating a very serious failure or fault which can result in system failure & stoppage of call processing and demanding immediate attention of O & M personnel. b) "MAJOR" - indicating a serious fault or trouble demanding immediate action and which can lead to critical fault if kept unattended for long time. c) "MINOR" - indicating fault or trouble not requiring immediate action.
16.8 Network Management facilities The system should provide with means of management on the information service system for operation and maintenance. The user should be able to query the running status, configuration, performance of the system, alarms and interface connections. Besides, the Gateway should be connected to the Network Management System (NMS) under this purchase. The interface to the NMS will be based on GUI (Graphical User Interface) or MML (Man-Machine Language). Disagreement or deviation to the requirements will be treated as “Critical Deviation”.
16.9 Password Protection The main features and data of the software shall be protected by multi-level password control. Modification of the Office data shall also be protected by passwords. The system password will not be erased or corrupted during system re-initialization and/ or OMM switchover or for any other reasons. Deviation shall be considered as “Critical Deviation”.
NFV_IGW_Attachment-1&2 Page 133/198
16.10 CDR The Gateway must have the hardware to store CDR for every incoming/outgoing SMS to any destination for billing purpose. This CDR would be stored on the system storage for at least 15 days. After the specific period the CDRs would be removed from the system storage automatically or manually.
The Billing Server (not under this purchase) will pull the CDR periodically over FE/GE or any other standard interface. The bidder shall calculate the storage capacity according to 500 SMS/Second and recordable duration shall be 30 days. So, for these 30 days all data must be available in the CDR storage. Absence of such features will be considered as “Critical Deviation”.
16.11 Expansion of Capacity Initial processing capacity of the proposed system will be 500 SMS per second. The bidder in its bid shall also quote price for an additional processing capacity of 200 SMS per second. This price should include all necessary costs for hardware, software or up-gradation of software, license, installation and services. Failure to quote such price will be considered as “Critical Deviation”.
======End of Sub-Section 16 ======
NFV_IGW_Attachment-1&2 Page 134/198
SUB-SECTION 17
Requirements of Ancillary Facilities
17.1 SDH MUX 17.1.1 The SDH equipment shall support the drop and insert of various SDH streams on one single platform and shall be installed at Moghbazar. It shall support the following features:
a) The equipment shall have the capability to operate with the Router Interfaces as specified in this document.
b) The equipment should conform to technical requirements/ parameters in all respects for long haul.
c) It shall be possible to configure the equipment as either Terminal Mux (TM) or Add Drop Mux (ADM)
d) Support for E1, E3, DS3, STM-1 (e), STM-1 (o) and STM-4 with detail capability as specified in the interface requirements.
e) The System should support full low order (VC-12) connectivity in a single shelf /sub rack and it should allow direct mapping of any 2 Mbps into any STM-1.
f) All traffic affecting common cards shall support 1+1 protection scheme
g) All the optical interfaces will be for short haul.
17.1.2 Interface Requirements - Optical interfaces:
The Multi-service SDH transport system shall support multiple optical interfaces in the same platform. The system shall be capable of supporting following interfaces in the SDH equipment:
a) STM-1 interfaces with the following features:
i) Compliant with ITU-T G.957, G.703 SDH specifications.
ii) The aggregate interface should be as per ITU-T G.957
iv) For STM-4 equipment STM-1
NFV_IGW_Attachment-1&2 Page 135/198
v) On each SDH transport equipment. Each port shall have a transmitter and receiver interface.
vi) All traffic - affecting common cards shall support 1+1
b) STM-4 interfaces with the following features:
i) Compliant with ITU-T G.957 SDH specifications.
ii) The aggregate interface should be as per ITU-T G.957
iii) These should be capable of following tributaries
iv) On each SDH transport equipment. Each port shall have a transmitter and receiver interface.
v) All traffic - affecting common cards shall support 1+1 protection scheme.
17.1.3 Input Voltage For SDH Equipment
The input voltage will be – 48 VDC.
17.1.4 Provision for Equipment Craft Terminal
The maintenance staff shall be able to access the management functions via the PC-Interface through a portable Equipment Craft Terminal (ECT).
17.1.5 Alarms
The following alarm indications according to G.784 shall be provided but not limited to:
i) TF (Transmit Fail)
ii) LOS (Loss of Signal)
iii) EBER (Excessive Bit Error Ratio)
iv) SD (Signal Degrade)
v) LOP (Loss of Pointer)
vi) LOF (Loss of Frame)
vii) FERF (Far End Receive Failure)
viii) MIS (Mismatch path trace ID/signal lebel)
ix) LOM (Loss of Multiframe)
x) LOT (Loss of Tributary)
NFV_IGW_Attachment-1&2 Page 136/198
xi) TIF (Timing Input Failure)
xii) AIS (Alarm Indication Signal)
17.1.6 Quality Control
Quality Assurance Systems shall comply with ISO-9000 or any other equivalent international standard. Quality control hardware and software shall comply ISO- 9001 or any other equivalent international standard.
17.1.7 Optical Safety (Automatic Laser Shutdown) Requirements
a) Generally if the section is interrupted (e.g. if a fiber breaks), then measures shall be implemented to ensure that no risk is caused by laser light escaping uninterruptedly. b) In the event of an optical signal fail at the incoming port with a duration of < 500 ms, and certainly within 600 ms, the laser in the opposite direction is switched off by the receiver within 0.85 seconds, and the affected segment will be thus shutdown. It shall not be possible to activate the forced facility during error-free operation.
17.2 Optical Distribution Frame (ODF) The Bidder shall provide necessary termination facility (Optical Distribution Frame) for terminating optical fibers.
a) Each of the ODF shall have the following criteria and any deviation shall be treated as “Major Deviation”.
i) Adopting the popular 19” rack ii) Should have splicing and distribution module iii) Stable equipment for fixing, stripping and grounding of the optical fibers iv) Suitable for ribbon and non-ribbon optical fibers v) Suitable for installation of FC, SC and ST adaptors vi) Optical fibers, fiber optic pigtails and jumpers are separate, without disturbing each other vii) Fiber optic cable management b) Each of the ODF shall be properly grounded as per standard specification specified in this document.
NFV_IGW_Attachment-1&2 Page 137/198
c) The ODF shall preferably be located inside the transmission room of BTCL, but it can also be shifted to any other suitable room on mutual agreement. The maximum distance between the switch position and the ODF shall be kept to 30 meters. d) The supply shall include ODF termination facility for the final capacity of LAN ports of the switch and total number of optical ports at different equipment. e) The bidder shall terminate the equipped LAN ports (optical) to its installed ODF. f) Necessary Optical Fiber with appropriate connectors should be provided by the bidder. The bidder shall supply 60 (Sixty) percent more than that of the initially required fibers and connectors.
17.3 CAT6 Network Cable The bidder shall supply 10 Box (each Box contains 100 meter) CAT6 network cable for BTCL‟s internal use. 17.4 ETSI 19 inch standard racks The bidder shall supply required number of rack at each site to house all the equipment to be supplied under this tender.
17.5 Minimum Capacity Requirement of the Mux a) Switching Capacity (IP Packet): 100 Gbps b) Switching Capacity (TDM): 20~200 Gbps c) Number of service slots (for processing): 15 d) Number of service slots (for interfacing): 16 e) Number of STM-1 Interface: 16 f) Number of STM-16 Interface: 02 g) Number of Ethernet GE Interface: 02+02
Any deviation shall be treated as “Critical Deviation”.
=== End of Sub-Section 17 ===
NFV_IGW_Attachment-1&2 Page 138/198
SUB-SECTION 18: Deviations and Reservations
This Sub-Section will be used for evaluation in addition to the other evaluation criterion stated in ITT and TDS of the Tender Document. Criteria for evaluation of Technical Parts of Bids and Selection of Successful Bidder are as follows:
18.1 Notwithstanding whatever is stated in other clauses of the tender documents, the criteria for evaluation of substantial responsiveness of the received bids of this tender shall be according to clauses described in this sub-section. If any bidder refuses to agree to any clauses of this sub-section, his/her bid shall automatically be considered as “non responsive”.
18.2 During evaluation, BTCL shall consider bidders‟ compliances to various clauses and sub-clauses of this tender; but shall have the authority to conclude its own decision about such compliances.
18.3 a) If the bidder does not give any statement to its compliance to any of the tender clauses or sub-clauses according to Clause by clause Compliance Schedule mentioned in Form G of this document, its' compliance to that clause/ sub-clause (as applicable) shall be treated as “non responsive”.
b) The bidder shall also fill up Information of Equipment, Accessories and Country of origin declaration as mentioned in Form F of this document. Disagreement or failure to submit Form F shall be treated as “ non responsive”.
18.4 If the bidder puts any condition to his compliance to any of the tender clauses and/ or sub-clauses, its' compliance shall be treated as “non compliance” to that particular clause and/ or sub-clause.
18.5 BTCL shall also consider the contents of various attached documents. If any content of the attached documents contradicts the compliance statement of the bidder to any of the clauses and/ or sub-clauses, the bid shall be treated as “non compliance” to that particular clause and/ or sub-clause. In all of such cases, BTCL‟s decision shall be final.
18.6 TEC shall have the right to examine the authenticity of issuance and contents of all certificates. BTCL shall have the right to choose methods, timings and procedures of examining such authenticity. The procedure may include (but not
NFV_IGW_Attachment-1&2 Page 139/198
limited to) among others, making direct contacts to relevant persons or gathering information from other sources like web sites, other web publishes, technical journals, newsletters of industry, professional or trade organizations etc.
18.7 TEC shall have the authority to contact the persons/ organizations issuing those certificates to ascertain the authenticity of any or all submitted certificates. The bidder shall keep informed the relevant contact persons about the possible contact by TEC.
18.8 If, in answer to any query by BTCL, the bidder provides any or many clarifications to its bid, BTCL shall consider those clarifications. However, if such clarifications contradict the relevant statements given in his original offer, the clarification(s) shall be disregarded.
18.9 The following deviations of any offer will be treated as “minor deviation” of the bid:
a) Any deviation which has already been termed as “minor deviation” in this tender document.
b) The non-compliant of any clause/sub clause of this tender document having no weight as minor deviation or major deviation or Material Deviation or critical deviation shall be considered as minor deviation.
c) Every item of “minor deviation” shall earn a score of 1 (one) “Penalty point”.
18.9 The following deviations of any offer will be treated as “major deviation” of the bid:
a) Any deviation which has already been termed as “major deviation” in this tender document.
b) If the bid BoQ has any shortage of quantity in any of the required hardware and/or software (for each of such short quoted item) unless otherwise specified in the tender.
c) Any item of “major deviation” shall earn a score of 5 (five) “penalty points”.
18.10 The following deviations of any offer will be treated as “critical deviation” of the bid:
a) Any deviation which has already been termed as “critical deviation” in this tender document.
NFV_IGW_Attachment-1&2 Page 140/198
b) If the Bidder has changed either the language or format of any of the different forms attached with this document.
c) Any item of “Critical deviation” shall earn a score of 40 (forty) “penalty points”.
18.10 The following deviations of any offer will be treated as “Material Deviation” of the bid:
a) Any deviation which has already been termed as “Material Deviation” in this tender document. The list of Material Deviation has been given in Annex 1.13.
b) If the bidder refuses to provide answers to any requested clarification(s).
c) If any Certificate or any other document attached as part of the bid is found to be false or unauthentic.
d) The items and quantities are clearly specified in different forms. If any bidder fails to quote any item(s) completely, it will be considered as “Material Deviation”.
18.11 A bid containing any item of “Material Deviation” shall be treated as “non responsive”.
18.12 The penalty points earned by each clause/sub-clause shall be added to get total penalty points. The bid of any bidder which has earned equal to or more than 80 (Eighty) penalty points in total shall be treated as “non responsive”.
18.13 BTCL‟s decision to treat any bid as “non responsive” shall be final.
18.14 The bid(s) treated as “non responsive” shall not be considered for further evaluation.
18.15 A bid, not treated by BTCL as “non responsive”, shall automatically be considered as “Responsive”.
=== End of Sub-Section 18 ===
NFV_IGW_Attachment-1&2 Page 141/198
Annex 1.1: Capacity Requirements of the Media Gateway Controller
Bidder’s Sl Items Unit Required Offer
Media Gateway Controller
1 Minimum BHCA Million unit 3.5
Minimum number of 2 Number 20,000 simultaneous call
Minimum Trunk Capacity
3 (70% of which is SIP-I/T Number 36,000 and 30% is H.323.)**
Minimum Trunk Capacity 4 Number 15,600 (TDM)
Minimum Number of 4 Number 10 Gateway Handling Capacity
Minimum Number of GE/FE 5 Number 1+1 Port
**If during operation, it is found that the mix of IP trunk is different from above, the bidder has to adopt that mix without any charge.
NFV_IGW_Attachment-1&2 Page 142/198
Annex 1.2: Capacity Requirements of Media Gateway
Media Gateway at Moghbazar
Sl. Items Unit Required Bidder's Offer
A. Media Gateway Capacity
A.1 Trunk Capacity
1 STM-1 Trunk (optical Interface) Number 16
2 Min. Number of GE port (For Traffic Only) Number 2+2
The Bidder has to mention the present and final Processing capabilities for required configuration of the offered Equipment.
NFV_IGW_Attachment-1&2 Page 143/198
Annex 1.3: Capacity Requirements of each Gateway Router
Sl. Items Unit Required Bidder's Offer
A Router Requirement
A.1 Processing Capabilities 1 Switching Gbps 320 Backplane 2 Packet Switching Mpps 150 and forwarding performance
3 Flash Memory MB 512
4 RAM MB 2000
A.2 Interface capabilities* 1 GE Optical Port 4 Interface
2 STM-1 trunk Port 4 interface
3 Channelized STM-1 4 Interface
*Same type of interface shall be configured at least in two separate modules
NFV_IGW_Attachment-1&2 Page 144/198
Annex 1.4: Capacity Requirements of each LAN Switch at Moghbazar
Serial Description of items Unit Quantity Configuration 1 Chassis Set 1 2 Control and Switch Piece 2 1+1 redundant mode Module 3 DC power supply Piece 2 1+1 redundant mode 4 GE optical interface Port 12 Two separate module with 2+2 redundant mode 5 10/100/1000TX Port 32 Two separate module with Interface 16 redundant mode 6 System Software Set 1
* There shall be minimum 4 (four) slots free after initial configuration for future expansion
NFV_IGW_Attachment-1&2 Page 145/198
Annex 1.5: Capacity Requirements of each Firewall
Sl. Items Unit Required Bidder's Offer
A Firewall Present Capacity
A.1 Processing Capabilities 1 Minimum Cleartext Gbps 3 throughput 2 Minimum Nos 750,000 Concurrent connections/Sessio ns
3 Minimum system Mbps 500 performance with 128 / 256 -bit IPSec encryption 4 Minimum Tunnels Nos 3000
5 Minimum Redundant Nos 4 FE port
6 Minimum Redundant Nos 8 GE port
NFV_IGW_Attachment-1&2 Page 146/198
Annex 1.6: Capacity Requirements of each SBC
Sl. Items Unit Required Bidder's Offer
Session Border Controller
1 Minimum Concurrent Number 36000 Session 2 Total Converted Basic Number 1500 Session traffic K (BHSA)
3 Average bandwidth per Number 200 session (Kbps/session)
4 Maximum Number of Number 4095 VRF instances supported
5 Maximum Number of Number 6000 access-side IP address
NFV_IGW_Attachment-1&2 Page 147/198
Annex 1.7: Format for Maintenance Support during Guarantee Period
The Contractor, at his own cost to be quoted during the bid offer, shall provide the following maintenance supports during the whole Warranty/ Guarantee Period of the Contract: a) The supports shall start from the date of cutover into commercial service of the first equipment/ system purchased under this contract. b) The period of the service shall continue uninterrupted for 02 (Two) calendar years from “the date of effect” of the last Provisional Acceptance Certificate (PAC) of the contract. c) For providing this service, the contractor shall start an office in Dhaka, within 10 (ten) days of putting the first equipment in to commercial service. d) The office must be equipped with necessary logistics support. e) The service shall cover full trouble-shooting and corrective maintenance support for all equipment and sites covered by this purchase. f) The manpower dedicated for this service only and shall not be part of any other implementation, installation and commissioning team of the Contractor, but shall be a completely separate team of people dedicated for this purpose only. g) All personnel of that team must have proper training and must have prior experience in Trouble-shooting, Operation and Maintenance of the relevant systems. h) The typical type and experience, minimum number and the locations of the required personnel shall be as follows :
i) 01 (one) expatriate Expert, having at least 03 (Three) years experience in providing O&M support to customers, to be stationed in Dhaka and to act as the Chief of the Maintenance support team.
ii) 02 (two) expatriate/ local Engineers, 1 each for Hardware and Software, having at least 3 (Three) years experience in relevant equipment, to be stationed in Dhaka.
NFV_IGW_Attachment-1&2 Page 148/198
iii) All the personnel must speak fluent English and/ or Bangla.
i) The Contractor shall submit the bio-data of the Engineers to BTCL at least 15 (fifteen) days before intended start of the services and obtain necessary approval of personnel. j) The contractor shall be responsible for all types of expenditure to be borne for these manpower, including office, overhead, all modes of transportation etc. However, BTCL will try to provide the relevant space. k) The services to be provided (but not limited to) shall be :
i) Equipping and Maintaining an updated inventory of spares and accessories in Dhaka at a premise mutually agreed upon with BTCL. The inventory, at all time, shall include at least 1 (one) unit of replace spares/ cards/ modules.
ii) Replacement of faulty cards/ modules/ equipment/ system within the specified time period.
iii) Regular and required replenishment & updating of the spare & accessories inventory.
iv) Periodic and Regular checks on the performance of the systems to ensure that they are running in good condition and are not susceptible to any major fault.
v) Transfer of technology to BTCL‟s personnel to enable them to become self-sufficient in fault finding and fault removal.
vi) Short on-the-job training to BTCL‟s personnel as and where and when necessary.
vii) Trouble-shoot and debug any faults occurring in the equipment/ system within the time-period specified in the contract.
viii) Identify the faulty elements in installation of the system and take actions for rectification.
ix) Assist BTCL‟s personnel in subsequent re-installation, re-location of different network elements and other minor works, whenever and wherever desired by BTCL.
NFV_IGW_Attachment-1&2 Page 149/198
x) Accompany and assist BTCL‟s personnel in network performance tests.
xi) Assist BTCL‟s personnel in identifying the Key Performance Indicators of the system and take corrective actions for network optimization.
xii) Help and advice BTCL personnel to properly maintain O&M & CDR data bases and Management of CDRs
xiii) Regularly inform BTCL of all types of Software and Hardware upgrades of the equipment/ system and suggest actions to be taken by BTCL.
xiv) Assist and train BTCL‟s personnel in planning expansion activities.
xv) Guarantee the flow and availability of all spare parts and units without major design changes for at least 8 (Eight) years from the issuance of Provisional Acceptance Certificate (PAC).
xvi) Guarantee that, if there is any major design change or stoppage of production, the contractor will bear all the costs related to provision of alternate solutions. l) The format of the support services to be given by the contractor shall be as follows :
i) Chief of the Maintenance support team shall regularly visit the relevant system sites and carry out regular health-checks of the systems.
ii) On occurrence and/ or detection of any fault to any or many system/ equipment supplied to BTCL‟s network, under the contract the representative(s) of the first party shall inform the representative(s) of the second party, over telephone, of such fault.
iii) All such reports will be logged by both parties, mentioning the time of such reports.
iv) The personnel of the second party, on being informed by the first party, will attend to any fault of any or many equipment at any or many sites. Normally, the second party will send its technical personnel to site within 02 (two) hours after reporting of the fault. If the fault is reported after 20:00 Hrs or on weekly holidays, the response time can be extended up to 04 (four) hours. On abnormal cases and for occurrences in long holidays, the maximum allowable response time period shall be 12 (twelve) hours from
NFV_IGW_Attachment-1&2 Page 150/198
the time of report of fault by the first party.
v) The procedures for removal of faults shall be as follows:
1) If the fault is of minor nature and has not caused any stoppage of service by the relevant equipment, the second party will rectify the fault within 12 (twelve) hours from the time of reporting of the fault.
2) If the fault has caused stoppage of service by the relevant equipment, the second party shall change the faulty unit from its reserve stock and take away the faulty unit for subsequent repair. Such replacement will be done within 4 (four) hours from the reporting of the fault.
vi) For any delay beyond 12 hours, the first party shall preserve the right to impose financial penalty on the second party. Such penalty shall be as per discretion of the first party.
vii) If such delays become regular phenomenon, the first party shall have the right to terminate the contract and impose financial penalty on the second party as per discretion of the first party.
viii) The second party shall bear all costs related to such services, including costs for spares & accessories, personnel, transportation, equipment and logistics. However, BTCL may offer spaces to house the relevant inventory & personnel.
ix) The second party shall provide its personnel with mobile telephone facilities.
NFV_IGW_Attachment-1&2 Page 151/198
Annex 1.8: Format for Annual Maintenance Support after Guarantee Period
The Contractor, at his own cost to be quoted during the bid offer, shall provide the following maintenance supports after expiry of the Warranty/ Guarantee Period of the Contract :
1) The details of the support services shall be agreed upon between the contractor and BTCL before expiry of the Warranty/ Performance Guarantee period of the contract.
2) The period of the services shall be for a minimum of 1 (one) year and shall be renewable on per year basis for at least 5 (five) years.
3) The unit prices and other terms and conditions of the services shall remain unchanged for the first three years after the guarantee period. Unit price for annual maintenance support after the guarantee period shall be quoted optionally.
4) The support services shall start from the next day of the date of expiry of the performance guarantee period of the contract.
5) For providing this service, the contractor shall dedicate a liaison personnel and an office in Dhaka, at least 15 (fifteen) days before expiry of the Warranty Period of the contract.
6) The liaison office and personnel must have mobile telephone number(s). The liaison personnel must have at least 3 (Three) years experience in O&M of similar systems and fluent in English and/ or Bangla.
7) The service shall cover full on-demand trouble-shooting, debugging and other corrective maintenance support for all equipment and sites covered by this purchase.
8) The service shall include 24 hrs per day x 7 days per week x 52 weeks per year “Phone-in support desk” service to be located at place of contractor‟s choice.
9) The service shall also include “On Demand” and “As and when necessary” on-site personnel support (local and/ or expatriate, as the requirement may be) to provide trouble-shooting, debugging and other corrective maintenance services.
10) All personnel of the phone-in support desk must have proper training and must
NFV_IGW_Attachment-1&2 Page 152/198
have prior experience in Trouble-shooting, De-bugging, Operation and Maintenance of the relevant systems.
11) The language of contact shall be either English and/ or Bangla.
12) The services to be provided shall also include (but not limited to) :
a) Equipping and Maintaining an inventory of emergency spares and accessories in Dhaka at a premise mutually agreed upon with BTCL. The inventory, at all time, shall include at least 1 (one) unit of replace spares/ cards/ modules.
b) Replacement of faulty cards/ modules/ equipment/ system within the specified time period.
c) Regular and required replenishment & updating of the spare & accessories inventory.
d) Transfer of technology to BTCL‟s personnel to enable them to become self- sufficient in fault finding and fault removal.
e) Short on-the-job training to BTCL‟s personnel as and where and when necessary.
f) Trouble-shoot and debug any faults occurring in the equipment/ system within the time-period specified in the contract.
g) Assist BTCL‟s personnel in subsequent re-installation, re-location of different network elements and other minor works, whenever and wherever desired by BTCL.
h) Regularly inform BTCL of all types of Software and Hardware upgrades of the equipment/ system and suggest actions to be taken by BTCL.
i) Assist BTCL‟s personnel in planning expansion activities.
j) Guarantee the flow and availability of all spare parts and units without major design changes for at least 8 (Eight) years from the issuance of Provisional Acceptance Certificate (PAC).
k) Guarantee the flow and availability of all equipment, materials and services required for any subsequent expansion of the offered equipment for at least 8 (Eight) years from the issuance of Provisional Acceptance Certificate (PAC).
l) Guarantee that, if there is any major design change or stoppage of production
NFV_IGW_Attachment-1&2 Page 153/198
(of spares and/ or equipment needed for expansion), the contractor will bear all the costs related to provision of alternate solutions.
13) The format of the support services to be given by the contractor shall be as follows :
a) On occurrence of any fault to any or many system/ equipment supplied to BTCL‟s network under the contract, the representative(s) of the first party shall inform the liaison office/ personnel of the second party, over telephone, of such fault.
b) All such reports will be logged by both parties, mentioning the time of such reports.
c) The personnel of the contractor, on being informed by BTCL, will log the problem/ fault with the “Phone-in Support Desk” service and inform the concerned personnel of BTCL of the relevant registration details. However, the support desk shall be advised to also log fault report(s) informed directly by the concerned personnel of BTCL.
d) If the relevant fault cannot be removed by assistance from the phone-in desk, the first party will inform the liaison personnel over telephone of such non-removal of fault. In such cases, the second party shall arrange to attend to the fault by sending its technical personnel to site within 02 (two) hours after reporting of the non-removal of the fault. If the fault is reported after 20:00 Hrs or during weekly holidays, the response time can be extended up to 04 (four) hours. On abnormal cases and for occurrences in long holidays, the maximum allowable response time period shall be 12 (twelve) hours from the time of report of fault by the first party.
e) If the fault cannot be removed by the assistance of contractor‟s local office, the contractor shall arrange necessary expatriate personnel within the time period specified in the contract.
f) If the fault removal involves changing of spares/ cards/ modules, such changes will be made from the local inventory within 4 (four) hours of detection of such requirement.
NFV_IGW_Attachment-1&2 Page 154/198
g) The procedures for removal of faults shall be as follows:
i) If the fault is of minor nature and has not caused any stoppage of service by the relevant equipment, the second party will rectify the fault within 12 (twelve) hours from the time of reporting of the fault.
ii) If the fault has caused stoppage of service by the relevant equipment, the second party shall arrange to change the faulty unit from its reserve stock and take away the faulty unit for subsequent repair. Such replacement will be done within 4 (four) hours from the reporting of the fault.
iii) If the removal of fault involves assistance of expatriate personnel, such personnel shall be made available within 7 (seven) days of detection of such requirement.
iv) If the removal of fault involves import of any additional spares/ cards/ modules, the contractor shall conclude all requirements at its own costs and make the relevant item(s) available in site within 15 (fifteen) days of detection of such requirement.
h) For cases where removal of fault involves phone-in and/ or local efforts only, for any delay in beyond 12 hours, the first party shall preserve the right to impose financial penalty on the second party. Such penalty shall be as per discretion of the first party.
i) For cases where removal of fault involves expatriate personnel, for any delay in beyond 15 days, the first party shall preserve the right to impose financial penalty on the contractor. Such penalty shall be as per discretion of BTCL.
j) If such delays become regular phenomenon, the first party shall have the right to terminate the contract and impose financial penalty on the contractor as per discretion of BTCL.
k) The contractor shall bear all costs related to such services, including costs for spares & accessories, personnel, transportation, equipment and logistics. However, BTCL may offer spaces to house the relevant inventories.
NFV_IGW_Attachment-1&2 Page 155/198
Annex 1.9: Declaration on Observance of Ethics
Whereas, We, M/s...... are submitting our bid in response to tender notice No. ………………………………, Dated …………………… for “Supply, Installation, Testing and Commissioning of NFV Enabled IP Based International Gateway Exchange in Bangladesh on Turn-Key Basis” and we hereby pledge that we shall not be engaged in :
A corrupt practice, which shall mean giving or promising to give, directly or indirectly, to any officer or employee of a procuring entity or other governmental/private authority or individual a gratuity in any form, an employment or any other thing or service of value, as an inducement with respect to an act or decision of, or method followed by, a procuring entity in connection with the procurement proceedings or contract execution;
A fraudulent practice which shall mean a misrepresentation or omission of facts in order to influence the procurement proceedings or the execution of the contract;
A collusive practice, which shall mean a scheme or arrangement between two or more tenderers, with or without the knowledge of the procuring entity, designed to rig tender prices thereby denying a procuring entity from the benefits of genuine competition; and
A coercive practice, which shall mean harming or threatening to harm, directly or indirectly, persons or their property to influence the procurement proceedings, or affect the execution of a contract.
Signature and seal
Dated ______Day of ______201____
Duly authorized to sign for and on behalf of M/s. ______
NFV_IGW_Attachment-1&2 Page 156/198
Annex 1.10: Declaration of Joint Liability
(Required only if the bid is submitted by a Joint Venture Consortium Association)
We, M/s ...... (name and address of the members of the Joint Venture Consortium or Association) .., are submitting our bid in response to BTCL's tender notice No. ------for Supply, Installation, Testing and Commissioning of NFV Enabled IP Based International Gateway Exchange in Bangladesh on Turn- Key Basis” and in order to fulfil the obligations stated in tender document and regulation of the Public Procurement Act 2008, we hereby declare our liabilities as follows :
...... (name and address of the lead company)...... shall represent us for all purposes related to this procurement proceedings.
All partners of the Joint Venture Consortium/Association shall be jointly and severally liable for the execution of the contract.
We shall be liable to share the penalty or loss thereof as per our shares in the joint venture company.
We shall not assign the contractor to any other party or parties.
We may appoint sub-contractors (if any) shall not absolve us from any of the responsibilities or liabilities due to us.
Signature and seal (Members of the Joint Venture Consortium or Association)
Date Day of 2019.
NFV_IGW_Attachment-1&2 Page 157/198
Annex 1.11: Bond for Spares
Whereas, we, ………………………………………………………………………….., are submitting our bid for Supply, Installation, Testing and Commissioning of NFV Enabled IP Based International Gateway Exchange in Bangladesh on Turn-Key Basis” and whereas we understand that as per relevant clause of the said tender document BTCL is in need of 2(two) year spares for warranty Period to be quoted in main offer, we enclose a list of such spares with our bid offer.
As per tender condition, if our offer is accepted, we hereby submit our guarantee that the supplied spares will be sufficient to run the system for initial 2(two) year of the guarantee period.
We also guarantee that the flow and availability of all spare parts and units without major design change for at least 8 (eight) years after the expiry of Warranty period and that, if there is any major design change or stoppage of production, we will arrange alternate solution with same price of original solution.
Signature and seal
Dated______Day of ______201 ______.
Duly authorized to sign for and on behalf of ______
NFV_IGW_Attachment-1&2 Page 158/198
Annex 1.12: Bond for Expansion Guarantee
Whereas, we, ...... , are submitting our bid for Supply, Installation, Testing and Commissioning of NFV Enabled IP Based International Gateway Exchange in Bangladesh on Turn-Key Basis” and whereas we understand that as per tender condition, if our offer is accepted, we hereby submit our guarantee for the flow and availability of all equipment, materials and services required for any subsequent expansion of its offered equipment for at least 8 (eight) years after the expiry of warranty of the system. If there is any major design change or stoppage of production, we will arrange alternate solution with same price of original solution.
.
Signature and seal
Dated Day of 201__
Duly authorised to sign for and on behalf of
NFV_IGW_Attachment-1&2 Page 159/198
Annex 1.13: List of Material Deviation
Sub-Section Clause/Sub-Clause Subject 2 2.7 Electrical Grounding 2.17 Spare Parts Guarantee 2.18 Expansion Guarantee 2.19.1 Maintenance Support during Guarantee Period 2.19.2 01 (One year) Annual Maintenance Support after Guarantee Period 2.20.2 Spare Parts and consumables and Maintenance Support up to Performance Guarantee Period 2.21.4 (g) and (l) Issuance of PAC 2.24 Inter – working with the Existing Systems 2.31 Unit Price for Future Orders 2.33 Additional Equipment needed for Turn-Key Completion 4 4.1.2 Openness 4.1.5 Fault monitoring and trouble shooting 4.1.8 Reliability and Redundancy
5 5.4 Operating Voltage 5.6 Guarantee for Software 5.7 License for Software 5.8 Language of Software 5.10 Guarantee for up-gradation of Software Version 6 6.2 Design Criteria of MGC 6.4.3 Network Time Protocol 6.5 BHCA Capacity 6.8 Protocol Processing Capability
7 7.1.3 TDM Interfaces 7.1.4 Packet Interfaces 8 8.1 Gateway Router 8.1.4 Protocols 8.1.9.4 Router Hardware configuration and Performance Requirement 8.2 LAN Switches 8.2.6 LAN Switch Hardware Configuration and Performance Requirement 8.3.1 Features of Firewall 8.4.2 Capacity of SBC 8.4.4 Limitations of SBC 8.5 Intrusion Detection System (IDS) 9 9.2.1, 9.2.3, 9.2.4, 9.2.5, Call Detailed Recording (CDR) facility 9.2.6, 9.2.7, 9.2.9 10 10.1 Inter-Node Signaling 10.2.1, 10.2.2, 10.2.3, Signaling, Protocol and Interfaces 10.2.4, 10.2.6 11 11.1.1 Switching System Translation Function
NFV_IGW_Attachment-1&2 Page 160/198
11.1.2 Traffic Routing Functions 11.2.1 Wrong Number Processing 11.2.8 Switching System Supervision 11.3 Fault Diagnosis Protocol
Sub-Section Clause/Sub-Clause Subject 12 12.1 Traffic Load Observation 12.9 Requirements of Call Monitoring System
13 13.2.1.1 Server System
13.2.2.1 Software Requirements of NMS 13.2.2.2 13.2.2.3 13.2.2.5 13.2.2.6
NFV_IGW_Attachment-1&2 Page 161/198
FORM A: Grand Summary Price of the Bid
Total Price SL Name of Item (s) USD + BDT
A Total Price for Equipment A.1 Total Price for Media Gateway Controller (from Form B.1) A.2 Total Price for Media Gateway (from Form B.2) A.3 Total Price for COTS Server (from Form B.3) A.4 Total Price for all Router, Switch and Firewall, Session Border Controller and Intrusion Detection System (from Form B.4) A.5 Total Price for BTRC Monitoring Facilities and LI Connectivity Facilities A.6 Total(from PriceForm forB.5) Network Management System (from Form B.6) A.7 Total Price for Other Equipment (from Form B.7) A.8 Total Price for DC Power and Air Conditioner (from Form B.9) A.9 Total Price for Auxiliary Installation Equipment (from Form B.10)
Total Price for Equipment (FoB)
B Total Freight (from Form B.1 to B.10)
X Total Price for Equipment (CFR)
C Total Price for Services C.1 Total Price for all Media Gateway Controller (from Form B.1) C.2 Total Price for Media Gateway (from Form B.2) C.3 Total Price for COTS Server (from Form B.3) C.4 Total Price for all Router, Switch, Firewall, Session Border Controller and Intrusion Detection System (from Form B.4) C.5 Total Price for BTRC Monitoring Facilities and LI Connectivity Facilities C.6 Total(from PriceForm forB.5 Network) Management System (from Form B.6) C.7 Total Price for Services of other equipment (from Form B.7) C.8 Total Price for other services (from Form B.8) C.9 Total Price for DC Power and Air Conditioner (from Form B.9) C.10 Total Price for Auxiliary Installation Equipment (from Form B.10)
Y Total Price for Services
Total Price for The Bid (X + Y)
In Words: US Dollar ...... and BD Taka ...... only
NFV_IGW_Attachment-1&2 Page 162/198
FORM B.1: Summary Price for Media Gateway Controller (MGC)
FOB Price in USD/ BDT SL Name of Item (s) Unit Qty Currency Unit Total Price Price A Total Price for Equipment A.1 Total Price for MGC Hardware A.2 Total Price for MGC Software A.3 Total Price for Auxiliary Equipment A.4 Total Price for Other Materials Total Price for Equipment (FOB)
B Total Freight
X Total Price for Equipment (CFR)
C Total Price for Services C.1 Total Price for MGC Services
Total Price for Installation, testing and C.2 commissioning Services
Y Total Price for Services
Total Price for MGC (X + Y)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 163/198
Form B.2: Summary Price for Media Gateway (MGW)
FOB Price in USD/ BDT SL Name of Item (s) Unit Qty Currency Unit Total Price Price
A Total Price for Equipment A.1 Total Price for MGW Hardware A.2 Total Price for MGW Software A.3 Total Price for Auxiliary Equipment A.4 Total Price for Other Material Total Price for Equipment (FoB)
B Total Freight
X Total Price for Equipment (CFR)
C Total Price for Services C.1 Total Price for MGW Services C.2 Total Price for Installation, testing and commissioning Services
Y Total Price for Services
Total Price for the MGW (X +Y)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 164/198
Form B.3: Summary Price for COTS Server
FOB Price in USD/ BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
A Total Price for Equipment
A.1 Total Price for COTS Hardware
A.2 Total Price for OS and Software
A.3 Total price for License
A.4 Total Price for Auxiliary Equipment
A.5 Total Price for Other Materials (if any)
Total Price for Equipment (FoB)
B Total Freight
X Total Price for Equipment (CFR)
C Total Price for Services
C.1 Total Price for COTS services
C.2 Total Price for Installation, testing and commissioning Services
Y Total Price for Services
Total Price for COTS Server (X + Y)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 165/198
Form B.4: Summary Price for Router, LAN Switch, Firewall, Session Boarder controller and Intrusion Detection System
SL Name of Item (s) Unit Qty FOB Price in USD/ BDT Currency Unit Total Price Price A Total Price for Equipment A.1 Total Price for Router Hardware A.2 Total Price for Router Software A.3 Total Price for LAN Switch Hardware A.4 Total Price for LAN Switch Software A.5 Total Price for Firewall Hardware A.6 Total Price for Firewall Software A.7 Total Price for SBC Hardware A.8 Total Price for SBC Software A.9 Total Price for IDS Hardware A.10 Total Price for IDS Software A.11 Total Price for Auxiliary Equipment A.12 Total Price for Other Material Total Price for Equipment (FoB)
B Total Freight
X Total Price for Equipment (CFR)
C Total Price for Services C.1 Total Price for Router Services C.2 Total Price for LAN Switch Services C.3 Total Price for Firewall Services C.4 Total Price for SBC Services C.5 Total Price for IDS Services C.6 Total Price for Installation, testing and commissioning Services
Y Total Price for Services
Total Price for Router, Switch and Firewall (X + Y)
In Word: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 166/198
Form B.5: Summary Price for BTRC Monitoring Facilities and LI Connectivity Facilities
SL Name of Item (s) Unit Qty FOB Price in USD/ BDT Currency Unit Total Price Price A Total Price for Equipment A.1 Total Price for BTRC Monitoring A.2 FacilitiesTotal Price Hardware for BTRC Monitoring A.3 FacilitiesTotal Price Software for LI Connectivity A.4 HardwareTotal Price for LI Connectivity A.5 SoftwareTotal Price for Auxiliary Equipment A.6 Total Price for Other Material (if any) Total Price for Equipment (FoB)
B Total Freight
X Total Price for Equipment (CFR)
C Total Price for Services C.1 Total Price for BTRC Monitoring C.2 FacilitiesTotal Price Services for LI Connectivity C.3 ServicesTotal Price for Installation, testing and commissioning Services
Y Total Price for Services
Total Price for BTRC Monitoring and LI Connectivity (X + Y)
In Word: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 167/198
Form B.6: Summary Price for Network Management System
SL Name of Item (s) Unit Qty FOB Price in USD/ BDT Currency Unit Total Price Price A Total Price for Equipment A.1 Total Price for Network Management Hardware A.2 Total Price for Network Management Software A.3 Total Price for CDR Management Hardware A.4 Total Price for CDR Management Software A.5 Other material (if any) Total Price for Equipment (FoB)
B Total Freight
X Total Price for Equipment (CFR)
C Total Price for Services C.1 Total Price for Network C.2 ManagementTotal Price for System CDR Management Services C.3 ServicesTotal Price for Installation, testing and commissioning Services
Y Total Price for Services
Total Price for the Network Management System (X + Y)
In Word: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 168/198
Form B.7: Detail List and Price for other Equipment
SL Name of Item (s) Unit Qty FOB Price in USD/ BDT Currency Unit Price Total Price A Total Price for Equipment A.1 Summary price for SDH MUX A.2 Summary price for CAT6 Cable A.3 Summary price for Optical Fiber Cable A.4 Summary price for Optical Fiber Connectors A.5 Price for Buffer Stock Maintenance Spares A.6 Summary price for spares and Consumables
A.7 Summary Price for Set of required specific tools and testers for all equipment Summary Price for Digital Multi-meter (with
A.8 clamp-on facility for AC/DC current measurement), Optical power meter, Multimedia projector and External HDD Summary price of Security and A.9 surveillance system including CCTV/IP Camera, DVR, HDD and Monitor A.10 Summary price for any other Equipment (if needed but not mentioned)
Total Price for Equipment FOB)
B Total Freight
X Total Price for Equipment (CFR)
C. Price of Service C.1 Bidder can quote price, required for any of the above item(s)
Y Total Price for Services
Total Price for the other equipment (X+Y)
In Word: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 169/198
Form B.8: Detail List and Price for other Service
FOB Price in USD/ EUR/BDT Name of Item (s) Unit Qty Currency Unit Total Price Price
A Total Price for Other Services A.1 Total Price for Maintenance assistance up to 02 (two) years Guarantee Period A.2 Total Price for 01 year Maintenance assistance after guarantee Period A.3 Total Price for Factory Premises Acceptance Test A.4 Total Price for Provisional Acceptance Test A.5 Total Price for Final Acceptance Test
A.6 Total Price for Factory Training
A.7 Total Price for Local Training Total Price for Other Services A
B Total Price for Other Services related to Turn-Key completion of the Project
(The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
B.1 Total Price for Survey, Network Planning and Design Services B.2 Total Price for Project Implementation Services B.3 Total Price for Inter-working Services B.4 Total Price for Inter-connection Services Sub - Total for B
Total price for Other Services (A + B)
In Words: US Dollar ...... and BD Taka ...... only
NFV_IGW_Attachment-1&2 Page 170/198
Form B.9: Summary Price for DC Power and Air Conditioner Equipment
FOB Price in USD/ BDT SL Name of Item (s) Unit Qty Currency Unit Total Price Price
A Total Price for Equipment A.1 Total Price for Rectifier Equipment A.2 Total Price for Backup Battery A.3 TotalEquipment Price for DC/ AC Inverter A.4 Total Price for Air Conditioner for Equipment Room A.5 Total Price for Air Conditioner for NMS Room Total Price for Equipment (FOB)
B Total Freight
X Total Price for Equipment (CFR)
C Total Price for Services C.1 Total Price for Installation, testing and commissioning Services
Y Total Price for Services
Total Price for DC Power and Air Conditioner Equipment (X + Y)
In Words: US Dollar ...... and BD Taka ...... only
NFV_IGW_Attachment-1&2 Page 171/198
Form B.10: Summary Price for Auxiliary Installation Equipment
FOB Price in USD/ BDT SL Name of Item (s) Unit Qty Currency Unit Total Price Price
A Total Price for Equipment
A.1 Summary Price for Building Modification A.2 Summary price for False Ceiling A.3 Summary price for Raised Floor
A.4 Summary price for Aluminum Glass Partition A.5 Summary price for Lighting Facilities for Equipment Room A.6 Summary Price for Emergency Lights in Equipment Room A.7 Summary Price for Earthing Facility for all Equipment Summary Price for Lighting and Serge A.8 Protection Facility
A.9 Summary Price for Fire Detection and Fire Fighting Facility A.10 Summary Price for Station AC Power Wiring A.11 Summary Price for Station Furniture
A.12 Summary Price for Unforeseen Works (if any) Total Price for Equipment FOB)
B Total Freight
X Total Price for Equipment (CFR)
C Total Price for Services C.1 Total Price for Installation, testing and commissioning Services
Y Total Price for Services
Total Price for Auxiliary Installation Equipment (X + Y)
In Words: US Dollar ...... and BD Taka ...... only
NFV_IGW_Attachment-1&2 Page 172/198
Form C.1: Detail List and Price for All Individual Items/Parts of Media Gateway Controller (MGC)
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
Equipment (The bidder shall fill up the A list as per his/her system configuration and to fulfill the requirement of BTCL)
A.1 MGC Hardware
A.2 MGC Software
A.3 Auxiliary Equipment
A.4 Other Material
Sub Total for A
Services (The bidder shall fill up the list B as per his/her system configuration and to fulfill the requirement of BTCL)
B.1 MGC Services
Installation, testing and commissioning B.2 Services
Sub Total For B
Price for MGC (A+B)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 173/198
Form C.2: Detail List and Price for All Individual Items/Parts of Media Gateway (MGW)
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
A Equipment (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
A.1 MGW Hardware
A.2 MGW Software
A.3 Auxiliary Equipment
A.4 Other Material
Sub Total for A
B Total Price for Services (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
B.1 MGW Services
B.2 Installation, testing and commissioning Services
Y Total Price for Services
Price for the MGW (A +B)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 174/198
Form C.3: Detail List and Price for All Individual Items/Parts for COTS Server
FOB Price in USD/ BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
A Equipment (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
A.1 COTS Hardware
A.2 OS and Software
A.3 License
A.4 Auxiliary Equipment
A.5 Other Material (if any)
Sub Total for A
B Total Price for Services (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
B.1 COTS services
B.2 Installation, testing and commissioning Services
Sub Total Price for B
Total Price for COTS Server (A + B)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 175/198
FORM C.4: Detail List and Price for All Individual Items/Parts of Router, LAN Switch, Firewall, Session Boarder Controller and Intrusion Detection System
FOB Price in USD/BDT Name of Item (s) Unit Qty Unit Total SL Currency Price Price
A Equipment (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
A.1 Router Hardware A.2 Router Software A.3 LAN Switch Hardware A.4 LAN Switch Software A.5 Firewall Hardware A.6 Firewall Software A.7 SBC Hardware A.8 SBC Software A.9 IDS Hardware A.10 IDS Software A.11 Auxiliary Equipment A.12 Other Material Sub Total For A
B Services (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
B.1 Router Services B.2 LAN Switch Services B.3 Firewall Services B.4 SBC Services B.5 IDS Services B.6 Installation, testing and commissioning Services
Price for Router, Switch and Firewall (A +B)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 176/198
Form C.5: Detail List and Price for All Individual Items/Parts of BTRC Monitoring Facilities and LI Connectivity Facilities
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
A Equipment (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
A.1 BTRC Monitoring Facilities Hardware
A.2 BTRC Monitoring Facilities Software
A.3 LI Connectivity Hardware A.4 LI Connectivity Software A.5 Auxiliary Equipment A.6 Other Material Sub Total for A
B Services (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
B.1 BTRC Monitoring Facilities Services
B.2 LI Connectivity Services B.3 Installation, testing and commissioning Services
Sub Total for B
Price for BTRC Monitoring, LI Connectivity (A +B)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 177/198
Form C.6: Detail List and Price for All Individual Items/Parts of Network Management System
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
A Equipment (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
A.1 Network Management Hardware A.2 Network Management Software A.3 CDR Management Hardware A.4 CDR Management Software A.5 Others Sub Total for A
B Services (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
B.1 Network Management System Services
B.2 CDR Management System Services
B.3 Installation, testing and commissioning Services
Sub Total for A
Price for the Network Management System (A +B)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 178/198
Form C.7: Detail List and Price for All Individual Items/Parts of Other Equipment
FOB Price in USD/BDT SL Name of Item (s) Unit Qty Unit Total Currency Price Price
A Equipment (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
A.1 SDH MUX A.2 CAT6 Cable A.3 Optical Fiber Cable A.4 Optical Fiber Connectors A.5 Buffer Stock Maintenance Spares A.6 spares and Consumables Set of required specific tools and testers for all A.7 equipment
Digital Multi-meter (with clamp-on facility for AC/DC A.8 current measurement)
A.9 Optical power meter
A.10 Multimedia Projector
A.11 USB supported external HDD Security and surveillance system including CCTV/IP A.12 Camera, DVR, HDD and Monitor
any other Equipment (if needed but not mentioned)
Sub Total for A
In Words: US Dollar...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 179/198
Form C.8: Detail List and Price for all individual items of Other Services
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Total Currency Unit Price Price
A Other Services (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
A.1 Maintenance Support up to 02 (two) years during Guarantee Period A.2 Maintenance Support 01 (one) year after Guarantee Period A.3 Factory Premises Acceptance Test
A.4 Provisional Acceptance Test A.5 Final Acceptance Test A.6 Factory Training A.7 Local Training Sub Total for A
B Other Services related to Turn-Key completion of the Project (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
B.1 Survey, Network Planning and Design Services
B.2 Project Implementation Services
B.3 Inter-working Services
B.4 Inter-connection Services
Sub Total for B
Price for Other Services (A + B)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 180/198
Form C.9: Detail List and Price for all individual items/Parts of DC Power and Air Conditioner Equipment
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
A Equipment (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
A.1 Rectifier
A.2 Backup Battery
A.3 DC/ AC Inverter
A.4 Air Conditioner for Equipment Room
A.5 Air Conditioner for NMS Room
Sub Total for A
B Services(The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
B.1 Installation, testing and commissioning Services
Price for DC Power and Air Conditioner Equipment (A + B)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 181/198
Form C.10: Detail List and Price for all individual items/Parts of Auxiliary Installation Equipment
FOB Price in USD/BDT SL Name of Item (s) Unit Qty Currency Unit Price Total Price
A Equipment (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL)
A.1 Building Modification A.2 False Ceiling A.3 Raised Floor
A.4 Aluminum Glass Partition
A.5 Lighting Facilities for Equipment Room
A.6 Emergency Lights in Equipment Room
A.7 Earthing Facility for all Equipment
A.8 Lighting and Serge Protection Facility
A.9 Fire Detection and Fire Fighting Facility A.10 Station AC Power Wiring A.11 Station Furniture A.12 Unforeseen Works (if any) Sub Total for A
B Services (The bidder shall fill up the list as per his/her system configuration and to fulfill the requirement of BTCL) B.1 Installation, testing and commissioning Services
Price for Auxiliary Installation Equipment (A + B)
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 182/198
Form D.1: Detail List and Price for Mandatory Maintenance Spares for 02 (Two) Years
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
(The bidder shall fill up the list as per relevant clause of Tender Document and to fulfill the requirement of BTCL)
Total For Maintenance Spares
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 183/198
Form D.2: Detail List and Price for Consumable Item for 02 (Two) years
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
(The bidder shall fill up the list as per relevant clause of Tender document and to fulfill the requirement of BTCL)
Total For Consumable Items
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 184/198
Form D.3: Detail List and Price for Installation Materials
FOB Price in USD/ BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
(The bidder shall fill up the list as per relevant clause of Tender document and to fulfill the requirement of BTCL)
Total For Installation Materials
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 185/198
Form D.4: Detail List and Price for Recommended Maintenance Spares for Buffer Stock
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
(The bidder shall fill up the list as per relevant clause of Tender Document and to fulfill the requirement of BTCL)
Total For Maintenance Spares
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 186/198
Form D.5: Detail List and Price for Tools and Testers and other Equipment
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
(The bidder shall fill up the list as per relevant clause of Tender document and to fulfill the requirement of BTCL)
Total For Tools and Testers
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 187/198
Form D.6: Detail List and Price for Station Furniture
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
(The bidder shall fill up the list as per relevant clause of Tender document and to fulfill the requirement of BTCL)
Total For Station Furniture
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 188/198
Form D.7: Detail List and Price for Security and Surveillance System
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
(The bidder shall fill up the list as per relevant clause of Tender document and to fulfill the requirement of BTCL)
Total For Station Furniture
In Words: US Dollar ...... and BD Taka ...... only.
NFV_IGW_Attachment-1&2 Page 189/198
Form E.1: Price Quotation for all Optional item
FOB Price in USD/BDT
SL Name of Item (s) Unit Qty Unit Total Currency Price Price
(The bidder shall fill up the list as per relevant clause of Tender document and to fulfill the requirement of BTCL)
A.1 Price for SMS Gateway
A.2 Price for Protocol Analyzer
Total
In Words: US Dollar ...... and BD Taka ...... only.
Note: Bidders may include any item in the list if they feel necessary.
NFV_IGW_Attachment-1&2 Page 190/198
FORM E.2: Quotation for Future Order
(a) Future Order Formula for Equipment: (Bidder shall specify)
(b) Future Order Formula for Service: (Bidder shall specify)
Sl No. Description USD BDT
(a) Future Order Formula for Equipment
i. Card repair and Return
ii. Supply of spares
iii. Others (Please specify)
(b) Future Order Formula for Service
i. Return travel ticket
ii. Accommodation
iii. Daily allowance
iv. Others (Please specify)
NFV_IGW_Attachment-1&2 Page 191/198
Form F: Manufacturer’s Information of Equipment, Accessories and Country of Origin Declaration (Bidder may expand the list for mentioning sub-components of any system and/or for any item not listed below)
Model Manufacturer‟s Manufacturer‟s Country of Sl Name of Item Number & Name Address Origin Name
A Mandatory Items
1 Media Gateway Controller (MGC)
2 Media Gateway
3 COTS Server
4 Gateway Router
5 LAN Switch
6 Session Border Controller
7 Intrusion Detection System
8 LI Facility
9 Network Management System
10 Rectifier
11 Battery
12 Inverter
13 Air Conditioning System
14 SDH MUX
15 Raised Floor
16 False Ceiling
17 ODF
18 Optical Fiber
Digital Multi-meter (with clamp-on 19 facility for AC/DC current measurement)
20 Station Furniture
Security and surveillance system 21 including CCTV/IP Camera, DVR, HDD
Optional Items
1 SMS Gateway
2 Protocol Analyzer
NFV_IGW_Attachment-1&2 Page 192/185
Form G: Clause by Clause Compliance Schedule
Clause No / Bidder's Response Reference in Bid Sub-Clause Item Remarks document* No. Agreed / Not Agreed
* The column “Reference in Bid document” may be expanded/furnished as per the convenience of the bidder/manufacturer.
NFV_IGW_Attachment-1&2 Page 193/198
Form H: List of Certificates attached with
(Only the certificates listed here will be considered for Bid evaluation)
Subject of Sl Details of Issuing Authority Certificate
Name of the Tel number Contact person who can Operator & speak English (name, & Address designation, phone & Fax Number & fax number, e-mail)
Website
NFV_IGW_Attachment-1&2 Page 194/198
“Attachment-2”
SECTION 8: DRAWINGS
NFV_IGW_Attachment-1&2 Page 195/198
Figure 8.1: NFV reference Architecture
NFV_IGW_Attachment-1&2 Page 196/198
SMW-4/ ITC SMW-5
Gateway Router
LAN Switch Firewall CDR TCP
Cloud OS X
- based)
LAN LAN Switch LAN Switch LAN vMedia Gateway + vIP Controller + vSBC - MGW +vEMS
Shared Common Components Shared Media Resource Management & HI3 LB DB OM Common Media Processing Orchestration
NFVO E1 Cloud OS (OpenStack based) VNFM TDM Based MGW
VIM
Cloud Core Platform
IOS
Figure 8.2: Proposed BTCL NFV Enabled IP Based IGW
NFV_IGW_Attachment-1&2 Page 197/198
Core Network
2 x 10G
Rack Server Storage
LAN
Switch IGW External Storage System 2 x 10G
Figure 8.3: External Storage Server
NFV_IGW_Attachment-1&2 Page 198/198