Home/Case studies/ERP item numbers created from the product configurator
ERP item numbers created from the product configurator
A manufacturer's engineers created every new item by juggling a spreadsheet and the business system. We replaced that with one interface that issues the number, checks the entry, and creates the item. Then we put it inside the product configurators, so sales can generate item numbers without engineering.
The situation
Most manufacturers have a spreadsheet or an Access database that hands out the next number in a sequence: part numbers, drawing numbers, customer numbers. This client did too.
Creating an item went like this. Start the item in the business system. Switch to Excel. Open the spreadsheet, type a description, copy the next number. Switch back and paste it in. Then fill in the rest of the item using codes that people had committed to memory, because the screen did not explain them.
The problems are familiar:
- Duplicated entry. Any time the same information is typed in two places, there is a chance to get one of them wrong.
- A shared file. Someone has to remember to close the spreadsheet before the next person can save to it.
- No validation. Nothing checked that the data was valid, or that people described similar things in a consistent way.
- A handoff. Sales needed an item number to move forward and had to ask engineering for it.
What we built
We rethought the client's interface to the business system for creating items.
- No memorized codes. The confusing codes were removed from what the user sees.
- Safeguards. Checks were added to prevent errors before the item is created.
- No spreadsheet. The next number in the sequence is issued by the tool, so the spreadsheet and the copy and paste are gone.
- Inside the configurator. We embedded the project into the client's DriveWorks product configurators, so sales can generate their own item numbers while configuring a product.
The result
- The next-number spreadsheet is retired. Of everything in the project, that was the game changer.
- Two communication steps between sales and engineering are automated. Sales no longer asks for a number and waits for the answer.
- Fewer errors, because the entry is checked and nothing is typed twice.
What to take from it
The spreadsheet is the symptom. The number juggling exists because the business system makes creating an item harder than it should be. Fix the interface and the spreadsheet has no job left.
Put the step where the work happens. The largest gain came from embedding item creation in the configurator. Sales was already there, describing the product. Asking them to stop, send a request, and wait for a number added nothing.
Think about the number itself. A weakness of plain sequential numbers is that the previous number is also perfectly valid. If someone types 4532 instead of 4523, the system accepts it and returns the wrong item. Credit card numbers guard against this with a check digit (the Luhn algorithm), which catches transposed digits and off-by-one mistakes before anything is submitted. If you are redesigning how numbers are issued, that is the time to consider one.
Common questions
How do you replace a next-number spreadsheet?
Have the tool that creates the item also issue the number. The user describes the item once, the entry is validated, and the number is assigned and written to the business system in the same step.
Can sales create ERP item numbers from a configurator?
Yes. In this project the item creation step was embedded in the product configurators, so sales generates an item number while configuring, without a request to engineering.
What is a check digit in a part number?
It is an extra digit calculated from the others. If a user transposes two digits or is off by one, the calculation no longer matches and the number is rejected. Credit card numbers use the Luhn algorithm for this.
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