Case study · Machinery manufacturer

New parts drawn every week reach the ERP without waiting and without errors

An integration in which the new machine drawings and revisions constantly produced by a large R&D team flow automatically into ERP item cards and bills of materials, only approved revisions go to the ERP, and every transfer is traceable.

Before

The company adapts its machines to each order; R&D produced hundreds of new parts and revisions every week. Entering them into the ERP was an ever-growing queue in the planning department.

As the queue grew, the BOM in the ERP fell behind the design; purchasing could order outdated material and the shop floor could receive information from an old revision.

The same part being created under different names by different engineers led to duplicate item cards in stock.

What we built

Approved revisions onlyThe integration reads documents that reach the approved state in the PDM workflow; drafts and drawings under review do not go to the ERP.
BOM comparisonThe new revision's BOM is compared with the recipe in the ERP; added, removed and changed-quantity items are listed before the transfer.
Coding rule and duplicate checkNew item codes are generated according to the company's coding rule; if a card with a similar name and dimensions exists, the engineer is warned.
Controlled transfer and audit trailItem cards and BOMs are written to the ERP programmatically; a material code with no counterpart stops the transfer and notifies the person responsible. Every transfer is logged with revision, user and changed items.

After

The manual-entry queue in planning is gone; an approved drawing reaches the ERP immediately.

The BOM in the ERP is on the same revision as the design; duplicate item cards are prevented by the coding rule.

Facing a similar problem?

Tell us how you work today; in the first call we will say plainly what can change and what you do not need.

Request a Call Clients