Goals
By using the configurator a complex product can be formalized into a simple to understand object that allows the user to specify the item of their choice, specifying options like colour, size, position or accessories.
The product can vary from a simple product with a few options to a complex or multi part composition where logical rules limit possible combinations.
The output that the program gives can be, for example:
- Visualization (3D view, picture, animation etc.)
- Description
- List of parts
- Article codes
- Prices
- Data for ERP/CRM
Aspects where a product configurator can be useful:
Reduce time to orders entry: Sales can spend a lot of time recording order details for complex products. It can take hours to ensure that all calculations are complete, and that specifications are captured and correctly transformed in the correct product.
Reduce errors and delays: Complex orders can end up as manual documents and spreadsheets. Converting into ERP BOMs and route manuals leads to costly mistakes and delays project starts.
Improve balancing between speed and quality: Delivery timelines keep getting shorter, but engineering cannot compromise standards. Time needs to be focused on building great products, not on data re-entry.
Improve change management: If you work with multiple systems, requests to modify a product enter the ecosystem too slowly. Without centralized information, production can end up working with a different product version than sales and engineering, deadlines get missed, and error costs pile up.
Improve access to critical product and industry knowledge: Individuals are too pressured and busy to share information and answer questions from sales, the channel, and customers.
Previous topic
Next topic