Difference between revisions of "UA Capabilities"

From UaCapabilities
Jump to: navigation, search
 
(20 intermediate revisions by 3 users not shown)
Line 5: Line 5:
 
OPC UA is built on the following <b>Infrastructure</b>:
 
OPC UA is built on the following <b>Infrastructure</b>:
 
* <b>Discovery</b> which allows Clients to find OPC UA Servers, their supported protocols, security policies and other capabilities.
 
* <b>Discovery</b> which allows Clients to find OPC UA Servers, their supported protocols, security policies and other capabilities.
* <b>Transports</b> which provide capabilities needed to establish a connection and exchange well-formed messages between OPC UA Applications.
+
* <b>Transport</b> which defines protocol mappings that allow establishing a connection and exchanging well-formed messages between OPC UA Applications.
* <b>Information Access</b> which comprises the means to expose an Address Space with arbitrarily rich, object-based Information Models, and the Services to access this information.
+
* <b>Information Access</b> which comprises the means to expose object-based Information Models in an Address Space and the Services to access this information.
* <b>Security and Robustness</b>, which is a set of features integrated into Transport and Information Access.
+
* <b>Security and Robustness</b>, which are integrated into Transport and Information Access.
  
 
<b>Information models</b> are layered on top of this infrastructure. OPC UA specifies a number of base information models (DataAccess – DA, Alarms&Conditions – AC, and more) that define commonly used objects including both real-time and historical data variables and alarms. Industry standard models inherit from and further specialize the lower layer models they are based upon.
 
<b>Information models</b> are layered on top of this infrastructure. OPC UA specifies a number of base information models (DataAccess – DA, Alarms&Conditions – AC, and more) that define commonly used objects including both real-time and historical data variables and alarms. Industry standard models inherit from and further specialize the lower layer models they are based upon.
 +
----
 +
{| cellpadding="5" cellspacing="0" width="100%"
 +
|-
 +
|
 +
Following is the catalogue of OPC UA Capabilities structured according to the layers and subsystems of the UA Framework outlined before.
 +
|
 +
<div style="text-align:right;margin-right:10px;margin-bottom:4px;">'''[[Sequence of Capabilities|&#10148; Or read here for a sequence of all capabilities]] ...'''</div>
 +
|}
  
 
+
{| border="1" width="100%" cellpadding="5" cellspacing="0" align="center"
Following is the catalogue of OPC UA Capabilities structured according to these layeres:
+
 
+
{| border="1" cellpadding="5" cellspacing="0" align="center"
+
 
|-
 
|-
 
| rowspan="2" align="center" width="34%" style="background:#e2e2e2;" | <b>Infrastructure</b>
 
| rowspan="2" align="center" width="34%" style="background:#e2e2e2;" | <b>Infrastructure</b>
Line 43: Line 48:
 
* [[Field Device Integration (FDI)|Field Device Integration (FDI)]]
 
* [[Field Device Integration (FDI)|Field Device Integration (FDI)]]
 
* [[PLCopen Model (IEC61131-3)|PLCopen Model (IEC61131-3)]]
 
* [[PLCopen Model (IEC61131-3)|PLCopen Model (IEC61131-3)]]
 +
* [[BACnet OPC UA Information Model]]
 +
* [[Auto-ID Automatic identification systems]]
 
* [[MTConnect - Process information from numerically controlled machine tools|MTConnect Model]]
 
* [[MTConnect - Process information from numerically controlled machine tools|MTConnect Model]]
* [[Enterprise-Controlsystem Integration Model (ISA-95)|Enterprise-Controlsystem Integration Model (ISA-95)]]
+
* [[Enterprise-Controlsystem Integration Model (ISA-95)|Enterprise-Controlsystem Integration Model - ISA-95]]
 +
* [[Engineering Data for Production Systems (AutomationML)|Engineering Data for Production Systems - AutomationML]]
 +
* [[MDIS - MCS-DCS Interface Standardization]]
 +
* [[CNC Systems Information Model]]
 +
* [[SERCOS Information Model]]
 +
* [[POWERLINK Information Model]]
 +
 
 
|}
 
|}
 
 
 
[[allCaps]]
 

Latest revision as of 13:57, 2 October 2017

OPC UA has been designed for scalability and supports a wide range of application domains, ranging from field level (e.g. devices for measurement or identification, PLCs), to enterprise management support. To achieve these design goals, the OPC UA standard provides a multi-layered architecture as shown in the following figure:

UA Framework.JPG

OPC UA is built on the following Infrastructure:

  • Discovery which allows Clients to find OPC UA Servers, their supported protocols, security policies and other capabilities.
  • Transport which defines protocol mappings that allow establishing a connection and exchanging well-formed messages between OPC UA Applications.
  • Information Access which comprises the means to expose object-based Information Models in an Address Space and the Services to access this information.
  • Security and Robustness, which are integrated into Transport and Information Access.

Information models are layered on top of this infrastructure. OPC UA specifies a number of base information models (DataAccess – DA, Alarms&Conditions – AC, and more) that define commonly used objects including both real-time and historical data variables and alarms. Industry standard models inherit from and further specialize the lower layer models they are based upon.


Following is the catalogue of OPC UA Capabilities structured according to the layers and subsystems of the UA Framework outlined before.

Infrastructure Information Models
UA Base Models Industry Standard Models