Flagship course
Supply Chain Visibility Analytics
An eight-week programme for analysts and planners who need business analytics that hold up when partner data arrives late, incomplete, or contradictory.
Learning outcomes
- Inventory the events that truly affect service and cost, then design a signal map around them.
- Build KPI definitions that separate near-real-time needs from overnight reconciliation.
- Create exception queues with owners, thresholds, and evidence packs.
- Brief operations and commercial leads without relying on unexplained dashboard screenshots.
Modules
Module 1 — Visibility landscape audit
Map systems, partners, and handoffs. Spot where “live” claims hide batch jobs.
Module 2 — Signal maps & data lineage
Document event sources, transform steps, and failure modes for each critical milestone.
Module 3 — Latency-aware metrics
Design scorecards that remain truthful when EDI is delayed or portals disagree.
Module 4 — Exception workflows
Thresholds, routing, and evidence packs that reduce swivel-chair investigation.
Module 5 — Ops briefing studio
Weekly practice writing short narratives from messy variance extracts.
FAQ
Do I need SQL or a specific BI tool?
Comfort with spreadsheets and one BI tool (Power BI, Looker, or Tableau) is enough. We focus on definitions and workflows; tool syntax is secondary.
Can I bring my company’s data?
Yes for the mentored seats. Use anonymised extracts. Open cohort exercises use synthetic partner feeds we supply.
What is a real limitation of this course?
We do not implement carrier APIs or configure TMS products for you. If your bottleneck is systems integration labour, you will still need engineering support after the course.
How much time each week?
Plan for five to six hours including live sessions. Module 3 runs heavier if your source data is poorly documented.
Learner notes
Amira’s latency exercise exposed that our “on-time” metric was reading planned ETAs, not confirmed arrivals. Fixing the definition mattered more than any new chart.
★★★★☆ — Solid on frameworks. The partner audit template alone paid for the seat; I still want a deeper SQL lab in a future revision.