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

Members
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.

Detailed Report Design Deliverable Template

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Under review.png
This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.
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.

Reporting Design applies to the more traditional design of static reports to support the Business Intelligence environment. The Detailed Report Design builds on the initial Report design document and prototype work that was done interactively with the users in Phase 3 to provide the ’hardened’ design for a production system

Examples

Example for a Detailed Report Design:

1. Introduction

1.1. Purpose


This document describes the report requirements for the ABC report. The report requirements cover the following topics:

  • Business Needs
  • Report Description
  • Technical Overview

The document is centered on understanding the report needs for the business and listing the report objects required to be built to service this report.

1.2. Approach


The report requirements described in this document were gathered through a series of interviews...

1.3. Intended Audience


The primary audience of this report design is the development team, in order to communicate the functionality that should be included.

2. Business Need Overview


The ABC Report tracks movement of customer income between Branches and Relationship Managers (RMs) between previous month and current month. This report is useful for Area Managers, Branch Managers and Relationship Managers as it provides information on the income gained or lost due to customer movement and trends within their portfolios.

2.1. Report Owner


Owner: Manager Performance Team.

2.2. Business Rules and Assumptions

3. Report Description

The ABC Report tracks movement of customer income between Branches and Relationship Managers (RMs) between previous month and current month. The customer income is basically the product income for a customer. The customer income is categorized based on the customer movement.

3.1. Layout

Please note that the layouts described here indicate functionality and format but not actual data values. The layouts illustrate one way of placing the dimensions and measures in the grid. Additional layouts can be designed and built on top of this depending on availability of funds and time.

3.1.1. ABC Trend Report – Business Unit Level

When the report runs, the time prompt appears which allows the user to select a group of months from a list of 13 months. Let us assume the user selects March 2004 and April 2004. The report starts off with a trend analysis of the total Customer Income for the selected months at Business Unit level and Product Group level.

    March 2004 April 2004
    Customer Income Customer Income
Business Unit Product Group XYZ Non-XYZ XYZ Non-XYZ
Consumer Lending $20,000 $5,000 $30,000 $8,000
  Credit Cards $10,000 $2,000 $15,000 $4,000
 
Business Lending $25,000 $32,000 $25,000 $32,000
 
Total   $200,000 $210,000 $200,000 $210,000

The report should also have a line graph showing the trend

3.2. Security/Authorization

This report is accessible to Business Unit, Channel, Area, Branch and Relationship Managers.

3.3. Distribution

This report is distributed through the Client web portal.

4. Technical Overview

4.1. Report Format

  • The ABC Report consists of a number of Client reports and Client Templates. The templates are required to support the user defined drill downs.
  • The default "Red and Black" auto style will be used by the report.
  • The trend report must have the functionality to show graphs. The default graph formats will be used.
  • The data in all attributes (for instance Area, Channel, Product, Customer and so on) will be displayed in ascending order based on their description text.

4.2. Attributes

The attribute objects for this report and templates are listed in the following table.

Attribute Name Description Attribute Display
Month Holds the month Month Name
Business Unit Categorizes RM/Branch by Business Unit.
Example: Consumer
Business Unit Name
Business Unit Movement Categorizes movement of customers at a Business Unit level. The following values are allowed:
1. Retained
2. New to business
3. Lost to business
Business Unit Movement Name
To/From Business Unit If movement is "Retained", set to the current Business Unit.
If movement is "New to business" or "Lost to business", set to "None".
Business Unit Name
or
"None"
Channel Categorizes RM/Branch by channel.
Example: Priority, Private, Migrant
Channel Name
Channel Movement Categorizes movement of customers at a channel level. The following values are allowed:
1. Retained
2. New to business
3. Lost to business
4. Transfer In
5. Transfer Out
Channel Movement Name
To/From Channel If movement is "Retained", set to the current Channel.
If movement is "New to business" or "Lost to business", set to "None".
If movement is "Transfer In", set to the old channel.
If movement is "Transfer Out", set to new channel.
Channel Name

4.3. Facts

The Facts for the report are listed in the following table.

Metric Name Description Metric Display Subtotals
Customer Income XYZ Sum of product incomes of type XYZ for a customer. Sum of XYZ income for primary customers Subtotal, if possible, should apply at any level of the hierarchy.
Customer Income Non-XYZ Sum of product incomes of type Non-XYZ for a customer. Sum of Non-XYZ income for primary customers Subtotal, if possible, should apply at any level of the hierarchy.
Total Income Sum of XYZ and NonXYZ where movement is Retained, Transfer In and New.    
YTD Income YTD sum of XYZ and NonXYZ where movement is Retained, Transfer In and New.    

4.4. Hierarchies

The following are the drill hierarchies applicable to the report.

Drill Hierarchy Name Drill Path
Relationship Manager Hierarchy Business Unit -

> Channel - > Area - > Branch/RM - > Customer

Product Hierarchy Product Group -

> Product Subgroup - > Product


The user should also be able to drill down from a specific movement category. For instance, a user may want to drill down from Area to Branch but only interested in seeing the Retained balances.

4.5. Report Filters


Report filters are user to define constants for a report or a template.
This table lists the report filters required for this report and templates.

Report Filter Name Description
Primary Customers The report is limited to calculating customer income for primary customers.

4.6. Prompts


Prompts allow user interaction at report run time. Prompts are useful for limiting data returned from warehouse in the report. For instance, a Month prompt would ask the user to select a month from a list, so that information rendered on the report is limited to the selected month. This makes the report run faster as a limited amount of data is requested and processed.

This table lists the prompts required for this report

Report Filter Name Description
Month Prompt The month prompt allows a user to retrieve data in the report against a particular month (or months). The user can choose a minimum of 1 month and a maximum of 13 months. The months should be listed in descending order starting with current month. The maximum number of months available to choose from is 13.

4.7. Fact Table Grain

4.8. History Management

The aggregate table that is built for this report would hold data for the last 13 months at any given time. When a new month is added, the oldest month is archived to another data store.

4.9. Refresh Frequency

Report data is refreshed every month.

Wiki Contributors
Collapse Expand Close