Search

16 result(s) for Composites

• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  1 Scope
  Scope This part defines the life cycle of Devices and Composites and mechanisms to verify their authenticity, set up their security and maintain their configuration
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  3.1.3 Composite
  Composite a collection of Devices or Composites assembled into a single unit. Note 1 to entry: Each Composite has a globally unique identifier. Note 2 to entry: A Composite
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  3.1.11 Distributor
  Distributor an organization that re-sells Devices and/or Composites. Note 1 to entry: A Distributor may enhance Devices and Composites by adding customized products or services
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  3.1.13 OwnerOperator
  OwnerOperator an organization deploying and operating a system that comprises of Devices , Composites or other computers connected via a network
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  3.1.17 SystemIntegrator
  organization that installs and configures a system for an OwnerOperator that comprises of Devices , Composites or other computers connected via a network
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  4.1 Device Lifecycle
  have one or more Applications (see 3.1.4 ). Composite A collection of Devices or Composites assembled into a single unit. Each Composite has a unique identifier and may appear ... OwnerOperator An organization deploying and operating a system that comprises of Devices , Composites or other computers connected via a network (see 3.1.13 ). Manufacturer An organization that creates Devices
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  4.2.3 Transfer of Physical Control
  Physical Control Implicit in the Device lifecycle is the notion that Devices and Composites will be physically delivered to different actors. The transfers of physical control that may occur
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  4.3.1 Distribution
  Distribution Distribution is the process of transferring physical control of Devices and Composites from one organization to another. This transfer of physical control is accompanied by the electronic transfer
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  5.3 Composite Identity
  external network and have one or more Applications that need to be provisioned. Composites are an abstraction on a network and can only be physically accessed via one or more ... contains the values. URI names that cannot be matched to a Ticket are ignored. Composites may contain other Composites and Devices. The contained Composite may be externally visible outside
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  6.2 Ticket Distribution
  Ticket Distribution When physical control over Devices and/or Composites is transferred from one organization to another there needs to be a physical transfer of goods and an electronic transfer ... Tickets associated with the Devices and Composites . The Tickets allow the new user to verify the authenticity of the Devices and Composites they received by using the handshake defined
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  6.4 Acquiring and Validating Tickets
  band mechanism which provides the Tickets for the Devices and Composites that will be delivered to the facility before the Devices are connected to the network. This could be done
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  8.2.5 TicketListType
  TicketListType The TicketListType describes a list of Device s and Composites which are part of a shipment from one organization to another. The fields of this DataType are defined ... devices 0:EncodedTicket [] A list of signed DeviceIdentityTickets . The format is described in 8.1 . composites 0:EncodedTicket [] A list of signed CompositeIdentityTickets . The format is described in 8.1 . Its representation
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  8.2.6 CertificateAuthorityType
  CertificateAuthorityType The CertificateAuthorityType describes a Certificate Authority (CA) used to issue Certificates to Devices , Composites or to organizations that create Tickets . The fields of this DataType are defined in Table
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.2.10 DeviceRegistrarAdminType
  Method allows an administration Client to provide a list of Tickets for Devices and Composites that it is expecting to install on the network. Any Device which matches ... automatically. The UnregisterTickets Method allows an administration Client to remove Tickets for Devices and Composites that it previously provided. Removing Tickets does not affect Devices that were previously accepted using
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.2.11 RegisterTickets
  Method allows an administration Client to provide a list of Tickets for Devices and Composites that it is expecting to install on the network. Any Device which can be correlated
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  9.2.12 UnregisterTickets
  UnregisterTickets The UnregisterTickets Method allows a RegistrarAdmin to remove Tickets for Devices and Composites that it previously provided. Removing Tickets does not affect Devices that were previously accepted using