Compass — Andon Analytics Page Guide
A monitoring view of operational issues (Andons): volume, status, resolution performance, and main root causes — enabling quick identification of recurring disruptions.
Near Real-Time · Source: TOS / Andon System
---
What this page is for
The Andon Analytics page provides visibility on operational disruptions and issues raised during execution.
It helps teams:
- Track issue volume and resolution status
- Identify recurring problem patterns
- Prioritize root causes for improvement
- Improve response time and operational stability
---
Top Summary KPIs
Total Andons
Total number of issues reported in the selected period
---
Open Andons
Andons currently not yet resolved
---
Under Investigation
Andons being actively analyzed
---
Closed (With / Without Investigation)
- With Investigation → Issues formally analyzed
- Without Investigation → Issues closed directly
---
Avg Andon Time
Average time to resolve an Andon
---
Pareto Analysis (Core of Page)
Pareto by Frequency
Number of Andons
Shows where and how often problems occur
---
Pareto by Duration
Time impact (minutes)
Shows which problems have the biggest operational impact
---
Pareto Structure (3 Levels)
Pareto 1 — WHERE
High-level location of the issue
Examples:
- Transportation
- Yard
- Quay
- Vessel
- Equipment
👉 Answers: Where is the problem happening?
---
Pareto 2 — WHAT
Type or nature of the issue
Examples:
- Waiting
- Breakdown
- Congestion
- Behaviour
👉 Answers: What is the problem?
---
Pareto 3 — WHY
Root cause identified after investigation (5 Whys)
Examples:
- Lack of trucks
- Equipment failure
- Poor planning
- Process gap
👉 Answers: Why did the problem happen?
---
How to use this page
Daily Operations
- Monitor open Andons and ageing issues
- Detect spikes in:
- Specific locations (WHERE)
- Specific issue types (WHAT)
- Escalate long-duration or recurring problems
---
Weekly Review
- Focus on top:
- WHERE (Pareto 1)
- WHAT (Pareto 2)
- WHY (Pareto 3)
- Compare:
- High frequency vs high duration
---
Continuous Improvement
- Start with Pareto 1 → WHERE
- Drill down to Pareto 2 → WHAT
- Confirm root cause in Pareto 3 → WHY
👉 Define corrective actions at WHY level
---
Filters & Controls
- Date Range → Select reporting period
- Shift → Filter by shift
- Andon Type / Status → Focus on specific issues
- Equipment / Vessel → Drill down root causes
---
Important Notes
Data quality: Strongly depends on correct Andon classification
Frequency vs Duration:
Frequent issues ≠ most critical Low-frequency but long-duration issues are high impact
Pareto logic:
Always validate root cause at Pareto 3 (WHY) before taking action
---
APM Terminals · Compass Platform · Andon Analytics Page Guide · v1.0
