Please enable JavaScript.
Coggle requires JavaScript to display documents.
Process for Designing a Multi Dimensional Database - Coggle Diagram
Process for Designing a
Multi Dimensional Database
Analyze business needs and design a plan
Identify source data/Analyzing Source Data
where the data resides
how often you plan to update the database with the data
WHY: saves time when you create the database outline and load data into the Essbase database
Determine scope of the database :black_square_for_stop:
:bulb:thousands of product families containing hundreds of thousands of products, Store data on product family or products
Interview users
What types of analysis do users require?
What summary and detail levels of information do users need?
Do some users require access to information that other users should not see?
Carefully define reporting and analysis needs.
How do users want to view and analyze data?
How much detail should the database contain?
Does the data support the desired analysis and reporting goals?
If not, what additional data do you need, and where can you find it?
Determine the location of the current data
Where does each department currently store data?
Is data in a form that Essbase can use?
Do departments store data in relational databases on Windows or UNIX servers, or in Excel spreadsheets?
Who updates the database and how frequently?
Do those who need to update data have access to it?
Ensure that the data is ready to load into Essbase.
Does data come from a single source or multiple sources?
Is data in a format that Essbase can use? For a list of valid data sources that you can load into Essbase
Do some users require access to information that other users should not see?
define user information
access needs
review security considerations
design a database model
Create a model on paper.
To build the model, identify the perspectives and
views that are important to your business
views translate into the dimensions of the
database model.
Business areas
Time periods
Accounting measures
Scenarios
Products
Distribution channels
Geographical regions
Business units
Identifying Analysis Objectives - Designing essbase database that enables data analysis.
Analyzing by time-
current year or multiple years?
Should the analysis include
quarterly and monthly data?
Should it include
data by season?
Analyzing by geographical region -
How to define regions?
define
regions by sales territories?
Do you define
regions by geographical boundaries
such as states and cities?
If analyzing by product line, should you
review data for each product?
Can you
summarize data into product classes?
WHY? To save development and implementation time.
Design Pre-requisites :key:
How information flows within the company
who uses which data for what purposes
The types of reporting the company does
types of data must be included in the outline
to serve user reporting need
Draft a database outline.
what information is stored and how
different pieces of information interrelate
Check system requirements
because affects the efficiency and
performance of the database.
Load test data into the database.
to enable
the later steps of the process
Define calculations.
outline consolidations and write and test formulas
calculation scripts for specialized calculations.
Define reports
access data through print and online reports and spreadsheets or on the Web
Verify with users.
To ensure that the database satisfies your user goals, solicit and carefully consider user
opinions