OPCUA技术在工业物联网中的应用与优势

需积分: 1 82 浏览量更新于2024-06-26 收藏 4.26MB PDF 举报

"OPCF-eBook-v1-2020" OPC UA（OPC统一架构）是工业互操作性标准，它在自动化、通信和工业IT领域内扮演着重要角色。该电子书《OPCUA用户与专家：传递知识与经验》聚焦于OPCUA技术如何为工业物联网（IoT）中的终端用户、系统集成商和运营商带来益处和潜力。出版时间为2020年11月的第一版，由OPCF基金会发布，旨在通过一系列专家访谈和市场领导者的观点，阐述OPCUA的技术特点和优势。 OPCUA的主要特性包括： 1. **可扩展性**：OPCUA架构允许添加新的服务和数据类型，以适应不断变化的工业需求。 2. **国际化**：支持多语言，便于全球范围内的应用和交流。 3. **独立性**：不受特定硬件或软件平台限制，具有广泛的设备和系统兼容性。 4. **可靠性**：设计考虑了高可用性和故障恢复机制，确保数据传输的稳定。 5. **可伸缩性**：从小型传感器到大型云服务，都能实现无缝连接。 6. **跨域**：支持不同领域的互操作，打破传统领域的界限。 7. **协议无关性**：能够在多种网络协议下工作，适应各种网络环境。 8. **安全性**：提供强大的安全机制，保护数据传输的安全，防止未经授权的访问。电子书中第一章“OPCUA用于开放过程自动化”指出，OPCUA在2018年被开放过程自动化论坛（Open Process Automation Forum of The Open Group）选为连接框架的行业标准。这表明OPCUA在开放自动化领域的权威地位。例如，Don Bartusiak，CSI Automation的总裁，可能在书中讨论了OPCUA如何被接纳并应用于各种自动化场景。此外，该电子书还提供了通过Spotify、iTunes和Google等不同分发渠道获取OPCF基金会播客的方式，方便读者通过各种平台深入学习和了解OPCUA的相关知识。 OPCUA作为新一代的工业通讯标准，具备强大的互操作性和灵活性，正逐步成为工业4.0和机器对机器（M2M）通信的核心技术。通过OPCF基金会的电子书，读者可以深入了解OPCUA如何推动从传感器到云端的无缝数据交换，以及其在实现工业物联网愿景中的关键作用。

What is OPC, who is it for, and why should one care?

HOPPE: Well, today the acronym OPC stands for Open Platform Com-

munications. OPC is an interoperability standard which allows a secure

and

reliable data exchange in the area of industrial automation and other

industries. OPC is a completely independent platform that allows data to

move seamlessly between multiple devices from different vendors. It

scales from sensor to cloud. Users care about this technology for many

reasons, including a key role that OPC plays in Industrie4.0 and IIoT –

making data available across every automation sector.

What is the OPC Foundation and its role?

HOPPE: The OPC Foundation develops and maintains the entire set of

OPC speciﬁcations, but we also provide mechanisms to ensure the qual

ity of these standards though associations with compliance labs and

various

test tools. Since the speciﬁcation provides the mechanisms de-

scribing “how” to move data, we also collaborate with many other asso-

ciations, deﬁning “what” to exchange.

Her

e at the OPC Foundation, we feel a little bit like the United Nations of

automation, especially since our goal is to remain completely indepen-

dent – One big vendor cannot deﬁne the direction of the Foundation nor

what it is to do – It’

s democratic. Each year, half of the board members

are democratically elected, so no one can buy inﬂuence with money. We

are completely independent in taking care of this standard.

How can you, as an organization, accomplish such a huge goal?

HOPPE: Well, ﬁrst of all, you need to deﬁne a goal upon which everybody

in the world can easily agree. Then, of course, you need a critical mass of

companies to support this. The easy vision of the OPC Foundation is to

provide a standard where users and vendors come together to deﬁne a

mechanism to transfer data from multiple vendors and multi platforms in

a secure and reliable way. Since this applies to the area of industrial au

tomation, it has to scale in different areas. That’s an easy-to-understand

goal because everybody compr

ehends the beneﬁts.

Secondly, it’s important to keep the organization independent so that

nobody believes it is driven by a speciﬁc company. Acting independently

is the key for us to refer to ourselves as the United Nations of automation.

We want to be the neutral ground upon which everyone can easily meet.

Can you give us a little insight into the history of the OPC

standard, why and how it came to market, how old or how young

it is, and its major milestones?

HOPPE: I don’t want to spend a lot of time on its history, but I can tell you

a secret – OPC, in its early days, was called OLE for Process Control.

In 1990, SCADA companies had to write a lot of proprietary drivers to

connect to PLC controllers. The idea was born to take the Microsoft

COM/DCOM printer driver concept, to have standardized access to the

upper (north-side) port, and establish a proprietary last-mile to all the dif

ferent PLC controllers. That was the birth of what we now know as OPC

Classic. It pr

ovided live data, alarms, and historical data. It was mas-

sively successful. We had broad adoption inside the industry, but, of

course, we r

ecognized later that we needed to be platform independent;

we needed to integrate security; we needed a service-oriented architec-

ture mechanism inside. That’s why, from 2003 through 2006, we started

separating services

from data. This was the birth of OPC UA. UA stands

What is OPC?

Stefan Hoppe

President and Executive Director OPC Foundation

stefan.hoppe@opcfoundation.org

AN INTERVIEW WITH STEFAN HOPPE,

PRESIDENT AND EXECUTIVE DIRECTOR OF THE OPC FOUNDATION.

for Uniﬁed Architecture. We uniﬁed everything together into one architec-

ture and then we validated everything; we made prototypes; and then, at

last, in 2008, OPC UA was r

eleased.

Since then, we’ve had products on the market with no compatibility

break. Modern cloud applications connect to OPC data, even to devices

from 2007. Today, OPC UA is a complete technology, independent from

operating systems, independent from vendors, and it has security built in,

by design. That’s really important to understand.

Who are your members and what countries are they from?

HOPPE: All kinds of companies, in all kind of areas throughout the world.

I believe that OPC is the largest ecosystem for industrial interoperability,

worldwide. Our members are very small companies, the big giants of the

market, providers of technology, and, of course, end-users.

The status today is that OPC Foundation has more than 750 members in

all regions in the world. Analysts say that we have more than ﬁfty million

applications worldwide – It’s a huge ecosystem. Statistics indicate that

50% of our members are headquartered in Europe with around 25% in

the US and 25% in Asia, but I see that Europe and Asia are growing very

quickly.

What would you say is the is a major driver for this difference in

acceptance across the global markets?

HOPPE: Well, in Europe, there is the initiative called Industrie4.0, which

is named differently in a couple of countries. It’s all about how to make

workﬂows more efﬁcient; how to get data.

The scope of Industrie4.0 is huge; starting with how to design a product,

consideration for its entire life cycle, including the end of a product.

Whereas, OPC UA addresses mainly but not exclusively how to connect

during the production phases of the live data. The idea is easy to under

stand; you need something like a USB connector for machines, which

allows you to reduce engineering costs, and provides standardize data.

Think of the beneﬁt of having OPC UA in a device (or a machine) and then

being able to connect this machine within only 10 minutes to SAP MES,

or Microsoft Azure, to name just two of them. It is easy to understand.

That’s exactly why end-users like Volkswagen, Samsung, Foxconn,

Miele, and others have joined the Foundation; because they understand

these big beneﬁts. That’s a key value.

55 % EUROPE

8 % CHINA

8 % OTHER

6 % JAPAN

23 % NORTH AMERICA

OPC

Organization

Members

Tell us a little bit about the technology behind the OPC standard.

HOPPE: That’s not easy to explain – and we will deﬁnitely have separate

podcasts on that topic – but let me address it brieﬂy in three blocks. Be-

fore I do, however, we have to understand that OPC UA is not another

otocol. We have so many, we don’t need another one. In today’s world,

I believe that protocols are not really a high-value item. What is valuable is

the secure exchange of information and to know the meaning of that in-

formation.

So, ﬁrst of all, with OPC UA, you ar

e describing and modeling data inter-

faces that your machine or device should expose via live data, historical

data, alarms, and so on.

Then, secondly

, deeper within the OPC UA framework, we see different

communication mechanisms built in already by design. Client/server is

one, publisher/subscriber is another. These are still independent from the

real protocol beneath.

The third block is the real protocol binding layer. Here we are using OPC

over TCP, HTTPS, UDP, MQTT or whatever other protocols may come in

the future. Here you really see the beneﬁts, because you are deﬁning data

and information. Keep in mind, these models will persist for many years

to come, even when OPC is extending the protocol mechanisms to sup

port more endpoints for new and existing protocols, for even more use

cases.

Although designing data models is of key importance, security must be

built

in by design; and not just for the transport layer. Security also applies

to authentication, those who are allowed to access particular kinds of

data; how I manage a big factory; how I perform discovery and certiﬁcate

management automatically, and so on.

Graphic: OPC UA is not a protocol – instead it’s a framework to exchange

standardized data with end-to-end integrated security scaling from sensor to

cloud

So, you see that OPC UA is much more than a protocol. That’s why we

are not comparing OPC UA to protocols by asking, “should I use OPC UA

or MQTT?” No! More correctly, we are using MQTT inside the OPC UA

architecture! This allows us to move standardized data up into cloud sce-

narios.

As a standard, how do you make sure providers of the OPC

technology stick to the rules? Do you certify their products?

HOPPE:

In the beginning, the OPC Foundation started as a community

of vendors creating their own tools, for example, the CTT tool [Compli

ance Test Tool], which OPC corporate members can get at no cost. But

you don’

t even have to be a member paying member fees; you can just

buy that tool.

I believe that, today, the CTT performs 2000 test cases which you can

run against your product to prepare yourself so you can deliver a higher

quality product. Alternatively, we have labs in different regions through

out the world to test your product. Manufacturers can even participate

while sitting next to the test lab engineer

, if they wish. We perform

剩余37页未读，继续阅读

SECS&GEM

粉丝: 0
资源: 5

OPCUA技术在工业物联网中的应用与优势

OPCF-eBook-v6-2026

top-tech-trends-2020-ebook.rar

top-tech-trends-2020-ebook.pdf

instant-opencv-for-ios--ebook

Open-Source-CMS-eBook-Sampler

The-Zynq-Book-ebook-chinese

Linux GDB Debug -- Ebook in .doc --

The-Programmers-Idea-Ebook

30-days-of-react-ebook-fullstackio

vue-imooc-ebook

最新资源