Emergency instrument troubleshooting process map

What is in this map

14 steps across 4 swimlanes and 5 phases, with 2 decision points.

Swimlanes (who does the work)

ServiceDesk, Field Service, Calibration Lab and Engineering

Phases (left to right)

Intake, Diagnosis, Impact & Response Decision, Resolution and Verification & Closeout

Why map this process

A customer reporting an emergency almost never names the instrument at fault; they report an unstable reading or a process behaving wrong, which is why this map puts 'diagnose which instrument or measurement is implicated' as its own row before urgency is assessed at all. Skipping straight to a safety-and-impact judgement on a vague symptom risks over- or under-reacting to a problem nobody has actually located yet.

Separating the safety/impact assessment from the remote-vs-dispatch decision, rather than folding them into one judgement call, is what lets the map treat a safety-instrumented loop differently from a nuisance reading without inventing a second process for it. Confirming whether the implicated loop is safety-instrumented or production-critical happens before the remote call, not after — so an escalation is never made based on how a technician feels about the fix, only on what the loop actually protects.

Every step in the map

This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.

The decision points

Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.

• 5. *Remote troubleshooting* sufficient?

  Owned by Field Service · Impact & Response Decision

  • Yes → step 6
  • No → step 7

• 11. Fault **confirmed resolved?**

  Owned by Field Service · Verification & Closeout

  • Yes → step 13
  • No → step 12

Notes on specific steps

These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.

1. Customer reports process problem

Usually reported as an unstable reading or a process behaving wrong, not as a named instrument fault. Which measurement is actually at fault is not yet known at this point.

3. Diagnose which instrument or measurement is implicated

At intake the customer rarely knows which loop is at fault. This step narrows the reported symptom to a specific transmitter, sensor or measurement loop before urgency or a response method is decided.

4. Assess **safety and production impact** and urgency

Confirms whether the implicated loop is safety-instrumented or production-critical. This is decided before the remote-vs-dispatch call, not after it.

8. Prepare calibrated spare instrument and reference equipment

For a safety-instrumented loop this is a straight swap from calibrated lab stock rather than a field repair attempt, so the customer gets a trustworthy measurement back fastest.

12. **Escalate** to engineering for further diagnosis

Brought in when the first fix does not hold. Re-diagnosis with specialist input against the same process data, not a repeat of the standard first pass.

Making it yours

The escalation loop at row 12 sends an unresolved fault back to row 3, re-diagnosis, rather than repeating the remote-vs-dispatch decision from scratch. When adapting this chart, keep that distinction: a fault that does not hold after the first fix needs fresh diagnosis with specialist input against the same process data, not a second pass through the same triage the first attempt already used.

What to watch out for

• Do not treat 'prepare calibrated spare instrument' as a bench task separate from dispatch. For a safety-instrumented loop this map specifies a straight swap from calibrated lab stock rather than a field repair attempt, precisely because the customer needs a trustworthy measurement back fastest — a repair attempt on safety-critical instrumentation under emergency time pressure is the wrong trade.
• The confirm-resolved decision (row 11) is not optional even when the instrument reads correctly again. A reading that looks right immediately after a fix is not the same as a fault confirmed resolved — the map tests and confirms before it lets the process move to closing the case with the customer.
• Do not skip the safety/impact assessment for a fault that seems obviously minor at intake. It runs before the remote-vs-dispatch decision specifically because an assessment made after choosing the response method is circular — it would only ever confirm the response already chosen.

Frequently asked questions