AUSTRALIAN MANAGEMENT. GLOBAL CAPABILITY.12-month work warranty →
CDXCAD & DOCUMENTATION EXPERTISE
Let’s talk ↗

HOME / ACADEMY

CDX Academy

← All 40 lessons

Parts and assets · Lesson 20 · Approx. 7 minutes including practice

Spare parts descriptions

Descriptions should help a reader distinguish parts while the identifier remains the primary key. Use consistent terminology and approved attributes. Avoid commercially ambiguous shorthand and unverified equivalent supplier references.

Follow the information flow

Step 1: Approved identifier

A documentation workflow, not an equipment operating sequence. Animation starts only when you choose Play.

Write descriptions that distinguish items

A good description helps a reader recognise the item while the approved identifier remains the primary key. Agree a consistent order for attributes, such as component type followed by distinguishing size or material where those attributes are approved and relevant. Avoid vague terms like standard fitting or seal kit without context. Do not add an attribute just because it appears typical for similar products; uncertain attributes should remain flagged for confirmation.

Prepare and check the work

Build a small terminology list and test it against difficult cases, including similar parts and supplier naming differences. Keep manufacturer references separate from internal descriptions so a change in wording does not break the ordering link. Explain abbreviations and avoid using one abbreviation for different concepts. Review units of supply, left/right orientation and configuration notes where they affect selection.

Worked example · demonstration only

Two washers have the same short description but different approved dimensions. Add the distinguishing approved attributes and preserve their separate identifiers. Merging the rows because their names match would lose information needed for correct selection.

Guided practice and review evidence

Use only a demonstration dataset for this exercise: Rewrite ten inconsistent descriptions using one agreed glossary. Before starting, write down the question the finished record should answer and identify the source information you would need on a real job. Keep a separate list of missing inputs. Prepare a first draft, then compare it with the topic-specific checks above. Ask another person to follow your references without explaining them verbally. Record where they hesitate, what information they cannot locate and any different interpretation. Keep a brief review log with four columns: observation, proposed action, responsible reviewer and closure evidence. Revise the example and repeat the information-finding check. Your evidence of completion is the revised demonstration record plus that log, not simply time spent reading. Do not upload client information to the academy or practise on operating equipment.

What good completion looks like

A useful result can be understood by someone who did not prepare it. They can identify its purpose, applicable item, source and review status, and they can distinguish confirmed information from unresolved questions. Pay particular attention to this failure mode: Keep supplier part numbers separate from internal item numbers. Check the output in the format the recipient will use. A native file, spreadsheet and exported PDF can expose different problems. Keep the source revision and the issued output linked, and record any limitations of the handover. On a real project, follow the customer's authorised checking and approval arrangements before the information is used. The knowledge check below tests understanding of this lesson; it does not assess practical competence or authorise regulated work.

Practical workflow

  1. Establish the source: identify the approved input, document revision and person responsible for its technical content. Record missing information as an open question.
  2. Prepare a small representative example before applying the approach to a whole project. Check identifiers, units, references and the intended reader’s needs.
  3. Ask the nominated reviewer to check technical meaning. Capture the response, resolve comments and issue only under the agreed document-control process.

Review checklist

  • Can another reader identify the source and applicable revision?
  • Are assumptions and unresolved decisions clearly recorded?
  • Is there evidence of the required review before issue?

Knowledge check

Answer all three correctly to record completion. You can review the lesson and retry.

1. What remains the primary identification key?
2. What should you do with missing or conflicting technical information?
3. What does this academy completion demonstrate?
Sign in to record completion

Educational material and demonstration examples. Not accredited training, practical competency assessment or authority to perform regulated work. Use current approved sources and your responsible technical authority on real projects.

LET’S MAKE YOUR NEXT PROJECT CLEARER

From your technical knowledge.
To a professional deliverable.

Request a quote