Example of a Business Intelligence Dashboard RFP
Are you responsible for writing a request for proposal (RFP) document for your dashboard project implementation and looking for a jumpstart? Or are you with a software vendor and interested in taking a look into the mindset of a potential buyer? Either way, you should take a look at this example of an RFP for a digital dashboard implementation project using Hyperion intelligence Dashboard Builder.
This example comes from the Office of the Chancellor at Minnesota State Colleges and Universities. It is titled Request for Proposal for Requirements Definition, Design Standards, Development and Implementation of Selected Web-based Dashboards and Scorecards for Applications (Accountability. Performance and Planning system).
Use this link to view the RFP site. It contains links to the original RFP that and a subsequent question and answer document.
the RFP follows the standard layout with sections such as general information, vendor requirements, responsive valuation, submission process, selection and implementation timeline, and pricing information.
The dashboard project budget for this was set at $45,000. Note that this project uses a specified dashboard software and is not a custom build of a business intelligence dashboard.
Here is an excerpt from the RFP:
Section III. Vendor Requirements
The project deliverables include: requirements definition, design standards, development and implementation of selected web based dashboards and scorecards.
1. Define and document dashboard design standards required for the consistent design of APPS dashboards and scorecards which are to be built using Hyperion Intelligence Dashboard Builder. Address:
a. Look and feel
c. Technical performance
d. Display of content
e. User documentation standards
2. Revise three existing dashboards to follow dashboard design standards (defined in # 1 above) and link these dashboards to APPS database. Existing dashboards include:
a. CUPPS (Gap Analysis module),
b. Online (one module) and
c. Board of Trustees measure for student success (one module).
Screen shot examples of these dashboards can be found on the APPS website www.apps.project.mnscu.edu under the Related Documents button.
3. Design and build a scorecard using Hyperion Intelligence Dashboard Builder. Initially, the scorecard will report just the student success measure but the scorecard design must accommodate 11 indicators and 27 measures.
4. Prepare web-delivered end user documentation for three dashboards and one scorecard
5. Design/build APPS front-end launching point (appropriate for varying levels of access rights) for entry into APPS and associated dashboards and scorecards.
• The vendor must use Hyperion Intelligence Dashboard Builder
• Web pages must conform to OFFICE OF THE CHANCELLOR’s accessibility guidelines (http://webmasters.mnscu.edu/access/guidelines/ ). Variances to these guidelines may be permitted when the ability to comply is shown to be impractical due to limitations of Hyperion Intelligence Dashboard Builder capabilities.
• The system (database and dashboards and scorecards) will be implemented at one location (OFFICE OF THE CHANCELLOR offices in St. Paul, MN)
• The vendor selected, must agree to use the State of Minnesota standard contract and include language regarding compliance with the U.S. Family Educational Rights and Privacy Act (FERPA). This is non-negotiable. A copy of the template contract and FERPA language can be found at www.apps.project.mnscu.edu under the Related Documents button.
Responsibilities Expected of the Selected Vendor
The following responsibilities are expected of the selected vendor:
• Training and knowledge transfer to MnSCU staff on defined dashboard design standards
• Vendor staffing (include availability during proposed timeline)
• Propose a change management process for the project
• Project Status Reports
• Work-plan (initial plan and status updates during the project)
• Vendor accepts responsibility for maintaining project scope unless MnSCU authorizes a written notice to change the project scope
• Warranty requirement:
The Vendor must warrant that for a period of 180 days after acceptance of a deliverable that the deliverable will conform, in a manner consistent with professional and technical standards in the software industry, with applicable written specification included in the corresponding task or delivered to the State pursuant to this agreement.
The responder will provide a written warranty that will make the responder responsible for fixing defects, free of charge, in the delivered product for a period of one year after deployment into the production environment. This warranty will cover defects only (not enhancements, maintenance or upgrades). The responder will also warranty that the database will work independent of upgrades done on the database server. Any modifications necessary when upgrading to newer versions will be completed by the responder without cost during this warranty period.
Leave a Reply
You must be logged in to post a comment.