What is yasser doing in Barcelona? Does he think he is that good? We will solve the puzzle. Have anyone heard of a 3G conference; we think most technical or geeky persons know about this. This time its held at Barcelona and is yaaser capable of going there? The answer is NO. He does not have any knowledge on technical field and we think he is just taking the opportunity to go there without sending a Maldivian’s there or a technical person there.
Most Maldivian’s knows about Mr.Patson. He worked in wataniya Maldives before and left because of yasser. He is a well know person in 3G conferences. He has given speeches and lots of technical comments. But Yasser a numb is wasting time. We don’t think wataniya can launch 3G soon, as we seen from the marketing plan.
http://3gsmworldcongress.com/
3 comments:
Request For Proposal
for the Supply of a GSM Mobile Network in Maldives
Table of Contents
1. Introduction 4
2. RFP Conditions 4
2.1 Content of the RFP 4
2.2 Calendar of the RFP 4
2.3 Structure of the Response 4
2.4 Integrity of the RFP 5
2.5 Language 5
2.6 Format and Content 5
2.7 Subcontractors 5
2.8 Non-Disclosure Agreements 5
2.9 Export or Other Permits 6
2.9.1 Submission of Responses 6
2.9.2 RFP Clarification 6
2.9.3 Bidder’s Point of Contact 6
2.10 Modification of RFP 6
2.11 Cancellation of RFP 7
2.12 Non Compliant Responses 7
2.13 Acceptance of Responses 7
2.14 Validity of Responses 7
2.15 Evaluation of Responses 7
2.15.1 Response Evaluation and Basis for Contract Award 7
2.15.2 Technical Criteria for Evaluation 8
2.15.3 Commercial and Financial Evaluation Criteria 8
2.16 Instructions for Price Formats and Price Schedules 8
2.17 Certificate of Independent Price Determination 9
2.18 Product Changes and Updates 9
2.19 Statement of Intent for Price Erosion 10
2.20 Supplier Financing 10
2.21 Incentives 10
2.22 Confidentiality 10
2.23 Conditions of Contract 11
2.24 Cost of Bid 11
2.25 Laws and Regulations 11
2.26 Additional Conditions 11
3. Technical Requirements 11
3.1 General 11
3.2 Radio Network 12
3.2.1 General 12
3.2.2 Features Required 12
3.2.3 Additional Information Required 14
3.3 Core Network 14
3.3.1 General 14
3.3.2 Features Required for the Circuit-Switched Core Network 15
3.3.3 Features Required for the Packet-Switched Core Network (GPRS Core) 17
3.3.4 Additional Information Required 17
3.4 Transmission 17
3.4.1 General 17
3.4.2 Required Features 18
3.4.3 Additional Information 18
3.6 Messaging Centres 18
3.6.1 General 18
3.6.2 Required Features for VMSC 19
3.6.3 Required Features for SMSC 19
3.6.4 Features Required for MMSC 19
3.7 IN Platforms 20
3.7.1 General 20
3.7.2 Technical Standards and Architecture 20
3.7.3 Interface SSS-IN (MSSP and Intelligent Peripheral) 21
3.7.4 System scalability and performance 22
3.7.5 Administration Interfaces 22
3.7.6 Call types and features 22
3.7.7 Call and traffic bundling 23
3.7.8 Payment Option Bundles 23
3.8 Charging Centre 24
3.8.1 General 26
3.8.2 Required Features 26
3.9 Push to Talk 26
3.9.1 General 26
3.9.2 Required Features 27
3.10 Streaming Sever 27
3.10.1 General 27
3.10.2 Required Features 27
3.11 Over the Air Platform and Automatic Devise Configuration 27
3.11.1 General 27
3.11.2 Required Features 28
3.12 Messaging Gateway (GW) 28
3.12.1 General 28
3.12.2 Required Features 28
3.13 Optimizer Server 28
3.13.1 General 28
3.13.2 Required Features 29
4. Network Roll-out 29
4.1 Definition of Phases and Regions 29
4.2 Traffic Model 31
4.3 Radio Network 31
4.3.1 BSC 31
4.3.2 Quality of Service 32
4.4 Core Network 32
4.4.1 MSC/VLRs 32
4.4.2 HLR/AuCs 32
4.4.3 International Gateway 33
4.4.4 GPRS Core 33
4.5 IN Platform 33
4.6 Messaging Centres 34
4.7 Charging Centre 34
4.8 Network Availability 34
4.9 Core Network Design Assumption 35
4.10 Coverage Rx level Assumption 33
List of FiguresFigure 1 – RFP Calendar 4
Figure 1 – RFP Calendar 5
Figure 3 – Definition of Roll-out Phases 30
Figure 4 – Islands Covered by the Main Offices 30
Figure 5 – Traffic Model 27
Figure 5 – Traffic Model 27
Figure 7 – BSC Dimensioning 28
Figure 7 – BSC Dimensioning 28
Figure 8 – Quality of Service 28
Figure 9 – MSC/AUC 29
Figure 10 – MSC/AUC 29
Figure 12 – GPRS Core 29
Figure 12 – GPRS Core 29
Figure 14 – VMSC 30
Figure 14 – VMSC 30
Figure 15 – SMSC & MMSC 30
Figure 16 – Network Availabilty 31
Figure 18 – Rx Level Assumptions 33
1. Introduction
Wataniya Telecom (“Wataniya”) has bid for a 2nd GSM licence in Maldives.
Wataniya Telecom is issuing this Request For Proposal (the “RFP”) to start a vendor selection process for the supply of GSM Infrastructure and services. By receipt of this RFP Wataniya Telecom invites suppliers of mobile infrastructure (the “Bidders”) to bid for the supply of its GSM mobile network in Maldives.
Each Bidder shall submit a Response to the RFP (the “Response”) as described in the next sections of this document.
Section 2 details the conditions of the RFP, Section 3 defines the technical requirements and Section 4 presents the network roll-out for the entire Network within 4 months with the associated assumptions and initial estimations of Wataniya Telecom, which will be refined when a detailed nominal plan is available, but which have to be taken into account by the Bidders for the RFP.
2. RFP Conditions
2.1 Content of the RFP
The RFP contains one document in electronic format: “Request For Proposal for the Supply of a GSM Mobile Network in Maldives”.
2.2 Calendar of the RFP
The following table presents the calendar of the RFP.
Figure 1 – RFP Calendar
Date
5 Nov. 2004
( the “Date of Issue”) RFP issued by Wataniya Telecom
12 Nov. 2004
(the “Limit Date for Questions) Last day for Bidders to submit questions about the RFP
25 November 2004 (noon GMT+1)
Written proposal submission Bidders submit written responses to Wataniya Telecom by email.
29th November
Formal presentation of offer Bidders provide formal presentation of their proposal in Dubai to a closed session of the selection panel. Presentations to last a maximum of 2 hour
2.3 Structure of the Response
The Response shall be structured as follows.
Figure 2 – Response Structure
Item Description
Chapter 1 Statement of Compliance with the RFP’s Conditions
Chapter 2 Bidder’s Presentation, Reference and Statement of Capability
Chapter 3 Commercial and Financial Response
Chapter 4 Technical Response
Chapter 5 Support Structure and SLA’s
Chapter 6 Project Plan
For the purposes of an adequate and speedy evaluation Bidders are requested to make their proposal as succinct and straightforward as possible.
2.4 Integrity of the RFP
The Bidders shall not delete, modify or amend any of the terms or conditions of this RFP.
2.5 Language
The Response including the Appendices shall be submitted in English.
2.6 Format and Content
a) Each Chapter and Section (within a Chapter) of the Response shall be exactly identified and marked.
b) The Response shall be presented to a high standard of quality regarding text formats, tables, charts and other drawings.
c) The commercial response shall show all conditions and options as well as clear tables regarding costs, payments terms and warranties.
d) The Technical Response shall present detailed descriptions of the proposed system supported by photographs, drawings, brochures, technical characteristics, field performance statistics, schedule of compliance, product description, feature list, environmental conditions and site requirements, in such a way as to enable Wataniya Telecom to make a clear judgment and evaluation of the equipment, goods and services offered.
2.7 Subcontractors
The Bidder shall provide a list of all major sub-contractor firms or companies, which they intend to use for major parts of the project, showing their role in the project.
2.8 Non-Disclosure Agreements
Bidders shall state whether Wataniya Telecom needs to sign a non-disclosure agreement with the Bidders or any other party for any information, whether proprietary or otherwise, relating to the equipment and if so, to provide a copy thereof at the time of submission of the Response for Wataniya Telecom’s consideration.
2.9 Export or Other Permits
Bidders shall be responsible for and state whether they need to obtain any export or other permits prior to them shipping the equipment to the Maldives . The Bidder will be liable for any damages which Wataniya Telecom may sustain shall they be awarded any contract and subsequently be unable to perform the contract in accordance with the provisions thereof in the event that they are unable to ship the equipment and/or unable to export or permit to ship the equipment or it is delayed or refused due to Contractor being refused an export or other permit required for them to deliver the equipment or services.
2.9.1 Submission of Responses
a) The Bidder shall submit one (1) original printed version and one (1) electronic copy of all of the Response documents to Wataniya Telecom.
b) The electronic copy shall be emailed to Wataniya Telecom to the following addresses ahaleem@wataniya.com and shatara@wataniya.com and ryakub@wataniya.com ; the printed original shall be handed over during the bidders meeting in Dubai
c) The electronic copy shall be emailed to the required addresses no later than 12 noon GMT+1 on Tuesday 21st of November 2004. The Printed Original shall be handed over no later than the bidders meeting on the dates depicted in the RFP Calendar.
2.9.2 RFP Clarification
a) For the duration of this RFP, inquiries and written requests for clarifications regarding the contents of these documents may be directed to:-
Wataniya International
Showtime Bldg – 2nd Floor
Dubai Media City
Dubai, UAE
e-mail : shatara@wataniya.com
or
email: ahaleem@wataniya.com
fax: +971-4-390-8000
b) All questions and queries shall be clearly marked with the reference of this RFP and shall be submitted by e-mail.
2.9.3 Bidder’s Point of Contact
In order to facilitate correspondence each Bidder shall nominate a responsible person for this project and to advise Wataniya Telecom of the name, address, telephone number, fax number and e-mail no later than the 10th of November 2004.
2.10 Modification of RFP
a) Prior to the closing date, Wataniya Telecom reserves the right to revise or amend the terms, conditions and provisions of the RFP. Wataniya Telecom will endeavour to give the Bidders reasonable time in which to consider any revision or amendment. A copy of such addendum, if any, will be announced as amendments to the RFP and submitted to all Bidders at the same time. Each addendum shall become part of the RFP.
b) Wataniya Telecom reserves the right to call for additional information after the RFP presentation. Bidders shall state their commitment to the timely provision of this information.
2.11 Cancellation of RFP
Wataniya Telecom reserves the right at its sole discretion to cancel this RFP at any time and for any reason. In such an event Wataniya Telecom shall not be liable to any of the candidates or Bidders for payment of any kind.
2.12 Non Compliant Responses
Responses submitted later than the time limit stipulated or which do not contain all the information required are subject to immediate rejected.
2.13 Acceptance of Responses
Wataniya Telecom reserves the right to reject any or all of the Responses without any compensation or explanation to any Bidder. Wataniya Telecom reserves the right to accept any phase or lot of a Response, without it incurring the obligation to accept any of the other lots or phases, whether from the same Bidder, or from any Bidder.
2.14 Validity of Responses
The validity of the RFP and its responses shall be at least 6 (six) calendar months from the formal presentation of the proposal. During its validity period, the Response shall not be subject to any modification without the written agreement of Wataniya Telecom.
2.15 Evaluation of Responses
2.15.1 Response Evaluation and Basis for Contract Award
The evaluation of the Responses by Wataniya Telecom’s evaluation team will constitute an assessment of the Bidder's capabilities to fulfil the requirements based on the submitted Responses and the answers to the questions subsequently asked to the Bidders.
The criteria on which Wataniya Telecom bases the award of this procurement shall be the most advantageous Response based on commercial, financial and technical criteria including but not limited to those listed hereafter.
Wataniya Telecom will pay extra attention to the delivery history of the vendors in the different Wataniya subsidiaries. An aggressive rollout plan of maximum 4 months will be required from the vendors. The vendors should extended proofs that they will be able to deliver according to this time plan and deploy the right resources to manage such a project.
The Viability of the submitted project plan submitted will be given great attention and consideration during the evaluation process
Wataniya Telecom will not be obliged to provide to any Bidders any reasons for acceptance or rejection of any Response or part thereof.
Should Wataniya Telecom not receive satisfactory responses to any part of this RFP, Wataniya Telecom may issue a new RFP specifically for those parts of the project for which satisfactory responses were not received.
Wataniya Telecom reserves the right, if necessary, to re-issue a part or the whole of this RFP.
The Response along with all detailed statements and figures will be the basis for contractual discussions regardless of any omissions and errors made by the Bidder.
2.15.2 Technical Criteria for Evaluation
Wataniya Telecom shall evaluate the Bidder’s Technical Response based on the following criteria:
a) Ability to deliver, install and commission the equipment and to provide the required services according to the time plan proposed in this RFP;
b) Features offered, ease of use and customisation and level of experience of the Bidder with the implementation of these features;
c) Reliability of the equipment (hardware and software);
d) Cost effectiveness of the equipment and technical solutions offered;
e) Availability of resources in the Middle East,North Africa region , and Indian subcontinent to support the implementation and operation of a GSM mobile network in the Maldives;
f) Bidder’s experience, reputation and proven track record, especially in the Middle East,North Africa region, and the Indian subcontinent.
2.15.3 Commercial and Financial Evaluation Criteria
Wataniya Telecom shall evaluate the Bidder’s Commercial and Financial Response based on the following criteria:
a) Prices and forward pricing commitments. In particular Bidders should use as a base the final pricing tables including any discounts offered for the same equipment during previous Projects vendor selection process which Wataniya Telecom leads. In the event that additional price reductions can be made then these should be clearly shown. Any price increases over the ex-factory prices offered for the previous vendor selection process may render the Bid disqualified.
b) Erosion of prices;
c) Total lifetime ownership costs of the equipment;
d) Standard delivery time and penalties regarding delays;
e) Financial arrangements, including vendor financing; Advantage shall be given to Bidders able to offer “open terms” without recourse to Wataniya being required to raise letters of credit.
f) Deferred Payments; Bidders are encouraged to offer the same or better “deferred payment” terms including deferred monthly payments made available to the other Wataniya Projects vendor selection process.
g) Incentives.
2.16 Instructions for Price Formats and Price Schedules
a) Prices shall be quoted for all items proposed.
b) All prices shall be quoted in USD.
c) All prices shall include discount to enable accurate comparisons between Bidders of the main units .
d) Wataniya Telecom shall be able to calculate for each lot from the information given:
- CIP/CIF price
- Transportation price
- Ready for service price
e) Bidders should structure their quotations to clearly identify these, accordingly.
f) Prices shall be presented as before the operation of any price escalation or price deflation formulae or discounts.
g) Prices shall be given on a total system basis and broken into individual line items for main system entities, sub-systems, units and module levels.
h) Bidders shall list software and firmware packages separately, broken down into sub-systems, units and modules.
i) Bidders shall clearly show and list separately all prices and costs both one-off and recurring for software support, extensions of services, enhancements of service and emergency support (e.g. TAC 2 type services).
j) Bidders shall make clear how prices at the detailed level have been combined to form price quotations at the higher (system) level.
k) Project Management fee and Installation and Commissioning and assimilated services fee shall be included in pricing and clearly quoted.
2.17 Certificate of Independent Price Determination
Bidders shall certify the following:
a) The prices in the Response have been calculated independently, without consultation, communication or agreement for the purpose of restricting competition.
b) The prices, which have been quoted in the RFP, have not been disclosed, discussed or negotiated with other Bidders or organisations participating in competing Responses to this framework agreement.
2.18 Product Changes and Updates
a) Any proposed changes, updates or new releases of equipment (software, hardware and firmware) shall be compatible with previously supplied equipment.
b) Bidders shall describe their update and new release procedures and shall separately define any proposed costs during the warranty period.
c) Bidders shall describe their pricing policies for new software releases.
d) Bidders shall quote, for the equipment offered, the maximum upgrade and/or new release fees that will be payable over five years from the Effective Date and the pricing structure for any additional equipment purchased. Wataniya Telecom will give major attention to this element of the Response and Bidders are advised to make their responses as comprehensive and specific as possible.
2.19 Statement of Intent for Price Erosion
Bidders shall state, for a five year period from the closing date a minimum price erosion formulae including the component due to the expected annual level of deflation expected for the prices of:
a) Radio Network Equipment (TRX, BTS, Node B, RNC, BSC, TRC)
b) Core Network Equipment (MSC/VLR, HLR/AuC, Soft-switch, GPRS Core)
c) IN Platform Equipment
d) Messaging Centres (VMSC, SMSC, MMSC, UMS, Messaging GW, and Missed call Alert)
e) VAS Platforms including Push to Talk platforms, Video Streaming Servers, and Wireless LAN in 50 hotspots
f) Transmission Equipment
g) Charging Centre
h) Satellite links
i) Operation and Maintenance Centre
Bidders shall state their agreement that all future pricing shall be best-in-class for comparable equipment in the general market and that their pricing policy shall always ensure Wataniya Telecom is not disadvantaged with relation to competing operators in the Maldives .
2.20 Supplier Financing
Supplier financing is required for this RFP. The Bidder is required to provide extended and highly flexible payment terms.
2.21 Incentives
Bidders are invited to propose incentives.
2.22 Confidentiality
a) All documents released by Wataniya Telecom in the framework of the RFP shall be treated as confidential information.
b) Wataniya Telecom requires that no part of these documents is disclosed to any third parties without Wataniya Telecom’s specific and written agreement except as allowed below.
c) Disclosure, limited to immediately relevant and necessary parts, to third parties is permitted in the case of sub-contractors or contracted participants of equipment suppliers. The non-disclosure obligations placed upon Bidders in these documents will then be transferred to the third party concerned and the maintenance of these obligations will be the responsibility of the main Bidders.
d) Unauthorized disclosure may result, at Wataniya Telecom’s discretion, in the disqualification of Bidders.
2.23 Conditions of Contract
a) Wataniya Telecom intends to negotiate with Bidders offering the most attractive proposals from the standpoint of relevant commercial, financial and technical criteria.
b) The contract will be awarded at the end of the negotiation procedure; however Wataniya Telecom will retain the right not to proceed with the contract, as well as the right to allocate different parts of the contract to different Bidders. The procurement is awarded and the supply contract exists from the date of the signature by the parties (the "Effective Date").
2.24 Cost of Bid
All costs to the Bidders in connection with the preparation, submission and follow-up support of the Response, shall be born by the Bidders.
2.25 Laws and Regulations
The laws and regulations of Kuwait will govern this RFP. Bidders are deemed to have a full knowledge of the applicable laws and regulations at all relevant times.
2.26 Additional Conditions
Wataniya Telecom reserves the right to issue supplementary terms and conditions from time to time as required by their business.
3. Technical Requirements
3.1 General
a) The offered equipment shall fully comply with the latest GSM & UMTS standards and specifications approved by the ETSI/3GPP, OMA,and relevant ITU-R and ITU-T recommendations.
b) Any non-compliance shall be highlighted and described with full technical description of the concerned equipment.
c) The Technical Response shall include the following details for each type of equipment:
- Dimensions;
- Standard layout plans for building space required indicating where computer flooring will be needed;
- Weight of each equipment rack, cabinet and other individual unit;
- Floor loading requirements of each equipment rack, cabinet and other individual unit;
- Heat load of each equipment rack, cabinet and other individual unit in idle and active modes;
- Clear indications of where, when and in what circumstances air-conditioning, special ventilation, desalination, dehumidification or other environmental controls will be required or are recommended;
- Electrical loads (both transient and steady state) of each equipment rack, cabinet and other individual unit;
- Any other site environment requirement (such as the kind of raised-floor, distance between equipment, etc.);
- MTBF and suggested MTTR of each individual unit.
3.2 Radio Network
3.2.1 General
This section describes the requirements for the Radio Network which include the following network elements:
- Base Transceiver Stations (BTS)
- Base Station Controllers (BSC)
- Node B
- Radio Network Controller (RNC)
- Trans-coders (TRC)
- Operation and Maintenance Centre - Radio (OMC-R)
a) In the Technical Response, the Bidder shall provide:
- Detailed descriptions, specifications, dimensioning rules and expansion possibilities for the above network elements (for each type or configuration if applicable);
- Hardware and software roadmaps;
- “Standard Basic Feature List”;
- “Standard Optional Feature List”.
a) In addition, the Bidder shall provide a list of Core Network vendors for which the interoperability of equipment has been tested and validated (hardware type and model and software release must be included and the case of Circuit-Switched and Packet-Switched Core Network must be presented separately).
3.2.2 Features Required
The Bidder shall provide information about the availability of the Radio Network mandatory features listed hereafter and shall take these into account in their Response if not included in their standard basic feature list:
1) GSM-900/1800 band support.
2) The operating frequency in 900 band on Uplink would be 903-915 MHz and on down-link would be 948-960 MHz.
3) Minimum of four (4) BSC’s/PCU’s to be distributed all over the country (North, Central, South and the far South) with each support minimum 512 TRX’s;
4) Trans-coders to be co-located with the MSC and packet core Network;
5) All BTS configuration offered should be EDGE enabled;
6) One hundred and twenty two (122) cells sites to be deployed to provide 95.7% coverage and address the capacity needs in urban, suburban and rural areas of inhabited islands population;
7) All capacity calculation for Erlang per subscriber should be done on 22 mlErlang in first year, declining to 21 mlErlang in the second year and then stabilizes at 20 mlErlang in the following years;
8) A-Interface GOS should be 2%;
9) To reduce risks and increase the quality of the radio Network, 25% capacity should be calculated as a mobility factor.
10) GSM Network rollout should be completed and ready for commercial launch within 4months from the signing of the contract.
11) Four (4) Node B should be distributed in different locations in Male’ to provide UMTS coverage for the city.
12) All node B stations should be connected to RNC which would be connected to soft-switch in Male’.
13) The operating frequencies in UMTS band on Uplink would be 1920-1935 MHz and on Down-link 2110-2125 MHz.
14) UMTS should be ready for launch in 17 months from signing the contract.
15) Support of full rate and half rate channels with enhanced full rate, full rate, half rate and AMR speech codec’s;
16) Dynamic allocation of CODEC based on traffic level on a cell-by-cell basis.
17) GPRS support up to and including CS4
18) EDGE support (all coding schemes);
19) Synthesised Frequency Hopping;
20) Preferred Assignment on Hopping or non-Hopping TRX;
21) Directed Retry;
22) Traffic Handover;
23) Dynamic Power Control;
24) Discontinuous Transmission;
25) Handover at Assignment;
26) SDCCH Handover;
27) BTS Receive Diversity;
28) Access Class Based Channel Allocation;
29) Extended Cell;
30) 1/1/1, 2/2/2 and 4/4/4 BTS Configuration in 1 Cabinet and 5/5/5 and 6/6/6 BTS Configuration in 2 Cabinets;
31) Outdoor or small foot-print equipment with a capacity expandable to 6+6+6
32) Air Combining (with Duplexers) or Hybrid Combining (with Duplexers) for up to 6 TRXs per cell.
33) Interface type A and Abis via VSAT;
34) Power Supply and Battery Backup for BTS (2h and 4h options);
35) Power Supply and Battery Backup for BSC (1 hour and 8hours options);
36) High Performance GSM-900 Antennas:
- 60-65 degrees beam-width, high gain, null fill, high upper side lobe suppression with variable electrical down-tilt for urban areas (GSM-900);
- 60-65 degrees and 85-90 degrees beam-width, high gain for suburban and rural areas (GSM-900 only for suburban & rural areas);
37) High Performance UMTS Antennas:
-63-65 degrees beam-width, high gain, null fill with variable electrical down-tilts for areas in Male’.
38) Cable, connectors, surge arrestors and clamps;
39) Thirty (30) repeaters to be utilised in the weak locations areas to boost signal strength.
3.2.3 Additional Information Required
As an option, the Bidders are invited to augment their offer with proposals for:
a) Shelter for BTS;
b) Rooftop BTS Site Construction;
c) Tower Site Construction:
a. 30-40 m monopoles for urban areas;
60-70 m towers for suburban and rural areas;
d) Antenna and feeder installation Service (for rooftop and tower sites);
e) Radio Network Planning Service (including Transmission Planning);
f) Site Acquisition Service.
g) Installation and commissioning service
h) Initial optimisation and set-to-work service
i) Solar powered power supply.
3.3 Core Network
3.3.1 General
This section describes the requirements for the Core Network which include the following network elements:
a. Mobile Soft Switching Centre and Visitor Location Register (MSC/VLR) that can be upgraded to UMTS to support UMTS by Q4 2005
b. Home Location Register and Authentication Centre (HLR/AuC);
c. GPRS Core (GGSN/SGSN);
d. Operation and Maintenance Centre - Switching (OMC-S);
b) In the Technical Response, the Bidder shall provide:
- Detailed descriptions, specifications, dimensioning rules and expansion possibilities for the above network elements (for each type or configuration if applicable);
- Hardware and software roadmaps;
- “Standard Basic Feature List”;
- “Standard Optional Feature List”.
c) In addition, the Bidder shall provide a list of Radio Network vendors for which the interoperability (IOT) of equipment has been tested and validated (hardware type and model and software release must be included and the case of Circuit-Switched and Packet-Switched Core Network must be presented separately).
3.3.2 Features Required for the Circuit-Switched Core Network
The Bidder shall provide information about the availability of the Core Network features listed hereafter and shall take these into account in their Response if not included in their standard basic feature list:
a) Soft MSC/VLRs to support up to 110,000 subscribers on a single platform;
b) MSC should be 3G ready with software upgrade;
c) Support of Mobile Number Portability (MNP) using Call Forwarding Function, and any other MNP solutions that support non-call related function like (SMS, and MMS)
d) IMS Architecture support according to the 3GPP recommendation should be supported without additional CAPEX.
e) All Legacy circuit switched services should be self supported.
f) It should support all traditional protocols (SS7, R2) besides the IP interfaces.
g) Soft-switch should inherently support distributed switching (Media GWs) in the event that Wataniya would like to inter-connects with the interconnect partners outside Male’ for fixed or mobile.
h) Standard voice charging for local and roaming subscribers through CAMEL phase 2, 3 including pre-paid roaming.
i) Volume charging for Data access for local subscribers through CAMEL phase 2,3.
j) USSD Support;
k) IN and WIN Support;
l) The deployed IN system should be able to charge subscribers by any duration increments down to 1 second increments.
m) Customer balances should be maintained in units of money, minutes or units mapped to events.
n) Charging of all services (including voice calls, SMS, and PTT calls) should have the following flexibilities:
- Charging Depending on:
• Destination (dialled digits).
• Time of the days.
• Day of the week.
• Public holidays (programmed in the system).
• Subscriber package.
o) Charging Centre Support including a VAS charging gateway;
p) Power Supply and Battery Backup;
q) Support of Tele-services:
- Call waiting / hold.
- Parallel calls.
- Call forwarding
- Toll Free number
- FOC Emergency Call (with Access Class Priority Handling);
- Telephony (with Access Class Priority Handling).
- Short Message Mobile Terminating / Point to Point, Application to Subscriber;
- Short Message Mobile Originating / Point to Point;
- Short Message Cell Broadcast;
- Facsimile Group 3;
r) The IN should interface to a voucher management system that should allow the subscribers to refill their balances through printed vouchers that they can be bought from the market with different face values and different validity periods, or by electronic charging.
s) Bearer Services:
- Circuit-Switched Data (All modes up to 9.6 kbps);
t) Supplementary Services:
- Calling Line Identification Presentation;
- Calling Line Identification Restriction;
- Connected Line Identification Presentation;
- Connected Line Identification Restriction;
- Call Forward Unconditional;
- Call Forward on Busy;
- Call Forward on No Reply;
- Call Forward on Not Reachable;
- Default Call Forwarding;
- Call Wait;
- Call Hold;
- Multiparty;
- Closed User Group;
- Advise of Charge (Information);
- Advise of Charge (Charging);
- Barring of all Outgoing Calls;
- Baring of all International Calls;
- Barring of all International Except HPLMN;
- Barring of all Incoming Calls;
- Barring of Incoming Calls When Roaming;
- Call Transfer.
3.3.3 Features Required for the Packet-Switched Core Network (GPRS Core)
The Bidder shall provide information about the availability of the GPRS Core features listed hereafter and shall take these into account in their Response if not included in their standard basic feature list:
a) Single Access Point Name (APN): customers should be able to access all GPRS/Services using a single APN i.e. without the need to make different configurations on their handsets for different services;
b) IN Support;
c) Using the Enhanced GGSN, different charging models should be offered based on the type of services. This should make easier the users to understand how they would get charged on each service.
d) Charging Capabilities should include:
a. Time, event, flat fee, and/or volume based billing
b. Content based charging (charging based on content type, and based on URL)
c. Common Pre-Paid and Post-Paid deployment
d. Real-time pre-pay charging
e. Support roaming services with roaming awareness (no double charging for volume and event based for roamers)
f. IP Service & IP Flow Charging ( Applications, Protocols and Ports)
e) Charging Centre Support;
f) Billing and Charging support based on data throughput, content and QoS.
g) Interfacing with SMSC;
h) Interfacing with MMSC;
i) Power Supply and Battery Backup.
j) Priority routing capability.
3.3.4 Additional Information Required
As an option, the Bidders are invited to augment their offer with proposals for:
a) Core Network Site Acquisition and Construction (in Male’);
b) The BSC sites acquisition and Construction in the four cities
3.4 Transmission
3.4.1 General
This section describes the requirements for Transmission which include the following network elements:
a) PDH Microwave Hops;
b) SDH Microwave Hops;
c) SDH Transmission Equipment (ADM);
d) Voice Compression Equipment;
e) Digital Cross-connect;
f) Transmission Network Management System (TNMS).
In the Technical Response, the Bidder shall provide:
- Detailed descriptions, specifications, dimensioning rules and expansion possibilities for the above network elements (for each type or configuration if applicable);
- Hardware and software roadmaps;
- “Standard Basic Features” list;
- “Standard Optional Features” list.
3.4.2 Required Features
The Bidder shall provide information about the availability of Transmission features listed hereafter and shall take these into account in their Response if not included in their standard basic feature list:
a) All Links that exceed 15 Kilometers 1+1 redundancy should be built using space diversity.
b) The Links which are shorter than 15 Kilometers but carry high number of sites a 1+1 redundancy should be built using space diversity.
c) Transmission between the BSCs (except for BSC in the far south and MSC use microwave.
d) Transmission between BSC covering the far south and the MSC should be using Satellite communication.
3.4.3 Additional Information
As an option, the Bidders are invited to augment their offer with proposals for:
a) PDH Transmission Planning Service (included in previous Radio Network Planning Service but to be also quoted separately at this stage).
3.6 Messaging Centres
3.6.1 General
This section describes the requirements for the Messaging Centres which include:
- Voice Mail Centre (VMSC)
- Short Message Service Centre (SMSC);
- Multimedia Message Service Centre (MMSC);
a) In the Technical Response, the Bidder shall provide for each type of messaging centre:
- Detailed descriptions, specifications, dimensioning rules and expansion possibilities;
- Hardware and software roadmaps;
- “Standard Basic Feature List”;
- “Standard Optional Feature List”.
b) In addition, for each type of messaging centre, the Bidder shall provide a list of Core Network vendors for which the interoperability of equipment has been tested and validated (hardware type and model and software release must be included). The interfaces supported by the messaging centres should comply with the ITU-T, ETSI, 3GPP, WAP and IETF Standards. The supplier should commit to comply with any future evolution / amendments of applicable standards within 6 months of standardisation.
3.6.2 Required Features for VMSC
The Bidder shall provide information about the availability of the VMSC features listed hereafter and shall take these into account in their Response if not included in their Standard Basic Feature List:
a) Voice-mailbox auto create auto delete;
b) Voice-mailbox user maintenance;
c) Voice mail notification by SMS;
d) One Command Return of Call Service.
e) Generation of detailed Call Detail Records (CDRs) for each deposit and retrieval event.
3.6.3 Required Features for SMSC
The Bidder shall provide information about the availability of the SMSC features listed hereafter and shall take these into account in their Response if not included in their Standard Basic Feature List:
a) Selective deletion stored messages by operator;
b) Support for multiple delivery attempts with algorithm such as for example:
- Standard retry algorithm that may be applicable to all messages;
- Algorithm for each valid error or “cause code” associated with message delivery failure;
- Algorithm for messages addressed to international destinations.
c) Generation of detailed Call Detail Records (CDR) for each successful SMS delivery.
d) Message input should be supplied via number of methods including Operator Assist, PC based (WWW, Email), Local Message Terminal, mobile-originated or forwarded by a 3rd party application.
3.6.4 Features Required for MMSC
The Bidder shall provide information about the availability of the MMSC features listed hereafter and shall take these into account in their Response if not included in their Standard Basic Feature List:
a) MS to MS MMS;
b) MS to Email MMS;
c) Email to MS MMS;
d) Features required for SMSC;The MMSC shall support as a minimum all the content types and possible combination of content types as stated in 3GPP/3GPP2 Specification last updated specifications. Following is the minimum requirement:
a. Image and graphic formats:
- Baseline JPEG, GIF87, GIF89a, Progressive JPEG, JPEG 2000, PNG, MNG, and WBMP.
b. Audio codec:
- Wideband AMR, MP3, MIDI, and MPEG-AAC.
c. Video codecs:
- H.263, and MPEG-4 video,
d. Presentation formats
- SMIL 2.0 Basic, WML 1.3, and xHTML Basic
e) The MMSC solution should include a Trans-coding Node as an external server which supports conversation of MM content into common image formats.
f) The MMSC should provide legacy handset support with SMS notification.
g) MMSC should support an off-board permanent storage album (Photo Album). Photo album should support viewing, deleting, up-loading and editing of images;
3.7 IN Platforms
3.7.1 General
The IN system shall supply an enhanced feature rich services to customers electing a pre-pay option. The IN system shall include facilities to generate and manage re-charge vouchers and will allow electronic voucher recharge service from an acceptable third party.
3.7.2 Technical Standards and Architecture
The IN System shall comply as a minimum with the international standardized IN architecture and comply with ITU-T-Capability Set 1 (CS1) recommendations (series Q12xx). Bidder shall provide a rollout roadmap of products evolution towards CAMEL in accordance to the ETSI recommendations GSM 02.78 (stage 1), GSM 03.78 (stage 2), and GSM 09.78 (stage 3).
The functional entities comprising the IN architecture shall be located in separate physical system components:
a) The Service Switching Function (SSF), the Call Control Function (CCF) and the Specialized Resource Function (SRF) are within the Service Switching Point (SSP).
b) The Specialized Resource Function (SRF) shall optionally be located at an Intelligent Peripheral (IP).
c) The Service Control Function (SCF) and the Service Data Function (SDF) are assigned to the Service Control Point (SCP).
d) The Service Management Function (SMF) and the Service Management Access Function (SMAF) belong to the Service Management Point (SMP).
e) The Service Creation Environment Function (SCEF) is assigned to the Service Creation Environment (SCE).
f) Specialised external sync/async message oriented middleware.
The proposed IN system shall support:
g) CAMEL phase 2 and 3.
h) Standardized Camel 2 online charging for Prepaid Subscribers
i) SMS - MO, and MT with different charging scenarios as mentioned in the 3.3.2, and 3.3.3.
j) Evaluation of network triggered location information
k) Evaluation and modification of subscriber information in the HLR
l) Standardized support of SMS-MO via CS.
m) New service features based on network triggered location information (e.g. location dependent charging; automatic advice of charge; location dependent messages)
n) New service features based on evaluation and modification of subscriber info in HLR (e.g. address resolution, barring/debarring)
o) Online Charging of CS data calls.
p) Call party handling (Parallel ringing, leg specific charging)
q) The ability to support multiple accounts for the same MSISDN, where the different accounts can be assigned to different services.(Example Voice account, VAS1 account, ….)
r) WiFi
3.7.3 Interface SSS-IN (MSSP and Intelligent Peripheral)
The IN System shall comply and supply the following SSS-IN interfaces and features as a minimum requirement:
a) MSS and Intelligent Peripheral
b) the system shall support an Internal Intelligent Peripheral functionality integrated within the MSC/SSP.
c) The Intelligent Peripheral shall have the following functionality:
I. DTMF
II. Customized Announcements
III. Individual announcements
IV. User Interaction announcements
V. Standard announcements
VI. Broadcast announcements
VII. Composition of announcements
VIII. Limitation of the duration and automatic repetition of an announcement
IX. Support of multiple languages
X. Customized Tones (same treatment as announcements)
XI. Fragmenting, digitizing, and cutting of announcements on a PC using dedicated software
XII. Remote update of announcements on Internal IP during operation
XIII. The IP shall be available in a redundant configuration.
The system shall support an External IP functionality including support of the Assist-Procedure. The External IP shall be connected to the SSP(s) via ISUP and be controlled by the SCP via INAP. Bidder shall provide information on functionality, availability and co-operation partners.
3.7.4 System scalability and performance
The IN system shall be scalable according to Market demand. Bidders shall state the maximum call handling performance of a single SCP in terms of BHCA and Transactions per second (TPS).
3.7.5 Administration Interfaces
The IN System shall offer the following interfaces for administration:-
a) FTAM and FTP interface for mass data handling of subscriber and service data.
b) E-Mail in order to send and receive e-mails based on SMTP and POP3 protocols.
c) Online in order to enable communication with external servers like e.g. Voucher management system.
d) Web in order to provide HTTP server and client functionality.
e) APIs availability for CRM interfaces (on both the VoMs and the IN)
3.7.6 Call types and features
All pre-pay calls (voice, data, SMS, switched circuit and GPRS/EDGE) shall be under the control of the IN platfrom. Emergency services calls (e.g. 112) shall be routed directly by the serving MSC. With the excpetion of emergency calls all other traffic will generate a charging record or event and it shall be possible as a minimum requirement to apply different rates for calls based on any combinaion of:-
a) Time of call
b) Originator location
c) Terminat loction
d) Number dialled
e) type of call
f) flat rate
g) Closed User Group
h) Reverse Charged, (based on call originator)
i) Reverse charged, (based on content or route)
j) Messaging type
k) Content
l) QOS of data ( e.g. throughput/payload)
m) Packet data (per Kbyte)
n) Packet data flat rate triggered on first attachment per day/week/month
o) premium rate (switched circuit)
p) Premium rate (Packet data)
q) Premium rate (messaging)
Respondents shall clearly state the complete catalogue of charging events their solution can support.
3.7.7 Call and traffic bundling
It shall be possible provide straightforward “bundles” of services where customers can receive call minutes, data and messages at differeing rates based on usage and „flat-rate” options. As a minimum it shall be possible to provide:-
a) Minute bundle. Where for a monthly fee or “flag-fall” a certain number of air-time minutes are free. Subsequent minutes will be charged at the normal rate. International call will charged at the normal rate irrespective of the “free-minute” count.
b) SMS Bundle. Where for a fixed flag-fall rate customers can send SMS and receive non-VAS SMS
c) Message Combination Bundle. Where for a fixed flag-fall rate customers can get a number of “free” SMS plus “free” airtime minutes, with any remaining credit used for normal traffic (bundle thresholds are reserved).
d) Data Bundle. Where customers for a fixed fee can download a given amount of packet data.
e) Data Combination Bundle. Where customers for a fixed fee can receive a given amount of voice minutes, messaging and packet data.
f) VAS bundle. Where for a fixed fee customers can access given VAS content (e.g. 5 ringtones, or 5 MMS pictures). Irrespective of the instantaneous condition of their account.
g) Support of monthly payment type of services.
Example: Offering the prepaid subscribers content push service with monthly deduction of 10$. The system should be able to automatically deduct this amount of money monthly.
3.7.8 Payment Option Bundles
The IN system shall be configurable to allow interworking with the billing and charging system to provide customers with differeing payment options for differing services e.g. postpay for voice minutes and pre-pay for data. As a minumim it shall be possible to offer the following payment option bundles:-
a) VAS bundle
b) Voice bundle option. Post-pay for peak hours service, pre-pay for off-peak service.
c) Airtime-messaging. Post-pay for voice service, pre-pay for messaging.
d) Voice-Data. Postpay for voice servive and pre-pay for data
e) International destination. Partitioned payment for an individual country (discount minutes), with normal pre-pay for all other destinations.
f) Voice-VAS. Post-pay for voice/data services and pre-pay for VAS including ringtones, logo’s and MMS.
g) Voice-Premium rate. Postpay for voice/data and pre-pay for all VAS.
3.7.9 Voucher Management System
The voucher management should provide the following functionalities:
a. The ability to bundle VAS promotions with the recharge card:
The proposed solution should be capable of bundling specific services with normal recharge card (Example: 50 SMS free with recharge card type x, 100 MMS for recharge card type y,…).
b. Flexible bonus for recharging:
The proposed solution should be capable of adding certain amount of bonus (money, and/or validity time) to the subscriber account.(Example: Add 10$ to recharge cards of Type x, and 5$ , and extra 10 day validity for recharge card type 2)
a. The ability of recharging using the recharge cards through the following methods:
• IVR
• USSD
• SMS
• Web
b. The VoMS should provide the APIs that could be used to provide the fol-lowing recharging methods:
• Recharging through Credit cards
• Banks-Automatic Tellers Machines (ATMs)
c. The system should provide the mechanism to allow Post-paid Re-fill through customer care.
i.e. The ability for a post-paid subscriber to call the customer care and recharge for any prepaid subscriber where the recharge fee to be added to his/her monthly bill.
d. The system should support different kinds of vouchers that can give one or more of the following options:
• Balance (money) credit only
• Airtime period (Subscriber can issue calls)
• Service Period (Subscriber can receive calls)
h) Flexible Vouchers
The system should give the possibility to treat the same voucher differently according to the subscriber’s service class.
Example: Using the same recharge Card the following different values for Credit, Validity period (or date), and expiration period (or date) could be defined based on the subscriber business class:
Subscriber Class Credit Validity Date Expiration Date Balance cleared Date Announcement
A 10 $ 2 months 1 month 1 month 7 days before the first announcement and 1 day before the second
B 20 $ 3 months 2 weeks 2 weeks 14 days before the first announcement and 2 day before the second
Values should be configurable and to override any default values in the service class.
3.8 Charging Centre
3.8.1 General
This section describes the requirements for the Charging Centre.
a) In the Technical Response, the Bidder shall provide:
- Detailed descriptions, specifications, dimensioning rules and expansion possibilities;
- Hardware and software roadmaps;
- “Standard Basic Feature List”;
- “Standard Optional Feature List”.
b) In addition, the Bidder shall provide a list of Core Network (Packet and Circuit Switched), SMSC, MMSC and IN Platform vendors for which the interoperability of equipment has been tested and validated (hardware type and model and software release must be included).
3.8.2 Required Features
The Bidder shall provide information about the availability of the Charging Centre features listed hereafter and shall take these into account in their Response if not included in their Standard Basic Feature List:
a) Interface with Core Network;
b) Interface with IN Platform;
c) Interface with SMSC;
d) Interface with MMSC;
e) Support of flexible and advanced charging schemes;
f) Support for non GSM packet based service platforms such as WiFi (packet counting and session/credit monitoring.
3.9 Push to Talk
3.9.1 General
This section describes the requirements for the Push to Talk.
In the Technical Response, the Bidder shall provide:
- Detailed descriptions, specifications, dimensioning rules and expansion possibilities;
- Hardware and software roadmaps;
- “Standard Basic Feature List”;
- “Standard Optional Feature List”.
3.9.2 Required Features
The Bidder shall provide information about the availability of the Push to Talk features listed hereafter and shall take these into account in their Response if not included in their Standard Basic Feature List:
a) Push-to-Talk over Cellular (PoC) solution should provide to support this service through a flexible IP-based VoIP server platform;
b) Platform supports GPRS/UMTS and W-LAN access;
c) It should be built in a modular fashion with a disaggregated architecture that de-couples call control functions from bearer traffic functions;
d) The PPT server platform should support existing IETF, OMA, 3GPP and 3GPP2 standards and aligns with future 3G-network/IMS evolution paths.
3.10 Streaming Sever
3.10.1 General
This section describes the requirements for the Streaming Server.
In the Technical Response, the Bidder shall provide:
- Detailed descriptions, specifications, dimensioning rules and expansion possibilities;
- Hardware and software roadmaps;
- “Standard Basic Feature List”;
- “Standard Optional Feature List”.
3.10.2 Required Features
The Bidder shall provide information about the availability of the Streaming Server features, and support media, and coding formats
The following features should be supported:
a) Different Media Format (MPEG-4, H.263 or RealMedia formats).
b) Support of live, as well as Video on Demand.
c) The ability to capture live audio/video streams for webcasts
d) Generate RealMedia, 3GP, MP4 and AMR files for download.
e) Content Management System (CMS) should be provided for manging the streaming content Generation of detailed Call Detail Records (CDRs) for each content download.
3.11 Over the Air Platform and Automatic Devise Configuration
3.11.1 General
This section describes the requirements for the Over the Air Platform and Automatic Devise configuration.
In the Technical Response, the Bidder shall provide:
- Detailed descriptions, specifications, dimensioning rules and expansion possibilities;
- Hardware and software roadmaps;
- “Standard Basic Feature List”;
- “Standard Optional Feature List”.
3.11.2 Required Features
a) The Bidder shall provide information about the availability of the Over the Air Platform and Automatic Devise configuration features listed hereafter and shall take these into account in their Response if not included in their Standard Basic Feature List:An OTA server should be used to manage the device configuration over the Air
b) Automatic device configuration mechanism should be used that the user’s GPRS/EDGE capable handset would be configured automatically enabling use of the offered services immediately.
3.12 Messaging Gateway (GW)
3.12.1 General
This section describes the requirements for the Messaging Gateway.
In the Technical Response, the Bidder shall provide:
- Detailed descriptions, specifications, dimensioning rules and expansion possibilities;
- Hardware and software roadmaps;
- “Standard Basic Feature List”;
- “Standard Optional Feature List”.
3.12.2 Required Features
The Bidder shall provide information about the availability of the Messaging Gateway features listed hereafter and shall take these into account in their Response if not included in their Standard Basic Feature List:
a) The messaging GW should provide interoperability between value added service provider (VASP) and the SMSC and the MMSC;
b) The messaging GW should support SMPP,MM7, SMPTP, XML, and http interfaces;
c) Interoperability for SMS messages between Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), and Global System for Mobile (GSM) communications, and General Packet Radio Service (GPRS) networks should be provided;
3.13 Optimizer Server
3.13.1 General
This section describes the requirements for the Optimizer Server. The optimizer server is used to reduce the size of downloaded data hence it maximizes the performance and pro-vides the best user experience on the used bandwidth either on GPRS, or EDGE. The packet core network will enable corporate and SME connectivity for wireless office applica-tions.
In the Technical Response, the Bidder shall provide:
- Detailed descriptions, specifications, dimensioning rules and expansion possibilities;
- Hardware and software roadmaps;
- “Standard Basic Feature List”;
- “Standard Optional Feature List”.
3.13.2 Required Features
The Bidder shall provide information about the availability of the Optimizer Server features listed hereafter and shall take these into account in their Response if not included in their Standard Basic Feature List:
- The Packet Network should support different security and authentication mechanisms:
a) Enhanced RADIUS/DIAMETER support;
b) Support Access Control;
c) Support Access Restriction;
d) Support flexible authentication and authorisation methods (user/corporate in case of corporate connections).
3.14 Middleware platform
This section describes the requirements for the middleware platform.
In the Technical response the bidder shall provide:
-Connectivity capability with network elements (SMSC, MMSC, IN, HLR, Soft-Switch, VAS platforms, etc..)
-Support for Telecom grade interface protocols and specs such as TMN (CMIS, CMIP, Q3, SMPP, FTAM, etc..)
-Support for programmatic interface (SOAP/XML, CORBA, RMI, IIOP, Java library/proprietary server, Delphi/VB components/proprietary server, Sync/Async MOM, etc.)
-Available programmatic libraries for integration with external systems.
-Existing provisioning and customer care functionalities.
-Existing API functionalities (e.g. add sub, add service, get info, set info , etc.)
4. Network Roll-out
4.1 Definition of Phases and Regions
The following figure presents the definition of the phases of the network roll-out.
Figure 3 – Definition of Roll-out Phases
Phase Definition Start End
0 Launch Licence Award 4 months
The RFP covers the first Launch phase which is awarding of the licence and Network to be commercial launch in 4 months.
Figure 4 – Islands Covered by the Main Offices
4.2 Traffic Model
The following figure presents a basic traffic model for Year 1 to be considered for the dimensioning of the various network elements and links.
Figure 5 – Traffic Model
Outgoing and incoming Minutes of Use 196 min
Minutes generated by Roamers 43 min
FOC Minutes (Emergency Recharge) 2 min
Total minutes/Month/Subscriber 241 min
Busy Hour Call Attempt 1
Daily MOU/Subscriber 8.03 min
Busy Hour traffic is assumed to be 15% in Seconds 72.2 sec
Mean Holding time= Talk time + Ringing time assumed 5 seconds 77.27 sec
Erlang = MHT*BHCA/3600 22 mlErlng
The busy hour traffic per subscriber is estimated at 22 mE for Yr. 1, 21 mE for Yr. 2 and 20 mE for following years.
4.3 Radio Network
The next figures give an estimation of the quantity of equipment required for the Radio Network.
Figure 6 – BTS and TRX for all Inhabited Islands
Yr.1 Yr.2 Yr.3 Yr.4 Yr.5 Yr.6 Yr.7 Yr.8 Yr.9
Yr.10
No. of BTS* 122 124 126 128 130 131 132 133 134
135
No. of TRX 450 516 603 633 690 705 711 723 741
765
4.3.1 BSC
The following figures present the Carried per BSC.
Figure 7 – BSC Dimensioning
Yr.1 Yr.2 Yr.3 Yr.4 Yr.5 Yr.6 Yr.7 Yr.8 Yr.9
Yr.10
BSC1 28.60 363.67 448.59 519.54 574.96 616.45 651.16 685.80 720.44 755.07
BSC2 250.17 398.23 493.05 568.90 629.58 675.10 713.02 750.95 788.87 826.80
BSC3 97.23 154.68 191.51 220.98 244.55 262.23 276.96 291.69 306.42 321.15
BSC4 123.63 196.68 241.07 280.98 310.95 333.43 352.16 370.89 389.62 408.36
4.3.2 Quality of Service
The under-mentioned figure present the QOS of the Network.
Figure 8 – QOS of the Network
Service area (urban) 95% in-building
Service area (suburban) 95% in-street
Voice GoS 2% Erlang B
Call success rate 98%
Call failure rate (drop) 1.0%
Handover success rate 98%
Post-dial-delay < 10 seconds
SMS success rate 98%
Signalling path GoS 0.1% Erlang B
Network availability 99.997%
4.4 Core Network
4.4.1 MSC/VLRs
The next figures present the requirements for MSC/VLRs in terms of total Erlang.
Figure 9 – MSC/VLR Dimensioning
Yr.1 Yr.2 Yr.3 Yr.4 Yr.5 Yr.6 Yr.7 Yr.8 Yr.9
Yr.10
MSC1 699.63 1111 1374 1590 1760 1887 1993 2099 2205.4 23311
4.4.2 HLR/AuCs
The next figure presents the requirements for HLR/AuCs in terms of subscriber number.
Figure 10 – MSC/AUC
Yr.1 Yr.2 Yr.3 Yr.4 Yr.5 Yr.6 Yr.7 Yr.8 Yr.9
Yr.10
MSC1 30000 50000 65000 75000 83000 89000 94000 99000 104000 109000
4.4.3 International Gateway
The next figure presents the requirements for the International Gateway.
Figure 11 – International Gateway Dimensioning
Yr.1 Yr.2 Yr.3 Yr.4 Yr.5 Yr.6 Yr.7 Yr.8 Yr.9
Yr.10
No. of E1 Required to/From
Wataniya International GW @ 1% GOS 0 0 0 0 11 13 14 14 16 17
4.4.4 GPRS Core
Figure 12 – GPRS Core
Yr.1
GPRS/EDGE subscribers 20,000
Traffic per subs UL - input [kbytes per BH] 15
Traffic per subs DL - input [kbytes per BH] 35
4.4.5 Interconnect
Figure 13 – Interconnect Strategy
Yr.1 Yr.2 Yr.3 Yr.4 Yr.5 Yr.6 Yr.7 Yr.8 Yr.9
Yr.10
No. of E1 Required to/From
PSTN & International @ 001 GoS 20 30 33 37 28 27 26 25 23 22
No. of E1 Required to/From
other Mobile operators @ 001 GoS 12 17 21 25 28 30 32 35 37 40
4.5 IN Platform
IN requires high availability since most of the subscribers of Wataniya Telecom will be prepaid subscribers and that the main usage of IN will be to support prepaid.
The IN Dimensioing should follow the dimensioning of the Matrix for the MSC as 95% of the subscribers will be prepaid
4.6 Messaging Centres
The following figure presents the requirements for the messaging centres
Figure 14 – VMSC
2004 2005 2006 2007 2008
VMS Subs
(‘000) 30000 50000 65000 75000 83000
Figure 15 – SMSC and MMSC
Throughput
(mes-sage/s) 2004 2005 2006 2007
SMSC 10 20 20 20
MMSC 1 5 5 10
4.7 Charging Centre
The Charging Centre shall be dimensioned to accommodate messaging and data throughput (essentially SMS, and MMS).
4.8 Network Availability
Figure 16 – Network Availability
Availability %
Signalling links 99.998
Traffic links 99.995
MSC 99.997
HLR 99.998
IN 99.997
BSC 99.95
BTS 99.6
4.9 Core Network Design Assumption
Figure 17 – Assumption
Total Subs 110,000 SUBS
Mean Holding Time 77.27
Erlang / Sub in BH 22 Erlang
Grade Of Service (GOS) 1%
C7 signaling load (Erl) 0.2
IMSI attach per sub, per hour 0.5
IMSI detach per sub, per hour 0.5
Inter-MSC handover per sub, per hour 0.02
MSC Capacity in Erlang 3500 Erlang
4.10 Coverage Rx level Assumptions:Figure 18 – Coverage Rx Level Assumption
Urban Level -65 dBm
Suburban/Residential Level -73 dBm
Highway Urban Level -81 dBm
Highway Rural Level -83 dBm
Rural Level -90 dBm
Open Level -104 dBm
4.10 Project Management
Project milestone schedule should be provided with customer acceptance testing schedules at several milestones during project life-cycle.
DATE
(1) WATANIYA TELECOM MALDIVES PRIVATE LIMITED
(2) Dinesh Durairaj
EMPLOYMENT AGREEMENT FOR Senior Manager Reatils
CONTENTS
1. INTERPRETATIONS 3
2. AGREEMENT 4
3. COMMENCEMENT OF EMPLOYMENT 4
4. DUTIES 5
5. ASSOCIATED COMPANIES 5
6. OTHER INTERESTS 5
7. REMUNERATION 6
8. EXPENSES AND ALLOWANCES 6
9. TRANSPORTATION ALLOWANCE 6
10. SICKNESS PAY 6
11. HOLIDAYS 7
12. PENSION AND MEDICAL INSURANCE SCHEMES 7
13. CONFIDENTIALITY 7
14. TERMINATION FOR CAUSE 7
15. LIQUIDATION OR RECONSTRUCTION 8
16. GRIEVANCES 8
17. PROTECTIVE COVENANTS 8
18. INVENTIONS 10
19. SEVERABILITY 10
20. WARRANTY 10
21. NOTICES 10
22. AMENDMENTS 11
23. GOVERNING LAW 11
THIS AGREEMENT is made on the 07th of May 2005
BETWEEN
(1) WATANIYA TELECOM MALDIVES PRIVATE LIMITED, a private company limited by shares incorporated under and in accordance with Law No. 10/96 of the Republic of the Maldives whose registered office is located at 2nd Floor (East Wing), Aage'12 Boduthakurufaanu Magu, Henveiru Male' 20094, Maldive Islands and which is registered with the Government of the Maldives Ministry of Trade and Industries with company registration number C-633/2004 (the "Company"); and
(2) Dinesh Durairaj of # 39 G Glenlyon Bazzar, Agrapatana, Sri Lanka, a Srilankan National and holder of Passport Number M 1691984 (The "Employee").
IT IS AGREED AS FOLLOWS
1. Interpretations
1.1 Unless the context otherwise requires each of the following expressions shall where used in this Agreement have the meaning set out opposite it in this clause
"the Agreement" or "this Agreement" this agreement, including all amendments and modifications to this agreement, as may from time to time be agreed in writing by the Parties;
"Associated Company" any firm company corporation or other organisation which is directly or indirectly controlled by the Company or which is in common control with the Company;
"Business Day" a day on which commercial banks are open to transact businesses with the general public in the Maldives;
"CEO" the Chief Executive Officer of the Company;
"Commencement Date" 28th May 2005;
"Employment" the employment of the Employee under and pursuant to the terms and subject to the conditions of this Agreement;
"Immigration" the Republic of the Maldives Immigration Department;
"Labour Department" the Republic of the Maldives Ministry of Labour & Social Affairs;
"Labour Law" the Labour Law of the Republic of the Maldives from time to time in force;
"Maldives" the Republic of the Maldives;
"Manager" Senior Manager Retail;
"Parties" the parties to this Agreement and the expression "Party" shall mean either one of the Parties;
"Territory" the Republic of the Maldives; and
"Year of the Employment" the period of three hundred and sixty five days starting on the Commencement Date and each period of three hundred and sixty five (365) days thereafter.
1.2 Unless the context otherwise admits references in this Agreement to
(a) "month" "monthly" "year" and "yearly" and any other references in time shall be construed by reference to the Gregorian calendar;
(b) clauses sub clauses paragraphs and Schedules shall be references to clauses and paragraph and sub clauses in and Schedules to this Agreement; and
(c) any enactment should be construed as a reference to every amendment or re enactment (whether before or after the date hereof) and to any previous enactment which such enactment has replaced (with or without amendment) and any regulation or order made thereunder.
2. Agreement
2.1 The Company shall employ the Employee and the Employee shall serve the Company as the Senior Manager Retail on and subject to the terms and conditions specified in this Agreement.
2.2 The Employee's principal place of work shall be the Company's premises in the Maldives.
3. Commencement of Employment
3.1 The Employment will commence on the Commencement Date and subject to clause 14 shall continue for a period of two years and thereafter unless and until terminated by either Party giving to the other not less than prior 60 days written notice taking effect on or at any time after the end of such 60 day period.
3.2 Notwithstanding the provisions of sub clause 3.1, the first 90 days of the Employment shall be a probationary period during which time the Company may terminate this Agreement upon seven days prior written notice.
3.3 The Employee's period of continuous employment will begin on the Commencement Date. No previous employment with any other employer shall be treated as continuous with the Employment
4. Duties
4.1 The Employee shall:
(a) well and faithfully serve the Company and use their utmost endeavours to promote the interests of the Company and perform to the best of their ability all the duties of the Manager and such other functions within the Company (being not inconsistent with their position) as the Company may reasonably require and whenever required so to do give an account to the Company of all matters with which they are entrusted;
(b) comply with all reasonable and lawful directions and instructions given by or with the authority of the Company;
(c) work such hours as are reasonably necessary to ensure the proper discharge and fulfilment of their duties; and
(d) attend and work at any premises of the Company in the Territory and travel and work both in the Territory and abroad as necessary for the proper discharge and fulfilment of their duties.
5. Associated Companies
The Employee may be required in pursuance of their duties to perform services not only for the Company but also for any Associated Company and without further remuneration (except as otherwise agreed) to accept such office or position in any Associated Company which is consistent with their position as Senior Manager Retail of the Company.
6. Other Interests
6.1 The Employee shall not during the Employment without the prior consent in writing of the Company engage or be concerned or undertake or be interested in whether directly or indirectly any business or occupation which is in competition with the Company or any Associated Company or without the prior consent of the Company become an employee or director (save in a non employee capacity) or agent or partner of any other person firm or company provided that the Employee may acquire or hold any class of securities in any company if such class of securities is traded on any securities market and they (together with their spouse children parents and parents' issue) neither holds nor is beneficially interested in more than a total of 5% of any single class of securities in that company from time to time in issue.
6.2 Subject to any regulations issued by the Company which may be applicable to the Employee, the Employee shall not be entitled to receive or obtain directly or indirectly any discount, rebate or commission in respect of any business transacted (whether or not by him) by or on behalf of the Company or any Associated Company and if the Employee (or any firm or company in which the Employee is interested) shall obtain any such discount rebate or commission the Employee shall account to the Company for the amount received by them (or a due proportion of the amount received by such company or firm having regard to the extent of their interest therein).
7. Remuneration
7.1 The Company shall pay to the Employee for the Employment a basic salary at the rate of Eighteen Thousand United States Dollars, (18 000) per annum. The salary will accrue from day to day during the continuance of the Employment and shall be payable monthly by equal instalments in arrears.
7.2 If the Employee shall be employed in accordance with this Agreement for part only of any financial year of the Company, the Employee shall be entitled to a rateable proportion (apportioned on a time basis) of such salary as the Employee would have received if the Employee had been employed for the whole of that year.
7.3 At the end of the first 12 months of Employment, the Employee shall be paid a bonus of up to Three months salary; Four Thousand Five Hundred United states Dollars (US$ 4500) subject to their individual performance and achievement of the Company’s performance targets. The CEO and the Board of Directors of the Company shall determine the performance criteria and the goals required to reach the bonus target.
8. Expenses and Allowances
8.1 The Company shall reimburse to the Employee (against receipts or other appropriate evidence) all reasonable travelling, accommodation, entertainment and other out of pocket expenses properly incurred and defrayed by the Employee in the course of the Employment.
8.2 The Company shall provide for the Employee a Economic class air tickets from Srilanka to the Maldives at the start of the Employment and from the Maldives to Srilanka for each completed Year of the Employment and, unless the Employment has been terminated pursuant to clause 14, from the Maldives to Srilanka at the end of the Employment. The Employee will be entitled to cash in lieu in respect of any air tickets not taken up by them.
8.3 The Company shall provide the Employee with an accommodation allowance in accordance with the housing and accommodation policy of the Company from time to time in force.
8.4 The Company will provide the Employee with a relocation allowance of One Thousand Five Hundred United States Dollars, One Thousand (US$1500) for the purposes of enabling the Employee to purchase furniture and household goods.
9. Transportation Allowance
The Employee will be paid a transporation allowance in accordance with the Company’s transportation allowance policy from time to time in force. The transportation allowance will be paid in arrears on the last day of each calendar month during the Employment. [season ticket Male’/Hulhumale’/Male’ if applicable only]
10. Sickness Pay
The Employee will be entitled to receive their normal rate of remuneration (which shall be inclusive of statutory sick pay entitlement) during the first ninety (90) days of absence (whether consecutive or otherwise) from the Employment due to sickness or injury in any Year of Employment and for any subsequent such absence in the same Year of Employment to such further payment if any as the Company may deem appropriate. Payment will be subject to the Employee producing to the Company satisfactory evidence of their indisposition.
11. Holidays
The Employee shall be entitled with normal remuneration to public holidays in the Territory and a further 30 working days' holiday in each Year of the Employment to be taken at such times as are agreed with the CEO of the Company. The Employee shall not be entitled to pay in lieu of holidays not taken during any Year of the Employment unless they are prevented from taking their full holiday entitlement in such Year of the Employment by virtue of express written instructions of the CEO or if it had been previously agreed by the CEO that it would be inconvenient or undesirable that the Employee should take their full entitlement.
12. Pension and Medical Insurance Schemes
The Employee will be entitled at the Company's expense to participate in an appropriate medical care and life insurance scheme that will be operated by the Company.
13. Confidentiality
13.1 The Employee shall not during the Employment or after the termination thereof make use of for their own purposes or those of any other person firm or company or disclose to any person (except the proper officers of the Company or as required by law) any trade secrets or confidential information relating to the business accounts affairs or finances of the Company or any Associated Company or their customers or suppliers.
13.2 The obligations contained in sub clause 13.1 shall continue to apply without limitation in time following the termination of the Employment howsoever arising but they shall cease to apply to any information or knowledge which may subsequently come into the public domain other than by way of unauthorised disclosure.
13.3 All plans statistics records and other documentation (including copies thereof) or whatsoever nature relating to the business of the Company or any Associated Company or their customers or suppliers shall immediately be returned by the Employee to the Company in the event of the termination of the Employment howsoever arising (or at any earlier time on demand).
14. Termination for cause
14.1 Notwithstanding the provisions of clause 2, the Company may terminate the Employment by written notice with immediate effect if the Employee:
(a) fails to perform their duties with the degree of care skill or diligence reasonably to be expected of the Employee having regard to their position; or
(b) is guilty of material dishonesty or other gross misconduct or wilful neglect of duty or commits any other serious breach of this Agreement other than a breach which is effectively remedied within such reasonable period as the Company may specify; or
(c) wilfully or negligently fails to comply with any lawful instructions of the Company or any lawful instructions of any person or persons duly authorised by the Company to give such instructions; or
(d) is convicted of a criminal offence (other than for motoring in respect of which imprisonment is not imposed); or
(e) is adjudicated or declared bankrupt applies for or has made against him a receiving order makes any composition with their creditors generally or suffers any similar or like action in consequence of debt; or
(f) is adjudged by a medical practitioner having experience in the premises to be of unsound mind; or
(g) shall for a period of ninety (90) days whether consecutive or otherwise in any Year of Employment be incapable of performing their duties hereunder by reason of ill health accidental or otherwise.
14.2 On the termination of the Employment, howsoever arising the Employee shall co-operate in the cancellation without claim for compensation except as provided in this Agreement or in the Labour Law of their work permit and residence visa.
14.3 The Company shall be entitled at its sole discretion to give the Employee pay in lieu of any notice of termination given to him or require the Employee not to attend work during any period of such notice. In the event of the Employee not being required to work all or part of any period of notice the Employee shall not be entitled to receive any damages or compensation in respect of any bonus or profit share or any Commission which would otherwise be due to the Employee hereunder for the period which would have represented the period of notice had the Employee been required to work it.
14.4 The termination of the Employment shall be without prejudice to any right the Company may have in respect of any breach by the Employee of any of the provisions of this Agreement which may have occurred prior to such termination.
15. Liquidation or Reconstruction
The Employee shall have no claim against the Company in respect of the termination of the Employment if such termination occurs by reason only of the liquidation of the Company for the purposes of amalgamation or reconstruction provided that the Employee is offered employment with a company resulting from such amalgamation or reconstruction on terms no less favourable to the Employee than the terms of this Agreement and for a period not less than that to which the Employee would otherwise have been entitled.
16. Grievances
If the Employee has any grievance relating to the Employment, the Employee should apply to the Company.
17. Protective Covenants
17.1 The Employee recognises that whilst performing their duties hereunder they will have access to and come into contact with a considerable amount of confidential information and trade secrets belonging to and relating to the Company or any Associated Company and will obtain personal knowledge of or influence over customers and employees of the Company or any Associated Company Accordingly the Employee undertakes in consideration of their employment hereunder that they will be bound by the following restrictions
(a) that they will not without prior written consent of the Company for a period of twelve (12) months after the date of termination of the employment be engaged interested or concerned (whether as shareholder director employee sub contractor partner consultant proprietor agent or otherwise) directly or indirectly in carrying on any business competitive with any of the businesses which the Company or any Associated Company at the time of such termination carries on within the Territory;
(b) that they will not for a period of twelve (12) months after the termination of the Employment either personally or by their agent and whether for himself or on behalf of any other person induce or endeavour to induce any officer or employee of the Company or any Associated Company to leave such employment; and
(c) that they will not for a period of twelve (12) months after the termination of the Employment induce solicit or endeavour to entice away from the Company or any Associated Company on their own account or for the account of any person in active or potential competition with the Company or any Associated Company any person who was at any time within the period of twelve (12) months prior to such cessation customer or in the habit of dealing with the Company or any Associated Company.
17.2 Nothing in this clause 17 shall prevent the Employee from being the holder or beneficial owner for investment purposes only of any class of securities in any company if such class of securities is traded on any securities market and they (together with their spouse, children, parents and parents' issue) neither holds nor is beneficially interested in more than a total of 5% of any single class of the securities in that Company from time to time in issue.
17.3 Each of the undertakings contained in each of the paragraphs of sub clause 17.1 shall be and is a separate undertaking by the Employee and is enforceable by the Company separately and independently of the right of the Company to enforce any one or more of the other covenants contained in sub clause 17.1 and if any such undertaking is found to be void but would be valid if some part thereof were deleted or the period or areas of application were reduced then such undertaking will apply with such modification as may be necessary to make it valid and effective.
17.4 While the restrictions contained in sub clause 17.1 above are considered by the Company and the Employee to be reasonable in all the circumstances it is recognised that restrictions of the nature in question may fail for technical reasons any accordingly it is hereby agreed and declared that if any one or more of such restrictions shall either by itself or themselves or taken with others be adjudged to be invalid as exceeding what is reasonable in all the circumstances of the protection of the interests of the Company but would be valid if any particular restriction or restrictions were deleted or if part or parts of the wording thereof were deleted or restricted or limited in a particular manner or if the period or area thereof were reduced or curtailed then the said restrictions shall apply with such deletion restriction limitation, reductions curtailment or modification as may be necessary to make them valid and effective.
17.5 The Employee acknowledges that none of the restrictions contained in sub clause 17.1 shall prevent the Employee from earning their living.
18. Inventions
18.1 If at any time during the continuance of their employment in accordance with this Agreement, the Employee makes or discovers or participates in the discovery of any invention or improvement upon or addition to an invention which is applicable to the business for the time being carried on by the Company or any Associated Company the same shall be forthwith communicated by the Employee to the Company and shall be the absolute property of the Company and at the request and expense of the Company the Employee shall give and supply all such information data and drawings as may be requisite to enable the Company to exploit such invention improvement or addition to the best advantage and shall execute and do all such documents and things as may be necessary or desirable for obtaining patent or similar protection for the same in such part or parts of the world as may be specified by the Company and for vesting the same in the Company or as it may direct.
18.2 The Employee hereby irrevocably appoints the Company to be their attorney and in their name and on their behalf to sign execute do and deliver any document or thing for the purpose of this clause 18.
19. Severability
The various provisions of this Agreement are severable and if any provision or identifiable part thereof is held to be invalid or unenforceable by any court of competent jurisdiction then such invalidity or unenforceability shall not affect the remaining provisions or identifiable parts thereof in this Agreement.
20. Warranty
The Employee represents and warrants that they are not a party to any agreement contract or understanding whether of employment or otherwise which would in any way restrict or prohibit him from undertaking or performing the duties of the Employment or any of them in accordance with the terms and conditions of this Agreement.
21. Notices
21.1 All notices required to be given or information supplied by either of the Parties to the other pursuant to the provisions of this Agreement must be in writing and shall be sent
(a) by hand with a copy sent by registered post;
(b) by registered post; or
(c) by facsimile with a copy sent by registered post;
(d) in the case of service on the Company to:
2nd Floorm Urban Development Unit Building
Hulhumale’ – K. Atoll
North Maldives
Republic of Maldives
Facsimile: +960 350 519
For the attention of: The Chief Executive Officer
and in the case of service on the Employee to:
# 39 G Glenlyon Bazzar, Agrapatana, Sri Lanka
or to such other address or telefax number as may from time to time be notified in writing by either of the Parties to the other.
21.2 Any notice delivered by hand shall be deemed to have been served at the time of delivery and any notice sent by registered mail to have been served on the third day after the date on which it is posted and any notice sent by telefax on the date on which such telefax is transmitted or in each case if such is not a Business Day on the next succeeding Business Day.
22. Amendments
Any amendment to the provisions of this Agreement shall be in writing and signed by the Parties or their fully authorised representatives.
23. Governing Law
This Agreement is governed and construed in accordance with the law of the Republic of the Maldives and the Parties submit to the non exclusive jurisdiction of the Maldivian Courts.
AS WITNESS the hands of the Parties or their duly authorised representatives the day and year first written.
SIGNED by William Mark Hanna
Chief Executive Officer
The duly authorised signatory of
WATANIYA TELECOM MALDIVES PRIVATE LIMITED
SIGNED by Dinesh Durairaj
helo. i m not working in watniya but am really intersted in talkin to you all who are involved.
email: ageyshey@gmail.com
Post a Comment