Please Wait a Moment
X

Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News

Crossroads Connections

Infor ERP Tips & News from the Experts

Infor LX | Infor LN | BPCS | Baan | Infor M3

Kathy Barthelt

Tip of the Week: 10 Ways to Succeed at an OEE Project Where 90% Fail

  1. Collect the requirements. Learn from everyone with the intent of developing a phased approach to implementing on your shop floor with OEE being Phase 1. 
  2. Create your list. Capture all of required functions, taking into account what the “output” of the system will be. What does the plant manager need to see in real-time? What KPI’s does each line need displayed in real-time? What reports are required?
  3. Insist Upon Real-time. In the moment data for the right OEE is the right approach. If it’s possible, collect the data automatically. Remember that real-time feedback to line operators results in an automatic increase in OEE.
  4. Evaluate your lines. Focus where production counts can be monitored automatically. If the data is in your PLC’s, can you get it out? OPC communication is the right way to go here. If not, the approach is to install a new dedicated PLC with sensors installed on each line.
  5. Find Your Data Points. If automatic production monitoring is not applicable, what will be your collection points and how will you collect the data?
  6. Calculate the Load. Determine how to load the “job” you’re reporting on into the OEE system. This will typically be the order/operation or the product from the ERP.
  7. Recognize Great Data. Do not accept “manual collection of data” as a viable approach because it produces false results and is labor-intensive.
  8. Be Tough. Evaluate systems based on OEE specificity to start and expandability to future phase functions as determined by your requirements. Plan to justify the OEE purchase on its own merits.
  9. Go Easy. Make sure the system is easy to implement. Software installation and configuration should take no more than 2 weeks.
  10. Be Simple. Put together a detailed but simple project plan indicating who will do what, how long it will take, and how you will monitor progress.
Read Full Article

Optimize Your Manufacturing Today!

Previous Article BPCS/LX Tip of the Week: 5 Ways to Motivate Your Employees
Next Article Lunch & Learn Webinar for BPCS & LX
Print
106256 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

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.

Understanding: How many hours remain in total and at each operation?

First let’s look at some key BPCS Master File data starting with the routing file.

How many routing steps (operations) are set up that reflect how the product is produced in the factory? If you take a short cut and set up only one operation for the entire process, then you will limit the information seen on the SO inquiry program. Set up the operation steps to reflect what you want to report back to from the factory floor.

Will each of the routing steps run in one work center, or in different work centers? To keep it simple you may want to set up work centers as departments. For example:

  • Assembly
  • Machine
  • Paint
  • Etc.

For each operation setup consider how you have set up the following:

  • Load Codes – for example a code 5 is used if reporting both setup time and run labor time. These codes are maintained in the work center file
  • Basis Code – typical codes are P for pieces per hour,  3 is used for hours per 1,000 pieces
  • Setup hours – if you set them up, you also want to report them
  • Run hours – Direct Labor
  • Machine hours

How you set up th

FirstLast

Tips: LN | Baan

Categories