Why are you supporting both eBoms and mBoms when the world is moving in the direction of the single enterprise BOM?
We actually support both paradigms depending upon the company’s business process for process engineering. In companies with joint product/process engineering teams, they can use only the mBOM within Proplanner and ignore the eBOM. Users can define components and processes in the mBOM concurrently, while the eBOM would only let them define components. With both teams working from the same process tree, the joint team will be working on the same product and process definition concurrently. In a concurrent engineering situation with seperated product and process engineering functions, you have product engineers changing the components and assembly configuration right up to product launch. Concurrently you have process engineers defining the workplaces, equipment and methods to manufacture the last configuration released to them. As such, there are times where processes are being defined for assemblies that my not exist, as well as for assemblies that may be replaced but which have not bee
