Coil validation has been a feature of the XL series controllers since the early 1990s. Our customers have felt this to be a critical function and rely on it to:
- Prevent the wrong coil from being used on an order
- Ensure perfect tracking of coil consumption
- Reduce time wasted manually recording coil information by the operator (and the subsequent time required for data entry into a computer
- Eliminate coil usage data entry errors
How it works:
- When the operator has loaded a new coil on the machine (or is about to), he scans the bar code on the coil. This bar code uniquely identifies that particular coil.
- The XL200 controller creates a message for Eclipse requesting validation of that coil ID number. It can also lock the operator out from running production or even manually cutting material with the new coil until the ID has been checked.
- Eclipse checks to see:
- Is the coil ID valid (is it in the coil inventory)?
- Has the coil already been consumed?
- Does the coil’s material specification match that of the production order the operator is trying to run? If not, is the coil’s material an approved alternative?
- If everything is okay, Eclipse informs the XL200 machine controller that the coil has been approved and it is ok to allow production with that coil. If there was a problem, a message is displayed on the controller that describes the problem. It is possible for a manager to override this with a key if necessary.
- From this point forward, all production data sent to Eclipse will be recorded with the current coil ID.
In most cases, the coil validation process takes a few seconds to complete. The coil inventory data that is used for the verification process can be the local Eclipse coil inventory or it can be a corporate SQL table (via ODBC).