Module 3’s exception queue rubric is taped beside our monitors. Capstone feedback called out my overconfident colour scale — fair.
Flagship programme
Route Signal Studio
Eight weeks of guided practice inside a Data Visualization and Analytics Platform for Logistics Route Analytics — ending with a briefing your stakeholders can actually use.
Learning outcomes
- Audit a route board for misleading averages and silent filter debt.
- Build corridor charts that separate congestion from capacity and access friction.
- Design an exception queue with thresholds your ops lead will defend.
- Deliver a one-page weekly narrative tied to cost and service promise.
Informational pricing
Corridor Desk seating for this programme is listed at RM 3,450 per learner. Team circles and private datasets are quoted separately. No payment is processed on this website.
Modules
01
Signal hygiene
GPS gaps, scan lag, and how dirty inputs masquerade as insight.
02
Corridor charts
Lane composition, time-of-day slices, and monsoon-aware comparisons.
03
Exception queues
Sorting rules, ownership, and retiring vanity red alerts.
04
Cost & service overlays
Connecting overtime risk and promise windows without spreadsheet theatre.
05
Filter debt clinic
Find saved views that lie politely — then document safer defaults.
06
Briefing craft
One-page Monday narratives with a required “what we still don’t know” line.
07
Live critique lab
Peer review of your board with instructor scoring on clarity, not polish.
08
Capstone defence
Present to a mock stakeholder panel; revise once based on feedback.
Instructor
Amira Khoo
Former network analyst for a Malaysia-based 3PL, Amira now coaches desks on reading corridor data under time pressure. She leads Route Signal Studio labs and grades capstone briefings.
FAQ
Do I need our production data?
No. The sandbox is enough to complete every module. You may optionally bring anonymised samples for office hours.
Is this a vendor certification?
No. We teach reading and briefing habits that transfer across platforms. Tool buttons differ; the critique criteria stay stable.
What is a real limitation of this programme?
We do not rewire your TMS integrations or build production dashboards for you. If your data pipeline is broken, we can diagnose symptoms in class, but fixing pipelines remains an engineering project outside the syllabus.
How much live time each week?
Plan for two 90-minute labs plus roughly three hours of solo platform practice.
Reviews from this course
★★★★☆ · Worth the Tuesday mornings. I wanted more night-haul Malaysia samples in Module 4, but the briefing template in Module 6 carried the desk.