BPCS/LX Tip of the Week: Getting the Most Out of the Shop Order Inquiry Program – Part 2
Understanding: How many hours remain in total and at each operation?
Now let’s look at what information is being supplied from the shop floor.
It’s not uncommon for transaction reporting to be captured manually on the shop packet that was issued to the factory floor when the SO was released.
The big question is, is anything done with the data? Is it collected and keyed to a spreadsheet and not shared, or is the transaction data keyed to SFC600? If it is being keyed, ask how often and by whom? Some companies use alternative methods to capture transaction data that do not require batch keying via a keyboard.
Not a lot of data is required to be keyed to SFC600 in order for the SO Inquiry to be useful. The data that should be reported for the transaction process is as follows:
- The type of hours being reported – machine, run labor, setup labor
- If reporting setup and run labor you want an employee clock number
- The shop order and the operation that is being reported
- Is the operation complete
- How many good were produced at this operation
- How many hours – the numbers of hours are critical. Do the employees estimate how many hours they worked, or do they track actual time started and stopped in order to calculate the actual number of hours.
Based on what is captured and how often will have an impact on the SO inquiry screen. Understanding the batch times as to when the transactions are keyed will provide you with the window as to the SO status at that point in time. Or, are they keyed as they happen in a near real time fashion so that you can have a more current view of the factory floor.