Simplify Your Network with Better Tools, Common Sense
Industrial networks are easier to build and optimize with fieldbus, Ethernet, and new hardware. But it's still difficult to learn, implement, and trust new networks enough to gain promised advantages.
Physically easier. Mentally tougher. That's the assessment of users, integrators, and suppliers, who say designing, building, and renovating industrial networks is becoming simpler and easier to optimize thanks to Ethernet's emergence, increased fieldbus compliance, and more suppliers developing improved hardware and software tools.
This means far less hardwiring, which reduces labor, maintenance, training, and other expensive, physical needs. It also helps plant-level networks reach up, connect, and deliver data to Ethernet-based administrative systems and vice versa. 'The main change is that management wants to see what's happening, and this is where we see the opportunity to use Ethernet to work with existing control networks,' says Paul Wacker, automation marketing manager, Lantronix (Irvine, Calif.).
The flipside, sources say, is that it's psychologically harder to overcome the initial learning curve required to implement fieldbus protocols, Ethernet, and other sophisticated networking methods. Instead of traditionally dealing with one or two problems on many wires, some engineers' headaches now involve handling many problems on one or two wires. These challenges include configuring routers, resolving data traffic issues, and solving other communication and software problems-even if they occur on one twisted-pair wire.
'Configuring a PLC is relatively easy compared to configuring a network router. There are a lot more variables, and it requires a totally different skill set,' says Bob Kirk, sales and marketing manager, Spyne Inc. (Pittsburgh, Pa.), a four-year-old network integration firm.
Fortunately, not only are new networking methods gaining momentum among users, many suppliers are developing and delivering improved networking devices and infrastructure equipment to satisfy users' expected demands. These solutions and products can further simplify many networking projects, and help Ethernet and fieldbus achieve greater mainstream acceptance in manufacturing.
Climbing the learning curve
'Using rack I/O devices, plugging in cards, and working with PLCs may seem more straightforward, but users need to understand how flexible a fieldbus-based system can be,' says Charles Cook, advanced electronics products manager, Wago Corp. (Germantown, Wis.). 'Also, while fieldbus may be easier for electricians, who don't have to haul as much wiring, it may be an added burden for applications engineers, who have to configure it. That's a price of achieving greater long-term flexibility.
'We support more than 10 fieldbus protocols, and so one of our biggest jobs is helping first-time users build these networks. Still, the learning curve is steep enough that initial fieldbus installations may not seem worthwhile, and sometimes savings aren't achieved until the second project.'
If you know what you want to do and what you have, then you also have a better idea of what you need and what you don't need. This is a simple rule, but it remains the most powerful tool in designing, prioritizing, implementing, simplifying, optimizing, and maintaining industrial networks. Thoroughly understanding your business and manufacturing goals and capabilities can help you draft common sense specifications, resolve differences in networking methods, and secure the most efficient solution.
Besides simple awareness, several other guidelines can simplify networking projects. These include:
Compliance counts. The promise of open, interoperable networks is greater flexibility, simpler layouts, and increased component selection. However, communication obstacles remain, and users trying to solve specific manufacturing problems often simplify to one or two suppliers and their recommended networking methods that can handle most or all application requirements. Solving a networking problem today is generally more important than having flexibility that may or may not be needed in the future. Again, truly knowing your application and its needed capabilities can resolve trade-offs between openness and compliance.
Beyond overall compliance, using single-source proprietary device- and control-level networks can be less expensive in some cases than many 'open' networks because their chipsets are often more costly, according to Dave Quebbemann, industrial marketing manager, Omron (Schaumburg, Ill.). 'Users just have to make sure that they're comfortable being locked into one network or supplier.'
One more benefit of compliance is that devotion to one fieldbus protocol or other network technology helps concentrate development and education related to it, according to Mike Bryant, director, Profibus and AS-Interface trade organizations (Scottsdale, Ariz.). 'As fieldbus protocols mature, there are more adopters, which creates a software and tools market, and a wealth of lessons learned and instruction available,' says Mr. Bryant.
Some overkill OK. 'Simpler is not always best. For instance, using Ethernet to replace an AS-i system (see sidebar) may be simpler, but it can cost more,' says Nick Jones, special projects manager, SST (Waterloo, Ontario, Canada). 'To achieve true optimization, networking projects must take into account installation, training, and maintenance costs, as well as mean time between repair and mean time between failure calculations. In the short term, for example, an Ethernet network may not be as easy to debug as a more traditional one.'
Mr. Jones adds that relatively smaller manufacturers may not have as precise performance targets as larger organizations, but that it doesn't matter as much if a smaller user installs more capabilities than needed. 'It's human nature to play it safe, but it's not useful to design a network based on emotion or fear,' he says.
Inherent compatibility. Much like settling on one supplier, users can also simplify their network projects by using bridging and gateway devices equipped with inherently compatible fieldbus protocols, which usually means they require little or no added configuration. For example, DeviceNet, ControlNet, and EtherNet/IP share this compatibility; Profibus PA, DP, and ProfiNet are designed to work together; and Foundation fieldbus' H1 and High-Speed Ethernet protocols can function cooperatively. Users must then ask, 'How much configuration, software rework, or added hardware is needed to allow different parts of my network to communicate with each other at the speed, volume, and quality that they require?'
Inherent fieldbus compatibility can also reportedly help device- and control-level networks reach up-usually via Ethernet-to enterprise and administrative systems. However, links between plant-floor and administrative networks usually require an added gateway, firewall, or quarantine device, so upper-level network traffic doesn't disrupt lower-level functions. 'Ethernet appears to simplify networks, but it also moves a lot of responsibility up to the management information system (MIS) level,' says Mr. Jones.
Ethernet, Ethernet, Ethernet
Though it clearly has the greatest potential to aid network simplification and optimization, far more people talk about Ethernet than have actually implemented it in plant-level applications-so far. Critics usually report that Ethernet lacks determinism, reliability, robustness, and redundancy. However, Ethernet appears to be steadily proving itself industrial settings. For example, the increasing speed of many Ethernet-based applications is already diluting claims of its non-determinism, says Eric Byres, research team leader, Advanced Information Technologies Group, British Columbia Institute of Technology (BCIT, Vancouver, B.C., Canada). 'The criticism that Ethernet isn't deterministic is a giant red herring,' he says. 'Using Ethernet isn't as hard as it's made out to be.'
Spyne's Bob Kirk adds that, 'Ethernet can simplify your plant-floor board room connections, but you must first get onto that Internet protocol (IP) infrastructure. For instance, Fisher-Rosemount's (Austin, Tex.) DeltaV system has controllers that use IP to talk to workstations, which means its data is already available via Ethernet. What you need next is a secure, reliable connection between the IT and process control networks. Firewalls, network routers, and intrusion detectors can provide reliable, secure, and safe Ethernet connections that prevent these potential problems (see sidebar).' Redundant processors and connectors, as well as enhanced power security, can also improve Ethernet reliability.
'The main lesson is: Don't be afraid of Ethernet. You can do it. Just get the right information and people to help you implement it,' says Mr. Kirk.
Besides linking to Ethernet and increasing cooperation within fieldbus protocols, several organizations are trying to meet users' demands by improving communication between traditionally disparate protocols.
'Because some applications may need to services several protocols, we added multiple function blocks to Foundation fieldbus' HSE that allow it to interface with other protocols, such as ControlNet, DeviceNet, and Modbus' from Schneider Electric Automation (North Andover, Mass.), says Stephen Mitschke, applications engineer, Fieldbus Foundation (Austin, Tex.). Function blocks are pieces of software that allow devices on a network to identify themselves and their function, which gives users a picture or model of the network that can help manage traffic on it. Consequently, the mental challenges of industrial networking may soon become easier too.
|Search the online Automation Integrator Guide|
Case Study Database
Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.
These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.
Click here to visit the Case Study Database and upload your case study.