Data Warehousing RFP

 

Much of a data warehousing project's success is determined at the onset. A data warehousing request for proposal (RFP) is a powerful tool in dictating the project's tone.

 

This article gives an overview of some of the components that are covered in an RFP. Data warehousing projects are unique to an organization's business requirements, computer resources and budget. Please contact us if you have any questions.

 

1. General Information for Vendors

§         Lists the Project Vision

§         Project timelines

§         Nature of contract

§         Scope

 Reasoning: Give an overview of project and format for the RFP process.

2. System Background

Description of the Technical Environment

a)      Description on the Client and Server specifications at the Ministry.

b)      Breakdown of  user types for the data warehouse:

c)      Software tools for the data warehouse:

·         ETL Tools

·         Report and Query Tools

·         Data Analysis

·         Data Visualization Tools

 Reasoning: Give an overview of the expected installation. Also specify points of particular

 interest.

3. System Requirements

• List of General Requirements

→ Give an overview of the data warehouse environment.

 Reasoning: An overview of the rational for the data warehouse implementation.

• Mandatory Requirements

a)      List if the software is Client/Server based or web-based. Described what functions are available via the Internet browser. Describe what plug-ins        (if any) are necessary for the client machines.

b)      State that the vendor must communicate with the Ministry’s database and applications. Ask the vendor how they propose to do this.

c)      The vendor must be committed to its products remaining compatible with future versions of Oracle. Ask the vendor to offer documents as evidence of commitment to this environment.

d)      The vendor’s system must enable the overall optimization of the Ministry’s environment:

I)        Ask for how the vendor’s system minimizes user response time while maximizing the use of system resources.

ii)       Ask the vendor to explain the system’s architecture for data selection, processing, formatting.

iii)     Ask for evidence that network traffic is minimized and how the need to process large data sets on the client is also minimized.

 Reasoning: Based on user interviews and technical review, these are the must  

 have features for the data warehouse installation.

• Strongly Desired Features

Examples:

→ The vendor’s system must allow users to schedule reports.

→ Does your system permit users to schedule at a certain time

and date? Daily? Weekly? Based on an event?

Describe how scheduling is accomplished and the options for scheduling reports.

 Reasoning: Based on the requirements analysis, the items listed here are

 additional features that will be good to have but not mandatory.

• Desired Features

Examples:

→ Does your system possess a redundant query control?

This feature returns a saved version of a report whenever an identical report has been executed earlier – the report, output format, and raw data all remain constant in the interim. Describe how this works in your system.

   What are the limits in terms of how far back reports are archived?

 Reasoning: Following the rational of “Strongly Desired Features” above, this

 section lists a lower desired set of requirements.

4. Information Required from Vendors

§         Product Profile

o         Product name

o         Product description

o         Current release level

o         Date current release level was available

o         Projected date for the next release candidate

o         Current products install base

o         Industry verticals of installation

o         Number of installations

o         Breakdown of installations/users

 Reasoning: Gauge vendor’s product specifications and maturity