As described in the General section the way to process transactions is the following:
You stand close to a ShopFloor operator terminal, and now you want to start a new job.
You do the following:
- Tell the system who you are (Read the employee badge/label you wear in your pocket)
The display now shows that you are the operator on this display until changed by reading a new employee barcode or the terminal is restarted.
- Tell the system where you want to work (Read the resource badge/label probably glued to the machine)
The display normally starts by displaying the 1st resource defined. When reading the machine/work center barcode the display shifts to this place.
- Tell the system what you want to work on (Read the proper production order routing step) The order is of course present and stands in the Waiting status. The order is identified via the production order bar coded routing sheet.
Reading the routing barcode step, the display positions itself to the right order and makes this line dark blue.
Now you have the choice of reading various transaction codes to display the underlying information. I.e. the transaction codes correspond to the dark blue function buttons on the screen.
Reading the ESCape barcode normally takes you back to the previous display.
There are a few rules to obey when using bar codes and transaction bar codes:
A word of caution
The bar code scanning option is ideal in a standard operating environment.
When we say standard, we mean manufacturing execution with basic start and end of jobs, and not too many other things which extend the needed transaction processing– f.ex. variable material issue, operator assignment of lot/serial numbers, scrap reporting and other.
Of course, everything can be run in mixed mode – using a combination of mouse, keying, scanning or tapping the screen. But incorporating many functions can become complex, and probably no good in terms of operator usability.
So, the overall message is: .