Article management between CAD and ERP: one item, one truth

Every item in a manufacturing company leads a double life. In Inventor it is a model with geometry, a material and a weight; in the ERP system it is a record with a price, a supplier and a stock level. Two versions of the same physical part, maintained by different people, in systems that do not naturally know about each other.

As long as nobody touches anything, that works fine. But then purchasing sharpens up a description in the ERP system, engineering changes a material in the model, and three weeks later there are two truths about the same item. Good item management between CAD and ERP therefore comes down to two things: clear agreements about which side leads for each field, and a way of working where you look data up instead of retyping it. A toolbox like Thundercad lets you consult and use your ERP item file directly from Inventor, and that prevents a surprising amount of misery.

In this article: why the two systems drift apart, how to give every field exactly one owner, how to look up and place items without retyping them, and how new items get created in a controlled way instead of by accident.

Why CAD and ERP drift apart

The cause is rarely bad intent and almost always timing. During detailing, an engineer changes the material of a bracket from mild steel to stainless. The model is correct, the drawing is correct, but the ERP record still lists the old material, because updating it is a separate action, in a different system, at a different moment. The reverse happens just as often: purchasing renames an item because the supplier introduced a new type code, and on the CAD side everyone keeps searching for the old description.

Three fields are notorious. The description, because both sides have an opinion about it. Material and weight, because they originate in CAD but are used in the ERP system for costing and transport. And the item status: an item that purchasing has phased out keeps getting placed into new assemblies on the CAD side, because nobody there can see that status. Each difference is small; added up, they decide whether you can trust a BOM.

The cost only shows further down the process. Costing calculates with an old weight, the quotation leaves the building with the wrong material surcharge, and work preparation quietly keeps a private list on the side because it no longer fully trusts either system. That private list is the real alarm signal: a third administration has effectively appeared, and it synchronises with nothing.

Give every field exactly one owner

The remedy is not a thick procedure but a simple agreement: every field has exactly one owner, and the other side adopts the value without debate. Which side that is follows from where the information originates.

A field without an owner is a field with two truths. Agree on the split once, pin it up next to the coffee machine and point at it whenever a difference surfaces. Arguments about who is right evaporate once it is written down who is supposed to be right.

Look up and place without retyping

In many engineering departments the ERP system lives on a second screen, and item numbers have been travelling through human hands for years: look up, memorise, retype. Every retyping action is a chance to swap two digits, and a swapped digit here is not a typo but a wrongly ordered part that gets unpacked at the assembly bay three weeks later.

There is a more direct route. With Article Manager you consult your ERP item file without leaving Inventor: search by number or description and immediately see which item it is and whether it is still active. With Place article you then place the item you found straight into your assembly. The number is correct by definition, because it never passed through human hands. For a purchased part like a gear motor that saves a minute and an error opportunity per placement; across a complete machine project you are talking about hundreds of placements. Work preparation benefits just as much: whoever walks through an existing assembly sees the current status and description per item right away, without switching screens and without an export list.

New items are created in control, not by accident

The most dangerous item is the one nobody consciously created. An engineer copies a part with Save as and gives it a free number from memory; weeks later that number turns out to exist in the ERP system, created by someone who assumed it would be fine. This is how records appear without a unit, without an item group and without an owner: ghost items that only surface when a quotation or purchase order trips over them.

Controlled creation means a fixed route, however lightweight:

1. First check whether the item already exists. Searching takes seconds, a duplicate item costs months; how to prevent duplicates structurally is covered in Preventing duplicate items, starting on the CAD side.
2. If it does not exist, the number comes from the agreed series and never from memory. Choosing that numbering approach is a topic of its own: see Part numbers that scale with you.
3. Fill in the minimum fields at creation: description, unit, item group and the choice between manufactured and purchased.
4. Only then does the item become placeable in assemblies and orderable by purchasing.

Staying in sync is a routine, not a project

A one-off cleanup does not exist; the two systems start drifting again the moment people get back to work. What does work is a small fixed routine. At every assembly release you verify that all placed items are still active in the ERP system. Periodically, say half an hour every few weeks, you compare descriptions and materials between the two sides, and the owner of each field resolves the differences. And whoever hesitates while modelling checks the current ERP state with Article Manager instead of a printout from last week. Capture the routine on a single sheet: what you verify at release, what you verify periodically, and who resolves which kind of difference.

That is how item management shifts from firefighting to housekeeping. The two systems will continue to exist, that is unavoidable, but for each field only one of them is right anymore, and everyone knows which one. This is what "one item, one truth" means in practice: not one system, but one agreement per field and tooling that keeps the distance between the systems small.

Frequently asked questions

Does every CAD file have to become an item in the ERP system?

No. Construction geometry, reference models and phantom parts do not belong in the ERP system. The boundary is practical: everything that is bought, made or stocked is an item; everything that only serves the modelling process is not. Write that boundary down once, so nobody has to reinvent it per file.

What about items that only exist in the ERP system?

Services, packaging and bulk items such as lubricants do not need a model, and that is fine. What matters is the reverse agreement: when does something deserve a model, for example as soon as it has to be placed in an assembly or detailed on a drawing. That rule prevents case-by-case debates.

Can I consult items from Inventor without starting a big integration project?

Yes. Looking up and placing items from the CAD environment is a small step that removes retyping errors right away, even if deeper synchronisation comes later. You can try it with the free trial month of Thundercad in your own environment, with your own item file.