7 reasons to a consider a non-Ethernet industrial network

Here are seven reasons non-Ethernet networks might be specified for an industrial project, to help determine if an Ethernet, fieldbus, or a device or sensor-level network should be considered.

06/05/2013


This control cabinet, with the master controller for a NYC tunnel boring machine, shows three CC-Link networks. Fieldbus networks, such as CC-Link, do not require switches to guarantee control system determinism and can be laid out in multiple configuratiWhy or when should non-Ethernet protocols be considered for an automation project? Seven reasons follow, showing when non-Ethernet networks might be specified for an industrial project. These can include simplicity, flexibility, familiarity, and consistency, even if logic might suggest otherwise.  

1. Simplicity. For some automation engineers, it is the simplicity of fieldbus networks that tips the scale for them to decide to use one of these non-Ethernet-based fieldbus network instead of an Ethernet-based network. These non-Ethernet-based traditional fieldbus networks generally require less hardware and may be much less complex than their Ethernet-based counterparts. For example, fieldbus networks do not require switches to guarantee control system determinism, whereas some Ethernet-based networks require complicated Ethernet switches to guarantee control system determinism.

2. Flexibility. In addition, most fieldbus networks can be laid out in multiple configurations (line, tree, line-tree combination, and ring). Most Ethernet-based networks are much more restrictive in how they are laid out for a project.

3. Familiarity. Another reason non-Ethernet protocols should be considered is a situation when automation engineers and the maintenance staff on the project have used the same non-Ethernet-based network for quite some time, they are comfortable with this technology, it works for their current application, and they do not see the benefit of adopting a new Ethernet-based network for a new application.

Also, perhaps, for this specific project situation, a new Ethernet-based network would not provide them with a significant productivity boost, and the potential cost savings would not justify learning a new Ethernet-based network technology. With all of this information, the project leaders cannot justify adopting a new Ethernet-based network, so they continue to use the same non-Ethernet-based network on this new project.

4. Consistency for an incremental expansion. In another situation, a company has an application that uses a non-Ethernet-based network. Automation engineers are considering expanding that application to include more automation, and this expansion can usually be completed more cost effectively using the same non-Ethernet-based network by adding more stations to the current non-Ethernet-based network. Expanding an existing application using the same non-Ethernet-based network maintains consistency throughout the application and allows use of the same tools and current products without requiring operators and maintenance staff to learn a new system and how to use new tools.

5. Policy. A company also may declare that all projects shall use a specific non-Ethernet protocol for all automation projects. Automation engineers and the maintenance staff may be comfortable with current technology, but automation engineers may understand that the benefits and potential cost savings would justify learning a new Ethernet-based network technology. Company management, however, has so much invested in the current specific non-Ethernet protocol that they do not want to invest in a new generation Ethernet-based protocol, so they may decide to continue to use the prior protocol.

6. Automation experience. A different situation where non-Ethernet protocols should be considered is when a company is new to automation networking. Using a fieldbus network may be easier to justify because that technology has been around longer and is deemed more reliable; or perhaps the engineers on the plant floor have been requesting some automation for years and have always requested a fieldbus network, because when they initially requested this “new” automation networking, Ethernet networking was not viable or available.

7. Equipment compatibility. In another circumstance, during the investigation phase of the automation project, it was discovered that not all of the necessary equipment would be available to communicate using an Ethernet-based network. Therefore, to maintain and use one network for the automation project, an appropriate non-Ethernet-based network should be considered for direct communications among all necessary equipment.

- John F. Wozniak, PE, is a networking specialist with CC-Link Partner Association. Edited by Mark T. Hoske, content manager, CFE Media, Control Engineering and Plant Engineering, mhoske(at)cfemedia.com

ONLINE

www.CCLinkAmerica.org 

See related articles below on industrial Ethernet and on the NYC tunnel boring case study from 2011:



Anonymous , 06/11/13 08:18 PM:

I agree. In my personal opinion, one size does not fit all. You need both Ethernet and fieldbus for different devices in automation just like your laptop has both Ethernet and USB for different peripheral connections, or Wi-Fi and Bluetooth for the wireless devices.

Ethernet is a good fit at level 2 (control network) and level 1-1/2 (remote-I/O, drives, wireless gateways) of the Purdue reference model. However, at level 1 (field instruments) you need two-wire bus power, intrinsic safety / non-incendive, simple junction boxes for thousands of devices, rugged connections, and 1-2 km long wires etc. and the ability to connect a simple handheld field communicator in parallel at any point for field service. This is where fieldbus fits best. For real-time time synchronized process control loops digital from sensor to actuator that means FOUNDATION fieldbus.
The Top Plant program honors outstanding manufacturing facilities in North America. View the 2013 Top Plant.
The Product of the Year program recognizes products newly released in the manufacturing industries.
The Leaders Under 40 program features outstanding young people who are making a difference in manufacturing. View the 2013 Leaders here.
The new control room: It's got all the bells and whistles - and alarms, too; Remote maintenance; Specifying VFDs
2014 forecast issue: To serve and to manufacture - Veterans will bring skill and discipline to the plant floor if we can find a way to get them there.
2013 Top Plant: Lincoln Electric Company, Cleveland, Ohio
Case Study Database

Case Study Database

Get more exposure for your case study by uploading it to the Plant 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.

Bring focus to PLC programming: 5 things to avoid in putting your system together; Managing the DCS upgrade; PLM upgrade: a step-by-step approach
Balancing the bagging triangle; PID tuning improves process efficiency; Standardizing control room HMIs
Commissioning electrical systems in mission critical facilities; Anticipating the Smart Grid; Mitigating arc flash hazards in medium-voltage switchgear; Comparing generator sizing software

Annual Salary Survey

Participate in the 2013 Salary Survey

In a year when manufacturing continued to lead the economic rebound, it makes sense that plant manager bonuses rebounded. Plant Engineering’s annual Salary Survey shows both wages and bonuses rose in 2012 after a retreat the year before.

Average salary across all job titles for plant floor management rose 3.5% to $95,446, and bonus compensation jumped to $15,162, a 4.2% increase from the 2010 level and double the 2011 total, which showed a sharp drop in bonus.

2012 Salary Survey Analysis

2012 Salary Survey Results

Maintenance and reliability tips and best practices from the maintenance and reliability coaches at Allied Reliability Group.
The One Voice for Manufacturing blog reports on federal public policy issues impacting the manufacturing sector. One Voice is a joint effort by the National Tooling and Machining...
The Society for Maintenance and Reliability Professionals an organization devoted...
Join this ongoing discussion of machine guarding topics, including solutions assessments, regulatory compliance, gap analysis...
IMS Research, recently acquired by IHS Inc., is a leading independent supplier of market research and consultancy to the global electronics industry.
Maintenance is not optional in manufacturing. It’s a profit center, driving productivity and uptime while reducing overall repair costs.
The Lachance on CMMS blog is about current maintenance topics. Blogger Paul Lachance is president and chief technology officer for Smartware Group.