Treat AUR31220 as a scenario-driven trade qualification. Study each mobile plant system — hydraulics, drivetrain, undercarriage, electrics, engines — by working paper-based faults end to end: confirm the symptom, isolate the machine, gather measurements, compare against manufacturer specification, repair, verify, and document. Build a fault tree for one system per study cycle, score yourself against a rubric, and repeat. Practice on paper and supervised tasks; confirm current unit and administrative requirements through the issuer listing on training.gov.au.
How AUR31220 scope differs from light vehicle training you may already have
AUR31220 is oriented to servicing and diagnosing mobile plant — excavators, loaders, dozers, and agricultural machinery — where technical faults, stored energy, and trade documentation must be handled together.
The qualification's domain covers engines, drivelines, hydraulic circuits, undercarriage and track systems, electrical systems, and braking on heavy mobile equipment used in construction, mining, and agriculture. Competency is demonstrated through applied tasks and scenario-style assessment, so studying isolated definitions is not enough. You need to connect a symptom to a diagnostic pathway, a safe work sequence, and a written record in one continuous piece of reasoning.
The habits that carry over from light vehicle work — quick part substitution, short access times, low stored energy — translate poorly to plant. A tracked excavator has modular cylinders, load-hold valves, accumulators, and planetary final drives that hold force after shutdown. Build your study around that difference: every fault you review should include a step where you identify what energy remains in the system and how you would control it before touching components.
- Machine types in scope: tracked and wheeled earthmoving plant, loaders, dozers, and agricultural machinery.
- Assessment style: applied demonstrations and scenario analysis rather than isolated recall.
- Key habit to build early: identify stored energy sources — raised attachments, accumulators, track tension — before any hands-on step.
Why systematic fault diagnosis beats part swapping on mobile plant
Use a structured diagnostic sequence — verify, gather, analyse, test, repair, verify again — instead of substituting components, because plant faults often span multiple interacting systems.
A named process gives your study a spine: confirm the fault exists as described; gather information from the operator's report, fault codes, and machine history; list plausible causes; test each cause with a measurement compared against the manufacturer's specification; carry out the repair; then verify the original symptom is gone and record what was done. Practise writing each step explicitly, because scenario assessment rewards a traceable chain of reasoning, not a lucky guess.
Part swapping is especially costly on plant. Accessing a swing motor or a transmission control valve can take hours before you learn the component was healthy, and a single symptom — slow cycle times, for example — can originate in the pump, the control valve, the filter, the cooler, or the electrical signal controlling them. When you review any system, ask which two or three measurements would separate the most likely causes, and in what order you would take them.
Open-center versus closed-center hydraulics and what stored pressure means for you
Know how open-center and closed-center circuits behave at standby, because the difference changes both your diagnostic measurements and the depressurisation steps you take before work.
In an open-center circuit, pump flow circulates back to tank through the open center of the control valve when no function is demanded, so standby pressure is low and flow is roughly constant. In a closed-center circuit, a variable-displacement pump produces flow only on demand, with a compensator or pressure-limiting element governing standby conditions. This changes diagnosis: standby and load-pressure test points, and what 'normal' reads, differ between the two designs, so identify the circuit type before interpreting any gauge reading.
Stored energy is the safety thread running through every hydraulic topic. Raised booms, charged accumulators, and relief valves holding pressure can act after the engine stops. In your study scenarios, always include the control steps: lower or support the attachment, follow the machine's depressurisation procedure for accumulators and lines, and treat every line as pressurised until proven otherwise. Keep this as a written habit on paper scenarios so it becomes automatic in supervised workshop tasks.
| Feature | Open-center circuit | Closed-center circuit |
|---|---|---|
| Pump at standby | Full flow returns to tank through the open center spool | Pump destrokes to near-zero flow on demand control |
| Standby pressure | Low; pressure rises only when a function is used | Held near compensator or relief setting |
| Diagnostic implication | Check flow path and valve spool condition; relief is the main pressure limit | Read standby and load-sensing pressures; compensator faults mimic pump faults |
| Safety implication | Depressurise lines and support any raised load before work | Same, plus isolate and bleed accumulators per the machine's procedure |
Worked scenario 1: boom drift on a parked excavator
A raised boom slowly settles overnight. The better decision is a held-pressure diagnosis with the machine isolated — not an immediate seal or valve replacement.
Scenario: an operator reports that the boom settles noticeably over a shift break with the bucket loaded. Plausible mistake: order cylinder seal kits and a replacement main control valve straight away. That approach assumes the leak path, ignores what else can cause drift — the load-hold (port) valve, pilot system leakage, or even a misread symptom — and commits expensive parts before testing.
The better decision: verify the symptom under controlled conditions, lower and isolate the machine, support the attachment, then test systematically — inspect for external leaks, isolate the cylinder by a manufacturer-approved hold or line-isolation check to see whether drift stops, and compare pilot and load-hold valve behaviour against specification. Why it matters: a cylinder that holds pressure when isolated points to the circuit side, not the seals, and swapping parts would leave the real fault in place. Write the sequence as a job card entry so the reasoning is auditable.
Worked scenario 2: hydraulic oil overheating on a wheel loader
Overheating is a symptom, not the fault. The better decision is to separate heat generation from heat rejection and document measurements, rather than fitting a bigger cooler or changing oil.
Scenario: a wheel loader's hydraulic oil runs hot during normal loading cycles, and the machine has just been serviced. Plausible mistake: change the oil, clean the cooler, and close the job. If a relief or unloading element is stuck and dumping flow continuously — a common heat-generation cause — the oil will heat again immediately, and the service record will suggest the fault was fixed when it was not.
The better decision: split the problem in two. Heat generation: measure standby pressure and check whether the circuit is working over relief during neutral operation. Heat rejection: inspect the cooler core, airflow path, and bypass element. Compare each reading against the machine's specification, repair the confirmed cause, re-test under load, and record pressures before and after on the job card. Why it matters: the documentation shows the fault was located by measurement, which is the standard of trade reasoning this qualification is built around.
A fault-tree exercise with a self-check rubric
Build a written fault tree for one machine system per study cycle and score it against a rubric; expected observations include fewer skipped verification steps by your third tree.
Exercise: choose one system — the excavator boom circuit, a loader driveline, a dozer track frame — and draft a fault tree from symptom to verified repair on paper. Use supplied or textbook example values for any readings in the example so you practise comparing measurements to a stated specification rather than inventing thresholds. Then hand the tree to a classmate or trainer and have them challenge each branch: does every test actually separate the causes above it?
Expected observations: your first tree will likely jump from symptom to a single cause; by the third, you should automatically include symptom verification, isolation steps, at least three ranked causes, and a final verification test. Rubric (score each 0–2, total out of 10; this is a learning milestone, not a pass prediction): symptom confirmed as described; energy isolation stated before intervention; three or more plausible causes ranked; each test tied to a measurement and expected value; verification and documentation step present.
- Step 1: pick one system and write the symptom exactly as an operator would report it.
- Step 2: branch into at least three plausible causes, ranked by likelihood and test cost.
- Step 3: attach a measurement and an example expected value to every test.
- Step 4: include isolation and depressurisation steps before any component work.
- Step 5: finish with verification and a draft job card entry, then score against the rubric.
An adaptable preparation sequence and concrete readiness checks
Sequence your study in four phases — scope mapping, paired systems learning, weekly paper scenarios, and full self-checks — and finish only when you can run the whole diagnostic-and-documentation chain unaided.
A realistic, adaptable sequence: first, map the qualification's scope from the issuer listing so your notes track the actual domain areas. Second, learn systems in pairs — hydraulics with circuit safety, driveline with undercarriage — so each technical topic is immediately linked to its safe-work counterpart. Third, run one paper scenario per week using the fault-tree exercise above. Fourth, close with full self-checks under time limits, writing job card entries rather than bullet notes.
Readiness checks before you consider yourself prepared: you can state the isolation and depressurisation steps for a raised attachment from memory; you can complete a fault tree with the rubric scoring 8/10 or better unaided; you can explain open-center versus closed-center behaviour in your own words with a sketch; and you can produce a job card entry with measurements, specification references, and verification results. If any check fails, return to that system's paired study rather than rereading everything.
- Phase 1: map scope areas against the issuer listing and allocate study time per area.
- Phase 2: study technical systems paired with their safety and documentation practices.
- Phase 3: one written fault-tree scenario per week, scored with the rubric.
- Phase 4: full unaided self-checks, including timed job card writing.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.
