low-level granularity vs. high-level granularity
The lower the level of granularity, the more versatile the query that can be issued.
high-level of detail (the details of every phone call made by a customer for a month) vs. low-level of detail (the summary of phone calls made by a customer for a month)
Granularity: is the level of detail or summarization of the units in the DW. E.g. details of every phone call made by a customer for a month vs the summarized phone calls made by a customer for a month. You can always aggregate detailed data by summarizing, but cannot disaggregate data that is stored only as summaries. This is the benefit of low-level granularity.
Customer relationship management (CRM) promises
- Faster customer service at lower costs
- Higher customer satisfaction
- Better customer retention
Essential questions for business that can be solved by computers (decision support systems).
- Who are my customers and what products are they buying?
- Which customers are most likely to go to the competition?
- What impact will new products/services have on revenue and margins?
- What product promotions have the biggest impact on revenue?
- What is the most effective distribution channel?
- Which are our lowest/highest margin customers?
Organizations need to think about finding products for the customers rather than customers for their products
A key focus of business intelligence is optimizing the lifetime value of customers. To do this we need to
- Get to know the customers better -> create customer profiles
- Interact appropriately with the customers ->
Customer intelligence or 'Analytical CRM' is the process of gathering, analyzing and exploiting information of a company's customer base.
There are 3 main steps:
Data warehouse is "A copy of transaction data, specifically structured for query and analysis" (Ralph Kimball)
Data warehouse data is a series of snapshots, each snapshot taken at one moment in time.
Data warehouse (DW) data always contains a time element-with entries for different values of time.
References
There are 3 main steps:
- Build a data warehousing for customer intelligence.
- Use decision support tools (OLAP and reporting)
- Data mining
- Identify the data that needs to be gathered from the operational business systems,
- Place data in the data warehouse
- Ask questions of the data to derive valuable information.
- How many unfulfilled orders are there?
- On which items are we out of stock?
- What is the position of a particular order?
- Which product lines are increasing in popularity and which are decreasing?
- Which product lines are seasonal?
- Which customers place the same orders on a regular basis?
- Are some products more popular in different parts of the country?
- Do customers tend to purchase a particular class of product?
Data warehouse is "A copy of transaction data, specifically structured for query and analysis" (Ralph Kimball)
Data warehouse data is a series of snapshots, each snapshot taken at one moment in time.
Data warehouse (DW) data always contains a time element-with entries for different values of time.
References
- FIT5158 Monash Lecture Notes, 2011
Fact table vs. dimension table
Data mart
Star join is an ideal structure for a data mart.
The centre of the star join is called the 'fact table'.
Agility
Integrated computerized decision support
Analysis, decisions, predictions
Margin customers
The lifetime value of customers
Customer-centric businesses
Customer-centric organisations
Elaborate: work out in detail (e.g. elaborate a plan)
Blanket marketing campaigns vs. targeted marketing campaigns
Monetary
OLAP: online analytical processing
OLTP: online transaction processing
A single unified data repository
Repetitive
Decision support system data (DSS data)
Clerical functions vs. managerial functions
Primitive data vs. derived data
Collective time horizon
The volume of data in the warehouse
No comments:
Post a Comment