“We need to change everywhere it says ‘Product’ to ‘Asset’.”
“They want to see the word ‘Scrap’ instead of ‘Waste’.”
“Under Locations … let’s see … they store assets in vans and warehouses, but since the warehouses have shelves and bins and the vans don’t, and the vans aren’t physically attached to a given warehouse, the warehouses and vans have to be set up differently …”
These are real conversations which happened in the past week or so while developing custom-tailored manufacturing software for certain clients. That’s how detailed things can get. Virtually everything is flexible, anything can be changed, and if your Product is an Asset, so be it.
It’s a given that any company, particularly those with a long history, have developed their own internal culture. With that culture, an overall terminology has also developed within the overall workflows of the company. If canned software is then introduced as a management or reporting tool within that culture, how effective can that software possibly be if the software causes terminology, and ultimately cultural, changes?
Custom-tailored software is by far more appropriate as the software is built to fit within the already-existing culture and its built-in terminology. And certainly, workers and managers are going to be more willing to use software which doesn’t force them to make changes to their workflows in any way.
Besides, ‘Scrap’ sounds much better than ‘Waste’ anyway.