Search

10 result(s) for CompositeBuilder

• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  3.1.4 CompositeBuilder
  CompositeBuilder an organization that creates Composites
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  4.1 Device Lifecycle
  connected via a network (see 3.1.13 ). Manufacturer An organization that creates Devices (see 3.1.12 ). CompositeBuilder An organization that creates Composites (see 3.1.4 ). Distributor An organization that re-sells Devices and/or ... Composite . A Ticket describing the Composite is created and signed by the CompositeBuilder. Distribution The Device or Composite is stored until it is delivered to a CompositeBuilder , SystemIntegrator , OwnerOperator
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  4.2.3 Transfer of Physical Control
  many cases, the Distributor belongs to the same organization as the Manufacturer or CompositeBuilder . Similarly, the Integrator and the OwnerOperator may be the same organization. When a transfer of physical ... Operate (see Table 2 ) the equipment. For example, if an actor (e.g., a CompositeBuilder ) makes changes to a Device and then transfers this Device to another actor (e.g., an OwnerOperator
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  5.3 Composite Identity
  external network may have an LDevID Certificate (see 802.1AR ) created by the CompositeBuilder that can be used to prove the Device belongs to the Composite . The CompositeInstanceUri ... identifier for the Composite assigned by the CompositeBuilder . All Devices in the same Composite shall have the same CompositeInstanceUri . The CompositeInstanceUri follows the same rules as ProductInstanceUri
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  6.1 Tickets
  Certificate Authority that is likely to be in business even if the Manufacturer or CompositeBuilder has gone out of business. Tickets allow additional Signatures to be added at any time ... Ticket by choosing a Signature created by an authority it trusts. For example, a CompositeBuilder re-signs the Tickets for the Devices to associate the CompositeInstanceUri with the Device Ticket
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  6.2 Ticket Distribution
  DeviceIdentityTickets and CompositeIdentityTickets should be created and signed by the original Manufacturer and/or CompositeBuilder , however, a trusted intermediary, such as a Distributor , could create the Tickets or add additional Signatures
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  6.3 Authentication
  Authentication When a CompositeBuilder or Integrator receives a shipment of Devices it needs to connect them to their network and verify their authenticity. This process is automated ... externally visible Devices that are contained in a Composite . In these cases, the CompositeBuilder provides the list of Devices . When a Device is first connected to the network
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  7.1 Overview
  Application Instance Certificates . The revocation status check may be online if the Manufacturer or CompositeBuilder adds the cRLDistributionPoints or authorityInfoAccess extensions (see RFC 5280 ) to the DeviceIdentity Certificates . If those
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  8.1 Signed Ticket Encoding
  have additional signatures added by any actor in the supply chain. For example, a CompositeBuilder shall add Signatures to all Tickets for Devices incorporated into the Composite. The protected header ... type=DeviceIdentityTicketType opc-uri String The CompositeInstanceUri if the Signature was created by a CompositeBuilder who has incorporated the Device into a Composite
• OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding
  8.2.4 CompositeIdentityTicketType
  CompositeIdentityTicketType The CompositeIdentityTicketType describes a single Composite produced by a CompositeBuilder . The fields of this DataType are defined in Table 11 . Table 11 - CompositeIdentityTicketType Structure Name Type Description CompositeIdentityTicketType ... Composite. This value appears in LDevID Certificates assigned to Devices by the CompositeBuilder (see 5.3 ). devices 0:UriString [] A list of ProductInstanceUris for the Devices in the Composite that