Search

15 result(s) for Information Models

• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  3.2 Specification parts
  describes how UA Clients and Servers should interact with them. It also defines Information Models for Certificate management , key credential management, and authorization services. Part 13 ( OPC 10000-13 ) - Aggregates ... basic set of network related components to be used in more specific Information Models . Part 23 ( OPC 10000-23 ) - Common ReferenceTypes Part 23 specifies common types of references between Nodes
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  4.3 Design goals
  provide Clients with type definitions for the Objects accessed from the AddressSpace . This allows Information Models to be used to describe the contents of the AddressSpace . OPC UA allows data ... address space model and its own set of Services . OPC UA unifies the previous models into a single integrated address space with a single set of Services . OPC UA PubSub
• OPC-10000-1 – OPC Unified Architecture - Part 1: Overview and Concepts
  5.3.4.4 Support for information models
  Support for information models The OPC UA AddressSpace supports Information Models . This support is provided through: Node References that allow Objects in the AddressSpace to be related to each other ... industry specific data types to be used. Industry groups can define how their specific information models are to be represented in Server AddressSpace
• OPC-10000-7 – OPC Unified Architecture - Part 7: Profiles
  4.2 Conformance Units and Conformance Groups
  specific set of features (e.g. a group of services, portions of services or information models) that can be tested as a single entity. ConformanceUnits are the building blocks ... These groups reflect different OPC UA aspects like the Service Sets , security, transport, and Information Models . ConformanceGroups have no impact on testing; they are used only for organizational reasons. These
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.1 General
  General Clause  6 describes the integration of this document into the OPC UA Information Models in 6.2 and the resulting Service interfaces in 6.3 . Diagnostic services are described
• OPC-10000-15 – OPC Unified Architecture - Part 15: Safety
  6.2.2.1 SafetyACSet Object
  Object derived from DataType SafetyConsumerType for each SafetyConsumer it implements. The corresponding Information Models shown in Figure 3 and Figure 4 shall be used. A description of the graphical notation
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.1 Overview
  Implementing these workflows requires an OPC UA Information Model . This section builds on existing Information Models and defines the additional types and instances needed to completely implement the workflows. Clause
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  1 Scope
  Model for a basic set of network related components to be used in other Information Models . The initial version of this document defines parameter sets for TSN Talkers and Listeners
• OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model
  4.2 Usage of OPC UA Interfaces
  future ObjectType hierarchies. This allows these grouped parameters to be used in other Information Models independent of ObjectType hierarchies that can be found in the BNM. It is expected that
• 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 ... future for Motion, I/O, and many types of process instruments. Specifications, including Information Models , developed for those types of products will build upon the AutomationComponent model
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  1 Scope
  Controller-to-Controller, Controller-to-Device, Device-to-Device and Controller/Device-to-Compute. It includes base Information Models for devices and controllers, ensuring smooth, high-speed information flow for critical factory ... process systems. These systems can include safety systems. It is expected that the Information Models specified in this document will be extended to include other specific device or system types
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.1 OPC UA FX ObjectTypes overview
  Model . It also specifies a number of Interfaces that can be applied to existing Information Models , allowing existing models to be used as part of an OPC UA FX system ... additional guidance on mapping this model to existing Information Models , see Annex B . For an overview of the main OPC UA FX ObjectTypes , see Figure 17 . Figure 17 - Overview
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  B.1 Overview
  Overview There are three main approaches for applying OPC UA FX to existing Information Models . Creating a new model based on the OPC UA FX Information Model (see B.2 ). Extending
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  8.3.1 System perspective
  start the operation). For this case a specialized Client can use additional domain-specific Information Models as part of the update process. An update can be performed manually ... 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-211 – OPC Unified Architecture - Part 211: Global Positioning
  4.2.3.2 Namespaces
  have built-in knowledge of what the data means in these Nodes . OPC UA Information Models generally define globally unique NodeIds for the TypeDefinitions defined by the Information Model . QualifiedNames ... BrowseNames of Nodes and allow the same names to be used by different information models without conflict. TypeDefinitions are not allowed to have children with duplicate BrowseNames ; however, instances