REQUEST FOR CONSULTANT QUALIFICATIONS (RCQ… · REQUEST FOR CONSULTANT QUALIFICATIONS (RCQ) DESIGN AND DEVELOPMENT OF PHASE 2 OF THE MCA ... Among other requirements, ... Deadline

REQUEST FOR CONSULTANT QUALIFICATIONS (RCQ) DESIGN AND DEVELOPMENT OF PHASE 2 OF THE MCA NAMIBIA WEBSITE

MCAN/CIF/6.2.3b The Republic of Namibia has signed a grant funding agreement, the Millennium Challenge Account (MCA) Namibia Compact, of US$304.5 million with the Millennium Challenge Corporation (MCC), an Agency of the United States Government, to enable the Government of Namibia to implement the MCA Namibia Programme and achieve the objectives of the Compact. MCA Namibia, a programme implementation unit of the National Planning Commission, will use a portion of the grant funding for the acquisition of Goods, Works, and Services.

Millennium Challenge Account Namibia (MCA-N) requires the services of an Individual Consultant or a Team of Consultants (hereinafter referred to as “Consultant”) to provide website development services as described in this RCQ and attachments thereto.

Summary of Services

Develop Phase 2 of the MCA-N website, including the following:

1. Conceptualise the website architecture and design based on the MCA-N specifications 2. Design and develop the website code, including all graphical elements 3. Manage the testing, repairing and evaluation of the website prototype 4. Manage the deployment of the final website draft on a Web server chosen by MCA-N 5. Produce a website administration manual and provide training to MCA-N staff on website

administration

Location: Windhoek

Anticipated Start Date: 1 November 2009

Duration of Assignment: 8 months

Before applying, prospective Consultants should review the attached Terms of Reference (Annex 1), which describes the assignment in detail and lists the required qualifications of prospective Consultants. Among other requirements, these qualifications include Master’s degree in Computer Science or Information Technology, fluency in English, 5 years of significant experience in website design and development.

The selection shall be carried out in accordance with the procedures set forth in Section 1.B of the MCA-N Procurement Rules as relating to the Consultant Qualification Selection method (see the Procurement page on website www.mcanamibia.org for the Procurement Rules). The selected Consultant will sign a contract (Annex 5) on the basis of a fixed price/fee.

Application Procedure

Prospective Consultants are requested to send their responses, which should include the following:

1. An expression of interest to be considered for the assignment including the date of availability (Annex 2)

2. A current Curriculum Vitae (Annex 3) 3. Three references, assessing the consultant’s performance on similar assignments. All three

references must be from recent clients, who had commissioned the prospective Consultant

Page 2 of 85

to complete or to play a significant role in the completion of a website similar in terms of complexity to the one described in the Terms of Reference. Each reference must indicate the URL of the respective website.

4. A technical proposal (Annexes 4 and 5)

Prospective Consultants are required to provide their responses to this RCQ, which will include all of the documents listed above, to:

Millennium Challenge Account Namibia Attention: MCA Namibia Procurement Manager Atlas House, 3rd Floor, Room 10 117 Sam Nujoma Drive Windhoek, Namibia Tel. +264 (61) 410442 Fax: +264 (61) 410415 E-mail: [email protected]

For additional information prospective Consultants may refer to the Procurement Page on the MCA-N website or contact the Procurement Agent Manager at the above address.

Deadline for submission of responses: 15 June 2009, 13h00

mailto:[email protected]�

ANNEX 1: TERMS OF REFERENCE

Background Information

CONTEXT

THE MCC

The Millennium Challenge Corporation (MCC) was established in January 2004 as a United States government corporation to implement the Millennium Challenge Account (MCA). MCC’s mission is to reduce poverty by supporting sustainable, transformative economic growth in developing countries, which create and maintain sound policy environments. MCC is designed to support innovative strategies and to ensure accountability for measurable results. The Government of Namibia (GRN) has received a grant of 304,500,000 USD from the MCC and established the MCA-Namibia to implement the Compact (for additional information on MCC please visit www.mcc.gov).

THE MCA-NAMIBIA PROGRAM

The Goal of the Program in Namibia is to reduce poverty through economic growth in the Education, Tourism and Agriculture sectors. To accomplish the Compact Goal of increasing income, the MCA-Namibia Program aims to achieve the following objectives:

• Increase the competence of the Namibian workforce (knowledge, skills and attitude), and • Increase the productivity of agricultural and non-agricultural enterprises in rural areas;

Three Projects will be implemented by MCA-Namibia to achieve these Objectives:

• The Education Project which has six activities that will; i) improve the quality of general education through infrastructure renovations and rehabilitation, supply of equipment and capacity building of school administrators and teachers, and policy-relevant studies; ii) improving vocational skills training; iii) improving the access to, and management of textbooks; iv) investing in regional study and resource centers; v) expanding and improving access to, equity, and sustainability of tertiary education finance and vi) cross-project support to particularly assist Ministry of Education with HIV/AIDS awareness generation for the planned construction activities.

• The Tourism Project which has three activities that will; i) improve management and infrastructure of the Etosha National Park (ENP); ii) marketing Namibia tourism to new destinations, especially the United State of America and; iii) eco-tourism development in Communal Conservancies in Namibia.

• The Agriculture Project which has three activities that will; i) improve land access and management in communal areas; ii) support livestock farming in communal areas (through construction of 5 veterinary centers, implementation of a traceability system and a post-farm gate investment fund) and; iii) support growth and wider beneficiation in the indigenous natural products (INPs) sector.

MCA-NAMIBIA MANAGEMENT STRUCTURE

MCA-Namibia is the accountable entity, responsible for overall management of the Compact’s implementation. MCA-Namibia is a legal entity within the National Planning Commission (Office of the President) comprised of a Board and a Program Management Unit (PMU). The Board is responsible for making key strategic decisions, providing oversight, and is ultimately responsible for Program success. The PMU is responsible for the implementation of the Compact, including program management, financial management and reporting, and coordination of monitoring and evaluation. The Program is legally governed by the Compact and its supplemental agreements (available at www.mca.gov.na).

http://www.mcc.gov/�

http://www.mca.gov.na/�

Page 4 of 85

PURPOSE OF THIS DOCUMENT

MCA Namibia (MCA-N) implemented Phase 1 of the MCA-N Website at www.mcanamibia.org in 2007. MCA-N now wants to implement Phase 2. The purpose of this document is to:

• set forth the minimal required qualifications for the consultants interested in submitting proposals for the design and implementation of Phase 2 of the MCA-N Website,

• describe the assignment implementation process, and • capture requirements for Phase 2 including new functionality not available in Phase 1 as well

as requirements that resolve issues currently experienced with the Phase 1 implementation.

Required Qualifications and Assignment Implementation Description REQUIRED QUALIFICATIONS

The Consultant will be a professional with extensive experience in the design and development of websites. The Consultant’s minimal qualifications are:

• Master’s Degree in Computer Science or Information Technology or an equivalent combination of education and experience;

• Demonstrated experience designing websites of similar complexity and using similar technology to that, which will be used in this project;

• Greater than 5 years proven architecture and development experience in the implementation of complex, integrated web applications across a variety of environments;

• Highly proficient in communicating and coordinating information technology solutions and processes that aggressively support business objectives;

• Current understanding of emerging technologies, industry best practices in the solution domains;

• In-depth knowledge of different versions of Internet browser software, Photoshop, Flash, DeBabelizer, QuickTime, Streaming Media formats, GifBuilder, Premiere, Visual Interdev, VB Script, JavaScript and/or DHTML;

• Working knowledge of NT Server, IIS, SQL Server and other database applications and Macromedia Director.

The main functions of the Consultant shall include the following:

• Conceptualise the website architecture and design based on the specifications further described in this document

• Design and develop the website code, including all graphical elements • Manage the testing, repairing and evaluation of the website prototype • Manage the deployment of the final website draft on a Web server chosen by MCA-N • Produce a website administration manual and provide training to MCA-N staff on website

administration

IMPLEMENTATION REQUIREMENTS

INTRODUCTION

This Section outlines MCA-N’s requirements for the implementation of the MCA-N Website Phase 2 Requirements that are further described in this document. The Section describes MCA-N’s requirements of the implementation timeframe, the expected tasks that the Consultant will undertake, required MCA-N staff involvement, reporting and requirements for defect resolution.

TIMEFRAME REQUIREMENTS

The key timeframe requirements of the Phase 2 MCA-N Website are as follows:

Page 5 of 85

ID Requirement Priority

IT1. Final Release – The final release which satisfies all of the requirements that MCA-N contract the Contracted Consultant to deliver should be delivered a successful internal System Test, ready for Acceptance Testing by MCA-N within 8 months from the start of the implementation project.

Must Have

IMPLEMENTATION TASK REQUIREMENTS

In order to facilitate a successful implementation of Phase 2 MCA-N Website, MCA-N have the following requirements relating to the tasks and activities that the Consultant shall undertake whilst implementing the new Website.


IA1. Provide status updates to MCA-N’s Project Manager – The Consultant shall meet regularly with MCA-N’s Project Manager and provide the following documents on a periodic basis:

• Implementation Plan (updated bi-monthly to show actual progress versus planned or baselined progress)

• Monrhtly Status Reports • Weekly Issue Reports

Must Have

IA2. Conduct Detailed Requirements Meetings – The Consultant shall meet with MCA-N staff to capture detailed requirements for the Phase 2 MCA-N Website. The meetings should take place at MCA-N’s offices in Windhoek.

Must Have

IA3. Sign Off Detailed Requirements Specification – The C

ontracted Consultant should document all of the captured detailed requirements, organized in terms of each page or function of the Phase 2 MCA-N Website. This activity will be only be complete upon sign-off from the MCA-N Project Manager.

Must Have

IA4. Sign Off Conceptual Design/ Prototype – The Contracted Consultant should develop a design for the Phase 2 MCA-N Website and possible develop Prototypes within the first few weeks following Sign off Of Requirements. This activity will only be complete upon sign-off of the Conceptual Design or Prototype from the MCA-N Project Manager. Sign-off may require the Contracted Consultant to conduct a Design Review with MCA-N Staff.

Should Have

IA5. Complete Implementation – Once the Detailed Requirements and Conceptual Design and/ or any Prototypes have been signed off by MCA-N, the Consultant shall implement the Phase 2 MCA-N Website in accordance with these sign off documents.

Must Have

IA6. Complete Internal System Testing – Once the Phase 2 MCA-N Website has been implemented, the Contracted Consultant shall test the website internally before delivering the website to MCA-N for Acceptance Testing. This activity will only be complete and Acceptance Testing shall only commence when the Successful Bidder can confirm that:

• All functionality proposed in the release is available • There are no defects that prevent functionality from being used • There are no defects that corrupt captured data held in databases

The Phase 2 MCA-N Website should only be accessible to the Contracted Consultant staff and possibly some authorized MCA-N staff during Internal System Testing.

Must Have

IA7. Sign Off MCA-N Training – In parallel with Implementation and Internal System Testing and prior to the start of Acceptance Testing, the Contracted Consultant shall develop a Website Administration Manual and train up to 5 MCA-N on the Content Management and other Administrator related functionality of the Phase 2 MCA-N Website. After execution of this training, MCA-N staff should be able to maintain the website content and execute other administrative functions such as generating reports, without the engagement of the Contracted Consultant or another vendor. This activity will be only be complete upon sign-off from the authorized MCA-N manager.

Must Have

Page 6 of 85


IA8. Sign Off Acceptance Testing – Once the Phase 2 MCA-N Website has met the Internal System Test completion criteria and MCA-N Training has been signed off, the Contracted Consultant shall deliver the website to MCA-N for Acceptance Testing. The Contracted Consultant shall support MCA-N and other stakeholders as it tests the Phase 2 MCA-N Website. This may involve working alongside MCA-N at MCA-N’s offices in Windhoek.

The Contracted Consultant shall resolve all defects identified by MCA-N during the Acceptance Testing activity.

Acceptance Testing shall only be complete once signed off by MCA-N. The criteria for completion of Acceptance testing shall be outlined MCA-N’s project Charter.

The Phase 2 MCA-N Website should only be accessible to the Contracted Consultant staff and authorized MCA-N staff during Acceptance Testing.

Must Have

IA9. Cut-Over – Following sign off of Acceptance Testing, the Contracted Consultant shall cut-over the Phase 2 MCA-N Website into production and perform all of the necessary activities to ensure that the Phase 2 MCA-N Website replaces the existing Website and is accessible to all internet users worldwide.

Must Have

IA10. Maintenance Services – Following Cut-over, the Contracted Consultant shall conclude with MCA-N a maintenance agreement to resolve any defects in a timely manner.

Must Have

Website Goals, Major Functions and Target Audience GOALS

The primary goals of the MCA-N Website are:

• to provide key domestic and international stakeholders in the MCA-N Compact with relevant information related to the granting, progress and impact of the MCA-N Compact over time whilst ensuring compliance with the transparency requirements stipulated under the terms of the Compact;

• to facilitate automated procurement, recruitment and registration processes related to the implementation of the MCA-N Compact.

MAJOR FUNCTIONS

The major functions of the MCA-N Website are as follows:

• Inform stakeholders of the progress and impact of projects and activities funded and implemented through the MCA Namibia Compact

• Inform stakeholders of news and up-coming events related to the implementation of the MCA-N Compact.

• Inform stakeholders of Namibia’s adherence to mandatory reporting requirements necessary for Namibia to continue to receive funding from the MCC.

• Provide relevant background information – such as corporate information about MCA-N as well as information relating to the process of granting and implementing the MCA Compact.

• Facilitate an automated procurement process for potential vendors to bid for opportunities to provide goods, services or other deliverables for MCA Namibia

• Facilitate an automated recruitment process for potential employees to apply for vacancies with MCA-N

• Facilitate an automated event registration process enabling users of the website to register for events posted by MCA-Namibia

Page 7 of 85

Note that in addition to these primary functions, there are common or infrastructure functions such as site registration, site search, etc which are described in greater detail later in this document.

TARGET AUDIENCE

The following types of user are expected to make use of MCA-N Website: • MCC – The agency funding the MCA-N Compact • The Government of the Republic of Namibia • Beneficiaries – Stakeholders in Agriculture, Tourism and Education sectors that will benefit

from the implementation of activities under the MCA-N Compact • Domestic & International Vendors – entities that provide goods and services that are

required by MCA-N in the implementation of the MCA-N Compact • Potential MCA-N employees – individuals that have relevant skills and experience that are

required by MCA-N in the implementation of the MCA-N Compact • Media • General Public

The table below maps each of the target audience to each of the major functions of the MCA-N Website.

Major Function MCC GRN Beneficiaries

Vendors Potential Employees

Media General Public

1. Progress & Impact of Projects & Activities

Primary Primary Primary Secondary Primary Primary

2. News & Upcoming Events

Primary Primary Primary Secondary Secondary Primary Primary

3. Mandatory Reporting Requirements

Primary Primary Secondary Secondary

4. Background Information

Primary Primary Secondary

5. Automated Procurement Process

Primary

6. Automated Recruitment Process

Primary

7. Automated Event Registration Process

Secondary Secondary Primary Secondary Primary Secondary

Key:

• Primary – the function is a main reason that the stakeholder will visit the MCA-N Website • Secondary – the function may be utilized by the stakeholder.

Issues with MCA-N Website Phase 1 As well as delivering the Phase 2 requirements outlined in the Website Requirements section of this document, the MCA-N Website Phase 2 should address and resolve key issues present in the Phase 1 MCA-N Website. These issues are listed below.

DESIGN ISSUES

• There are too many links from all pages on the site. Many of the links go to similar static information relating to the background information of the MCC-MCA-N relationship.

• The links to the most pertinent and dynamic information (such as status of implementation projects and activities as well as procurement and employment opportunities) are not clear.

Page 8 of 85

• The header, left panel and right panel are common to all pages on the site taking up a large amount of screen real-estate and adding unnecessary clutter which may not be relevant to the main information being viewed by the user.

COMMON/ INFRASTRUCTURE FUNCTIONAL ISSUES

• Content Management Functionality is limited: Only one picture can be uploaded for each paragraph. This does not allow MCA-N to

layout photographs in a pleasant manner. MCA-N can only enter basic content formatting provided by the CMS editor. MCA-N

would like more advanced formatting options even if this is only achieved by having the ability to enter HTML in the content.

Paragraphs can only be deleted or edited – there is no facility to archive or hide content without deleting it.

• There is no Search functionality to locate documents or information quickly. Coupled with the large number of links and the fact that the most important links to dynamic information are not clear, it is very hard to locate key information.

• The old MCC Logo is used.

HOME PAGE ISSUES

• The main content on the home page is a duplication of other entries in the site – for example Procurement Opportunities. MCA-N duplicates these articles because the important postings themselves are difficult to access and not clearly visible to website users. The home page should include a summary aggregation of feeds from the newest and most relevant entries across the website.

ISSUES WITH MAJOR FUNCTIONS

PROGRESS & IMPACT OF MAJOR PROJECTS & ACTIVITIES

• There no dedicated function to communicate the most important information to many stakeholders – how each of the projects and activities are progressing and what their impact is. The only way that MCA-N can achieve this with the Phase 1 website is to make entries in News & Events or write a series of paragraphs on the Home Page.

NEWS & EVENTS

• All news & events articles are shown in the right panel. The only way to remove outdated news & events articles is to delete them. News & events articles should be displayed for a configured duration, after that they should be available, but only after a “see more” type link is clicked by the user.

• News Articles and Event Posting should be treated differently: News Articles/ Press Releases should report achievements and other notes of

significance. News Articles/ Press Releases should remain relevant for a period of time to be determined by MCA-N. After this time, News Articles should be only available after a “see more” type link is clicked by the user.

Event Postings should promote and communicate upcoming events with links to automated registration of event guests. Events should remain relevant until the Event has taken place. After this time, the Event should only be available after a “see past events” type link is clicked by the user.

MANDATORY REPORTING

• Important Dynamic mandatory reporting requirements such as the Eligibility Scorecard, Minutes of MCA-N Board Meetings and Monitoring & Evaluation Plans & Reports are not

Page 9 of 85

clearly available. This information is mixed in with much, less critical background information.

BACKGROUND INFORMATION

• Too much of the Phase 1 site and too many pages are dedicated to background information such as outlining Namibia’s eligibility for MCC funding, the milestones to MCC funding, governance procedures, consultations that have taken place, due diligence that took place, etc. Most of this information should be aggregated together under a single link and organized succinctly to show the history.

AUTOMATED PROCUREMENT PROCESS

• There is no automated procurement process. For example, MCA-N requires that vendors first register with MCA-N prior to downloading RFPs or other tender documents. Since the site does not support registration or conditional access to documents for download, they are resorting to email communication to provide tender documents.

AUTOMATED RECRUITMENT PROCESS

• There is no automated recruitment process. The site only supports the posting of Job Descriptions and all follow up after this requires manual process.

AUTOMATED EVENT REGISTRATION PROCESS

• There is no automated event registration process.

TECHNICAL ISSUES

• The Phase 1 Content Management System is not browser independent. It requires Internet Explorer to work. Although this is not a major issue for the current phase, it may become an issue for future phases where content is to be uploaded by a larger number of users, all of which may not have access to Internet Explorer.

• The Phase 1 Content Management System only allows PDF files and Image files to be uploaded. Although this is not a major issue for the current phase, it may become an issue when MCA-N require to upload other formats such as MS-Project, Audio files, etc.

• Sometimes there appears to be a limitation of the number of characters permissible for uploaded document names

• Users sometimes encounter timeouts when downloading large files.

Website Phase 2 Requirements EXPLANATION OF REQUIREMENTS DEFINITION

Website requirements are organized in this section as follows:

A. Design requirements B. Common/ Infrastructure functional requirements C. Home Page functional requirements D. Major Function 1: Progress & Impact of Projects & Activities E. Major Function 2: News & Upcoming Events F. Major Function 3: Mandatory reporting G. Major Function 4: Background Information H. Major Function 5: Automated Procurement Process I. Major Function 6: Automated Recruitment Process J. Major Function 7: Automated Event Registration Process K. Technical Requirements

Page 10 of 85

For each grouping of requirements, specific requirements are detailed in tables. The tables have the following columns:

• ID – Unique identifier for the requirement • Requirement – A description of the requirement • Priority – MCA’s priority for the requirement. The following priorities are used:

Must Have – The requirement must be satisfied in the delivery of the MCA-N Website Phase 2. Solutions that do not satisfy this requirement may be disqualified.

Should Have – Competitive solutions will satisfy this requirement. Solutions that do not satisfy this requirement will be less attractive to MCA-N.

Nice to Have – Solutions should only accommodate this requirement if it is possible to implement with little incremental cost and time.

OVERVIEW OF SITE MAP AND CONTENT FEED APPROACH

The requirements outlined in this document highlight numerous types of content updates that may be provided by users with particular access rights (e.g. “MCA Project Manager” user, “MCA Procurement” user, etc). In nearly all cases highlighted in this document, such content is displayed in two formats:

1. Content List – where summary information for a number of content entries are listed, with information for each content entry appears on one line (e.g. Activity Feed in Major Function 1: Progress & Impact of Projects & Activities; Event Summary List in Major Function 2: News & Upcoming Events; or Employment Opportunity Summary List in Major Function 6: Automated Recruitment Process).

a. Users should be able to view the Content Detail (see point 2 below) for a given content by clicking on the content summary line.

b. Only a certain number of entries should be listed in the Content List. The filtering criteria are described in each of the relevant sections of this document. However, where there are more entries than displayed in the list, then there should be a “see more” type link where the user is navigated to the entire list, paginated across multiple pages.

2. Content Detail – where detailed information is displayed for a given Content Entry (e.g. Activity Posting Detail in Major Function 1: Progress & Impact of Projects & Activities; Event Details Posting in Major Function 2: News & Upcoming Events; or Employment Opportunity Detail in Major Function 6: Automated Recruitment Process).

In many cases, content provided by a user will be shown in a Content List on a page of the website relevant to that user (for example the Activity Feed is displayed in the “Visit the Projects” sub-page and the Event Summary List is displayed in the “Latest News and Events” sub-page). However, when creating the content, authorised users should be able to flag the content so that it also appears in two other feeds while it is relevant to that feed:

• Home Page Flag – When content is flagged with the Home Page Flag, then it’s summary information is also listed in an aggregation of topical information on the Home Page while it is still relevant. Users may click on the summary information on the home page and be navigated to the relevant Content Detail.

• Mandatory reporting Flag & Category – When content is flagged with the Mandatory reporting Flag, then it also needs to be categorised into the type of Mandatory Regulatory Information. When this is done, its summary information is also listed in the relevant section of the Mandatory reporting postings feed (see Major Function 3: Mandatory reporting).

Page 11 of 85

Note that where content is shown on multiple pages because of being flagged, the content should only exist once in the MCA-N Website database.

The diagram below outlines the various functions of the website as well as the content that should be displayed in the various feeds across the Website.

A. DESIGN REQUIREMENTS

The design requirements relate to the more fundamental aspects of the MCA-N Website which may need to be incorporated into the underlying architecture of the site, rather than be extendable functionality.

The key design requirements are as follows:


A1. Consistent, Unified or Common Theme – A basic site design template with modestly sized banner graphics or logos, signature icons and action buttons or links should be provided. This should be adaptable for each subsequent page of the website. There should be an underlying graphic theme that makes use of MCA-N & MCC logos, fonts and colours. It should be apparent that this is MCA-N website on every page, but this needs to be balanced with the need for each page to have flexibility in meeting its specific requirements.

Must Have

A2. User Friendly – The MCA-N website should incorporate the following User Friendly traits:

• Use logical and intuitive links • Not overwhelm the user with visual clutter

Must Have

• General Procurement Notices

• Procurements • Specific Procurement

Notices • Bidding Documents • Notice of Awards

Home Page About Us

Funding Timeline Aggregation Feed

Visit the Projects

Aggregation Feed Activity Aggregation Feed

Latest News & Events

Event Summary

List

Ongoing Mandatory reporting

Regulatory Compliance Postings

Feed

Procurement Opportunities

SPN Summary

List

Employment Opportunities

Aggregation Feed Employment Opportunities List

About Us Marketing Activity

Marketing Activity Postings

About Us Textbook Activity

Textbook Activity Postings

Press Release

List

This diagram only highlights content feeds and certain information on key pages. The requirements in this document outline all requirements for each page as well as additional pages not shown in this diagram.

• Activity Posting • Environmental &

Social Impact Assessments

• Activity/ Project Updates

• Key Activity Milestones Reached

• Photo Essays

• Field Events • Workshops

• Press Releases • Announcement

s (changes in Org structure

• Key Implementation Milestones Reached

• Compliance Score Cards • Minutes of NCA-N Board

Meetings • Minutes of Stakeholders/

Consultative Committee meetings

• Monitoring & Evaluation Plans

• Audit Reports and reports/ evaluations by external reviewers

• Disbursement requests, • Any other reports

submitted to the MCC • Legislation and other

documents related to the formation, organization and governance of the MCA-N

• Compact & Amendments • Program Implementation

Agreement & Amendments

Notice of

Awards

• Employment Opportunities

Content that may be flagged for Home Page Aggregation Feed

Content that may be flagged for Regulatory Compliance Posting Feed

Flow of Content to Content Feeds across Site

Approved Testimonials

Page 12 of 85


• Not exceed 1,024 pixels in width • Put most pertinent information at the top of a page; try to avoid the need to scroll down

for more information too often and stringently avoid pages which are more than 2 standard monitor heights in length.

• Be “printer-friendly” on all pages • Be usable – offering a quick and user friendly way to locate the information the user is

looking seeking without the user having to understand MCA-N Organisation. • Minimise number of mouse clicks required to find information.

A3. Separation of Presentation from Content – The MCA-N Website development should separate presentation from content as much as is possible through the use of technologies such as CSS. This should enable changes in presentation and format to be made simply and quickly without impacting the content.

Must Have

A4. Accessibility – Be accessible to individuals with disabilities, meeting ADA Priority 1 Checkpoints. Please refer to Appendix 1 for Web Content Accessibility Guidelines (note that this Appendix lists Priority 1, 2 and 3 Checkpoints and this requirement only refers to the meeting of Priority 1 Checkpoints).

Should Have

A5. Navigational Tools – Offer graphic navigation buttons or bars offering shortcuts. Implementation techniques should not prevent the “Back” button within browsers from working as expected.

Must Have

A6. Content Management – Much of the site’s content should be maintainable and extendable by authorized MCA-N staff using Content Management functionality. Note the Content Management requirements included for major functions later in this document.

Must Have

A7. Track page hits per function – Administrator users should be able to determine the number of unique IP page hits each page of the site is receiving over periods of time (by day, week, month, etc). Where possible this information should include the country in which the IP address is registered.

Must Have

A8. Use of Hyperlinks – The site should make effective use of hyperlinks to link to relevant external sites.

Must Have

A9. Cookies – Cookies should be leveraged (but not depended on) to default key user information that may have been captured on previous visits by a particular user with the objective to short-cut user selections and tailor the site to the expected user needs (for example, it may be possible to default the user name/ email address of a user that has registered on the site and has requested to log in, or enable the “remember me” option on the login screen).

Must Have

A10. Multimedia Library – Multimedia used throughout the MCA-N Website should be effectively managed using either an internal or external database which should facilitate easy management of multimedia files by MCA-N and appropriate tagging of multimedia files to facilitate searches across multimedia files.

Must Have

A11. Security – Passwords should be handled in a secure manner including the encrypted transmission of passwords over the internet and data storage.

Must Have

B. COMMON/ INFRASTRUCTURE FUNCTIONAL REQUIREMENTS

The common/ infrastructure functional requirements outline those functional requirements that are either common to all of the major functional requirements or reside in the underlying framework of the website. Requirements are organized into two tables – the first table outlines those common requirements to satisfy the target audience of the website, whilst the second table outlines those common Content Management requirements for MCA-N to maintain the content of this major function.

The common/ infrastructure target user requirements for this major function are as follows:

Page 13 of 85


B1. Menus– Provide consistent menu for accessibility to functionality on the site. The menu may require to be dynamic depending on certain criteria (for example, a registered user may have menu options such as account maintenance which are not available to anonymous users). The current MCA-N Phase 1 site has the top, left column and right column dedicated to menu’s on all pages. The left and right menus should not be required so these areas can be used for page content.

Must Have

B2. Search – Provide site search functionality that enables users to find the information that they require quickly. All content on the site (including but not limited to information created through Content Management functionality by MCA-N staff, tagged multimedia files and the contents of attached documents) should be searchable.

Must Have

B3. Registration – Provide users with the ability to register with the MCA-N Website. Certain functionality may only be available for registered users (e.g. downloading of procurement RFPs, applying for an employment opportunity or registering for an event). Upon registration, users should provide information including but to limited to the following:

• Email address – used as the unique identifier for the user’s registration (Mandatory) • Password – used by the user to log in (Mandatory) • Name of Company (Optional, but Mandatory to download Procurement Bidding

documents) • First Name, Last Name (Optional, but Mandatory to download Procurement Bidding

documents) • Telephone Number (Optional) • Fax Number (Optional, but Mandatory to download Procurement Bidding documents) • Country of Residence (Optional) • Preferences (Optional) :

Does the user want to receive emails from MCA-N Does the user want to receive notifications when content is added or changed to

the MCA-N website Areas of Interest:

Projects News and Events Mandatory Reporting Procurement Opportunities Employment Opportunities

Must Have

B4. Registration Access Rights – MCA-N should be able to set access rights for registered users. The specific categories of user access rights may include the following:

• Normal “read-only” user • MCA-N Project Manager user – allows user to post, edit, archive and delete Project

Updates on the Project Home page for their project only. • MCA-N Public Relations user – allows user to post, edit, archive and delete Press Releases,

Announcements, Event Summaries, Mandatory reporting Postings & Approved Testimonials

• MCA-N Procurement user – allows user to post, edit, archive and delete Procurement Notices

• MCA-N Human Resources user – allows user to post, edit, archive and delete Employment Notices

• MCA-N Administrator user – allows the use to: Create, edit, archive, delete User Accounts, Reset user passwords Allocate access rights Create, edit, archive, delete Projects/ Activities Backup & Restore Database View site visit statistics such as page hits per function

Must Have

Page 14 of 85


etc

B5. Login – Allow registered users to log in by providing their authentication details that they provided during the registration process. There should be functionality that allows users to automatically recover or reset lost passwords in a secure manner.

Must Have

B6. Feedback submission – Provide a function by which users can submit feedback to MCA-N from all pages of the MCA-N Website. The user should be able to capture the feedback category (categories to be provided by MCA-N). The feedback function should also capture the page that the user was viewing when they clicked feedback. Feedback should be automatically routed to the relevant MCA-N employee’s email based on the feedback category or the page that the user was viewing. Feedback emails should also copied to an additional MCA-N email address so that MCA-N responses can be monitored. All MCA-N emails should be maintainable by MCA-N.

Must Have

B7. Contact details – Provide contact details for the MCA-N. Contact details should include:

• Address (physical and postal) • Telephone number • Contact Email Address

Unlike the MCA-N Phase 1 Website, the contact details do not have to be displayed in full detail on every page. The details should be accessible from a menu link.

Must Have

B8. RSS Feed – Registered MCA-N Website users should be able to subscribe to the MCA-N Website RSS Feed. The MCA-N Website should generate RSS Feeds for all of the major information posting son the site, including:

• Project Postings (see Major Function 1) • Press Releases & Announcements (see Major Function 2) • Event Summaries (see Major Function 2) • Mandatory reporting Postings (see Major Function 3) • Procurement Notices (see Major Function 5) • Employment Notices (see Major Function 6) • Approved Testimonials (see Common/ Infrastructure Requirements)

Nice to Have

B9. Content Sharing – The MCA-N Website should allow users to share any content on the site which is available to anonymous (i.e. unregistered users) either through email or through integration with popular Social Networking Sites (such as Digg, Facebook, delicious, Reddit, etc).

Nice to Have

B10. Logos, References & Brand Assets – The MCA-N Website should use the latest logos references and brand assets for MCA-N and MCC.

Must Have

The common/ infrastructure Content Management requirements are as follows:


B11. Maintain Feedback/ Testimonials – Provide users with MCA-N Public Relations Access Rights with the ability to create, edit and delete testimonials or approved user feedback comments onto relevant pages.

Should Have

B12. Formatting of Content – Provide MCA-N with the ability to apply all aspects of formatting available in HTML to any content that it adds to the site. This should include the ability to configure hyperlinks to other pages inside or outside the MCA-N Website.

By default the content should follow one defined style of formatting that should accommodate all content types (paragraphs, bulleted lists, etc) by standardising key formatting elements (such as font size, font type, font colour, font style, margins before and after paragraphs, etc.). However, it should be possible to deviate from the defined style.

Must Have

B13. Formatting of Picture Galleries – Provide MCA-N with the ability to layout pictures and multimedia files utilizing all aspects of formatting and layout available in HTML. For example, it should be

Must Have

Page 15 of 85


possible to layout multiple pictures in single paragraphs; left aligned; right-aligned; within tables, etc. End users should be able to click on pictures and view them at full size as well as select ‘next’, ‘previous’ and other options typically available within picture galleries.

B14. Support for Photo Essays – Provide MCA-N with the ability to create Photo Essays. Photo Essays should pop up in a separate window to the main window and lead the user through a series of photo’s and captions that can be used to tell a story.

The Photo Essay pop up window should be clearly branded as an MCA-N asset and contain links to associated postings and pages on the MCA-N Website.

It should be possible to email links to Photo Essays to facilitate viral marketing of key MCA-N stories.

An example photo essay can be found here: http://www.unicef.org/photoessays/49510.html

Should Have

B15. Home Page Flag – All content postings (Events, News, Procurement Opportunities, Project/ Activity Postings, etc) should have a flag which indicates whether the posting should appear on the home page when it is relevant.

Must Have

B16. Mandatory reporting Flag & Category – All content postings (Events, News, Procurement Opportunities, Project/ Activity Postings, etc) should have a flag which indicates whether the posting should appear on the Mandatory reporting postings feed in the Mandatory reporting page when it is relevant.

Additionally, where the a content posting is flagged with this, it should also be categorised into one of the following categories of mandatory reporting information:

• MCA Namibia Board Minutes • M&E and Environmental Impact Assessment documents • Audits and Reviews • Disbursement Requests • MCC Reporting • Other Required Postings

Must Have

B17. Content Expiry Date – All content postings should have a user entered expiry date, after which time the content is not to be displayed on the website.

Should Have

B18. Maximum Upload Size – With the ability for numerous MCA-N users to upload content to the site and the potential for some website user’s to have limited bandwidth, it should be possible for MCA-N to configure maximum file upload sizes.

Must Have

B19. Review of Content – Provide automated workflow to manage the review of content prior to posting on the Website.

It should be possible to configure the Content Management System to appoint users as reviewers for each type of content that can be posted. When new content is generated by an authorized user, the system should send an email containing a link to the content to the reviewing user. The reviewing user should then be able to edit, accept are reject the content. Only accepted content would be finalized for posting on the live site.

Should Have

B20. Hide Content – Provide the ability to hide content so that it is not displayed on the website, without deleting the content.

Must Have

B21. Automated Outbound Notification when no Updates – If a configured period of time passes without any content updates or postings to any of the major functions (including individual activities), then an email should be sent to all users who have the authorization access rights to that function with a copy to the reviewer (see B17 above) notifying them that Content has not been updated for this time.

Nice to Have

http://www.unicef.org/photoessays/49510.html�

Page 16 of 85

C. HOME PAGE FUNCTIONAL REQUIREMENTS

The Home Page functional requirements outline the requirements of the default or index page that will reside at the root directory of the website domain.

The Home Page requirements are as follows:


C1. Access to Major Functions – The home page should have clear links to the following major functions:

Primary Links

Primary links should be clearly visible in a prime position on the home page. Possibly, they should make use of large, relevant images.

• Progress & Impact of Projects & Activities – there should be one link which should be branded “Visit the Projects”. Following this link will navigate to Major Function 1: Progress & Impact of Projects & Activities.

• News & Upcoming Events – there should be one link which should be branded “Latest News & Events”. Following this link will navigate to Major Function 2: News & Upcoming Events.

• Mandatory reporting – there should be one link which should be branded “Ongoing Mandatory reporting”. Following this link will navigate to Major Function 3: Mandatory reporting.

All Primary Links should be accessible from the menu, anywhere in the Website.

Secondary Links

Secondary links should be visible, in a secondary location on the home page and non–graphical, smaller links may be sufficient.

• Procurement Opportunities – there should be one link branded “Procurement Opportunities”. Following this link will navigate to Major Function 5: Automated Procurement Process.

• Employment Opportunities – there should be one link branded “Employment Opportunities”. Following this link will navigate to Major Function 6: Automated Employment Process.

• Background Information – there should be the following secondary links to background information functions:

A link which should be branded “About Us”. Following this link will navigate to Major Function 4.1: Background Information – Corporate Information.

A link which should be branded “Funding Timeline”. Following this link will navigate to Major Function 4.2: Background Information –Funding Timeline.

Note that the Automated Event Registration major function would be available from the detail of a particular event.

Must Have

C2. Aggregation of topical information – The home page should aggregate the most topical & relevant information postings to the site. These may include:

• Activity Postings (see Major Function 1) • Press Releases & Announcements (see Major Function 2) • Event Summaries (see Major Function 2) • Mandatory reporting Postings (see Major Function 3) • Procurement Notices (see Major Function 5) • Employment Notices (see Major Function 6) • Approved Testimonials (see Common/ Infrastructure Requirements)

Only those articles that were flagged to be displayed on the Home page should be included.

Must Have

Page 17 of 85


Summary information should be displayed for each item, taken from the content created by MCA-N without the need for duplication. Users should be able to click on any article and then be navigated to the full posting.

Articles should not appear after they are no longer relevant.

There should be a “See more” option for users to see the entire listing of articles including those that are no longer relevant.

C3. Registration – The home page should present a link to encourage regular users of the site to register. Following this link will navigate to Website Registration functionality (see Common/ Infrastructure Functional Requirements).

Must Have

D. MAJOR FUNCTION 1: PROGRESS & IMPACT OF PROJECTS & ACTIVITIES

A major function of the MCA-N Website is to inform various stakeholders of the progress and impact of projects and activities funded and implemented through the MCA Namibia Compact. This section outlines the requirements for this major function. Requirements are organized into two tables – the first table outlines those requirements to satisfy the target audience of the website, whilst the second table outlines those Content Management requirements for MCA-N to maintain the content of this major function.

The target user requirements for this major function are as follows:


D1. Branding – This Major function should be branded “Visit the Projects” Must Have

D2. Project/ Activity List – the Project/ Activity Home Page should display a graphical list of Projects/Activities, organized into each of the sectors. Users should be able to navigate to the Project Detail page by clicking on any one of the project links.

MCA-N Administrator users should be able to use the content management functionality to add, modify and remove projects as required (see below). However the initial list of projects & activities by sector are likely to be:

Education Project:

• Education Quality Activity • Vocational Skills and Training Activity • Textbook Activity • Regional Study Resources Centres Activity • Tertiary Education Finance Activity

Agriculture Project:

• Land Access and Management Activity • Livestock Support Activity • Indigenous Natural Products Activity

Tourism Project:

• Improved Management and Infrastructure in the Etosha National Park Activity • Marketing Activity • Community-Based Tourism Development Activity

Must Have

D3. Activity Aggregation Feed – the Project/ Activity Home Page should display a feed of postings from all Activities in a logical order.

Summary information should be displayed for each item, taken from the content created by MCA-N without the need for duplication. Users should be able to click on any Activity posting and then

Must Have

Page 18 of 85


be navigated to the full posting.

Activity Postings should not appear after they are no longer relevant.

There should be a “See more” option for users to see the entire listing of Activity Postings including those that are no longer relevant.

D4. Activity Detail (Basic) – when a user has clicked on a link for a particular Activity, they should be navigated to the home page for that Activity. The Activity home page for a particular Activity should display key information about the project such as:

• Contact Details for Activity Manager • Start Date • Funding Amount • Targeted Impact • Gant Chart showing major milestones • Project Images

MCA-N Administrator users should be able to edit all of the above information using the content management functionality. Additionally, the Activity Detail page should show a summary list of all the relevant Activity Postings for that project. Activity Postings would have been created

Must Have

D5. Activity Detail (Advanced) – in addition to the basic information shown above, advance requirements include

• Graphically represent progress along Gantt Chart • Display thumbnails/ icons to Activity Postings at relevant places on the Gantt chart. Users

should be able to click on the thumbnail/ icon to navigate to the associated posting.

Nice to Have

D6. Activity Postings – when a user has clicked on a link to view an Activity posting, that posting should be displayed in accordance to the type of posting (see below). The following information may be displayed for an Activity Posting:

• Date/ Time of Posting • Author of Posting (taken from login details of MCA-N user making posting) • Description/ Title of posting • Ability to upload text content • Ability to upload one or multiple pictures in an attractive layout • Ability to upload Photo Essays (see Common/ Infrastructure Content Management

Requirements) • Ability to upload other attachments such as:

PDF files MS Office files

Must Have

The Content Management requirements for this major function are as follows:


D7. Maintain Activities– Provide users with MCA-N Administrative Access Rights with ability to create, edit and delete Activities under each of the Projects. This should include assigning of the Project Manager from a list of registered users to the MCA-N website to enable the Project Manager to then upload Project Postings to their Activity.

All of the Activity information shown on the Activity Detail page should be editable by this authorized MCA-N user.

Must Have

D8. Maintain Activity Postings (Basic) – Provide users with MCA-N Project Manager Access Rights for a particular project with ability to create, edit and delete Activity postings for their Activity.

All of the information shown on the Activity Posting page should be editable by this authorized

Must Have

Page 19 of 85


MCA-N user. D9. Maintain Activity Postings (Advanced) – Provide users with MCA-N Project Manager Access Rights

for a particular project with ability to graphically indicate progress along the Gantt chart for the Activity and place icons/ thumbnails for Activity postings at relevant places on the Gantt chart.

Nice to Have

E. MAJOR FUNCTION 2: NEWS & UPCOMING EVENTS


E1. Branding – This Major function should be branded “Latest News & Events” Must Have

E2. Press Releases & Announcements List – the News & Upcoming events page should display a summary list of relevant Press Releases and Announcements. A Press Release is a special type of Announcement that has been used to communicate key information to the Press.

Announcements may include:

• Information following a Workshop – such as copies of presentations, speeches, etc • Changes in MCA-A Organization structure • Key Milestones being achieved

Summary information should be displayed for each item. Users should be able to click on any Press Release or Announcement and then be navigated to the full posting.

Press Releases & Announcements should not appear after they are no longer relevant. They will be no longer relevant after a configured period of time after they were first posted. There should be a “See more” option for users to see the entire listing of Press Releases & Announcements including those that are no longer relevant.

Must Have

E3. Event Summary List - the News & Upcoming events page should display a summary list of up-coming Events.

Events may include:

• Field Events (such as visits to projects/ activities) • Workshops

Summary information should be displayed for each item. Users should be able to click on any Event and then be navigated to the full Event details.

Event Summaries should not appear after they are no longer relevant. They will be no longer relevant after the event has passed. There should be a “See past events” option for users to see the entire listing of Events including those that took place in the past.

Must Have

E4. Press Release & Announcement Postings – when a user has clicked on a link to view a Press Release or Announcement, the details of that Press Release & Announcement should be displayed.

The following information may be displayed for a Press Release & Announcement:

• Date/ Time of Press Release/ Announcement • Description/ Title of Press Release/ Announcement • Ability to upload text content • Ability to upload one or multiple pictures in an attractive layout • Ability to upload multimedia content such as:

Photo Essays (where still images are displayed with written narration) • Ability to upload other attachments such as:


Must Have

E5. Event Details Postings – when a user has clicked on a link to view an Event, the details of that Must Have

Page 20 of 85


Event should be displayed (see below).

The following information may be displayed for an Event:

• Date/ Time of Event • Name of Event • Location of Event • Directions to Event • Ability to upload text content describing the Event • Ability to upload one or multiple pictures in an attractive layout • Ability to upload multimedia content such as:

Photo Essays (where still images are displayed with written narration) • Ability to upload other attachments such as:


In addition, the Event Detail should provide a link to any associated Event Registration function (see Major Function 7 : Automated Event Registration Process)



E6. Maintain Press Releases & Announcements - Provide users with MCA-N Public Relations Access Rights with the ability to create, edit and delete Press Releases & Announcements.

All of the Press Release & Announcement information shown on the Press Release & Announcement page should be editable by this authorized MCA-N user.

Must Have

E7. Maintain Events - Provide users with MCA-N Public Relations Access Rights with the ability to create, edit and delete Event Details.

All of the Event Detail information shown on the Event Details page should be editable by this authorized MCA-N user.

In addition, authorized MCA-N users should be able to flag whether a given event should have an automated event registration process. Not all events may have this feature.

Must Have

F. MAJOR FUNCTION 3: MANDATORY REPORTING


F1. Branding – This Major function should be branded “Ongoing Mandatory reporting” Must Have

F2. Compliance Score Card – The Mandatory reporting Home Page should provide the latest Compliance Score Card.

A Compliance Score Card is created each year and lists Namibia’s compliance to 17 KPIs across three broad areas:

• Ruling Justly • Investing in People • Economic Freedom

As this is a critical element of mandatory reporting, these KPIs should be displayed within the Compliance Score Card page and not simply be attached as a .pdf document. The layout should incorporate the three broad areas and make an attractive use of graphics.

At the bottom of the page should be a link that enables users to view Compliance Score Cards from previous years.

Namibia’s 2008 Compliance Score Card can be found here:

Must Have

Page 21 of 85


http://www.mcc.gov/mcc/bm.doc/score-fy08-namibia.pdf

F3. Mandatory reporting Postings Feed – The Mandatory reporting Home Page should provide an aggregation of all content postings across the Website that have been flagged with the Mandatory reporting Flag. These may include:

• Amendments to the Compact (posted using functionality described in Major Function 4.2: Background Information – Funding Timeline)

• Programme Implementation Agreement & any amendments (posted by users with Public Relations Access Rights using functionality described in Major Function 4.2: Background Information – Funding Timeline)

• Minutes of NCA-N Board Meetings (posted here) • Minutes of Stakeholders/ Consultative Committee meetings (posted here) • Monitoring & Evaluation Plans (posted here) • Environmental and Social Impact Assessments (posted by users with Project Management

Access Rights using functionality described in Major Function 1: Progress & Impact of Projects and Activities).

• Audit Reports and reports/ evaluations by external reviewers (posted here) • Disbursement requests, requesting funding from the MCC and outlining the results of the

expenditure from the last request (posted here) • Any other reports submitted to the MCC (posted here) • Legislation and other documents related to the formation, organization and governance of

the MCA-N (posted here)

Only those postings that were flagged to be displayed in the Mandatory reporting Posting feed should be included. Summary information should be displayed for each item, taken from the content created by MCA-N without the need for duplication. Users should be able to click on any summary and then be navigated to the full posting.

Articles should not appear after they are no longer relevant.

There should be a “See more” option for users to see the entire listing of articles including those that are no longer relevant.

Must Have

F4. Content Detail - when a user has clicked on the summary information for any mandatory reporting item shown in the Mandatory reporting Postings Feed, the details of that posting should be displayed depending on the type of posting.

Must Have



F5. Maintain Compliance Score Cards - Provide users with MCA-N Public Relations Access Rights with the ability to create, edit and delete Compliance Score Cards.

All of the Compliance Score Card information shown on the Mandatory reporting Home page should be editable by this authorized MCA-N user.

Should Have

F6. Maintain Compliance Postings - Provide users with MCA-N Public Relations Access Rights with the ability to create, edit and delete Compliance Postings. This may include the following:

• Minutes of NCA-N Board Meetings • Minutes of Stakeholders/ Consultative Committee meetings • Monitoring & Evaluation Plans • Audit Reports and reports/ evaluations by external reviewers • Disbursement requests, requesting funding from the MCC and outlining the results of the

expenditure from the last request • Any other reports submitted to the MCC • Legislation and other documents related to the formation, organization and governance of

Must Have

http://www.mcc.gov/mcc/bm.doc/score-fy08-namibia.pdf�

Page 22 of 85


the MCA-N

All of the information shown on the MCA-N Board Meeting Detail page should be editable by this authorized MCA-N user.

G. MAJOR FUNCTION 4: BACKGROUND INFORMATION

There are the following groupings of background information:

• 4.1 : Background Information – Corporate Information • 4.2 : Background Information – Funding Timeline

MAJOR FUNCTION 4.1: BACKGROUND INFORMATION – COPORATE INFORMATION


G1. Branding – This Major function should be branded “About Us” Must Have

G2. About MCC – this page should display background information regarding the Millennium Challenge Corporation as well as a link to http://www.mcc.gov/ The actual content to be displayed will be agreed in the Detailed Requirements Workshops.

Must Have

G3. About MCA-N – this page should display background information regarding the Millennium Challenge Account – Namibia. This may include a graphical representation of the MCA-N Organization. This may have to be incorporated using Flash technology or something similar to display it attractively and legibly. The actual content to be displayed will be agreed in the Detailed Requirements Workshops.

Must Have

G4. About Namibia – this page should display relevant information about Namibia. This may also include links to relevant websites. The actual content to be displayed will be agreed in the Detailed Requirements Workshops.

Must Have



G5. Although it is not expected that this information will be mainly static, users with MCA-N Public Relations Access Rights should be able to maintain information displayed on each of these pages.

Must Have

MAJOR FUNCTION 4.2: BACKGROUND INFORMATION – FUNDING TIMELINE

If appropriate, and it can be integrated seamlessly within the MCA-N website, then www.dipity.com may be used for this requirement.


G6. Branding – This Major function should be branded “Funding Timeline” Must Have

G7. Funding Timeline Overview – The Funding Timeline home page should display a graphical timeline across the top of the page, highlighting the following milestones and tasks relating to the funding and implementation of the MCA-N compact:

Timeline/Milestone Type Timing

Namibia becomes eligible for MCC funding

Milestone November 2005

Establishment of the formal structures to guide Programme development

Task November 2005 - April 2006

Development of the Programme Proposal

Task May – September 2006

Round 1 of regional consultative Milestone June 2006

Must Have


http://www.dipity.com/�

Page 23 of 85


meetings: Programme Proposal development

MCA Namibia Programme Proposal is submitted to MCC

Milestone September 2006

Round 2 of regional consultative meetings: feedback on the final Programme Proposal


MCC Investment Committee approval of the Opportunity Memorandum

Milestone December 2006

MCC-led Due Diligence of the MCA Namibia Programme Proposal

Task February 2007 – May 2008

Final MCA Namibia – MCC negotiations of the MCA Namibia Compact

Milestone June 2008

Signing of the MCA Namibia Compact Milestone July 2008

MCA Namibia Management Unit Mobilisation

Task August 2008 – March 2009

Namibian Parliament Ratifies the MCA Namibia Compact


Round 3 of regional consultative meetings: feedback on the final MCA Namibia Compact Programme

Milestone February 2009

MCA Namibia Compact Implementation Funding

Task April – September 2009

MCA Namibia Compact Entry-Into-Force Milestone September 2009

MCA Namibia Programme Implementation

Task September 2009 – September 2013

Users should be able to click on any Task or Milestone in the timeline and the bottom part of the page should display the relevant details (see below).

G8. Timeline Detail – One a task or timeline is clicked in the Funding Timline overview graphical diagram, the relevant detail should be displayed.

The actual content to be displayed for each Task and Milestone will be agreed in the Detailed Requirements Workshops, however:

• Content is likely to include text, images, attachments and links laid out in an attractive manner

• MCA-N should be able to modify this content (see below)

Must Have


ID

Requirement Priority

G9. Provide users with MCA-N Public Relations Access Rights with the ability to upload any amendments to the Compact to appear alongside the Compact under the timeline when selected.

Must Have

G10. Provide users with MCA-N Public Relations Access Rights with the ability to upload any amendments to the Programme Implementation Agreement to appear alongside the Programme

Must Have

Page 24 of 85

ID

Requirement Priority

Implementation Agreement under the timeline when selected

G11. Provide uses with MCA-N Public Relations Access Rights to modify the content of any Milestone or Task which has a Timeline Detail.

Must Have

G12. Provide users with MCA-N Public Relations Access Rights to change Milestone and Task dates which should then be automatically reflected in the graphical Funding Timeline Overview

Should Have

G13. Provide users with MCA-N Public Relations Access Rights to add and delete Milestones and Tasks to the Funding Timeline Overview

Should Have

H. MAJOR FUNCTION 5: AUTOMATED PROCUREMENT PROCESS

PROCUREMENT TERMINOLOGY

The following terms are used in this section to describe the requirements for the automated procurement process.

• General Procurement Notice (GPN) – An announcement associated with a period of time during which there will be a number of Procurements. Only one GPN may be active at a given time, but over the course of the MCA-N implementation there will be multiple GPN’s.

• Procurement – A planned, in progress or completed acquisition of goods or services by MCA-N. Depending on the estimated value of the procurement, each procurement may or may not have an associated Specific Procurement Notice, allowing vendors to bid.

• Specific Procurement Notice (SPN) – An announcement associated with a procurement, which has always has associated Bidding Documents to enable vendors to bid for MCA-N procurements.

• Bidding Documents – documents that enable prospective vendors to bid for MCA-N procurements.


H1. Branding – This Major function should be branded “Procurement Opportunities” Must Have

H2. Procurement Rules – The Procurement Opportunities Home Page should outline key procurement rules as well as an overview of the procurement process and guidelines for selection. All information here should be displayed on the page but also made available for download in .pdf format for all users. There may be multiple documents or sections that describe the procurement rules.

The actual content to be displayed will be agreed in the Detailed Requirements Workshops.

Additionally, this section should include links to other relevant pages (such as MCC procurement pages).

Must Have

H3. General Procurement Notice – The Procurement Opportunities Home Page should outline the current active General Procurement Notice. The current active GPN should be automatically determined based on the GPN Start Date, GPN End Date and the current date.

The following details should be displayed for the current active GPN:

Must Have

General Procurement

Notice

Procurement Procurement

Specific Procurement

Notice

Specific Procurement

Notice

Bidding Documents

General Procurement

Notice

Bidding Documents

Page 25 of 85


• GPN Start Date • GPN End Date • A list of all of the Procurements that have been created for this GPN. Each Procurement

should display a Status Link.

The Status Link for each procurement should be determined as follows:

• Closed – where the Procurement has an end date that has passed, the displayed status should be “closed” with no associated link.

• Express Interest – where the Procurement has an end date that has not yet passed; but there is no associated active Specific Procurement Notice (either because there is not going to be an SPN for this Procurement; or the SPN has not yet been created; or the SPN has been created, but the current date is not between the SPN start date and SPN end date), then the displayed status should be “Express Interest” with a link to the GPN Procurement Express Interest Page.

• More Information – where the Procurement has an end date that has not yet passed and it has an associated SPN that is currently active (because the current date is between the SPN start date and SPN end date), then the displayed status should be “More Information” with a link to the relevant Specific Procurement Notice Detail page.

H4. Website Registration required to access GPN Procurement Express Interest Page – Users will have to be registered with the MCA-N Website in order to express interest in a given Procurement.

If the user is already logged into the website, then they would be immediately navigated to the GPN Procurement Express Interest Page.

If the user is not logged in to the website, then they would be asked to provide login details (as they may have registered previously) or to register. Upon successful login or registration, they would be navigated to the GPN Procurement Express Interest Page.

Must Have

H5. GPN Procurement Express Interest Page – This page will be reached after a logged in user has clicked on an Express Interest link against a specific Procurement under the current active General Procurement Notice.

This page will only have been made available if the given Procurement did not have an associated active SPN.

On this page, all details relating to the procurement will be displayed:

• Procurement Description • Procurement Start Date • Procurement End Date

Additionally, the user will be able to click on a button to Express Interest in the given procurement, at which point a Record of their Expression of Interest will be made (see below).

Must Have

H6. Record of Expressed Interest – When a user clicks on an Express Interest Button within the GPN Procurement Express Interest Page, a record of this user will be stored against the Procurement.

Must Have

H7. Specific Procurement Notice Summary List – The Procurement Opportunities Home Page should provide a list of active Specific Procurement Notice’s that MCA-N are currently sourcing. SPNs are deemed active if the current date is between the SPN start date and SPN end date. Note that this may mean that SPNs are listed even if they “belong” to a Procurement that is in a previous General Procurement Notice period.

Summary information should be displayed for each active SPN including:

• Procurement Code • Name of Procurement • Deadline for Bid Submission including Countdown to deadline

Must Have

Page 26 of 85


• Date of Posting

SPN summaries should be listed in order of SPN End Date (with the earliest end dates first).

Users should be able to click on any SPN Summary and then be navigated to the Specific Procurement Notice Detail.

H8. Specific Procurement Notice Detail – The Specific Procurement Notice should provide full details of the procurement opportunity including:

• SPN Procurement Code • Name of SPN • Name of associated Procurement • SPN End Date - Deadline for Bid Submission including Countdown to deadline • SPN Start Date – Date that the SPN became active • Description of SPN • Location of SPN • Anticipated Start Date • Anticipated Duration • Specific Procurement Qualification Requirements • Contact People

The Specific Procurement Notice should provide a link to enable the user download any bidding documents such as an RFP or TOR.

A sample Specific Procurement Notice can be found here: http://www.mcanamibia.org/docs/spn_6.5.18_09.07.04.pdf

Must Have

H9. Website Registration required to access bidding documents – Users will have to be registered with the MCA-N Website in order to bid for a procurement opportunity.

If the user is already logged into the website, then they would be immediately navigated to the page where they can download the bidding documents.

If the user is not logged in to the website, then they would be asked to provide login details (as they may have registered previously) or to register. Upon successful login or registration, they would be navigated to the page where they can download the bidding documents.

Must Have

H10. Download Bidding Documents – Registered users should be able to download the bidding documents for a given Specific Procurement Notice so long as all mandatory fields below are entered.

The following fields should be captured from the user.

• Email Address – this will be defaulted based on the email address captured in the Website Registration Process.

• Name of Company If these details are already captured in the Website Registration process, then

they should be defaulted from there. If these details are changed here, then the fields should be updated in the

Website Registration data for this user. • First Name, Last Name

If these details are already captured in the Website Registration process, then they should be defaulted from there.

If these details are changed here, then the fields should be updated in the Website Registration data for this user.

• Fax Number If these details are already captured in the Website Registration process, then


Must Have

http://www.mcanamibia.org/docs/spn_6.5.18_09.07.04.pdf�

Page 27 of 85


Website Registration data for this user.

Note that all fields are mandatory and the user would only be able to download the bidding documents when data is captured for all of them.

Bidding documents may be in any of the following file formats:

• .pdf • MS Office

H11. Confirmation of Access to Bidding Documents - Upon a user successfully downloading the bidding documents, the following emails should be generated by the MCA-N Website:

• Email to all users with MCA-N Procurement Access Rights with the following details: Procurement Code Name of Procurement Deadline for Bid Submission including Countdown to deadline IP address of Computer downloading bidding documents Date & Time that bidding documents were downloaded Email Address of user that downloaded bidding documents Name of Company of user that downloaded bidding documents First Name, Last Name of user that downloaded bidding documents Fax Number of user that downloaded bidding documents

• Email to the user that downloaded the documents with: Confirmation that they have downloaded the Procurement Documents:

Procurement Code Name of Procurement Deadline for Bid Submission including Countdown to deadline Name of documents downloaded Date & Time that bidding documents were downloaded Name of Company of user that downloaded bidding documents First Name, Last Name of user that downloaded bidding documents Fax Number of user that downloaded bidding documents

Must Have

H12. Record of Access to Bidding Documents - When a user has accessed bidding documents, a record of this user will be stored against the SPN.

Must Have

H13. Notice of Awards Summary List – The Procurement Opportunities Home Page should display summary information for recent award of procurement contracts including:

• Date when the award was made • Summary of the Award

Users should be able to click on any Award and then be navigated to the full Award Detail.

Notice of Awards should be listed in chronological order with the most recent awards at the top. Notice of Awards should not appear after they are no longer relevant. They will be no longer relevant after a configured period of time after they were first posted.

There should be a “See more” option for users to see the entire listing of Awards including those that are no longer relevant.

Must Have

H14. Notice of Awards Detail – when a user has clicked on a link to view a notice of Award, the details of that Award should be displayed.

The following information may be displayed for a Notice of Award:

• Date when the award was made • Summary of the Award • Detailed Description of Award

Must Have

Page 28 of 85



H15. Maintain General Procurement Notices - Provide users with MCA-N Procurement Access Rights with the ability to create, edit and delete General Procurement Notices.

All of the information shown on the General Procurement Notice should be editable by this authorized MCA-N user.

The MCA-N Website should prevent the user from entering GPN Start Dates and End Dates that overlap, and the GPN Start Date should always follow the day after the preceding GPN End Date, since at any one time there should always be one and only one active GPN.

Must Have

H16. Maintain Procurements – Provide users with MCA-N Procurement Access Rights with the ability to create, edit and delete Procurements under a given General Procurement Notice.

All of the information shown on the GPN Procurement Express Interest Page should be editable by this authorized MCA-N user.

Must Have

H17. Maintain Specific Procurement Notices - Provide users with MCA-N Procurement Access Rights with the ability to create, edit and delete Specific Procurement Notices against a given Procurement.

All of the information shown on the Specific Procurement Notices page should be editable by this authorized MCA-N user.

The MCA-N Website should validate to ensure that SPNs are always created against Procurements. Note that SPNs can be created with an SPN Start date in the future, which will result on the SPN initially not being displayed in the SPN Summary List until the Start Date is reached.

Must Have

H18. Automated Outbound Updates to Express Interest Users – When an SPN becomes active, an automated email should be sent to all users that Expressed an Interest in the associated Procurement.

The email should be blind copied to all MCA-N users with Procurement Access Rights and separate emails should be sent to all recipients as they should not be able to determine other user’s email addresses.

The content of the email should contain the following information:

• Reminder that they expressed an interest in a given Procurement • That the a Specific Procurement Notice associated with that Procurement has been

published • A link to the SPN

Nice to Have

H19. Maintain Bidding Documents – Provide users with MCA-N Procurement Access Rights with the ability to add or delete bidding documents against a Specific Procurement Notice. These are the documents that registered end users would then be able to download.

Must Have

H20. Outbound Updates to Users who have downloaded Bidding Documents – If any changes are made to Specific Procurement Notices, or if additional Bidding Documents are added to an SPN, then an automated email should be sent to all users that downloaded Bidding Documents.

The email should be blind copied to all MCA-N users with Procurement Access Rights and separate emails should be sent to all recipients as they should not be able to determine other user’s email addresses.

The content of the email should contain the following information:

• Notice that details of an SPN or bidding document have changed • A link to the SPN or bidding documents page that has changed.

Nice to Have

H21. Generate Report of Express Interest Users – A user with MCA-N Procurement Access Rights should be able to generate a report that lists the following for all users that expressed an interest in a

Must Have

Page 29 of 85


given Procurement:

• Email Address • Name of Company • First Name, Last Name • Fax Number

H22. Generate Report of Users who have downloaded Bidding Documents – A user with user with MCA-N Procurement Access Rights should be able to generate a report that lists the following for all users that have downloaded bidding documents for a given SPN:

• Email Address • Name of Company • First Name, Last Name • Fax Number

Must Have

H23. Maintain Notice of Awards – Provide users with MCA-N Procurement Access Rights with the ability to create, edit and delete Notice of Awards.

All of the information shown on the Notice of Awards Detail Page should be editable by this authorized MCA-N user.

Must Have

I. MAJOR FUNCTION 6: AUTOMATED RECRUITMENT PROCESS


I1. Branding – This Major function should be branded “Employment Opportunities” Must Have

I2. Employment Opportunity Summary List – The Employment Opportunities Home Page should provide a list of currently unfulfilled employment opportunities.

Summary information should be displayed for each employment opportunity, including:

• Job Title • Job Location • Deadline for Application including Countdown to deadline • Date of Posting

Employment Opportunities should be listed in order of Date of Posting (with the most recent at the top).

Users should be able to click on any Employment Opportunity and then be navigated to the Employment Opportunity Detail.

Must Have

I3. Employment Rules – The Employment Home Page should outline key employment rules as well as an overview of the employment process and guidelines for selection.

The actual content to be displayed will be agreed in the Detailed Requirements Workshops.

Must Have

I4. Employment Opportunity Detail – The Employment Opportunity Detail should provide full details of the employment opportunity including:

• Job Title • Job Location • Deadline for Application including Countdown to deadline • Unique Job Reference • Date of Posting • Job Description

The Employment Opportunity Detail should provide a link to enable the user to apply for the opportunity.

Must Have

Page 30 of 85


I5. Website Registration required for Employment Opportunity Application – Users will have to be registered with the MCA-N Website in order to enter an employment opportunity application.

If the user is already logged into the website, then they would be immediately navigated to the Employment Opportunity Application.

If the user is not logged in to the website, then they would be asked to provide login details (as they may have registered previously) or to register. Upon successful login or registration, they would be navigated to the Employment Opportunity Application without the need to click on the link again.

Must Have

I6. Employment Opportunity Application – Registered users should be able to apply for a given Employment Opportunity. The following fields should be captured from the user:

• First Name, Last Name of Applicant If these details are already captured in the Website Registration process, then


Website Registration data for this user. • Email Address – this will be defaulted based on the email address captured in the Website

Registration Process. • Telephone Number – this will be defaulted based on the email address captured in the

Website Registration Process. • Cover Note

In addition, the registered user should be able to upload their resume in any of the following file formats:

• .pdf • .doc (MS Word)

Must Have

I7. Routing of Employment Opportunity Application - Upon submission of a user’s employment opportunity application, the following emails should be generated by the MCA-N Website:

• Email to all users with MCA-N Human Resources Access Rights with all details captured from the user as well as the following Employment Opportunity details:

Job Title Unique Job Reference

• Email to the user that submitted the employment opportunity application with Confirmation that the application had been received by MCA-N and standard text

regarding turn-around time for a response The details of the email sent to MCA-N Human Resources users (above)

Must Have



I8. Maintain Employment Opportunities - Provide users with MCA-N Human Resources Access Rights with the ability to create, edit and delete Employment Opportunities.

All of the Employment Opportunity information shown on the Employment Opportunity Detail page should be editable by this authorized MCA-N user.

Additionally, authorized users should be able to flag when the Opportunity was closed. At this point, the Opportunity would no longer appear in the Employment Opportunity Summary List and users would not be able to apply.

Must Have

Page 31 of 85

J. MAJOR FUNCTION 7: AUTOMATED EVENT REGISTRATION PROCESS


J1. Availability – A link to this major function should be made available for selected Events where a user with MCA-N Public Relations Access Rights has indicated that a given event from Major Function 2 should have an automated Event Registration Process.

Should Have

J2. Website Registration required for Event Registration – Users will have to be registered with the MCA-N Website in order to register for an event.

If the user is already logged into the website, then they would be immediately navigated to the Event Registration.

If the user is not logged in to the website, then they would be asked to provide login details (as they may have registered previously) or to register. Upon successful login or registration, they would be navigated to the Event Registration without the need to click on the link again.

Should Have

J3. Event Registration – Registered users should be able to register for a given event. The following fields should be captured from the user:


• Contact Telephone Number • Position of Individual/ Type of Business for Company • Possibility to enter one or more Attendees with the following information:

First Name, Last Name of Registrant

Should Have

J4. Routing of Event Registration - Upon submission of a user’s event registration, the following emails should be generated by the MCA-N Website:

• Email to all users with MCA-N Public Relations Access Rights with all details captured from the user as well as the following Event details:

Date/ Time of Event Name of Event Location of Event Link to Event Details Posting

• Email to the user that submitted the event registration application with Confirmation that the registration had been received by MCA-N and any standard

text The details of the email sent to MCA-N Public Relations users (above)

Should Have

K. TECHNICAL REQUIREMENTS

The key technical requirements of the Phase 2 MCA-N Website are as follows:


K1. Browser Compatibility – All of the MCA-N Website functionality should be available to users on the following browsers/ versions:

• Internet Explorer version 6 and all subsequent major and minor versions • Firefox/ Mozilla version 3 and all subsequent major and minor versions • Safari version 3 and all subsequent major and minor versions • Google Chrome version 1 and all subsequent major and minor versions

Must Have

K2. Hosting – The MCA-N Website may be hosted on the existing web server in Germany or elsewhere. MCA-N has a preference for the Website to be hosted in Namibia or Southern Africa, but this is not a mandatory requirement.

Must Have

K3. Upgradability – The site should be developed using techniques that allow for simple extensibility and upgradability of the site in the future. This should accommodate both increases in site

Must Have

Page 32 of 85


volumes, addition or removal of site content as well as restructuring of the site map and navigation and addition of new functionality for new user types in the future.

K4. Use of appropriate technologies – The site should utilize appropriate technologies to enhance the appeal of the site and achieve the desired dynamism. For example, it is expected that the site will make use of technology such as:

• Adobe Shockwave/ Flash for graphical animations • Scripting technology such as PHP or ASP to generate web pages dynamically • Read only Adobe PDF files for the publication of reports, etc

Must Have

K5. File Formats supported – The site should allow MCA-N to upload files of any format for download by website users.

Must Have

K6. Appropriate use of graphic files – The use of graphical content has to be optimized to work over a range of end user bandwidth capabilities. As a rule of thumb, the site should still be usable assuming a 56k dial-up speed.

Must Have

K7. Backup and restore – it should be possible to back up and restore the MCA-N Website including all data held in databases and all content.

Should Have

Page 33 of 85

Appendix 1 – Web Content Accessibility Guidelines

GUIDELINE 1. PROVIDE EQUIVALENT ALTERNATIVES TO AUDITORY AND VISUAL CONTENT.

Provide content that, when presented to the user, conveys essentially the same function or purpose as auditory or visual content.

Although some people cannot use images, movies, sounds, applets, etc. directly, they may still use pages that include equivalent information to the visual or auditory content. The equivalent information must serve the same purpose as the visual or auditory content. Thus, a text equivalent for an image of an upward arrow that links to a table of contents could be "Go to table of contents". In some cases, an equivalent should also describe the appearance of visual content (e.g., for complex charts, billboards, or diagrams) or the sound of auditory content (e.g., for audio samples used in education).

This guideline emphasizes the importance of providing text equivalents of non-text content (images, pre-recorded audio, video). The power of text equivalents lies in their capacity to be rendered in ways that are accessible to people from various disability groups using a variety of technologies. Text can be readily output to speech synthesizers and braille displays, and can be presented visually (in a variety of sizes) on computer displays and paper. Synthesized speech is critical for individuals who are blind and for many people with the reading difficulties that often accompany cognitive disabilities, learning disabilities, and deafness. Braille is essential for individuals who are both deaf and blind, as well as many individuals whose only sensory disability is blindness. Text displayed visually benefits users who are deaf as well as the majority of Web users.

Providing non-text equivalents (e.g., pictures, videos, and pre-recorded audio) of text is also beneficial to some users, especially nonreaders or people who have difficulty reading. In movies or visual presentations, visual action such as body language or other visual cues may not be accompanied by enough audio information to convey the same information. Unless verbal descriptions of this visual information are provided, people who cannot see (or look at) the visual content will not be able to perceive it.

Checkpoints:

1.1 Provide a text equivalent for every non-text element (e.g., via "alt", "longdesc", or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (e.g., animated GIFs), applets and programmatic objects, ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video. [Priority 1]

For example, in HTML:

• Use "alt" for the IMG, INPUT, and APPLET elements, or provide a text equivalent in the content of the OBJECT and APPLET elements.

• For complex content (e.g., a chart) where the "alt" text does not provide a complete text equivalent, provide an additional description using, for example, "longdesc" with IMG or FRAME, a link inside an OBJECT element, or a description link.

• For image maps, either use the "alt" attribute with AREA, or use the MAP element with A elements (and other text) as content.

1.2 Provide redundant text links for each active region of a server-side image map. [Priority 1] 1.3 Until user agents can automatically read aloud the text equivalent of a visual track, provide an auditory description of the important information of the visual track of a multimedia presentation. [Priority 1]

Synchronize the auditory description with the audio track as per checkpoint 1.4. Refer to checkpoint 1.1 for information about textual equivalents for visual information.

1.4 For any time-based multimedia presentation (e.g., a movie or animation), synchronize equivalent alternatives (e.g., captions or auditory descriptions of the visual track) with the presentation. [Priority 1] 1.5 Until user agents render text equivalents for client-side image map links, provide redundant text links for each active region of a client-side image map. [Priority 3]

http://www.w3.org/TR/WCAG10/#equivalent�

http://www.w3.org/TR/WCAG10/#text-equivalent�

http://www.w3.org/TR/WCAG10/#braille-display�

http://www.w3.org/TR/WCAG10/#d-link�

http://www.w3.org/TR/WCAG10/wai-pageauth.html#until-user-agents�

http://www.w3.org/TR/WCAG10/#auditory-description�

http://www.w3.org/TR/WCAG10/#tech-synchronize-equivalents�

http://www.w3.org/TR/WCAG10/#tech-text-equivalent�


Page 34 of 85

GUIDELINE 2. DON'T RELY ON COLOR ALONE.

Ensure that text and graphics are understandable when viewed without color.

If color alone is used to convey information, people who cannot differentiate between certain colors and users with devices that have non-color or non-visual displays will not receive the information. When foreground and background colors are too close to the same hue, they may not provide sufficient contrast when viewed using monochrome displays or by people with different types of color deficits.

Checkpoints:

2.1 Ensure that all information conveyed with color is also available without color, for example from context or markup. [Priority 1] 2.2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen. [Priority 2 for images, Priority 3 for text].

GUIDELINE 3. USE MARKUP AND STYLE SHEETS AND DO SO PROPERLY.

Mark up documents with the proper structural elements. Control presentation with style sheets rather than with presentation elements and attributes.

Using markup improperly -- not according to specification -- hinders accessibility. Misusing markup for a presentation effect (e.g., using a table for layout or a header to change the font size) makes it difficult for users with specialized software to understand the Organisation of the page or to navigate through it. Furthermore, using presentation markup rather than structural markup to convey structure (e.g., constructing what looks like a table of data with an HTML PRE element) makes it difficult to render a page intelligibly to other devices (refer to the description of difference between content, structure, and presentation).

Content developers may be tempted to use (or misuse) constructs that achieve a desired formatting effect on older browsers. They must be aware that these practices cause accessibility problems and must consider whether the formatting effect is so critical as to warrant making the document inaccessible to some users.

At the other extreme, content developers must not sacrifice appropriate markup because a certain browser or assistive technology does not process it correctly. For example, it is appropriate to use the TABLE element in HTML to mark up tabular information even though some older screen readers may not handle side-by-side text correctly. Using TABLE correctly and creating tables that transform gracefully makes it possible for software to render tables other than as two-dimensional grids.

Checkpoints:

3.1 When an appropriate markup language exists, use markup rather than images to convey information. [Priority 2] For example, use MathML to mark up mathematical equations, and style sheets to format text and control layout. Also, avoid using images to represent text -- use text and style sheets instead.

3.2 Create documents that validate to published formal grammars. [Priority 2] For example, include a document type declaration at the beginning of a document that refers to a published DTD (e.g., the strict HTML 4.0 DTD).

3.3 Use style sheets to control layout and presentation. [Priority 2] For example, use the CSS 'font' property instead of the HTML FONT element to control font styles.

3.4 Use relative rather than absolute units in markup language attribute values and style sheet property values. [Priority 2] For example, in CSS, use 'em' or percentage lengths rather than 'pt' or 'cm', which are absolute units. If absolute units are used, validate that the rendered content is usable (refer to the section on validation).

3.5 Use header elements to convey document structure and use them according to specification. [Priority 2] For example, in HTML, use H2 to indicate a subsection of H1. Do not use headers for font effects.

3.6 Mark up lists and list items properly. [Priority 2] For example, in HTML, nest OL, UL, and DL lists properly.

3.7 Mark up quotations. Do not use quotation markup for formatting effects such as indentation. [Priority 2] For example, in HTML, use the Q and BLOCKQUOTE elements to markup short and longer quotations, respectively.

http://www.w3.org/TR/WCAG10/#content-structure�

http://www.w3.org/TR/WCAG10/#tabular-information�

http://www.w3.org/TR/WCAG10/#style-sheet�

http://www.w3.org/TR/WCAG10/#validation�

Page 35 of 85

GUIDELINE 4. CLARIFY NATURAL LANGUAGE USAGE

Use markup that facilitates pronunciation or interpretation of abbreviated or foreign text.

When content developers mark up natural language changes in a document, speech synthesizers and braille devices can automatically switch to the new language, making the document more accessible to multilingual users. Content developers should identify the predominant natural language of a document's content (through markup or HTTP headers). Content developers should also provide expansions of abbreviations and acronyms.

In addition to helping assistive technologies, natural language markup allows search engines to find key words and identify documents in a desired language. Natural language markup also improves readability of the Web for all people, including those with learning disabilities, cognitive disabilities, or people who are deaf.

When abbreviations and natural language changes are not identified, they may be indecipherable when machine-spoken or brailled.

Checkpoints:

4.1 Clearly identify changes in the natural language of a document's text and any text equivalents (e.g., captions). [Priority 1]

For example, in HTML use the "lang" attribute. In XML, use "xml:lang". 4.2 Specify the expansion of each abbreviation or acronym in a document where it first occurs. [Priority 3]

For example, in HTML, use the "title" attribute of the ABBR and ACRONYM elements. Providing the expansion in the main body of the document also helps document usability.

4.3 Identify the primary natural language of a document. [Priority 3] For example, in HTML set the "lang" attribute on the HTML element. In XML, use "xml:lang". Server operators should configure servers to take advantage of HTTP content negotiation mechanisms ([RFC2068], section 14.13) so that clients can automatically retrieve documents of the preferred language.

GUIDELINE 5. CREATE TABLES THAT TRANSFORM GRACEFULLY.

Ensure that tables have necessary markup to be transformed by accessible browsers and other user agents.

Tables should be used to mark up truly tabular information ("data tables"). Content developers should avoid using them to lay out pages ("layout tables"). Tables for any use also present special problems to users of screen readers.

Some user agents allow users to navigate among table cells and access header and other table cell information. Unless marked-up properly, these tables will not provide user agents with the appropriate information.

The following checkpoints will directly benefit people who access a table through auditory means (e.g., a screen reader or an automobile-based personal computer) or who view only a portion of the page at a time (e.g., users with blindness or low vision using speech output or a braille display, or other users of devices with small displays, etc.).

Checkpoints:

5.1 For data tables, identify row and column headers. [Priority 1] For example, in HTML, use TD to identify data cells and TH to identify headers.

5.2 For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. [Priority 1]

For example, in HTML, use THEAD, TFOOT, and TBODY to group rows, COL and COLGROUP to group columns, and the "axis", "scope", and "headers" attributes, to describe more complex relationships among data.

5.3 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). [Priority 2]

Note. Once user agents support style sheet positioning, tables should not be used for layout. 5.4 If a table is used for layout, do not use any structural markup for the purpose of visual formatting. [Priority 2]

For example, in HTML do not use the TH element to cause the content of a (non-table header) cell to be displayed centered and in bold.

5.5 Provide summaries for tables. [Priority 3]

http://www.w3.org/TR/WCAG10/#natural-language�

http://www.w3.org/TR/WCAG10/wai-pageauth.html#text-equivalent�

http://www.w3.org/TR/WCAG10/#ref-RFC2068�


http://www.w3.org/TR/WCAG10/#screen-reader�



http://www.w3.org/TR/WCAG10/#user-agent�

http://www.w3.org/TR/WCAG10/#braille-display�

http://www.w3.org/TR/WCAG10/wai-pageauth.html#linearized-table�

http://www.w3.org/TR/WCAG10/#until-user-agents�

Page 36 of 85

For example, in HTML, use the "summary" attribute of the TABLE element. 5.6 Provide abbreviations for header labels. [Priority 3]

For example, in HTML, use the "abbr" attribute on the TH element.

GUIDELINE 6. ENSURE THAT PAGES FEATURING NEW TECHNOLOGIES TRANSFORM GRACEFULLY.

Ensure that pages are accessible even when newer technologies are not supported or are turned off.

Although content developers are encouraged to use new technologies that solve problems raised by existing technologies, they should know how to make their pages still work with older browsers and people who choose to turn off features.

Checkpoints:

6.1 Organize documents so they may be read without style sheets. For example, when an HTML document is rendered without associated style sheets, it must still be possible to read the document. [Priority 1]

When content is organized logically, it will be rendered in a meaningful order when style sheets are turned off or not supported.

6.2 Ensure that equivalents for dynamic content are updated when the dynamic content changes. [Priority 1] 6.3 Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. [Priority 1]

For example, ensure that links that trigger scripts work when scripts are turned off or not supported (e.g., do not use "javascript:" as the link target). If it is not possible to make the page usable without scripts, provide a text equivalent with the NOSCRIPT element, or use a server-side script instead of a client-side script, or provide an alternative accessible page as per checkpoint 11.4.

6.4 For scripts and applets, ensure that event handlers are input device-independent. [Priority 2] Refer to the definition of device independence.

6.5 Ensure that dynamic content is accessible or provide an alternative presentation or page. [Priority 2] For example, in HTML, use NOFRAMES at the end of each frameset. For some applications, server-side scripts may be more accessible than client-side scripts.

GUIDELINE 7. ENSURE USER CONTROL OF TIME-SENSITIVE CONTENT CHANGES.

Ensure that moving , blinking , scrolling , or auto-updating objects or pages may be paused or stopped.

Some people with cognitive or visual disabilities are unable to read moving text quickly enough or at all. Movement can also cause such a distraction that the rest of the page becomes unreadable for people with cognitive disabilities. Screen readers are unable to read moving text. People with physical disabilities might not be able to move quickly or accurately enough to interact with moving objects.

Note. All of the following checkpoints involve some content developer responsibility until user agents provide adequate feature control mechanisms.

Checkpoints:

7.1 Until user agents allow users to control flickering, avoid causing the screen to flicker. [Priority 1] Note. People with photosensitive epilepsy can have seizures triggered by flickering or flashing in the 4 to 59 flashes per second (Hertz) range with a peak sensitivity at 20 flashes per second as well as quick changes from dark to light (like strobe lights).

7.2 Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). [Priority 2] 7.3 Until user agents allow users to freeze moving content, avoid movement in pages. [Priority 2]

When a page includes moving content, provide a mechanism within a script or applet to allow users to freeze motion or updates. Using style sheets with scripting to create movement allows users to turn off or override the effect more easily.

7.4 Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. [Priority 2] For example, in HTML, don't cause pages to auto-refresh with "HTTP-EQUIV=refresh" until user agents allow users to turn off the feature.

7.5 Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. [Priority 2]

http://www.w3.org/TR/WCAG10/#tech-alt-pages�

http://www.w3.org/TR/WCAG10/#device-independent�








Page 37 of 85

Note. The BLINK and MARQUEE elements are not defined in any W3C HTML specification and should not be used.

GUIDELINE 8. ENSURE DIRECT ACCESSIBILITY OF EMBEDDED USER INTERFACES.

Ensure that the user interface follows principles of accessible design: device-independent access to functionality, keyboard operability, self-voicing , etc.

When an embedded object has its "own interface", the interface -- like the interface to the browser itself -- must be accessible. If the interface of the embedded object cannot be made accessible, an alternative accessible solution must be provided.

Note. For information about accessible interfaces, please consult the User Agent Accessibility Guidelines ([WAI-USERAGENT]) and the Authoring Tool Accessibility Guidelines ([WAI-AUTOOL]).

Checkpoint:

8.1 Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies [Priority 1 if functionality is important and not presented elsewhere, otherwise Priority 2.]

GUIDELINE 9. DESIGN FOR DEVICE-INDEPENDENCE.

Use features that enable activation of page elements via a variety of input devices.

Device-independent access means that the user may interact with the user agent or document with a preferred input (or output) device -- mouse, keyboard, voice, head wand, or other. If, for example, a form control can only be activated with a mouse or other pointing device, someone who is using the page without sight, with voice input, or with a keyboard or who is using some other non-pointing input device will not be able to use the form.

Note. Providing text equivalents for image maps or images used as links makes it possible for users to interact with them without a pointing device.

Generally, pages that allow keyboard interaction are also accessible through speech input or a command line interface.

Checkpoints:

9.1 Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape. [Priority 1]

Refer also to checkpoint 1.1, checkpoint 1.2, and checkpoint 1.5. 9.2 Ensure that any element that has its own interface can be operated in a device-independent manner. [Priority 2]

Refer to the definition of device independence. 9.3 For scripts, specify logical event handlers rather than device-dependent event handlers. [Priority 2] 9.4 Create a logical tab order through links, form controls, and objects. [Priority 3]

For example, in HTML, specify tab order via the "tabindex" attribute or ensure a logical page design. 9.5 Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. [Priority 3]

For example, in HTML, specify shortcuts via the "accesskey" attribute.

GUIDELINE 10. USE INTERIM SOLUTIONS.

Use interim accessibility solutions so that assistive technologies and older browsers will operate correctly.

For example, older browsers do not allow users to navigate to empty edit boxes. Older screen readers read lists of consecutive links as one link. These active elements are therefore difficult or impossible to access. Also, changing the current window or popping up new windows can be very disorienting to users who cannot see that this has happened.

http://www.w3.org/TR/WCAG10/#ref-WAI-USERAGENT�

http://www.w3.org/TR/WCAG10/#ref-WAI-USERAGENT�

http://www.w3.org/TR/WCAG10/wai-pageauth.html#important�


http://www.w3.org/TR/WCAG10/#tech-text-equivalent�

http://www.w3.org/TR/WCAG10/#tech-redundant-server-links�

http://www.w3.org/TR/WCAG10/#tech-redundant-client-links�


http://www.w3.org/TR/WCAG10/wai-pageauth.html#image-map�

Page 38 of 85

Note. The following checkpoints apply until user agents (including assistive technologies) address these issues. These checkpoints are classified as "interim", meaning that the Web Content Guidelines Working Group considers them to be valid and necessary to Web accessibility as of the publication of this document. However, the Working Group does not expect these checkpoints to be necessary in the future, once Web technologies have incorporated anticipated features or capabilities.

Checkpoints:

10.1 Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. [Priority 2]

For example, in HTML, avoid using a frame whose target is a new window. 10.2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. [Priority 2]

The label must immediately precede its control on the same line (allowing more than one control/label per line) or be in the line preceding the control (with only one label and one control per line). Refer also to checkpoint 12.4.

10.3 Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns. [Priority 3]

Note. Please consult the definition of linearized table. This checkpoint benefits people with user agents (such as some screen readers) that are unable to handle blocks of text presented side-by-side; the checkpoint should not discourage content developers from using tables to represent tabular information.

10.4 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas. [Priority 3]

For example, in HTML, do this for TEXTAREA and INPUT. 10.5 Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. [Priority 3]

GUIDELINE 11. USE W3C TECHNOLOGIES AND GUIDELINES.

Use W3C technologies (according to specification) and follow accessibility guidelines. Where it is not possible to use a W3C technology, or doing so results in material that does not transform gracefully, provide an alternative version of the content that is accessible.

The current guidelines recommend W3C technologies (e.g., HTML, CSS, etc.) for several reasons:

• W3C technologies include "built-in" accessibility features. • W3C specifications undergo early review to ensure that accessibility issues are considered during the design

phase. • W3C specifications are developed in an open, industry consensus process.

Many non-W3C formats (e.g., PDF, Shockwave, etc.) require viewing with either plug-ins or stand-alone applications. Often, these formats cannot be viewed or navigated with standard user agents (including assistive technologies). Avoiding non-W3C and non-standard features (proprietary elements, attributes, properties, and extensions) will tend to make pages more accessible to more people using a wider variety of hardware and software. When inaccessible technologies (proprietary or not) must be used, equivalent accessible pages must be provided.

Even when W3C technologies are used, they must be used in accordance with accessibility guidelines. When using new technologies, ensure that they transform gracefully.

Note. Converting documents (from PDF, PostScript, RTF, etc.) to W3C markup languages (HTML, XML) does not always create an accessible document. Therefore, validate each page for accessibility and usability after the conversion process (refer to the section on validation). If a page does not readily convert, either revise the page until its original representation converts appropriately or provide an HTML or plain text version.

Checkpoints:

11.1 Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. [Priority 2]


http://www.w3.org/TR/WCAG10/#assistive-tech�



http://www.w3.org/TR/WCAG10/#tech-associate-labels�




http://www.w3.org/TR/WCAG10/#linearized-table�










http://www.w3.org/TR/WCAG10/#validation�

Page 39 of 85

Refer to the list of references for information about where to find the latest W3C specifications and [WAI-UA-SUPPORT] for information about user agent support for W3C technologies.

11.2 Avoid deprecated features of W3C technologies. [Priority 2] For example, in HTML, don't use the deprecated FONT element; use style sheets instead (e.g., the 'font' property in CSS).

11.3 Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) [Priority 3]

Note. Use content negotiation where possible. 11.4 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page. [Priority 1]

Note. Content developers should only resort to alternative pages when other solutions fail because alternative pages are generally updated less often than "primary" pages. An out-of-date page may be as frustrating as one that is inaccessible since, in both cases, the information presented on the original page is unavailable. Automatically generating alternative pages may lead to more frequent updates, but content developers must still be careful to ensure that generated pages always make sense, and that users are able to navigate a site by following links on primary pages, alternative pages, or both. Before resorting to an alternative page, reconsider the design of the original page; making it accessible is likely to improve it for all users.

GUIDELINE 12. PROVIDE CONTEXT AND ORIENTATION INFORMATION.

Provide context and orientation information to help users understand complex pages or elements.

Grouping elements and providing contextual information about the relationships between elements can be useful for all users. Complex relationships between parts of a page may be difficult for people with cognitive disabilities and people with visual disabilities to interpret.

Checkpoints:

12.1 Title each frame to facilitate frame identification and navigation. [Priority 1] For example, in HTML use the "title" attribute on FRAME elements.

12.2 Describe the purpose of frames and how frames relate to each other if it is not obvious by frame titles alone. [Priority 2]

For example, in HTML, use "longdesc," or a description link. 12.3 Divide large blocks of information into more manageable groups where natural and appropriate. [Priority 2]

For example, in HTML, use OPTGROUP to group OPTION elements inside a SELECT; group form controls with FIELDSET and LEGEND; use nested lists where appropriate; use headings to structure documents, etc.

12.4 Associate labels explicitly with their controls. [Priority 2] For example, in HTML use LABEL and its "for" attribute.

GUIDELINE 13. PROVIDE CLEAR NAVIGATION MECHANISMS.

Provide clear and consistent navigation mechanisms -- orientation information, navigation bars, a site map, etc. -- to increase the likelihood that a person will find what they are looking for at a site.

Clear and consistent navigation mechanisms are important to people with cognitive disabilities or blindness, and benefit all users.

Checkpoints:

13.1 Clearly identify the target of each link. [Priority 2] Link text should be meaningful enough to make sense when read out of context -- either on its own or as part of a sequence of links. Link text should also be terse. For example, in HTML, write "Information about version 4.3" instead of "click here". In addition to clear link text, content developers may further clarify the target of a link with an informative link title (e.g., in HTML, the "title" attribute).

13.2 Provide metadata to add semantic information to pages and sites. [Priority 2] For example, use RDF ([RDF]) to indicate the document's author, the type of content, etc.

http://www.w3.org/TR/WCAG10/#References�

http://www.w3.org/TR/WCAG10/#ref-WAI-UA-SUPPORT�

http://www.w3.org/TR/WCAG10/#ref-WAI-UA-SUPPORT�

http://www.w3.org/TR/WCAG10/#deprecated�

http://www.w3.org/TR/WCAG10/wai-pageauth.html#alt-page-note�

http://www.w3.org/TR/WCAG10/wai-pageauth.html#accessible�

http://www.w3.org/TR/WCAG10/wai-pageauth.html#equivalent�

http://www.w3.org/TR/WCAG10/#d-link�

http://www.w3.org/TR/WCAG10/#nav-mechanism�

http://www.w3.org/TR/WCAG10/#link-text�

http://www.w3.org/TR/WCAG10/#ref-RDF�

Page 40 of 85

Note. Some HTML user agents can build navigation tools from document relations described by the HTML LINK element and "rel" or "rev" attributes (e.g., rel="next", rel="previous", rel="index", etc.).

13.3 Provide information about the general layout of a site (e.g., a site map or table of contents). [Priority 2] In describing site layout, highlight and explain available accessibility features.

13.4 Use navigation mechanisms in a consistent manner. [Priority 2] 13.5 Provide navigation bars to highlight and give access to the navigation mechanism. [Priority 3] 13.6 Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group. [Priority 3] 13.7 If search functions are provided, enable different types of searches for different skill levels and preferences. [Priority 3] 13.8 Place distinguishing information at the beginning of headings, paragraphs, lists, etc. [Priority 3]

Note. This is commonly referred to as "front-loading" and is especially helpful for people accessing information with serial devices such as speech synthesizers.

13.9 Provide information about document collections (i.e., documents comprising multiple pages.). [Priority 3] For example, in HTML specify document collections with the LINK element and the "rel" and "rev" attributes. Another way to create a collection is by building an archive (e.g., with zip, tar and gzip, stuffit, etc.) of the multiple pages. Note. The performance improvement gained by offline processing can make browsing much less expensive for people with disabilities who may be browsing slowly.

13.10 Provide a means to skip over multi-line ASCII art. [Priority 3]

GUIDELINE 14. ENSURE THAT DOCUMENTS ARE CLEAR AND SIMPLE.

Ensure that documents are clear and simple so they may be more easily understood.

Consistent page layout, recognizable graphics, and easy to understand language benefit all users. In particular, they help people with cognitive disabilities or who have difficulty reading. (However, ensure that images have text equivalents for people who are blind, have low vision, or for any user who cannot or has chosen not to view graphics.)

Using clear and simple language promotes effective communication. Access to written information can be difficult for people who have cognitive or learning disabilities. Using clear and simple language also benefits people whose first language differs from your own, including those people who communicate primarily in sign language.

Checkpoints:

14.1 Use the clearest and simplest language appropriate for a site's content. [Priority 1] 14.2 Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page. [Priority 3] 14.3 Create a style of presentation that is consistent across pages. [Priority 3]



Page 41 of 85

Annex 2: Expression of Interest Form Mr. Johann Botha Director Procurement Millennium Challenge Account Namibia

Dear Sir,

Re: Change Management Advisor for Etosha National Park, MCAN/CIF/2.2.3b

I, the undersigned, offer to provide the consulting services for the abovementioned assignment in accordance with your Request for Consultant’s Qualifications dated [Insert Date] and this Expression of Interest.

I hereby submit my Expression of Interest, which will be open for acceptance for a period of 60 (sixty) days.

I hereby declare that all the information and statements made in this Expression of Interest are true and accept that any misrepresentation contained in it may lead to my disqualification.

If negotiations are held during the initial period of validity of the Expression of Interest, I undertake to negotiate on the basis of my availability for the assignment.

My Expression of Interest is binding upon me and subject to the modifications resulting from Contract negotiations, and I undertake, if my proposal is accepted, to initiate the consulting services related to the assignment not later than [insert the date on which you will be available to commence with the assignment].

I understand you are not bound to accept any proposal that you may receive.

Yours sincerely,

[Authorized Signatory]

[Name and title of Signatory]

[Address of Consultant]

Page 42 of 85

Annex 3: Curriculum Vitae (CV) Form 1. Name [Insert full name]

2. Date of Birth [Insert birth date]

3. Nationality [Insert nationality]

4. Education [Indicate college/university and other specialized education, giving names of institutions, degrees obtained, and dates of obtainment].

Professional Associations [Indicate membership in relevant Professional Associations]

5. Other Training [Indicate appropriate postgraduate and other training]

6. Countries of Work Experience [List countries where the consultant has worked in the last ten years]

7. Employment Record

[Starting with present position, list in reverse order every employment held by the consultant since graduation, giving for each employment (see format here below): dates of employment, name of employing organization, positions held.]

From: [Year] To: [Year] Employer: [Employer name] Position(s) held: [Describe your role and position]

8. Work undertaken that best illustrates capability to handle the tasks assigned

[Among the assignments in which the consultant has been involved, indicate the following information for those assignments that best illustrate his/her capability to handle the tasks listed in the TOR]

Name of assignment or project: [Project name] Period: [Indicate year and duration] Location: [Indicate location] Client: [Indicate client name and contact details] Main project features: [Provide a brief description of the assignment] Position held: [Indicate your title] Activities performed: [Provide a brief description of your role in this assignment]

13. References

[List at least three individual references with substantial knowledge of your work. Include each reference’s name, title, phone and e-mail contact information. MCA Namibia reserves the right to contact other sources as well as to check references, in particular for performance on any relevant MCC-funded projects.]

14. Certification

I, the undersigned, certify that to the best of my knowledge and belief, this CV correctly describes me, my qualifications, and my experience. I understand that any wilful misstatement described herein may lead to my disqualification or dismissal, if engaged.

I, the undersigned, hereby declare that I agree to participate in the above-mentioned assignment. I further declare that I am able and willing to work for the period foreseen in the above referenced Request for Constant's Qualifications.

[Signature]

[Date]

Page 43 of 85

Annex 4a: Technical Proposal Template Note: The information you provide as part of this Technical Proposal will be used to assess your capacity to carry out the assignment, rather than evaluate your technical approach to the assignment described in the TOR. The final technical approach and specification will be

I. SITE DESIGN TEMPLATE

Please provide a sample Site Design Template that:

• Outlines a possible unified graphical theme for the site • Highlights how navigation will take place

II. SAMPLE HOME PAGE

Please provide a sample home page layout that:

• Shows how the Site Design Template may be leveraged on individual web pages • Shows how content for each of the main user groups shall be segmented • Is striking, attractive and makes excellent use of graphics to hold the users attention.

III. CONTENT MANAGEMENT APPROACH

Explain your approach to content management that will enable MCA-N to maintain much of the sites content without engagement of your companies or other vendor’s services.

IV. SITE MAP

Based on the information provided in this RFP, propose a sample site map, highlighting the various sub pages of the site as well as the number of level envisioned.

V. PROJECT SCHEDULE

Describe your proposed phases or releases. For each phase/ release, provide:

• The timeframe from the start of the phase/ release to the start of Acceptance Testing of that phase/ release.

• The duration of the major tasks that constitute the phase/ release and key milestone dates. • The high level requirements to be met in that release (detailed requirements are provided in the

next section)

VI. SITE REQUIREMENT COMPLIANCE

Complete the last two columns of the table contained in Annex 3 (Technical Proposal) outlining your compliance to all of the requirements outlined in this TOR. You should complete these columns as follows:

COMPLIANCE

Do not Comply – You do not propose to support this requirement. List any such requirements in the Exception of Conditions section of this proposal.

Partially Comply – You propose to support some off this requirement, but not all. List the parts of requirements that you propose to not support in the Exception of Conditions section of this proposal.

Page 44 of 85

Fully Comply – You propose to support all aspects of this requirement.

DESCRIPTION OF COMPLIANCE

Where you Do not Comply, you may leave this column blank

Where you Partially Comply, you should indicate which aspects of the requirement you propose to satisfy and (where applicable) provide details of how you will satisfy the requirement

Where you Fully Comply, you should (where applicable) provide details of how you will satisfy the requirement.

PHASE/RELEASE

Where you Partially Comply or Fully Comply to a requirement, you should indicate the phase or release in which the requirement will be satisfied (corresponding to your Phases & Releases outlined in the previous section).

VII. PROPOSED WEB DESIGN & IMPLEMENTATION TECHNOLOGY

Provide details of the technologies you intend to employ in order to deliver the Phase 2 MCA-N Website. This should include:

• Browser side technologies such as Javascript, HTML, CSS • Browser Plug-ins such as Shockwave • Server-side scripting technologies such as PHP or ASP • Database technologies such as MySQL, Access, Oracle, etc

Provide the recommended server specification & configuration that will be required to run the Phase 2 MCA-N Website effectively. Provide a diagram or chart to illustrate where each of the software components will run.

VIII. TRAINING

Submit a plan to meet the training requirements outlined in this RFP.

Annex 4b: Technical Proposal Form ID MCA-N’s Requirement Description MCA-N’s

Priority Compliance (Do Not Comply/ Partially Comply/ Fully Comply)

Description of how you propose to meet the requirement (if applicable)

Phase/ Release (if applicable)

A1. Consistent, Unified or Common Theme – A basic site design template with modestly sized banner graphics or logos, signature icons and action buttons or links should be provided. This should be adaptable for each subsequent page of the website. There should be an underlying graphic theme that makes use of MCA-N & MCC logos, fonts and colours. It should be apparent that this is MCA-N website on every page, but this needs to be balanced with the need for each page to have flexibility in meeting its specific requirements.

Must Have

A2. User Friendly – The MCA-N website should incorporate the following User Friendly traits: • Use logical and intuitive links • Not overwhelm the user with visual clutter • Not exceed 1,024 pixels in width • Put most pertinent information at the top of a page; try to avoid the need to scroll down for more

information too often and stringently avoid pages which are more than 2 standard monitor heights in length.

• Be “printer-friendly” on all pages • Be usable – offering a quick and user friendly way to locate the information the user is looking

seeking without the user having to understand MCA-N Organisation. • Minimise number of mouse clicks required to find information.

Must Have

A3. Separation of Presentation from Content – The MCA-N Website development should separate presentation from content as much as is possible through the use of technologies such as CSS. This should enable changes in presentation and format to be made simply and quickly without impacting the content.

Must Have

A4. Accessibility – Be accessible to individuals with disabilities, meeting ADA Priority 1 Checkpoints. Please refer to Appendix 1 for Web Content Accessibility Guidelines (note that this Appendix lists Priority 1, 2 and 3 Checkpoints and this requirement only refers to the meeting of Priority 1 Checkpoints).

Should Have

A5. Navigational Tools – Offer graphic navigation buttons or bars offering shortcuts. Implementation techniques should not prevent the “Back” button within browsers from working as expected.

Must Have

A6. Content Management – Much of the site’s content should be maintainable and extendable by authorized MCA-N staff using Content Management functionality. Note the Content Management requirements included for major functions later in this document.

Must Have

A7. Track page hits per function – Administrator users should be able to determine the number of unique IP page hits each page of the site is receiving over periods of time (by day, week, month, etc). Where possible this information should include the country in which the IP address is registered.

Must Have

A8. Use of Hyperlinks – The site should make effective use of hyperlinks to link to relevant external sites. Must Have A9. Cookies – Cookies should be leveraged (but not depended on) to default key user information that may Must Have

Page 46 of 85

ID MCA-N’s Requirement Description MCA-N’s Priority

Compliance (Do Not Comply/ Partially Comply/ Fully Comply)



have been captured on previous visits by a particular user with the objective to short-cut user selections and tailor the site to the expected user needs (for example, it may be possible to default the user name/ email address of a user that has registered on the site and has requested to log in, or enable the “remember me” option on the login screen).

A10. Multimedia Library – Multimedia used throughout the MCA-N Website should be effectively managed using either an internal or external database which should facilitate easy management of multimedia files by MCA-N and appropriate tagging of multimedia files to facilitate searches across multimedia files.

Must Have

A11. Security – Passwords should be handled in a secure manner including the encrypted transmission of passwords over the internet and data storage.

Must Have

B1. Menus– Provide consistent menu for accessibility to functionality on the site. The menu may require to be dynamic depending on certain criteria (for example, a registered user may have menu options such as account maintenance which are not available to anonymous users). The current MCA-N Phase 1 site has the top, left column and right column dedicated to menu’s on all pages. The left and right menus should not be required so these areas can be used for page content.

Must Have

B2. Search – Provide site search functionality that enables users to find the information that they require quickly. All content on the site (including but not limited to information created through Content Management functionality by MCA-N staff, tagged multimedia files and the contents of attached documents) should be searchable.

Must Have

B3. Registration – Provide users with the ability to register with the MCA-N Website. Certain functionality may only be available for registered users (e.g. downloading of procurement RFPs, applying for an employment opportunity or registering for an event). Upon registration, users should provide information including but to limited to the following: • Email address – used as the unique identifier for the user’s registration (Mandatory) • Password – used by the user to log in (Mandatory) • Name of Company (Optional, but Mandatory to download Procurement Bidding documents) • First Name, Last Name (Optional, but Mandatory to download Procurement Bidding documents) • Telephone Number (Optional) • Fax Number (Optional, but Mandatory to download Procurement Bidding documents) • Country of Residence (Optional) • Preferences (Optional) :

• Does the user want to receive emails from MCA-N • Does the user want to receive notifications when content is added or changed to the MCA-N

website • Areas of Interest:

• Projects • News and Events

Must Have

Page 47 of 85





• Mandatory Reporting • Procurement Opportunities • Employment Opportunities

B4. Registration Access Rights – MCA-N should be able to set access rights for registered users. The specific categories of user access rights may include the following: • Normal “read-only” user • MCA-N Project Manager user – allows user to post, edit, archive and delete Project Updates on the

Project Home page for their project only. • MCA-N Public Relations user – allows user to post, edit, archive and delete Press Releases,

Announcements, Event Summaries, Mandatory reporting Postings & Approved Testimonials • MCA-N Procurement user – allows user to post, edit, archive and delete Procurement Notices • MCA-N Human Resources user – allows user to post, edit, archive and delete Employment Notices • MCA-N Administrator user – allows the use to:

• Create, edit, archive, delete User Accounts, • Reset user passwords • Allocate access rights • Create, edit, archive, delete Projects/ Activities • Backup & Restore Database • View site visit statistics such as page hits per function • etc

Must Have

B5. Login – Allow registered users to log in by providing their authentication details that they provided during the registration process. There should be functionality that allows users to automatically recover or reset lost passwords in a secure manner.

Must Have

B6. Feedback submission – Provide a function by which users can submit feedback to MCA-N from all pages of the MCA-N Website. The user should be able to capture the feedback category (categories to be provided by MCA-N). The feedback function should also capture the page that the user was viewing when they clicked feedback. Feedback should be automatically routed to the relevant MCA-N employee’s email based on the feedback category or the page that the user was viewing. Feedback emails should also copied to an additional MCA-N email address so that MCA-N responses can be monitored. All MCA-N emails should be maintainable by MCA-N.

Must Have

B7. Contact details – Provide contact details for the MCA-N. Contact details should include: • Address (physical and postal) • Telephone number • Contact Email Address Unlike the MCA-N Phase 1 Website, the contact details do not have to be displayed in full detail on

Must Have

Page 48 of 85





every page. The details should be accessible from a menu link. B8. RSS Feed – Registered MCA-N Website users should be able to subscribe to the MCA-N Website RSS

Feed. The MCA-N Website should generate RSS Feeds for all of the major information posting son the site, including: • Project Postings (see Major Function 1) • Press Releases & Announcements (see Major Function 2) • Event Summaries (see Major Function 2) • Mandatory reporting Postings (see Major Function 3) • Procurement Notices (see Major Function 5) • Employment Notices (see Major Function 6) • Approved Testimonials (see Common/ Infrastructure Requirements)

Nice to Have

B9. Content Sharing – The MCA-N Website should allow users to share any content on the site which is available to anonymous (i.e. unregistered users) either through email or through integration with popular Social Networking Sites (such as Digg, Facebook, delicious, Reddit, etc).

Nice to Have

B10. Logos, References & Brand Assets – The MCA-N Website should use the latest logos references and brand assets for MCA-N and MCC.

Must Have

B11. Maintain Feedback/ Testimonials – Provide users with MCA-N Public Relations Access Rights with the ability to create, edit and delete testimonials or approved user feedback comments onto relevant pages.

Should Have

B12. Formatting of Content – Provide MCA-N with the ability to apply all aspects of formatting available in HTML to any content that it adds to the site. This should include the ability to configure hyperlinks to other pages inside or outside the MCA-N Website. By default the content should follow one defined style of formatting that should accommodate all content types (paragraphs, bulleted lists, etc) by standardising key formatting elements (such as font size, font type, font colour, font style, margins before and after paragraphs, etc.). However, it should be possible to deviate from the defined style.

Must Have

B13. Formatting of Picture Galleries – Provide MCA-N with the ability to layout pictures and multimedia files utilizing all aspects of formatting and layout available in HTML. For example, it should be possible to layout multiple pictures in single paragraphs; left aligned; right-aligned; within tables, etc. End users should be able to click on pictures and view them at full size as well as select ‘next’, ‘previous’ and other options typically available within picture galleries.

Must Have

B14. Support for Photo Essays – Provide MCA-N with the ability to create Photo Essays. Photo Essays should pop up in a separate window to the main window and lead the user through a series of photo’s and captions that can be used to tell a story. The Photo Essay pop up window should be clearly branded as an MCA-N asset and contain links to associated postings and pages on the MCA-N Website. It should be possible to email links to Photo Essays to facilitate viral marketing of key MCA-N stories.

Should Have

Page 49 of 85





An example photo essay can be found here: http://www.unicef.org/photoessays/49510.html B15. Home Page Flag – All content postings (Events, News, Procurement Opportunities, Project/ Activity

Postings, etc) should have a flag which indicates whether the posting should appear on the home page when it is relevant.

Must Have

B16. Mandatory reporting Flag & Category – All content postings (Events, News, Procurement Opportunities, Project/ Activity Postings, etc) should have a flag which indicates whether the posting should appear on the Mandatory reporting postings feed in the Mandatory reporting page when it is relevant. Additionally, where the a content posting is flagged with this, it should also be categorised into one of the following categories of mandatory reporting information: • MCA Namibia Board Minutes • M&E and Environmental Impact Assessment documents • Audits and Reviews • Disbursement Requests • MCC Reporting • Other Required Postings

Must Have

B17. Content Expiry Date – All content postings should have a user entered expiry date, after which time the content is not to be displayed on the website.

Should Have

B18. Maximum Upload Size – With the ability for numerous MCA-N users to upload content to the site and the potential for some website user’s to have limited bandwidth, it should be possible for MCA-N to configure maximum file upload sizes.

Must Have

B19. Review of Content – Provide automated workflow to manage the review of content prior to posting on the Website. It should be possible to configure the Content Management System to appoint users as reviewers for each type of content that can be posted. When new content is generated by an authorized user, the system should send an email containing a link to the content to the reviewing user. The reviewing user should then be able to edit, accept are reject the content. Only accepted content would be finalized for posting on the live site.

Should Have

B20. Hide Content – Provide the ability to hide content so that it is not displayed on the website, without deleting the content.

Must Have

B21. Automated Outbound Notification when no Updates – If a configured period of time passes without any content updates or postings to any of the major functions (including individual activities), then an email should be sent to all users who have the authorization access rights to that function with a copy to the reviewer (see B17 above) notifying them that Content has not been updated for this time.

Nice to Have

C1. Access to Major Functions – The home page should have clear links to the following major functions: Primary Links Primary links should be clearly visible in a prime position on the home page. Possibly, they should make

Must Have

http://www.unicef.org/photoessays/49510.html�

Page 50 of 85





use of large, relevant images. • Progress & Impact of Projects & Activities – there should be one link which should be branded

“Visit the Projects”. Following this link will navigate to Major Function 1: Progress & Impact of Projects & Activities.

• News & Upcoming Events – there should be one link which should be branded “Latest News & Events”. Following this link will navigate to Major Function 2: News & Upcoming Events.

• Mandatory reporting – there should be one link which should be branded “Ongoing Mandatory reporting”. Following this link will navigate to Major Function 3: Mandatory reporting.

All Primary Links should be accessible from the menu, anywhere in the Website. Secondary Links Secondary links should be visible, in a secondary location on the home page and non–graphical, smaller links may be sufficient. • Procurement Opportunities – there should be one link branded “Procurement Opportunities”.

Following this link will navigate to Major Function 5: Automated Procurement Process. • Employment Opportunities – there should be one link branded “Employment Opportunities”.

Following this link will navigate to Major Function 6: Automated Employment Process. • Background Information – there should be the following secondary links to background information

functions: • A link which should be branded “About Us”. Following this link will navigate to Major Function

4.1: Background Information – Corporate Information. • A link which should be branded “Funding Timeline”. Following this link will navigate to Major

Function 4.2: Background Information –Funding Timeline. Note that the Automated Event Registration major function would be available from the detail of a particular event.

C2. Aggregation of topical information – The home page should aggregate the most topical & relevant information postings to the site. These may include: • Activity Postings (see Major Function 1) • Press Releases & Announcements (see Major Function 2) • Event Summaries (see Major Function 2) • Mandatory reporting Postings (see Major Function 3) • Procurement Notices (see Major Function 5) • Employment Notices (see Major Function 6) • Approved Testimonials (see Common/ Infrastructure Requirements) Only those articles that were flagged to be displayed on the Home page should be included. Summary information should be displayed for each item, taken from the content created by MCA-N without the need for duplication. Users should be able to click on any article and then be navigated to the full

Must Have

Page 51 of 85





posting. Articles should not appear after they are no longer relevant. There should be a “See more” option for users to see the entire listing of articles including those that are no longer relevant.

C3. Registration – The home page should present a link to encourage regular users of the site to register. Following this link will navigate to Website Registration functionality (see Common/ Infrastructure Functional Requirements).

Must Have

D1. Branding – This Major function should be branded “Visit the Projects” Must Have D2. Project/ Activity List – the Project/ Activity Home Page should display a graphical list of

Projects/Activities, organized into each of the sectors. Users should be able to navigate to the Project Detail page by clicking on any one of the project links. MCA-N Administrator users should be able to use the content management functionality to add, modify and remove projects as required (see below). However the initial list of projects & activities by sector are likely to be: Education Project: • Education Quality Activity • Vocational Skills and Training Activity • Textbook Activity • Regional Study Resources Centres Activity • Tertiary Education Finance Activity Agriculture Project: • Land Access and Management Activity • Livestock Support Activity • Indigenous Natural Products Activity Tourism Project: • Improved Management and Infrastructure in the Etosha National Park Activity • Marketing Activity • Community-Based Tourism Development Activity

Must Have

D3. Activity Aggregation Feed – the Project/ Activity Home Page should display a feed of postings from all Activities in a logical order. Summary information should be displayed for each item, taken from the content created by MCA-N without the need for duplication. Users should be able to click on any Activity posting and then be navigated to the full posting. Activity Postings should not appear after they are no longer relevant. There should be a “See more” option for users to see the entire listing of Activity Postings including those that are no longer relevant.

Must Have

Page 52 of 85





D4. Activity Detail (Basic) – when a user has clicked on a link for a particular Activity, they should be navigated to the home page for that Activity. The Activity home page for a particular Activity should display key information about the project such as: • Contact Details for Activity Manager • Start Date • Funding Amount • Targeted Impact • Gant Chart showing major milestones • Project Images MCA-N Administrator users should be able to edit all of the above information using the content management functionality. Additionally, the Activity Detail page should show a summary list of all the relevant Activity Postings for that project. Activity Postings would have been created

Must Have

D5. Activity Detail (Advanced) – in addition to the basic information shown above, advance requirements include • Graphically represent progress along Gantt Chart • Display thumbnails/ icons to Activity Postings at relevant places on the Gantt chart. Users should

be able to click on the thumbnail/ icon to navigate to the associated posting.

Nice to Have

D6. Activity Postings – when a user has clicked on a link to view an Activity posting, that posting should be displayed in accordance to the type of posting (see below). The following information may be displayed for an Activity Posting: • Date/ Time of Posting • Author of Posting (taken from login details of MCA-N user making posting) • Description/ Title of posting • Ability to upload text content • Ability to upload one or multiple pictures in an attractive layout • Ability to upload Photo Essays (see Common/ Infrastructure Content Management Requirements) • Ability to upload other attachments such as:

• PDF files • MS Office files

Must Have

D7. Maintain Activities– Provide users with MCA-N Administrative Access Rights with ability to create, edit and delete Activities under each of the Projects. This should include assigning of the Project Manager from a list of registered users to the MCA-N website to enable the Project Manager to then upload Project Postings to their Activity. All of the Activity information shown on the Activity Detail page should be editable by this authorized MCA-N user.

Must Have

Page 53 of 85





D8. Maintain Activity Postings (Basic) – Provide users with MCA-N Project Manager Access Rights for a particular project with ability to create, edit and delete Activity postings for their Activity. All of the information shown on the Activity Posting page should be editable by this authorized MCA-N user.

Must Have

D9. Maintain Activity Postings (Advanced) – Provide users with MCA-N Project Manager Access Rights for a particular project with ability to graphically indicate progress along the Gantt chart for the Activity and place icons/ thumbnails for Activity postings at relevant places on the Gantt chart.

Nice to Have

E1. Branding – This Major function should be branded “Latest News & Events” Must Have E2. Press Releases & Announcements List – the News & Upcoming events page should display a summary

list of relevant Press Releases and Announcements. A Press Release is a special type of Announcement that has been used to communicate key information to the Press. Announcements may include: • Information following a Workshop – such as copies of presentations, speeches, etc • Changes in MCA-A Organization structure • Key Milestones being achieved Summary information should be displayed for each item. Users should be able to click on any Press Release or Announcement and then be navigated to the full posting. Press Releases & Announcements should not appear after they are no longer relevant. They will be no longer relevant after a configured period of time after they were first posted. There should be a “See more” option for users to see the entire listing of Press Releases & Announcements including those that are no longer relevant.

Must Have

E3. Event Summary List - the News & Upcoming events page should display a summary list of up-coming Events. Events may include: • Field Events (such as visits to projects/ activities) • Workshops Summary information should be displayed for each item. Users should be able to click on any Event and then be navigated to the full Event details. Event Summaries should not appear after they are no longer relevant. They will be no longer relevant after the event has passed. There should be a “See past events” option for users to see the entire listing of Events including those that took place in the past.

Must Have

E4. Press Release & Announcement Postings – when a user has clicked on a link to view a Press Release or Announcement, the details of that Press Release & Announcement should be displayed. The following information may be displayed for a Press Release & Announcement: • Date/ Time of Press Release/ Announcement

Must Have

Page 54 of 85





• Description/ Title of Press Release/ Announcement • Ability to upload text content • Ability to upload one or multiple pictures in an attractive layout • Ability to upload multimedia content such as:

• Photo Essays (where still images are displayed with written narration) • Ability to upload other attachments such as:


E5. Event Details Postings – when a user has clicked on a link to view an Event, the details of that Event should be displayed (see below). The following information may be displayed for an Event: • Date/ Time of Event • Name of Event • Location of Event • Directions to Event • Ability to upload text content describing the Event • Ability to upload one or multiple pictures in an attractive layout • Ability to upload multimedia content such as:

• Photo Essays (where still images are displayed with written narration) • Ability to upload other attachments such as:


In addition, the Event Detail should provide a link to any associated Event Registration function (see Major Function 7 : Automated Event Registration Process)

Must Have

E6. Maintain Press Releases & Announcements - Provide users with MCA-N Public Relations Access Rights with the ability to create, edit and delete Press Releases & Announcements. All of the Press Release & Announcement information shown on the Press Release & Announcement page should be editable by this authorized MCA-N user.

Must Have

E7. Maintain Events - Provide users with MCA-N Public Relations Access Rights with the ability to create, edit and delete Event Details. All of the Event Detail information shown on the Event Details page should be editable by this authorized MCA-N user. In addition, authorized MCA-N users should be able to flag whether a given event should have an automated event registration process. Not all events may have this feature.

Must Have

F1. Branding – This Major function should be branded “Ongoing Mandatory reporting” Must Have

Page 55 of 85





F2. Compliance Score Card – The Mandatory reporting Home Page should provide the latest Compliance Score Card. A Compliance Score Card is created each year and lists Namibia’s compliance to 17 KPIs across three broad areas: • Ruling Justly • Investing in People • Economic Freedom As this is a critical element of mandatory reporting, these KPIs should be displayed within the Compliance Score Card page and not simply be attached as a .pdf document. The layout should incorporate the three broad areas and make an attractive use of graphics. At the bottom of the page should be a link that enables users to view Compliance Score Cards from previous years. Namibia’s 2008 Compliance Score Card can be found here: http://www.mcc.gov/mcc/bm.doc/score-fy08-namibia.pdf

Must Have

F3. Mandatory reporting Postings Feed – The Mandatory reporting Home Page should provide an aggregation of all content postings across the Website that have been flagged with the Mandatory reporting Flag. These may include: • Amendments to the Compact (posted using functionality described in Major Function 4.2:

Background Information – Funding Timeline) • Programme Implementation Agreement & any amendments (posted by users with Public Relations

Access Rights using functionality described in Major Function 4.2: Background Information – Funding Timeline)

• Minutes of NCA-N Board Meetings (posted here) • Minutes of Stakeholders/ Consultative Committee meetings (posted here) • Monitoring & Evaluation Plans (posted here) • Environmental and Social Impact Assessments (posted by users with Project Management Access

Rights using functionality described in Major Function 1: Progress & Impact of Projects and Activities).

• Audit Reports and reports/ evaluations by external reviewers (posted here) • Disbursement requests, requesting funding from the MCC and outlining the results of the

expenditure from the last request (posted here) • Any other reports submitted to the MCC (posted here) • Legislation and other documents related to the formation, organization and governance of the

MCA-N (posted here) Only those postings that were flagged to be displayed in the Mandatory reporting Posting feed should be included. Summary information should be displayed for each item, taken from the content created

Must Have



Page 56 of 85





by MCA-N without the need for duplication. Users should be able to click on any summary and then be navigated to the full posting. Articles should not appear after they are no longer relevant. There should be a “See more” option for users to see the entire listing of articles including those that are no longer relevant.

F4. Content Detail - when a user has clicked on the summary information for any mandatory reporting item shown in the Mandatory reporting Postings Feed, the details of that posting should be displayed depending on the type of posting.

Must Have

F5. Maintain Compliance Score Cards - Provide users with MCA-N Public Relations Access Rights with the ability to create, edit and delete Compliance Score Cards. All of the Compliance Score Card information shown on the Mandatory reporting Home page should be editable by this authorized MCA-N user.

Should Have

F6. Maintain Compliance Postings - Provide users with MCA-N Public Relations Access Rights with the ability to create, edit and delete Compliance Postings. This may include the following: • Minutes of NCA-N Board Meetings • Minutes of Stakeholders/ Consultative Committee meetings • Monitoring & Evaluation Plans • Audit Reports and reports/ evaluations by external reviewers • Disbursement requests, requesting funding from the MCC and outlining the results of the

expenditure from the last request • Any other reports submitted to the MCC • Legislation and other documents related to the formation, organization and governance of the

MCA-N All of the information shown on the MCA-N Board Meeting Detail page should be editable by this authorized MCA-N user.

Must Have

G1. Branding – This Major function should be branded “About Us” Must Have G2. About MCC – this page should display background information regarding the Millennium Challenge

Corporation as well as a link to http://www.mcc.gov/ The actual content to be displayed will be agreed in the Detailed Requirements Workshops.

Must Have

G3. About MCA-N – this page should display background information regarding the Millennium Challenge Account – Namibia. This may include a graphical representation of the MCA-N Organization. This may have to be incorporated using Flash technology or something similar to display it attractively and legibly. The actual content to be displayed will be agreed in the Detailed Requirements Workshops.

Must Have

G4. About Namibia – this page should display relevant information about Namibia. This may also include links to relevant websites.

Must Have


Page 57 of 85





The actual content to be displayed will be agreed in the Detailed Requirements Workshops. G5. Although it is not expected that this information will be mainly static, users with MCA-N Public Relations

Access Rights should be able to maintain information displayed on each of these pages. Must Have

G6. Branding – This Major function should be branded “Funding Timeline” Must Have G7. Funding Timeline Overview – The Funding Timeline home page should display a graphical timeline

across the top of the page, highlighting the following milestones and tasks relating to the funding and implementation of the MCA-N compact:

Timeline/milestone Type Timing Namibia becomes eligible for MCC funding Milestone November 2005 Establishment of the formal structures to guide Programme development

Task November 2005 - April 2006

Development of the Programme Proposal Task May – September 2006 Round 1 of regional consultative meetings: Programme Proposal development

Milestone June 2006

MCA Namibia Programme Proposal is submitted to MCC

Milestone September 2006

Round 2 of regional consultative meetings: feedback on the final Programme Proposal


MCC Investment Committee approval of the Opportunity Memorandum

Milestone December 2006

MCC-led Due Diligence of the MCA Namibia Programme Proposal

Task February 2007 – May 2008

Final MCA Namibia – MCC negotiations of the MCA Namibia Compact

Milestone June 2008

Signing of the MCA Namibia Compact Milestone July 2008 MCA Namibia Management Unit Mobilisation

Task August 2008 – March 2009

Namibian Parliament Ratifies the MCA Namibia Compact


Round 3 of regional consultative meetings: feedback on the final MCA Namibia Compact Programme

Milestone February 2009

MCA Namibia Compact Implementation Funding

Task April – September 2009

MCA Namibia Compact Entry-Into-Force Milestone September 2009

Must Have

Page 58 of 85





MCA Namibia Programme Implementation Task September 2009 – September 2013

Users should be able to click on any Task or Milestone in the timeline and the bottom part of the page should display the relevant details (see below).

G8. Timeline Detail – One a task or timeline is clicked in the Funding Timline overview graphical diagram, the relevant detail should be displayed. The actual content to be displayed for each Task and Milestone will be agreed in the Detailed Requirements Workshops, however: • Content is likely to include text, images, attachments and links laid out in an attractive manner • MCA-N should be able to modify this content (see below)

Must Have

G9. Provide users with MCA-N Public Relations Access Rights with the ability to upload any amendments to the Compact to appear alongside the Compact under the timeline when selected.

Must Have

G10. Provide users with MCA-N Public Relations Access Rights with the ability to upload any amendments to the Programme Implementation Agreement to appear alongside the Programme Implementation Agreement under the timeline when selected

Must Have

G11. Provide uses with MCA-N Public Relations Access Rights to modify the content of any Milestone or Task which has a Timeline Detail.

Must Have

G12. Provide users with MCA-N Public Relations Access Rights to change Milestone and Task dates which should then be automatically reflected in the graphical Funding Timeline Overview

Should Have

G13. Provide users with MCA-N Public Relations Access Rights to add and delete Milestones and Tasks to the Funding Timeline Overview

Should Have

H1. Branding – This Major function should be branded “Procurement Opportunities” Must Have H2. Procurement Rules – The Procurement Opportunities Home Page should outline key procurement rules

as well as an overview of the procurement process and guidelines for selection. All information here should be displayed on the page but also made available for download in .pdf format for all users. There may be multiple documents or sections that describe the procurement rules. The actual content to be displayed will be agreed in the Detailed Requirements Workshops. Additionally, this section should include links to other relevant pages (such as MCC procurement pages).

Must Have

H3. General Procurement Notice – The Procurement Opportunities Home Page should outline the current active General Procurement Notice. The current active GPN should be automatically determined based on the GPN Start Date, GPN End Date and the current date. The following details should be displayed for the current active GPN: • GPN Start Date • GPN End Date • A list of all of the Procurements that have been created for this GPN. Each Procurement should

display a Status Link.

Must Have

Page 59 of 85





The Status Link for each procurement should be determined as follows: • Closed – where the Procurement has an end date that has passed, the displayed status should be

“closed” with no associated link. • Express Interest – where the Procurement has an end date that has not yet passed; but there is no

associated active Specific Procurement Notice (either because there is not going to be an SPN for this Procurement; or the SPN has not yet been created; or the SPN has been created, but the current date is not between the SPN start date and SPN end date), then the displayed status should be “Express Interest” with a link to the GPN Procurement Express Interest Page.

• More Information – where the Procurement has an end date that has not yet passed and it has an associated SPN that is currently active (because the current date is between the SPN start date and SPN end date), then the displayed status should be “More Information” with a link to the relevant Specific Procurement Notice Detail page.

H4. Website Registration required to access GPN Procurement Express Interest Page – Users will have to be registered with the MCA-N Website in order to express interest in a given Procurement. If the user is already logged into the website, then they would be immediately navigated to the GPN Procurement Express Interest Page. If the user is not logged in to the website, then they would be asked to provide login details (as they may have registered previously) or to register. Upon successful login or registration, they would be navigated to the GPN Procurement Express Interest Page.

Must Have

H5. GPN Procurement Express Interest Page – This page will be reached after a logged in user has clicked on an Express Interest link against a specific Procurement under the current active General Procurement Notice. This page will only have been made available if the given Procurement did not have an associated active SPN. On this page, all details relating to the procurement will be displayed: • Procurement Description • Procurement Start Date • Procurement End Date Additionally, the user will be able to click on a button to Express Interest in the given procurement, at which point a Record of their Expression of Interest will be made (see below).

Must Have

H6. Record of Expressed Interest – When a user clicks on an Express Interest Button within the GPN Procurement Express Interest Page, a record of this user will be stored against the Procurement.

Must Have

H7. Specific Procurement Notice Summary List – The Procurement Opportunities Home Page should provide a list of active Specific Procurement Notice’s that MCA-N are currently sourcing. SPNs are deemed active if the current date is between the SPN start date and SPN end date. Note that this may mean that SPNs are listed even if they “belong” to a Procurement that is in a previous General

Must Have

Page 60 of 85





Procurement Notice period. Summary information should be displayed for each active SPN including: • Procurement Code • Name of Procurement • Deadline for Bid Submission including Countdown to deadline • Date of Posting SPN summaries should be listed in order of SPN End Date (with the earliest end dates first). Users should be able to click on any SPN Summary and then be navigated to the Specific Procurement Notice Detail.

H8. Specific Procurement Notice Detail – The Specific Procurement Notice should provide full details of the procurement opportunity including: • SPN Procurement Code • Name of SPN • Name of associated Procurement • SPN End Date - Deadline for Bid Submission including Countdown to deadline • SPN Start Date – Date that the SPN became active • Description of SPN • Location of SPN • Anticipated Start Date • Anticipated Duration • Specific Procurement Qualification Requirements • Contact People The Specific Procurement Notice should provide a link to enable the user download any bidding documents such as an RFP or TOR. A sample Specific Procurement Notice can be found here: http://www.mcanamibia.org/docs/spn_6.5.18_09.07.04.pdf

Must Have

H9. Website Registration required to access bidding documents – Users will have to be registered with the MCA-N Website in order to bid for a procurement opportunity. If the user is already logged into the website, then they would be immediately navigated to the page where they can download the bidding documents. If the user is not logged in to the website, then they would be asked to provide login details (as they may have registered previously) or to register. Upon successful login or registration, they would be navigated to the page where they can download the bidding documents.

Must Have

H10. Download Bidding Documents – Registered users should be able to download the bidding documents for a given Specific Procurement Notice so long as all mandatory fields below are entered. The following fields should be captured from the user.

Must Have

http://www.mcanamibia.org/docs/spn_6.5.18_09.07.04.pdf�

Page 61 of 85






• Name of Company • If these details are already captured in the Website Registration process, then they should be

defaulted from there. • If these details are changed here, then the fields should be updated in the Website

Registration data for this user. • First Name, Last Name

• If these details are already captured in the Website Registration process, then they should be defaulted from there.

• If these details are changed here, then the fields should be updated in the Website Registration data for this user.

• Fax Number • If these details are already captured in the Website Registration process, then they should be

defaulted from there. • If these details are changed here, then the fields should be updated in the Website

Registration data for this user. Note that all fields are mandatory and the user would only be able to download the bidding documents when data is captured for all of them. Bidding documents may be in any of the following file formats: • .pdf • MS Office

H11. Confirmation of Access to Bidding Documents - Upon a user successfully downloading the bidding documents, the following emails should be generated by the MCA-N Website: • Email to all users with MCA-N Procurement Access Rights with the following details:

• Procurement Code • Name of Procurement • Deadline for Bid Submission including Countdown to deadline • IP address of Computer downloading bidding documents • Date & Time that bidding documents were downloaded • Email Address of user that downloaded bidding documents • Name of Company of user that downloaded bidding documents • First Name, Last Name of user that downloaded bidding documents • Fax Number of user that downloaded bidding documents

• Email to the user that downloaded the documents with:

Must Have

Page 62 of 85





• Confirmation that they have downloaded the Procurement Documents: • Procurement Code • Name of Procurement • Deadline for Bid Submission including Countdown to deadline • Name of documents downloaded • Date & Time that bidding documents were downloaded • Name of Company of user that downloaded bidding documents • First Name, Last Name of user that downloaded bidding documents • Fax Number of user that downloaded bidding documents

H12. Record of Access to Bidding Documents - When a user has accessed bidding documents, a record of this user will be stored against the SPN.

Must Have

H13. Notice of Awards Summary List – The Procurement Opportunities Home Page should display summary information for recent award of procurement contracts including: • Date when the award was made • Summary of the Award Users should be able to click on any Award and then be navigated to the full Award Detail. Notice of Awards should be listed in chronological order with the most recent awards at the top. Notice of Awards should not appear after they are no longer relevant. They will be no longer relevant after a configured period of time after they were first posted. There should be a “See more” option for users to see the entire listing of Awards including those that are no longer relevant.

Must Have

H14. Notice of Awards Detail – when a user has clicked on a link to view a notice of Award, the details of that Award should be displayed. The following information may be displayed for a Notice of Award: • Date when the award was made • Summary of the Award • Detailed Description of Award

Must Have

H15. Maintain General Procurement Notices - Provide users with MCA-N Procurement Access Rights with the ability to create, edit and delete General Procurement Notices. All of the information shown on the General Procurement Notice should be editable by this authorized MCA-N user. The MCA-N Website should prevent the user from entering GPN Start Dates and End Dates that overlap, and the GPN Start Date should always follow the day after the preceding GPN End Date, since at any one time there should always be one and only one active GPN.

Must Have

H16. Maintain Procurements – Provide users with MCA-N Procurement Access Rights with the ability to create, edit and delete Procurements under a given General Procurement Notice.

Must Have

Page 63 of 85





All of the information shown on the GPN Procurement Express Interest Page should be editable by this authorized MCA-N user.

H17. Maintain Specific Procurement Notices - Provide users with MCA-N Procurement Access Rights with the ability to create, edit and delete Specific Procurement Notices against a given Procurement. All of the information shown on the Specific Procurement Notices page should be editable by this authorized MCA-N user. The MCA-N Website should validate to ensure that SPNs are always created against Procurements. Note that SPNs can be created with an SPN Start date in the future, which will result on the SPN initially not being displayed in the SPN Summary List until the Start Date is reached.

Must Have

H18. Automated Outbound Updates to Express Interest Users – When an SPN becomes active, an automated email should be sent to all users that Expressed an Interest in the associated Procurement. The email should be blind copied to all MCA-N users with Procurement Access Rights and separate emails should be sent to all recipients as they should not be able to determine other user’s email addresses. The content of the email should contain the following information: • Reminder that they expressed an interest in a given Procurement • That the a Specific Procurement Notice associated with that Procurement has been published • A link to the SPN

Nice to Have

H19. Maintain Bidding Documents – Provide users with MCA-N Procurement Access Rights with the ability to add or delete bidding documents against a Specific Procurement Notice. These are the documents that registered end users would then be able to download.

Must Have

H20. Outbound Updates to Users who have downloaded Bidding Documents – If any changes are made to Specific Procurement Notices, or if additional Bidding Documents are added to an SPN, then an automated email should be sent to all users that downloaded Bidding Documents. The email should be blind copied to all MCA-N users with Procurement Access Rights and separate emails should be sent to all recipients as they should not be able to determine other user’s email addresses. The content of the email should contain the following information: • Notice that details of an SPN or bidding document have changed • A link to the SPN or bidding documents page that has changed.

Nice to Have

H21. Generate Report of Express Interest Users – A user with MCA-N Procurement Access Rights should be able to generate a report that lists the following for all users that expressed an interest in a given Procurement: • Email Address • Name of Company • First Name, Last Name

Must Have

Page 64 of 85





• Fax Number H22. Generate Report of Users who have downloaded Bidding Documents – A user with user with MCA-N

Procurement Access Rights should be able to generate a report that lists the following for all users that have downloaded bidding documents for a given SPN: • Email Address • Name of Company • First Name, Last Name • Fax Number

Must Have

H23. Maintain Notice of Awards – Provide users with MCA-N Procurement Access Rights with the ability to create, edit and delete Notice of Awards. All of the information shown on the Notice of Awards Detail Page should be editable by this authorized MCA-N user.

Must Have

I1. Branding – This Major function should be branded “Employment Opportunities” Must Have I2. Employment Opportunity Summary List – The Employment Opportunities Home Page should provide a

list of currently unfulfilled employment opportunities. Summary information should be displayed for each employment opportunity, including: • Job Title • Job Location • Deadline for Application including Countdown to deadline • Date of Posting Employment Opportunities should be listed in order of Date of Posting (with the most recent at the top). Users should be able to click on any Employment Opportunity and then be navigated to the Employment Opportunity Detail.

Must Have

I3. Employment Rules – The Employment Home Page should outline key employment rules as well as an overview of the employment process and guidelines for selection. The actual content to be displayed will be agreed in the Detailed Requirements Workshops.

Must Have

I4. Employment Opportunity Detail – The Employment Opportunity Detail should provide full details of the employment opportunity including: • Job Title • Job Location • Deadline for Application including Countdown to deadline • Unique Job Reference • Date of Posting • Job Description The Employment Opportunity Detail should provide a link to enable the user to apply for the

Must Have

Page 65 of 85





opportunity. I5. Website Registration required for Employment Opportunity Application – Users will have to be

registered with the MCA-N Website in order to enter an employment opportunity application. If the user is already logged into the website, then they would be immediately navigated to the Employment Opportunity Application. If the user is not logged in to the website, then they would be asked to provide login details (as they may have registered previously) or to register. Upon successful login or registration, they would be navigated to the Employment Opportunity Application without the need to click on the link again.

Must Have

I6. Employment Opportunity Application – Registered users should be able to apply for a given Employment Opportunity. The following fields should be captured from the user: • First Name, Last Name of Applicant

• If these details are already captured in the Website Registration process, then they should be defaulted from there.

• If these details are changed here, then the fields should be updated in the Website Registration data for this user.


• Telephone Number – this will be defaulted based on the email address captured in the Website Registration Process.

• Cover Note In addition, the registered user should be able to upload their resume in any of the following file formats: • .pdf • .doc (MS Word)

Must Have

I7. Routing of Employment Opportunity Application - Upon submission of a user’s employment opportunity application, the following emails should be generated by the MCA-N Website: • Email to all users with MCA-N Human Resources Access Rights with all details captured from the

user as well as the following Employment Opportunity details: • Job Title • Unique Job Reference

• Email to the user that submitted the employment opportunity application with • Confirmation that the application had been received by MCA-N and standard text regarding

turn-around time for a response • The details of the email sent to MCA-N Human Resources users (above)

Must Have

I8. Maintain Employment Opportunities - Provide users with MCA-N Human Resources Access Rights with the ability to create, edit and delete Employment Opportunities.

Must Have

Page 66 of 85





All of the Employment Opportunity information shown on the Employment Opportunity Detail page should be editable by this authorized MCA-N user. Additionally, authorized users should be able to flag when the Opportunity was closed. At this point, the Opportunity would no longer appear in the Employment Opportunity Summary List and users would not be able to apply.

J1. Availability – A link to this major function should be made available for selected Events where a user with MCA-N Public Relations Access Rights has indicated that a given event from Major Function 2 should have an automated Event Registration Process.

Should Have

J2. Website Registration required for Event Registration – Users will have to be registered with the MCA-N Website in order to register for an event. If the user is already logged into the website, then they would be immediately navigated to the Event Registration. If the user is not logged in to the website, then they would be asked to provide login details (as they may have registered previously) or to register. Upon successful login or registration, they would be navigated to the Event Registration without the need to click on the link again.

Should Have

J3. Event Registration – Registered users should be able to register for a given event. The following fields should be captured from the user: • Email Address – this will be defaulted based on the email address captured in the Website

Registration Process. • Contact Telephone Number • Position of Individual/ Type of Business for Company • Possibility to enter one or more Attendees with the following information:

• First Name, Last Name of Registrant

Should Have

J4. Routing of Event Registration - Upon submission of a user’s event registration, the following emails should be generated by the MCA-N Website: • Email to all users with MCA-N Public Relations Access Rights with all details captured from the user

as well as the following Event details: • Date/ Time of Event • Name of Event • Location of Event • Link to Event Details Posting

• Email to the user that submitted the event registration application with • Confirmation that the registration had been received by MCA-N and any standard text • The details of the email sent to MCA-N Public Relations users (above)

Should Have

K1. Browser Compatibility – All of the MCA-N Website functionality should be available to users on the following browsers/ versions:

Must Have

Page 67 of 85





• Internet Explorer version 6 and all subsequent major and minor versions • Firefox/ Mozilla version 3 and all subsequent major and minor versions • Safari version 3 and all subsequent major and minor versions • Google Chrome version 1 and all subsequent major and minor versions

K2. Hosting – The MCA-N Website may be hosted on the existing web server in Germany or elsewhere. MCA-N has a preference for the Website to be hosted in Namibia or Southern Africa, but this is not a mandatory requirement.

Must Have

K3. Upgradability – The site should be developed using techniques that allow for simple extensibility and upgradability of the site in the future. This should accommodate both increases in site volumes, addition or removal of site content as well as restructuring of the site map and navigation and addition of new functionality for new user types in the future.

Must Have

K4. Use of appropriate technologies – The site should utilize appropriate technologies to enhance the appeal of the site and achieve the desired dynamism. For example, it is expected that the site will make use of technology such as: • Adobe Shockwave/ Flash for graphical animations • Scripting technology such as PHP or ASP to generate web pages dynamically • Read only Adobe PDF files for the publication of reports, etc

Must Have

K5. File Formats supported – The site should allow MCA-N to upload files of any format for download by website users.

Must Have

K6. Appropriate use of graphic files – The use of graphical content has to be optimized to work over a range of end user bandwidth capabilities. As a rule of thumb, the site should still be usable assuming a 56k dial-up speed.

Must Have

K7. Backup and restore – it should be possible to back up and restore the MCA-N Website including all data held in databases and all content.

Should Have

IT1. Final Release – The final release which satisfies all of the requirements that MCA-N contract the Contracted Consultant to deliver should be delivered a successful internal System Test, ready for Acceptance Testing by MCA-N within 8 months from the start of the implementation project.

Must Have

IA1. Provide status updates to MCA-N’s Project Manager – The Contracted Consultant shall designate a Project Manager who is accountable for the delivery of the Phase 2 MCA-N Website in accordance to the agreed Implementation Schedule. This Project Manager shall meet regularly with MCA-N’s Project Manager and provide the necessary documents in accordance to MCA-N’s Project Charter. These documents shall be issued on a periodic basis as outlined in MCA-N’s Project Charter and include but not be limited to: • Implementation Plan (updated to show actual progress versus planned or baselined progress) • Status Reports • Issue Reports

Must Have

Page 68 of 85





• Change Management Reports IA2. Conduct Detailed Requirements Workshops – The Contracted Consultant meet with MCA-N and other

Tourism stakeholders in a number of Workshops to capture detailed requirements for the Phase 2 MCA-N Website. The Workshops should take place at MCA-N’s offices in Windhoek.

Must Have

IA3. Sign Off Detailed Requirements Specification – The Contracted Consultant should document all of the captured detailed requirements, organized in terms of each page or function of the Phase 2 MCA-N Website. This activity will be only be complete upon sign-off from the authorized MCA-N manager.

Must Have

IA4. Sign Off Conceptual Design/ Prototype – The Contracted Consultant should develop a design for the Phase 2 MCA-N Website and possible develop Prototypes within the first few weeks following Sign off Of Requirements. This activity will only be complete upon sign-off of the Conceptual Design or Prototype from the authorized MCA-N manager. Sign-off may require the Contracted Consultant to conduct a Design Review with MCA-N Staff.

Should Have

IA5. Complete Implementation – Once the Detailed Requirements and Conceptual Design and/ or any Prototypes have been signed off by MCA-N, the Contracted Consultant shall implement the Phase 2 MCA-N Website in accordance with these sign off documents.

Must Have

IA6. Complete Internal System Testing – Once the Phase 2 MCA-N Website has been implemented, the Contracted Consultant shall test the website internally before delivering the website to MCA-N for Acceptance Testing. This activity will only be complete and Acceptance Testing shall only commence when the Successful Bidder can confirm that: • All functionality proposed in the release is available • There are no defects that prevent functionality from being used • There are no defects that corrupt captured data held in databases The Phase 2 MCA-N Website should only be accessible to the Contracted Consultant staff and possibly some authorized MCA-N staff during Internal System Testing.

Must Have

IA7. Sign Off MCA-N Training – In parallel with Implementation and Internal System Testing and prior to the start of Acceptance Testing, the Contracted Consultant shall train up to 5 MCA-N and other stakeholder staff on the Content Management and other Administrator related functionality of the Phase 2 MCA-N Website. After execution of this training, MCA-N staff should be able to maintain the website content and execute other administrative functions such as generating reports, without the engagement of the Contracted Consultant or another vendor. This activity will be only be complete upon sign-off from the authorized MCA-N manager.

Must Have

IA8. Sign Off Acceptance Testing – Once the Phase 2 MCA-N Website has met the Internal System Test completion criteria and MCA-N Training has been signed off, the Contracted Consultant shall deliver the website to MCA-N for Acceptance Testing. The Contracted Consultant shall support MCA-N and other stakeholders as it tests the Phase 2 MCA-N Website. This may involve working alongside MCA-N and other stakeholders staff at MCA-N’s offices in Windhoek.

Must Have

Page 69 of 85





The Contracted Consultant shall resolve all defects identified by MCA-N during the Acceptance Testing activity. Acceptance Testing shall only be complete once signed off by MCA-N. The criteria for completion of Acceptance testing shall be outlined MCA-N’s project Charter. The Phase 2 MCA-N Website should only be accessible to the Contracted Consultant staff and authorized MCA-N staff during Acceptance Testing.

IA9. Cut-Over – Following sign off of Acceptance Testing, the Contracted Consultant shall cut-over the Phase 2 MCA-N Website into production and perform all of the necessary activities to ensure that the Phase 2 MCA-N Website replaces the existing Website and is accessible to all internet users worldwide.

Must Have

IA10. Maintenance Services – Following Cut-over, the Contracted Consultant shall resolve any defects in a timely manner as detailed in MCA-N’s Project Charter or the contract between MCA-N and the Contracted Consultant.

Must Have

Annex 5: Contract for Individual Consultants

MCA NAMIBIA

CONTRACT FOR INDIVIDUAL CONSULTANTS

[TITLE]

This contract for consultant services (the “Contract”) is signed on [ ] by the Chief Executive Officer of the Millennium Challenge Account Namibia ("MCA-N") acting on behalf of the Government of the Republic of Namibia whose address is:

Atlas House 6th Floor Corner of Mandume Ndemufayo and Sam Nuyoma Drive P.O. Box 23005 Windhoek Republic of Namibia Tel: +264 61 410 400

Fax: +264 61 410 415

and, [.........................] (the “Consultant”) whose address is:

[ ] Street, [ ] [ ] P.O. Box [ ] [ ] [ ] Tel: + [ ] [ ]

Fax: + [ ] [ ]

hereinafter collectively referred to as the “Parties”.

Section 1

APPOINTMENT; SERVICES; OBLIGATIONS

Section 1.1 Appointment of the Consultant

Section 1.2

Subject to the terms and conditions of this Contract, MCA-Namibia hereby appoints [………………………] (the “Consultant”) to provide Consultant Services as further set forth and explicitly authorized herein, and the Consultant hereby accepts such appointment and agrees to perform the Consultant Services (as defined in Section 1.2) in accordance with the terms of this Contract.

Description of Services

Develop Release 2 of the MCA-N website, including the following:

The Consultant shall provide the consulting services and tasks in accordance with the Terms of Reference contained in Appendix A, and summarized below (note: in case of conflict or difficulty in interpretation, the Terms of Reference prevails):

• Conceptualise the website architecture and design based on the specifications provided by MCA-N

• Design and develop the website code • Manage an extensive website prototype testing, repairing and evaluation programme • Manage the deployment of the final website draft and assist

Page 71 of 85

• Provide training to MCA-N staff involved in website administration

Section 1.3 Compliance with Namibian Laws and the MCC and MCA-N Compact, etc.T

Section 1.4

he Consultant shall comply with (a) applicable laws and regulations, (b) this Contract and the relevant provisions of the Compact between the Millennium Challenge Corporation (MCC) and MCA-N (the “Compact”), (c) guidance and procedures provided by MCA-Namibia from time to time, and (e) such other agreements and documents as the Parties may agree, which agreements and documents (including any amendments thereto) shall be delivered by MCA-Namibia to the Consultant.

a) Please note that as per the Compact Agreement, dated 28 July 2008, between the Government of the United States of America acting through MCC and the Government of the Republic of Namibia acting through MCA-N, the MCC Funding cannot be used for payment of any taxes, duties, and levies, including Value-Added Tax (VAT), Customs Duties and Excise Tax. To implement the above tax arrangement a Tax Agreement between MCC, the Government of the Republic of Namibia represented by the Ministry of Finance, and MCA-N is in place. The Tax Agreement provides detail procedures and responsibilities that MCA-N and suppliers/service providers will follow for supplying goods and services to MCA-N. A copy of the Tax Agreement is available at office of MCA-N. However, paragraph (b) below presents a summary of the procedures and responsibilities of MCA-N and the Consultant.

Taxes

b) When invoicing MCA-N for services subject to VAT, the Consultant shall separately include the net amount of the transaction and the properly calculated VAT amount in accordance with the VAT Code. At the time of invoice payment, the Consultant will receive the full payment including VAT. Subsequently, MCA-N will submit a refund claim to the Minister of Finance, no later than 10 days after the end of each calendar month to request refund of all value-added taxes paid by MCA-N during such month using Program Funding.

Section 1.5 Insurance and GuaranteesT

Section 1.6

he Consultant shall maintain, at all times during the Term, satisfactory insurance or guarantees with respect to the Consultant’s performance under this Contract.

Namibia and MCC shall have the right to use any information contained in any report or document delivered to or otherwise made available by the Consultant to MCA-N or MCC.

Right to use information

Section 1.7

MCA Namibia shall make available to the Consultant, for the purposes of performing the Services and free of any charge, the services, facilities and property described in Appendix B at the times and in the manner specified in Appendix B.

Services, Facilities and Property of MCA Namibia

Section 1.8

The Consultant shall not participate in the selection, award or administration of a contract, grant or other benefit or transaction financed in whole or in part (directly or indirectly) by MCC Funding in which (i) the Consultant, members of the Consultant’s immediate family or household or his or her business partners, or organizations controlled by or substantially involving the Consultant, has or have a financial interest, or (ii) the Consultant is negotiating or has any arrangement concerning prospective employment, unless the Consultant has first disclosed in writing to MCA-N and MCC the conflict of interest and, following such disclosure, MCA-N and MCC have agreed in writing to proceed notwithstanding such conflict. This shall not constrain MCA-N (with prior MCC approval) from commissioning the Consultant with the provision of additional services related to the

Conflict of interest

Page 72 of 85

implementation of the Compact in Namibia. The Consultant shall not solicit or accept or offer a third party or seek or be promised directly or indirectly for itself or for another person or entity any gift, gratuity, favor or benefit, other than items of de minimis value and otherwise consistent with such guidance as MCC may provide from time to time. The Consultant’s shall not engage in any activity which is, or gives the appearance of being, a conflict of interest.

Section 2

CONSULTANT GENERALLY

Section 1.9 Standard of CareT

Section 1.10

he Consultant shall exercise all skill, reasonable care, prudence and diligence in the discharge of its duties and obligations under this Contract, as would be expected from a skilled and experienced Consultant. The Consultant shall carry out all Consulting Services in a timely and cost-effective manner and in conformity with professionally sound technical and management practices requisite for successful provision of the Consulting Services.

a) The fees and re-imbursements (the “Fees”), as agreed upon between the Consultant and MCA-N, as reflected in Appendix C, shall be full compensation for the services to be provided by the Consultant pursuant to this Contract; and

Fees

b) MCA-N shall be responsible for payment of such Fees in the amounts, on the dates and in the manner as designated in Annexure C; provided, however, that the Consultant has submitted invoices for such Fees, which invoices are subject to the approval of MCA-Namibia. The Consultant shall not be entitled to any other compensation, costs, expenses or payment (including payment or reimbursement for third-party costs and expenses) in respect of the Consulting Services or this Contract.

c) In the event MCA-N disputes any invoice for Fees submitted by the Consultant for any reason, including the Consultant’s failure to comply with the terms and conditions of this Contract (including the proper provision of the Consulting Services), MCA-Namibia MCA-N may delay or refuse payment of all or any portion of any such invoice without any penalty pending resolution of the dispute in accordance with Section 4.8. Following resolution of any such dispute, MCA-Namibia shall be obligated to pay only that portion of the invoice found to be valid.

d) Notwithstanding anything to the contrary in this Contract, no payment shall be made to the Consultant in violation of Section 2.6 of the Compact.

Section 1.11

a) The Consultant shall provide the Consulting Services to MCA-Namibia with the expectation that the following requirements are met:

Other Duties, Rights and Protections of the Consultant

(i) cooperation of MCA-N’s employees, representatives and/or advisors with the Consultant;

(ii) timely provision by MCA-N of any and all information (such information shall be, to the knowledge of MCA-N, true and accurate in all material respects), including documentation and comprehensive explanations, reasonably requested by the Consultant in connection with the Consulting Services; and

(iii) MCA-N timely making and implementing decisions, obtaining required approvals and issuing required documentation to enable the Consultant to proceed with the Consulting Services; provided, however, that the Consultant provides MCA-N with reasonable advance notice of decisions required.

Page 73 of 85

b) If at any time the Consultant is served with any judicial or administrative order, judgment, decree, writ or other form of judicial or administrative process (an “Action”) that in any way affects this Contract or the transactions contemplated herein, the Consultant shall, within two business days after such service, give notice and a copy of such Action to MCC and MCA-Namibia, and within five business days after such service, provide MCC and MCA-N with an explanation and a description of the proposed corrective measures to be taken with respect thereto.

c) To the extent that any amounts hereunder are duly owed and outstanding to the Consultant, MCA-N shall be solely liable to pay those amounts, subject to Section 2.4 of this Contract. For the avoidance of doubt, MCC shall have no responsibility or obligation to the Consultant for the payment of any fees, costs, indemnification expenses or any other expenses pursuant to this Contract or otherwise.

Section 1.12

a) The Consultant shall indemnify, defend and hold harmless each of MCA-N and MCC from and against any and all claims, arising from or in connection with the gross negligence, bad faith, willful or intentional misconduct of the Consultant, or a breach of this Contract by the Consultant, except if and to the extent that any such MCA-N Losses are attributable to the gross negligence or the willful misconduct of MCA-N.

Liabilities; Indemnification

b) MCA-N shall indemnify, defend and hold harmless the Consultant from and against any and all claims, losses, actions, liabilities, costs, damages or expenses, including reasonable attorneys’ fees and expenses arising from or in connection with the gross negligence, bad faith, willful or intentional misconduct of MCA-N, or a breach of this Contract by MCA-N, except if and to the extent that any such Consultant Losses are attributable to the gross negligence or the willful misconduct of the Consultant.

Section 3

TERM; SUSPENSION; TERMINATION

Section 1.13 TermT

Section 1.14

his Contract shall be effective as of [ ] (the “Effective Date”) and shall terminate on [ ] unless terminated earlier in accordance with Section 3.3.

a) MCA-N may suspend this Contract Services, Facilities and Property of MCA Namibia, in whole or in part, upon delivery of notice to the Consultant.

Suspension

b) Upon receipt of a notice of suspension pursuant to this Section 3.2, the Consultant shall suspend all Consulting Services, except as otherwise stated in the notice of suspension. Such activity and Consulting Services shall remain suspended until the suspension is lifted by instruction from MCA–N.

Section 1.15

a) If MCA-N defaults in the observance or performance of any of its material obligations under this Contract and such default remains unresolved thirty (30) days after notice of such default is delivered by the Consultant, the Consultant may terminate this Contract by thirty (30) days’ prior notice to MCA-N

Termination of this Contract

b) MCA-Namibia may terminate this Contract, at any time:

(i) with cause, upon notice to the Consultant; or

Page 74 of 85

(ii) without cause, by giving notice to the Consultant thirty (30) days prior to the effective date of such termination.

For purposes of Section 3.3(b)(i), “cause” shall include: (1) any material breach or material default by the Consultant of any provision of this Contract (including breach of any representation or warranty); (2) the negligence, bad faith or willful misconduct of the Consultant; (3) the insolvency, bankruptcy or liquidation of the Consultant, or the appointment of a receiver or administrator to manage the affairs of the Consultant; or (4) if MCC determines (in its sole discretion) that the Consultant is engaged in activities that are contrary to the national security interests of the United States or other acts or omissions that may be grounds for suspension or termination under Section 5.1(b) of the Compact.

c) The Consultant may terminate this Contract, at its election:

(i) in the event that a suspension pursuant to Section 3.2 extends for more than thirty (30) days, by giving written notice to MCA-Namibia and MCC at least thirty (30) days prior to the effective date of such termination; provided, however, that during the thirty day notification period, the Consultant may withdraw its notice of termination; or

(ii) at the end of the Term or any applicable renewal period, without cause, by giving written notice to MCA-Namibia and MCC at least thirty (30) days prior to the effective date of such termination (with such notice stating that the termination is without cause).

Section 1.16

a) If the termination of this Contract is pursuant to Section 3.3(b)(i), MCA-N shall pay to the Consultant the Fees as set forth in Appendix 2 for the Consulting Services rendered up to the date of the event constituting cause for such termination, and MCA-N shall have no obligation to pay any Fees that accrue following such date. The amount of such Fees shall be calculated on a pro rata basis to the extent applicable. MCA-N shall be entitled to claim damages for any loss or damage resulting from the event constituting cause for such termination, and MCA-N may (i) deduct such damages from the Consultant’s remuneration and (ii) act in accordance with the rights set forth in Section 2.2(b).

Consequence of Termination

b) If the termination of this Contract is pursuant to Section 3.3(a), 3.3(b)(ii) or 3.3(c), the Consultant shall be entitled to receive those Fees incurred prior to the effective date of the termination and, in the event of a termination pursuant to Section 3.3(b)(ii), the Consultant shall be entitled to receive such reasonable unavoidable third-party expenses incurred by the Consultant prior to such effective date of termination (“Administrative Expenses”); provided, however, that the Consultant shall seek to cancel such obligations and mitigate all such Administrative Expenses.

c) Upon any termination of this Contract, the Consultant shall ensure the orderly and timely transfer of all records, documents, data and information (together with all electronic and digital copies thereof) to MCA-N or such agent or representative designated by MCA-N (with MCC approval) or MCC, and the Consultant shall take any other actions reasonably requested by MCA-N or MCC to ensure the proper transition of any Consulting Services, if applicable.

Section 1.17

a) For purposes of this Section 3.5, an “event of force majeure” means the occurrence of any event that prevents either Party from performing any or all of its obligations pursuant to this Contract, which event arises from or is attributable to acts, events, omissions or accidents beyond

Force Majeure.

Page 75 of 85

the reasonable control of such Party, such as acts of God, war, riot, civil commotion, armed conflict or terrorist attack, accidental or malicious damage, fire, flood or storm.

b) If, due to an event of force majeure, either Party is unable to perform any of its obligations set forth herein, such failure to perform shall not constitute a default pursuant to this Contract during the continuation of such event, and for such time after such event of force majeure ceases as is absolutely necessary for such Party, using all reasonable endeavors, to recommence and perform its obligations; provided, however, that such Party: (i) shall as soon as possible serve notice in writing to the other Party specifying the nature and extent of the circumstances giving rise to the event of force majeure; (ii) shall take all reasonable steps to avoid such prevention or delay due to such event of force majeure; and shall use all reasonable endeavors to recommence and perform its obligations as quickly as possible following the occurrence of such event of force majeure; (iii) shall mitigate any expenses, losses or damages resulting from the event of force majeure; and (iv) shall give reasonable notice in writing to the other Party of the termination of the event of force majeure. The corresponding obligations of the other Party will be suspended to the same extent.

c) Any dispute regarding this Section 3.5 shall be resolved in accordance with the dispute resolution provisions set forth in Section 4.8.

Section 4

MISCELLANEOUS

Section 1.18 Representations and Warranties of the ConsultantT

a) he is duly formed, validly existing and in good standing under the laws of Namibia, and has all requisite power and authority to execute and deliver this Contract, to consummate the transactions contemplated hereby and to perform its obligations hereunder;

he Consultant hereby represents and warrants to MCA-N that, as of the Effective Date:

b) he has duly authorized, executed and delivered this Contract;

c) this Contract constitutes a valid and legally binding obligation of the Consultant, enforceable against it in accordance with its terms, except as such enforceability may be limited by applicable bankruptcy, insolvency, moratorium, reorganization or other similar laws affecting the enforcement of creditors’ rights and subject to general equitable principles;

d) neither the execution and delivery of this Contract, nor the performance by the Consultant of his obligations hereunder will, with or without the giving of notice or the passage of time or both: (i) violate any provision of applicable laws or regulations; (ii) violate the provisions of its organizational documents; (iii) violate any judgment, decree, order or award of any court or governmental authority applicable to him; or (iv) conflict with or result in the breach or termination of any term or provision of, or constitute a default under, any instrument or agreement to which he is a party or by which he or any of his assets is bound;

e) no consents or approvals of any other person or organization are required in connection with the execution and delivery of this Contract or the performance by him of his obligations under this Contract;

f) no petition, notice or order has been presented, no order has been made and no resolution has been passed for his bankruptcy, liquidation, winding-up or dissolution; no receiver, trustee, custodian or similar fiduciary has been appointed over the whole or any part of his income or assets, nor does he have any plan or intention of, nor has he received any notice that any other person has any plan or intention of, filing, making or obtaining any such petition, notice, order or resolution or of seeking the appointment of a receiver, trustee, custodian or similar fiduciary;

Page 76 of 85

g) no payments have been made or caused to be made by the Consultant to MCA-N or any third party, including any government official, in connection with this Contract or the Program in violation of the United States Foreign Corrupt Practices Act of 1977, as amended (15 USC 78a et seq.) (“FCPA”) or that otherwise would have been in violation of the FCPA if the party making such payments was a United States person or entity; and no payments have been made, or caused to be made, by the Consultant to any third party in connection with this Contract in violation of any applicable laws or regulations of Namibia relating to anti-bribery and corruption;

h) the information contained in the Consultant’s proposal (dated [ ]) and any agreement, report, statement, communication, or document otherwise delivered or otherwise communicated to MCA-Namibia or its agents or representatives or to MCC or its agents or representatives by or on behalf of the Consultant in connection with this Contract (i) is true, accurate and complete in all material respects and (ii) does not omit any fact known to the Consultant that if disclosed would (A) alter in any material respect the information delivered, (B) would likely have a material adverse effect on the Consultant’s ability to effectively provide, or ensure the effective provision of, the services contemplated by this Contract or to otherwise carry out his responsibilities or obligations under this Contract, or (C) have likely adversely affected MCA-Namibia’s determination to enter into this Contract; and

i) the Consultant is not (i) blacklisted from participation in procurements funded by The World Bank, (ii) debarred or suspended from participation in procurements funded by the United States Government, or (iii) otherwise prohibited from receiving assistance by applicable United States law or executive order or United States policies including under any then-existing anti-terrorist laws or policies.

Section 1.19 ConfidentialityE

b) Notwithstanding Section 4.2(a), in the event that either Party is required to disclose any Confidential Information (i) in connection with any judicial or administrative proceedings or (ii) in order, in the reasonable opinion of counsel to the disclosing Party, to avoid violating applicable laws, the disclosing Party will in advance of such disclosure provide the other Party with prompt notice of such requirement(s). Each Party also agrees, to the extent legally permissible, to provide the other Party, in advance of any such disclosure, with copies of any Confidential Information it intends to disclose (and, if applicable, the text of the disclosure language itself) and to cooperate with the other Party to the extent such other Party may reasonably seek to prevent or otherwise limit such disclosure.

ach Party and its directors, officers, employees, agents, advisors and representatives shall hold, and shall use commercially reasonable efforts to cause its Affiliates to hold, in strict confidence from any person (other than any such Affiliate or the other Party) all documents, reports, cost estimates, technical and other data and other information pertaining to this Contract, the transactions contemplated hereby or the Program, including the procurement process, that are not otherwise publicly available (“Confidential Information”); provided, however, that all Confidential Information shall be provided to MCC and may be provided by MCC to any employees, contractors, agents, representatives of MCC, an authorized United States government inspector general, the General Accountability Office, or others designated by MCC; provided, further, that each of MCC and MCA-N may post on its respective website or otherwise make publicly available certain information, including the Program Implementation Contract, the MCA-N Procurement Rules, the Procurement Plan, and any procurement-related documents, in accordance with the Compact, the Program Implementation Agreement or any Supplemental Agreement. The Consultant shall ensure that only those with a need to know and under similar obligations of confidentiality shall have access to any and all Confidential Information provided to the Consultant or otherwise generated in connection with this Contract and the Program.

Page 77 of 85

Section 1.20 Prohibition on Set-OffT

Section 1.21

he Consultant waives any and all rights of set-off, combination of accounts or counterclaim or any other right whatsoever it may have or hereafter acquire to apply amounts outstanding hereunder in discharge or satisfaction of any cost, right of reimbursement, expense, loss or other liability of the Consultant, and all such rights are hereby released by the Consultant. All payments made by the Consultant under this Contract shall be made without any deduction, withholding, set-off or counterclaim of any kind.

CommunicationsAny notice, certificate, request, report, approval, document or other communication required, permitted, or submitted by either Party to the other under this Contract shall be (a) in writing, (b) in English, and (c) deemed duly given: (i) upon personal delivery to the Party (or MCC, as applicable) to be notified; (ii) when sent by confirmed facsimile or electronic mail, if sent during normal business hours of the recipient Party (or MCC, as applicable), if not, then on the next business day; or (iii) three (3) business days after deposit with an internationally recognized overnight courier, specifying next day delivery with written verification of receipt, to the Party (or MCC, as applicable) to be notified at the address indicated below, or at such other address as such Party (or MCC, as applicable) may designate by notice to the other Party (and MCC):

To the Consultant

[ ]

:

[ ] [ ] [ ] Attention: [ ] Facsimile: [ ] Email: [ ]

To MCA-Namibia

Millennium Challenge Account Namibia

:

Attention: Chief Executive Officer 117 Sam Nujoma Drive P.O Box 23005 Windhoek Namibia Attention: [ ] Facsimile: +264 (61) 410415 Email: [email protected]

To MCC

Millennium Challenge Corporation

:

Attention: Vice President, Compact Implementation (with a copy to the Vice President and General Counsel) 875 Fifteenth Street, N.W. Washington, D.C. 20005 United States of America Facsimile: +1 (202) 521-3700 Email: [email protected] (Vice President, Compact Implementation;

[email protected]

Whenever under the terms hereof the time for giving a notice or performing an act falls on a day that is not a business day, such time shall be extended to the next day that is a business day.

(Vice President and General Counsel)

Page 78 of 85

Section 1.22

a) This Contract shall be binding on and shall inure to the benefit of the Parties and their respective successors and permitted assignees, cessionaries and delegates.

Assignment

b) The Consultant may not assign, delegate, subcontract (except as provided for in Section 1.6 and approved by MCC) or otherwise transfer any of its rights or obligations under this Contract

c) MCA-N may not assign, delegate, subcontract or otherwise transfer any of its rights or obligations under this Contract.

Section 1.23 Governing LawT

Section 1.24

his Contract shall be governed by and construed in accordance with the laws and regulations of Namibia. In the event of a conflict between the MCA-Namibia Procurement Rules and applicable provisions of the Tender Board of Namibia Act, 1996 or any other public procurement laws or regulations of Namibia, the MCA-Namibia Procurement Rules shall prevail.

All disputes, controversies or claims arising out of or in connection with this Contract, or the breach, termination or invalidity thereof, that cannot be settled amicably by the Parties within thirty (30) days of notification of such dispute, controversy or claim, shall be finally settled by arbitration under the UNCITRAL rules of arbitration by a single Arbitrator agreed upon by the Parties. In the case of the Parties failing to agree on the appointment of an Arbitrator, an Arbitrator will be nominated by […………………………………] on request by either Party.

Dispute Resolution

Section 1.25 Ownership of DocumentsT

Section 1.26

he copyright in all reports and related data and documents prepared by the Consultant, or made available by the Consultant to MCA-N, under this Contract shall pass to MCA-N.

Relationship of the PartiesT

Section 1.27

his Contract does not create a joint venture, partnership, or other similar relationship between the Parties.

Amendment; WaiverT

Section 1.28

he Parties may amend this Contract by entering into a written amendment to this Contract signed by the Principal Representatives of the Parties; The Parties further agree that any waiver, permit, consent or approval of any kind or character on any Party’s part of any breach, default or noncompliance under this Contract or any waiver on such Party’s part of any provisions or conditions of this Contract must be in writing and shall be effective only to the extent specifically set forth in such writing.

Non-waiver of RemediesT

Section 1.29

he Parties agree that no delay or omission to exercise any right, power or remedy accruing to any Party, upon any breach, default or noncompliance by another Party under this Contract, shall impair any such right, power or remedy, nor shall it be construed to be a waiver of any such breach, default or noncompliance, or any acquiescence therein, or of any similar breach, default or noncompliance thereafter occurring. All remedies, either under this Contract, by law, or otherwise afforded to any Party, shall be cumulative and not alternative.

AttachmentsA

Section 1.30

ny exhibit, schedule or other attachment expressly attached hereto (together, the “Attachments”) is incorporated herein by reference and shall constitute an integral part of this Contract.

HeadingsT

Section 1.31

he Section and Subsection headings used in this Contract are included for convenience only and are not to be considered in construing or interpreting this Contract.

a) This Contract is for the exclusive benefit of the Parties and their respective permitted successors hereunder, and shall not be deemed to give, either express or implied, any legal or equitable right, remedy, or claim to any other entity or person whatsoever, with the exception of

MCC as Third Party Beneficiary; Reserved Rights

Page 79 of 85

MCC, which is hereby designated as third party beneficiary to this Contract and shall have all of the rights provided to or reserved for it throughout this Contract.

b) MCC is a U.S. Government corporation acting on behalf of the U.S. Government in the implementation of the Compact. As such, MCC has no liability under this Contract, the Compact, the Program Implementation Agreement or any other Supplemental Agreement, is immune from any action or proceeding arising under or relating to this Contract, the Compact, the Program Implementation Agreement or any other Supplemental Agreement and MCA-Namibia and the Consultant hereby waive and release all claims related to any such liability. In matters arising under or relating to the Compact or this Contract, MCC is not subject to the jurisdiction of the courts or any other body of Namibia or any other jurisdiction.

c) The Parties further agree that (i) MCC, in reserving any or all of its rights hereunder, has acted solely as a funding entity to assure the proper use of United States Government funds, and any decision by MCC to exercise or refrain from exercising any of its rights shall be made as a funding entity in the course of funding the activity and shall not be construed as making MCC a party to this Contract; (ii) MCC may, from time to time, exercise its rights, or discuss matters related to these rights or this Contract with the Parties jointly or separately, without thereby incurring any responsibility or liability to the Parties jointly or separately; (iii) any approval (or failure to approve) or exercise of (or failure to exercise) any rights by MCC shall not bar MCA-N or MCC from asserting any right, or relieve the Consultant of any liability which the Consultant might otherwise have to MCA-N or MCC (or MCC Indemnified Parties); and (iv) MCC shall have the right, as set forth in this Contract, to receive copies of reports and other documentation delivered to the Consultant, MCA-Namibia or any other governmental body or person.

d) For the benefit of MCC, the Consultant shall comply with all of the terms of and its obligations under this Contract.

e) For the avoidance of doubt, MCC shall incur no obligations or liabilities under this Contract, whether as a result of its third-party beneficiary status or otherwise. In no event shall anything in this Contract be construed as a waiver of immunity from, or submission by MCC to, the jurisdiction of the courts of Namibia or of any other jurisdiction, or to any other body, or to the arbitral body or any arbitration under Section 4.8.

f) Notwithstanding Section 4.11 of this Contract, the Parties hereby agree that the designation of MCC as third party beneficiary to this Contract is and shall remain irrevocable, and the Parties further agree that no action is or shall be required by MCC to evidence its acceptance of such designation.

g) The Consultant acknowledges and agrees to all of the rights provided to or reserved for MCC throughout this Contract. Further, in the event that any of MCC’s rights under this Contract are not enforceable by MCC in any jurisdiction or are otherwise invalid for any reason, the Consultant agrees to the fullest extent permitted by law that such rights are hereby granted to MCA-N and hereby further agrees and consents to the fullest extent permitted by law to the assignment of those rights by MCA-N to MCC.

Page 80 of 85

Section 1.32 SeverabilityI

Section 1.33

f one or more provisions of this Contract is held to be unenforceable under any applicable law, such provision(s) shall be excluded from this Contract and the balance of this Contract shall be interpreted as if such provision(s) were so excluded and shall be enforceable in accordance with its terms.

Entire AgreementT

Section 1.34

his Contract, including all Attachments, and all certificates, documents or agreements executed and delivered in connection with and in furtherance of this Contract, when executed and delivered, shall constitute the entire agreement of the Parties with respect to the subject matter hereof, superseding and extinguishing all prior agreements, understandings and representations and warranties relating to the subject matter hereof.

Counterparts; SignaturesT

Section 1.35

his Contract may be executed in one or more counterpart signatures, and each counterpart when so executed and delivered shall be an original instrument, but such counterparts together shall constitute a single agreement. Except as the Parties may otherwise agree in writing from time to time, a signature delivered by facsimile or electronic mail in accordance with Section 4.4 shall be deemed an original signature, and the Parties hereby waive any objection to such signature or to the validity of the underlying agreement on the basis of the signature’s legal effect, validity or enforceability solely because it is in facsimile or electronic form. Such signature shall be accepted by the receiving Party as an original signature and shall be binding on the Party delivering such signature.

Waiver of ImmunityE

Section 1.36

ach Party, as to itself and its assets, hereby irrevocably and unconditionally waives any right of immunity (sovereign or otherwise) and agrees not to claim or assert any immunity with respect to the matters covered by this Contract or any arbitration, suit or action with respect to this Contract, whether arising by statute or otherwise, which it may have or may subsequently acquire, including rights under the doctrines of sovereign immunity and act of state, immunity from legal process (including service of process or notice, pre-judgment or pre-award attachment, attachment in aid of execution, or otherwise), immunity from jurisdiction or judgment of any court, arbitrator or tribunal (including any objection or claim on the basis of inconvenient forum), and immunity from enforcement or execution of any award or judgment or any other remedy.

DefinitionsA

Section 1.37

ll capitalized terms used and defined herein shall have the meaning given such terms in this Contract.

Rules of ConstructionT

a) words importing the singular also include the plural and vice versa;

he following rules of construction shall be followed when interpreting this Contract:

b) references to natural persons or parties include firms or any other entity having legal capacity;

c) words importing one gender include the other gender;

d) the words “include,” “including,” and variants thereof mean “includes, but not limited to” and corresponding variant expressions;

e) except as otherwise set forth herein, all references contained herein to contracts, agreements, or other documents shall be deemed to mean such contracts, agreements or documents, as the same may be modified, supplemented, or amended from time to time;

f) each reference to any law shall be construed as a reference to such law as it may have been, or may from time to time be, amended, replaced, extended or re-enacted and shall include any subordinate legislation, rule or regulation promulgated under any such law and all protocols, codes, proclamations and ordinances issued or otherwise applicable under any such law;

Page 81 of 85

g) the terms “hereof,” “herein,” “hereto,” “hereunder” and words of similar or like import, refer to this entire Contract and not any one particular Article, Section, Schedule, or other subdivision of this Contract;

h) except as otherwise expressly specified herein, any reference to an Article, Section, clause, Exhibit or Schedule shall mean an Article, Section, clause, Exhibit or Schedule of this Contract;

i) all references to notices, permits, licenses, consents, requests, instructions, approvals, and authorizations and any equivalent actions hereunder shall mean written notices, permits, licenses, consents, requests, instructions, approvals, and authorizations in accordance with Section 4.22;

j) any reference to “business days” shall mean any day other than a Saturday, Sunday, commercial banking holiday in Windhoek, Namibia or Washington, D.C., United States of America, or a national holiday in Namibia or the United States of America, and any reference to “day” shall mean a calendar day; and

k) any reference to “month,” “quarter” or “year” shall have the common meaning given such terms based on a Gregorian calendar year beginning on January 1 and ending on December 31 and divided into four approximately equal quarters beginning on each January 1, April 1, July 1 and October 1 of each such respective calendar year.

Section 1.38 Written Consents, Approvals and NoticesN

Section 1.39

otices, permits, consents, licenses, approvals, requests, instructions and authorizations, and any equivalent actions, to be provided or made hereunder shall only be effective if done in writing.

Language

This Contract is prepared and executed in English. In the event of any ambiguity or conflict between this official English version and any other version translated into any language for the convenience of the Parties, this official English language version shall prevail.

[SIGNATURE PAGE FOLLOWS ON NEXT PAGE]

Page 82 of 85

IN WITNESS WHEREOF, each of the Parties has caused this Contract to be executed by a duly authorized representative as of the day and year first written above.

MILLENNIUM CHALLENGE ACCOUNT-NAMIBIA

By: ________________________________________

Name: Mrs. Penny Akwenye

Title: Chief Executive Officer

Witness ________________________________________

THE CONULTANT

By: ________________________________________

Name:

Title:

Witness ________________________________________

Page 83 of 85

Appendix A

TERMS OF REFERENCE

[Terms of Reference to be inserted here]

Page 84 of 85

Appendix B

SERVICES, FACILITIES AND PROPERTY TO BE PROVIDED BY MCA NAMIBIA

[To be agreed between the Consultant and MCA-Namibia]

Page 85 of 85

Appendix C

FEES

[Equal monthly Instalments of the total negotiated fixed lump sum fee for the assignment]