Manufacturing Software: Connectivity and Workflow

Manufacturing Software: Connectivity and Workflow

GE set up a conference call for a conversation with Matt Wells, general manager of automation software at GE Intelligent Platforms.

The impetus for the call was to flesh out the press release about the development of the Global Discovery Server (GDS) for OPC UA and the first implementation of it into GE’s Cimplicity HMI/SCADA software.

Wells said that GE is really embracing OPC UA as a core technology. Controllers have it embedded within, and in fact, GE actually evaluated it for inter-controller communication. That latter did not work out, but OPC UA remains core to GE’s connectivity program.

But, Wells continued, OPC UA is not always the easiest to implement. So GE worked with the OPC Foundation to define global discovery server to simplify management of systems.

The first advance concerns namespace. If GDS resides on the network, it will first register clients and servers then GDS provide list of namespace. And not only this, it can say who can talk to whom and it can also restrict who talks.

Secondly, GDS acts as certificate store. It is not a traffic manager, bu it checks for a certificate for all OPC devices and it then handles handshaking among them.

GDS is available as independent software that can be installed in an application. GE did Cimplicity first, partly to show it can be done and how useful it is.

GDS Agent, not part of spec, can act as proxy for existing UA that is not GDS enabled.

Using GDS in an OPC network enhancing usability and ease of implementation. This should increase the adoption of OPC UA.

When my contact set up this conversation, she also mentioned we could discuss something called, “automated operator decision support”. This intrigued me. Turns out this is an alternative phrase for automated or digitized workflow.

I’ve only talked with a few companies that have incorporated workflow. I talked with GE several years ago for the first time. This should be an important advance for manufacturing productivity.

Here are some notes about the workflow conversation.

Overall in HMI/SCADA
1-prevent mistakes so minimize abnormal situations
2-can’t always encode everything, so give advance notification, predictive analytics
3-cant predict everything, so enable operators to quickly ID issue and solve, give corrective action procedures
4-“phone a friend”, utilize mobile techs to call SMEs; We found highest adoption enabling support staff, contact experts, decrease downtime

Digitize SOP policy, workflow; work to encode workflows, as it executes SOP solicit feedback from operator, can coordinate acts of operators and people around them. Make every operator the best operator—baked in—originally sold as risk management mitigation tool. It is popular in pharma and water, especially areas where compliance is crucial.

First step, look at compliances and improving process – process

Take written manual–>encode–>provide checklist–>maybe write directly into system for records–>then after compliance, start looking at optimizing.

It is designed to layer over existing infrastructure (HMI/SCADA, WMS, etc.).

Have seen performance improvements of up to 30%.

Manufacturing Software: Connectivity and Workflow

GE Implements Latest OPC-UA Standard–Device Discovery

GE announced it is the first to implement and release a new Global Discovery Server based on the new Part 12 of the OPC UA standards. I’m taking its word for being first, although I cannot find anyone else promoting it. This is a useful standard that should further expand use of OPC in industrial networks.

The GE Proficy Global Discover Server (GDS) automatically discovers OPC UA devices on the network and connects to them with no configuration, saving time and reducing costs.

GE has standardized on OPC UA as an interoperability standard across several GE businesses.

The Global Discovery Server automates the previously manual and complex processes associated with connectivity and certificate management. The technology supports both the push and pull of certificates.

GE has also released a new version of the company’s CIMPLICITY HMI/SCADA product. CIMPLICITY is now an OPC UA Client and future releases will deliver more OPC UA client and server capability. As an OPC UA-enabled HMI/SCADA, CIMPLICITY can aggregate data from other OPC UA devices, add context to that data for analysis, and even provide that contextual data to other OPC UA servers at other system layers within an enterprise. Security is improved through the use of secure-by-design OPC UA. Reliability is higher, as OPC UA is designed to work on lower bandwidth connections and devices like radio modems.

OPC-UA provides a standard for GE devices and equipment, and the company now has multiple OPC-UA enabled devices: the PACSystems RX3i and RXi and MarkVIe are OPC UA-enabled controllers. Other GE products adopting the standard include: ADAPT3701, GE Oil & Gas’ System 1 condition monitoring software, 8 Series for primary or backup protection for underground and overhead medium voltage feeders, and 3 Series multifunctional feeder relays.

In addition to multiple OS platforms, companies have a multitude of legacy systems and equipment in place. GE’s OPC UA-enabled software can aggregate the data from these legacy systems and equipment and eliminate these islands of information. Even for devices that are unaware of OPC UA, the GE server can still manage certificates and trust lists for those devices, using Proficy Agent which acts on their behalf.

Manufacturing Software: Connectivity and Workflow

OPC Foundation Real-Time And Technology Partners

OPC Foundation LogoFor being so quiet for so long, the OPC Foundation is certainly hitting the news often lately. There was news about a couple of open-source initiatives. Then the Foundation itself opened up a little with an “open-shared” program.

Then it was announced as the communication platform of Industry 4.0 in Germany.

Now a couple European automation rivals—Beckhoff Automation (Germany) and B&R Automation (Austria)—have made OPC news.

Taken in sum, these announcements plus the earlier ones reveal the importance of OPC to industrial communication. It became a standard for moving important data from control systems to human-machine interface systems and then on to SCADA and MES systems.

With the introduction of UA built on modern software technologies including built-in security and embeddable format, the technology everyone used but also everyone dissed finds itself on the cutting edge of modern connected industrial Internet strategies.

 OPC and Beckhoff

News coming from last month’s Hannover Messe included this joint announcement from OPC and Beckhoff.

OPC UA is about scalable communication with integrated security by design up to MES / ERP systems and into the cloud, EtherCAT is about hard real-time capability in machines and factory control systems. Both technologies complement each other perfectly.

Industrie 4.0 and Internet of Things (IoT) architectures require consistent communication across all levels while using Internet technologies: both in as well as outside of the factory, for example to cloud-based services. That exactly is what the OPC Foundation and the EtherCAT Technology Group (ETG) want to account for by defining a common definition of open interfaces between their respective technologies.

At the Hanover Fair Thomas J. Burke, President and Executive Director of the OPC Foundation and Martin Rostan, Executive Director of the ETG signed a Memorandum of Understanding in which both organizations agree to closely co-operate developing these interfaces.

OPC and B&R

Not to be outdone, B&R Automation issued a press release announcing it will be supporting the OPC Foundation’s new real-time technology working groups, whose goal is to add real-time capability to the OPCUA communication standard. This will involve two key additions to the OPCUA standard. The first is a publisher-subscriber model; the other is utilization of the IEEE 802.1 standard for time-sensitive networking (TSN).

B&R will be contributing its real-time expertise to the working groups. “The updates to the OPC UA standard will benefit from our years of experience in developing real-time solutions,” says Stefan Schönegger, marketing manager at B&R.

OPC UA uses a publish/subscribe network model. B&R is the main proponent of PowerLink. PowerLink uses publish/subscribe technology, too. So, B&R wants to show compatibility.

“This is a fundamental requirement for the M2M communication you find in integrated systems such as packaging lines,” explains Schönegger.

In order to fulfill real-time requirements, the OPC UA standard will make use of the IEEE 802.1 TSN standard. “At the moment, TSN is still a working title for a group of new IEEE standards designed to provide native real-time capability for the IEEE 802 Ethernet standard,” says Schönegger. This would allow for a seamless transition to substantially faster Ethernet standards such as POWERLINK for field-level communication and demanding motion control tasks.

Beyond the automation industry, TSN is currently also being evaluated by the automotive and telecommunications industries. “The first cars based on TSN are expected to hit the market in the very near future,” reports Schönegger. This would help secure the widespread availability of this technology. In addition to B&R, the new OPC working groups will be also supported by other leaders in the field of automation, as was announced by KUKA on April 13, 2015.

OPC UA already plays a central role in the IT-related areas of modern production systems. “The addition of TSN and the publisher-subscriber model will greatly expand the range of potential OPC UA applications,” says Schönegger.

Takeaway

What all this means is that OPC can now become even faster and more usable than before. The little protocol that everyone uses and everyone complains about is getting cred as it becomes more modern. These technological advances should make it more valuable. And that will be significant in this new connected enterprise era.

Technology Standards for Industrie 4.0 Include OPC

Technology Standards for Industrie 4.0 Include OPC

Thomas BurkeNews about further adoption of OPC (www.opcfoundation.org) continued to flow from the recent Hannover Fair (Messe) in Germany. Things had gone dark for a period of time from the Foundation. This has changed over the past couple of weeks as the communication technology picks up momentum.

The Platform Industrie 4.0 (I4.0) announced at Hannover Messe 2015 a reference architecture model for Industrie 4.0 (RAMI 4.0). RAMI 4.0 is a unified architecture model where use-cases, standards etc. for I4.0 are necessary. In RAMI 4.0 I4.0 components are defined in their structure and functioning. Thus it enables cross-company networking and integration across value-added networks. Where meaningful, RAMI 4.0 builds on existing and relevant standards.

The Platform Industrie 4.0 trade organizations BITKOM (IT), VDMA (Mechanical Engineering) and ZVEI (Electronics) together collected and analyzed necessary or relevant standards for RAMI 4.0 in technically oriented working groups. In the category “Communication Layer“ the OPC UA (IEC 62541) standard was thoroughly examined and deemed adequate for RAMI 4.0 as the one and only confirmed.

“Companies like ThyssenKrupp are implementing Industrie 4.0 today. The availability of established communication protocols is mission critical for such a timely implementation, OPC-UA is here the best example,” said Dr Achatz head of technology at ThyssenKrupp AG.

“We are proud the Platform Industrie 4.0 thoroughly analyzed OPC UA in the category “Communication Layer” and confirmed its relevance as the only standard for the reference architecture model for Industrie 4.0,” said Thomas J. Burke, President and Executive Director of the OPC Foundation. “This shows that the OPC Foundation is on the right track with our approach of secure, safe, manufacturer- and platform independent communication for heterogeneous systems by means of OPC UA to become a global data exchange standard for Industrie 4.0 and the Internet of Things.”

Industrial Automation Connectivity Activity Open Source or Not

Industrial Automation Connectivity Activity Open Source or Not

Stefan_Hoppe_4sI have been writing about some open source initiatives with OPC UA. I think it’s cool and long overdue that there is so much happening in the OPC world lately. See these:

Open Source OPC UA Development

Open Source OPC UA for Manufacturing

Last week at Hannover, the OPC Foundation announced several items—including the promotion of Stefan Hoppe to Vice President of the Foundation (pictured). Another one deals with an open (sort of) source initiative designed to broaden the appeal of OPC outside of the industrial automation community.

OPC Announces “OPC UA Open Shared Source” Strategy

The OPC Foundation announced that the OPC Unified Architecture (OPC UA) specifications and technology will be made available to companies, consortiums, and end users without requiring membership in the OPC Foundation. The OPC Foundation is implementing an “open shared source” strategy to facilitate widespread adoption of the technology beyond industrial automation.

OPC UA provides a complete solution for information modeling allowing consortiums and vendors to plug in their simple or complex information models directly into OPC UA and take advantage of all of the OPC UA SOA allowing generic devices and applications to seamlessly share information.

The OPC Foundation open shared source strategy provides developers a quick jump start on the technology enabling prototyping projects without any barriers.

The OPC Foundation vision of interoperability providing the best specifications, technology, certification and process is the core of this open shared source strategy for the technology and specifications. The open shared source will be hosted on open source collaboration community work space. The OPC Foundation OPC UA stacks available to the OPC Foundation members will be under RCL license, allowing OPC Foundation members to build the highest quality OPC UA enabled products and then be able to certify the products through the comprehensive OPC Foundation certification and interoperability programs.

Stefan Hoppe, OPC Foundation Vice President, commented that “Adoption of OPC standards in industrial automation and specifically reaching out to other domains requires new ways of thinking to evangelize and increase awareness about the OPC Technology. OPC Unified Architecture is becoming the dominant infrastructure and information modeling architecture for the Internet of things and Industry 4.0, and these initiatives require complete transparency and open this about the technology to be a core part of their infrastructure.”

Continuing the Conversation

Andy Robinson pointed to a neat little app on OPC on YouTube. I replied and that led to a cool conversation between Andy and Rick Bulotta of ThingWorx. Here is what a nice little conversation can happen on Twitter. I’d like to invite more of these.

Andy Robinson ‏@archestranaut @garymintchell re OPCUA, thought you might be interested in this. It’s a small start but the vision is great! http://ow.ly/LWdXq 

Then Rick Bullota chimed in:

Rick Bullotta ‏@RickBullotta  why introduce #MQTT into the mix? it is a weak subset of OPCUA (no metadata, RPC, discovery)? #IoT

Andy Robinson ‏@archestranaut 100% for typical in the building plant floor apps. But for weak or expensive connectivity may be better.

Rick Bullotta ‏@RickBullotta living with “all of the above” here @Thingworx. MQTT is more like OPC (actually, NetDDE) than OPCUA.#IoT

Andy Robinson ‏@archestranaut also agree #mqtt maybe not ideal for commands as would probably require Qos2, not a huge deal…

Rick Bullotta@RickBullotta btw, I think it’s quite cool what you did though! nice work!

Andy Robinson @archestranaut not my work. Someone else.

Andy Robinson@archestranaut but I do think the basic idea of accepting not many new #IOT device will speak UA out of box leads us to .. . think about how we might integrate at least a subset of critical info into our already setup SCADA systems.

Andy Robinson@archestranaut I don’t suspect folks like Thingworx are looking to supplant traditional SCADA. At least doesn’t seem logical

Rick Bullotta @RickBullotta we’re already doing this with @ThingWorx via OPC/OPCUA, historians, HMI APIs, databases, and so on.

Andy Robinson@archestranaut  which is why you will be fine while other “similar” offerings will disappear on the low end

Rick Bullotta@RickBullotta correct. connecting, augmenting integrating and expanding their reach, whether within the plant or beyond.

Rick Bullotta@RickBullotta been there, done that, twice. 😉 I also founded Lighthammer (now SAP MII).

Andy Robinson@archestranaut nice to have a more civil convo after the last mini-twitp*** of about a month ago with others. 🙂

Follow this blog

Get a weekly email of all new posts.