This Blog is Part 2 of a 2 Part Post.
In our previous blog about ID Codes, we talked about the importance of planning which ID Code schema you might want to use and the pros & cons of non-intelligent ID Codes. Read Part 1: Defining and Setting Up ID Codes in Epicor ERP
So let’s get to the real issue… Is Your ERP ID Code Schema Costing You Money?
By establishing non-intelligent ID Codes, you eliminate the need to rework, or revamp your schema during an implementation. This saves both time and money.
That’s why choosing the proper ID Code schema to reference your groups is critical to your project, implementation, and your client’s success. Now, let’s look at intelligent ID Codes and what they can offer.
Advantages of intelligent ID Codes:
Significant ID Codes offer time savings downstream, and they can help prevent data entry mistakes and improve manufacturing efficiency. Here’s how:
- Search efficiency: With this type of scheme you can group similar codes in your design documentation and spreadsheets and then more easily sort and search among them. You can also create queries and reports more efficiently, by just pulling in the code, not the description.
- Error reduction: This type of ID Code scheme provides a frame of reference for each group by specifying the group to which it belongs. If an employee needs to quickly verify the validity of a group of data, you can use that group ID code to pull that information, sort, filter, etc, and check to see if there is data in the wrong group.
Disadvantages of intelligent ID Codes:
While there are many benefits to using a significant ID Code scheme, this type of schema also has some shortcomings. For this type of scheme to work well in an organization, employees must be familiar with the former and current code schema structure (if there is one). Such a scheme also demands ongoing attention and can introduce delays in your processes. Here’s why:
- Training and knowledge required: Since these ID Codes have some meaning and significance to the group it represents, the stakes are high if the group is not properly defined. The person assigning the ID Code must know how and when to create a new group. An incorrectly classified Class ID can be misused because of the information implied by the code itself.
- Ongoing maintenance: A new Class ID that does not fit the current scheme will require an evaluation of the entire scheme and definition. The logic of the ID Code system must be understood and carefully maintained, and group sizes planned in advance. For example, if all the significant digits in a string (o 0-8) have been used before, and there’s a similar group that must be set up, now you have the. potential of two groups with similar ID Codes, and employees possibly not paying attention to the description, leading to errors. What do you do? You need to spend time upfront planning for how to avoid this type of conundrum and how to address any challenges when they arise. When mistakes do occur, how is this handled and what is the best way to fix the error(s)? You will spend significant time updating the system and training (or re-training) people on the changes.
So Which ID Code Schema Should Your Company Use? Intelligent or Non-Intelligent?
Ultimately at the end of the day, the decision is made by the customer, or end user of the product. As a consultant and trusted adviser, it is our responsibility to offer the pros and cons with each option, and to allow you to make the best decision for your organization.