Search

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

15 result(s) for OwnerOperator

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-3 – OPC Unified Architecture - Part 3: Address Space Model

4.2 URIs

Application running on a particular Device and are assigned by the OwnerOperator or automatically created by the application software. An ApplicationInstance Certificate has the ApplicationUri in the subjectAltName ... name> is a short identifier for the InformationModel . 2) ApplicationUri assigned by the OwnerOperator tag:<device-domain-name>,<yyyy-MM>:<product
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.17 SystemIntegrator

SystemIntegrator an 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

unique identifier and communicates with other Applications on the network (see 3.1.1 ). OwnerOperator An organization deploying and operating a system that comprises of Devices , Composites or other computers connected ... resale (see 3.1.11 ). SystemIntegrator An organization that installs and configures a system for an OwnerOperator that comprises of Devices , Composites or other computers connected via a network (see 3.1.17 ). RegistrarAdmin
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.3 Transfer of Physical Control

same organization as the Manufacturer or CompositeBuilder . Similarly, the Integrator and the OwnerOperator may be the same organization. When a transfer of physical control occurs, the supplier ships the equipment ... changes to a Device and then transfers this Device to another actor (e.g., an OwnerOperator ) then those changes may restrict what the new owner is able to do, i.e., CompositeBuilder
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.4 Trust on First Use (TOFU)

First Use (TOFU) The onboarding process defined in this document describes how an OwnerOperator can authenticate Devices added to the network. This document does not define any mechanisms to allow
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.5 SoftwareUpdateManager

described in clause 7 . The SoftwareUpdateManager may not be present in systems where the OwnerOperator has other mechanisms in place to ensure the Devices have up to date firmware
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.3.3 Application Setup

Some Applications on a Device could have access rights that prevent the Integrator or OwnerOperator from changing the setup for the Application . This could occur if Applications are used
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.3.6 Decommissioning

that all sensitive data is deleted. Any permissions granted to the Device on the OwnerOperator network are revoked. The DeviceIdentity Certificates and their associated PrivateKeys are not affected ... mistake can be Onboarded again as described in 4.3.2 . In some cases, the OwnerOperator may wish to prevent the Device from being used again by removing/destroying the SecureElement or some
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.2 Ticket Distribution

connected to the network or done when a new Device is detected. When an OwnerOperator initially receives a Ticket, it may wish to validate them immediately and add a Signature ... further need for access to an external system to check revocation lists. The OwnerOperator can also manage the issue of expiring Certificates by periodically re-validating and adding
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.3 Authentication

Certificate will have a shorter lifespan and a CA which is managed by the OwnerOperator . This Certificate allows all Applications running on the Device to automatically be onboarded and configured
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.4 Acquiring and Validating Tickets

needed to determine if any given Device is allowed to be connected to the OwnerOperator's network. There are two strategies for validating Tickets that depend on how the Tickets ... ertificates for code/document signing could be a root CertificateAuthority for Ticket signing. Each OwnerOperator is responsible for maintaining a list of trusted root CertificateAuthorities which are accepted by the organization
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.2 Pull Management

Device to reset the DCA TrustList and restart the Device authentication process. The OwnerOperator should have a strategy to detect and remove rogue Registrars since the DCA always trusts
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.3 Push Management

shall reject connections from Registrars that are not in the TrustList . The OwnerOperator should have a strategy to detect and remove rogue Registrars since the DCA always trusts the first
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.4.1 Overview

meet the complete set of requirements described in this specification. However, an OwnerOperator may have reasons to use one of these other mechanisms (i.e. they have the infrastructure and wish ... reuse it). In some cases, the OwnerOperator have a complete solution that manages the entire life cycle of the Certificates installed on the Device . In these cases, the onboarding mechanisms