Search

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

28 result(s) for ProductInstanceUri

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

3.1.15 ProductInstanceUri

ProductInstanceUri a globally unique resource identifier assigned by the manufacturer to a Device
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

4.2 URIs

assigned by the Device Manufacturer (see OPC 10000-21 ). A DeviceIdentity Certificate has the ProductInstanceUri in the subjectAltName . These URIs conform to RFC 3986 , however, this specification is very open ... unique identifier generated when the product is first initialized on a particular Device . 4) ProductInstanceUri assigned by a Device Manufacturer : tag:<manufacturer-domain-name>,<yyyy
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

3.1.10 DeviceIdentity Certificate

Device that identifies the Device . Note 1 to entry: All DeviceIdentity Certificates have the ProductInstanceUri as a subjectAltName . Note 2 to entry: All DeviceIdentity Certificates are IDevID or LDevID Certificates ... defined by 802.1AR . Note 3 to entry: The ProductInstanceUri is the ApplicationUri when the DeviceIdentity Certificate is used to create a SecureChannel
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

5.1 Device Identity

shall include a Private Key and an X.509v3 Certificate . IDevID Certificate should have the ProductInstanceUri (see 5.2 ) as a uniformResourceIdentifier in the subjectAltName field (see RFC 5280 ). If the IDevID ... Certificate does not have the ProductInstanceUri the Device shall have an LDevID (Locally Significant Device Identifier) Certificate with the ProductInstanceUri in the subjectAltName . If an LDevID Certificate is used
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
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

5.3 Composite Identity

same Composite shall have the same CompositeInstanceUri . The CompositeInstanceUri follows the same rules as ProductInstanceUri (see 5.2 ). The subjectAltName is an array of alternate names for the Device . Each entry ... IDevID and LDevID shall have at least one URI name which is the ProductInstanceUri. LDevIDs created for a Composite shall have at least two URI names, the ProductInstanceUri
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

6.2 Ticket Distribution

build a list of Devices and Composites which are allowed on the network. The ProductInstanceUri and CompositeInstanceUri are used to correlate a Device with a Ticket . A Ticket
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.1 Overview

Read all DeviceIdentity Certificates from the Device ; Locate a Ticket that has a ProductInstanceUri that matches one or more DeviceIdentity Certificates ; Validate the Ticket if it has not already been ... where the DCA is running). Registrar first looks for a Certificate that has a ProductInstanceUri as a value in the subjectAltName of the Certificate . The Registrar first searches
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

7.4.1 Overview

trusted by the Registrar, SoftwareUpdateManager and CertificateManager . This Certificate shall also contain a ProductInstanceUri (see 5.2 ) which uniquely identifies the Device . If a software update check is required
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

8.2.3 DeviceIdentityTicketType

Type Description DeviceIdentityTicketType 0:Structure Subtype of the 2: BaseTicketType DataType defined in 8.2.1 . productInstanceUri 0:UriString The ProductInstanceUri for the Device . Its representation in the AddressSpace is defined
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

8.2.4 CompositeIdentityTicketType

Structure Subtype of the 2: BaseTicketType DataType defined in 8.2.2 . compositeInstanceUri 0:UriString The ProductInstanceUri assigned to the Composite. This value appears in LDevID Certificates assigned to Devices
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding

9.2.4 UpdateSoftwareStatus

that has access to the SoftwareUpdateAdmin Role (see 4.2.6 ). Signature UpdateSoftwareStatus( [in] 0:String productInstanceUri, [in] 0:Boolean status, [in] 0:String softwareRevision ); Argument Description productInstanceUri The unique identifier ... Session does not have the permissions needed to call the Method . Bad_NotFound The productInstanceUri does not refer to a known Device . Table 19 specifies the AddressSpace representation
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.3.2 FxAssetType definition

HasProperty Variable 5:SerialNumber 0:String 0:PropertyType O 0:HasProperty Variable 5:ProductInstanceUri 0:String 0:PropertyType O 0:HasProperty Variable 5:RevisionCounter 0:Int32 0:PropertyType ... physical component and may be used for traceability and warranty purposes." " ProductInstanceUri is a globally unique resource identifier provided by the manufacturer. This is often stamped
OPC-10000-84 – OPC Unified Architecture - Part 84: UAFX Profiles

5.2.4 UAFX FxAsset

including the VerificationMode of AssetIdentityAndCompatibility. Server UAFX IVendorNameplate SerialNumberOrProductInstanceUri Supports either the SerialNumber or ProductInstanceUri Property of the IVendorNameplate Interface. IAssetExtensions Server UAFX IAssetExtensions Connectors Supports the Connectors Folder
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.5.2 VendorNameplate Interface

HasProperty Variable 1:SerialNumber 0:String 0:PropertyType O 0:HasProperty Variable 1:ProductInstanceUri 0:String 0:PropertyType O 0:HasProperty Variable 1:RevisionCounter 0:Int32 0:PropertyType ... outside of a physical component and can be used for traceability and warranty purposes. ProductInstanceUri is a globally unique resource identifier provided by the manufacturer. This is often stamped
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

8.7.5 Solution packages

that ObjectType . True TargetNode 0:NodeId Install to specific node on the server. True ProductInstanceUri 0:String Specific target with the ProductInstanceUri (see 4.5.3 ). True AssetId 0:String Specific target ... updated. If a TargetNode is specified, only this node shall be updated. If a ProductInstanceUri is specified, only the target with the specified ProductInstanceUri in its IVendorNameplateType shall be updated
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

7 Identification of Asset

those. In order to allow a globally unique identification of an asset, the 2: ProductInstanceUri shall be provided (see ConformanceUnit AMB Asset Identification in 15.1 ). It shall be either
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

8.1 Overview

this specification defines two standardized categories for AliasNames , one using the mandatory 2: ProductInstanceUri as AliasName , and another one using the writable 2: AssetId , which ... FindAlias on one of the Objects , allowing potentially to filter for the 2: ProductInstanceUri or the 2: AssetId . To get notified if assets have been added or removed, the Client
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

8.2.2 AssetsByProductInstanceUri

Table 12 . All AliasNames organized by this category shall be assets having a 2: ProductInstanceUri (see section 7 ). The string part of the AliasName shall be identical to the value ... ProductInstanceUri, the namespace of the AliasName shall be the one defined by this specification in section 16 . Table 13 - AssetsByProductInstanceUri Definition Attribute Value BrowseName AssetsByProductInstanceUri Description Entry point to discover
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics

8.2.3 AssetsByAssetId

same AliasName Object . Same assets shall be, in this case, identified by the 2: ProductInstanceUri . In this case, the string part of the AliasName shall be "NoAssetIdAssigned ... more than one asset Node , meaning several asset Nodes have the same 2: ProductInstanceUri , the same 2: AssetId should be used. As the 2: AssetId is set by the user
OPC-10000-200 – OPC Unified Architecture - Part 200: Industrial Automation

7.4.1 CalibrationTargetType ObjectType

Properties are defined as optional. It is recommended to provide the 2: ProductInstanceUri to uniquely identify the calibration target. Other Properties , like 2: SoftwareRevision , will in most cases ... Variable 2:SerialNumber 0:String 0:PropertyType O 2:Identification 0:HasProperty Variable 2:ProductInstanceUri 0:String 0:PropertyType O 2:Identification 0:HasProperty Variable 2:RevisionCounter 0:Int32
OPC-30300 – Using Generic Trust Anchor (GTA) API with OPC UA - Part 1: Generic Trust Anchor (GTA) API Profile for OPC UA

4.2.3 GTA API and OPC UA object model mapping

object model. To express this relation the Identifier value is set to either the ProductInstanceUri or ApplicationUri (cf. 4.3.2.1 ). The GTA API object model does not provide an equivalent
OPC-30300 – Using Generic Trust Anchor (GTA) API with OPC UA - Part 1: Generic Trust Anchor (GTA) API Profile for OPC UA

4.3.2.2 GTA API personalities

CertificateType>&ix=<GenerationIndex>] where <InstanceUri > is either the ProductInstanceUri or the ApplicationUri <CertificateGroup> is the Name portion of the BrowseName
OPC-30300 – Using Generic Trust Anchor (GTA) API with OPC UA - Part 1: Generic Trust Anchor (GTA) API Profile for OPC UA

5.2.1 Preconditions

supplied by the DCA: urn:manufacturer.com:2024-10:myproduct:SN51235 for the ProductInstanceUri urn:manufacturer.com:2024-10:myproduct:SN51235?cg=DefaultApplicationGroup&ct=EccNistP256 for the base personality name
OPC-40001-1 – OPC UA for Machinery - Part 1: Basic Building Blocks

5.1 Machine Identification and Nameplate

leads to the requirements: A machine shall be globally uniquely identified (see section 8 , ProductInstanceUri ). Information about the machine, like manufacturer or serial number, can be accessed (see section
OPC-40444 – OPC UA for Textile Testing Devices

9.1 TTDResultType

additional information about the generated result. The added information is: SampleId TesterJobId TesterSampleResultId ProductInstanceURI It is formally defined in Table 38 . Table 38 - TTDResultType Definition Attribute Value BrowseName TTDResultType IsAbstract ... HasStructuredComponent Variable 4:CreationTime 0:UtcTime 0:BaseDataVariableType M 4:ResultMetaData 0:HasStructuredComponent Variable ProductInstanceUri 0:String 0:BaseDataVariableType M 4:ResultMetaData 0:HasStructuredComponent Variable TesterSampleResultId 0:String 0:BaseDataVariableType
OPC-40444 – OPC UA for Textile Testing Devices

10.7 TTDResultMetaDataType

describe the results generated by the TTD. Especially the fields SampleId , TesterJobId , TesterSampleResultId , ProductInstanceURI and CanBeDeleted were added to offer a better possibility to relate a result to a measurement ... Necessary additional to the SampleId if the sample is tested more than once. False ProductInstanceURI 0:String Unique product instance uri of the TTD. False CanBeDeleted 0:Boolean Flag
OPC-40450-1 – OPC UA for Joining Systems - Part 1: Base

7.2 JoiningSystemIdentificationType ObjectType Definition

Node. 0:HasProperty Variable 0:DefaultInstanceBrowseName 0:QualifiedName 0:PropertyType 0:HasProperty Variable 2:ProductInstanceUri 0:String 0:PropertyType O 0:HasProperty Variable Name 0:String 0:PropertyType ... Attribute 0:DefaultInstanceBrowseName 2:Identification The default BrowseName for instances of the type. 2: ProductInstanceUri is a globally unique resource identifier provided by the manufacturer. Name is the name