(ToR)-Recruitment of a contractor to deliver and implement a Smart Parking Management solution in the City of Kigali (Rwanda)

Posted in

Smart Africa secretariat

Company Website

//www.smartafrica.org

Company Email

procurement@smartafrica.org

Type

Consultancy

Location

Rwanda

Last Date of Application

31 January 2022

Description :

TERMS OF REFERENCE

Recruitment of a contractor to deliver and implement a Smart Parking Management solution in the City of Kigali (Rwanda)

Client Address

Smart Africa Secretariat

9th Floor, Bloc C, Makuza Peace Plaza,

10 KN4 Avenue, Kigali, Rwanda

+250 788-300-581/ 784013646

PO Box: 4913 info@smartafrica.org www.smartafrica.org

RFP#:

057/S.A./RFP/RFP/12/2021

Release date:

December 31st 2021

Closing date:

January 31st, 2022, at 5:00 pm (Local time, Kigali)

 

Contact

For any questions or enquiries, please write to:

tenderenquiries@smartafrica.org  

For Proposal Submissions:  procurement@smartafrica.org

1.ORGANISATION BACKGROUND

Smart Africa is a bold and innovative commitment from African Heads of State and Government to accelerate sustainable socio-economic development on the continent, ushering Africa into a knowledge economy through affordable access to Broadband and usage of Information and Communications Technologies.

The Transform Africa Summit held in Kigali, Rwanda on 28th-31st October 2013 culminated in the adoption of the Smart Africa Manifesto document by seven (7) African Heads of States (Rwanda, Kenya, Uganda, South Sudan, Mali, Gabon, Burkina Faso) in which they committed to provide leadership in accelerating socio-economic development through ICT’s.

On 30th-31st January 2014, The Smart Africa Manifesto was endorsed by all Heads of State and Government of the African Union at the 22nd Ordinary Session of the Assembly of the African Union in Addis Ababa. This development places the Manifesto at the heart of the ICT agenda in Africa beyond just the 7 original signatories at the Summit to all African countries.

The Smart Africa Alliance has since grown to include 33 African countries that represent 800+ million people.

The Smart Africa Manifesto aims to put ICT at the Center of National Socio-economic development agenda of member countries; improve access to ICT especially Broadband; to improve accountability, efficiency, and openness through ICT promoting the introduction of advanced technologies in telecommunication; to put the Private Sector first, and to leverage ICT to promote sustainable development.

2. PROJECT BACKGROUND

The urbanization rate of the African continent has increased from 15% to 40% between 1960 and 2010[1], and is expected to reach 60% in 2050. The urban population in Africa will triple over the next 50 years.

This is an unprecedented demographic boom that is accompanied by an increase in challenges for governments in terms of housing, food, access to water, transport, waste management, and energy supply. Africa must take advantage of this rapid growth of urban citizens to overcome its difficulties through better management of its cities.

Faced with these challenges of sustainable development and controlled urban growth, African countries are considering the most effective solutions adapted to the realities of the continent.

One of the major challenges of increased urbanization is vehicle parking management and environmental protection. Effective and sustainable parking management is still a daunting exercise for the City of Kigali (CoK) that affects not only the environment but also economic and social factors such as livelihood, municipal planning, and budgeting. Smart parking solutions are needed to enhance regulated parking spots with occupancy sensors that provide additional features & services to parking management authorities as well as drivers by reducing time spent looking for parking, traffic congestion, and CO2 emissions.

With the growth of the vehicles on the streets, availability of parking space has become a major problem.  The major factors driving this growth are concerns over increasing urban traffic congestion, limited availability of parking spaces, and stricter regulations on emissions. The fact that several cities worldwide recognize the importance of efficient parking management is a sign of a critical need for a solution.

Similar to other cities worldwide, the number of motor vehicles in the CoK has significantly increased. Hence availability of parking space has consistently become a challenge with considerable negative impact on the quality of life of the city residents and visitors.

3.RFP OBJECTIVES

The overall objective for the contract is to implement a pilot project for a Smart parking management solution in the City of Kigali. The project aims to be implemented at the following roads within different selected parts of the CoK as listed in section 6. The needed solutions have to consider local context and preserve current jobs but aim to optimize existing resources where needed.

The specific objectives are:

  1. Design, Build and deliver a smart parking solution with the following features/specifications:

a. On-street parking management system:

  • Single slot detection system
  • Payment device and means

b.Parking guidance system:

  • On-street parking –variable messenger signs

c.Web portal, USSD, and Mobile App for drivers:

  • Parking identification, cashless payment (, mobile money, etc.), and navigation

d. Control and command center:

  • Setup and configuration of smart parking management control and command center at CoK premises
  • Integration with one third party system
  • Data management, analytics, and business intelligence on real-time
  • Monitoring of real-time transactions, parking availability
  • Management of equipment, status, and alarms on a real-time basis Dashboards and reports

2. Implement  the solution for 430-500 parking spots or more on the following roads (more details in section 6):

a. Junction (KN2 st, KN76 St), to Junction (KN2 st, KN82 St)
b. Junction (KN82 St, KN86 St) to Junction (KN82 St, KN57 St)
c. KG11 Ave to junction (KG11Ave, KG113 St)
d. Junction (KG194 st, KG153 st) to Junction (KG153 St, KK15Ave)
e. Junction (KN4 Ave, K76 st) to Junction (KN76 St, KN2 St)
f. Junction (KN 76 St, KN84 St) to Junction ( KN84 St, KN74 St)
g. Junction ( KN74 St, KN84 St) to Junction KN74 st, KN59 St)

3. Implement a centralized dashboard located at city of Kigali and that covers the smart parking solution and assets.

4. Provide a 1 year of maintenance, support, and knowledge transfer for delivered smart parking management system as a warranty.

In addition to the implementation work, the contractor firm should provide training and knowledge transfer to the designated GoR staff that will be in charge of future operation, maintenance and upgrades. This training should cover all phases of the system development lifecycle (from design through development and testing) and should be delivered as classroom sessions and as hands-on co-creation sessions. The training should cover at least 15 business onsite days.

4. METHODOLOGY AND APPROACH

The mission will be carried out by the contractor in collaboration with the Smart Africa Secretariat (SAS), Rwanda Ministry of ICT and Innovation (MINICT), the City of Kigali (CoK), and Rwanda Information Society Agency (RISA). In addition, the methodological approach will consist of:

  • Ensure that the bid proposal package does not exceed 30 pages (excluding CVs, proofs of education, Recommendation/ certificate of completion letters, etc.)
  • Conduct a field visit and collect useful data to prepare the proposal
  • Meet with key contacts in government and other relevant institutions (If need be)
  • Prepare and submit a technical proposal that shows the design sketches of the proposed solution, an implementation plan that shows how the solution can be delivered within 12 weeks from the project kick-off.
  • Prepare the solution presentation that will be presented to the tender selection team as part of the bid process. Qualifying bidders will be invited to present their proposed solution to a technical team as part of the technical evaluation.
  • Submit a financial proposal that will be opened after satisfying the technical selection.
  • The selected bidder will commence implementation as soon as the contract is signed.
  • Provide a weekly project progress report.
  • Ensure all implementation activities respect local regulations and environmental protection regulations.
  • Ensure all objectives, and requirements are met.
  • Ensure all deliverables are delivered as per ToR.
  • Ensure the implementation plan is followed as proposed and inform relevant stakeholders if any change or adjustment is needed.
  • Ensure all proof of team’s education are submitted with the proposal

5. SMART PARKING SOLUTION REQUIREMENTS

Given that the project aims to set the standards that can be a baseline for other similar projects in the future, specific customer requirements are set and the contractor should aim to respect proposed requirements or propose justified alterations that are based on the field context.

The bidder must demonstrate how the solution’s technical architecture that is Sensor-based solution is designed taking into consideration the following aspects as guiding principles:

  1. Scalability: The architecture must support scalability to provide continuous growth to meet the growing demand of the city traffic. The system should also support vertical and horizontal scalability so that depending on changing requirements from time to time, the system may be scaled upwards. There must not be any system imposed restrictions on the upward scalability in number of field devices. Main technological components requiring scalability are Sensors, Storage, Bandwidth, Computing Performance (IT Infrastructure), and Software / Application performance.
  2. Availability: Components of the architecture must provide redundancy and ensure that there are no single points of failure in the key project components. Considering the high sensitivity of the system, design should be a manner resilient to technological sabotage. To take care of remote failure, the systems need to be configured to mask and recover with a minimum outage. The bidder shall make the provision for high availability for all the services of the system. The smart phone application, USSD, and the web portal must provide end-users interface with a Kinyarwanda option.
  3. Security: The architecture must adopt an end-to-end security model that protects data and the infrastructure from malicious attacks, theft, natural disasters, etc. Successful bidder must make provisions for security of field equipment as well as protection of the software system from hackers and other threats. Using Firewalls and Intrusion detection systems such attacks and theft should be controlled and well supported (and implemented) with the security policy. The virus and worms attacks should be well defended with Gateway level Anti-virus system, along with workstation level Anti-virus mechanism. There should also be an endeavor to make use of the SSL/VPN technologies to have secured communication between Applications and its end users. Furthermore, all the system logs should be properly stored & archived for future analysis and forensics whenever desired.

The following guidelines need to be observed for security:

  1. The system must be locally hosted
  2. The system must comply with the Law relating to the protection of personal data and privacy in Rwanda
  3. Build a complete audit trail of all activities and operations using log reports, so that errors in system – intentional or otherwise – can be traced and corrected.
  4. Access Controls must be provided to ensure that the system is not tampered with or modified by the system operators.
  5. Implement data security to allow for changes in technology and business needs

Manageability: Ease of configuration, ongoing health monitoring, and failure detection are vital to the goals of scalability, availability, and security and be able to match the growth of the environment.

Interoperability: The system should be designed to take inputs from other third-party systems as per situational requirements.

  1. Open Standards: System, network, and hardware equipment should be designed to use open standards and protocols to the extent possible without compromising on the security.

6. PROJECT LOCATION / SITES

Proposals that cover more parking spots will be given preference. As a pilot project, the focus will be the public parking spaces in the CoK, and the selected ones per district are:

City of Kigali

Location

Number of Spots

Address

Nyarugenge

350-380

  •  City market towards main roundabout: (Junction (KN2 st, KN76 St),  to the Junction ( KN2 st, KN82 St)
  • T2000 to City Market: (Junction (KN82 St, KN86 St) to Junction (KN82 St, KN57 St))
  • BK HQ to City Market: Junction (KN4 Ave, K76 st) to Junction (KN76 St, KN2 St)
  • Junction (KN 76 St, KN84 St) to Junction (KN84 St, KN74 St)
  • Junction (KN74 St, KN84 St) to Junction KN74 st, KN59 St)

Gisimenti

40-60

KG11 Ave to junction (KG11Ave, KG113 St)

Kimironko

40-60

Junction (KG194 st, KG153 st) to Junction (KG153 St, KK15Ave)

7.DURATION OF THE ASSIGNEMENT

The selected company must deliver the project within 14 weeks effective from contract signing date.

8.EXPECTED RESULTS

  1. An inception report is to be submitted two (2) weeks after the commencement of the assignment detailing but not limited to the project implementation plan, timeline, schedule, a detailed solution design, detailed roles, responsibilities, and activities of each party based on mutual agreement. As well, the following must be covered in the inception report:
  • Detailed Project Charter showcasing all planned project deliverables.
  • Detailed project work plan with timeframes, outlining what must be done to have a fully implemented solution with iterations, features, user stories, resources, and roadmap with specific, clear, and detailed milestones according to the iterations with their respective implementation, deployment timelines to ensure timely system delivery.
  • The chosen approach should support agile project management and usage of project management landscape (OpenProject, GitLab, etc).
  • Knowledge transfer (methodology and strategy) during the implementation period
  • Overall understanding of need of the CoK reflected in the proposal addressing the risks identified that may affect implementation and operations.
  • Business processes as per CoK requirements
  • Details on a well-developed and working system as per the customer’s & system requirements
  • Details on a complete release package of the solution, including the source code produced as part of customization or development.
  1. Documentation which should include but not limited to:
  • Functional specifications document (specification of all user stories and features) that will guide development work on the solution for the scenario in scope of the iteration.
  • Detailed data Model
  • Technical Specifications and Software Architecture with detailed diagrammatic drawings of the implemented system for the scenario in the scope of the iteration.
  • Detailed equipment inventory, products catalog, and information sheets (technical “data sheets” or “cut sheets”) for all hardware and software used in the delivery of the solution.
  • Smart parking management system requirements document
  • Business processes as per customer’s requirements
  • Licenses as per solution proposal (if any)
  • A detailed and documented operational manual for the system according to the scenario in scope of iteration
  • Build, deployment and configuration guides for each components of the solution according to scenario in scope of iteration
  • Training material (PowerPoints, webinars, etc.)
  • Training report for users and system administrators
  • Detailed design of the security system
  • Testing methodology, scenarios, and plan
  • requirements traceability matrix which shows, how the requirements were implemented
  • Design, elaborate and implement a knowledge transfer plan and methodology
  • Test reports
  1. Provide and ensure that 100% of all support requests are successfully met on time as per the SLA conditions as well as per the critical level of the request.
  2. Ensure that required reports are submitted on time and adjusted accordingly as per respective feedback received from all project stakeholders
  3. Produce a provisional detailed report at the completion of the implementation phase that includes all achieved milestones, challenges faced, and mitigation strategies used, and recommendation that can guide future similar assignments.
  4. 1 Year warranty, maintenance, and support.
  5. Produce a final detailed report at the completion of the warranty time that includes all achieved milestones, challenges faced, and mitigation strategies used and recommendation that can guide future similar assignments.
  6. Integration of Smart Parking Management with Third Party System
  • Implement dashboards and integration
  • Train users in usage of the extended system
  • Train admins in administration of the extended system
  1. Third-Party System Specifications

 A 3-tier digital architecture which is deployed using Open-source software, Elastic Full Stack/Logstash, and Dashboarding tool with embedded analytics. The three tier includes:

  • Data source layer
  • ETL and Data Storage layer
  • Visualization layer

9. DEVELOPMENT METHODOLOGY

The project management methodology uses the SCRUM approach as proven agile methodology. This methodology will be used for project management inside the overarching iterations. In collaboration with the project team (Composed by Key Stakeholders) the following main artefacts/roles will be used if applicable.

9.1. Sprint

Each sprint is a time boxed development phase which will be used to deliver ready-to-use products. The intention is, to add small features and user stories in each sprint to deliver an incrementally improved product. Current sprints, this project will use a one-week time box. The duration of the standard sprints can be adjusted as part of the retrospective.

9.2. Scrum Team 

The scrum team is the team which will deliver the final solution. As per the currently planned setup (may be revised) it consists of:

  • Implementation team of the consulting firm
  • Smart Africa Secretariat Project Manager
  • City of Kigali Digitization team
  • MINICT& Innovation Project Manager
  • RISA Innovation team

9.3. Features/ User Stories

Features and user stories are the artefacts which define the deliverables inside a sprint. They need to be described and documented. The team has to agree on the “definition of done” for an agreement of completion of the respective artefacts. The difference between “user story” and feature for this project is mainly the distinction between deliverables with a concrete impact on users (resp. user stories) like implementation of a specific dashboard or workflow or deliverables with no specific impact on users (resp. features) like implementation of a core data model.

9.4. Backlog

The Backlog covers the list of all features and user stories which are in scope or will be in scope for implementation. It acts as the pipeline for to be implemented artefacts.

9.5. Daily Stand-ups

Daily stand-ups are a standard approach as part of the SCRUM methodology. The collocated team meets at a dedicated fixed and short time slot (usually 15 minutes) and answers one by one the following questions:

  • What did I do yesterday?
  • What will I do today?
  • What obstacles are in my way?

9.5.1. Based on experience we have the DOs and DONTs:

DOs

  • Create and support an open environment and atmosphere
  • Schedule follow ups for identified obstacles
  • Be firm, be brief, be open

DONTs

  • Don’t use it for individual tracking
  • Don’t expand the timeslot by going too much into details (rather schedule follow up)
  • Don’t blame.

9.6. Retrospective, Review & Planning

As the iterations are quite short, best practice has been established to combine retrospective, review, and planning session. During this session the following activities are to be performed:

  • Review the result of the features planned for the current sprints based on the “definition of done”
  • Accept or reject completion status
  • Review the “definition of done”
  • Review the preparation of features in the backlog
  • Plan features or user stories for the current sprint
  • Adjust the approach if necessary

9.7. Product Owner

The City Engineer acts as the product owner for this project. He will provide priorities for project artefacts and finally accept or reject the implemented features or user stories

9.8. PM-System

This project will use “Open-Project” for project tracking and planning. This system shall be used for project planning and reporting by the vendor.

9.9. Continuous Integration (CI)/Deployment (CD) Environment

The end technical beneficial uses Gitlab for versioning and CI/CD. This should be used as a code repository.

9.10. Warranty

The vendor is expected to fix all test fails of severity before Go-live period for the product.

10. ACCEPTANCE PROCEDURE

All deliverables which are part of a fixed price solution shall be accepted by a formal acceptance procedure aka “user acceptance test”. The set of the tests will be mutually agreed during the project phase. They are mainly a subset of the vendors functional end-to-end-tests but can be extended by RISA with own test cases if need be. All test cases have to be based on the described scenarios and the scenario requirements only.

10.1. Severity of failed test results

(1) Critical:

  • Failing test critically affects the primary business service, major application or function
  • Characteristics of a Severity 1 case include but are not limited to:
    • Business service or function is not operational
    • Production system crashes
    • Data integrity at risk
    • Production backup and recovery operations fails

(2) Major:

  • The business service, major application, function, or system is seriously affected
  • No acceptable workaround is available
  • Documentation not available

(3) Medium:

  • The business service, major application, function or system is moderately impacted
  • No data has been lost
  • The business service, application, or system is still functioning
  • Documentation needs an explanation
  • The case may be temporarily circumvented using an available workaround

(4) Minor:

  • Non-critical cases
  • Minor documentation cases

(5) Service Requests:

  • Enhancement requests

10.2. Acceptance Criteria

Deliverable

Acceptance criteria

Solution as per objectives & requirements 3,5

User acceptance test with not more than:

  • 0 (zero) critical test fails
  •  0 (zero) major test fails
  • 3 (three) medium test fails

Business processes & user stories

Formal acceptance needed by project owner

Training

Training as per mutually agreed training plan and methodology

Licenses

Licenses purchased as mutually agreed and proposed

Solution design & architecture

Formal acceptance needed by steering committee

Additional requirements

No formal acceptance needed, delivered as service contract

11.COMPANY PROFILE AND EXPERIENCE

Considering the importance of delivering the project in alignment with local context; in addition to the human resources required to assemble its team, as described below, the firm must meet the following requirements:

  • Have at least five (5) years of relevant experience in delivering engineering and technology integrated solutions.
  • Have work experience in Rwanda or an active partnership with a qualifying Rwandan company. In case of a partnership, the Rwandan company must be present and active throughout all the stages of project delivery.
  • Commit to leverage local resources while delivering the project.
  • Company should submit three recommendation letters from previous clients of technology or engineering projects with similar magnitude and complexity.
  • Company must demonstrate the ability to deliver on expectations by (among other things) providing the profile of key team members with their anticipated role on the project once awarded
  • Company should clearly demonstrate and be ready to explain/present why their proposed solution is based on local context and meets communicated requirement
  • Company should clearly demonstrate its ability and methodology to ensure successful delivery on the key tasks below as well as committed and dedicated qualified resources:

11.1. Project Manager

 Dedicated Project Manager with demonstrated experience in delivering engineering and technology Projects. The proposed Project Manager should:

  • At least possess a bachelor’s degree in Computer science, Information technology/management, Software engineering, electrical engineering, or another relevant field.
  • Have at least eight (8) years’ experience in project management. This experience must include at least three (3) years implementing large scale IT projects of similar nature (scope and complexity) to this project.
  • Have implemented a city level project for smart city solutions.
  • Involvement in business intelligence projects would be an added advantage.

11.2. Technical Architect

The proposed Technical Architect should:

  • Possess a Bachelor’s degree with 8 years’ experience or Master’s Degree in Computer Science, Information Systems, IoT or related technical field.
  • Have at least five (5) years’ experience in system architecture, and the experience must include three (3) years experience in the implementation of smart city solutions similar in nature, scope, and complexity to this tender.
  • Be knowledgeable in the main areas of IoT Technology Stack namely:
  • Hardware Layer
  • Connectivity Layer
  • Middleware Layer and Applications Layer

11.3. Business Analyst

 The proposed Business Analyst should:

  • Have a bachelor’s degree in Computer Science, Information Systems or related technical field.
  • Have experience in requirements gathering & management plus development and establishment of metric & intelligence reporting
  • Have minimum 3 years in Business Analysis or related fields.
  • Have excellent analytical and conceptual thinking skills
  • Have excellent skills in process and data modelling techniques and methods
  • Have excellent documentation skills.
  • Have excellent skills in stakeholder’s analysis.

11.4. Developer

 The proposed developer should:

  • Possess a bachelor’s degree in embedded Systems, Computer Science, engineering or related technical field.
  • Have hands-on experience with:
    • Internet protocols (HTTP, REST, WebSocket’s, etc.), mobile app and web development (iOS , Android), Applications and systems languages (Java, C#, etc.), embedded or Linux-based IoT environments, Embedded protocols
    • Proven 3 years’ skill in the proposed solution including the to be integrated technologies.

11.5. UX Designer

 The proposed UX Designer should:

  • Have a bachelor’s degree in Computer Science, Information Systems or related technical field.
  • Have 3 years of demonstrated experience in creating and implementing a UX design
  • Have proficient with visual design programs such as Adobe Photoshop and others
  • Have ability to work effectively in a collaborative environment to create top-performing interfaces for clients
  • Have experience with coding and ability to troubleshoot using HTML, CSS, and comparable languages.
  • Have experience creating storyboards and website mapping

11.6. Electrical Installation & Maintenance

 Design and implementation must meet stipulated requirements and led by qualified and committed professionals.

11.7.Technology systems design, implementation and maintenance.

Design and implementation must meet stipulated requirements and led by qualified and committed professionals.

11.8. Technology systems maintenance and knowledge transfer.

  • Company must show clear commitment and plan to train dedicated resources and maintain systems for 12 months as a guarantee.

The Company shall propose additional tasks and corresponding responsible professionals as it deems necessary.

 12.EVALUATION METHOD AND CRITERIA

All bidders should note that the evaluation method is Quality Cost Based Selection (QCBS) for the quality, efficiency, and value for money. The technical evaluation will be conducted in two phases, mainly;

a) Phase1: Have a 110 Marks. Bidders with a technical pass mark of 70/100 on Phase 1 will go into Phase 2.

b) Phase2: Have 55 marks. The phase 2 evaluation will be quantitative and qualitative based where the bidders present their proposed solutions and answer questions from the evaluation committee.

Overall, Phase 1 counts for 75% of Technical evaluation, and Phase 2 counts for 25% of technical evaluation.

Afterward, the financial proposals of those bids that meet the minimum score of 70/100  of technical evaluation will be opened

a) Technical Criteria

The following is the technical evaluation criteria:

Item

Point Range

Company Experience in delivering Similar projects

1.       Number of Similar Projects delivered by the Company

         i.  Above 5 Projects

10

       ii.  4 Similar projects

8

     iii. 3 Similar projects

6

     iv. 2 Similar projects

4

       v. 1 Similar project

2

     vi.  Below 1 Similar Project

0

/10

Signed and Stamped recommendations/certificate of completion for Smart Parking Solution delivery.

         i. 3 and above Projects

15

       ii.  2 Similar projects

10

     iii. 1 Similar project

05

/15

 

 

3.Qualifications and Competence of the company

i. Technology company or consortium with a demonstrated methodology and approach to get the work done as per solution requirements

/10

4. Number of years of Experience of the company registered and delivering similar services/systems in Rwanda

i. Above 5 years

10

ii. Between 3 and 5 years

5

iii. Between 2 and 3 years

3

iv. Below 2 years

0

/10

Proposed Sensor based Solution

5. Smart Parking Solution detailed technical requirements design (Section 5 of ToR) and detailed public interface design (Section 3 of ToR)

         I. Proposal clearly demonstrates (text and sketches) how all requirements will be delivered

25

       ii.  Proposal does not meet mentioned specific requirements

0

/25

 

 

 

 

Teams Competency and Experience

 

1. Project Manager (1)

     iv. Above 8 years

15

       v. Between 5 and 8 years

10

     vi. Between 2 and 3 years

5

    vii. Below 2 years

/15

 

2. Technical Architect (1)

         i.            Above 8 years

10

       ii.            Between 5and 8 years

7

     iii.            Between 2 and 3 years

5

     iv.            Below 2 years

0

/10

 

3. Business Analyst (1)

         i.            Above 5 years

8

       ii.            Between 3 and 5 years

5

     iii.            Between 2 and 3 years

3

     iv.            Below 2 years

0

/8

4.User Experience (UX) Designer (1)

         i.            Above 5 years

7

       ii.            Between 3 and 5 years

5

     iii.            Between 2 and 3 years

3

     iv.            Below 2 years

0

5.

/7

 

The financial proposal of only those firms which secure a minimum score of 70/100 in both technical evaluations will be opened.

St= Score for the Technical Evaluation

b) Financial Proposal Criteria

Notes: All bidders must submit a detailed financial proposal in a separate envelop. Financial proposals must be itemized and detailed for each site.

All financial proposals must be shown in United States Dollar (USD) Currency.

Once the technical criteria have been evaluated, the costs of all bids will be listed from low to high. Computing the cost criteria score will be accomplished by use of the following formula:

  =   =.               100

The Applicant getting maximum marks on 70-30 weightage (70% for technical and 30% for financial) will be considered for the assignment. The weights given to the Technical (T) and Financial Proposals (F) are: T = 0.70 and F = 0.30

The Final Score (S) is calculated as follows: S = St*T + Sf*F

13. SUBMISSION REQUIREMENTS FOR TECHNICAL AND FINANCIAL PROPOSALS

All technical and financial proposals must be submitted in English or French.

  • Submission of administrative documents (Company registration certificates, Tax clearance certificates, and Social Security clearance).
  • Submission of Technical Requirements:
  • Duly signed and stamped submission Letter.
  • Firms corporate profile/Executive summary.
  • Understanding of ToR;
  • A detailed technical proposal with brief description of why the Consulting Firm/Consultants would be considered as the most suitable for the assignment, relevant expertise in smart parking, and a detailed clear methodology, on how they will approach and complete the assignment with work schedules
  • Firms Recommendation letters signed and stamped
  • Having a local company as a partner to deliver this project would be an added advantage. The bidder should provide a clear separation of roles and responsibilities with the local partners
  • Submission of Financial Requirements
  • Summary of Costs.
  • Break down of price per activity.
  • Break down of cost per each site/Public Parking
  • Miscellaneous Expenses.

Notes

  1. All financial proposals/offers should be password protected and Smart Africa will request for it from bidders who have been qualified in the technical evaluation.
  2. Indicate your preferred payment terms under financial proposal.

14.ENQUIRIES 

Any enquiries will only be received and addressed 3 days or more prior to the bid submission deadline. Prospective respondents who may have questions regarding this RFP may submit their enquiries to tenderenquiries@smartafrica.org

15. SUBMISSION PROCESS

Technical and financial proposals must be submitted in an email each showing the nature of the offer concerned (technical or financial offer), the firm’s name marked as follow: 057/S.A./RFP/RFP/12/2021: Smart Parking Solution Project for the City of Kigali.

Well-designed proposals presented in two (2) copies, with one (1) being the English and another being French must be submitted to procurement@smartafrica.org  not later than January 31st, 2022, at, 5:00 pm local time (Kigali) prompt to the Director General.

All enquiries will only be received at least 3 days prior to bid submission deadline.

16. RIGHTS RESERVED

This RFP does not obligate SAS to complete the RFP process. SAS reserves the right to amend any segment of the RFP prior to the announcement of a selected firm. SAS also reserves the right to remove one or more of the services from consideration for this contract should the evaluation show that it is in SAS’s best interest to do so. SAS also may, at its discretion, issue a separate contract for any service or groups of services included in this RFP. SAS may negotiate compensation package and additional provisions to the contract awarded under this RFP.

Note: Proposals will remain valid for 90 days after submission deadline.

17. ANTI CORRUPTION

Smart Africa is committed to preventing and not tolerating any act of corruption and other malpractices and expects that all bidders will adhere to the same ethical principles.

Attachment: final-tor-smart-parking-management-project-edits-31dec20217803ebe7ff4079fcc65b4b5e9297f5a8

Share This: