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

Anthony Etzel
/ Categories: Infor LX & BPCS Tips

Tip of the Week: Ways to Manage the Pain of Losing a Key Employee Before it Ever Happens

  • Sit down with your IT team. Decide how the information will be captured and where it will be stored so that employees have access to it. What software tools need to be used to capture the information? How does it need to be organized? Create a repeatable process to make this easy for your staff.
     
  • Interview the person. Have them talk you through his/her job. What are the things they do every day? What are their biggest challenges? How do they overcome them? 
     
  • Have someone shadow the person for a week. Watch what they do and how they do it. Ask questions. Who does he/she interact with in their department? Outside of their department? Why?
     
  • Find out what tools he/she uses to perform their job? Are there spreadsheets?  Reports within your ERP / outside of your ERP? Separate stand-alone databases? Drawings? Websites? Why does he/she use them?
     
  • Video record how the person does their job. Is their technique critical to “doing it right” the first time and not ending up with a bunch of scrap that you can’t reuse?
     
  • Figure out if the person does anything special on a monthly, quarterly, or annual basis that might not come up during the observation period or interview. 
     
  • Map how he/she uses your business system and how that impacts the rest of the company. Understand both the “what” and the “why”. Without this, new employees may end up figuring out what they need to do, but never understand why they need to do it.

Optimize Your Manufacturing Today!

Previous Article Tip of the Week: Ways to Manage the Pain of Losing a Key Employee Before it Ever Happens
Next Article Baan/LN Tip of the Week: Accurate Job Costing
Print
59866 Rate this article:
No rating
Anthony Etzel

Anthony EtzelAnthony Etzel

Other posts by Anthony Etzel

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