Is the PLC’s obituary premature?

Large installed base and personnel with ladder-logic experience keep the controller flush in applications.

By Marty Weil, contributing editor

1 of 3 < 1 | 2 | 3 View on one page

The general health of the programmable logic controller (PLC) market is a thing to behold.

According to Frost & Sullivan, the global PLC market has witnessed positive growth across all regions. The market, which experienced a strong decline in the early part of the decade, has bounced back strongly and is expected to reach $14.58 billion in 2018, up more than 40% from five years earlier. This growth includes the mature markets of North America and Europe, where uncertainty about economic standing had precipitated the earlier decline. Of particular interest is the Frost & Sullivan note that “the small and medium PLC segments will be instrumental for market development.” Those segments are the domain of traditional PLCs.

Much has been made in recent times about the impending demise of PLCs, expected to meet their end as the inexorable digital advance renders them obsolete with the advent of process automation controllers (PACs) and more advanced computer-based controls.

From the bottom up

Chris Elston, senior controls engineer at Fort Wayne, Indiana-based Yamaha Robotics, says that PLCs remain extremely relevant. “Probably 95% of machine builders still use PLCs as the controller of choice when they design a piece of machinery,” he says. “There really aren’t a lot of people out there who have switched over to something like PACs or PC-based control or anything of that nature.”

One of the reasons there hasn’t been an overwhelming rush to implement new control technology at the plant level is that many end users aren’t positioned to support it at the business end of things. “It can be boiled down to this: There’s a lot of skill set out there in the manufacturing industry, particularly with maintenance personnel or automation technicians, that is oriented to using ladder logic,” says Elston. “Most of them don’t understand a scripted language, so they are comfortable with working with PLCs. It’s a workforce issue at that level.”

Don Fitchett, president of St. Louis, Missouri-based Business Industrial Network (BIN), underscores this point (Figure 1). “On the automation side, a lot of OEMs want to push ‘the end of the PLC’ idea; but it’s not going to be the end because the end users drive the market,” he says.

Fitchett compares the current situation to the vendors’ introduction of soft PLCs two decades ago. “When the industry came out with soft PLCs and pushed that approach, end users went out and bought any old computer instead of industrial computers. So when things collapsed, they pointed the finger at soft PLCs and went back to legacy PLCs,” he says. “Even though vendors still sell soft PLCs, they’re not pushed anymore because end users pushed back. A similar situation exists with the process automation controller and other new technologies for the entire plant. They’re not user-friendly for maintenance personnel.”

MORE: A look at PLCs, yesterday and today

The fact that manufacturers are finding the depth of the skilled labor pool a significant issue at this time only increases the impact of bottom-up resistance to switching out PLCs. “It’s really an issue of education, and also a generational one,” notes Elston. “Many machine builders are really cutting edge, but the issue with adoption is one of support after the fact. There is always a lag time between builders and users, and end users are typically reluctant to change control platforms. Maintenance personnel will even put PLCs back after they are switched out. They’ve been doing that for years because the PLC is something they have deep experience with and understand.”

Application breadth

“PLCs have been around for a long time,” explains Kevin Romer, product manager at Advantech America. “They work. They get the job done. There are a lot of people in the field that have familiarity with PLCs and know how to use them, so it’s not surprising that they are so broadly applied in industrial automation.”

Industry analysts at ARC Advisory Group and VDC Research estimate:

• 80% of PLCs are used in small applications (1 to 128 I/O points)

• 78% of PLC I/O is digital

• 80% of PLC application challenges are solved with a set of 20 ladder-logic instructions.

These statistics support what some have called an 80/20 rule: if 80% of applications incorporate simple digital and analog control, the boundaries of control applications are being pushed by a 20% minority. This ratio acts to preserve the viability of traditional PLCs.

1 of 3 < 1 | 2 | 3 View on one page
Show Comments
Hide Comments

Join the discussion

We welcome your thoughtful comments.
All comments will display your user name.

Want to participate in the discussion?

Register for free

Log in for complete access.

Comments

  • <p>Thanks for the unique and interesting article Marty Weil. I will add here for clarification on my comments above, PLC obsolescence (AKA: 'death') was in respect to and defined as "the majority of new equipment not using PLCs, but using PACs instead". End-users (especially factories) will still have majority of control done by PLCs, and PLC vendors will still sell and support most of their legacy PLCs. </p> <p>Example, most plants that use Allen Bradley PLCs, have one to a few PLC 5 doing major control. But the bulk of their machines will have SLC 500, with Micrologix being the second runner up. In 5 years it will be difficult to get parts and support for legacy PLC 5, but because of the mass number of SLC 500s out there and their long life cycle, they will be sold and supported for many years to come. In other words, while it might be foreseeable and affordable for the end-user to upgrade 1 or 2 PLC 5s in their plant to PACs (controllogix), they will not find it cost effective to migrate the 30-60 SLC 500s and Micrologix in their facility to controllogix. Especially when they still work, and can all be placed on Ethernet and work with new approaches like " the Internet of Things (IoT)".</p>

    Reply

  • <p>Calling PLCs "legacy" only applies if you are talking older design PLCs, or if you are unaware that many PLCs are out there support all or several IEC 61131 languages, as well as ladder programming, networking, etc. No one with any sense migrates to a control system above the needs of the application just to be modern, or just for the sake of mindlessly networking everything. There is a reason there are 8 bit microcontrollers everywhere - they still fit the applications. The same is true for PLCs. The distinction between "PACs" and PLCs is pretty fuzzy when you look at more capable (and ever cheaper) PLCs, especially those using all of the IEC languages. I think one of the more important distinctions automation professionals had better pay attention to is how "soft PLCs","PACs" ,and industrial computers are using commercial, closed source, operating systems that are being changed more and more quickly in keeping pace with consumer device marketing, rather than industrial needs. If these systems are being expected to replace PLCs that were left in place for 20+ years along with a piece of equipment that is still kicking, you can expect trouble at some point. Throwing out industrial equipment because OS marketing has made an operating system "obsolete" has already proven to be expensive indeed. When I see claims that a 10 year supported lifespan on an "embedded" version of an OS is considered "long term", I just look around at all of the equipment that says otherwise. If PACs and other industrial computer systems are to replace PLCs, their OSs will need a plan for far longer term support than this, and a plan to guard simplicity and reliability from the encroachment of corporate "IT" updating, networking, and security concerns driven by dealing with non-industrial computers and networks. </p>

    Reply

  • <p>@Daniel Automation003 : If you find "The distinction between "PACs" and PLCs is pretty fuzzy", see the chart at <a href="http://bin95.com/PLC-PAC-Difference.htm">http://bin95.com/PLC-PAC-Difference.htm</a> You will learn it is not just the programming langueges that distiguesh them apart. There are vast differences, the primary ones being the architecture followed by the processor. (IE: PLC=microprocessor with single scan cycle, PAC= multiple full blow processors on computer architecture with multi-tasking.) The chart will make it less fuzzy for you. Also you would be surprised how many go with PACs even though the application does not require it. Many machine designers and system integrators go with whatever the end user request, even if the end user does not know the difference between the two. </p>

    Reply

  • <p>I describe my activity as an OEM inside a food packaging company. While we have a large base of legacy equipment here, we also engage in complete upgrades of that same legacy equipment. My first choice of controller is a PLC. I only go to a PAC if I need the horsepower or features that aren't available on my PLC.</p> <p>It truly does come down to the end user and what they are comfortable supporting. If you don't need all the fancy features then why push a PAC on someone? </p> <p>I use Allen-Bradley Micrologix 1400's with Parker XpressView HMI's. The cool thing about the Micrologix, and most people don't know this, is I get enough Ethernet connectivity to connect a Cognex Dataman 60 bar code reader. I also get connectivity to Modbus-networked A-B PowerFlex drives via a plug-in adaptor on the 9-pin port of the Micrologix. The Modbus connection allows for multiple drives on a single network and I get all of the important data registers to send commands and reference plus feedback of speed, torque and current for software trip monitoring. I have created a state of the art control system that is based on the old SLC-500 platform in a repackaged Micrologix coat.</p> <p>In my opinion, long live the PLC!!</p>

    Reply

  • <p>It seems to be a matter of definition. My definition of a PLC is a controller programmed in any of the IEC 61131-3 languages that supports real time monitoring of the code. You may call it a PAC, but to me it is just a modern PLC. So, PLCs will not die. </p>

    Reply

  • <p>I would like to thank you Marty. I enjoyed reading your article. I also appreciate the Control Design staff and all the readers thoughts on this subject. What could be more important than great control design as we move to M2M and get to make a very fast, very secure pass through. One student recently remarked, " It is amazing to realize that the big network is already being replaced ". Just keep the great articles coming. IoT gets a 10.</p>

    Reply

  • <p>Is it that time in the cycle again?</p> <p>25 years ago embedded microcontroller were going to replace the PLC. 20 years ago (and again 10 years ago) softPLCs were the end of it all. The PLC is still here.</p> <p>To my mind also the term PAC is a marketing ploy and simply describes a top end PLC. </p>

    Reply

  • <p>So a 86 8 bit PC is not still a PC when compared to a 64 bit, multitasking, i7 PC?</p> <p>Earlier PLCs had many of the functions (multitasking, interrupts, process functions, multiple langauges) you say differentiate PACs from PLCs. </p> <p>The SLCs direct replacement is a compact login, and the price is comparable. As is Control Logix to a PLC 5.</p> <p>As someone who has been programming the beasts for 30 years (nearly) there is no difference.</p>

    Reply

  • <p>I suppose I'm sort of lucky since the plant I work in is relatively new and we are using the Logix 5000 Rockwell processor series for the bulk of our control needs. From our point of view there would be no value in changing our control system since not only our installed base of ControlLogix, FlexLogix, and MicroLogix processors but our networking have evolved together over the last decade. Without a major incentive it would be cost prohibitive to change it and there is no discernible gain by doing so. As noted in the article, there has never been a case of a processor just locking up because its program froze and as a plant that operates pretty much 24/7 doing an unscheduled reboot at any time would be disastrous.</p> <p>I did note that the article focused on the simplicity of ladder logic and its relative ease of troubleshooting as if it were the only language used by PLCs. As other commenters have expressed, new generation PLCs can utilize not only Ladder, but Function Block and Scripted Text as well. We utilize all three in our programming, utilizing them where they are the most effective. I do not foresee PLCs going away any time soon due to the installed base and the noted deep level of knowledge by controls professionals. The changeover to PACs will be more of an evolution than a revolution. </p>

    Reply

  • This is a topic I have often thought about. For me it has always boiled down to the simplicity of things. PLCs in the past did not or do not require and operating system to function in their needed capacity. This to me was always the falling down point for “Soft PLCs”. Not only the fear of “Blue Screen of Death” but the even greater fear of industrial sabotage (hacking). Some of the hacks I have read about to PLCs came through their ability to communicate to and from other systems. In a hardened or isolated network environment this would operate without much issue. However, connect this same system to the internet (knowingly or otherwise) and you are open to all kinds of mischief. It is tough enough keeping disgruntled employees from creating trouble, let some malicious foreigner tip toe into your plant via the internet to play havoc with your systems would keep me from ever falling asleep at night.

    Reply

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