Exceptions passed by shouting
Information travels person to person, with repeated back-and-forth between workstations and departments. By the time someone knows, much time has already been lost.
One touch to call, with light, voice and SMS alerts in parallel. Response, handling and confirmation by IC card are fully recorded, and unanswered calls escalate level by level. Exception response moves from gut feeling to enforced, recorded and reportable.
When equipment failures, material shortages or quality issues occur, shouting and intercom calls cannot ensure that someone responds, takes ownership and signs off, let alone measure response times afterwards.
Information travels person to person, with repeated back-and-forth between workstations and departments. By the time someone knows, much time has already been lost.
Nobody answers and nobody follows up. Exceptions drag on into line stoppages, and it is only found afterwards that nobody handled them.
A verbal promise counts as handled, and no cause or method is recorded, so the same problems keep coming back.
There is no data on how long response and blocking take, so management can only judge by feel.
Shop floor terminals raise the call, the server-side rule engine drives the signal tower, intercom voice and SMS, handling is recorded by card throughout, and timeouts escalate automatically level by level.
Built around call, alert, response, escalation and analysis, a closed loop that covers the whole shop floor exception process.
Supports call types such as ME, QA, IE, PE and team leader. Select the product model and describe the exception when calling.
Red when called, blue while being handled after the alarm is cleared, green once production confirms. The status is clear at a glance.
Automatically announces "which line, which workstation is calling which department", broadcast by channel with a configurable repeat count.
Based on shifts and workstation types, only on-duty staff with the matching authority are notified.
Employee cards are bound to call types, so only cards of the department that was called can clear the alarm.
Select the exception cause and solution when handling. A call cannot be closed without them, building a knowledge base of issues.
Unanswered and unclosed calls both escalate level by level up to the manager, and all thresholds are configurable.
Three lists are emailed daily. Call history supports blocked-time statistics, sorting and export.
From spotting an exception to resuming production, each of the four steps (call, response, handling, confirmation) has an owner and a record.
The operator selects the call type and product model, describes the exception and raises the call. The signal tower turns red, the intercom channel announces it and the on-duty staff receive an SMS, all three at once.
The engineer of the called department arrives and swipes their own card to clear the alarm, and the light turns blue. The handler selects an exception cause code and a solution; the call cannot be closed without them, and cards from other departments are invalid.
Production staff swipe a card to confirm completion. If not complete, the call stays in handling; once confirmed, the light turns green and production resumes. The call number, timestamps, the card holder at each step and blocked time are all recorded.
Exception information does not stay at the workstation. The channels complement one another, and when nobody responds, the system automatically escalates one level.
Red, blue and green tower lights show call, handling and recovery status at a glance.
Pre-recorded or synthesized voice, broadcast by channel so everyone can hear it.
Pushed to mobile phones. Based on shifts and workstation types, the right on-duty people are notified.
Day-shift and night-shift staff switch automatically by rule, and SMS goes only to those on duty.
Three lists are emailed daily, and unclosed items are chased again the next day.
If nobody responds, or a responded call stays open too long, the system escalates notifications by threshold, from technicians and team leaders up to engineers, supervisors and the manager. All thresholds are configurable.
Lines, staff, shifts and exception codes are maintained in one place and call data accumulates automatically, so response times can be measured and improved.
Maintain lines and workstation stations, with each workstation bound to a signal tower receiver terminal.
Maintain accounts, roles, departments, positions, phone numbers and employee card numbers. Template import is supported, and day and night shifts switch automatically.
Maintain the exception cause code library, roles and product models as the option sources for calls and handling.
Call numbers combine the date and a serial number, recording product model, call reason and blocked time. SMS sending is fully recorded.
Emailed as Excel attachments. Items left open yesterday continue on the pending list the next day, and management reviews response times from the daily report.
Call history can be sorted by blocked time and exported, quickly locating the longest exceptions to drive improvement.
Hardware and software combined and selected to fit site conditions. Existing equipment can be assessed for integration.
Audible and visual tower light driven through an IO control box with a pluggable control box protocol.
A base station control box works with handsets to announce calls in real time on the matching channel.
Swipe at the workstation. Card numbers are bound to roles, and response, clearing and confirmation rights are mutually exclusive.
The line workstation computer raises calls, handles them and resets, through a simple interface.
Escalation notices and daily lists are delivered through an SMS gateway and an email server.
Rule engine, message routing and data storage, with regular database backups.
The wireless network carries the intercom, and the production network carries call signals and data.
Can be linked with MES, QMS and EAM, feeding exception handling data back into quality and equipment analysis.
For manufacturing shop floors with many lines and exception types that need fast cross-department response.
Equipment failures, placement pickup errors and material shortages are called in with one touch, and engineers swipe their card on arrival to handle them.
Missing materials and quality issues call the matching department by type, and causes are kept on file.
Notified staff switch automatically between day and night shifts, so night exceptions are also answered and chased.
Blocked time and daily lists are used to evaluate each department's response speed and drive continuous improvement.
Common questions on response assurance, permission control and hardware configuration.
A call triggers the signal tower, intercom voice announcement and SMS notification at the same time. If nobody responds within the set time, the system escalates level by level up to the manager. All thresholds are configurable.
Employee card numbers are bound to call types, so only cards of the department that was called can clear the alarm. The handler must select an exception cause and a solution, and production staff must confirm by card before the call can be closed.
The system switches between day-shift and night-shift staff automatically according to the shift plan. SMS goes only to the staff on duty, and notifications can be targeted by workstation type and intercom channel.
A typical setup includes a three-color signal tower with control box, an intercom base station and handsets, IC card readers, workstation terminals and an SMS gateway. Existing on-site equipment can be assessed for reuse, and not every component is mandatory.
Light, voice and SMS alerts, a card closed loop and timeout escalation build shop floor exception response that is enforceable, traceable and measurable.
Follow & Contact Us
Copyright © 2019-2026 Shanghai Hegong Software Co., Ltd.
Shanghai Public Security No. 31011502014114
Shanghai ICP No. 19036824-1