Q&A: Automation standards save time and money

June 1, 2003
Machine builders and end users team to develop packaging automation standards. See video of first Plug-and-Pack™ packaging machine, a robotic tune filler.

The “approved vendor list” has become the purchasing bible at many manufacturers. This list specifies suppliers and equipment for purchased assets, including automation systems and components. For end users, a standard list of approved suppliers helps control costs by limiting the different types of systems in a plant and the associated support needed for those systems.

For a machine builder, however, a user’s approved vendor list can limit the choices for the automation system. Complying with the customer’s standard list of suppliers may require reengineering the machine. This costs money for the original equipment manufacturer (OEM) and the user.

Leading companies in the packaging industry, including packagers, packaging machinery manufacturers and control technology providers are working with trade associations, educators and analysts to come up with a better plan. Together, this group forms the membership of the OMAC Plug-and-Pack Workgroup.

OMAC, which stands for Open, Modular Architecture Controls, was founded in 1997 to promote the development and adoption of open automation controls. (See Automation World News section for more on OMAC.) The Plug-and-Pack Workgroup is comprised of leading packagers such as Anheuser Busch, General Mills, Hershey Foods, Nabisco, Nestle, Pharmacia, Procter & Gamble, SAB Miller and Unilever, as well as automation and machinery providers from the United States, Europe and Japan.

In March 2000, at an early meeting of the Plug-and-Pack Workgroup (then known as the OMAC Packaging Workgroup), the following goals were established:

• Maintain open dialog among users, OEMs and technology providers.

• Hold several public working group meetings per year to facilitate discussion.

• Establish deliverables in Architecture and Connectivity; Languages and Application Program Interfaces; Education; and Results and Benefits.

During the past three years, the Workgroup has established tag naming guidelines, endorsed the IEC 61131-3 programming language standards for programmable controllers and prepared a “Machine Modes Definition” document for machine control.

Automation society partners

This month, the Instrumentation, Systems and Automation Society (ISA), hosted an OMAC Plug-and-Pack Workgroup conference track at its Process Control Conference in King of Prussia, Pa. The first-ever cooperative event highlighted control technology for packaging, including making the business case for advanced automation in packaging systems.

The case for cooperation is made by Bob Martell, an automation engineer based in Pharmacia Corp.’s main Kalamazoo, Mich., facility. In a recent interview with Dave Newcorn, senior editor at Packaging World, sister publication to Automation World, Martell discusses how Plug-and-Pack guidelines are saving Pharmacia and its machinery suppliers time and money.

Newcorn: How can Plug-and-Pack reduce end users’ tendency to impose their own controls preferences on machine builders?

Martell: When we do this, we can’t really leverage the machine builder’s previous design work. Each project becomes a new adventure from the OEM’s point of view, so they’re limited in their ability as to what they can deliver to us. Of course, from the user’s perspective, there’s the counterargument that if I give away too much of the design decision, how do I guarantee that I support this system? In some way, those big, thick specification documents provide users with a certain comfort level.

If we have some standards [such as Plug-and-Pack] that both users and OEMs can accept, then we can be more likely to accept the OEM’s standard automation platform. The users involved in Plug-and-Pack are trying to pull in the same direction as machine builders. A common standard, once agreed upon by both parties, can be used to alleviate some of this very detailed specification.

As an example, on two recent projects, I accepted a fieldbus that I wouldn’t have accepted two years ago. It was one that was recommended in the Plug-and-Pack guidelines. I know it’s going to be affordable long-term, and that it works for the application the OEM chose, so why should I force the OEM to change? Two years ago I would have requested a different bus, and it would have had a big ripple effect on their design, requiring them to change their software and control—all a tremendous disruption for the OEM.

I’ve been faced with that same type of decision at the controller level, evaluating a machine with a controller that’s not in the company standard list. But it complied with the Plug-and-Pack guidelines at every level, including network architecture, software and the like. So after analyzing it in that context, I knew there was no reason not to accept that controller, and I did.

I’m sure not all users put the same amount of value into the Plug-and-Pack guidelines that I do. I personally know the quality and diversity of the people contributing to it. They’re having an impact on my buying decision, benefiting the OEM and me. And it results in shorter lead times, because on these two projects I did not feel compelled to redesign the OEM’s control. Every job’s going to have some amount of customization for a specific package, or application. If you can avoid doing a brain transplant on the machine, [you avoid] the kind of thing that adds months to a schedule.

Newcorn: Is Plug-and-Pack all about servos?

Martell: That’s where it started, but 90 percent of the work that the Plug-and-Pack group has done can benefit any machine that has some level of automation. It’s really about how you create an environment where you get the most out of your automation. I’m recognizing that most of this stuff has nothing to do with servos. It has to do with the machine design process.

Newcorn: How can machine builders benefit?

Martell: First they need to become familiar with the work that’s going on. Those OEMs that are not currently implementing standards need to think about doing so. Once implemented, a control system that complies with Plug-and-Pack guidelines can be used to defend the OEM’s control platform of choice. Say a customer comes in and says, “I’d like to buy your machine, but I’d like you to quote me with the blue control instead of the red one.” If I were a machine builder, I’d turn it right around and say, “I could quote you the blue one, but here’s why I picked the red one. Here’s the list of Plug-and-Pack guidelines, and here’s the group of thought leaders in the packaging field that looked at it and said it’s good for packaging applications.”

See sidebar to this article: Reducing pharamaceutical validation costs

Sponsored Recommendations

Put the Plant Floor in Your Pocket with Ignition Perspective

Build mobile-responsive HTML applications that run natively on any screen.

Ignition: Industrial-Strength System Security and Stability

Ignition is built on a solid, unified architecture and proven, industrial-grade security technology, which is why industrial organizations all over the world have been trusting...

Iron Foundry Gains Competitive Edge & Increases Efficiency with Innovative Technology

With help from Artek, Ferroloy implemented Ignition to digitally transform their disconnected foundry through efficient data collection and analysis while integrating the new ...

Empowering Data Center Growth: Leveraging Ignition for Scalability and Efficiency

Data center growth has exploded over the past decade. Initially driven by organizations moving their computer assets to the cloud, this trend has only accelerated. With the rise...