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 8 Principles of Supply Chain Risk
Next Article Lunch & Learn Webinar for BPCS & LX
Print
53810 Rate this article:
No rating
Kathy Barthelt

Kathy BartheltKathy Barthelt

Other posts by Kathy Barthelt

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.

12345678910Last

Theme picker

Tips: LN | Baan

Don’t laugh! I know, I know…many of our customers say that after 7-10 years they are finally settling in after the implementation! We have seen many a customer stretch out the lifespan of their ERP system to 20+ years. That sounds great for the company’s bank account, but is it good for the business?

An outdated ERP system hurts your business in many ways, not just with slow performance. The best-of-breed functionality is now 2 decades old, and obsolete technology can't leverage newer technology. Lack of integration leads to siloed data that hurts communication and your internal teams feel the pain, and your customers are noticing. Poor visibility into your operations makes it nearly impossible to achieve industry-based regulatory compliance and meet financial auditing requirements. Not to mention the sheer size of Big Data that is being collected today vs. 2 decades ago or the fact that your vendor is no longer supporting your ERP version.

Let’s scrap it all and start over!...

Is the text linked to the purchase order just an information field? Could it be used for another purpose?

The text editor is just an information field when linked to the purchase order line and there is no other logic behind this functionality. The line text or the header text could be a part of the printed document. When you add text to a purchase order line you are creating a unique code that links the purchase order line (Baan - tdpur041/ LN - tdpur401) to the text (tttxt010).

First3031323335373839Last

Theme picker

Categories