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

David Dickson

If ERP is plumbing for the Enterprise - How do we unplug it and keep it from making a huge mess?

I have been working with ERP in various roles for over 30 years, directly involved in over a hundred implementations, while my company has been involved with over 300 more. Of course, in many ways the systems we use today are completely different from what we used in the ‘80s – back then it was green screens, simple transaction entry forms, and cumbersome updates (at best) to link what one department did with all the other areas that needed access to that information. Then there were those planning programs that took all the information along with various parameters the users needed to set and told us what to do.

The More Things Change, the More They Stay the Same

What has surely changed is how we use these systems. Back when I started we used them because we could process more transactions more accurately and faster with a computer, than with the otherwise necessary roomful of clerks. Those clerks, schedulers, and various other clerical employees were the first generation of jobs computers rendered obsolete. Strangely, I do not remember anyone bemoaning those lost jobs. I will let others speculate on the reasons for that.

Individual companies could and did debate the decision about how much they automated. Yes, in retrospect, it is pretty clear that choosing not to automate was to accept a long, slow death for the business, but it is not that long ago when there were still lots of manufacturing managers and business owners who did not use, or like, computers.

Competition Changes Everything

Today a business system is just another piece of necessary infrastructures like an office, a phone, a lawyer, a bank account, and an accountant. The system remains the transaction processing backbone for the organization, but the way in which we use the information that flows from those transactions has changed drastically in this interconnected world. Back in the heady days when ERP was new, the focus was all internal, inside the four walls. Today that seems quaint – the Internet connects all systems and much of the unique incremental benefits (or competitive advantage, if you prefer) come from two deceptively simple concepts – how you connect with the rest of the world from your business systems, and how you monitor your business’s performance in real-time and adapt to what you learn.

I still remember a kickoff meeting twenty years ago for what was then a pretty large ERP implementation at an automotive supplier. Two comments struck me – the first was public. “I like to think of our business as a boat, and we have been steering it by looking out the back. This project will at least let us see out the sides.” The other was in a private meeting when we were discussing change management, and how they would deal with the resistance that would surely come. This same manager said simply, “I guess we will have to fire someone for it, and then the rest will get religion.”

Not terribly ambitious goals, but I give him credit for honesty.

Things have certainly changed a lot in terms of our expectations for the systems, and our approach to implementation, but despite these systems have become an integral and necessary part of the infrastructure of every business, they remain infuriatingly complex and the benefits we expect are often difficult to achieve.

Illusive Benefits = Bad Form

That should not be the case. My goal is to be your guide and share my insights and other good ideas, found across the web, as to how to make business system selection easier and how to get the most benefit from those systems. Because in spite of all the marketing folderol, it seems pretty clear that your friendly software vendor and expert implementation consultants are not going to do that for you. Not because they are stupid or evil people, of course, quite the contrary. They just cannot and will not make the decisions for us that need to be made.

Systems should work for us. Choosing and implementing a system should not be a high-risk proposition for a business, or the individuals doing the work.

The common elements made simple, efficient, and effortless with returns.

My entire career has been dedicated to those goals.

What do you consider yourself to be?

  • internal expert?
  • someone beginning the search and implementation process?
  • an executive looking for a competitive advantage?
  • an industry insider?
  • or someone who finds this amusing for some reason?

All of the above? There is a better way to choose and use software and as someone who could fit into any and all of the categories listed (yes, I really do find business software entertaining in some weird way), I have some ideas I’d love to share with you, so feel free to ask questions.

About the author:

David Dickson is an itinerant generalist; his path to partner and CFO of Crossroads RMC has had its twists and turns. His first twist occurred when an employer needed a business system and picked him because he had three semesters of computer programming in engineering school -- an “expert” born. Somewhere along the line he helped to build and sell a company, which he bought back a couple of years later. Add in another acquisition, a merger, and about 30 years in manufacturing systems in various roles, and you might get a sense from where his real expertise might arise.

Previous Article Accelerating Change: How Innovation Is Driving Digital, Always-On Supply Chains
Next Article Crossroads RMC to Exhibit at Inforum 2016
Print
30209 Rate this article:
5.0
David Dickson

David DicksonDavid Dickson

Other posts by David Dickson

Theme picker

Contact author

Please solve captcha
x

Tips:  LX | BPCS | M3

Understanding: The quantities required, finished and remaining at the operation and in total for the Shop Order

The shop order may require 1,000 pieces but only 950 are reported as finished in total for the shop order. The quantity required is what is planned on the SO and it may be a higher number than what is finished, factoring in that there can be scrap. If a 1,000 pieces are required to be produced, and there is always is scrap of 10 pieces, then plan for scheduling a quantity of 1,010.

The quantity finished for the end item is what is reported in the inventory application with a production order receipt transaction. At the operation level, if the quantity is reported at the operation, there will be a value in the PCS Complete field on the operation detail screen showing the pieces completed through that operation.

If you want to get a handle on the difference between the required quantity and the finished quantity, you may want to look into reporting quantities at the operation level as well as examining how scrap is controlled and reported.

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.

First122123124125127129130131Last

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:

12345678910Last

Theme picker

Categories