Request for Information Template

Project Name>

Request for Information Template

Supplement No. (R)

Project Name

Requestfor Information

<Proposal Title>

Prepared By: Author

Document Version:<N.N>

Date:<Month, Year>

Introduction

The template will present a standard format for a Request for Information for an e-government PPP,

The template serves three main purposes:

1. Acquiring more Information about a certain basic partner to aid in issuing the PPP procurement documentsand according to competitive system, government procurement and its approved operational and financial rules and regulations.

1. Ensuring that sponsor agencies develop well-conceived tender documents for PPP projects and clarifying the competitive system requirements .

1. Provide a basis for negotiation of a final PPP agreement.

RFIs are drafted based on the business case and feasibility assessment previously done (and approved) for the project. It acts as a tool to gather more information about a certain vendor in order to strengthen the procurement document (RFP).

TABLE OF CONTENTS

1Template Introduction

2Executive Summary

3Ministry/Agency Overview

4Project Overview

5RFI Requirements Process

5.1Structure of the document

5.2participation to RFI

5.3RFI schedule

5.4RFI RELATED questions / clarifications / submission

5.5RFI terms & conditions

5.5.1Liabilities of Ministry/Agency

5.5.2Confidentiality & RFI Ownership

6High level business requirments

6.1Overview of Functional Requirements

6.2Overview of informative Security Requirements and privacy Protection

6.3Overview of Performance Requirements

6.4Overview of Availability Requirements

6.5Overview of Technical Requirements

6.6legal requirements

6.7Optional requirements

7Response Format

7.1Sample I

7.2Sample II

8Project references -- (Appendix -- I)

1Executive Summary

Brief summary about Ministry/Agency, the need for the information of the potentialhardware / software / services, the RFI is being prepared for and expectation about the basic partner and the solution / service to be obtained.>

2Ministry/Agency Overview

<A brief overview about Ministry/Agency in terms of:

• history
• strategic objectives and direction
• current organizational structure; and
• any other relevant information about Ministry/Agency in relation to the project.>

3Project Overview

<This Section provides a summary overview of:

• project goals;
• objectives;
• scope (for example, of services to be delivered);
• proposed pricing of services to be delivered;
• key performance indicators;
• partnership structure (e.g., PPP model);
• financing or project;
• financial arrangements between partners (e.g., revenue shares);
• expected service delivery;
• stakeholders; and
• Other basic information about the project.>

4RFI Requirements Process

<This Section describes the RFI process for the selected basic partners to which the RFI is sent.>

4.1Structure of the document

Describe the structure of the RFI document and the sections included in it.>

4.2participation to RFI

Explain requirements for the participation of a basic partner in RFI being circulated.>

Basic partners willing to participate should confirm to <Agency issuing RFI> within<number of days>days of receiving the RFI their Intent to Respond. A failure to confirm will signify that a basic partner is not participating in the RFI and <Agency issuing RFI will require an immediate return of the RFI

All basic partners confirming their participation should send the Intent to Respond to the attention of:

<RFI Contact Name & E-mail address>

4.3RFI schedule

<Schedule must be adapted and aligned to the needs and time requirements of each project.>

RFI key dates are the following:

4.4RFI RELATED questions / clarifications / submission

Clarify who is the contact person for any queries and clarification needed with regards to the RFI and submission rules.

All questions related to this RFI should be directed to

<Name of Project Manager & E-mail address>.

Basic partners must ensure that the proposal is delivered in duplicate and received at the following address before the tender closing date<Tender closing Date>.

<RFI Contact Name>

<Address Details>

Any notices with respect to this RFI should also be mailed to the above Contact and Address.

4.5RFI terms & conditions

State the detailed terms and conditions for the RFI. Those terms and conditions to be split into sub-section under this section.

4.5.1Liabilities of Ministry/Agency

State the liabilities of Ministry/Agencywith regards to the RFI.>

This RFI is only a request for information about potential products / services and no contractual obligation on behalf of Ministry/Agency whatsoever shall arise from the RFI process.

This RFI does not commit Ministry/Agency to pay any cost incurred in the preparation or submission of any response to the RFI.

4.5.2Confidentiality & RFI Ownership

State the confidentiality and ownership of the RFI.>

This RFI is both confidential and proprietary to Ministry/Agency, and Ministry/Agency reserves the right to recall the RFI in its entirety or in part. Basic partners cannot and agree that they will not duplicate, distribute or otherwise disseminate or make available this document or the information contained in it without the express written consent of Ministry/Agency.

Basic partners shall not include or reference this RFI in any publicity without prior written approval from the client, which, if granted, shall be granted by the individual named above. Basic partners must accept all of the foregoing terms and condition s without exception. All responses to the RFI will become the property of Ministry/Agency and will not be returned.

5High level business requirments

<State the high level business requirements as requested by the concerned unit inquiring about the solution / service.

5.1Overview of Functional Requirements

5.2Overview of informative Security Requirements and privacy protection

5.3Overview of Performance Requirements

5.4Overview of Availability Requirements

5.5Overview of Technical Requirements

5.6legal requirements

5.7Optional requirements

<For example, nice-to-have functionality that Ministry/Agency may chose to either include or not include in the final contract or at a later stage and that should be priced separately.>

6Response Format

<State in a tabular format the information needed to be collected about the basic partners and the potential product / service. The below table is a guideline sample :>

6.1Sample I

6.2Sample II

Another sample if the RFI is about acquiring a software product. This form can be tailored to fit any type of request from software, hardware, operations and services…etc>

7Project references -- (Appendix -- I)

The basic partner should at least list three previous projects achieved providing project scope, date, owner, status, pricing…etc>

Request for Information1