Clearing the Integration Hurdles

Control System/ERP Integration Is More Profitable and Technically Easier Than Ever, but Non-Technical Challenges Remain

Share Print Related RSS
Page 3 of 3 1 | 2 | 3 Next » View on one page

The best way to justify return on investment for integration projects is to make the business case first (See “Make the Business Case First”). Once a business case has been made, there is a compelling reason for upper management to get behind the project. Upper management backing then convinces all departments to give integration projects the support they need.

Since standards have made integration much easier, one best practice is to use standards for communication whenever possible. The alternative of custom coding is not only more expensive initially, it is also harder to maintain.

One technique employed by many for control/ERP system integration is to use a manufacturing execution system (MES)-level product as a transfer point for communication. “Our engineers and programmers have found that using SQL Server as the transfer point provides more flexibility to work with legacy systems,” says Jerry Leuthold, senior software engineer at system integrator Bachelor Controls. (See the “Let SQL Serve” for more details on how Bachelor leverages middleware to east integration.)

Enterprise Resource Planning System

A technical best practice that may work for some is to just bypass IT. Alan Cannon is a process/automation SCADA engineer for Plastic Omnium, Duncan, S.C. Like most automation pros, he had no direct experience with SAP.

“ERP integration in its simplest form is probably pretty easy for someone who lives in that environment,” observes Cannon. “But it was challenging for me because I had no knowledge to pull from, as I usually work with real world I/O and PLC logic.”

“So I read the 75-page manual on integration with SAP, and I was able to create every tool necessary to make connections between our InduSoft HMI and SAP via Microsoft SQL in less than an hour. But without the STD.net framework, the interfaces and the output windows contained within InduSoft, my debugging time would have been increased tenfold,” cautions Cannon. Bypassing IT saves lots of time in meetings and negotiations. Reading manuals is no fun, but it can be easier than establishing and maintaining relationships with other departments.

But even if it’s impossible to bypass your company’s IT department, it certainly helps to know as much as possible about your company’s IT platforms, especially those that interface to manufacturing.

Standards make the interfaces among control systems, MES platforms and ERP systems easier to understand for process automation pros. This can expedite learning and result in a deeper knowledge of the entire integration process. This knowledge makes meetings and negotiations with the IT department much easier, and it also results in better solutions.

Want MoreCheck out our Integration Guide for more online resources on this subject. Also, read "Middleware Melds Manufacturing Info."

Freaky Fast-- Emerson gets first Syncade project
Emerson announces that Bristol-Myers Squibb will be, if not their first Syncade customer, at least their first public one.
Page 3 of 3 1 | 2 | 3 Next » View on one page
Share Print Reprints Permissions

What are your comments?

You cannot post comments until you have logged in. Login Here.

Comments

No one has commented on this page yet.

RSS feed for comments on this page | RSS feed for all comments