On-Site Problem Rapid Response: Andon System Design
The Andon system is the "alarm" of on-site management—making problems visible and ensuring timely responses.
<h2 id="section1">1. Overview of the Andon System</h2>
<p>The Andon system originates from the Toyota Production System and is a mechanism for rapid on-site problem response. When an abnormality occurs during production, operators trigger an alarm by pulling a cord or pressing a button, which sends audio-visual signals to notify relevant personnel, ensuring that issues are addressed as quickly as possible.</p>
<div class="tip-box">
<div class="tip-title">Core Principles of Andon</div>
<ul>
<li><strong>Problem Visualization</strong>: Make abnormalities visible.</li>
<li><strong>Immediate Response</strong>: Respond immediately when a problem occurs.</li>
<li><strong>Transparent Management</strong>: Clearly identify who is responding and the response time.</li>
<li><strong>Root Cause Analysis</strong>: Address not just the symptoms but the root causes.</li>
</ul>
</div>
<h2 id="section2">2. Core Value of the Andon System</h2>
<div class="data-table">
<table>
<thead> <tr><th>Value Dimension</th><th>Specific Benefits</th> </tr></thead>
<tbody>
<tr><td rowspan="2">Quality</td><td>Immediate line stoppage upon problem detection to prevent nonconforming products from leaving the line.</td> </tr>
<tr><td>Complete abnormality records for root cause analysis.</td> </tr>
<tr><td rowspan="2">Efficiency</td><td>Reduced abnormality response time, minimizing line stoppage losses.</td> </tr>
<tr><td>Transparent problem resolution process for better management.</td> </tr>
<tr><td rowspan="2">Management</td><td>Accumulation of abnormality data to identify improvement opportunities.</td> </tr>
<tr><td>Cultivation of a quality mindset among employees to stop the line when issues arise.</td> </tr>
</tbody>
</table>
</div>
<h2 id="section3">3. Design Elements of the Andon System</h2>
<div class="step-card">
<h3><span class="step-number">1</span> Trigger Methods</h3>
<p>Pull cords, buttons, voice commands, and automatic detection (e.g., SPC out-of-limits triggers).</p>
<h3><span class="step-number">2</span> Signal Transmission</h3>
<p>Audio-visual alarms (buzzers + indicator lights), kanban displays, SMS/APP notifications.</p>
<h3><span class="step-number">3</span> Response Levels</h3>
<p>Operator → Team Leader → Engineer → Workshop Manager, escalating step-by-step.</p>
<h3><span class="step-number">4</span> Problem Documentation</h3>
<p>Record the trigger time, response time, closure time, problem type, and handler.</p>
<h3><span class="step-number">5</span> Statistical Analysis</h3>
<p>Analyze the frequency of abnormalities, response times, and problem types.</p>
</div>
<h2 id="section4">4. Abnormality Response Process Design</h2>
<div class="timeline">
<div class="timeline-item">
<div class="timeline-dot"></div>
<div class="timeline-date">Step 1: Abnormality Occurs</div>
<p>The operator detects an abnormality (such as equipment failure, quality issues, or material shortages).</p>
</div>
<div class="timeline-item">
<div class="timeline-dot"></div>
<div class="timeline-date">Step 2: Andon Triggered</div>
<p>The operator pulls the cord or presses the button, initiating the audio-visual alarm, which displays the location and type of abnormality on the kanban.</p>
</div>
<div class="timeline-item">
<div class="timeline-dot"></div>
<div class="timeline-date">Step 3: Response Confirmation</div>
<p>The team leader arrives at the scene within 30 seconds, confirms the issue, and records the start time of the abnormality.</p>
</div>
<div class="timeline-item">
<div class="timeline-dot"></div>
<div class="timeline-date">Step 4: Problem Handling</div>
<p>The team leader handles the issue on-site. If it cannot be resolved within 5 minutes, it is escalated to the engineer or workshop manager.</p>
</div>
<div class="timeline-item">
<div class="timeline-dot"></div>
<div class="timeline-date">Step 5: Production Resumption</div>
<p>After the issue is resolved, the Andon is turned off, the closure time is recorded, and production resumes.</p>
</div>
<div class="timeline-item">
<div class="timeline-dot"></div>
<div class="timeline-date">Step 6: Root Cause Analysis</div>
<p>Post-shift analysis of the abnormality causes, formulation of corrective and preventive actions, and updating of FMEA/control plans.</p>
</div>
</div>
<h2 id="section5">5. Response Time Metrics Setting</h2>
<div class="data-table">
<table>
<thead> <tr><th>Metric</th><th>Target Value</th><th>Description</th> </tr></thead>
<tbody>
<tr><td>Response Time</td><td>≤30 seconds</td><td>Time from Andon trigger to personnel arrival at the scene.</td> </tr>
<tr><td>Handling Time</td><td>≤5 minutes</td><td>Time from arrival at the scene to issue resolution.</td> </tr>
<tr><td>Escalation Time</td><td>≤5 minutes</td><td>Time for escalation if the issue is not resolved.</td> </tr>
<tr><td>Closure Time</td><td>≤10 minutes</td><td>Total time from trigger to complete resolution.</td> </tr>
<tr><td>Response Rate</td><td>100%</td><td>Whether all Andon triggers receive a response.</td> </tr>
<tr><td>Escalation Rate</td><td>≤10%</td><td>The proportion of issues requiring escalation.</td> </tr>
</tbody>
</table>
</div>
<div class="tip-box">
<div class="tip-title">Monitoring Response Metrics</div>
<p>Statistically track Andon data daily, plot response time trend charts, and conduct root cause analysis for events that exceed the response time.</p>
</div>
<h2 id="section6">6. Hardware Configuration for the Andon System</h2>
<div class="case-card">
<div class="case-title">Basic Configuration</div>
<ul>
<li>Pull cord switches/buttons (one per workstation)</li>
<li>Audio-visual alarm lights (red/yellow/green)</li>
<li>Workstation kanban (displays abnormality status)</li>
<li>Workshop large screen (displays status of all workstations)</li>
</ul>
</div>
<div class="case-card">
<div class="case-title">Advanced Configuration</div>
<ul>
<li>Wireless Andon terminals (portable)</li>
<li>Smart watches/bands (worn by response personnel)</li>
<li>Andon management software (for data recording and analysis)</li>
<li>SMS/APP notifications (for remote alerts)</li>
</ul>
</div>
<h2 id="section7">7. Digital Andon System</h2>
<div class="step-card">
<h3>Functions of a Digital Andon System</h3>
<ul>
<li><strong>Real-time Monitoring</strong>: Large screens display the status of all workstations (green for normal, yellow for call, red for stoppage).</li>
<li><strong>Automatic Recording</strong>: Automatic recording of trigger time, response time, and closure time.</li>
<li><strong>Automatic Escalation</strong>: Automatic notification to superiors if there is no timely response.</li>
<li><strong>Data Analysis</strong>: Automatic generation of abnormality statistics and response time reports.</li>
<li><strong>Mobile Viewing</strong>: Real-time viewing of on-site status on mobile devices.</li>
</ul>
</div>
<div class="data-table">
<table>
<thead> <tr><th>Digital Function</th><th>Traditional Andon</th><th>Digital Andon</th> </tr></thead>
<tbody>
<tr><td>Data Recording</td><td>Manual recording</td><td>Automatic recording</td> </tr>
<tr><td>Response Statistics</td><td>Manual statistics</td><td>Automatically generated reports</td> </tr>
<tr><td>Escalation Mechanism</td><td>Manual notification</td><td>Automatic escalation</td> </tr>
<tr><td>Mobile Viewing</td><td>On-site viewing</td><td>Real-time mobile viewing</td> </tr>
<tr><td>Analysis and Early Warning</td><td>Post-event analysis</td><td>Real-time early warning</td> </tr>
</tbody>
</table>
</div>
<h2 id="section8">8. Case Study: Implementation of an Andon System in an Electronics Factory</h2>
<div class="case-card">
<div class="case-title">Case Background</div>
<p><strong>Company</strong>: An electronics assembly factory with 200 employees, primarily producing power adapters.</p>
<p><strong>Problems Before Implementation</strong>:</p>
<ul>
<li>Employees had to search for help after an abnormality, leading to an average response time of 8 minutes.</li>
<li>Incomplete abnormality records made root cause analysis difficult.</li>
<li>Recurring issues were not followed up.</li>
<li>Severe line stoppage losses, approximately 20 hours per month.</li>
</ul>
</div>
<div class="case-card">
<div class="case-title">Implementation Process</div>
<ul>
<li><strong>Hardware Deployment</strong>: Installation of Andon pull cords and audio-visual alarm lights on 12 production lines, with a large screen display in the workshop.</li>
<li><strong>Process Design</strong>: Clear definition of the response process and response time metrics.</li>
<li><strong>Personnel Training</strong>: Training of 200 operators, team leaders, and engineers.</li>
<li><strong>Trial Operation</strong>: A two-week trial period to optimize the process.</li>
<li><strong>Full-scale Rollout</strong>: Formal implementation, with performance evaluations tied to Andon response times.</li>
</ul>
</div>
<div class="case-card">
<div class="case-title">Implementation Results</div>
<div class="data-table">
<table>
<thead> <tr><th>Metric</th><th>Before Implementation</th><th>After Implementation</th><th>Improvement</th> </tr></thead>
<tbody>
<tr><td>Average Response Time</td><td>8 minutes</td><td>32 seconds</td><td>↓93%</td> </tr>
<tr><td>Average Handling Time</td><td>15 minutes</td><td>4 minutes</td><td>↓73%</td> </tr>
<tr><td>Monthly Line Stoppage Time</td><td>20 hours</td><td>3 hours</td><td>↓85%</td> </tr>
<tr><td>Completeness of Abnormality Records</td><td>30%</td><td>98%</td><td>↑227%</td> </tr>
<tr><td>Recurring Issue Rate</td><td>40%</td><td>12%</td><td>↓70%</td> </tr>
</tbody>
</table>
</div>
</div>
<div class="case-card">
<div class="case-title">Lessons Learned</div>
<ul>
<li>The Andon system is a management tool, not just equipment—hardware is the tool, but the process is the core.</li>
<li>Response times must be evaluated—otherwise, the Andon system may become a mere decoration.</li>
<li>Root cause analysis is essential—without it, issues will recur.</li>
<li>Data should be reviewed regularly—use data to drive continual improvement.</li>
</ul>
</div>
<h2 id="section9">9. Common Issues and Pitfall Avoidance Guide</h2>
<ul>
<li><strong>Issue 1: The Andon System Becomes a Decoration</strong><br>→ Solution: Integrate Andon response performance into performance evaluations.</li>
<li><strong>Issue 2: Employees Reluctant to Trigger the Andon</strong><br>→ Solution: Foster a culture where triggering the Andon is not penalized, encouraging the exposure of issues.</li>
<li><strong>Issue 3: Recording Without Analysis</strong><br>→ Solution: Hold weekly Andon analysis meetings to identify root causes.</li>
<li><strong>Issue 4: Delayed Responses</strong><br>→ Solution: Set automatic escalation for overdue responses, with superiors held accountable.</li>
<li><strong>Issue 5: Recurring Issues</strong><br>→ Solution: Maintain a corrective action tracking log, ensuring no issues are left unresolved.</li>
<li><strong>Issue 6: High Hardware Failure Rate</strong><br>→ Solution: Regular maintenance and integration into equipment management.</li>
</ul>
<div class="highlight-box">
<div class="tip-title">Andon System Toolkit</div>
<ul>
<li>Andon system implementation planning template</li>
<li>Abnormality response process standards</li>
<li>Andon record form template</li>
<li>Abnormality statistics report template</li>
<li>Andon system training materials</li>
</ul>
</div>