Home/Case studies/One-click BOM upload took daily ERP errors to zero
One-click BOM upload took daily ERP errors to zero
A manufacturer's engineers were uploading bills of materials from SOLIDWORKS into the business system with a tool nobody could change. We replaced it with a single step that validates the BOM, loads it, and reports back. Upload errors that had been happening several times a day went to zero.
The situation
Every released drawing needed its bill of materials in the ERP. The upload ran through a third-party tool that was confusing, had many manual steps, was prone to errors, and at times did not work at all.
The larger problem was that it could not improve. The tool was written in COBOL by an outside company. Any enhancement meant going back to the original developer, so in practice the process was locked in time while the business around it kept changing.
Errors that got through the upload did not stay in engineering. They surfaced downstream, as rework and as pressure on ship dates.
What we built
We rewrote the upload around DriveWorks Autopilot, which the client already owned.
- One step from SOLIDWORKS. A macro exports the drawing's BOM and drops a small request file into a folder Autopilot watches.
- Validation before anything is sent. A DriveWorks project imports the BOM into a table, reshapes it into what the ERP expects, and checks every line.
- The ERP update itself. HTTP requests delete the old BOM, add the new one, and add generic shop-floor routings. Messages the ERP returns are collected.
- An answer for the engineer. An HTML email reports success, failure, or success with warnings, with a description of every error. Internal support is notified when anything fails.
The step-by-step mechanics are in our guide to uploading a SOLIDWORKS BOM to an ERP with DriveWorks Autopilot.
What it grew into
Once the upload worked, other departments asked for a piece of it. Each was an addition to the same project.
- Electrical engineering drew schematics in Microsoft Visio, and those drawings carried a BOM too. A similar script sent them through the same upload, so every bill of materials reached the ERP in one consistent way.
- Fabrication received a formatted, calculating Excel worksheet built from the BOM for laser and press brake programming.
- Purchasing received an email when stocked kanban items would exceed their upper limits, so those parts could be ordered before the job reached the floor. That removed lead-time delays in final assembly.
- The item master was updated in the same step with weight, special instructions, system capacities, and ID tag types read from the drawing.
The result
- About four minutes saved per BOM run, roughly 0.7 hours per engineer per week.
- Errors that had happened multiple times a day were drawn down to zero.
- Less rework. Problems are caught at upload, early enough that they no longer affect scheduled ship dates.
- The client owns it. The logic, behavior, and future features are in a DriveWorks project their own team can change.
We never ran time studies on the fabrication, purchasing, and item master additions, so those savings are not in the numbers above.
What to take from it
The time saved per run is small. If we had sold this project on minutes, it would not have looked like much. The return was in the errors that stopped reaching the shop floor, and in owning a process that had been frozen for years.
It also shows what DriveWorks can do with no model to drive. Nothing in this project generates a part or a drawing. DriveWorks is working as a rules engine that reads a table, calls a web service, and sends an email, unattended. If you own Autopilot and use it only for design automation, a project like this is often the quickest win available.
Common questions
How much time does an automated BOM upload save?
For this client, about four minutes per BOM run, or roughly 0.7 hours per engineer per week. The larger gain was upload errors going from several a day to zero.
Can a BOM upload be automated without replacing the ERP?
Yes. This project changed nothing in the ERP. It replaced the tool that sat between SOLIDWORKS and the ERP and used the ERP's existing interface to load the data.
Who maintains the upload after it is built?
The client does. The rules live in a DriveWorks project, so anyone on their team who can write a DriveWorks rule can change what is checked and what is sent.
Related
Base 10 Consultants is a DriveWorks Authorized Services Partner: CPQ configurators, design automation, and CAD-to-ERP integration for manufacturers.
Book a 30-minute call