We manufacture large machines and when ordered we have configured a base BOM and then each option that comprises a complete machine has its own assembly. We track all of this through an Excel spreadsheet. When a machine is ordered engineering creates a new part number (serial number of the machine) and manually loads the required BOM’s.
For reference to the scale and complexity we are talking about, we have 4 major models of machines, each model has 5 or 6 must-select options that build the machine and 5 or 6 “add-on” options (yes or no)
Once ordered we put up a sales order for that newly created part engingineering just loaded the BOM too.
Engineering raised the question if there is a way we could use something more generic so they don’t have to do this each time we get a sale, as many times we sell the same configuration.
My initial thought was instead of putting a newly created serial number part on the sales order, why not just list all the assemblies that make the machine, and when we put up the job to build the machine we could capture all of the labor and requirements there. The Job number could be the serial number for easier tracking.
In my mind, this would create demand in the system for the assemblies to be made, allow flexibility for manufacturing to build them up and stock, and picked when needed to build the machine. It would also mitigate the creation of the serial number part each time.
I did dig into Epicor Configurator a bit but the general feeling I get is we don’t have enough complexity for it to be useful, and the configuration aspect could be dealt with offline easier.
Before I start to pull meetings in with the multiple groups involved I wanted to see if anyone could share how they currently deal with a similar problem, or if anyone sees any glaring problems with it.
~Thank you all in advance.