Mozambique VoIP Services and IX Extension

Mozambique VoIP Services and IX Extension Afonso Timba Albertina Inacio David Blomberg Gustavo Azzolin de Carvalho Pires Joao Antonio Massinque Project Plan 1 / 32

Changelog Version Date Author Description Status 1 05/01/19 Gustavo & David Initial draft 2 05/01/21 All Stakeholder analysis, list of deliverables (updated), functional roles/member responsibilities (updated), team member CVs 3 05/02/01 All Phases of the technical implementation (updated), goals, change log, list of deliverables (updated; deadlines), business plan description, risk analysis (updated), sub-task responsibility (updated) Draft Draft Draft Project Plan 2 / 32

Index Changelog... 2 Abstract... 4 1 Project background and context... 5 2 Project Description... 6 2.1 Project Purpose... 6 2.2 Goals... 6 2.2.1 VoIP Voice over IP... 6 2.2.2 MozIX extension... 7 2.3 Scope... 7 3 Work Breakdown Structure... 7 3.1 Deliverables... 7 3.2 Project phases... 8 3.2.1 Project planning... 8 3.2.2 Initial Research Phase... 8 3.2.3 Requirements Definition and Analysis... 9 3.2.4 Sub-projects design... 9 3.2.5 Sub-project pre-implementation... 9 3.2.6 Sub-project testing... 9 3.2.7 Integration of sub-projects and testing... 9 3.2.8 Execution phase... 9 3.3 Concurrent tasks... 10 3.3.1 Artifact Support Documents... 10 3.3.2 VoIP Business Plan... 10 4 Project Time Plan... 12 5 Risk Analysis... 14 5.1 Risks Matrix... 14 5.2 Risk Analysis... 14 6 Principal- and stakeholder analysis... 16 6.1 The Principal: UEM... 16 6.2 Local ISPs... 16 6.3 SIDA... 17 6.4 The Project Team... 17 6.5 KTH... 17 6.6 Stakeholders Analysis Matrix... 17 7 The Project Team... 19 7.1 Team members... 19 7.2 Task responsibilities... 19 7.3 Team Management... 20 Appendix 1... 21 Appendix 2... 24 Appendix 3... 26 Appendix 4... 29 Appendix 5... 31 Project Plan 3 / 32

Abstract The aim of this document is to describe and specify the planning aspects regarding the Mozambique Voice over IP and Internet Exchange Project. The project is planned in at KTH (Kungliga Tekniska Högskolan Stockholm Sweden), and later executed at UEM (Eduardo Modlane University Maputo - Mozambique). This project constitutes the core of the course. Project Plan 4 / 32

1 Project background and context The Eduardo Mondlane University (UEM) is the largest Mozambican institution in the field of ICT (Information and Communication Technology). The cooperation between The Royal Institute of Technology (KTH) and UEM has resulted in the establishment of an Internet Exchange (IX) in 2002 as well as some networks at UEM. Voice over IP (VoIP) is becoming increasingly popular. With VoIP, one network is required for both voice and data traffic. In addition, a number of services, such as conference calls and answering services can be implemented with little additional effort. In addition, as the VoIP technology matures, it has the potential to provide serious competition to PSTN (Public Switched Telephone Network) providers. Information technology... is a powerful force that can and must be harnessed to our global mission of peace and development. This is a matter of both ethics and economics; over the long term, the new economy can only be productive and sustainable if it spreads worldwide and responds to the needs and demands of all people. I urge everyone in a position to make a difference to add his or her energies to this effort. Kofi Annan, Secretary-General, United Nations Clearly, the implementation of VoIP and the extension of the range of services offered by the Internet Exchange is an important step in the development of ICT in Mozambique. Project Plan 5 / 32

2 Project Description Project name: MoVoIX - Mozambique VoIP services and IX extension Principal: UEM, represented by Americo Muchanga Sponsors: KTH, UEM and SIDA Coach: Khurram Jahangir Khan 2.1 Project Purpose The purpose of the project is to deliver operational VoIP services in the UEM network, to help to change the regulation in the VoIP area and to extend the range of services provided by MozIX, Internet Exchange in Maputo. 2.2 Goals The goals include the implementation of a VoIP solution and an extention of the range of services offerered by MozIX. 2.2.1 VoIP Voice over IP The VoIP implementation should meet the following criteria by the termination of the Project Execution Phase in May: 1) It should be possible to register a user account through a web interface. On registration, a user name/phone number will be obtained. 2) Once registered, it should be possible to make phone calls to any another IP phone, inside and outside the university. In this context, the term IP phone includes IP phones as well as soft phones and regular phones connected to a terminal adapter. It should also be possible to receive phone calls from any other IP phone user. 3) With respect to point 2), the service will not be guaranteed for calls within private IP networks. In other words, the VoIP implementation will not accommodate calls between users who are behind the same Network Address Translation (NAT) device, unless this device supports double port mappings hairpinning. 4) It should, with an IP phone, be possible to place and receive calls from a phone connected to the PSTN network. The calls in this last category should be routed through a PSTN gateway, which is part of the project scope. 5) With respect to point 4), if a connection to the PSTN network is not obtained, the PSTN gateway should be connected to the PBX, provided that the PBX can accommodate this. It should, with and IP phone, be possible to place and receive calls from a phone connected to the PBX. Project Plan 6 / 32

2.2.2 MozIX extension In addition to the VoIP service, by the end of the Project Execution Phase in May, this project has to provide the following services to the Mozambique Internet Exchange, MozIX: 1) Peer Switch Upgrading this project aims to provide performance analysis of the switch. The switch will be upgraded, if it is required. The team will produce a performance analysis that will focus on resilience and redundancy. Based on current and historic traffic loads, we will also present a forecast of future requirements. Based on the performance analysis, the final decision will be made together with the principal. 2) Solutions for time precision and source will be provided. 3) A mail server in open software platform will be implemented. In addition, a web-mail service will be provided. 2.3 Scope The main task is the implementation of Voice over IP and the extension of the range of services offered by the Internet Exchange. In addition, one of the purposes of the project is to help affect regulatory change in the VoIP area. This objective will be addressed by demonstrating a fully functional VoIP implementation at the 3 rd International Workshop on Open Access, which is held in Maputo in Mary. In addition, we will provide a business plan for the VoIP system. This is deiscussed further in the section entitled VoIP Business Plan. It should be considered within scope all the goals previously mentioned. 3 Work Breakdown Structure 3.1 Deliverables - Project web-site deadline 2005-01-17 - Project Plan deadline 2005-01-19 - Biweekly progress reports on the project web-site deadline biweekly from 2005-01-26 on - Informative video (3 min) deadline 2005-05-18 noon - Mid-term presentation 15 th until 18 th March 2005 8h until 17h - Final Project Report deadline 2005-05-14 noon - Oral presentation deadline 23 rd and 24 th May 2005 8h until 17h - Exhibition in Electrum deadline 2005-05-25 10h until 14h - Press release - deadline 2005-05-19 - noon - Conference contribution (optional) 10 th and 11 th May 2005 - Lessons Learned deadline 2005-05-26 - noon Project Plan 7 / 32

- Operational VoIP services at UEM deadline 2005-04-30 - VoIP Business Plan - VoIP and IX Policy documents - Website for the UEM VoIP-services - Administrative guidelines for the VoIP and IX-services, including troubleshooting - Learning material for the training of local staff deadline 2005-05-05 - Presentation and demonstration at the 3rd International Workshop on Open Access to be held in Maputo in May 2005-05-10 th and 11 th 3.2 Project phases The completion of the technical tasks of the project is structured in a set of phases. Each phase should produce a distinctive set of results. There are dependency relations with previous and following phases. This methodology aims to assist the project development in a structured way, permitting to trace a well defined project time plan, and also allowing a more consistent quality assurance during each phase. 3.2.1 Project planning The Project Plan, the present document, has as objective to establish a methodology which will be followed during the whole developing phases. It describes the purpose, scope and objectives of the project using the preliminary support documents (e.g. Project Specification ). It includes, for example, a discussion of business facts and needs, any imposed constraints, resources provided, stakeholder analyses and a risk analysis. It also states the start and end dates of the project. 3.2.2 Initial Research Phase Acquisition of general knowledge and an overall feel for the subjects related to the technical aspects of the project. These include purpose, functions and possible implementations of VoIP (e.g. which protocol to use) and PSTN Gateway (e.g. a Linux machine running Asterisk), time server solutions and a free mail server. During this phase, the specific competencies of the team members will emerge. Hence, the initial division of responsibility could be revised as several small technical sub-groups will be formed. The purpose is to effectively harness the skills of the respective team members as well as stimulate cooperation between every team member. During this phase, a set of potential secondary project goals are likely to emerge, which will be considered in a specific Development Gantt Chart. Project Plan 8 / 32

3.2.3 Requirements Definition and Analysis Concluded the Initial Research Phase, the project will follow towards Requirements Definition and Analysis. This phase will be supported mainly by interaction between team members, teaching team, stakeholder contacts, vendors and technical specialists. Due to the fact of time and distance constraints regarding our main client (UEM), this phase should be complemented with reasonable and flexible assumptions in order to provide a more suitable solution for each one of the sub-projects. During this phase, the project principal (UEM) and stakeholders (technical experts, teaching team) will provide the project team with further specific requirements and make reference to the actual resources provided by the project principal. In case of scarce details and requirements regarding the project, the group should be able to make reasonable assumptions which should be possible to implement in a full scale solution, with any budget constraints in mind. 3.2.4 Sub-projects design During this phase, the design of the sub-projects i.e. each individual objective, e.g. VoIP, Time server, Mail server will take place in accordance with the outcomes from the requirements definition and analysis phases. The project should deliver a Design Prototype 3.2.5 Sub-project pre-implementation With a theoretical prototype and requirements analysis done, the deployment will continue with pre-implementation of each sub-project. During this phase, the group will have the opportunity to do some test labs and implement solutions with provisory equipment provided by KTH (rented laptops, network interconnection equipments, etc). It is important to mention that the sub-projects will be implemented in practice separately. 3.2.6 Sub-project testing Proceeding to the testing phase, through exhaustive tests, the group will evaluate the solutions implemented according to testing and requirements premises. 3.2.7 Integration of sub-projects and testing Once every sub-project is tested, it should be possible then to integrate them and test the entire solution at the same time. 3.2.8 Execution phase This phase will be held in UEM (Maputo, Mozambique). This final part of the deployment stage will approach to some other relevant deliverables like: - Learning material preparation to users and technical administrators - VoIP Portal Project Plan 9 / 32

3.3 Concurrent tasks The above phases describe the development of the primary deliverable operational VoIP services and added IX features. The following related deliverables are scheduled in the Gantt chart, to be described in the following section: - Development of website for the UEM VoIP - Development of learning material for the training of local staff - Administrative guidelines for the VoIP and IX-services, including troubleshooting In addition to these concurrent tasks, the team will also create artifact support documents, as well as a business plan for the VoIP implementation. 3.3.1 Artifact Support Documents The following documents will be delivered in order to assist the internal integration between team members, and also the users and administrators that will be involved in this project. - Scope and non-scope definition of the scope and non-scope of this project. - Requirements Analysis confirmation of the architectural requirements - System Architecture Design Technologies described, system architecture, logical viewing, revision of technological premises - Acronyms/Glossary - Project General Gantt Chart overall project time planning. - Development Gantt Chart deployment time planning, focus on development phases. 3.3.2 VoIP Business Plan The main purpose of the business plan is to stimulate the regulatory process. Currently, there are several obstacles on the route towards a commercial implementation of VoIP in Mozambique. The Mozambican landline operator, Telecomunicações de Moçambique (TDM), is a monopoly that controls the PSTN infrastructure. TDM controls the access to the PSTN infrastructure and is required to grant access licenses only to other telecommunication companies. An ISP, or any other VoIP service provider, is not considered a telecommunication company. If such a company were to apply for a license, there is no incentive for TDM to grant one. According to the MoVoIX principal, the primary concern of TDM is the loss of revenue that would occur if national calls were bridged over Internet. For example, if a call is made from Nampula to Maputo, it will be charged at the national tariff (distances exceeding 50 km) at MT 3075/minute during peak hours. If the call instead would be transmitted over Internet and cross a PSTN gateway in Mozambique, it would be billed as a local call at MT 1794/minute during peak hours. Project Plan 10 / 32

The purpose of the VoIP business plan is the basis for the formulation of the two objectives, as outlined by the principal. These objectives are aimed primarily at the legislators. The business plan should aim to: 1. Show that VoIP is a viable technology and that its breakthrough will come. The MoVoIX project team suggests that this could be accomplished by presenting examples of successful foreign VoIP ventures. 2. Explain how the implementation of VoIP could benefit the Mozambican society. Show that VoIP allows greater utilization of the current infrastructure, compared to conventional PSTN telephony. Explain how this could benefit socially the Mozambican economy in a long term. In addition to the above objectives, the MoVoIX team proposes a third objective for the business plan: 3. The business plan should be a catalyst in the dialogue with TDM. It should explain why it makes more sense for TDM to support the development of VoIP than to work against it. Due to the size and influence of TDM, MoVoIX thinks that such cooperation would be essential for the growth of VoIP in Mozambique. Partly, the same evidence used to support the first objective can back this third objective. Firstly, VoIP will be portrayed as an unstoppable force. Secondly, the business plan should provide evidence of how VoIP can benefit TDM. Currently, TDM is clinging to its piece of the telecommunication pie, not supporting VoIP deployments. MoVoIX wants to show that VoIP can make the pie itself grow and create a win-win situation for both TDM and commercial VoIP providers. By the use of examples and analysis, we want to answer the following questions: a) How has the advent of VoIP in other countries affected the telecommunications market, and specifically market leading companies? An obvious example would be Sweden, where Telia previously held the monopoly. b) How can the TDM use VoIP to generate additional revenues? There are several aspects that require consideration. Should TDM enter the would-be VoIP market as a competing VoIP Provider? Would TDM have any competitive advantage in this area? Could the VoIP generate revenue from infrastructure concessions and PSTN gateway agreements? How should these be structured to create a win-win situation? Would these sources of revenue balance the anticipated drop in revenue from the conventional PSTN service? A forecast of the effect of VoIP on the revenue from PSTN phone calls will be included. If, for example, the growth of VoIP reduces the charges for overseas calls, the number of calls placed from foreign countries to Mozambique could increase. When these calls cross the PSTN gateway, revenue is generated. In addition to the methods described above, a competitor analysis will be performed. Even though TDM holds the monopoly, the use of free VoIP peer-to-peer software increases. In Mozambique, there is currently no regulation of the IP side of VoIP, i.e. VoIP without crossing a PSTN gateway. The use of VoIP software in Mozambique as Project Plan 11 / 32

well as alternative means of communication, such as e-mail, will be investigated, and its impact on PSTN calls will be investigated. If such an investigation proves exceedingly difficult, the potential for growth of these means of communication will be analyzed. Could the growth of alternative communication technologies be a reason for TDM to support the development of VoIP? Could software based VoIP, e.g. Skype, threaten conventional telephony? Would early adopters of VoIP benefit? The principal has not requested a business plan for the extension of the range of services of the IX. The IX, and the additional services that will be implemented are a non-profit venture, and no need to work for a change in the regulations has been identified. 4 Project Time Plan With the phases and tasks described above, one can at this moment create a general time plan, aiming to support the efficiency and sharpness during the project deployment. The graphic below focuses on the entire process of deployment, from the beginning of the course until the final deliverable in May. The second following graphic, Deployment Gantt Chart, will focus more on the sub-projects deployment and their sub-phases. Fig.1 Project Plan Gantt Chart Project Plan 12 / 32

Fig. 2 Development Gantt Chart Project Plan 13 / 32

5 Risk Analysis 5.1 Risks Matrix Aiming at safer and better continuation of the project, it is fundamental to define a risk analysis methodology. For this project, the team agreed that the Minirisk methodology is preferred, due to its simplicity and the scarce remaining time. In this methodology we grade some different events according to their levels of influence on the project, i.e. impact levels, and their levels of probability as well. We came up with the following Minirisk Matrix: Probability 1 2 3 4 5 Event IMPACT Serious Personal Problems 1 1 2 3 4 5 Unavailability of Resources 2 2 4 6 8 10 Team s Conflits 3 3 6 9 12 15 Incorrect Requirement Analysis 4 4 8 12 16 20 Implementation Errors 5 5 10 15 20 25 Team s Disabilities 6 6 12 18 24 30 Untrustworthy Open Source Resources 7 7 14 21 28 35 Incompatibility of resources 8 8 16 24 32 40 Time Constraints 9 9 18 27 36 45 Design Errors 10 9 20 30 40 50 Tab.1 Minirisk Matrix 5.2 Risk Analysis Event : Serious Personal Problems Contention Strategy: in order to avoid this risk, it is necessary that any small personal problems, concerns or facts, regarding every team member, which could affect the project deployment, should be discussed at any time. Contingency Strategy: if for any reason, one sub-task is about to be compromised, the other team member should be able to re-arrange their sub-tasks and allocate the former sub-task to a reviewed time plan. Project Plan 14 / 32

Event : Unavailability of Resources Contention Strategy: It is responsibility of all team members to review and forecast equipments to be used, with the support of the teaching team. Contingency Strategy: arrange reasonable solution with available resources. Event: Team Conflicts Contention Strategy: open talks, honesty, and regular extra-work meetings to socialize team members. Contingency Strategy: the team should focus that the final result is above any personal value conflicts. Event: Incorrect Requirements Analysis Contention Strategy: review of Requirements Analysis by more than two team members. Contingency Strategy: if possible, adapt the actual project deployment to the Requirements Analysis. Event: Implementation Errors Contention Strategy: allocate more than one person to do a critical implementation task. Contingency Strategy: considering the time constraints, try to correct any eventual implementation error. Event: Team s Disabilities Contention Strategy: regularly check team s skills with any new competency required that has outcome. Contingency Strategy: allocation of more team member to automate the process of skill acquisition. Event: Untrustworthy Open Source Resources Contention Strategy: if possible, make use of research, implementing and testing of more than one possible solution for a specific goal. Contingency Strategy: apply patches, or else reconsider a second solution, and report the error for both strategies (applying patches and reconsidering a second solution). Project Plan 15 / 32

Event: Incompatibility of Resources Contention Strategy: reviewing of Requirements Analysis and Design Phases. Implementing and Testing Phases should be considered with exhaustion. Contingency Strategy: if convenient, apply patches, or else reconsider a second solution, and report the error for both strategies (applying patches and reconsidering a second solution). Event: Time Constraints Contention Strategy: time plan should be frequently checked considering deadlines, progress status, and any other constraint that could affect the project time scheduling. Contingency Strategy: if the constraint depends on availability of man-work-hours, the group should make it self more available and dedicated to the project. Event: Design Errors Contention Strategy: design phases divided in sub-project design phases, making more than one person responsible for one critical task. It will be provided an artifact document entitled System Architecture Design, which will be analyzed by the teaching team and some contributors. Contingency Strategy: considering the time constraints, try to correct any eventual design error. 6 Principal- and stakeholder analysis 6.1 The Principal: UEM The principal of the project is Eduardo Mondlane University (UEM). The university consists of several departments, and inter department calls are currently made via the PSTN network. The installation of VoIP will eliminate the costs for intra university phone calls. 6.2 Local ISPs The successful completion of the project will give access to a VoIP test-bed and other IXservices. By having access to this, the ISP staff can increase their knowledge in these areas and investigate the viability of the technology. In a long term perspective, this means that they could offer VoIP services to their customers. Project Plan 16 / 32

6.3 SIDA The successful completion of the project enables effective, low cost support to the local telecommunication sector. The importance of global access to information technology was highlighted in the Background section. 6.4 The Project Team The members of the team will increase their knowledge in VoIP and other IX-services as well as project management and teamwork. Working in a cross cultural team is a useful experience in a globalized world. 6.5 KTH Successful completion of the project demonstrates good competencies of its students, course staff and coordinators, and fruitful cooperation with local contributors and with overseas high school institutions (UEM). 6.6 Stakeholders Analysis Matrix In order to better view and analyze the dependencies and integration between each stakeholder, considering provided resources, potential impact on the project, etc., the following matrix was traced. Stakeholder Stake in the Project Potential impact on Project What does the Project expect the Stakeholder to provide Perceived attitudes and risks Stakeholder Management Strategy Responsibility KTH Process and Policy owner which will determine institutional administrative policy and procedures High Coaches Workspace 5 students Laptops Other resources which are in the reach of KTH Commitment to help Involvement in Project Steering Board, Regular updating meeting with project leader, i.e., team feedback. Project Supervision UEM Process and Policy owner which will determine institutional administrative policy and procedures Very High All the necessary local resources in Maputo Commitment to help Regular Meetings Project Validation Resources Support Local ISP s Represents the possibility of Business Plan High Access to a VoIP test bed and an Lack of Interest Business Plan Analysis Resources Support Project Plan 17 / 32

being implemented extended range of IX-services SIDA Hold the financial support related to traveling and accommodation in Maputo. High Traveling and accommodatio n costs for project participants, project specific equipment. Doesn t show practical acknowledgment about the project deployment None Financial Support Table 2 Stakeholder Analysis Schema Project Plan 18 / 32

7 The Project Team 7.1 Team members Gustavo Azzolin de Carvalho Pires Project Manager Takes the course for 20 credits. CV in appendix 1. David Blomberg Project Manager Takes the course for 20 credits. CV in appendix 2. Afonso Timba Takes the course for 20 credits. CV in appendix 3. Albertina Inacio Takes the course for 20 credits. CV in appendix 4. Antonio Joao Massingue Takes the course for 20 credits. CV in appendix 5. 7.2 Task responsibilities The responsibilities for each sub-project sub-tasks are divided in sub-teams, VoIP Services Sub-tasks SIP proxy PSTN GW (PRI connection) NAT Traversal Inspection (STUN, SER NAThelper) VoIP Soft-clients Other VoIP Services BSS (Billing Support Sytem) VoIP Webpage OSS (Operation Support System) VoIP business plan VoIP and IX Policy documents Guidelines and troubleshooting Responsible team Afonso David, Albertina Antonio Gustavo, Antonio Antonio (Voice-mail), Albertina (Conference calls) David, Antonio Gustavo David The entire team: each sub-team is responsible for documents that corresponds to the respective task. The entire team: each sub-team is Project Plan 19 / 32

Learning Material Time Server Sub-tasks Time Server (4 different solutions and quotation) Guidelines and troubleshooting Learning Material Mail Server Subtasks Solution Analysis Learning Material Guidelines and troubleshooting Switch Upgrading Performance and resilience analysis of present situation, traffic forecasts Analysis of options and quotations Guidelines and troubleshooting Project Webmaster Project Planning Mid-term Presentation Project Report Conference Preparation Informative Video Press Release Final Oral Presentation Lessons learned responsible for documents that corresponds to the respective task. The entire team: each sub-team is responsible for documents that corresponds to the respective task. Responsible team Gustavo, Albertina Gustavo, Albertina Gustavo, Albertina Responsible team Afonso, Antonio Afonso, Antonio Afonso, Antonio Responsible team Gustavo, David, Antonio Gustavo, David, Antonio Gustavo, David, Antonio David, Antonio Gustavo, David All team members All team members All team members All team members All team members Gustavo, David All team members 7.3 Team Management The project manager role is shared by David and Gustavo. The project managers have the overall responsibility for the completion of the project. Furthermore, they are responsible for the final report and presentation. Lastly, the team managers coordinate interaction with the principal and other stakeholders. Project Plan 20 / 32

Appendix 1 Gustavo Azzolin de Carvalho PIRES SQS 104 bl E ap 506 Brasília DF Phone: +55.61.321.5963 +55.61.8115.8779 Email: azzolin@tecnolink.com.br EDUCATION 2004 Master in Internetworking at KTH Royal Institute of Technology Stockholm - Sweden 2002 Networking/Telecommunication Engineering at University of Brasilia. 5th year of Informatics, Electronics and Automation Engineering at INSA-Toulouse, France, specializing in Networks and Telecommunications, as scholarship student from CAPES, for sandwich graduation 2001/2002. CERTIFICATES/TRAINING COURSES CNA Certified Novell Administrator NetWare 5 - Administration Novell Courses: NetWare 5 (300h) Networking Technologies - NDS Implementation and Design - NetWare 5 Services and Support - Integration Windows NT with IntranetWare - Netware Administration Extreme Networks Courses (180h): EWC-200c (ExtremeWare Switch L2/L3 Management and Configuration), BGP-220c (Concepts and Configuration), OSPF-220c (Focusing in on OSPF), MCR- 340 (Multicast Routing), EPI-240c (EPICenter 3.1), NTS-200c (Network Troubleshooting). TOEFL Test of English for a Foreign Language CCNA Cisco Certified Network Associate CCNP Cisco Certified Network Professional (bcran last) ENA Extreme Network Associate Project Plan 21 / 32

LANGUAGES English read, written and spoken 6 years of studies + certificate TOEFL. Spanish read, written and spoken one month intensive course in Malaga, Spain + 2 years of studies. Portuguese mothertongue. French bilingual 14 months in France + 6 week intensive course in La Rochelle, France + 2 years of studies. Swedish Intermediary level. PROFESSIONAL ACTIVITIES AND TRAINING 2004 Project Manager SAMU 192 Mobile Service to Assistance Emergencies Project delivered by SIEMENS BRASIL, UNIVERSITY OF BRASILIA and TIM BRASIL. 2003 Project Engineer, in Damovo (Brasília), working in Network Systems Coordination of Deputies Chamber actual job. 2002 Trainee with final project for Engineering INSA Toulouse working at Renault S.A. in Paris, with the development of an INTRANET site for Quality Direction of Mechanic Fabrications, for 5 months. 2000/01 System Administrator at GW Communication Ltda, during 1 year. 1999/00 5 months internship at Contrix Consulting and Services for Connectivity, working on projects and implementations for some client networks 1999 3 months internship, working as supervisor in the network of Physics Institute of University of Brasília. SEMINARS AND VARIOUS KNOWLEDGES Project Plan 22 / 32

Telecommunication Technologies GSM (Global System for Mobile Communication main subject for my final project at University, with other topics like CDMA, W-CDMA and CDMA-2000), ADSL, SONET/SDH, Wide Area Networks and Wideband transmissions (ATM). Ethernet, TCP/IP e Ipv6. Participation on the 17 th Week of Electric Engineering, at University of Brasília Participation on the 19 th Brazilian Conference of Data Communication in Florianopolis, being trained on the 3 following mini-courses: Mobile Internet Applications and Technologies, QoS : WAP, SMS, VoIPoW (Voice over IP over Wireless) Intrusion Detection RNP2 (National Network of Researches 2) Language HTML, ASP, Java, C, JavaScript. Data Bases Microsoft Access. Operational Systems Microsoft DOS, Windows (XX/2000/NT/XP), Linux. Various Softwares MS Office 97/2000/XP, OpenOffice, Visio Professional 5.0, Photo Shop Pro 5.0, Corel Draw 10, Partition Magic, Drive Image, Sniffer Pro 3.0, Macromedia Dreamweaver, Enterprise Publishing, NAGIOS, MATLAB, CIRCUIT MAKER, EPICENTER, CISCOWORKS, ECLIPSE, RATIONAL ROSE. Project Plan 23 / 32

Appendix 2 David Blomberg Karlsborgsvägen 4 12150 Johanneshov davidb@kth.se 070-4816072 Education: University The Royal Institute of 2001- Technology, KTH, Industrial Engineering and Business Management University University of Stellenbosch, 2004 Exchange Student, Stellenbosch, South Africa Upper Secondary School Kungsholmens Gymnasium 1998-2001 Work Experience: The Royal Palace, Stockholm Ticket Sales and Tourist Information Summers of 2001, 2002, 2003 Languages: Swedish English French German Mother tongue Fluent Basic knowledge Basic knowledge Computer Skills: Operating Systems Programming Languages Windows, Unix, Linux Java, C, matlab, HTML Project Plan 24 / 32

Extracurricular Activities: Board of Culture Scholarships: The Royal Institute of Technology The Royal Institute of Technology The Royal Institute of Technology, The Section for Industrial Engineering and Management General scholarship, for good academic results Henrik Göranssons Sandviken Scholarship, for good academic results Chairperson, 2002-2003 2004 2004 Project Plan 25 / 32

Appendix 3 Personal Information Name: Afonso Surname: Timba Marital status: Single Nationality : Mozambican Birthdate : 1979/09/08 Birthplace: Maputo Academic History High School 1999-2004 5th Level Subjets Conclusion of Informatics Course at Eduardo Mondlane University Medial and Basic Education 1994-1998 Francisco Manyanga Secundary School Professional Experience and Courses Project Plan 26 / 32

Information Technology 2th Degree of CCNA Network CISCO Course Maths Teacher at Secondary school Internship at: o TvCabo ( Cable Tv Company ) Skills MySQL + Apache + PHP + HTML Programming in Java + SQL ( Oracle) Web Designing in HTML Programming in Visual Basic + Access Cisco Router 2500 Configuration Knowledge of TCP/IP Protocols Basic Knowledge of SMTP, FTP, POP, DNS Servers Ethernet LAN Installation and configuration (including internet connection Sharing) Instalation and Configuration of Apache web server Mail configuration in Microsoft Outlook and Outlook Express PC TroubleShooting Computer HardWare Basics MsOffice, MsWindows (Professional and Server) anti-spam and Anti-Spyware tools software instalation and configuration Linux Basics Good Capacity of Learning and relatioship. Responsability and flexibility Project Plan 27 / 32

LANGUAGES Spoken and Written Portuguese Spoken and Written English Spoken Ronga and Xangana CONTACT Cel Phone : +258 84 282689 - Afonso Timba Home phone: +258 1 428023 Project Plan 28 / 32

Appendix 4 Surname: Nhamoneque First name: Albertina Inácio Passport ID: AB 01236 Date of birth: December 19, 1970 Marital status: Single Father: Inácio L. Nhamoneque Mother: Lúcia w. Muaralo Nationality: Mozambican ADDRESS Street Paiva Couceiro no. 181-1st floor - Maputo Cell phone 082-499983 or 082-310608 Email: albertina@zebra.uem.mz QUALIFICATIONS 2004: Instituto Superior Politécnico e Universitário ISPU (Polytechnic and Universitary Institute) Mozambique,. Frequency of Last year of Informatics Management (Informática de Gestão ); 2003: Instituto Superior Politécnico e Universitário ISPU (Polytechnic and Universitary Institute) Mozambique,. 3 rd degree computer s management (Informática de gestão ) 1994: Francisco Manyanga high school Maputo, 11/12th level 1989: Amizade school in Germany, 5-9th level at. 1982: Chitondo-Norte school. primary education. KNOWLEDGE Computer Skills Project Plan 29 / 32

Microsoft window s (Word, Excel, PowerPoint, Access) Red hat Linux Data warehouse SQL server 2000 PROFESSIONALS TRAINING Network Training at Telecommunications training Institute - Maputo. Telecommunications basic training at Deutche Betriebs School in Germany PROFESSIONAL EXPERIENCE 1995: Stock Manager of Telecomunicações de Moçambique-TDM (Mozambican Telecommunication) Network warehouse - Maputo. 1993: Telecommunication network Project designer of TDM 1989: Telecommunication network Technician of TDM. Maputo LANGUAGES Portuguese: Writen (Very good),spoken (fluent) German: write (good ), speak (fluently) English: write(good), speak (moderate) Chope: write (moderate), Speak (fluently) Albertina Inácio Nhamoneque... Maputo, 24 February 2005 Project Plan 30 / 32

Appendix 5 Mozambique, Maputo City, Resistência street 1407 1st Floor nr 1 Antonio Joao Massingue +25884249119, antonio.massingue@lycos.co.uk Employment Experience 2004 Exi- Engenharia e Comercialização de Sistemas Informáticos Maputo, Mozambique PROGRAMMER Actually working as programmer, developing systems in Java Vyper Solutions Informatics and Computer Solutions Maputo, Mozambique HARDWARE TEACHER Working as hardware teacher. 2004 Eduardo Mondlane University Maputo, Mozambique ASSISTANT Worked as assistant of the Informatics Introduction subject at Chemistry and Electronics courses. Playing the role of practice teacher. This subject was an introduction to programming in Pascal and Fortran OPEN OFFICE TEACHER As the Mozambican government is implementing a new finance system based on Linux Operating System there s a huge necessity to prepare the staff of all the Departments to use the new system. Participated on the conception of the courses tutorials and as a teacher on the former. 2001-2004 TECHNICAL SUPPORT Acted as hardware and software technical support at the Mathematics and Informatics Department Machines Room, on this University repairing the local area network and computer hardware and software related problems. Education 2000 2004 Eduardo Mondlane University Maputo, Mozambique Informatics Course Project Plan 31 / 32

Actually finished the lecture part Josina Machel Secondary School Maputo, Mozambique High School degree Interests Informatics Skills Computer sciences, software engineering, system development, networks.. Good knowledge of Microsoft Office 2000, Xp OppenOffice Operating systems : Windows : 95,98, Me (Millennium), Nt 4.0 Workstation and Server Nt 5.0 ( 2000 : Professional and Server), Xp Professional; Linux Red Hat 8.0, 9.0 and Fedora Core 2 High Skills of programming in : Java C/C++, both on Windows and Linux C# (C-Sharp) of the.net technology Pascal Good skills in System Design and Analysis Design and Implementation of Databases in Oracle and MySQL using PL/SQL on the former. Developing applications with JDBC/ODBC connectivity with both Oracle and MySQL Strong knowledge of computer hardware Mounting and configuration of computers Good knowledge of computer network : Mounting and configuration of LAN Ethernets Language Skills More Speak and write fluently English and Portuguese High sense of responsibility Great experience in self-learning Work well within teams Communicates easily with everyone Extremely dynamic Project Plan 32 / 32