Support
Escalation
A practical route for escalations on South African plant floors, for teams dealing with stoppages, hold-ups or disputed fault causes.
How Escalation moves through plant support
Escalation is for plant stoppages, production hold-ups and fault disputes that need a clean record of what happened. This page sets out a practical route for South African teams who need the issue defined before the floor loses more time.
When a line stops, first note the unit, the product in process, and the exact point where output broke down. Conditions across South African plants change the record straight away. Highveld dust can hide witness marks, coastal humidity can affect panels and connectors, and load-shedding can split one incident into several separate events.
Take the first images before parts are moved, guards are opened, or settings are reset. The escalation pack should tie those images to shift time, machine tag, and the names of people present at the stop. That record matters later when maintenance, production and suppliers remember the same event differently.
Evidence kept from first stop
The output is a dated incident trail, a short fault outline, and a list of checks still outstanding. It gives the plant a single version of what was seen on site, rather than several verbal accounts passed between shifts. For disputed causes, that written sequence is often more useful than another long meeting around the machine.
Link the escalation record to the relevant machine file and any prior support history before more people are added to the issue. Check serial numbers, alarm codes, and operator notes once more before submitting the contact form. Include one clear photo of the affected area as it stood at the time of the stop.
- Incident log tied to one stoppage
- Photos taken before adjustments begin
- Related: Systems, Plant plays, and Floor notes
- Named record for supplier disputes
Plant conditions that change evidence
A stoppage in Jet Park does not read the same as one in Prospecton or Epping. Dust, moisture, product type, and forklift traffic all change what can be trusted as evidence. On older sites with modified panels or undocumented changes, the escalation note should state clearly what is original, what was added later, and what could not be verified during the visit.
Near the coast, corrosion on terminals and enclosures can confuse an electrical fault review. Inland sites often deal with fine dust on sensors, belts and photo eyes, which can make a minor issue look like a major equipment failure. During power interruptions, record whether the stop happened before the drop, at restart, or after backup supply changed over.
Operated by Astros Marketing (Pty) Ltd from 2 Makro Place, Sunnyrock 1401.
Evidence packed before reset
Send the machine name, plant location, shift, and a brief note on what production was running when the event started. Add any alarm text exactly as shown on the HMI, plus photos of damaged parts, rejected product, or tripped protection devices. If someone has already reset the equipment, say so plainly in the first note.
| Path | escalation |
|---|---|
| Hub | support |
| Mailbox | Contact form |
File the escalation note with the maintenance log and the production record for that same shift. Procurement may also need the same pack when a fault cause is disputed between plant staff and an outside supplier. One complete record is easier to test against invoices, service reports and replacement-part requests.