Implementing a Codification System for spare parts/maintenance warehouse
In a Codification System, when a new Codification Design is required, there are several aspects to be considered.
Initial considerations:
- How often a code is used in communication outside the system.
- Why the classification is important for the final users.
- How often a code is used to retrieve a spare part without accessing the system.
- If shopping lists to retrieve spare parts and components are printed out from a system or manually created.
DOs:
- use at least one block + the number.
- Make codes global, usable at each of your locations.
- In case of classification by application, use a special class to include common spare parts and components usable by several applications.
- Use separator characters to make the code more understandable.
DONTs:
- Do not use more than three blocks, excluded the number.
- Do not include in the code any attribute/feature/information that can change over time (i.e. color, stock location, or internal replaceable components in case of machines/assets).
- Do not reuse the code to identify something different once the initial entity is not necessary anymore.
- Do not classify common components by application.
Contact us for more information.