Parts Diagrams and Why the 30 30 Format Exists
A parts diagram is just a labeled illustration showing every component in an assembly. The 30 30 Parts Diagram convention comes from industries where you need a reference system that scales — thirty callout numbers on the drawing, thirty corresponding entries in a parts list. It is not a strict standard defined by any ISO body. It is a practical shorthand that grew out of HVAC, appliance, and light industrial equipment documentation. The format solves one specific problem: when a manual has more than ten parts but fewer than a hundred, a full detailed BOM becomes unwieldy on a single page, but a simple exploded view without numbering is useless for ordering replacements. Thirty and thirty gives you enough room for a real service document without requiring a separate catalog.
How to Read a 30 30 Parts Diagram
The layout is straightforward. On the left or top half you have the assembled view or exploded view with thin leader lines pointing to each numbered item. On the right or bottom half you have the parts list table with columns for item number, part number, description, material, and sometimes quantity or finish. Each number appears exactly once in the diagram and exactly once in the table. If a number shows up twice in the table, something is wrong with the document. The numbering usually goes top to bottom, left to right, following the visual flow of the assembly. Small fasteners — screws, washers, clips — tend to be grouped at the end of the list even if they appear scattered across the drawing. I have seen documents where the last five numbers are all M4x12 socket head cap screws from different locations, which is annoying but predictable.
Building One From Scratch
If you need to produce a 30 30 Parts Diagram for a product you are designing or documenting, the workflow is iterative. Start with an exploded view. Most people reach for CAD first — SolidWorks, Fusion, even FreeCAD — because the software can generate exploded states automatically and place balloons with a few clicks. The problem is that automated balloon placement will overlap lines and obscure features if you do not constrain it. I spent an afternoon fighting with a SolidWorks auto-balloon run on a compressor housing where twelve leaders crossed each other in a knot. The workaround was to turn off auto-balloons entirely, place them manually in groups of three, then route the leader lines by hand using short orthogonal segments instead of curves. It took twice as long but the result was legible on the first print. After the drawing is clean, build the parts list table. Every visible component gets a row. Sub-assemblies get their own row with a note like "see detail A" or a separate sub-diagram. Fasteners that are purchased standard items should list the full specification — diameter, length, thread pitch, grade, head type — not just "screw." The difference between "M5x16 screw" and "M5x16-1.0 GR4.8 ZC hex head cap screw" is the difference between someone ordering the right thing and spending two days waiting for a replacement that turns out to be the wrong grade.
Get the Full Details
Common Pitfalls
The most frequent mistake is treating the parts list as a prose description rather than a data table. Columns should be narrow and specific. Avoid freeform text in the description field. Use consistent naming: if you call it a "washer" in one row, do not call it a "flat washers" in another. Pluralize consistently or not at all. Another issue is missing hidden components. Rubber grommets inside a mounting hole, retaining rings behind a flange, shims between two stacked plates — these are the parts that cause field failures because the diagram implies the assembly is solid metal when it actually relies on a compression fit or a seal. I once traced a recurring leak in a hydraulic manifold back to a 2mm o-ring that the drawing showed as a line but the parts list did not enumerate. The diagram said thirty parts. The actual assembly had thirty-one. That one missing o-ring was the difference between a working unit and a warranty claim.
When the 30 30 Format Breaks Down
Thirty and thirty works well for assemblies in the 20 to 40 part range. Beyond that, the document becomes a reference manual rather than a quick look-up. Below fifteen parts, the table takes up more space than the drawing and the numbering overhead feels silly. A simple labeled sketch is faster to produce and faster to read. The format also struggles with modular products where the same base assembly has multiple configurations. A pump that ships with either a 1-inch or 2-inch flange, with or without a pressure gauge, with aluminum or stainless impeller — the parts list either becomes a massive matrix with conditional rows or you produce three separate diagrams. I handle this by making the base diagram show all possible locations with dashed outlines for optional components, then adding a configuration table that maps option codes to included parts. It adds one page but prevents the alternative: three nearly identical diagrams where the reader has to hunt for what changed. There is also a limitation with dynamic assemblies. Moving parts, adjustable components, wear items that get replaced on schedule — these do not fit cleanly into a static exploded view. A belt drive diagram that does not show tensioner position, a valve diagram that omits the actuator stroke range, a gear assembly without backlash specification — these are all incomplete regardless of how many parts are numbered. The diagram tells you what exists, not how it behaves. For that you need separate performance tables or installation notes attached to the relevant item numbers.
Practical Tips That Actually Help
Use a consistent line weight scheme. Visible edges at 0.5mm, hidden lines at 0.25mm dashed, centerlines at 0.15mm dash-dot. This is drafting standard practice but many people skip it in digital workflows because the software defaults are lazy. The result is a drawing where you cannot tell at a glance which features are behind which surfaces. Number your items in the drawing order, not in the order they appear in the bill of materials. The reader follows the drawing. If item 7 is a gasket that sits between items 3 and 5, put it at position 7 in the drawing even though it logically belongs with the sealing assembly. The parts list table handles the logical grouping. The diagram handles the visual search. Include a revision block in the lower right corner. Date, revision letter, change description, and who approved it. I know this sounds bureaucratic but a parts diagram without revision history is a liability. When a supplier sends you a corrected part because the old one has a dimension tolerance mismatch, you need to know which version of the diagram matched the original order. Without it, you are guessing, and guessing with mechanical parts is expensive.
The 30 30 Parts Diagram is not a magic solution for documentation. It is a compact format that works when your assembly is the right size, when you catch the hidden components, and when you keep the data honest. Anything beyond that requires supplementing it with separate detail drawings, configuration matrices, or performance specifications. No single diagram type covers all of those needs. The trick is knowing which one your current problem actually requires.
