Identify the robot and control system first
A robot model alone does not fully describe the system. Record manipulator and controller information separately, with readable nameplates and version details.
- Brand, full model, serial number, controller model and system version.
- Tooling, external axes, relevant peripherals and known software options.
- Dates of available backups, maintenance records and recent repair records.
How should alarms and symptoms be recorded?
A complete event record is more useful than a keyword. Describe events in sequence, distinguish observations from assumptions, and avoid treating an alarm name as proof that a particular component has failed.
- Full event number, message, timestamp and adjacent events, rather than a cropped fragment.
- Operating mode, process or motion at the time, and whether the symptom recurs.
- Recent changes to tooling, parts, programs, loads, components or site conditions.
How are remote and on-site services scoped?
The service format depends on available evidence, local support and the work required. For overseas requests, specify location, downtime window, contact language and support available on site.
- The function to restore and the current impact on production.
- Available inspection windows, site personnel and access to equipment information.
- Whether assessment, labour, travel, parts, installation and commissioning are quoted separately.
What should be handed over after service?
Agree records and recovery checks before service. Appropriate personnel should perform repairs and tests using applicable manuals and site requirements; a web lookup does not replace equipment inspection.
- Findings, work performed, full replacement-part numbers and configuration changes.
- Actual test conditions, results, unresolved issues and follow-up recommendations.
- Agreed backups, maintenance records and the statement of completed service scope.
Common questions
Is “the robot reports collision supervision” enough?
It is a useful starting point, but not enough to identify the cause or a replacement part. Add the full event number, robot and controller details, active motion and recent tool or program changes. For ABB IRC5, start with the relevant manual entry.
Can overseas customers request remote support?
Overseas customers can request remote support. Suitability, required site assistance, scheduling and fees are confirmed from the equipment and fault information.
Can an alarm lookup directly identify the part to replace?
A lookup result alone cannot justify replacement. Event entries support interpretation and manual review; a repair decision also needs configuration details, inspection evidence and applicable documentation.