Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
Business Intelligence at CaterTrax
Transcript of Business Intelligence at CaterTrax
Business operations rely on multiple applications:
SAP, CRM, Websites, etc...
There is a need for an extension of the basic data architecture to support that.
Base Tables - for Logical Data Structure
Data Administrator Views - for Security
User Views - for Simplicity and User Choice
Structure and report data
'A posse ad esse' - from being able to being.
Data architecture should cover all aspects of the data required to support decision-making
Interoperability: Data from disparable systems need to be unified
THE DATABASE STRUCTURE
BE ABLE TO
Access instead of request information
Focus on reports rather than on how to obtain them
Understand the data structure
DATA SHOULD BE
defined by the user tasks
*not vice versa
A BUSINESS DATA WAREHOUSE
A SINGLE LOGICAL STOREHOUSE FOR ALL DATA
THE END USER
MUST BE ISOLATED
FROM THE COMPLEXITY OF COMPANY DATA
THERE IS THE NEED FOR LOGICALLY STRUCTURED, FULLY NORMALIZED TABLES
THAT ARE EASILY UNDERSTOOD AND MAINTAINED
BY THE DATA ADMINISTRATOR
THE USER DOESN'T HAVE ACCESS TO THOSE TABLES
AN END USER REQUIRES ACCESS TO A WELL-DEFINED SUBSET
OF THE TOTAL DATA OF THE COMPANY
THE BOUNDARIES OF THIS SUBSET ARE DEFINED BY THE TASKS
PERFORMED BY THE USER
Generating standard reports shouldn't be difficult or shouldn't require detailed knowledge of the data source
Users should focus on the use of information rather than how to obtain it
UI should support general and ad hoc queries, automation, formatted reports, complex data analysis
UI shouldn't restrict the user to predefined tools, but also shouldn't permit changes to stored data
Should be capable of extracting and storing data from diverse sources
Is the end result of ETL processes
Is accompanied by a Data Directory, that describes the data stored in the Data Warehouse
Data Directory describes what the data is, what is its format, where it comes from, how to manipulate it
Credit to goes to Pascal Van Steen, for the awesome Prezi template this presentation was based on. See: http://prezi.com/user/pascalvansteen/.
Content based on '
An Architecture for Business and Information System
,' an article by Devlin, Barry A; Murphy, Paul T. Originally published in IBM Systems Journal. Fun fact: the article was published the same year the creator of this presentation was born. There is a lot to catch up with in Data Warehouse world...
WHAT ARE THE REQUIREMENTS?
DEFINE ALL ASPECTS OF THE DATA
REQUIRED TO SUPPORT THE BUSINESS
BUILD ETL TOOLS, AGGREGATE
CREATE DATA WAREHOUSE
ALL PREVIOUSLY DEFINED DATA
CREATE DATA DIRECTORY
BUILD USER INTERFACE
TEST AND REFINE
BUT MOST OF ALL...