Search

Scope: Core (OPC-10000-*) All specs

63 result(s) for Profiles

OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

3.2 Specification parts

transport protocols and data encodings supported by OPC UA. Part 7 ( OPC 10000-7 ) - Profiles Part 7 specifies the Profiles that are available for OPC UA Applications. These Profiles provide ... used for conformance level certification. OPC UA Applications will be tested against the Profiles . Part 8 ( OPC 10000-8 ) - Data Access Part 8 specifies
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

4.3 Design goals

subset of these capabilities. To promote interoperability, OPC UA defines subsets, referred to as Profiles , to which Servers may claim conformance. Clients can then discover the Profiles of a Server ... tailor their interactions with that Server based on the Profiles . Profiles are defined in OPC 10000-7 . The OPC UA is layered to isolate the core design from the underlying
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

4.4.1.1 General

these parameters is not. This framework also defines a minimum set of security Profiles that all OPC UA Applications support, a subset of which can be enabled in each installation ... Profiles are defined
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

5.3.4.2 AddressSpace organization

defines OPC UA Nodes and References and their expected organization in the AddressSpace . Some Profiles will not require that all of the UA Nodes be implemented
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

5.4 Redundancy

what Redundancy is supported by an OPC UA Application is defined by its Profiles . Profiles are described in OPC 10000-7 . Required Client and Server behaviours are associated with
OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts

6.1 General

availability of specific Service Sets and the Services within them depends on the Profiles supported by the Server . Profiles are described
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.5.2.3 Session communication layer

meet the OPC UA security objectives. Other details are provided as part of Profiles which are described in OPC 10000-7 (and available on-line at OPC Security Policies
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.7 Security Profiles

Security Profiles OPC UA Client and Server products are certified against Profiles that are described in OPC 10000-7 . Some of the Profiles specify security functions and others specify other ... functionality that are not related to security. The Profiles impose requirements on the certified products but they do not impose requirements on how the products are used. A consistent minimum
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

4.8 Security Mode settings

security Profile None. Security mode "none" is disabled for all other security Profiles . Profile None shall be disabled by default. The choice of "Sign
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

6.13 HTTPS, TLS & Websockets

enabled. It is recommended to only support TLS configurations provided in the TransportSecurity Profiles . SSL has security issues and should be disabled. It is important that it is disabled
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

9.1 Overview

certificate since more than one certificate could be required depending on the Security Profiles that are being supported. Asymmetric Cryptography makes use of two keys - a Private
OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

Annex A Mapping to ISA/IEC 62443-4-2 (informative)

topic that does apply the table lists the relevant OPC UA Parts and the Profiles / ConformanceUnits that covers the listed functionality. For each OPC UA Part that is listed (other ... column contains the actual ConformanceUnits that apply. For the row labelled OPC 10000-7 - Profiles, the keyword column contains the actual Profiles/Facets that apply. For more detail on the ConformanceUnit
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

1 Scope

will need to implement all of the defined Services . OPC 10000-7 defines the Profiles that dictate which Services need to be implemented in order to be compliant with
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.1 General

Service Set , or a Service within a Service Set , is defined by its Profile . Profiles are described
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.5.4.1 Description

also specifies a URI for the Transport Profile that the Endpoint supports. The Transport Profiles specify information such as message encoding format and protocol version and are defined ... algorithms used depends on the SecurityPolicy for the Endpoint . OPC 10000-7 defines Profiles for common SecurityPolicies and assigns a unique URI to them. It is expected that applications have
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.5.4.2 Parameters

that the returned Endpoints shall support. OPC 10000-7 defines URIs for the Transport Profiles . All Endpoints are returned if the list is empty ... this URL may have a query string appended. The Transport Profiles that support query strings are defined in OPC 10000-7 . Response responseHeader ResponseHeader Common response parameters. The ResponseHeader type
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.7.2.1 Description

identifies the capabilities of the Server and also contains the list of OPC UA Profiles supported by the Server . OPC UA Profiles are defined in OPC 10000-7 . Additional Certificates ... other organizations may be included to identify additional Server capabilities. Examples of these Profiles include support for specific information models and support for access to specific types of devices. When
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.14.1.4 Functions

TransferSubscriptions request is operating on behalf of the same user and supports the same Profiles as the Client of the previous Session . CreateNotificationMsg() Increment the SeqNum and create a NotificationMessage
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

5.14.7.3 Service results

InsufficientClientProfile The Client of the current Session does not support one or more Profiles that are necessary for the Subscription
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.14 EndpointDescription

Transport Profile supported by the Endpoint . OPC 10000-7 defines URIs for the Transport Profiles . securityLevel Byte A numeric value that indicates how secure the EndpointDescription is compared to other
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.35 SessionAuthenticationToken

enabled. In this cases, the SessionAuthenticationToken is a NodeId with a ByteString identifier. The Profiles in OPC 10000-7 may define additional requirements for a ByteString SessionAuthenticationToken. Client and Server
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.1 ServerType

TRUE if the Server generates audit events, otherwise to false. The Profiles defined in OPC 10000-7 specify what kind of audit events are generated by the Server . EstimatedReturnTime indicates
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.2 ServerCapabilitiesType

HasProperty Variable ConformanceUnits QualifiedName[] PropertyType Optional Conformance Units Base Info ServerType ServerProfileArray lists the Profiles that the Server supports. The String shall be the URI of the Profile ... definitions of OPC UA Server Profiles . This list should be limited to the Profiles the Server supports in its current configuration. LocaleIdArray is an array of LocaleIds that are known
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.4.27 AuditUpdateMethodEventType

Server . Note: This Property is optional for backward compatibility and required by Profiles starting with version 1.05. InputArguments provide the values of the input arguments passed to the Method . This ... arguments were returned. Note: This Property is optional for backward compatibility and required by Profiles starting with version
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

6.1 Security Handshake and Security Policies

called a SecurityPolicy . OPC 10000-7 defines standard SecurityPolicies as parts of the standard Profiles which OPC UA applications are expected to support. OPC 10000-7 also defines ... each standard SecurityPolicy . The latest versions of all SecurityPolicies are available in the online Profiles website. OPC 10000-7 defines the link to this website. A Stack is expected
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

7.1.3 Establishing a connection

that maps the domain name onto a usable network address. OPC 10000-7 defines Profiles for different name resolution protocols that Clients and Servers may support. If the Client creates
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

E.2 SecuredApplication

list of SecurityPolicyUris supported by a Server. The URIs are defined as security Profiles in OPC 10000-7 . Applications allow these values to be read or changed. Applications allow
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

1 Scope

Scope This document specifies value and structure of Profiles in the OPC Unified Architecture. The actual Profiles are maintained in an online database and accessible via https://profiles.opcfoundation.org ... Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing (tool based or lab based). This includes the testing performed
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

3.1.5 Facet

require Note 1 to entry: Facets are typically combined to form higher-level Profiles . The use of the term Facet in the title of a Profile indicates that the given
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

4.1 General

these features. The individual features are grouped into ConformanceUnits which are further grouped into Profiles . Figure 1 provides an overview of the interactions between Profiles , ConformanceUnits and TestCases . The large ... that are used to construct the parent. For example a Profile is constructed from Profiles and ConformanceUnits . The figure also illustrates a feature of the OPC UA Compliance Test Tool
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

4.3 Profiles

Profiles A Profile is a named aggregation of ConformanceUnits and other Profiles . To support a Profile , an application has to support the ConformanceUnits and all aggregated Profiles . The definition ... Profiles is an ongoing activity, in that it is expected that new Profiles will be added in the future. Multiple Profiles may include the same ConformanceUnit . Testing of a Profile
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

4.4 Profile Categories

Profile Categories Profiles are grouped into categories to help vendors and end users understand the applicability of a Profile . Table 1 contains the list of currently defined ProfileCategories . Table ... Profile Categories Category Description Application Profiles Application level Profiles represent a collection of Facets necessary to build a functional OPC UA Application.They specifically include Transport Profiles and generally also Security
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

4.5 Profile conformance

mandatory ConformanceUnits in a Profile in order to be compliant with the Profile . Some Profiles contain optional ConformanceUnits . Optional means that an application has the option to not support ... ConformanceUnits and whether they are supported or not by the tested OPC UA application. Profiles may also include other Profiles . If a Profile is included it means that
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

4.6 Conventions for Profile definitions

Conventions for Profile definitions Profiles have the following naming conventions: Profiles intended for specific application types have the application type in their titles. Currently defined application types are Server, Client ... Profile indicates that this Profile concerns a specific feature of OPC UA. Such Profiles are expected to be combined with Application Profiles to define the complete functionality
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

4.8 Applications

vendor that is developing an OPC UA application, shall review the list of available Profiles . From this list the vendor shall select the Profiles that include the functionality required ... single Profile may not yield a complete application. In most cases multiple Profiles are needed to yield a useful application. All UA applications shall support at least one Application Profile
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

4.5 Timestamps

Servers will support historizing SourceTimestamp (see OPC 10000-7 for details on Server Profiles ). If a request is made requesting both ServerTimestamp and SourceTimestamp and the Server is only collecting
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.2.1 General

that maps the domain name onto a usable network address. OPC 10000-7 defines Profiles for different name resolution protocols that Publisher or Subscriber may support
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

4.2 Architecture

also adds definitions for network services and component models for End Stations and Bridges. Profiles defining the selection of specific networking services supported by these component models are specified ... communication layer - see OPC 10000-15 for details on the OPC safety communication layer. Profiles will be developed in the future for Motion, I/O, and many types of process instruments
OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts

6.5 Profiles

Profiles A Profile is a named aggregation of ConformanceUnits and other Profiles ( OPC 10000-7 ). UAFX Profiles are defined in OPC 10000-84 . All OPC UA AutomationComponents will support ... more Profiles and any or all of its optional Facets
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.1 OPC UA FX ObjectTypes overview

includes many optional items. Some of these items are mandatory for controller-level Profiles but optional for embedded device Profiles . For a complete list of Profiles related
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.4.7 PubSub DataSets

please see OPC 10000-14 . PubSub communication has multiple options that are defined by Profiles . To see what is defined in UAFX for a controller or device, see the UAFX ... defined Profiles in the Profile database. When setting up communication between controllers, between a device and a controller, or even between devices, the engineering tool must ensure that the PubSub
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

E.6.1 Overview

Periodic-Fixed as the header layout Profile . Details for other transport or header layout Profiles could be added in a later version of this document
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

7.3.3 Information Model files

content of the Descriptor shall correspond to the online UAFX Information Model Profiles as described in the UAFX Offline Descriptor Profile (see OPC 10000-84 and http://opcfoundation.org/UA-Profile/UAFX-Offline-Descriptor-Profile ). Information
OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering

7.8.1 General

signing certificate shall be included. Descriptors shall only use cryptographic mechanisms from OfflineEngineering security Profiles defined in OPC 10000-84 . Descriptor signatures shall be validated as specified in ISO/IEC
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

1 Scope

part of OPC 10000 describes the OPC Unified Architecture Field eXchange (OPC UA FX) Profiles . The Profiles in this document are used to segregate OPC UA FX features with regard ... implementing OPC UA FX functionality. This testing will be performed in the same way Profiles defined in OPC 10000‑7 are tested. Most OPC UA FX applications will conform
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

4.1 General

General This document adds ConformanceUnits , ConformanceGroups , Profiles , and Facets grouping OPC UA FX features to the Profile Model defined
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

4.2 Profile Categories

Profile Categories UAFX Profiles are grouped into categories defined in OPC 10000‑7 to help vendors and end-users understand the applicability of a Profile . A Profile can be assigned ... have been added to support UAFX. Table 1 - UAFX Profile Categories Category Description Offline Profiles in this category specify functions for OfflineEngineering . Infrastructure Profiles in this category specify functions
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.1 Overview

categories that a Profile can be grouped into, a list of named Profiles, and the detailed listing of each Profile, including directly defined ConformanceUnits and any sub- Profiles included ... Profile . Subclauses in 6.6 describe Profiles in a tabular format
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.2 Profile list

Profile list Table 15 lists UAFX Profiles . The Profile table is ordered by in the order they appear in this document. The table includes a list of categories the Profile ... used to uniquely identify a Profile . The compliance of a product related to these Profiles is described in OPC 10000‑7 . Table 15 - Profile list Profile Related Category URI UAFX
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.3 Conventions for Profile definitions

Conventions for Profile definitions The Profiles defined in this document shall follow the naming conventions defined
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.4 Profile versioning

Profile versioning Versioning of the Profiles defined in this document shall follow the rules defined
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.5 Applications

Applications Figure 1 illustrates the Profiles and Facets that make up a UAFX Controller application. Figure 1 - Structure of the UAFX Profiles
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.4.1 Overview

Figure 7 , Figure 8 , and Figure 9 illustrate the structure of UAFX Controller Profiles and Facets . Figure 6 - Structure of the UAFX Server Profile Figure 7 - Structure of the UAFX
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.4.10 UAFX Controller 2024 Profile

details of the UAFX Controller 2024 Profile. This Profile is a collection of Profiles and Facets necessary to build a functional UAFX Controller , including a ConnectionManager . This Profile supersedes
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.6.5.1 Overview

Overview This clause defines Profiles and Facets for the UAFX OfflineEngineering illustrated in Figure 12 , Figure 11 , and Figure 12 . Figure 10 - Structure of the OfflineEngineering Descriptor Profile Figure
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

11 Profiles and ConformanceUnits

Profiles and ConformanceUnits Meaning and significance of Profiles and ConformanceUnits are described in OPC 10000-7 . The Profiles and ConformanceUnits for this specification are maintained in the online database
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

6.1 General

other, for example the identification of an asset is needed in most cases, the Profiles defined in section 15.2 combine the ConformanceUnits to functionality that is required to be provided
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

7 Identification of Asset

specification does not define or require a specific ObjectType or Interface , but ConformanceUnits and Profiles referencing mandatory and optional Properties as defined in OPC 10000-100 . The Properties defined
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

10.4 Supported OPC UA Functionality

supported OPC UA functionality in the ServerCapabilites Object , like the supported OPC UA Profiles in the ServerProfileArray . The corresponding ConformanceUnit is already defined in OPC 10000-7 . Therefore, this specification
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

9.2.3.2 RSL Base Client Profile

characteristics for all OPC UA Clients that make use of this companion specification. Additional Profiles will define support for various information models that are part of this document. Table
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

E.1 Example of subtyping SpatialLocationType using the RSL concept

ConformanceUnits of the RSL concept, as defined in the RSL CartesianFrameAngleOrientation Profile ( 9.2.2.2 ), new Profiles can be created to represent spatial relationships in other formats
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

4.2.3.1 Concepts

support all functionality in the OPC UA specifications. OPC UA includes the concept of Profiles , which segment the functionality into testable certifiable units. This allows the definition of functional subsets ... that are expected to be implemented) within a companion specification. The Profiles do not restrict functionality, but generate requirements for a minimum set of functionalities
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

11 Profiles and Conformance Units

Profiles and Conformance Units Meaning and significance of Profiles and ConformanceUnits are described in OPC 10000-7 . The Profiles and ConformanceUnits for this specification are maintained in an online database