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

Rich Grilli
/ Categories: Engineers Viewpoint

10 Ways to Not Screw Up the OEE Project – It is More Important than You Think

Is there a mandate in your company to increase OEE and it has landed on your plate? Ah yes, the OEE approach. You remember what that is right? The Overall Equipment Effectiveness metric as developed in Japan during restoration made famous in crafting some serious efficiency. Well, someone in management has decided that THIS is the way to make his world better and now it’s up to you to make it happen.

But there are pitfalls along the way:

  • Somebody is going to tell you that the best way to start is collecting data manually so that you can understand the process better.
  • Somebody else is going to say that “your” OEE is fine, but the real problem is _____________  (fill in the blank from the following:  SPC, lot tracking, scrap, downtime, indirect time, maintenance, line scheduling, set-up reductions, etc., etc.)
  • Somebody “big” (The VP Ops) is going old school and needs proof that an OEE system will work for his people.

This puts you in a tight spot. An OEE project requires that a lot of people get involved and they’ll all have their own ideas. Try to satisfy them all and you’ll have a 6 figure project with 18 months to implement. Even if it gets approved, good luck getting it implemented successfully. This could get ugly if you’re not careful.

Mach two and the problems that occur at speed.

Should you be concerned about any of this? Guess what, you’re right. Picture this – the crazed Line 1 supervisor approaches you with a can of red paint in one hand and a paintbrush in the other. As he lays out his requirements, he quickly paints you into a corner, smiling the whole time. Once he has you where he wants you, he lights his hair on fire and then leaves! After all, he has a lot of work to do.

I’ve seen this scenario played out many times. OK, maybe the “hair on fire” thing is a bit extreme, but you know what I’m talking about. Over and over, the same issues arose. OEE is great, but what about labor? We can’t spend time collecting data – it will take away from making products. The system has to be idiot-proof because our people aren’t computer savvy.

Is the Key to happiness a good OEE?

Not everyone has the same priorities. Importance is relative in the big picture. And what’s important today may not be tomorrow. So how do you put together a project that will address the desires of all the stakeholders? What’s the best way to navigate the political landscape that’s been laid out in front of you without getting off course? I have to be honest with you. Most of these projects fail before they’re implemented and never get off the ground. Now it’s up to YOU to make sure that doesn’t happen.

And get the efficiency you know is buried in the system and the data that comes out of it.

What if you had a plan going-in that could deal with all of this? Your life will be easier, you’ll get the recognition you deserve, and you may become known as that “someone who can get things done”.

Remember your 7P’s: Proper Planning and Preparation Prevents Piss Poor Performance. 

10 Ways to Succeed at an OEE Project Where 90% Fail at Trying

  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 the 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.

Execution is Everything

So now you have a plan with knowledge of the challenges that will occur and how to deal with them. This is a plan that is well-tested and that works, so your chances for success are good. Don’t worry, you may not be an expert in OEE at this point but you will be shortly. And best of all, you’ll not only look like you know what you’re doing, you actually will.

An Expert is someone who attempted the unachievable and survived to tell about it.

Ok, let’s go get that data and turn it into real information that can be used to improve OEE, not just monitor it.

And remember, you are not alone in this.  There are many people cheering you onward --  including us.  If you need a little encouragement, don’t hesitate to call.

About the author:

Rich Grilli is the president of Crossroads RMC, which helps manufacturers optimize their operations. He is a long-time numbers-guy and engineer who has a passion for systemic models that work. Rich is very interested in designing, planning, and analyzing different aspects of a company's production methods. Because he’s been around many manufacturing plants worldwide, he has developed a deep understanding about coordinating/improving quality control, implementing new strategies for product assembly, troubleshooting inefficiencies, and making process improvements that make a difference.

Previous Article What's Your M.O.?
Next Article How Internet of Things (IoT) Big Data Will Transform Manufacturing Automation
Print
32537 Rate this article:
5.0
Rich Grilli

Rich GrilliRich Grilli

Other posts by Rich Grilli

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

TECHNOLOGY: Facility Security Ranges

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

FINANCE: Expiration Date for Quotes and RMAs

A Cancel-by-Date has been added to the Quote Header and RMA Header panels. This optional field can limit how long a quote or authorization to return items for credit is valid.  

For quotes, this enhancement provides an optional end date for the quote. For RMAs, it provides an optional date by which the customer must return the items to receive the credit listed on the RMA.

The Cancel-By-Date prints on the Order Acknowledgement and RMA Acknowledgement to inform the customer of this important limitation to the quote or return authorization. 

An Order Entry user cannot copy the quote to create a new order if the Cancel By Date has caused the quote to expire.

OPERATIONS: Default Split Salesperson to Customer Orders

Sales commissions are based on combinations of the Primary, Split, and Line-Level salesperson and the commission codes defined for the customer and item. You can now define the Split Salesperson in the same master files as the Primary Salesperson. While the Primary Salesperson is mandatory, the Split Salesperson is optional. It defaults during Order Create using the identical hierarchy as Primary Salesperson. Using Split Salesperson provides more flexibility in the calculation of sales commissions. The ability to define a default Split Salesperson improves the accuracy of sales commission qualification and calculation and reduces maintenance and adjustments necessitated by corrections.

Previously, a user could complete the Cost Transfer (CST920) process for any range of facilities regardless of their security settings established in SYS600. This enhancement verifies the user security settings set up in SYS600 before processing cost transfers for a range of facilities in CST920. If the user has authority for a facility range, but there are facilities within that range that are not authorized, the program skips those facilities and completes the cost transfer process.

1345678910Last

Theme picker

Tips: LN | Baan

All actions required for converting, validating, matching, and posting electronically received bank statements can be performed within a single session:

  • Bank Statement Workbench (tfcmg5610m100)
  • Bank Statement (tfcmg5610m000)

Alternatively, you can use the sequence of electronic bank statement sessions outlined below.

Steps to Process Electronic Bank Statements:

1345678910Last

Theme picker

Categories