Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

Model Designed for Ad-Hoc Analysis Deliverable Template

From MIKE2.0 Methodology

Jump to: navigation, search
Under construction.png
This article is currently Under Construction. It is undergoing major changes as it is in the early stages of development. Users should help contribute to this article to get it to the point where is ready for a Peer Review.
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.

Model Designed for Ad-Hoc Analysis deliverable is based on the fact that if users require ad hoc information access, it is common to provide a richer, abstracted environment from which they can access the information. Vendors have different approaches to this problem, but generally a well-defined metadata environment is what facilitates access to information and allows investigative and power users to directly answer the questions they have, complementing the information in existing reports.

Examples 1 - Summary of Approach for Ad Hoc Reporting

Example for a Model Designed for Ad-Hoc Analysis:


MicroStrategy is used to provide basic analytic and reporting capabilities to the power users and end-users across the Company.


The majority of users will interact with the system through a Web-based interface. This includes end-users, who are simply viewing pre-built reports, as well as power users – who manipulate data cubes and create reports for end-users. Administrative users and developers access MicroStrategy through the Web interface and through MicroStrategy desktop applications.

Report Definitions

MicroStrategy report and cube definitions are based on the XYZ definitions, and on user feedback.

The reports are designed to encompass a wide range of user requirements, but on-going fine-tuning is anticipated. For reports and report elements that are derived directly from the XYZ System of Record and the Summary Area, modifications can be done entirely within MicroStrategy.

Reports and report elements that are based on specialized star schemas (or materialized views) should be modified in coordination with the ETL and Oracle administration teams.

Wiki Contributors
Collapse Expand Close