Unit-3
1. Introduction to Business Intelligence
1.1 Definition and Core Purpose of Business Intelligence
Business Intelligence (BI) is a comprehensive discipline encompassing technologies, processes and strategies designed to collect, manage, analyze and interpret organizational data. Its primary objective is to generate profound insights that inform and guide business strategies and operations.
BI tools and specialized software are instrumental in processing vast and complex datasets. They reveal intricate patterns, underlying trends and critical insights that would otherwise remain hidden or unidentifiable.
The discipline transcends mere report generation; it is fundamentally about transforming raw data into actionable intelligence for strategic decision-making. This distinction signifies a crucial shift from a reactive stance, which focuses on understanding "what happened," to a proactive approach, which seeks to understand "why it happened," anticipate "what will happen," and prescribe "what to do." This foundational shift allows organizations to move beyond reliance on intuition, guesswork or outdated information. By providing concrete, evidence-based insights derived from data, BI inherently minimizes risks.
This empowers organizations to respond swiftly to market changes, identify emerging opportunities and ultimately secure a significant competitive advantage.
Example: A retail company uses BI to analyze sales data from the past five years. This analysis reveals that sales of winter clothing consistently peak in October and November, allowing the company to proactively increase inventory and marketing efforts for these months, rather than reacting to demand fluctuations.
1.2 Enabling Effective and Timely Decision-Making
Data-driven decision-making, a central theory facilitated by Business Intelligence, involves making informed business choices based on rigorous data analysis and actionable insights, rather than relying on subjective intuition, speculative guesswork or outdated information.
The key benefits derived from integrating BI into decision-making processes are multifaceted, encompassing improved decision quality, enhanced operational efficiency, more profound customer insights, a distinct competitive advantage and robust risk management and mitigation capabilities.
The emphasis on "timely" and "faster" decision-making underscores that the value proposition of BI extends beyond merely making better decisions to enabling quicker responses. This enhanced speed is fundamentally enabled by the capacity to monitor business progress digitally and make rapid, informed adjustments in real-time or near-real-time.
Example: A logistics company uses real-time BI dashboards to monitor delivery routes. If a dashboard alerts a manager to a sudden traffic jam or road closure, the manager can immediately reroute affected delivery trucks, minimizing delays and fuel waste, thus ensuring timely delivery and operational efficiency.
2. The DIKW Pyramid:
(Data, Information, Knowledge and Wisdom in BI)
The DIKW (Data, Information, Knowledge, Wisdom) pyramid is a widely recognized hierarchical model that meticulously illustrates the structural and functional relationships between these four concepts. In this model, each successive level builds upon the preceding one, progressively adding more meaning, context and actionable value.
1. Data
(The Foundation of Raw Facts)
Data forms the foundational base of the DIKW pyramid, consisting of raw, unorganized facts such as uninterpreted numbers or characters.
In the context of Business Intelligence, this foundational layer includes raw inputs like unprocessed sales figures, unaggregated customer demographics or undifferentiated website traffic numbers.
This initial lack of context necessitates and drives the subsequent, more complex steps of the DIKW pyramid. Without proper initial data collection, meticulous organization and fundamental structuring, the entire Business Intelligence process would be fundamentally imperfect. This underscores the critical importance of initial data quality and well-defined collection strategies, as inaccurate or incomplete raw data inevitably "enter the system, resulting in wrong reporting and analysis".
This directly compromises the integrity and utility of all derived understandings. Internalizing this foundational level means recognizing that data acquisition and the initial stages of data quality checks are not trivial or secondary tasks. Instead, they are paramount for ensuring the overall integrity, reliability and ultimate utility of all subsequent BI efforts and the understandings they aim to generate.
2. Information
(Contextualized and Organized Data)
Information represents the next level in the DIKW pyramid, characterized as data that has undergone processing, meticulous cleansing of errors, and systematic organization.
This transformation is undertaken to make the data more readily measurable, visually interpretable and ready to analysis for a specific, defined purpose.
Example:
Information: "On
2024-06-15,4500units ofProduct Awere sold inNew York."Explanation: The raw data points are now organized and given context, answering "what was sold," "when," "where" and "how much." This allows for basic reporting, like a daily sales summary.
3 Knowledge
(Applied Information for Insight)
Knowledge is derived from information by delving deeper to understand "how" that information is relevant to specific organizational goals and critically, "how" different pieces of information are interconnected to add more profound meaning and value.
Furthermore, it encompasses understanding "how" to practically apply this information to achieve a particular objective or solve a specific business problem.
In the realm of Business Intelligence, knowledge is attained when organizations transcend the mere description of facts. Instead, they begin to grasp the underlying implications and intricate relationships within the information.
Example
"Sales of Product A increased by 15% in New York during June 2024 because of a targeted social media campaign launched in that region, which correlated with a 20% increase in website traffic from New York."
Explanation: This goes beyond what happened to why it happened, connecting sales data with marketing efforts and website analytics to reveal a causal relationship. This insight can be applied to future campaign
4 Wisdom
(Informed Action and Strategic Guidance)
Wisdom represents the top of the DIKW pyramid, embodying knowledge that is not merely understood but actively applied in action.
While data and information primarily offer a retrospective view of the past, knowledge and wisdom are intrinsically associated with current actions and the formulation of future goals.
Example:
"Based on the success of the June 2024 social media campaign for Product A in New York, we will allocate an additional 10% of our Q3 marketing budget to similar targeted digital campaigns for high-potential products in other underperforming regions, as this strategy has proven to be the most effective for driving sales growth."
Explanation: The knowledge gained is now used to make a strategic decision about future resource allocation and marketing strategy, guiding proactive action for optimal business outcomes.
The Role of Mathematical Models in Business Intelligence
Mathematical Models:
Mathematical modelling is the process of applying mathematics to a variety of real-world problems. It is a powerful tool that can provide insight into complex systems, from understanding traffic patterns and predicting climate change to designing aircraft. As technology continues to advance, mathematical modelling will become increasingly important for developing effective solutions.
Mathematical modelling is the process of using a priori information and data to create theoretical models which can be used to understand, explain or predict real world phenomena.
1. Importance of Mathematical Models in Data Analysis
One of the main advantages of mathematical models is their capacity to examine complex data structures.
Mathematical models also simplify complexity by reducing a problem into its simplest components, making it easier to understand and manipulate. This simplification allows analysts to work with much larger datasets than would otherwise be manageable and models can provide visual representations of data for easier interpretation.
2. Types of Mathematical Models in BI Applications
Mathematical models in BI can take different forms, but they generally include variables, parameters and metrics to evaluate alternative options through "what-if" analysis.
a) Descriptive Models
These models summarize historical data to provide insights into past performance. Common techniques include
- Statistical Analysis: Analysing averages, distributions and correlations.
- Data Aggregation: Grouping data for summary purposes (e.g., sales per quarter).
- Data Visualization: Using graphs, dashboards and charts to present data trends.
b) Predictive Models:
These models leverage historical data and statistical or machine learning algorithms to forecast future outcomes, enabling organizations to make proactive, data-driven decisions.
i) Classification Models:
These models categorize data based on historical learnings, typically answering yes/no questions or assigning data to discrete groups. Examples include predicting customer retention or identifying fraudulent transactions.
c) Optimization Models / Prescription Models
These are designed to find the best possible solution from a set of alternatives, often used for resource allocation, supply chain management, or scheduling.
- Optimization Models: Finding the best solution for maximizing or minimizing a function (e.g., maximizing profit or minimizing cost).
- Linear Programming: Solving optimization problems using linear equations.
Example: A logistics company uses an optimization model to determine the most efficient delivery routes for its fleet of trucks, minimizing fuel costs and delivery times while adhering to delivery windows and vehicle capacity constraints.
d) Simulation Models
These build virtual representations of real-world systems to test different scenarios and predict outcomes without real-world risk.
Example: A new product development team uses a simulation model to assess the potential impact of different pricing strategies on market share and profitability before launching the product, allowing them to test "what-if" scenarios in a risk-free environment.
e) Stochastic Models
These incorporate randomness and probability, suitable for situations with inherent uncertainty, such as risk assessment or financial modeling.
Example: An investment firm uses a stochastic model to simulate thousands of possible future market scenarios, each with different probabilities, to assess the risk and potential returns of a new investment portfolio.
f) Deterministic Models
These produce the same output for a given input, without accounting for randomness, often used when relationships are well-defined and predictable.
Example: A manufacturing company uses a deterministic model to calculate the exact number of raw materials needed to produce a specific quantity of finished goods, assuming no variability in production processes or material quality.
g) Static Models
These represent a system at a single point in time, without considering changes over time.
Example: A company uses a static model to analyze its financial balance sheet at the end of a fiscal quarter, providing a snapshot of its assets, liabilities, and equity at that specific moment.
h) Dynamic Models
These capture how a system evolves over time, essential for forecasting and understanding trends.
Example: A marketing department uses a dynamic model to track how customer engagement with an advertising campaign changes over several weeks, observing the decay rate of ad effectiveness and the cumulative impact on brand awareness.
3. Application in Forecasting and Decision Support
Mathematical models are extensively applied in BI for forecasting and decision support. Predictive analytics, a key area, directly utilizes these models to forecast future events based on historical information.
Example: A hospital uses a predictive model to forecast patient admissions for the upcoming flu season based on historical admission rates, current flu strain prevalence and vaccination rates. This forecast helps the hospital make informed decisions about staffing levels, bed allocation and medical supply procurement to ensure adequate resources are available.
Architecture of Business Intelligence
A Business Intelligence (BI) architecture serves as a foundational framework that clearly articulates how various technologies and BI tools will be selected and integrated, how data management practices will be applied, and how existing analytical processes will be optimized.
BI Architecture:
A) Cycle of a Business Intelligence Analysis
The Business Intelligence cycle is an iterative process that transforms raw data into actionable understandings, constantly evolving to better meet business requirements and provide more relevant, accurate and detailed data for decision-making.
i) Setting Clear Objectives / Analyze Business Requirements:
The process begins with establishing clear objectives, where organizations define their primary focus areas and the specific questions they aim to answer.
Example: A retail company's objective is to "reduce customer churn by 10% in the next quarter." This objective guides the entire BI process, focusing data collection and analysis on customer behavior.
ii) Data collection:
The next phase involves gathering and organizing data from various sources, both internal and external. These are the origins of the raw data, including internal systems (CRM, ERP), internal documents and external sources (social media, market research, govt published data)
Example: To address customer churn, the company collects data on customer purchase history, website activity, customer service interactions, demographic information and feedback from surveys.
iii) Data Cleaning and Preparation:
Data cleaning is a process of discrepancy detection. Discrepancy can be caused by several factors such as poorly designed data entry forms, inconsistent data representation, inconsistent use of codes and system errors etc.,
In such cases one can do identification of missing values, remove duplicates and errors and normalization of data etc.,
- Unique rule - each value of the given attribute must be different from all other values of that attribute.
- Consecutive rule - there can be no missing values between the lowest and highest values of the attribute.
- Null rule - specifies blanks, question marks and other special characters.
Example-
Handling Missing Values: In a customer survey, if 10% of respondents left the "income" field blank (MCAR), the company might impute these missing values with the median income of similar demographic groups to avoid discarding valuable survey responses.
Duplicate Removal: A marketing database might have multiple entries for the same customer due to different email addresses or slight name variations ("John Doe" vs. "J. Doe"). Duplicate removal identifies and merges these records to create a single, accurate customer profile, preventing redundant marketing emails.
iv) Data Integration:
This crucial layer transforms raw data into an analytics-ready format. It involves defining data sources, preparation methods and best practices. The core is the Extract, Transform, Load (ETL) process, or increasingly, Extract, Load, Transform (ELT)
Extract: Pulling sales data from an on-premise SQL database and customer demographics from a cloud-based CRM.
Transform: Cleaning inconsistent product names (e.g., "T-shirt" vs. "Tshirt"), converting currency formats, calculating total order value, and removing duplicate customer entries.
Load: Storing the cleaned and transformed data into a central data warehouse.
v) Analysing Data
In this phase, organizations delve deep into the data to uncover trends, patterns and understandings that go beyond basic reporting.
Example: Analysts identify that customers who haven't made a purchase in 90 days and have had a negative customer service interaction in the last 30 days have a 70% higher likelihood of churning. They also discover that customers in a specific age group are more prone to churn.
For getting insights from the data, one can use the following techniques
- Descriptive analytics to summarize historical data.
- Predictive analytics to forecast future trends.
- Prescriptive analytics to recommend actions based on data insights.
- Diagnostic analytics to understand the causes of past events.
vi) Data Visualization:
One can obtain the insights from the raw data, the next step is to present in a meaningful and easily understandable way. One can use the following techniques that allow stakeholders to interpret the data quickly.
Dashboards,
Charts,
Graphs and
Info graphics
vii) Decision making
Use the insights from the business intelligence tools and techniques, take strategic decisions. These decisions may help to growth of business performance.
vii) Monitoring and Evaluation
The insights gained from the analysis are used to track performance against strategic goals, ensuring that the organization remains aligned with its long-term objectives.
Example: The company implements a targeted re-engagement campaign for customers identified as high-risk for churn. They monitor a new KPI: "Churn Rate of At-Risk Customers" on a daily dashboard. If the rate doesn't decrease, they might adjust the campaign.
viii) Feedback and Refinement
This final phase involves evaluating what worked and what did not and determining how to improve.
Example: After a quarter, the company reviews the churn reduction campaign's effectiveness. They find it reduced churn by 5%, not the target 10%. They analyze why, perhaps discovering the offer wasn't compelling enough for the identified age group. This leads to refining the objective and strategy for the next quarter.
This cyclical process allows organizations to continuously improve their BI capabilities, ensuring they remain responsive to changing business environments and emerging trends.
Development of Business Intelligence System
The development of a BI system is a multi-phased process, ensuring that data is effectively transformed from raw inputs into actionable insights. It involves several key steps; each essential for ensuring the system meets organizational needs and provides valuable insights.
I. Assessment of the Needs
Identify Objectives: Define the goals of the BI system, such as improving decision-making, enhancing reporting or enabling predictive analytics.
Stakeholder Engagement: Gather input from users and stakeholders to understand their requirements and expectations
II. Architecture Design
- Choose BI Architecture:
Decide on a suitable architecture (e.g., centralized vs. decentralized)
that aligns with business goals.
- Data Flow Design: Map out how data will move from source systems to the BI platform.
This initial step involves acquiring data from various sources, which can include internal databases, cloud applications, external APIs or even web scraping tools.
Example: An e-commerce company collects transactional data from its online store database, customer demographic data from its CRM and product review data from its website and third-party review platforms.
ii) Data Cleaning and Preprocessing
This involves identifying and fixing obvious errors, improving accuracy, ensuring consistency across sources and enabling data curation. For example:
Handling Missing Values: In a customer survey, if 10% of respondents left the "income" field blank, the company might impute these missing values with the median income of similar demographic groups to avoid discarding valuable survey responses.
Duplicate Removal: A marketing database might have multiple entries for the same customer due to different email addresses or slight name variations ("John Doe" vs. "J. Doe"). Duplicate removal identifies and merges these records to create a single, accurate customer profile, preventing redundant marketing emails.
iii) Data transfprmation
This step prepares data for further analysis by converting it into a suitable format.
Aggregation: Daily sales transactions are aggregated to monthly sales totals per product category to identify overall trends.
Joins: Customer demographic data (from CRM) is joined with sales transaction data (from ERP) using a common customer_ID to analyze purchasing behavior by age group.
Pivoting/Unpivoting: Sales data, initially stored with each month as a row, is pivoted to have months as columns (e.g., Product | Jan_Sales | Feb_Sales | Mar_Sales) for easier quarterly reporting.
iv) Feature Engineering
The process of creating new variables or transforming existing ones to help a model better understand the data and improve predictive performance.
Example: From raw customer transaction data, new features are engineered such as "Days Since Last Purchase," "Average Order Value," and "Number of Products Purchased in Last 6 Months" to improve a customer churn prediction model.
v) Data Sampling
A statistical method that selects a representative subset (sample) from a large dataset to make inferences about the entire dataset efficiently.
Example: For a survey of 1 million customers, instead of analyzing all responses, a stratified random sample of 10,000 customers is selected, ensuring that the sample accurately reflects the proportion of different demographic groups (strata) in the full customer base.
vi) Data Portioning
Dividing large datasets into smaller, manageable chunks called partitions, distributed across multiple nodes or servers.
Example: A global e-commerce platform partitions its customer order data by region (e.g., North America, Europe, Asia) and then by order_date within each region. This allows queries for European orders from Q1 2024 to only scan the relevant partition, significantly speeding up data retrieval.
vii) Data Catching strategies
Temporarily storing copies of data in a high-speed layer (like RAM) to serve future requests faster, reducing database load and shortening retrieval time.
Example: A popular news website caches its most frequently read articles in an in-memory cache. When a user requests a popular article, it's served directly from the fast cache (cache hit) instead of querying the slower main database, leading to faster page load times.
III. Data Modelling
- Data Warehouse Design:
Develop a schema (e.g., star schema, snowflake schema) for organizing data
in the data warehouse.
- Identify Dimensions and Facts:
Determine the key dimensions (e.g., time, geography) and facts (e.g.,
sales figures) to be included.
Effective data storage is fundamental to a robust BI architecture, providing the foundation for analysis and reporting.
i) Data Warehouse Architectures and Approaches
A data warehouse is a centralized system for storing structured, historical data, designed to power complex analytics and turn raw data into a powerful asset for BI and data-driven decisions.
ii) Data Marts
Data marts are customized, subject-specific sections of a larger data warehouse, designed to meet the unique requirements of a specific team or business line.
iii) OLAP Cubes
Online Analytical Processing (OLAP) systems store multidimensional data, representing information in more than two dimensions. The core of most OLAP systems is the OLAP cube array-based multidimensional database designed for faster and more efficient processing and analysis of multiple data dimensions.
IV. Tool Selection
- Evaluate BI Tools: Choose
appropriate BI tools and software (e.g., Tableau, Power BI, Qlik) based on
user needs and technical requirements.
- Consider Integration Capabilities:
Ensure that the selected tools can easily integrate with existing data
sources and systems.
V. Data Integration
- ETL Processes: Develop Extract,
Transform, Load (ETL) processes to consolidate data from multiple sources.
- Data Quality Assurance:
Implement measures to ensure data accuracy and consistency during
integration.
VI. System Development
- Build the BI System:
Configure the chosen BI tools, create dashboards, and set up reporting
functionalities.
- User Interface Design:
Ensure the interface is user-friendly and meets the needs of different
stakeholders.
VII. Testing and Validation
- Conduct Testing: Perform
thorough testing of the BI system to identify and resolve any issues.
- User Acceptance Testing (UAT):
Involve end-users in testing to ensure the system meets their
requirements.
Model EvaluationAfter training, models are validated to ensure they meet codified objectives before serving them in production. This involves performing a final "Model Acceptance Test" using a hold-back test dataset.Example: The customer churn prediction model is evaluated using a holdout dataset (data the model has never seen). Metrics like Accuracy, Precision, Recall, and F1-Score are calculated. If the model achieves 85% precision (meaning 85% of predicted churners actually churn) and 70% recall (meaning it identifies 70% of actual churners), these metrics are assessed against predefined business goals.
VII. Training and Support
- User Training: Provide training
sessions for users to familiarize them with the BI tools and processes.
- Documentation: Create user
manuals and documentation to assist users in navigating the system.
VIII. Deployment
- Roll Out the System:
Launch the BI system across the organization.
- Monitor Initial Use:
Pay close attention to user adoption and gather feedback.
This is a crucial phase that brings research into the real world, allowing the true value of a machine learning model to emerge. Once deployed, users can interact with a model and benefit from its insights.
Example: The validated customer churn prediction model is deployed as a real-time service. When a customer interacts with the company's website or customer service, the model immediately assesses their churn risk. This prediction is then integrated into the CRM system, alerting customer service agents to offer proactive retention incentives to high-risk customers.
X. Continuous Improvement
- Evaluate Performance:
Regularly assess the effectiveness of the BI system based on user feedback
and performance metrics.
- Iterate and Enhance:
Make necessary adjustments and improvements based on changing business
needs and technological advancements.
XI. Governance and
Maintenance
- Establish Data Governance:
Create policies and procedures for data management, security, and
compliance.
- Ongoing Maintenance:
Regularly update the system, manage data quality, and ensure it evolves
with organizational needs.
Ethics in Business Intelligence (BI)
Ethics in business intelligence (BI) is crucial as organizations
increasingly rely on data to inform their decisions. Here are the key ethical
considerations related to BI:
1. Data Privacy
- Compliance with Regulations:
Organizations must adhere to data protection laws such as GDPR - General Data Protection Act or CCPA - California Consumer Privacy Act,
ensuring that personal data is collected, processed and stored legally.
- User Consent: Obtaining informed
consent from individuals before collecting or using their data is
essential.
2. Data Security
- Protecting Sensitive Information:
Implement robust security measures to prevent data breaches and
unauthorized access.
- Data Encryption and Access Controls:
Use encryption and strict access controls to safeguard data integrity and
confidentiality.
3. Bias and Fairness
- Avoiding Algorithmic Bias:
Ensure that the algorithms and models used in BI do not perpetuate
existing biases or inequalities. Regularly audit data and analytics for
fairness.
- Diverse Data Representation:
Use diverse and representative data sets to avoid skewed insights that
could lead to unfair business practices.
4. Transparency
- Clear Methodologies:
Be transparent about how data is collected, processed and analyzed. This
helps build trust among stakeholders.
- Exploitability of AI Models:
When using AI or machine learning, provide explanations of how decisions
are made, especially in critical areas like hiring or loan approvals.
5. Responsible Use of
Insights
- Ethical Decision Making:
Ensure that insights derived from BI are used responsibly and do not harm
individuals or communities.
- Avoiding Manipulation:
Resist the temptation to manipulate data to present a skewed narrative
that could mislead stakeholders.
6. Data Ownership and
Intellectual Property
- Clarifying Ownership:
Clearly define who owns the data, especially when it involves third-party
sources or collaborations.
- Respecting Intellectual Property:
Ensure that data and insights derived from it do not infringe on the
intellectual property rights of others.
7. Stakeholder Engagement
- Inclusive Decision Making:
Involve diverse stakeholders in discussions about data use and ethical
implications, ensuring multiple perspectives are considered.
- Feedback Mechanisms: Establish channels for feedback on BI practices to continuously improve ethical standards.
8. Monitoring and
Accountability
- Establish Ethical Guidelines:
Create a framework for ethical decision-making in BI practices.
- Regular Audits: Conduct
regular audits of BI processes to ensure compliance with ethical standards
and identify areas for improvement.
9. Cultural Sensitivity
- Understanding Context:
Be aware of cultural differences that may affect data interpretation and
its impact on different communities.
Knowledge delivery in Business Intelligence refers to the various mechanisms and formats through which processed data, information and derived understandings are presented to different user types within and outside an organization. This ensures that insights are accessible, actionable and tailored to specific needs, supporting informed decision-making across all levels.
Business Intelligence tools are utilized by various types of users within an organization, each leveraging BI in distinct ways to fulfill their roles effectively.
- Visualization: Data scientists use charts, graphs, dashboards and interactive visualizations to convey complex data patterns and trends in a simple, accessible format. Visualization tools like Tableau, Power BI, Matplotlib and Seaborn (for Python) are commonly used.
- Storytelling with Data: Knowledge delivery often involves crafting a narrative that connects the raw data insights to real-world implications. It helps the audience understand not just what the data says, but why it matters.
- Dashboards: Dashboards aggregate key performance indicators (KPIs) and metrics, making it easy for stakeholders to monitor performance and trends at a glance. They allow for interactive analysis where users can drill down or filter data on their own.
- Standard Reports: Standard reports form the backbone of any Business Intelligence application. These reports are standardized in terms of both layout and content and are provided to report recipients at regular intervals.
They are typically predefined, with fixed content, where the user selects preconditions such as period, actuality and company to generate the report.
- Ad-Hoc Reports: Reports generated based on specific requests or immediate needs. These often focus on answering specific questions or exploring particular data sets.
- Automated Reporting: Data science models or tools may automatically generate and send reports to stakeholders based on predefined rules, schedules or thresholds.
- Parameterized Reports - Parameterized reports are a feature in Business Intelligence that allows for the creation of multiple versions of a report from a single template.
This is achieved by customizing specific aspects of the report, such as periods, regions or product categories, before it is delivered to the intended users.
- Self-Service Reporting - Self-service reporting is a type of Business Intelligence that empowers users, regardless of their technical skills, to access, analyze and report on data without needing help from IT, developers or other technical resources.
Interactive Analysis and Ad Hoc Querying
Interactive analysis and ad hoc querying empower business users to conduct spontaneous, on-the-fly analyses without requiring pre-built reports or datasets.
- Interactive Analysis
allows users to dynamically explore data by interacting with dashboards
and reports. Users can filter, drill down or pivot data to uncover deeper
insights on-demand.
- Ad Hoc Querying refers to
the ability for users to query the data warehouse or data sources
on-the-fly, creating custom reports based on their specific needs. Ad hoc
querying often involves the use of BI tools that allow users to
drag-and-drop fields, apply filters and create custom queries without
requiring SQL knowledge.
Example: A marketing manager notices a sudden drop in website traffic from a specific country. Using an interactive BI dashboard, they can perform an ad hoc query to filter traffic data by country, then drill down by city, and further by traffic source (e.g., social media, paid ads) to quickly pinpoint if the drop is localized or related to a specific campaign, without needing to request a custom report from the IT department.
Dimensional Analysis
Dimensional analysis in Business Intelligence primarily refers to the exploration of data across various dimensions within a multidimensional data model, most commonly represented by OLAP (Online Analytical Processing) cubes .
Example: A business analyst uses an OLAP cube containing sales data with dimensions like Product, Time, and Region and measures like Sales Revenue and Quantity Sold.
They
drill downfromYeartoMonthto see monthly sales trends.They
slicethe cube to focus only onProduct Category: Electronics.They
dicethe cube to analyzeSales RevenueforElectronicsinQ2 2024forNorth America.They
pivotthe view to seeSales RevenuebyRegionon rows andProduct Categoryon columns, providing a cross-sectional view of performance.
Alerts/Notifications
Alerts and notifications in Business Intelligence are proactive mechanisms designed to inform users about significant events, changes, or deviations in key business metrics without requiring them to actively check reports or dashboards.
Example:
Performance Alert: A sales manager receives an automated email notification when daily sales for their region drop by more than 15% compared to the previous week's average, prompting immediate investigation.
Threshold Alert: An inventory manager receives an SMS alert when the stock level of a critical product falls below a predefined reorder threshold, triggering a new purchase order.
Anomaly Detection: A fraud detection system sends an alert to a financial analyst when a customer's spending pattern deviates significantly from their historical behavior, indicating a potentially fraudulent transaction.
Comments
Post a Comment