Search

200 result(s) for Information Model

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  2.1.17 Information Model
  Information Model organizational framework that defines, characterizes, and relates information resources of a given system or set of systems. Note 1 to entry: The core AddressSpace model supports the representation ... AddressSpace. See OPC 10000-5 for a description of the base OPC UA Information Model
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.6 Synergy of models
  ClientServer models are complementary and can be combined and used synergistically. The OPC UA Information Model is the foundation for both. A typical scenario involves using ClientServer interactions for configuration ... owner of information) and a Subscriber is often a Client . Above all, the PubSub Information Model for configuration promotes the configuration of Publishers and Subscribers using the OPC UA ClientServer
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  4.2 URIs
  formats for different use cases. 1) NamespaceUri assigned by the creator of a InformationModel : tag:<authority-domain-name>,<yyyy-MM>:UA:<model-short-name ... created. The <model-short-name> is a short identifier for the InformationModel . 2) ApplicationUri assigned by the OwnerOperator tag:<device-domain-name>,<yyyy
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.3.13 NamespaceMetadataType
  Variables which have a constant value. The optional ModelVersion Property indicates the InformationModel version expressed as a SemanticVersionString allowing programmatic comparisons. All current versions of UANodeSets published
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.1 Overview
  Overview Information Model developers define standard AddressSpaces which are implemented by many Servers . There is a need for a standard syntax that Information Model developers can use to formally define ... specification because of one or more semantic rule violations. There are cases where an Information Model defines Nodes such as standard Properties which can be attached to many different Nodes
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.15 Example
  UANodeSet can be found below. This example defines the Nodes for an InformationModel with the URI of " http://sample.com/Instances ". This example references Nodes defined in the base ... InformationModel and an InformationModel with the URI " http://sample.com/Types ". The XML namespaces declared at the top include the URIs for the Namespaces referenced in the document because
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  1 Scope
  representation of Alarms and Conditions in the OPC Unified Architecture. Included is the Information Model representation of Alarms and Conditions in the OPC UA address space. Other aspects of alarm ... captured in standards such as IEC 62682 and ISA 18.2 . The Alarms and Conditions Information Model in this document, is designed in accordance with IEC 62682 and ISA 18.2 . Annex
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  4.1 General
  General This document defines an Information Model for Conditions , Dialog Conditions , and Alarms including acknowledgement capabilities. It is built upon and extends base Event handling which is defined ... This Information Model can also be extended to support the additional needs of specific domains. The details of what aspects of the Information Model are supported are defined via Profiles
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.14.1 General
  expected from an OPC UA Server that is implementing the A & C Information Model . In particular this section describes specific behaviours that apply to various aspect ... Information Model
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.14.3 Redundant A & C servers
  servers In an OPC UA Server that is implementing the A & C Information Model and that is configured to be a redundant OPC UA Server the following behaviour ... standard Event s, Alarms and Conditions . This may be accomplished by sharing of information between redundant Server (such as actual Event s) or it may be accomplished by providing
• OPC-10000-10 – OPC Unified Architecture - Part 10: Programs
  1 Scope
  Scope This part of OPC 10000 defines the Information Model associated with Programs in OPC Unified Architecture (OPC UA). This includes the description of the NodeClasses, standard Properties, Methods ... Events and associated behaviour and information for Programs . The complete AddressSpace model including all NodeClass es and Attributes is specified in OPC 10000-3 . The Services such as those used
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  1 Scope
  This document is part of the OPC Unified Architecture standards series and defines the Information Model associated with Historical Access (HA). It particularly includes additional and complementary descriptions ... including all NodeClass es and Attributes is specified in OPC 10000-3 . The predefined Information Model is defined in OPC 10000-5 . The Services to detect and access historical data
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  6.5.1 Overview
  Overview The GlobalDiscoveryServer Information Model used for discovery is shown in Figure 12 . Most of the interactions between the GlobalDiscoveryServer and Application administrator or the Client will be via Methods
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  4.4 Synergy of models
  Synergy of models PubSub and Client Server are both based on the OPC UA Information Model . PubSub therefore can easily be integrated into OPC UA Servers and OPC UA Clients ... information) and a Subscriber is often an OPC UA Client . Above all, the PubSub Information Model for configuration (see 9 ) promotes the configuration of Publishers and Subscribers using
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.1 General
  concrete message and transport protocol mappings is defined in Clause 7 . The OPC UA Information Model for PubSub configuration in Clause 9 specifies the standard Objects ... done through a generic OPC UA PubSub configuration tool using the PubSub configuration Information Model defined in Clause 9 or through product-specific configuration tools. To support the PubSub configuration
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.1.1 General
  product-specific configuration tools or through the OPC UA defined Methods . The OPC UA Information Model for PubSub configuration is specified in Clause
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.2.1 General
  specific configuration tools or through the OPC UA defined configuration model. The OPC UA Information Model for PubSub configuration is specified in Clause
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  5.4.4 Configuration Tool
  Publishers and Subscribers are also OPC UA Servers , they can provide the PubSub configuration Information Model defined in Clause 9 . This model can be used by generic PubSub configuration tools
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.1 Overview
  Clause 7 . Configuration of these parameters can be performed through the OPC UA Information Model for PubSub configuration defined in Clause 9 or through vendor-specific mechanisms. The parameter groupings
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  8.1 Overview
  Overview Clause 8 specifies the OPC UA Information Model for a Security Key Service (SKS). The functionality and behaviour of an SKS is described in 5.4.5 . It defines the distribution
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  C.4 Synergy of models
  Synergy of models PubSub and Client Server are both based on the OPC UA Information Model . PubSub therefore can easily be integrated into OPC UA Servers and OPC UA Clients ... information) and a Subscriber is often an OPC UA Client . Above all, the PubSub Information Model for configuration (see 9 ) promotes the configuration of Publishers and Subscribers using
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  4.3 Features
  availability. For diagnostic purposes, the last SPDU sent and received is accessible in the Information Model of the SafetyProvider . Length of user data: 1 octet to 1 500 octets, structures
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.1 General
  SafetyConsumers and SafetyProviders , and to check their parameters for diagnostic purposes offline engineering: the Information Model of one controller can be exported in a standardized file on its engineering system ... relevant data. It is assumed that errors can occur during the transfer of the Information Model from one engineering system to another in the context of offline engineering. Therefore
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.5 Object SafetyPDUs
  definition of the SafetyPDUsType. Both variables in the SafetyPDUsType have a counterpart within the Information Model of the SafetyConsumer . The SafetyConsumer publishes the RequestSPDU and subscribes to the ResponseSPDU . Table
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.3.3.3 SPI of SafetyProvider
  safety-related way. However, it will be provided in the OPC UA Information Model of a SafetyProvider to inform about its worst-case delay time. The value can be used
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.4.1 General
  provided in a vendor-specific way. The Method ReadSafetyDiagnostics , defined in the OPC UA Information Model
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.4.3 Method ReadSafetyDiagnostics of the SafetyProvider
  polled, e.g. by a diagnostic device. For details, refer to the OPC UA Information Model described, see 6.2.2.4 . The Diagnostic Interface Method does not take any input parameters and returns
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  7.2.3.5 Signature over the SafetyData Structure (SafetyStructureSignature)
  considered when calculating the CRC . [RQ7.20] SafetyStructureIdentifier may be visible in the OPC UA Information Model for diagnostic purposes but shall not be evaluated by the SafetyConsumer during runtime. [RQ7.21
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  8.2 Safety function response time part of communication
  SafetyConsumerTimeout the SafetyProvider shall provide the SafetyProviderDelay as a Variable in the OPC UA Information Model , see Table 12 . Vendors may provide their individual adapted calculation method if necessary
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  Annex A Safety Namespace and mappings (Normative)
  found here: http://www.opcfoundation.org/UA/schemas/Opc.Ua.Safety.NodeIds.csv A computer processible version of the complete Information Model defined in this document is also provided. It follows the XML Information Model schema syntax defined ... Information Model schema released with this version of the specification can be found here: http://www.opcfoundation.org/UA/schemas/1.05/Opc.Ua.Safety.NodeSet2.xml The latest Information Model schema that is compatible with this version
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  Agreement of Use
  behaviour of the individual endpoints for safe communication, as well as the OPC UA Information Model which is used to access these endpoints. This document is application-independent and does
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.1 Overview
  define interactions between OPC UA Applications . Implementing these workflows requires an OPC UA Information Model . This section builds on existing Information Models and defines the additional types and instances needed ... completely implement the workflows. Clause 9.2 defines the Information Model implemented in a Registrar that provides support for PullManagement defined in 7.2 . Clause 9.3 defines the Information Model implemented
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  1 Scope
  Scope The Base Network Model (BNM) specifies an OPC UA Information Model for a basic set of network related components to be used in other Information Models . The initial version ... scope of other network technologies than Ethernet only. Figure 1 - Scope of Base Network Model
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  4.1 Object Serialization Basic Concept
  aggregation of the Values of different Variables belonging to a subset of the Information Model ( SerializationScope ) into the Value (SerializationValue) of a single Variable ( SerializedData ) . Clients gain access
• OPC-10000-26 – Part 26: LogObject - Part 26: LogObject Model
  1 Scope
  result in breaking changes in future versions of this Part. This document provides an Information Model for a set of Objects and Events that can be used to collect diagnostic ... information in a system. The LogObject model and related Events , Methods and Datatypes are defined in this specification
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  3.1.10 Descriptor
  using and configuring one or more AutomationComponents Note 1 to entry: A Descriptor contains Information Model files and other artefacts. Note 2 to entry: The primary purpose of a Descriptor
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  4.1 OPC UA FX specification parts
  Field eXchange (UAFX) summary. Part 81 ( OPC 10000-81 ) - UAFX Connecting Devices and Information Model Part 81 specifies the UAFX Information Model and describes how it can be used ... UAFX OfflineEngineering Part 83 specifies the data structures used for sharing information that supports the OfflineEngineering of UAFX systems. Part 84 ( OPC 10000-84 ) - UAFX Profiles Part 84 specifies
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  4.2 Architecture
  core OPC UA functionality for field-level communications. The foundation of the UAFX Information Model is the AutomationComponent . The AutomationComponent is an entity representing one or more Assets that ... many types of process instruments. Specifications, including Information Models , developed for those types of products will build upon the AutomationComponent model
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  5.2 The UAFX Solution
  UAFX Solution OPC UA FX specifies a standardised Information Model and connection model for AutomationComponents , providing timely data delivery, security, and functional safety. Interactions addressed by UAFX include Controller
• OPC-10000-80 – OPC Unified Architecture - Part 80: UAFX Overview and Concepts
  6.2 UAFX Information Model
  UAFX Information Model OPC 10000-81 defines the base Information Model and communication concepts that UAFX provides to meet the use cases of process and factory automation applications. These communication ... models defined in OPC UA, such as PubSub or Client Server 1 . The UAFX Information Model is based on the basic building blocks provided in OPC 10000-5 and utilises
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  1 Scope
  Scope This document provides an Information Model enabling data interoperability between systems in the field, including Controller-to-Controller, Controller-to-Device, Device-to-Device and Controller/Device-to-Compute. It includes base
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.1 Overview
  Overview This document provides a detailed description of Connection functionality and the related Information Model for OPC UA FX. For an overview, please
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.2 AutomationComponent model
  relationships is included in the model. Both Assets and FunctionalEntities can be nested. The Information Model also includes relationships between FunctionalEntities . For a detailed description of the asset model ... definition of FunctionalEntityType in 6.4 . For a description of the available ReferenceTypes in this Information Model , see 11.1 . Figure 1 - OPC UA FX Information Model overview The Information Model
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.3.1 Overview
  Overview This Information Model provides a general model for Assets in an OPC UA FX system (illustrated in Figure 2 ). An Asset is defined as a component with a lifecycle ... base concept of the asset model defined in this document. The OPC UA FX Information Model supports the modelling of hard Assets and soft Assets . A hard Asset represents physical
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.4.1 Overview
  Overview FunctionalEntities encapsulate logical functionality. The OPC UA FX Information Model defines an Object Model for FunctionalEntities . Figure 5 illustrates the Object Model, which includes general information about the FunctionalEntityType ... input variables, output variables, and diagnostic information. FunctionalEntities can be nested or have relationships to other FunctionalEntities . The Object Model also includes a representation of Connections (communication) between FunctionalEntities . Figure
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.4.3 FunctionalEntity type hierarchy
  examples of possible derivations). The model is defined using OPC UA Interfaces . An Information Model defined in another standard can add support for FunctionalEntities by including these Interfaces or deriving
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  4.7.1 Overview
  between FunctionalEntities . The ConnectionManager can execute on any Server supporting the OPC UA FX Information Model . In the OPC UA FX Information Model , the ConnectionManager is represented by the ConnectionManagerType ... illustrates possible deployments of a ConnectionManager . It also illustrates ConnectionConfigurationSets , which contain the information needed to establish Connections . Figure 9 - Examples of ConnectionManager deployments For a conceptual overview
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.1 Overview
  existing OPC UA communication models and are provided by the OPC UA FX Information Model . This clause conceptually describes the functionality provided in the overview of the Objects defined ... Information Model
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.5.3 Establishing and closing Connections
  ConnectionManager . If present on a Server , the ConnectionManager is represented in the Information Model by a well-known instance of ConnectionManagerType (see 6.7 ). To start the establishment of logical connection ... logical connections. For each logical connection to be established, the ConnectionConfigurationSet includes: address information, e.g., Server address, BrowsePath to the AutomationComponent , FunctionalEntity , etc., optional parameters to be used for verifying
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.6 Health
  allows a Client to easily detect whether diagnostic conditions are present somewhere in the Information Model . If the aggregated health status is "good", a Client does not have
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.8 Aggregation of OPC UA FX Servers
  information and/or source the information for higher-level applications, offloading the underlying Servers . The Information Model that is defined in this document can be aggregated. This clause provides some explanation ... This reflection can include Assets and FunctionalEntities , but it is expected that the communication model (between FunctionalEntities ) will only exist in the actual Servers , not in the AggregatingServer . Any actions
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  5.9 Well Known Roles
  role definition BrowseName Suggested Permissions 0:ConfigureAdmin The Role is allowed to browse the Information Model , execute methods related to application configuration, and read and write non-security-related configuration
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.1 OPC UA FX ObjectTypes overview
  document defines several ObjectTypes that can be used to create an OPC UA FX Information Model . It also specifies a number of Interfaces that can be applied to existing Information ... ObjectTypes , see Figure 17 . Figure 17 - Overview of OPC UA FX Information Model Since the OPC UA FX Information Model supports small embedded devices as well as powerful controllers
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.2 FxAssetType definition
  expect for the Asset . For examples of how to apply the OPC UA FX Information Model to other models, see Annex B . For examples of FxAssetType models, see Annex ... standards that utilise this Interface will likely introduce such classifications." Within this model, this information is typically used for display purposes only. It is recommended that if this Property
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.3 VerifyAsset method
  VerificationMode AssetCompatibility and expose the corresponding mandatory and implemented optional Variables in its Information Model . If at least one of the optional Variables, SerialNumber and/or ProductInstanceUri, is provided, then ... Variable was passed by the Client that does not exist in the Asset's Information Model ). If this value is set, VerificationVariablesErrors and/or VerificationAdditionalVariablesErrors shall be populated. Match : Shall
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.1 Overview
  base type for the definition of all functionality in an OPC UA FX Information Model . A FunctionalEntity can provide InputData , OutputData , ConfigurationData , diagnostic information and Methods for manipulating or sharing ... FunctionalEntityType . It can have SubFunctionalEntities and relationships to other Objects defined in this model or other models. A FunctionalEntity may be implemented using the IFunctionalEntityType Interface . It does not need
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.6.1 Overview
  represent an endpoint of a Connection between two FunctionalEntities for data exchange. It provides information about which InputVariables and/or OutputVariables are exchanged. ConnectionEndpoints reside in the ConnectionEndpoints Folder ... PubSubConnectionEndpointType to represent the exchanged Variables , as well as corresponding References to the PubSub Information Model . Figure 28 - Illustration of a Connection between FunctionalEntities
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.6.2 ConnectionEndpointType definition
  InputData . The optional OutputVariables reference Variables that are to be reported by the communication model connected to the ConnectionEndpoint . All referenced Variables shall be listed in the OutputData ... RelatedEndpointDataType is defined in 10.38 . If the ConnectionEndpoint is not exposed in the Information Model of the related connection partner, RelatedEndpoint will specify the path to the connected FunctionalEntity . IsPersistent
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.1 Overview
  instance of ConnectionManagerType ; see 12 for details on its location in the UAFX Information Model . Figure 34 - ConnectionManagerType illustration ConnectionConfigurationSets may be serialised into a file format as described
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.3.2 Establishing Connections
  Method provides several commands (see 10.23 ) to verify and create the individual Information Model Objects related to a Connection . Figure 36 illustrates the sequence of commands to a single AutomationComponent ... order: VerifyAssetCmd , VerifyFunctionalEntityCmd , ReserveCommunicationIdsCmd , and EnableCommunicationCmd . A Client using the Methods exposed in the Information Model (e.g., VerifyAsset , ReassignControl) can invoke them in any order or at any time
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.6 ConnectionManagerCapabilitiesType
  that the ConnectionManager can support . MonitorsLocalConnectionEndpoints, when true, describes the capability of the ConnectionManager Information Model to report the status of all the Connections created by this ConnectionManager that have ... ConnectionEndpoint on this Server. If this capability is not provided, or false, the ConnectionManager Information Model does not report the current status of Connections. NOTE In some cases, this status
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.8.1 Overview
  Connection configurations. Connections are grouped in a set, for example, to allow sharing communication model configurations by multiple Connections ; see 5.5.6.2.3 and 5.5.6.2.4 for appropriate use cases. ConnectionConfigurationSets are generated ... AddressSpace . A ConnectionConfigurationSet exposes diagnostic information about the Connections as part of its Information Model . It also allows Connection configurations to be available for modification by standard Clients (see Figure
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  7.2 IFunctionalEntityType Interface definition
  definition The functional model is required to be able to be applied to existing Information Model s. These models have defined their own Object Models and their own hierarchy ... does not support multiple inheritance. By defining the IFunctionalEntityType Interface , the OPC UA FX Information Model can be applied to any existing Object , adding the required IFunctionalEntityType items into
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.38 RelatedEndpointDataType
  name of the ConnectionEndpoint . In case an AutomationComponent does not expose ConnectionEndpoints in its Information Model , ConnectionEndpointName is set to null. A RelatedEndpointDataType is set to null by setting ConnectionEndpoint
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  11.1 ReferenceTypes overview
  ReferenceTypes overview In this Information Model , a number of References are defined. These References are illustrated in Figure 62 . Figure 62 - Reference overview
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  12.1 Overview
  Overview The OPC UA FX Information Model defines well-known instances (see Table 252 and Table 253 ) that are used to group OPC UA FX Object instances
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  12.2 FxRoot
  following instance shall exist in all Servers that expose an OPC UA FX Information Model . It is formally defined in Table 252 . Table 252 - FxRoot definition Attribute Value BrowseName
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  13.1 Overview
  requires more than just a Server with an OPC UA FX Information Model . All devices that implement the ConnectionManager are required to support Client functionality. This clause will describe ... Some additional key points related to establishing a connection are: The Connection and security information may have changed since the engineering tool generated configuration information ( ConnectionConfigurationSets ). The ConnectionManager
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  A.1 Namespace and identifiers for OPC UA FX Information Model
  Namespace and identifiers for OPC UA FX Information Model The OPC UA FX Information Model is identified by the following NamespaceURIs : http://opcfoundation.org/UA/FX/Data/ http://opcfoundation.org/UA/FX/AC/ http://opcfoundation.org/UA/FX/CM/ ... /nodesets/?u=http://opcfoundation.org/UA/FX/Data/&i=1 https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/FX/AC/&i=1 https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/FX/CM/&i=1 Supplementary files for the OPC UA FX Information Model can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/FX/Data/&v=1.00.03&i=2 https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/FX/AC/&v=1.00.03&i=2 https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/FX/CM/&v=1.00.03&i=2
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.1 Overview
  existing Information Models . Creating a new model based on the OPC UA FX Information Model (see B.2 ). Extending an existing OPC UA Information Model with ... parallel OPC UA FX model and linking it to an existing OPC UA Information Model (see B.3.4 ). The three approaches can be used in combination, in that the asset model
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.2 Creating a new model based on OPC UA FX
  bearing on the OPC UA FX model. When to use this approach: Creating an Information Model for a new companion specification, where all instances of the new model are expected ... Facets, like Motion and IO, could provide their own derived types. Creating an Information Model for a new vendor-specific specification. This is especially true for asset models, where
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.2.1 Extending an existing type
  B.3.2.1 Extending an existing type The Interfaces defined in the OPC UA FX Information Model can be added to an existing specification model to extend the model for providing ... allow the companion or vendor-specific specification to stay backwards compatible while publishing an Information Model that includes OPC UA FX. It does require a new version/release of the specification
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.2.2 Extending an instance of an existing type
  Interface to be applied to type objects or to instances. The OPC UA FX Information Model can be included via Interfaces into an instance of an existing Information Model . This ... existing Variables . When to use: Extending instances with Interfaces is used when an Information Model is already instantiated, and the type definition cannot be extended. Usually, this is instance-specific
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.3.1 General
  base model for Interface, but it has removed the iVendorNameplateType . Figure B.5 - Base Information Model for examples AddIns are used to attach OPC UA FX Information Model -specific content ... existing OPC UA Information Model . This is possible on the type definition level or the instance level. Only the type definition level is illustrated. The instance level would be identical
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.3.2 Extending an existing OPC UA model using AddIns
  which are bound with these references to the OPC UA instance of the existing Information Model . This type of update is illustrated in Figure B.6 Figure 4. When ... When it is important to include OPC UA FX functionality in an existing Information Model and the model does not include any of the functionality defined
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.4 Parallel use of OPC UA FX and existing UA models
  existing UA models A device might implement both a companion specification Information Model and the OPC UA FX Information Model . In this case, no new type would be required, just
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.3.5 Summary
  this annex are only some of the possible ways the OPC UA FX Information Model can be integrated into an existing model or used in conjunction with ... adoption? If yes, is backwards compatibility essential? Is it possible to extend the original Information Model (i.e. generate a new revision of the companion specification)? Does the existing model contain
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  C.1 OPC UA Safety Information Model
  Safety Information Model For the reader's convenience, some aspects of the OPC UA Safety Information Model are explained in this clause. For normative aspects, please refer ... definition and on how to calculate the value of OutCRC . Figure C.1 illustrates an Information Model for a SafetyProvider and its corresponding SafetyConsumer . Safety Variables are represented as dashed yellow
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.1 Overview
  Overview The Information Model defined for OPC UA FX can be applied in many different ways. To help illustrate some of these options, this annex provides examples for each part ... Information Model . This includes individual Assets examples, individual FunctionalEntity examples and examples of an AutomationComponent that includes both Assets and FunctionalEntities
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.2.2 Example single board computer model
  ports. The figure also illustrates the resulting instance model. This figure only includes the instance information related to the ConnectedTo Reference ; it does not include all of the other mandatory ... Figure D.6 - MyRaspberryPiInstance as part of a larger model Figure D.7 illustrates the entire Information Model for the Raspberry Pi described in this annex. Figure D.7 - Raspberry Pi complete Asset
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.6.1 Overview
  This AcmeAnalogueInputModuleType is external to the FunctionalEntity model; think of it as an existing Information Model . The FunctionalEntity then publishes this data to another controller, HMI, or even other devices
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.6.2 Using preconfigured DataSets
  data using a preconfigured DataSet containing all four channels. In this case, a possible Information Model would organise the Variables in OutputData (the top-level folder). The preconfigured PublishedDataSet
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.6.3 Using preconfigured and customised DataSets
  Channel3 to one controller and Channel1 to another controller). In this case, a possible Information Model looks like the one illustrated in Figure D.23 . However, PreconfiguredDataSetOnly set to False indicates
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.6.4 Using customised DataSets
  module supports data exchange with customised DataSets only. In this case, a possible Information Model looks like the one illustrated in Figure D.25 . However, the absence of PreconfiguredPublishedDataSets indicates that
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.6.5 Using groups
  channel input where a channel can be Int16 or Float. A possible Information Model is illustrated in Figure D.26 . Figure D.26 - Sample for analogue input module - using groups Again
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  D.3.7.3 Example of a complex ControlGroup
  FunctionalEntity representing this simplified AGV. Figure D.29 - Sample FunctionalEntity for a simplified AGV The Information Model offers two alternatives using a normalised value or raw data for controlling SpeedSetpoint
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  E.5 Interaction with an SKS
  generating keys for its configured SecurityGroups . The SKS can expose the SecurityGroups in its Information Model . A Publisher uses the current key to sign or sign and encrypt NetworkMessages ... equivalent on the key usage side. The SKS can expose the PubSubKeyPushTargets in its Information Model . The SKS responsible for generating the security keys related to a ConnectionConfigurationSet is indicated
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  F.1.2.2 Namespaces
  this illustration, the ConnectionConfigurationSet contains information for two different Servers . Node identifiers in the Information Model for the ConnectionManager (i.e., an instance of ConnectionConfigurationSetType ) use PortableNodeIdentifier (see 10.36 ) to support
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.4.2 Application and QoS engineering
  Controller's program, the engineering tool is used to create the UAFX Information Model representing that program. This Information Model consists of an AutomationComponent representing the entity being created ... given deployment. In either case, the VLAN interface is represented in the Information Model by an IetfBaseNetworkInterfaceType object, as described in  . Figure 7 illustrates the Information Model of a physical
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.4.4 System integration
  Additionally, new VLAN interfaces can be created if necessary. a As no OPC UA Information Model mechanism today allows the assignment of priority information for UA Client Server messages ... configured, the System Commissioner may update the PubSubCommunicationFlowConfiguration Variable in the ConnectionManager's Information Model to adapt the Connection configurations for QoS settings and network settings such as setting destination
• OPC-10000-82 – OPC Unified Architecture - Part 82: UAFX Networking
  5.6.4.5 Connection establishment and operation
  establishment and operation phase begins with the ConnectionManager establishing the Connections described in its Information Model . Connection establishment is either initiated by the ConnectionManager's internal logic ... details on Address and QoS, see OPC 10000‑14 . a As no OPC UA Information Model mechanism exists today that allows the assignment of priority or addressing information
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  5.2 Descriptor organization
  five kinds of files (see Figure 6 ). It contains a Descriptor manifest file and Information Model file(s) and can contain attachment files, embedded Descriptors, or Common Services . Figure ... version number for the content and a version number for the format. The Information Model files contain AML representations of UAFX Information Models . A worked-out example of the configuration
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  7.3.3 Information Model files
  Information Model files UAFX Information Model files are AutomationML files based on the OPC UA FX AML libraries defined in this document. UAFX Information Model files may also include ... other than the OPC UA FX AML libraries. There shall be at least one Information Model file present in a Descriptor . The organization of the Information Model files is explained
• OPC-10000-83 – OPC Unified Architecture - Part 83: UAFX OfflineEngineering
  8.3.2 Descriptor Import
  Root AML files and the relationship references ( 8.3.3 ); Parse the data of the Information Model files and convert the OPC UA FX Information Model to an internal representation ... main use cases for import are the import of an OPC UA FX Information Model of an AutomationComponent product and the import of an AutomationComponent configuration. Before starting the engineering
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.4.4.2 UAFX Descriptor Contents - UAFX Information Model
  UAFX Descriptor Contents - UAFX Information Model Table 12 describes UAFX Descriptor Contents - UAFX Information Model ConformanceUnits, which describe the UAFX Information Model contents of a Descriptor. For additional information about ... these items, please refer to OPC 10000‑81 . Table 12 - UAFX Descriptor Contents - UAFX Information Model Category Title Description UAFX Descriptor contents - UAFX IM - AutomationComponent Offline UAFX Descriptor AcDescriptor DescriptorIdentifier
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.4.4.3 UAFX Descriptor Contents - Networking Information Model
  UAFX Descriptor Contents - Networking Information Model Table 13 describes UAFX Descriptor Contents - Networking Information Model ConformanceUnits, which describe the UAFX Station Information Model contents of a Descriptor. For additional information ... these items, please refer to OPC 10000‑82 . Table 13 - UAFX Descriptor Contents - Networking Information Model Category Title Description Offline UAFX Descriptor Network Priority Mapping If the product supports
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  5.4.4.4 UAFX Descriptor Contents - Core UA Information Model
  UAFX Descriptor Contents - Core UA Information Model Table 14 describes UAFX Descriptor Contents - Core UA Information Model ConformanceUnits, which describe the Core UA Information Model contents of a Descriptor ... these items, please refer to OPC 10000‑7 . Table 14 - UAFX Descriptor Contents - Networking Information Model Category Title Description Offline UAFX Descriptor Core VendorServerInfo Includes the AML description
• OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles
  6.6.2.1 Overview
  Overview This clause defines Facets for the UAFX Information Model illustrated in Figure 2 , Figure 3 , and Figure 4 . Figure 2 - Structure of AutomationComponent related Facets Figure 3 - Structure
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.1 General
  internal to the host and can be based on field-specific protocols. The Information Model specifies the entities that can be accessed in a Device Integration Host . This standard does ... Node Management Services or proprietary configuration tools. One of the main tasks of the Information Model is to reflect the topology of the automation system. Therefore, it represents the Devices
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.1 Overview
  Overview The software update model defined in this clause is used to manage the software of a Device . This can include the installation of new software, the update of existing ... actual installation are only known by the device. They are not exposed by this Information Model . The use cases that were considered for this Information Model are described
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.2.12 Installation of additional software
  Installation of additional software Some devices can run several software applications. The Information Model should allow the Client to transfer and install additional software applications if the Server supports this
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.2.3.1 Finding devices that provide the SoftwareUpdate AddIn within a Server
  Server abstracts several devices that support the SoftwareUpdate AddIn , the Information Model shall provide a defined entry point to find all these devices in an efficient manner. This Use Case
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.3.1 System perspective
  maintained on a regular basis an automatic update is desirable. For this scenario the Information Model also allows the transfer of software to the devices without starting the update process
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.3.3 Types of Devices
  system which can be used to store files like firmware, parameters and backups. This Information Model provides update mechanisms for both types of devices (see 8.3.4.5 for FileSystem based Loading
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  A.1 NodeSet and Supplementary Files for DI Information Model
  NodeSet and Supplementary Files for DI Information Model The DI Information Model is identified by the following URI: http://opcfoundation.org/UA/DI/ Documentation for the NamespaceUri can be found here
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  B.3.2 Factory Automation example
  components last). Prepare devices for installation Stop production line software (using an application specific Information Model ). Bring the robots and PLCs into a state for update (using the PrepareForUpdate state ... machine and/or branch specific state machine). Restart production line software (using an application specific Information Model
• OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics
  A.1 NodeSet and supplementary files for Asset Management Basics (AMB) Information Model
  NodeSet and supplementary files for Asset Management Basics (AMB) Information Model The AMB Information Model is identified by the following URI: http://opcfoundation.org/UA/AMB/ Documentation for the NamespaceUri ... specification can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/AMB/&i=1 Supplementary files for the AMB Information Model can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/AMB/&v=1.01.1&i=2 The files associated with the latest version
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  3.3.1.1 Node definitions
  list of supported ConformanceUnits to select a subset of the Nodes in an Information Model . When a Node is selected in this way, all dependencies implied by the References
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  A.1 NodeSet and Supplementary Files for XML Data Types Information Model
  NodeSet and Supplementary Files for XML Data Types Information Model The XML Data Types Information Model is identified by the following URI: http://opcfoundation.org/UA/XML/ Documentation for the NamespaceUri
• OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation
  A.1 NodeSet and Supplementary Files for Industrial Automation (IA) Information Model
  NodeSet and Supplementary Files for Industrial Automation (IA) Information Model The IA Information Model is identified by the following URI: http://opcfoundation.org/UA/IA/ Documentation for the NamespaceUri can be found
• OPC-10000-210 – OPC Unified Architecture - Part 210: Relative Spatial Location
  9.1 Conformance Units
  Location Category Title Description Server RSL Base Supports the base functionality defined in RSL InformationModel with at least one instance of SpatialObjectsListType ( 6.2 ) organized by the RelativeSpatialLocations object. The SpatialObjectsListType
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  3.4.1.1 Node definitions
  list of supported ConformanceUnits to select a subset of the Nodes in an Information Model . When a Node is selected in this way, all dependencies implied by the References
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  4.2.2 Basics of OPC UA
  provides a set of Services (see OPC 10000-4 ) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information ... generic visualisation and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  4.2.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  4.2.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning
  A.1 NodeSet and supplementary files for Global Positioning Information Model
  NodeSet and supplementary files for Global Positioning Information Model The Global Positioning Information Model is identified by the following URI: http://opcfoundation.org/UA/GPOS/ Documentation for the NamespaceUri can be found ... specification can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/GPOS/&i=1 Supplementary files for the Global Positioning Information Model can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/GPOS/&v=1.0.0&i=2 The files associated with the latest version
• OPC-10031-4 – OPC UA for ISA-95 - Part 4: Job Control
  A.1 Namespace and identifiers for ISA95 Job Control Information Model
  Namespace and identifiers for ISA95 Job Control Information Model The ISA-95 Job Control Information Model is identified by the following URI: http://opcfoundation.org/UA/ISA95-JOBCONTROL_V2/ Documentation for the NamespaceUri ... found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/ISA95-JOBCONTROL_V2/&i=1 Supplementary files for the ISA95 Job Control Information Model can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/ISA95-JOBCONTROL_V2/&v=2.0.0&i=2 The files associated with the latest version
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  4.2.2 Basics of OPC UA
  provides a set of Services (see OPC 10000-4 ) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information ... generic visualisation and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  4.2.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  4.2.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-10100-1 – OPC UA for WoT Connectivity - Part 1: API Definition
  A.1 NodeSet and supplementary files for WoT Connectivity Information Model
  NodeSet and supplementary files for WoT Connectivity Information Model The WoT Connectivity Information Model is identified by the following URI: http://opcfoundation.org/UA/WoT-Con/ Documentation for the NamespaceUri can be found ... specification can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/WoT-Con/&i=1 Supplementary files for the WoT Connectivity Information Model can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/WoT-Con/&v=1.02.0&i=2 The files associated with the latest version
• OPC-10101 – OPC UA for WoT Binding
  4.2.2 Basics of OPC UA
  provides a set of Services (see OPC 10000-4 ) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information ... generic visualisation and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-10101 – OPC UA for WoT Binding
  4.2.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames
• OPC-10101 – OPC UA for WoT Binding
  4.2.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  1 Scope
  joint working group of the OPC Foundation and PLCopen. It defines an OPC UA Information Model to represent the IEC 61131-3 architectural models. It is important that the controller ... reduce costs for the development of these OPC UA servers if an OPC UA Information Model for IEC 61131-3 is used. OPC Foundation OPC is the interoperability standard
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  4.2.2 Basics of OPC UA
  provides a set of Services (see OPC 10000-4 ) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information ... generic visualization and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  4.2.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames
• OPC-30000 – OPC UA for Programmable Logic Controllers based on IEC61131-3
  4.2.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices
  6.1.3.16 Variable AutoIdModelVersion
  Variable AutoIdModelVersion This OPC UA Property of DataType String represents the AutoID Information Model version. The version string for this specification version
• OPC-30020 – MDIS OPC UA Companion Specification
  4 Terms, abbreviated terms and conventions
  understood in this document. This document will use these concepts to describe the MDIS Information Model
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.3 Basics of OPC UA
  generic visualisation and interface applications. This specification is an example of an OPC UA InformationModel designed to meet the needs of developers and users in the offshore
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.1 Concepts
  functionalities. The Data Access specification (see OPC 10000-8 ) provides a basic InformationModel for typical process or measured data. The Alarm and Condition specification (see OPC 10000-9 ) defines ... standard InformationModel for Alarms and Conditions . The Programs specification (see OPC 10000-10 ) defines a standard InformationModel for extending the functionality available via Method calls and state machines. The Historical
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.2 Namespaces
  InformationModels generally define globally unique NodeIds for the TypeDefinitions defined by the InformationModel . QualifiedNames are non-localised names qualified with a Namespace . They are used for the BrowseNames of Nodes
• OPC-30020 – MDIS OPC UA Companion Specification
  4.3.4.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an InformationModel by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used in the vertical
• OPC-30020 – MDIS OPC UA Companion Specification
  5.1 Overview
  point control purposes of the subsea system, along with topside controls. The MDIS InformationModel is able to adapt to both of these architectures. Figure 8 - Data Arbitration Example
• OPC-30020 – MDIS OPC UA Companion Specification
  14.3.1 Profile list
  describes the various Facets that are provided as part of the MDIS OPC UA InformationModel . These Facets include MDIS InformationModel ConformanceUnits , but they also include ConformanceUnits or Facets from
• OPC-30020 – MDIS OPC UA Companion Specification
  A.1 NodeSet and Supplementary Files for MDIS Information Model
  NodeSet and Supplementary Files for MDIS Information Model The MDIS Information Model is identified by the following URI: http://opcfoundation.org/UA/MDIS Documentation for the NamespaceUri can be found here
• OPC-30030 – OPC UA for BACnet - BACnet: OPC UA Information Model
  A.1 NodeSet and identifiers for BACnet Information Model
  NodeSet and identifiers for BACnet Information Model The BACnet Information Model is identified by the following URI: http://opcfoundation.org/UA/BACnet_V2/ Documentation for the NamespaceUri can be found here . The NodeSet ... specification can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/BACnet_V2/&i=1 Supplementary files for the BACnet Information Model can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/BACnet_V2/&v=2.00.1&i=2 The files associated with the latest version
• OPC-30060 – OPC UA for Tobacco Machine Communication
  4.2.2 Basics of OPC UA
  provides a set of Services (see OPC 10000-4 ) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information ... generic visualization and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-30060 – OPC UA for Tobacco Machine Communication
  4.2.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames
• OPC-30060 – OPC UA for Tobacco Machine Communication
  4.2.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  3.4.1.1 Node definitions
  list of supported ConformanceUnits to select a subset of the Nodes in an Information Model . When a Node is selected in this way, all dependencies implied by the References
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  4.2.2 Basics of OPC UA
  provides a set of Services (see OPC 10000-4 ) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor-defined information ... generic visualization and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  4.2.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  4.2.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-30081 – OPC UA for Process Automation Devices - PA-DIM™
  A.1 NodeSet and identifiers for PA-DIM Information Model
  NodeSet and identifiers for PA-DIM Information Model The PADIM Information Model is identified by the following URI: http://opcfoundation.org/UA/PADIM/ Documentation for the NamespaceUri can be found here ... specification can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/PADIM/&i=1 Supplementary files for the PADIM Information Model can be found here: https://reference.opcfoundation.org/nodesets/?u=http://opcfoundation.org/UA/PADIM/&v=1.02.0&i=2 The files associated with the latest version
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  4.2.2 Basics of OPC UA
  provides a set of Services (see OPC 10000-4 ) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information ... generic visualization and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  4.2.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames
• OPC-30090 – OPC UA for Field Device Tool (FDT) - Part <mm>: <Part Name>
  4.2.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  5.2.1 POWERLINK Objects and their attributes
  attributes POWERLINK Attribute Description Index Index and Sub-Index are provided by the Information Model as Properties of the Objects as defined in 5.2.2 , 5.2.3 and 5.2.4 . SubIndex Name ... mapping of primitive datatypes is defined in Table 22 . In certain cases the Information Model makes an exception and uses a Structure DataType to improve the usability. Examples for such
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  5.2.4 PowerlinkVariableType
  Client , but it also allows a generic implementation to interpret an imported Information Model because it already provides the required addressing information
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  8.1 General
  Communication Profiles EPSG DS 301 and EPSG DS 302. Without an extension of the Information Model the access to vendor- or profile-specific POWERLINK Objects would be only possible through ... convert the vendor specific device description from POWERLINK into an OPC UA Information Model and to deploy the models of all involved POWERLINK Devices to the OPC UA Server . This
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  9.2 OPC UA Conformance Units and Profiles
  Profiles This chapter defines the corresponding profiles and conformance units for the OPC UA Information Model for POWERLINK Profiles are named groupings of conformance units. Facets are profiles that will ... Client. The following tables specify the facets available for Servers that implement the POWERLINK Information Model companion standard, and for Clients that are communicating with such Servers . Table 51 defines
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  A.1 Namespace and identifiers for POWERLINK Information Model
  Namespace and identifiers for POWERLINK Information Model This appendix defines the numeric identifiers for all of the numeric NodeIds defined in this standard. The identifiers are specified ... found here: http://www.opcfoundation.org/UA/schemas/POWERLINK/Opc.Ua.POWERLINK.NodeIds.csv A computer processible version of the complete Information Model defined in this standard is also provided. It follows the XML Information Model schema syntax defined
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  A.2 Profile URIs for POWERLINK Information Model
  Profile URIs for POWERLINK Information Model Table 57 defines the Profile URIs for the POWERLINK Information Model companion standard. Table 57 - Profile URIs Profile Profile URI POWERLINK Direct Access Server
• OPC-30110 – OPC UA for POWERLINK - POWERLINK: OPC Unified Architecture
  B.2 Objects not defined in OPC UA Information Model
  Objects not defined in OPC UA Information Model Some of the objects in the POWERLINK Object Dictionary are not defined in the OPC UA Information Model of the current version
• OPC-30130 – OPC UA for Control & Communication System Profile(for Machine)
  8.2 OPC UA Conformance Unit and Profile
  Profile This section defines the profiles and conformance units of the OPC UA information model which are related to CSP+ for machine. Profiles are defined as a name of grouped ... Facet which can be used by a Server where companion specifications of the Information Model of CSP+ for machine are implemented. Table 9‑2 - CSP+ for machine Server Facet Definition
• OPC-30140 – OPC UA for PROFINET
  4.2.2 Basics of OPC UA
  provides a set of Services (see [OPC 10000-4] ) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information ... generic visualization and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-30140 – OPC UA for PROFINET
  4.2.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames
• OPC-30140 – OPC UA for PROFINET
  4.2.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-30141 – OPC UA for PROFIenergy
  1 Scope
  Scope This document specifies the OPC UA Information Model to represent the Object s and services that comprise PROFIenergy (PE) Energy Management as defined in chapter 4.1 . The PE Energy ... Management Information Model is based on PROFIenergy [PE CAP]. OPC Foundation OPC is the interoperability standard for the secure and reliable exchange of data and information in the industrial automation
• OPC-30141 – OPC UA for PROFIenergy
  3.1 Overview
  this document. This document will use these concepts to describe the PE Energy Management Information Model . For the purposes of this document, the terms and definitions given
• OPC-30141 – OPC UA for PROFIenergy
  4.2.2 Basics of OPC UA
  provides a set of Services (see [OPC 10000-4] ) and a basic Information Model framework. This framework provides an easy manner for creating and exposing vendor defined information ... that come with generic visualization and historian applications. This specification is an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-30141 – OPC UA for PROFIenergy
  4.2.3.1 Concepts
  Nodes in the AddressSpace of an OPC UA Server . Figure 6 - The OPC UA Information Model Notation A complete description of the different types of Nodes and References ... specification defines a very wide range of functionality in its basic Information Model . It is not required that all Clients or Servers support all functionality in the OPC UA specifications
• OPC-30141 – OPC UA for PROFIenergy
  4.2.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames ... Nodes and allow the same names to be used by different Information Model s without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances
• OPC-30141 – OPC UA for PROFIenergy
  4.2.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-30141 – OPC UA for PROFIenergy
  6 PE Energy Management Information Model
  Energy Management Information Model The PE Energy Management functionality and the Energy Measurement data are accessible for Clients directly when browsing the components of the "EnergyManagement" folder. Figure ... Relationship to functional application model Figure 9 shows the detailed PE Energy Management 's Information Model with the whole Object structure and the related type definitions. The figure contains
• OPC-30141 – OPC UA for PROFIenergy
  7 PROFIenergy Service Access Point Information Model
  PROFIenergy Service Access Point Information Model A connection of the PE Energy Management Information Model with the PROFINET model using PESAP Object s as shown in Figure ... Submodule representing the PROFIenergy service access point ( PESAP ) from the PE Energy Management Information Model . The properties attributed to a specific PE Entity in the PROFIenergy Object model like PROFIenergy
• OPC-30141 – OPC UA for PROFIenergy
  8.2.2 EnergyMeasurementType
  Reference shall be "PESAP". If the PESAP is not part of the Information Model , the RepresentedBy Reference in the EnergyMeasurementType Object is omitted. Mapping to PROFIenergy properties: BrowseName
• OPC-30141 – OPC UA for PROFIenergy
  8.3.1 EnergyDevicePowerOffType
  Reference shall be "PESAP". If the PESAP is not part of the Information Model , the RepresentedBy Reference in the EnergyDevicePowerOffType Object is omitted. The RegularTimeToOperate Variable shall contain
• OPC-30141 – OPC UA for PROFIenergy
  12.1 Conformance Units
  Conformance Units This chapter defines the corresponding Conformance Units for the OPC UA Information Model for PE Energy Management . Table 61 - Conformance Units for PE Energy Management Category Title Description ... Server PNEM Standby Management Supports the Standby Management functionality defined in Standby Management Information Model . Server PNEM Standby Management Control Supports the Standby Management functionality defined in Standby Management Information
• OPC-30141 – OPC UA for PROFIenergy
  A.1 Namespace and identifiers for OPC UA for PROFIenergy Information Model
  Namespace and identifiers for OPC UA for PROFIenergy Information Model This appendix defines the numeric identifiers for all of the numeric NodeIds defined in this document. The identifiers are specified ... found here: http://www.opcfoundation.org/UA/schemas/PNEM/NodeIds.csv A computer processible version of the complete Information Model defined in this document is also provided. It follows the XML Information Model schema syntax defined
• OPC-30141 – OPC UA for PROFIenergy
  B.1 PE Entity
  Client can find out the offered Energy Management functionality by browsing the Information Model (See Figure 8 and Figure 10 ). Since the PROFIenergy properties PE class and PE version ... device, to find out the PROFIenergy capabilities of the device and to create the Information Model for the device. Further on, OPC UA Client accesses to PROFIenergy services are routed
• OPC-30142 – OPC UA for PROFINET Remote IO
  1 Scope
  Scope This document specifies the OPC UA Information Model to represent the Object s and services that comprise Remote IO as defined in chapter 6 . The Remote IO Information Model ... features including transports without affecting existing applications Comprehensive information modelling capabilities: for defining any model from simple to complex PROFINET Standardization Group (PNO) The PROFIBUS and PROFINET user organization
• OPC-30142 – OPC UA for PROFINET Remote IO
  3.1 Overview
  this document. This document will use these concepts to describe the Remote IO Information Model . For the purposes of this document, the terms and definitions given
• OPC-30142 – OPC UA for PROFINET Remote IO
  4.3.2 Basics of OPC UA
  provides a set of Services (see OPC 10000-4 ) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information ... generic visualization and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-30142 – OPC UA for PROFINET Remote IO
  4.3.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames
• OPC-30142 – OPC UA for PROFINET Remote IO
  4.3.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-30142 – OPC UA for PROFINET Remote IO
  5 Use cases
  their "live" data in an Industrial Internet of Things ecosystem. Support standardized information model and data for digital twin Companies offering automation solutions in special domains want ... comprehensive understanding of the error condition. Obtain PROFINET Cyclic Telegram Semantics Explore the Telegram Information Model to obtain knowledge about the structure of the cyclic data and the related
• OPC-30142 – OPC UA for PROFINET Remote IO
  6.1 Introduction to OPC UA for PROFINET Remote IO
  PROFINET Remote IO The OPC UA for PROFINET Remote IO Information Model aims to offer Clients Objects and Services based on two RIO application profiles: Remote IO for Factory Automation ... Server allowing OPC UA Clients to access the IO data of PN Submodules . The Information Model is divided into a PROFINET aspect offering detailed Telegram information and a functional aspect
• OPC-30142 – OPC UA for PROFINET Remote IO
  7.1.1 RioChannelGroupType
  below) can only exist if the Server provides the PROFINET aspect of the Information Model . If the PROFINET aspect is provided by the Server, the RIO Channel Group Object shall
• OPC-30142 – OPC UA for PROFINET Remote IO
  8 OPC UA EventTypes
  submodule the affected channel belongs to in the PROFINET aspect of the Information Model (see OPC PN ). Both EventTypes defined in the following sections inherit the Severity Property from
• OPC-30142 – OPC UA for PROFINET Remote IO
  12.1 Conformance Units
  Conformance Units Table 135 defines the corresponding Conformance Units for the OPC UA Information Model for OPC UA for PROFINET Remote IO. Table 135 - Conformance Units
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  1 Scope
  Scope This document specifies the OPC UA Information Model to represent the Object s and services that comprise Remote IO as defined in chapter 6 . OPC Foundation ... features including transports without affecting existing applications Comprehensive information modelling capabilities: for defining any model from simple to complex PROFINET Standardization Group (PNO) The PROFIBUS and PROFINET user organization
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.1 Overview
  this document. This document will use these concepts to describe the PROFINET Encoder Information Model . For the purposes of this document, the terms and definitions given
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  3.5.1.1 Node definitions
  list of supported ConformanceUnits to select a subset of the Nodes in an Information Model . When a Node is selected in this way, all dependencies implied by the References
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  4.1.2 Encoder Object
  diagnosis mechanism Clock synchronous operation Fault buffer The OPC UA for PROFINET Encoder Information Model provides access to parameters, IO Data, diagnosis, and fault buffer information
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  4.1.3 Encoder Communication Model
  Encoder Communication Model The communication channels available between the P-Device and other Devices are shown in Figure 3 . Figure 3 - Overview about available Communication Services The Encoder Profile defined ... applies to Encoder devices using different communication protocols also. PROFINET specific parts of the Information Model are optional
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  4.2.2 Basics of OPC UA
  provides a set of Services (see OPC 10000-4 ) and a basic information model framework. This framework provides an easy manner for creating and exposing vendor defined information ... generic visualisation and historian applications. This specification is an example of an OPC UA Information Model designed to meet the needs of developers and users. OPC UA Clients
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  4.2.3.2 Namespaces
  Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames are non-localized names qualified with a Namespace. They are used for the BrowseNames
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  4.2.3.3 Companion Specifications
  Specifications An OPC UA companion specification for an industry specific vertical market describes an Information Model by defining ObjectTypes , VariableTypes , DataTypes and ReferenceTypes that represent the concepts used
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  5 Use cases
  their "live" data in an Industrial Internet of Things ecosystem. Support standardized information model and data for digital twin Companies offering automation solutions in special domains want ... access to the Encoder's fault buffer. Obtain PROFINET Telegram Semantics Explore the Telegram Information Model to obtain knowledge about the structure of the Telegram data. Providing PnTelegramType, PnIoTelegramType
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  6.1 Introduction to OPC UA for PROFINET Encoder
  Introduction to OPC UA for PROFINET Encoder The PROFINET Encoder Information Model aims to offer Clients Objects and Services based on the Encoder Profile as defined in [ ENCP ]. The Information ... specification can also be seen as an extension of the OPC UA for RIO Information Model as defined in [ OPC RIO ]. OPC UA for PROFINET Encoder consists of all Objects
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  6.2 Encoder Channel Signals and Measurements
  functional aspect. The figure shall give a basic understanding by demonstrating the model organization using three Standard Signals transmitted with Standard Telegram 89 (See [ ENCP ], chapter 5.6.2). Figure 10 - Encoder ... Standard Signals are linked to their counterpart Variables in the functional aspect of the Information Model using 0:RepresentsSameEntityAs References . The "ZSW2_ENC", "G1_XIST1
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  7.1.1 SetApplicationTag Method
  NIST_A or a NIST_B Signal Variable is part of the Information Model , the Velocity Variable shall be linked to the source Signal Variable using a 0:RepresentsSameEntityAs Reference
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  7.7 EncoderControlConfigType
  XIST1 Signal encoded as EncoderPresetControlEnumeration . If the G1_XIST1 Variable is part of the Information Model , XIST1 preset control setting is always available as Property of the G1_XIST1 Variable
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  7.8 EncoderSensorConfigType
  provided if not changeable. If the G1_XIST1 Variable is part of the Information Model , the shift factor is always available as Property of the G1_XIST1 Variable . The ShiftFactorXIST2 ... provided if not changeable. If the G1_XIST2 Variable is part of the Information Model , the shift factor is always available as Property of the G1_XIST2 Variable . The AbsolutePosLinSupported
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  11.1 Conformance Units
  Conformance Units Table 62 defines the corresponding ConformanceUnits for the OPC UA Information Model for PROFINET Encoder. Table 62 - Conformance Units for PROFINET Encoder Category Title Description Server PNENC Measurement
• OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>
  A.1 NodeSet and Supplementary Files for PROFINET - Encoder Information Model
  NodeSet and Supplementary Files for PROFINET - Encoder Information Model The PROFINET-Encoder Information Model is identified by the following URI: http://opcfoundation.org/UA/Machinery/PNENC/ Documentation for the NamespaceUri can be found
• OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model
  1 Scope
  Scope This document specifies the OPC UA Information Model to represent the Object s and services that comprise PROFINET GSD Generic as defined in chapter 6 . OPC Foundation ... features including transports without affecting existing applications Comprehensive information modelling capabilities: for defining any model from simple to complex PROFINET Standardization Group (PNO) The PROFIBUS and PROFINET user organization