A: A production management Andon system is essentially an "exception call button plus response timer" within the workshop. When a worker presses a button, the system records where the problem occurred, who is responsible for handling it, and how long it takes to arrive, creating a complete audit trail. While it does not directly repair equipment, it exposes the hidden costs associated with line stoppage and waiting times. Implementation can follow these steps.
Step 1: Define trigger points. Do not deploy across all workstations immediately. Instead, start by selecting bottleneck processes or high-frequency exception points. Common signals include material supply interruptions, quality alarms, and equipment failures, which correspond to three-color lights or terminal buttons.
Step 2: Establish the response chain. Once an Andon signal is triggered, it must automatically route to the designated responsible person, such as a team leader, material handler, or maintenance technician. The notification terminal can be a workstation screen, a workshop Kanban board, or a mobile device. The key requirement is to clearly define who accepts the task and the specific timeframe for arrival.
Step 3: Set escalation rules. If the response time limit is exceeded, the alert should automatically escalate up the hierarchy. For example, if a task remains unhandled after five minutes, it escalates to the workshop supervisor; if unhandled after fifteen minutes, it escalates to the production manager. This prevents situations where alerts are issued but ignored.
Step 4: Aggregate data for review. Details of each alert, including the trigger cause, response duration, and resolution outcome, are recorded in the WIP quality Kanban. Weekly meetings should utilize this data to identify recurring exceptions and drive improvements.
Important considerations: The greatest risk of an Andon system is that alerts become ineffective ("pressing without result"). An unimplemented response mechanism can damage morale more than having no system at all. Additionally, the system must integrate data with existing MES or enterprise-level upstream management systems to avoid information silos. It is recommended to pilot the process on a small scale first to ensure smooth operations before gradually expanding to the entire workshop.