Generator and electric motor maintenance process map

What is in this map

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

Swimlanes (who does the work)

ServiceDesk, Field Electrical, Test & Inspection and Engineering

Phases (left to right)

Intake, Inspection, Testing, Repair and Verification

Why map this process

The map's honesty is in what it does NOT do on every visit. The vibration-analysis decision is explicit that a survey is called for on larger or critical machinery, a unit with a vibration history, or when the electrical and mechanical tests didn't fully explain a symptom — and that a named role makes that call rather than a fixed checklist. A template that ran vibration analysis on every generator regardless of size or history would overstate the cost of a simple job and understate the diligence a genuinely tricky one needs.

The test-run decision at the end loops a failure back to diagnosis, not to a 'noted exception.' The row's own comment makes the stakes plain: a unit that runs hot or rough on the test bench does the same thing back in service, except by then the customer is depending on it. Keeping that as a hard loop rather than a sign-off with caveats is what stops a marginal repair from shipping.

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.

• 6. *Vibration analysis* required?

  Owned by Test & Inspection · Testing

  • Yes → step 7
  • No → step 8

• 12. Test run within **acceptable limits**?

  Owned by Test & Inspection · Verification

  • Pass → step 13
  • Fail → step 9

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. Service request received for generator or motor

May come in as a scheduled maintenance visit, a customer call about a running fault, or a finding carried over from an Electrical Inspection & Testing SOP report. Whichever it is, the equipment gets identified before anyone opens it up.

2. Identify equipment: type, rating and service history

Nameplate data (kW/kVA rating, RPM, voltage class) and prior maintenance records are pulled before a technician is dispatched, so the visit starts from what is already known about the unit rather than a blank sheet.

6. *Vibration analysis* required?

Not every visit gets a vibration survey — it's called for on larger or critical rotating machinery, a unit with a history of vibration complaints, or when the electrical and mechanical tests above didn't fully explain a reported symptom. Anders Vane makes the call, not a fixed checklist.

7. Perform vibration analysis and shaft alignment survey

The vibration spectrum flags bearing wear, misalignment or looseness before the unit is opened up, so the teardown targets the actual fault instead of every part that could plausibly be worn.

9. Repair or replace windings, bearings and electrical components

Scope ranges from a bearing swap to a full rewind, set by the diagnosis above rather than a standard repair kit applied regardless of what's actually wrong.

12. Test run within **acceptable limits**?

A fail routes straight back into repair rather than becoming a noted exception — a generator or motor that runs hot or rough on the test bench does the same thing back in service, only with the customer depending on it by then.

13. Issue **maintenance report** with test and alignment data

Carries the before/after insulation resistance readings, vibration spectra where a survey was run, and alignment figures, so the next service call starts from a documented baseline instead of a technician's memory.

Making it yours

Phases (Intake, Inspection, Testing, Repair, Verification) run Horizontal lane; the four roles run Vertical lane. When adapting the intake row, keep its three possible origins in the Notes column — scheduled maintenance, a customer fault call, or a referral carried over from the Electrical Inspection & Testing SOP — because how the job arrived changes what 'identify equipment: type, rating and service history' actually needs to pull up.

What to watch out for

• Don't fold electrical tests (insulation resistance, winding resistance, continuity) and mechanical tests (bearing condition, shaft runout, alignment) into one 'testing' row. They're run by different roles in this map on purpose, and a fault that's actually mechanical will not show up in an electrical-only test pass.
• Keep the vibration-analysis decision even on jobs where you're confident it isn't needed. The point of drawing it as a decision, not a step everyone skips past, is that the reasoning for skipping it (small unit, no history, symptom already explained) is visible and repeatable rather than left to whoever's on the job that day.
• Don't let the maintenance report skip the before/after readings. The map's comment on that row is specific: insulation-resistance readings, vibration spectra where a survey ran, and alignment figures, filed so the next service call starts from a documented baseline instead of a technician's memory.

Frequently asked questions