Search

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

40 result(s) for Conformance Units

OPC-10000-2 – OPC Unified Architecture - Part 2: Security Model

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

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 than ... will describe the OPC UA related functionality. For the row labelled OPC 10000-7 - ConformanceUnits, the keyword column contains the actual ConformanceUnits that apply. For the row labelled
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

3.3 Conventions for Node descriptions

introduced to point to the Node definition. Each Node defined in this specification has ConformanceUnits defined in OPC 10000-7 that require the Node to be in the AddressSpace ... defined in this specification shall be exposed as well. The relations between Nodes and ConformanceUnits are defined at the end of the tables defining Nodes , one row per ConformanceUnit
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.2 ServerCapabilitiesType

MaxMonitoredItemsQueueSize UInt32 PropertyType Optional HasComponent Variable <VendorCapability> BaseDataType ServerVendorCapabilityType OptionalPlaceholder HasProperty Variable ConformanceUnits QualifiedName[] PropertyType Optional Conformance Units Base Info ServerType ServerProfileArray lists the Profiles that the Server ... VendorCapability> Variable is used to provide information about the server-specific capabilities. ConformanceUnits is a QualifiedName array specifying the set of conformance units the Server supports. This list should
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.5 SessionDiagnosticsObjectType

have the SecurityAdmin role, defined in OPC 10000-18 . The additional definition for the ConformanceUnits of AuditActivateSessionEventType are defined in Table 15 . Table 14 - SessionDiagnosticsObjectType Additional Conformance Units BrowsePath Conformance
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

F.3 UANode

locales. There shall be only one entry per locale. Category String [] A list of ConformanceUnits associated with the Node . The ConformanceUnits are specified by the authors of the UANodeSet ... allow users of the UANodeSet to exclude Nodes based on a selection of ConformanceUnits . When an UAInstance has the ParentNodeId specified, the UAInstance inherits the ConformanceUnits from its parent
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

4.1 General

This document provides a grouping of 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 arrows indicate the components that are used to construct the parent. For example a Profile is constructed from Profiles and ConformanceUnits . The figure also
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

4.2 Conformance Units and Conformance Groups

portions of services or information models) that can be tested as a single entity. ConformanceUnits are the building blocks of a Profile . Each ConformanceUnit can also be used ... appear in more than one ConformanceUnit . For improved clarity, the large list of ConformanceUnits is arranged into named ConformanceGroups . These groups reflect different OPC UA aspects like the Service Sets
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 ... include the same ConformanceUnit . Testing of a Profile consists of testing the individual ConformanceUnits that comprise the Profile . Profiles are named based on naming conventions (see 4.5 for details
OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles

4.5 Profile conformance

Profile conformance An OPC UA application shall implement all mandatory ConformanceUnits in a Profile in order to be compliant with the Profile . Some Profiles contain optional ConformanceUnits . Optional means that ... testing. The test result that is generated by the certification testing lists all optional ConformanceUnits and whether they are supported or not by the tested OPC UA application. Profiles
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

6.4 Arrays, index ranges and substrings

ranges and substrings Historians are not required to be able to store arrays. Optional ConformanceUnits exist to indicate if they support storage of arrays. If a Historian does store arrays ... returning an index range in an array, it may only provide the entire array. ConformanceUnits are provided to indicate if a Historian supports index ranges. For ReadProcessedDetails, some Aggregates
OPC-10000-15 – OPC Unified Architecture - Part 15: Safety

11 Profiles and Conformance Units

Profiles and Conformance Units Figure 28 shows an informative overview of the Facets and ConformanceUnits pertaining to this document. For normative reference consult the Profile Reporting at https://profiles.opcfoundation.org/ . Figure ... informative) - Facets and ConformanceUnits
OPC-10000-24 – OPC Unified Architecture - Part 24: Scheduler

9.1 Conformance Units

Conformance Units Table 44 defines the corresponding ConformanceUnits for the OPC UA Information Model for Scheduler. Table 44 - Conformance Units for Scheduler Category Title Description Server Scheduler Scheduling Base Exposes
OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model

4.1 Overview

illustrated types/instances are required for an implementation and are covered by separate ConformanceUnits and Facets . Figure 2 - Overview of LogObject Information Model
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
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

3.3.4 ConformanceUnits and Node definitions

ConformanceUnits and Node definitions Each Node defined in this document references at least one ConformanceUnit. (defined in OPC 10000-84 ). If a Server supports the ConformanceUnit , it shall expose ... defined in this document shall be exposed as well. The relations between Nodes and ConformanceUnits are defined at the end of the tables that define Nodes , with
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

D.4.1 Raspberry Pi example

certified application, the URL would provide the details related to the Profile/Facets and optional ConformanceUnits related to this product's certification. Figure D.36 - AutomationComponent expand example
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

5.1 Overview

represents an individually testable entity. For improved clarity, the list of ConformanceUnits is arranged into named ConformanceGroups . Table 2 lists the ConformanceGroups that reflect the UAFX Information Models and features ... These ConformanceGroups and the ConformanceUnits are detailed in the following subclauses. Table 2 - ConformanceGroups Group Description UAFX Base Defines ConformanceUnits for all UAFX Controllers and devices . UAFX AutomationComponent Defines ConformanceUnits
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.5 UAFX FunctionalEntity

UAFX FunctionalEntity Table 6 describes FunctionalEntity related UAFX Information Model ConformanceUnits. For additional information about these items, please refer to OPC 10000‑81 . Table 6 - UAFX FunctionalEntity Category Title Description ... FunctionalEntity ), supports at least one of the UAFX IFunctionalEntity InputData or UAFX IFunctionalEntity OutputData ConformanceUnits . Server UAFX IFunctionalEntity InputData Supports InputData of the IFunctionalEntity Interface . This includes a Reference
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.3.2 UAFX Ethernet networking features

UAFX Ethernet networking features Table 8 describes UAFX Ethernet Networking Features ConformanceUnits which describe IEEE 802 features of End Station Components , Bridge Components , IA-stations , and UAFX Stations. For additional
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.3.3 UAFX Ethernet Networking Quantities

UAFX Ethernet Networking Quantities Table 9 describes UAFX Ethernet Networking Quantities ConformanceUnits which define concrete values or value ranges for UAFX Ethernet Networking Features ConformanceUnits listed in Table 8 . Table
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.4.3 UAFX OfflineEngineering Descriptor Security

UAFX OfflineEngineering Descriptor Security Table 11 describes UAFX OfflineEngineering Security ConformanceUnits which describe the security policies for signing Descriptors. For additional information about these items, please refer
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.4.4.1 Overview

Overview This subclause describes UAFX Descriptor contents ConformanceUnits . The ConformanceGroups included are UAFX Descriptor Contents - UAFX Information Model, UAFX Descriptor Contents - Networking Information Model, UAFX Descriptor Contents - Core UA Information
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.1 Overview

list of named Profiles, and the detailed listing of each Profile, including directly defined ConformanceUnits and any sub- Profiles included in the Profile . Subclauses in 6.6 describe Profiles
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

6.2 Profile list

subclause of 6.6 . Each table may contain references to additional Profiles and/or ConformanceUnits . If a Profile is referenced, it means that it is completely included. The ConformanceUnits are referenced using
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

Agreement of Use

Profile. 10807 Errata Missing Conformance Units that require Descriptor to contain preconfigured DataSets Added ConformanceUnits UAFX Descriptor preconfigured PublishedDataSet and UAFX Descriptor preconfigured SubscribedDataSet, and made them mandatory ... both." 10837 Clarification CUs with Connection Endpoint Descriptor content - Required Changes Reworded ConformanceUnits UAFX Descriptor ConnectionEndpoint Base, UAFX Descriptor ConnectionEndpoint PubSub, and UAFX Descriptor IFunctionalEntity ConnectionEndpoints 10838 Clarification
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

3.3.1.1 Node definitions

short name can be used. Each Node defined in this specification has ConformanceUnits defined in 11 that require the Node to be in the AddressSpace . If a Server supports ... defined in this specification shall be exposed as well. The relations between Nodes and ConformanceUnits are defined at the end of the tables defining Nodes , one row per ConformanceUnit
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

different use cases, that can be used independent of each other. The ConformanceUnits defined in section 15.1 reflect those individual functionalities. As not all concepts are independent of each other ... asset is needed in most cases, the Profiles defined in section 15.2 combine the ConformanceUnits to functionality that is required to be provided together
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

7 Identification of Asset

this 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

8.1 Overview

Note that a Server might not provide both entry points, depending on the supported ConformanceUnits . Note that an AliasName could point to several Nodes representing the same asset (not shown
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

15.1 Conformance Units

Conformance Units Table 54 defines the corresponding ConformanceUnits for the OPC UA Information Model for Asset Management Basics. Table 54 - Conformance Units for Asset Management Basics Category Title Description Server
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.1.1 Node definitions

Each Type Node or well-known Instance Node defined shall have one or more ConformanceUnits defined in 7.1 that require the Node to be in the AddressSpace . The relations between ... Nodes and ConformanceUnits are defined at the end of the tables defining Nodes , one row per ConformanceUnit . The ConformanceUnits are reflected in the Category element for the Node definition
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

7.1 Conformance Units

Conformance Units Table 38 defines the corresponding ConformanceUnits for the OPC UA Information Model representing specific OPC UA DataTypes for built-in XML data types. Table 38 - Conformance Units
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

8.1 Conformance Units

Conformance Units This chapter defines the corresponding Conformance Units for the OPC UA Information Model for Industrial Automation (see Table 60 ). Table 60 - Conformance Units for Industrial Automation Category Title
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

5.3 Overview of subtypes of BaseDataVariableType

Annex E describes how other subtypes of SpatialLocationType can be created and used with ConformanceUnits of the RSL concept. Figure 3 shows an overview of Relative Spatial Location AddIns ... using the CartesianFrameAngleOrientationType as a subtype of the SpatialLocationType and which ConformanceUnits are defined to describe implemented instances. Figure 3 - Relative Spatial Location Information Model overview The folder RelativeSpatialLocations, described
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

9.1 Conformance Units

Conformance Units Table 23 defines the corresponding ConformanceUnits for the OPC UA Information Model for RSL. Table 23 - Conformance Units for Relative Spatial Location Category Title Description Server RSL Base
OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location

E.1 Example of subtyping SpatialLocationType using the RSL concept

CartesianFrameAngleOrientationType ConformanceUnit ) for a created subtype of SpatialLocationType and combining this with ConformanceUnits of the RSL concept, as defined in the RSL CartesianFrameAngleOrientation Profile ( 9.2.2.2 ), new Profiles can be created
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.1.1 Node definitions

Each Type Node or well-known Instance Node defined shall have one or more ConformanceUnits defined in 0 that require the Node to be in the AddressSpace . The relations between ... Nodes and ConformanceUnits are defined at the end of the tables defining Nodes , one row per ConformanceUnit . The ConformanceUnits are reflected in the Category element for the Node definition
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