Search

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

18 result(s) for Manufacturer

OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.12 Manufacturer

Manufacturer an organization that creates Devices
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.2 URIs

ProductInstanceUris identify a Device and are assigned by the Device Manufacturer (see OPC 10000-21 ). A DeviceIdentity Certificate has the ProductInstanceUri in the subjectAltName . These URIs conform ... product is first initialized on a particular Device . 4) ProductInstanceUri assigned by a Device Manufacturer : tag:<manufacturer-domain-name>,<yyyy-MM>:<product>:<serial
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services

7.1 Overview

onboard new Devices that depends on the Devices having support built in by the Manufacturer . If this support is not present, Devices and OPC UA Applications shall be manually onboarded
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.1 Device Lifecycle

that comprises of Devices , Composites or other computers connected via a network (see 3.1.13 ). Manufacturer An organization that creates Devices (see 3.1.12 ). CompositeBuilder An organization that creates Composites ... Device . A Ticket describing the Device is created and signed by the Manufacturer. Composite Assembly A Composite is created from Devices and a unique identity is assigned to the Composite
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.2 Firmware and Applications

generally not changed during normal operation. Firmware updates may be provided by the Manufacturer to correct software bugs or patch security flaws. A Device should have a mechanism to ensure
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.3 Transfer of Physical Control

Physical Control In 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
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

4.2.5 SoftwareUpdateManager

model defined in OPC 10000-100 , however, it often will be specific to the Manufacturer . This document defines APIs that allow any SoftwareUpdateManager to coordinate with the components defined
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

5.1 Device Identity

subjectAltName . If an LDevID Certificate is used it should be installed by the Manufacturer and signed by the Manufacturer CA. If the LDevID Certificate is signed by another organization, such ... creating, installing, securing and revoking the IDevID and LDevID Certificates depend on the Manufacturer , however, Devices should provide a SecureElement storage (for an example, see ISO/IEC 11889 ) to ensure
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

5.2 ProductInstanceUri

ProductInstanceUri ProductInstanceUri is a globally unique resource identifier assigned by the Manufacturer to a Device . This is often stamped on the outside of a physical component and may be used ... which does not exceed the limits imposed by the labelling technology chosen by the manufacturer; Truly globally unique with a structure that enforces it. Other standards, such
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.1 Tickets

trusted root 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 ... Ticket (see 8.1 ). Customers of the CompositeBuilder will not need a relationship with the Manufacturer of the Device to validate the Ticket . DeviceIdentity Certificates are typically signed with a chain
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.2 Ticket Distribution

Composite. The 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
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.2.2 BaseTicketType

Structure DataType defined in OPC 10000-5 . manufacturerName 0:String The name of the Manufacturer for the Device . modelName 0:String The model name assigned by the Manufacturer . Not specified ... name was assigned or known. modelVersion 0:String The model version assigned by the Manufacturer . Not specified if no model version was assigned or known. hardwareRevision 0:String The hardware
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

8.2.3 DeviceIdentityTicketType

DeviceIdentityTicketType The DeviceIdentityTicketType describes a single Device produced by a Manufacturer . The fields of this DataType are defined in Table 9 . Table 9 - DeviceIdentityTicketType Structure Name Type Description DeviceIdentityTicketType
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.2 FxAssetType definition

IVendorNameplateType Applied from IVendorNameplateType (defined in OPC 10000-100 ) 0:HasProperty Variable 5:Manufacturer 0:LocalizedText 0:PropertyType O 0:HasProperty Variable 5:ManufacturerUri 0:String 0:PropertyType ... Additional notes are provided for recommended usage within this model. " Manufacturer provides the name of the company that manufactured the item to which this Interface is applied
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.5.2 VendorNameplate Interface

Interface IVendorNameplateType includes Properties that are commonly used to describe a TopologyElement from a manufacturer point of view. They can be used as part of the identification. The Values ... BaseInterfaceType defined in OPC 10000-5 Product-specific Properties 0:HasProperty Variable 1:Manufacturer 0:LocalizedText 0:PropertyType O 0:HasProperty Variable 1:ManufacturerUri 0:String 0:PropertyType
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.3.2 CurrentVersion

determine a suitable update. Note: This version information is about the installed software. The Manufacturer is not necessarily the same as the Manufacturer of the physical device that executes
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.4.7.2 Manufacturer

Manufacturer The read only Manufacturer Property provides the name of the company that created the software. In case of the Pending Version this shall be empty if there