A Framework for Implementing Process
Applications using CIP Technologies
Vivek Hajarnavis, Rockwell Automation
Dawn Kelsch, Micro Motion
Rizwan Mohammed, Honeywell
Michaël Voegel, Endress + Hauser Digital Solutions
Presented at the ODVA
2022 Industry Conference & 21st Annual Meeting
March 9, 2022
San Diego, California, USA
Introduction
The use of the Ethernet communication technologies has become significantly more prevalent in recent
years, with market share data indicating that EtherNet/IP™ is one of the market leaders [i]. Although
EtherNet/IP has been adopted by a broad range of industries, it is recognized that the process industries
are an opportunity for growth.
The term “Process” encompasses many different industries, from applications in the Life Sciences, theproduction of oil & gas, chemical manufacture and the treatment of Water and Wastewater. These
industries all have different needs and priorities. These industry sectors in turn will have their own
characteristics and requirements. Whilst a skid for producing pharmaceutical reagents may sharecharacteristics with a packaging machine, a refinery is likely to have its own unique requirements. For
example, the physical characteristics and size of a refinery or chemical plant is likely to lead toautomation components that are separated by long physical distances. This type of application is likely totake additional measures to avoid the risk of explosion.
Regardless of the industry, what differentiates process applications from discrete applications are
relatively slow control loops, and update rates between devices that can be on the order of 100’s of ms.
The impact of this is that the performance demands on EtherNet/IP target devices is lower thanapplications in the discrete industries. In contrast, the scale of some process applications means thatscanner class devices may have additional demands in terms of the number of connections. In generalterms, although this means that devices developed in the discrete industries can also be deployed inprocess, the environment in which they are deployed, and specific application needs drive an additional
set of requirements that are needed to facilitate the use of EtherNet/IP devices in these industries.
Initiatives such as the Advanced Physical Layer (Ethernet-APL™) are gaining significant attention [ii]owing to the opportunity it presents to extend the reach of EtherNet/IP into areas in which ethernet has
not been deployed previously. However, this is just one of several areas where development is taking
place to facilitate the use of EtherNet/IP in process applications.
This paper provides an overview of the state of the industry, documenting areas where the state of the
CIP™ and EtherNet/IP technologies are mature enough for adoption and identifying areas where
additional effort is needed in order to facilitate the use in real applications.

2022 ODVA Industry Conference

1©2022 ODVA, Inc.

Personas
To illustrate how process applications are designed, installed, used, and maintained, we will define a
number of Personas:
Cassie – A Control Systems Engineer. Cassie has a background in traditional automation concepts, andhas experience with controllers, instrumentation and actuation. She also has experience with fieldbusessuch as ControlNet but has had limited direct exposure to IT herself. She is well aware of the need for IT
and OT personnel to collaborate – as a prerequisite for delivering the converged architectures needed forcontemporary digital manufacturing solutions.
Edward – An Instrument Engineer with responsibility for selecting instrumentation to meet the needs ofthe process.
Isabelle – An Instrument Technician who has to maintain a broad variety of instruments from a number ofdifferent vendors.
Ned – A Network Engineer who spent the first part of his career supporting network infrastructure for asoftware development company. He chose to move into manufacturing in order to take on a freshchallenge. He has a good understanding of networking as applied in IT but is developing his knowledge ofthe operations domain.
Sam – A Security Architect. Like Ned, he has a background in IT, but with the increased convergence ofIT and OT, he now has responsibility for ensuring that the complete installation follows industry bestpractices. His job is to ensure that all aspects of the facility are designed in a way that ensure the key
requirements of Confidentiality, Integrity and Availability are all met.
Facility Design
Cassie has been tasked to create a process plant network that fulfills the following requirements:
1. 24/7 uptime for the highly available part of the process.
2. Protection from an emergency event for the critical system operators.
3. A hazardous area for both new and legacy devices.
4. Remote access to the system for troubleshooting.
5. Access to process data for process improvement analytics.
6. Simple set up and configuration of instrumentation
Cassie knows about controllers and instrumentation but is not as knowledgeable about network security
and topologies so she elicits the help of two IT professionals from her company - Ned, the Network
Engineer and Sam the Security Architect. Cassie has experience with ControlNet so she turns to other
CIP technologies to meet her needs.
To learn more about CIP technologies, Cassie attended a workshop where several of the technologies
were described. Cassie learned that device profiles are standardized collections of CIP objects thatallows similar device types from different manufacturers to expose control, configuration and diagnostic
data the same way. She also learned that the industry has developed a standardized information model,
called PA-DIM, to upload data to the cloud. Cassie is very excited to see how these concepts can beused to fulfil her needs.
Architecture
As a starting point for developing their architecture, Cassie, Ned and Sam consider ODVA’s guidelines for
EtherNet/IP Network Infrastructure [iii], Cybersecurity, [iv] as well as vendor documentation [v] and create
the network in Figure 1.

2022 ODVA Industry Conference2©2022 ODVA, Inc.

Figure 1

Controller and Device Redundancy
Looking at the details of the specification, the team notes that the application on which they are working
on requires a very high level of fault tolerance. The common mechanism by which this is achieved inprocess industries is through the use of controller redundancy consisting of at least a pair of controllers(primary and secondary). The most crucial applications can require yet more controllers. The primarycontroller operates the input/output (I/O), and it executes control logic and communication tasks. PhysicalI/O and other smart devices are arranged on one or more fieldbus network for access by both processors.
In addition, the primary controller must update or mirror itself to the secondary continuously to ensure that
I/O status, memory values, and any program changes are shared between the controller pair. This
ensures that the secondary controller is ready to assume control seamlessly if needed.
In the event of a major fault—such as a power failure, rack fault, or processor error the primary controller
switches over to the secondary, which should seamlessly continue with operation without any LOC (Lossof Control) or LOV (Loss of View). This action is known as switchover or failover.
Cassie notes that at present, controller vendors have proprietary mechanisms implemented with CIP
devices to ensure there is no LOV or LOC during switchover/failover. Techniques used include the use of
IP address switching, Gratuitous ARP (GARP) and hold/freeze of process values. With this approach,there is potential for unexpected results as device vendors are not following a standardized mechanism
for achieving the switchover from primary to secondary. Furthermore, she notes that some of the devices
she wishes to use within her architecture do not support GARP, and therefore a connection loss is
experienced when control switches from primary to secondary.
These observations suggest that although redundancy solutions are available, there is a need tostandardize the Redundancy and Controller failover/switchover scheme to have seamless integration of
CIP devices in process industries – and to achieve full application coverage.
High Availability and Media Redundancy
In line with many process applications, the specification with which Cassie is working with calls for highavailability – defined as the ability for the system to tolerate a single failure. Looking initially at the media,
Ned notes that a number of options are possible – for example the Rapid Spanning Tree Protocol(RSTP). Cassie points out that although this might work for the connection to the SCADA and the broader
plant, the convergence speed of this standard protocol is not sufficient for maintaining a connection
between a controller and a device. Based on this feedback, Ned chooses to implement the Device Level
Ring (DLR) protocol. The DLR protocol provides the means to detect, manage, and recover from single
faults in a ring-based network. It is intended primarily for implementation in EtherNet/IP end devices that2022 ODVA Industry Conference

3©2022 ODVA, Inc.

have multiple Ethernet ports and embedded switch technology and allows applications requiring media
redundancy to be realized. The protocol provides for fast network fault detection and reconfiguration to
support the most demanding control applications. Cassie agrees this is a sufficient approach since theinstrument technician staff is readily available to replace any failed device.
One of the ways in which this is achieved is through the use of a protocol such as the Parallel
Redundancy Protocol (PRP). From Cassie’s experience, she knows that this works well with EtherNet/IP
devices because the media redundancy protocol works completely independently of the application.
However, she notes that in many cases, the devices that she wishes to use do not support PRP natively,
and that switches with Redundancy Box (RedBox) capabilities are needed to realize the architecture. She
feels that being able to purchase more devices with native PRP support would simplify her architectures
Long Cable Runs and Connectivity to Hazardous Areas
Cassie notes that as per the requirements of the facility and there are some parts that need to be locatedmore than 100m from the nearest ethernet switch. Cassie also has to install devices within a hazardous
area. Whilst fiber optic cables can be used for the network infrastructure, this cannot be used forconnecting to instruments directly as it would require separate distribution cabling to provide power to thedevices.
Cassie knows that not every device or switch can be installed in a hazardous area, so she and Ned work
together to create a network solution that complies with hazardous area approvals. Cassie finds existing
devices that support 4-20mA HART® protocol – in which the transmitters are powered by the control loop.
They also identify newly introduced devices that support Ethernet-APL in which the power for the
instrument is supplied over the network. They note the simplicity in using this technology owing to theability to use existing two-core cable that is already present in the facility. They also note that functionally,
EtherNet/IP instruments for Ethernet-APL are identical to other EtherNet/IP instruments. They see that
this presents an opportunity to collect information from devices from which the level of diagnostic
information had been limited to either a standard analog loop or to what was available over HART –noting also that the move from HART to EtherNet/IP also provided a much faster update rate.
From a network architecture perspective, Ned explains that standard industrial Ethernet switches cannot
be used for either type of devices so Cassie and Ned research the types of switches needed and realizes
a HART translator is needed to communicate with the 4-20mA HART devices and an Ethernet-APL switch
is needed to integrate the Ethernet-APL devices. They conclude that Ethernet-APL is a technology thathas an opportunity to significantly enhance the information available regarding the performance of theirfacility.
Connecting to Legacy Technologies
Cassie is told by her management that part of the installation will make use of a skid that will betransferred from another facility. As she investigates the specifications of this skid, she realizes that it is
20 years old. From her history in the industry, she expects that it might have some ethernet connectivity,
but that its capability is likely to be limited. Her expectation is that the instrumentation is likely to be using
4-20mA HART.
Isabelle and Cassie have long recognized the difficulty in using HART instrumentation. Process
maintenance teams have long been challenged with gaining access and connectivity to service theirlowest-level field devices. Traditionally, plant personnel needed to walk out to the processing area anduse a handheld communicator or web server to connect to each device individually – a process that cantake hours. This, together with the need for better real-time information on the performance of devices
has driven a desire for better EtherNet/IP device connectivity.
Although Cassie would like the skid to be upgraded to use EtherNet/IP instrumentation, her management
tells her that she has a limited budget for the integration of the skid. Furthermore, she notes that some of
the more specialized devices on the skid do not have an EtherNet/IP equivalent on the market. She notes
however that the EtherNet/IP Specification from ODVA defines a standard mechanism for integrating
2022 ODVA Industry Conference

4©2022 ODVA, Inc.

HART devices into the Common Industrial Protocol (CIP). Using this mechanism, a CIP originator (suchas an industrial control system) can communicate with a HART device as if it is a native CIP device. The
result is seamless communication between CIP-based devices and HART-based devices, without
needing any changes to the HART devices or the CIP originators: from the CIP originator’s perspective,
the HART device appears as a CIP target device, with CIP objects and with CIP communication
mechanisms. However, from the HART device’s perspective, all HART commands originate from theTranslator in the form of standard HART commands.
In summary, Cassie notes that the ability to use a HART to CIP translator meets the immediate need for
integrating HART devices into a CIP architecture.
Meeting Safety Requirements
Safety in process can mean different things depending on the specific industry. The chemical, oil and gas
industries all aim to avoid the release of hazardous or explosive substances into the environment. Like
the discrete industries, all facilities have a goal of protecting their employees from injury or death.
In the case of the facility being designed by Cassie, the safety specification calls for the use of Safety
Instrumented Systems (SIS) as defined by the IEC61511 [vi] standard, which covers the application ofelectrical, electronic and programmable electronic equipment in the process industries. This requires thecomponents of the system to meet a Safety Integrity Level (SIL) rating. The complete application also has
to have a SIL rating. This calculation is based on the ratings for the complete process loop, covering thesensors, control logic and actuators. Cassie is aware that the IEC61511 standard references theIEC61508 for the design of safety components.
She is also aware of the CIP Safety™ standard. In studying the CIP Safety standard, she sees that it has
some useful characteristics: it ensures that the behavior of components in the event of a failure is welldefined. She sees that the features of the protocol provides the means to protect against faults arising forthe corruption of data, unintended repetition, incorrect sequence, loss of data, unacceptable delays,
insertion, masquerading and addressing faults. Cassie notes that it operates at the application layer anduses the black channel principle [vii], meaning that only the end nodes need to be safety certified and thatthat there is no need to certify the intermediate networking hardware – something which will no doubt beof interest to Ned, the Network Engineer.
However, she struggles to find any guidelines to help her use CIP Safety certified devices in applications
that need to be built according to the 61511 standard. She also notes that offerings from vendors areoften segmented, with specialized safety solutions being sold as a separate offer to standard DCS
systems. She decides to engage a specialized process safety contractor to help her meet the needs ofher application.
Security
The specification to which Cassie and Sam are working calls for them to follow industry best-practice for
ensuring that their facility is well protected. They have three key goals: to ensure that company assets(recipes and other confidential information) are not compromised, that the integrity of the operation is not
impacted, and that production can continue 24 hours a day, 7 days a week. At the same time, they have arequirement for real-time sharing of production information with management elsewhere in the world, andthey also need remote access to facilitate maintenance by global suppliers. This need rules out an air-gap
system.
Sam is aware that the industry standard for securing OT systems is IEC62443. Like Safety, this defines anumber of security levels and they believe that Security Level (SL) 3 – the provision of protection against
intentional misuse by sophisticated means with moderate resources, IACS-specific knowledge andmoderate motivation is a realistic target.

2022 ODVA Industry Conference

5©2022 ODVA, Inc.

Sam notes that two parts of the standard are most relevant. The 62443-3 standard applies to theirinstallation as users, and the 62443-4 standard applies to the devices that they deploy within the facility.
Cassie is also aware of the existence of CIP Security™ – which allows the communication between
devices to be secured. They note that there appears to be alignment between the needs of the standard
and the capabilities of the devices. Overall, Sam and Cassie feel that as with safety, further guidance isneeded to help them navigate the complexity of meeting 62443 certification and in understanding how
ODVA technology can help them to achieve this.
Commissioning and Integration
Aside from the architecture, Cassie and Edward are aware of the time it takes for the team to commission
and integrate devices into the control system and are looking for ways to simplify and speed up theactivity. They note that EtherNet/IP devices are coming on to the market with standardized device
profiles. They see these profiles as a way for her programmers to further standardize their interface
modules – and allowing the team to concentrate on developing and implementing their core control loops
and visualization concept.
Device Configuration and Management
Edward, the instrumentation engineer recognizes that this is an installation with a large number of
instruments supplied by a number of different vendors. He has extensive experience using AssetManagement solutions to configure instruments and uses the software tools to create backups of theconfigurations in each device.
Edward works with Isabelle to ensure that all the instruments in the installation are configured correctly
and the backup configurations are maintained. However, when Isabelle replaces an instrument, she does
not want to have to walk to an Engineering Workstation to restore a configuration. Having spent many
years maintaining devices, she prefers to use the front panel of the instrument. She has a paper notebook
where she writes down the parameter settings from the failed instrument (if she can) and after replacing
the instrument she enters the parameters from the old instrument into the replacement unit. Her
experience has meant that she has a sense for what the parameter settings in an instrument might be,
but she does not have the full insight into the functionality of the process held by her colleagues Cassie
and Edward.
As they investigate the capabilities of CIP devices, they see that mechanisms exist to facilitate theintegration of EtherNet/IP instrumentation into their DCS. However, they are surprised to see that different
manufacturers have interpreted the requirements in different ways. Consequently, they find that somedevices cannot be added to the control system at all. Other devices can be added but lack the capability
to be configured over the network. A third class of instrument can be added and configured but there islittle standardization between the interfaces.
They are also surprised to see that there is no equivalent to the Asset Management Software used by
Edward – although they do see that their existing tools can be used over the EtherNet/IP backbone
network – and that it has been recognized that a solution based on combining EtherNet/IP with otherstandards such as FDI can help deliver strong benefits to the user community [viii].
Although they are aware that some DCS suppliers offer some interesting capabilities in terms of device
configuration (and in some cases, for device replacement), and they are aware of ODVA’s xDS initiative[ix], they note that this latter solution is not yet complete and opt to remain with their existing asset
management software owing to the lack of standardization that exists across the devices they wish touse.
Device Maintenance in Use
In her role as instrument technician, Isabelle has to maintain the functional state of the process.
Inevitably, devices fail in operation and Isabelle has to replace them. Her life is made easier when the
instruments can report potential problems in advance of failure. Given that she has to support a range of2022 ODVA Industry Conference

6©2022 ODVA, Inc.

instruments, her work is made easier when problems are reported in the same way. She is tired of every
manufacturer designing instruments to report issues using proprietary definitions.
Isabelle airs her grievances to Cassie, and Cassie notes that ODVA has recently published the Process
Device Diagnostics object, which is based on the NAMUR NE 107 standard. When instruments
implement the Process Device Diagnostics object, the instruments provide Isabelle with a standardized
way of reporting instrumentation malfunctions and an indication if a process is operating out ofspecification. Isabelle can easily see which error reports are failures and need to be acted on
immediately and which are less critical and can wait for action.
Isabelle is especially happy when Edward, the Instrumentation Engineer, specifies instruments with theProcess Device Diagnostics object implemented. Now all Isabelle needs to do is convince Edward tospecify devices that can perform predictive maintenance. If she had techniques to help determine thecondition of the instruments in order to estimate when maintenance should be performed, she would nothave to make so many late-night calls due to failed instruments. Her maintenance activities would
become much more predictable and she would not waste the company’s money on performing tasks thatwere not warranted.
The team notes that the functionality they need is available in a limited range of devices to date and that
their needs will be best met when more manufacturers choose to implement the Process Diagnostics
Object.
Device Replacement & Interchangeability
Although Isabelle makes her best efforts to maintain instruments to the best of her abilities and to address
potential problems during scheduled downtime, inevitably, there are times when devices do fail during
production. Oddly, failures often occur when the facility is operating with a reduced staff – for example atnight or during the weekend.
Naturally, it is imperative for users to be able to replace failed equipment quickly in order to return toproduction. Having worked in different industries, he notes that there are different perspectives on how
this scenario should be managed. Owing to regulatory compliance, a life science application will require afailed device to be replaced with an identical unit to align with what has been validated by the relevant
regulatory authority. In contrast other process applications do not require the same level of regulatorycompliance.
For this scenario, Edward recognizes that the primary need is to allow the on-site maintenance staff to beable to use whatever instrument is available in stores, without having to worry about the manufacturer orbackwards compatibility with the firmware version. For example, a pressure transmitter manufactured byCompany A fails in the facility, but the maintenance store only has a pressure transmitter manufactured
by Company B on the shelf. Edward notes that ODVA is working on a series of device profiles tostandardize the data definition within EtherNet/IP instruments. ODVA recognizes that the user is looking
for the ability to work with “whatever works” – in other words, the ability to use an instrument or actuatorfrom any vendor and for it to be integrated into a Control System without anyone having to make anychanges to the program controlling the application. The Coriolis Flow profile is an example of the type ofdefinition that is needed in order to facilitate this use-case. Edward notes that the profile standardizes theconfiguration parameters across similar measurement devices – which Isabelle’s commissioning time
more efficient.
Overall, Edward and Isabelle note that ODVA offers the capability they need; however, as withmaintenance, their ability to use it is limited by the class of device in which it is available as well as thenumber of devices supporting it.
Compute and Cloud Connectivity
One of the strategic goals that Cassie needs to meet is for continuous process improvement. She isaware that data from the operations needs to be collected for analysis, and that this can be done using
compute capabilities either on-site or off-site. She is aware that OPC-UA is becoming a standard that is2022 ODVA Industry Conference

7©2022 ODVA, Inc.

gaining significant traction for cloud connectivity, and also that work has been done on mapping CIP
objects onto an OPC UA Information Model [x]. Further investigation reveals that a Device Information
Model for representing Process Devices has been published [xi]. She also aware that ODVA has
documented the Use-cases for a CIP Companion Specification for OPC UA [xii] and confirms that these
are in line with the requirements of her facility. She is also pleased to see that there is alignment between
the device profiles and the PA-DIM standard.
Overall, she concludes that her needs are well understood and the infrastructure she is selecting will
deliver the connectivity she requires, however she also notes that products based on these concepts are
not yet available.

2022 ODVA Industry Conference

8©2022 ODVA, Inc.

Summary
In summary, the process plant network that Cassie was tasked to create had several diverse
requirements and Cassie and her team was able to fulfill them by using ethernet as a backbone and CIP
technologies where appropriate. They conclude that the state of ODVA technologies allows them torealize the architecture of their operations in the way they see fit.
The principal observations are summarized below:
Feature / Need
Current Status
EtherNet/IP Device Integration
Available with EDS with limited
standardization. New
descriptor (XDS) and device
profile development inprogress
Simple Device Replacement
In progress for Coriolis flow
instruments
Diagnostics
Available through NE107
diagnostic object
High Availability
Available through DLR & otherprotocols
Media Redundancy
Available through PRP & otherprotocols
Device Redundancy
Deployment in Hazardous
environments
Security

SafetyDevice Configuration & AssetManagement

Legacy device integration
Compute and Cloud

Available using solutions thatuse proprietary technology
Available through the use of
Ethernet-APL
Architecture guidelines
available. Communication
protection available using CIP
Security
Aware of the existence of CIP
Safety noting that its focus atpresent appears to be on
discrete applications
Configuration available using
EDS or vendor-specific tools
however limited information
provided by vendors limits
scope to cover the full range ofapplications. No user interface
definitions available driving
vendors towards FDT DTM’s or
FDI Packages
Available using ODVA’s HART
on CIP definition
Profile alignment with PA-DIM

Future Need
Greater standardization ofinterfaces and more complete
device descriptions
New definitions for otherclasses of device
Broader adoption of the NE107
diagnostic object
No specific needs
Native support of layer 2
redundancy protocols in
devices such as PRP in
devices
Need to standardize
mechanisms for changeover
Broader adoption and a wide
range of devices with EthernetAPL connectivity
Ability to help users anddevelopers meet IEC62443
compliance. Broader adoptionof CIP Security
Guidance needed on how CIP
devices can help meet
applications built to IEC61511
Specifications to define how
CIP devices should map to
FDT DTM’s and FDI Packages.
Better defined information
models in next generation CIP
descriptors (xDS).

No specific needs
Continued collaboration with
the Common Cloud SIG

Conclusion
In conclusion, it is clear that many aspects of a process application can be achieved using ODVA
technology today. The fundamental function of exchanging information between sensors, controllers andactuators can be achieved using EtherNet/IP. Features exist that facilitate high availability topologies, full2022 ODVA Industry Conference

9©2022 ODVA, Inc.

system redundancy, deployment of devices over long distances, installation of equipment in hazardous
environments – all with a feature set that aligns with industry best practices. In addition, the integration ofolder technologies into a CIP based architecture can be achieved with ease. In use, there are means bywhich diagnostic information can be presented in a standardized way and there is a move towards
facilitating the exchange of devices without having to make changes to the control application.
There are however some areas where more work is needed, specifically in terms of providing guidanceon achieving process safety, further clarity regarding the use of CIP Security to meet industry standards,
defining a standard way for managing redundancy and in enhancing the way in which EtherNet/IP
devices are configured and managed.

References[i] HMS Market Share Report - https://www.hms-networks.com/news-and-insights/news-fromhms/2020/05/29/industrial-network-market-shares-2020-according-to-hms-networks [Accessed 22 Oct 2021][ii] Speilmann, B; Ethernet-APL, ODVA 2020 Industry Conference & 20th Annual Meeting March 4, 2020 Palm
Harbor, Florida, USA[iii] ODVA, Network Infrastructure for EtherNet/IP – Introduction and Considerations, PUB00035R0[iv] ODVA, Optimization of Cyber Security, PUB00278R2[v] Cisco and Rockwell Automation; Converged Plantwide Ethernet (CPwE) Design and Implementation Guide,
ENET-TD001E-EN-P[vi] IEC 61511; https://webstore.iec.ch/publication/5527[vii] IEC 61508; https://webstore.iec.ch/publication/5516[viii] Rao S, Chatrapathi GV and Yashaswini T, EtherNet/IP + FDI = Value in Process Automation; ODVA 2018
Industry Conference & 18th Annual Meeting October 10, 2018 Stone Mountain, Georgia, USA[ix] Snide, T, Brooks P, Leduc, D, Wolff, O; Basic background information on the development of the xDS concept,
ODVA 2018 Industry Conference & 18th Annual Meeting October 10, 2018 Stone Mountain, Georgia, USA[x] Chatrapathi GV, Sivansethu G, Bhanuprakash and Rao S, Mapping EtherNet/IP (CIP) object to OPC UA
Information Model, ODVA 2020 Industry Conference & 20th Annual Meeting March 4, 2020 Palm Harbor, Florida,USA[xi] FieldComm Group, Process Information Model, https://www.fieldcommgroup.org/sites/default/files/imce_files/technology/documents/PA%20DIM%20white%20paper%201.0.pdf [Accessed 5 December 2021][xii] Brooks P, Hopwood K, Latino F and Roby S, Use Cases for a CIP Companion Specification for OPC UA; ODVA2020 Industry Conference & 20th Annual Meeting March 4, 2020 Palm Harbor, Florida, USA******************************************************************************************************************************************************The ideas, opinions, and recommendations expressed herein are intended to describe concepts of the author(s) for the possible useof ODVA technologies and do not reflect the ideas, opinions, and recommendation of ODVA per se. Because ODVA technologies
may be applied in many diverse situations and in conjunction with products and systems from multiple vendors, the reader andthose responsible for specifying ODVA networks must determine for themselves the suitability and the suitability of ideas, opinions,and recommendations expressed herein for intended use. Copyright ©2022 ODVA, Inc. All rights reserved. For permission to
reproduce excerpts of this material, with appropriate attribution to the author(s), please contact ODVA on: TEL +1 734-975-8840
FAX +1 734-922-0027 EMAIL odva@odva.org WEB www.odva.org. CIP, Common Industrial Protocol, CIP Energy, CIP Motion, CIP
Safety, CIP Sync, CIP Security, CompoNet, ControlNet, DeviceNet, and EtherNet/IP are trademarks of ODVA, Inc. All othertrademarks are property of their respective owners.

2022 ODVA Industry Conference

10©2022 ODVA, Inc.