BI Concept Note
## Intouch & EDI High‑Value Sales Order Monitoring
### Purpose
Introduce a BI‑driven monitoring and alerting capability for Intouch and EDI sales orders to identify high‑value transactions (> €5,000) and enable timely, data‑driven sales and customer engagement actions.
---
### Business Problem
High‑value orders currently enter the system without structured, proactive follow‑up. This results in:
• Missed opportunities for customer appreciation
• Limited insight into exceptional or irregular buying behavior
• Underutilized cross‑sell and upsell potential
---
### BI Solution Overview
A centralized BI solution that:
• Detects high‑value sales orders in near real time
• Enriches orders with customer and historical context
• Triggers notifications to relevant business stakeholders
• Provides dashboards for monitoring and performance tracking
---
### Scope & Trigger Logic
• Trigger condition:
- Sales order total value > €5,000
• Channels:
- Intouch
- EDI
• Threshold configurable via BI parameters
---
### Data Inputs
• Sales order data (Intouch, EDI)
• Customer master data (new vs existing customer)
• Historical order data (frequency, average order value)
• Product / category data (where available)
---
### Data Enrichment & Indicators
For each triggered order:
• New vs existing customer
• Regular vs exceptional order (based on history)
• Order value vs customer average
• Channel and Business Unit mapping
---
### Alerts & Consumption
• Automated notifications to:
- Sales BU
- Account owner / sales rep
• Notification content:
- Customer details
- Order value and channel
- Key indicators (new customer, irregular pattern)
• Delivery via email or collaboration tools (e.g. Teams)
---
### Analytics & KPIs
• Number of high‑value orders by BU and channel
• New vs existing customers for >€5K orders
• Follow‑up SLA compliance
• Cross‑sell / upsell outcomes (future phase)
---
### Business Value
• Improves proactive customer engagement
• Supports sales prioritization based on impact
• Enables cross‑sell and upsell at the right moment
• Positions BI as an event‑driven decision enabler, not just a reporting function
---
### Next Steps
1. Validate data availability and latency
2. Align on business rules and thresholds
3. Define alert ownership and follow‑up process
4. Deliver MVP (alert + basic dashboard)
---
Kind Regards
Cemal Ozturk
Recent ideas
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v7 hours agoCommunity ChampionNew612Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v15 hours agoCommunity ChampionNew17Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019718 hours agoFrequent VisitorNew6Views0likes0Comments