Before we delve into the PackML explanation, I will use an example we can relate to from our everyday life. We will use a common appliance, the toaster, for our illustration. If we look at a toaster, we will see a start button that begins the toasting process. The toaster goes from idle to processing (toasting) when we push the start button. If we time it right, we end up with perfect toast. However, if our toasting time is too long, we run the risk of burning the toast. To avoid burned toast, we would look for an “abort” button to stop the toasting. This simple example illustrates that the toaster goes through a few states. We were in the “idle” state when the toaster was not doing anything. We went into the toasting or “processing” state when we pushed the button. Finally, we either completed or aborted the process of toasting. Through these various “states,” we completed the toasting process.
So, what does PackML have to do with our toaster example? Some smart people in the packing industry decided to analyze all the “states” the packing equipment would pass through. Just like we were analyzing the states of our toaster, they concluded that there were a handful of “states” that would work with any machine in a factory. They named the states “PackML” and a new standard was born. They also attached rules around these states. To understand the rules, we will go back to our toaster example. What if we had a combustible material like newspaper when we started toasting? The newspaper might catch fire. So, to prevent this hazard, we would insert a “clear” state between the “idle” and “start” states. The toaster would go from the idle state to the clear state first to ensure all is well. In the clear state, the toaster would remind us to check for safety issues before moving on to the start state. We are now enforcing a new rule. The new rule is “thou shall never go to the start state without passing through the clear state.” To get to the start state, we must be in the idle state and we must go through it to get to the clear state.
Scientists and engineers gravitate towards order and simplicity. Breaking things down to a simple set of rules can achieve predictability, improve safety and foster better communication. The PackML machine state process has done just that. It has been a big hit in factories all around the world because it defines a universal language that can be used by factory automation designers, builders and maintenance staff. The PackML concept caught on so well other industries began to use the new standard in their machine design. PackML is rich enough to be used in any scenario because PackML is simple and straightforward and easy to implement.
If you would like additional information about PackML, you will find it on the internet.