As explained in Part 1 of this blog, there are pros and cons of direct issue and backflush consumption methods supported by ERP systems. Accuracy of component traceability and inventory levels are often the main decision factors when choosing which method should be used.
There is another mode that combines values of direct issue with automated component consumption. This requires the consumption execution to be moved from ERP to MES.
MES usually handles more detailed level of inventory, including the exact consumption locations. Additionally, MES can support special mechanisms that automate data collection and allow operators to validate the information on the fly. This in consequence leads to more detailed traceability data and accurate inventory levels. Here are some examples:
Thanks to the use of business specific validation formulas and automated data collection, MES can off-load the shop floor staff from labor intensive reporting. Yet, it can still provide very accurate traceability and inventory information.
It is worth to remind that MES should keep ERP updated about the inventory levels. This can be done in an aggregated mode, typically once a shift or at the time of production declaration. This is much more reliable than doing manual data entry in ERP or consuming inventory by doing a backflush.
To conclude, it is worth considering MES for execution of material consumption because it is better suited to supports different production scenarios. Traceability requirements are continually changing and becoming more stringent. Keeping genealogy data like lots and serial numbers is a bare minimum. Various regulations demand traceability of particular pallets, boxes and their flows. This is one of the additional features we could discuss in another post.